chapter 4 Flashcards
requirement
an expression of desired behavior.
focus on the customer’s needs.
the “what” instead of the “how.”
software requirements specification (SRS)
performed by analyst or system analyst.
they are responsible for obtaining user’s requirements.
stakeholders
any person who is impacted by the system.
anyone who has a stake.
clients
pay for the software to be developed.
customers
buy the software after it’s developed.
users
use the system.
domain experts
familiar with problems that the software must automate.
market researchers
conduct surveys to determine future trends and potential customers.
lawyers or auditors
familiar with the government, safety, or legal requirements.
software engineer
technology experts
means of obtaining software requirements
interviewing stakeholders.
observing current systems.
brainstorming with current and potential users.
types of requirements
functional requirements: required activities. quality requirements (non-functional): quality characteristics the software must posses. design constraints: platform, interface, etc. process constraints: restriction on techniques or resources that can be used.
requirements: essential
must be met.
requirements: desirable
not necessary but nice to have.
requirements: optional
possible but could be eliminated.