SE 4 Flashcards
Requirement Engineering Process
process of identifying, eliciting,
analyzing, specifying, validating, and
managing the needs and expectations of
stakeholders for a software system.
Steps in Requirement Engineering Process
➢ Feasibility Study
➢ Requirement Elicitation
➢ Requirement Analysis
➢ Software Requirement Specification
➢ Software Requirement Validation
➢ Software Requirement Management
A feasibility study is ;
A short, focused study that aims to check the
feasibility of the project considering resources,
cost/benefit, technology availability, etc..
Requirement Elicitation
process of gathering information about the needs and
expectations of stakeholders for the software system.
Techniques used to gather information
➢ Interviews
➢ Surveys
➢ Focus groups
➢ Document sampling
Requirement Analysis
- Analyzing the information gathered
*identify the high-level goals and objectives
*identifying any constraints or limitations that may
affect the development of the software system
Requirement Specification
detailed and specific description of the system
requirements
a basis for a contract
between client and software developer
Involves prioritizing and grouping the requirements
Requirement Validation
- Checking that the requirements are complete,
consistent, and accurate.
*check the correctness of the
specification of requirements
- meet the needs and expectations of stakeholders
Requirement Management
process of managing changing requirements during
the requirements engineering process
Includes
➢ Tracking and controlling changes
➢ Ensuring that the requirements are still valid and
relevant.
Requirement documents
User requirements (Requirements definition)
System requirements
Software Requirements Specification (SRS)
Functional Requirements
statements of services the system should provide, how the
system should react to particular inputs and how the system should
behave in particular situations.
Non-functional Requirements
constraints on the services or functions offered by the
system.
Functional Requirements
statements of services the system should provide, how the
system should react to particular inputs and how the system should
behave in particular situations.
Non-functional Requirements
constraints on the services or functions offered by the
system.
Domain Requirements
requirements that come from the system’s application
domain and reflect the domain’s characteristics
System Analyst
- IT professional who specializes in analyzing,
designing, and implementing information systems.
Examines the organization’s current systems (manual
or computerized) and procedures
working closely with the
client.
SKILLS
*Strong analysis skills
* Technical and business knowledge and skills
* Critical Thinking