Please enable JavaScript.
Coggle requires JavaScript to display documents.
Requirements Engineering (2.2.3 Requirement Elicitation and Analysis…
Requirements Engineering
-
-
2.2.1 Natural language specification and
Structured specification
Natural Language
The requirement are written using numbered sentences in natural language. Each sentence should express one requirement.
Structured Specification
The requirement are written in natural language on a standard form or template. Each field provides information about an expect of the requirement.
2.2.4 Recognize the importance of requirements validation
- Concerned with demonstrating that the requirements define the system that the customer really wants.
- Requirements error costs are high so validation is very important
Requirements Checking
- Validity
- Consistency
- Completeness
- Realism
- Verifiability
Requirements Validation Techniques
- Requirements reviews
(Systematic manual analysis of the requirement)
- Prototyping
( Using an executed table model of the system to check requirements)
- Test-case generation
(Developing tests for requirements to check testability)
Requirements reviews
- Regular reviews should be held while the requirements definition is being formulated
- Both client and contractor staff should be involved in reviews
Review checks
- Verifiability
- Comprehensibility
- Traceability
- Adabtibility
-
-
2.3.1 Develop full documentation of software requirement
- A software requirement specification is a document or set of documentation that outlines the futures and intended behavior of a software application
- in other words, the software requirement document describes the business or organization's understanding of the end user needs and dependencies as well as any constraints on the system.
The Structure of a requirements document
- Preface
- Introduction
- Glossary
- User requirements definition
- System architecture
- System requirements specification
- System models
- System evolution
- Appendices
- Index
Key Points
i. Requirements for a software system set out what the system should do and define constraints.
ii. Functional requirements are statement of the services that the system must provides or a description of how some computations must be carry out.
iii. Non-functional requirements often constraints the system being developed and the development process being used.
iv. The software requirements document is an agreed statement of the system requirements.
v. The requirements engineering process is an iteractive process including requirements elicitation, specification and validation.
vi. Requirements elicitation is an iteractive process that can be represented as a spiral of activities requirement discovery requirements classification and organization.
vii. Techniques of requirements elicitation including interviews, scenarios and ethnography.