Requirements

Engineering

Marco Toranzo
Mayo - 2020
 Objetivos

 Discutir las etapas para el identificación,

especificación y validación de requisitos.
 Agenda

 Modelo de proceso
 Proceso de Ingeniería de requisitos
 Trabajo en equipo
Modelo de proceso

 The systems engineering process

System System
requirements validation
engineering

Architectural System
design integration

Requirements Sub-system
partitioning development

Software
requirements
engineering
RE process - inputs and
outputs
Existing
systems
information

Stakeholder Agreed
needs requirements

Requirements System
Organisational engineering process
standards specification

System
Regulations models

Domain
information
Context of the RE
process
System acquisition

Requirements engineering

System design
The variability of RE
processes
RE processes vary radically from one organisation
to another. Why?
 Factors contributing to this variability include
 Technical maturity
 Disciplinary involvement
 Organisational culture
 Application domain
 There is therefore no ‘ideal’ requirements
engineering process.
RE process activities
 RE process activities
 Requirements elicitation
 Requirements analysis and
negotiation
 Requirements documentation
 Requirements validation
 Requirements management
Requirements Elicitation and
Analysis
Dr. Marco Toranzo
Dimensions to requirements
elicitation

Application Problem to
Domain be solved
understading

Stakeholder Business
needs and context
constraints
 Human and social factors

https://assetinsights.net/Glossary/G_Stakeholders.html
Elicitation, analysis and
negotiation Draft
statement of
requirements
Requirements
elicitation Requirements
analysis

Requirements
Requirements problems
document
Requirements
negotiation
Human and social factors
The requirements
elicitation process
A good requirements elicitation process should include four

critical activities:
1 2 3 4
Establish objectives Understand background Organise knowledge Collect requirements

Business Organisational Stakeholder Stakeholder

goals structure identification requirements

Goal Domain
Problem to be Application prioritisation requirements
solved domain

Domain Organisational
System Existing knowledge
constraints systems requirements
filtering
Proceso de Ingeniería de
requisitos Decision point:
Accept document
Informal statement of
requirements

or re-enter spiral

Requirements elicitation Requirements analysis and

negotiation

Requirements START
document and Agreed
validation requirements
report

Requirements validation Requirements documentation

Draft requirements
document

Requirements management
Human and social factors
• Factors influencing requirements
• Stakeholders will not necessarily give
priority to the requierements
engineering;
• Personality and status of stakeholders;
• The personal goals of individuals
within an organisation; and
• The degree of political influence of
stakeholders within an organisation;
Elicitation, analysis and
negotiation
 Requirements elicitation and requirements analysis are
closely linked processes.
 Requirements engineers and stakeholders negociate to
agree on the definition of the requirements to be
included in the requirements documents.
Proceso de Ingeniería de
requisitos Decision point:
Accept document
Informal statement of
requirements

or re-enter spiral

Requirements elicitation Requirements analysis and

negotiation

Requirements START
document and Agreed
validation requirements
report

Requirements validation Requirements documentation

Draft requirements
document

Requirements management
Validation inputs and
Certifies that the requirements document is an acceptable
description of the system to be implemented
outputs
Requirements
document List of problems

Organisational Requirements
knowledge validation Agreed actions

Organisational
standards
Validation objectives

 Validation works with a final draft of the requirements

document i.e. with negotiated and agreed requirements
 Certifies that the requirements document is an
acceptable description of the system to be implemented
 Checks a requirements document for
 Completeness and consistency
 Conformance to standards
 Requirements conflicts
 Technical errors
 Ambiguous requirements
Review
checklists
 Understandability
 Redundancy
 Completeness
 Ambiguity
 Consistency
 Organisation
 Conformance to standards
 Traceability
 Informal statement of
Decision point: requirements
Accept document

conclusions or re-enter spiral

Requirements elicitation Requirements analysis and

negotiation

Requirements START
document and Agreed
validation requirements
report

Requirements validation Requirements documentation

Draft requirements
document

Requirements management