16 Questions
What is the primary focus of a requirement, according to requirements engineering?
Customer needs
What type of requirement describes the functionality or system service and is written in natural language?
Functional Requirement
Who are the stakeholders in a system, according to requirements engineering?
Any person or organization who is affected by the system in some way and has a legitimate interest
What type of requirement constrains the services or functions offered by the system?
Non-Functional Requirement
What is the primary difference between user requirements and system requirements?
User requirements are statements in natural language, while system requirements are structured documents with detailed descriptions of the system’s functions and services.
What type of requirement constrains the system from the domain of operation?
Domain Requirement
What type of non-functional requirement specifies or constrains the runtime behavior of the software?
Product Requirement
Why are non-functional requirements often more critical than functional requirements?
Because they may apply to the system as a whole rather than individual features or services.
What are the different types of requirements that are typically considered in the requirements engineering process?
Functional, non-functional, organizational, and external requirements.
What is the main goal of requirements elicitation?
To understand the work that stakeholders do and how they might use a new system to support that work.
What are some common problems that can arise during the requirements elicitation process?
Unrealistic demands, expressing requirements in terms that are not understood by Requirements Engineers, and conflicting requirements from different stakeholders.
What is the purpose of requirements analysis?
To identify and prioritize the requirements gathered during elicitation.
What is requirements validation, and what is its purpose?
The process of checking that the requirements accurately capture the stakeholder's needs, and its purpose is to ensure that the developed system meets the stakeholders' needs.
Why are non-functional requirements important in the requirements engineering process?
They specify the constraints on the system's behavior, such as execution speed, reliability, security, and usability.
What is the role of organizational requirements in the requirements engineering process?
They are a consequence of organizational policies and procedures, and define how the system will be used.
What is the main characteristic of the requirements engineering process?
It is an iterative and interleaved process of elicitation, analysis, validation, and management.
Study Notes
Requirements Engineering
- Focus on customer needs, not on the solution or implementation
- Establishes the services that a customer requires from a system and the constraints under which it operates and is developed
Types of Requirements
- User Requirements:
- Statements in natural language
- Diagrams of the services the system provides
- Operational constraints
- Written for customers
- System Requirements:
- A structured document
- Detailed descriptions of the system’s functions, services, and operational constraints
- Defines what should be implemented, may be part of a contract between client and contractor
System Stakeholders
- Any person or organization affected by the system in some way
- Stakeholder types:
- End users
- System managers
- System owners
- External stakeholders
Functional and Non-Functional Requirements
- Functional Requirements:
- Describe functionality or system service
- Written in natural language
- Expand user requirements and are written as system requirements
- Describe system functions, inputs, outputs, and exceptions in detail
- Non-Functional Requirements:
- Constraints on the services or functions offered by the system
- Timing constraints, development process, standards, etc.
- Often apply to the system as a whole rather than individual features or services
- May be more critical than functional requirements
Types of Non-Functional Requirements
- Product Requirements:
- Specify or constrain the runtime behavior of the software
- Specify that the delivered product must behave in a particular way (e.g., execution speed, reliability, security, and usability)
- Organizational Requirements:
- Consequence of organizational policies and procedures
- Define operational process requirements and development process requirements
- External Requirements:
- Arise from factors external to the system and its development process
- Examples: regulatory requirements, legislative requirements, ethical requirements
Requirements Engineering Processes
- Processes vary widely depending on the application domain, people involved, and organization
- Generic activities common to all processes:
- Requirements elicitation
- Requirements analysis
- Requirements validation
- Requirements management
- An iterative activity in which these processes are interleaved
Requirements Elicitation
- Understand the work that stakeholders do and how they might use a new system to support that work
- Activities:
- Requirements discovery
- Requirements classification and organization
- Requirements negotiation
- Requirements documentation
Quiz about the process of establishing customer requirements from a system, including user requirements and constraints. Focus on customer needs and behavior. Learn about the types of requirements and operational constraints.
Make Your Own Quizzes and Flashcards
Convert your notes into interactive study material.
Get started for free
