10 Questions
What does the vision and scope document in the software requirement engineering domain contain?
Product's business requirements
In the pure waterfall life cycle, where is most of the requirements development effort allocated?
Beginning of the project
What is the purpose of creating user personas in software requirement engineering?
To represent particular user classes
What is the role of a product champion in requirement engineering?
Representing the voice of the customer for each user class
When does the traditional 'requirements phase' typically occur in a project following a waterfall model?
Beginning of the project
What is the purpose of defining a product vision and project scope in software development?
To provide a common understanding of the product’s outcome
What does identifying user classes and their characteristics help accomplish in software requirement engineering?
Avoiding overlooking the needs of any user community
"Even if you plan a traditional 'requirements phase' at the beginning of a project, you can count on having to do some additional requirements work". What does this statement imply about the software development process?
'Requirements phase' is a continuous process throughout the project
"In the pure waterfall life cycle, you plan to do only one major release". What characteristic of the waterfall model does this statement highlight?
'Requirements phase' is planned only once at the beginning
"Identify various groups of users for your product to avoid overlooking their needs". Why is this considered an important step in software requirement engineering?
To ensure all user needs are considered
Study Notes
Requirements Development Process Framework
- The requirements development process is interwoven, incremental, and iterative, with progressive refinement of detail.
- The process involves 7 initial steps and additional steps for each release or development iteration.
- The process framework is flexible and can be adjusted for different projects.
Requirements Analysis
- Model the application environment using simple analysis models like context diagrams and ecosystem maps.
- Create user interface and technical prototypes to clarify requirements and achieve mutual understanding.
- Analyze requirement feasibility by evaluating the implementation cost, performance, and risks associated with each requirement.
Requirements Elicitation
- Define product vision and project scope to establish a common understanding of the product's outcome.
- Identify user classes and their characteristics to avoid overlooking user needs.
- Create user personas to represent particular user classes.
- Select a product champion for each user class to serve as the literal voice of the customer.
Software Development Life Cycles
- Different life cycles allocate requirements effort across the product development period.
- The total requirements effort may not vary significantly between projects, but the timing distribution of requirements work is different.
- Examples of life cycles include the pure waterfall life cycle, which allocates most requirements development effort at the beginning of the project.
Learn about the requirements development process framework in the field of Requirement Engineering. Understand that these activities are interwoven, incremental, and iterative, rather than a simple linear sequence, allowing for progressive refinement of detail.
Make Your Own Quizzes and Flashcards
Convert your notes into interactive study material.
Get started for free
