15 Questions
What is the process of establishing the services that the customer requires from a system and the constraints under which it operates and is developed?
Requirements engineering
What are the descriptions of the system services and opreational constraints that are generated during the requirements engineering process?
Functional specifications
Which type of requirement includes statements in natural language plus diagrams of the services the system provides and its operational constraints, written for customers?
User requirements
Which type of requirement is a structured document setting out detailed descriptions of the system’s functions, services, and operational constraints, defining what should be implemented as part of a contract between client and contractor?
System requirements
Who is one of the readers of user requirements according to the text?
Client managers
Who is one of the readers of system requirements according to the text?
System architects
What do non-functional requirements define?
Constraints on the services or functions offered by the system
What are domain requirements?
Constraints on the system from the domain of operation
What is a common problem when requirements are not precisely stated?
Conflicts in requirements
What do functional user requirements describe?
High-level statements of what the system should do
Which type of requirement may be more critical than functional requirements?
Non-functional requirements
What is a constraint defined by non-functional requirements?
Reliability and response time
What do functional requirements describe?
Functionality or system services
What should requirements document be in principle?
Complete and consistent
What are process requirements?
Non-functional requirements
Study Notes
Requirements Engineering Process
- Establishes the services customers require from a system and operational constraints
- Generates descriptions of system services and operational constraints
Types of Requirements
- User Requirements: statements in natural language plus diagrams, written for customers
- System Requirements: structured document with detailed descriptions of system functions, services, and operational constraints, defines what should be implemented in a contract between client and contractor
Readers of Requirements
- User Requirements: customers
- System Requirements: contractors, developers, and testers
Non-Functional Requirements
- Define constraints on system operation and development
- Include constraints such as timing, security, and usability
Domain Requirements
- Constraints based on the application domain
Importance of Precise Requirements
- Imprecise requirements can lead to misunderstandings and errors
Functional Requirements
- Describe the system's functional capabilities
- Describe what the system must do
Non-Functional Requirements
- May be more critical than functional requirements in certain cases
- Define constraints such as performance, safety, and reliability
Characteristics of Requirements Document
- Should be unambiguous, complete, and consistent
- Should be feasible to implement and verify
Test your knowledge of the process of establishing system services and constraints, as well as the generation of system descriptions during the requirements engineering process.
Make Your Own Quizzes and Flashcards
Convert your notes into interactive study material.
Get started for free
