Requirements Engineering Flashcards
Where does RE start?
Starts with defining a problem to be tackled.
What is the key task of Problem Definition
Formulating a well defined problem so it can be reasonably solved
What is a stakeholder?
an Individual, Team, Organization with interests in, or concerns relating to the system to be
Do all stakeholders coalesce harmoniously?
No, you will have to make compromises and tradeoffs to satisfy all different stakeholders.
What are the components of RE?
- Requirements Elicitation.
- Requirements Analysis
- Requirements Specification
Define Requirements Elicitation
Help customer define what’s required, what is to be accomplished, how the system fits their needs, and how it will be used on a daily basis.
Define Requirements Analysis
Refining and modifying the gathered requirements
Define Requirements Specification
Documenting system requirements in a semi-formal or formal matter, to ensure clarity, consistency and completeness.
What are the different types of requirements
- Functional
- Non-functional
Define functional requirements
FRs are those that provide fundamental reason for the product’s existence.
Specifies what the product must do.
Define non-functional requirements
Quality of the entire system.
- Look and feel
- Usability (ease of use/learning)
- Performance
Define parts of the SRS
Open Issues
Off the shelf solutions (existing product, Ready made components, something to follow or copy)
New Problems (in the environment, existing users, limitations in the environment.)
Properties of Requirements
Abstract Unambiguous Traceable Validatable Complete Consistent
Tools for Requirements?
Most popular tool is the Use Case modelling
What are Use Cases?
step-by-step description of how a user will use a system to accomplish business goals.
Specifies what the system needs to accomplish.
Detailed use cases are written in usage scenarios or scripts.
What is an Actor
Person or other system that interacts with a system.
There are:
Initiating actors who initiate the use case.
Supporting Actors help the system complete the use case
Offstage actor, passively participates in the use case.
Detailed Use cases
Text stories that detail what happens when an actor attempts to obtain a service from a system.
A scenario is called a use case instance
Don’t mistake a use case for the diagram.
Use case format
Req. initiating actor actor goal participating actors Pre cond. Post cond.
Scenarios
Alt. scenarios
Who is interested in the SRS?
- Customers and Users
- Developers
- Testers
- Project Management
