40 Questions
What do non-functional requirements often constrain?
The system being developed and the development process
How many key activities are involved in requirements engineering?
Three
What is another term for the software requirements document?
Software Requirements Specification
Why do some agile methods argue against producing a requirements document?
Because requirements change quickly and the document becomes outdated
What is used in XP to express requirements instead of a requirements document?
User stories
What type of systems may not be suitable for agile methods that don't use a requirements document?
Critical systems
What do non-functional requirements often relate to?
The system's emergent properties
How do agile methods like XP approach requirements engineering?
Through incremental requirements engineering
What are the three key questions that a system should answer before implementing a project?
Does the system contribute to the overall objectives, can it be implemented within schedule and budget, and can it be integrated with other systems.
What is a key objective of the requirements elicitation and analysis process?
To find out about the application domain, services, and required system performance.
What is the purpose of the software requirements document?
To provide an agreed statement of the system requirements.
What is the main goal of the requirements prioritization and negotiation stage?
To prioritize and negotiate system requirements with stakeholders.
What is the main problem of requirements elicitation and analysis?
Stakeholders may hold back information.
What is the main objective of the requirements discovery stage?
To find out about the application domain, services, and required system performance.
What is the purpose of the requirements classification and organization stage?
To organize and categorize system requirements.
What happens if any of the three key questions are answered 'no'?
The project should probably not go ahead.
What is the primary purpose of the system architecture chapter?
To present a high-level overview of the anticipated system architecture
What type of information can be included in the system requirements specification chapter?
Graphical system models showing the relationships between system components
What is the purpose of the system evolution chapter?
To help system designers avoid design decisions that would constrain likely future changes
What type of information is typically included in the appendices?
Detailed, specific information related to the application being developed
What is the primary purpose of the system models chapter?
To show the relationships between system components and the system and its environment
What type of information can be included in the system requirements chapter?
Interfaces to other systems
What is the primary purpose of the description chapter?
To provide a natural language description of the system
What is the primary purpose of the system architecture chapter in relation to reused components?
To highlight architectural components that are reused
What is the main purpose of requirements validation techniques?
To ensure that the system meets the user's needs
What is the primary reason for changing requirements after installation?
The business and technical environment of the system always changes
Who imposes requirements due to organizational and budgetary constraints?
System customers
What is the primary goal of requirements management?
To ensure the system meets user needs
What is a consequence of changing business priorities?
Changes in the system support required
Why may new features need to be added to a system after delivery?
To support the system's end-users
What is a common conflict in system development?
Between system customers and end-users
What is the result of new legislation and regulations being introduced?
The system must necessarily abide by the new laws
What is the primary goal of requirements validation?
To ensure that the requirements are realistic and verifiable
What is the purpose of change analysis and costing?
To assess the effect of the proposed change on the system
What is the primary outcome of requirements change management?
A managed and controlled change to the system requirements
What is the purpose of traceability information in change analysis?
To assess the effect of the proposed change on the system
What is the outcome of a change proposal that is not accepted?
The change is withdrawn and the request is cancelled
What is the purpose of organizing the requirements document?
To make changes easier to implement
What is the primary goal of requirements elicitation?
To gather and document system requirements
What type of changes can lead to requirements changes?
Business, organizational, and technical changes
Study Notes
Non-Functional Requirements
- Non-functional requirements constrain the system being developed and the development process.
- They relate to the emergent properties of the system and apply to the system as a whole.
Requirements Engineering
- Requirements engineering involves three key activities:
- Elicitation and analysis
- Specification
- Validation
- Requirements engineering is the process of determining, documenting, and maintaining the requirements.
Software Requirements Document
- The software requirements document (SRS) is an agreed statement of the system requirements.
- It should be organized so that both system customers and software developers can use it.
- The document may include:
- Product and process standards
- System architecture
- Functional and non-functional requirements
- System models
- System evolution
- Appendices
Agile Methods and Requirements
- Many agile methods argue that producing a requirements document is a waste of time as requirements change quickly.
- Agile methods use incremental requirements engineering and express requirements as user stories.
Requirements Elicitation and Analysis
- Requirements elicitation and analysis involves working with system stakeholders to find out about:
- Application domain
- System services
- System performance
- Hardware constraints
- Other systems
- Stages include:
- Requirements discovery
- Requirements classification and organization
- Requirements prioritization and negotiation
- Requirements specification
Requirements Validation Techniques
- Requirements validation is the process of checking the requirements for:
- Validity
- Consistency
- Completeness
- Realism
- Verifiability
- Techniques include:
- Reviews
- Prototyping
- Modeling
Requirements Management
- Requirements management is the process of managing and controlling changes to the requirements.
- It involves:
- Change analysis and costing
- Change implementation
- Change tracking and reporting
Changing Requirements
- The business and technical environment of the system always changes after installation.
- Changes can include:
- New hardware
- Interface with other systems
- Business priorities
- Legislation and regulations
- Requirements change management involves:
- Assessing the impact of the proposed change
- Deciding whether to proceed with the requirements change
- Modifying the requirements document and system design and implementation
This quiz covers the basics of requirements engineering, including non-functional requirements and emergent properties of systems.
Make Your Own Quizzes and Flashcards
Convert your notes into interactive study material.
Get started for free
