/
Requirements Engineering Overview
Save to my account
Sign up
Requirements Engineering Overview
Requirements Engineering Overview
Study
1
Question
What is the definition of Requirements Engineering?
Answer
Requirements engineering is the process of establishing the services that a customer requires from a system and the constraints under which it operates and is developed.
2
Question
What do system requirements describe?
Answer
System requirements describe the system services and constraints generated during the requirements engineering process.
3
Question
What are Functional Requirements?
Answer
Functional Requirements are statements of services the system should provide, how it should react to particular inputs, and how it should behave in specific situations. They may also specify what the system should not do.
4
Question
What are Non-Functional Requirements?
Answer
Non-Functional Requirements are constraints on the services or functions offered by the system, such as timing constraints and standards. They often apply to the system as a whole rather than individual features.
5
Question
How are User Requirements expressed?
Answer
User requirements are expressed in natural language and diagrams for customers.
6
Question
What are System Requirements?
Answer
System requirements are structured documents detailing the system's functions, services, and operational constraints.
7
Question
Who are considered stakeholders in Requirements Engineering?
Answer
Any person or organization affected by the system and having a legitimate interest is considered a stakeholder.
8
Question
What are the types of stakeholders mentioned?
Answer
End users, system managers, system owners, and external stakeholders.
9
Question
Who are the stakeholders in the Mentcare System?
Answer
Patients, doctors, nurses, medical receptionists, IT staff, medical ethics managers, healthcare managers, and medical records staff.
10
Question
What is the Agile Approach to Requirements?
Answer
Many agile methods argue against producing detailed system requirements due to rapid changes. Requirements are expressed as 'user stories' and involve incremental requirements engineering.
11
Question
Why is abstraction important in requirements definition?
Answer
Requirements must be defined abstractly for contractors to propose solutions without pre-defining them. Detailed system definitions are created post-contract award for client understanding and validation.
12
Question
What is Requirements Elicitation?
Answer
Requirements elicitation involves technical staff working with customers to discover application domain needs, services, and operational constraints.
13
Question
Who are the stakeholders in Requirements Elicitation?
Answer
Stakeholders include end-users, managers, engineers, and domain experts.
14
Question
What are some techniques used in Requirements Elicitation?
Answer
Interviews (closed and open), ethnography, scenarios, and user stories.
15
Question
What are some challenges in Requirements Elicitation?
Answer
Stakeholders may not know what they want or express requirements in their own terms. Conflicting requirements may arise from different stakeholders.
16
Question
What is Requirements Specification?
Answer
Requirements Specification is the process of documenting user and system requirements in a requirements document.
17
Question
How should user requirements be written?
Answer
User requirements must be understandable to non-technical stakeholders, while system requirements can include technical details.
18
Question
What are the guidelines for writing requirements?
Answer
Guidelines include consistency, clarity, and avoiding jargon.
19
Question
What is the purpose of Requirements Validation?
Answer
The purpose of Validation is to ensure that requirements define the system the customer truly wants.
20
Question
What are some techniques used in Requirements Validation?
Answer
Requirements reviews, prototyping, and test-case generation.
21
Question
What necessitates changes in system requirements?
Answer
Business and technical environments evolve, necessitating changes in system requirements.
22
Question
What does Change Management involve?
Answer
Change Management involves problem analysis, change specification, change analysis, costing, and implementation.
23
Question
What is Requirements Management?
Answer
Requirements Management is the process of managing changing requirements during development.
24
Question
What is included in a Management Plan for Requirements?
Answer
The Management Plan establishes requirements identification, change management processes, traceability policies, and tool support.
25
Question
What are the key points in Requirements Engineering?
Answer
Requirements define what a system should do and constraints on its operation. The requirements engineering process is iterative, including elicitation, specification, and validation. Requirements management is crucial for adapting to changes in business and technical environments.