You are on page 1of 3

Chapter 1

Three goals address important facets of RE :


1- Process orientation
2- Stakeholders focus
3- Importance of risk and value consideration

Requirements engineering can avoid typical problems :


1- Non-consideration of stakeholders
2- Unclear or missing requirements
3- Insufficient documentation and ( change ) management of requirements
4- Insufficient negotiation
5- Missing distinction of requirements and design decisions
6- Insufficient relationship with testing activities

The role of communication :


1- Language is the most important means for communication in RE
2- Common glossary is essential
3- Similar backgrounds facilitate communication
4- Media must fit the project context
5- Filtering and transformation of information affect effective communication
6- Requirements engineer is mediator between the worlds

Done by Mariah Brashi


Characteristics of a good requirements engineer :
1- Analytic thinking
2- Empathy
3- Communication skills
4- Conflict resolution skills
5- Moderation skills
6- Self-confidence
7- Persuasiveness
8- Domain knowledge
9- Technical knowledge ( include SE knowledge )

Requirements types :
1- Functional Requirements
A requirement concerning a result of behavior that shall be provided by a function
of a system ( or a component or service )
2- Quality Requirements
A requirement that pertains to a quality concern that is not covered by functional
requirements
3- Constraints
A requirement that limits the solution space beyond what is necessary for meeting
the given functional requirements and quality requirements.
4- Non-functional requirements
Quality requirement + constraints
*Note : some publication consider non-functional requirements as quality requirements only

Done by Mariah Brashi


The importance of quality requirements:
1- Quality requirements are essential for product / project success
2- Quality requirements enable
- well-founded design decisions
- subcontracting
- early quality assurance
- differentiation at the market
3- Neglecting quality requirements can cause
- low product quality
- costly rework
- delivery problems
- loss of reputation

Example types of quality requirements:


1- Security and Accuracy
2- Reliability
3- Useability
4- Efficiency
5- Modifiability
6- Portability

Development Approaches :
1- ( Rational ) Unified Process
2- Scrum
3- XP

Done by Mariah Brashi

You might also like