Software Engineering - Requirements Engineering

thomaswesterman
Mind Map by thomaswesterman, updated more than 1 year ago
thomaswesterman
Created by thomaswesterman almost 6 years ago
34
1

Description

Requirements Engineering

Resource summary

Software Engineering - Requirements Engineering
1 Definition of Requirements
1.1 Descriptons of service and constraints of a system
1.1.1 ranges from high level to detaiiled
2 Definition of requirements engineering (services and constraints)
2.1 identifyinng
2.2 analysing
2.3 documenting
2.4 checking
3 where do requirements come from
3.1 customers stated needs
3.2 other stakeholders needs
3.3 implied needs
3.4 application domain
3.5 legal or other regulations
3.6 The client is not king
3.6.1 must identify real needs
3.6.2 duty to society- legal
4 User Requirements
4.1 statements in natural language
4.2 diagrams of services provided
4.2.1 operational restraints
4.3 Readers
4.3.1 client managers
4.3.2 system end users
4.3.3 client engineers
4.3.4 contractor managers
4.3.5 system architects
5 System Requirements
5.1 structured document
5.1.1 detailed descriptions
5.1.1.1 functions
5.1.1.2 services
5.1.1.3 operational constraints
5.2 part of contract between client and contractor
5.3 readers
5.3.1 system end users
5.3.2 client engineers
5.3.3 system architects
5.3.4 software developers
6 Functional , non Functional and domain Requirements
6.1 Functional requirements
6.1.1 statements of services provided
6.1.2 how system reacts to inputs
6.1.3 system behaviour in certain situations
6.2 non functional requirements
6.2.1 system as a whole
6.2.1.1 constraints
6.2.1.1.1 timing
6.2.1.1.2 development process
6.2.1.1.3 standards
6.3 Domain requirements
6.3.1 regulation
6.3.2 legislation
6.3.3 legal
6.4
7 Realism,Testability, traceabiility
7.1 Realistic requirements
7.1.1 budget and time
7.2 Testable Requirements
7.2.1 contains testable descriptions
7.3 untestable requirments
7.3.1 language to abstract
7.4 Traceability
7.4.1 record rationale for requirement
7.4.1.1 source
Show full summary Hide full summary

Similar

Design Patterns
Erica Solum
Network Protocols
Shannon Anderson-Rush
System Analysis
R A
SCRUM
R A
JOOSE2 Design Patterns
Isaac Jordan
Patents
Christina
Pears of Wisdom - Software Engineering Overview
Alex Poiry
2 Introduction
Alex C
Example Use Case: Emergency Management System
Stephanie Jeandell
Requerimientos
Romina V.
DEPENDABLE SYSTEMS
A J