Karteikarten
SCC 204 - Requirements Engineering
Karten in diesem Stapel (9)
- 1What is a requirement?a description of what the system under development (SUD) should do and any constraints under which it must do it
- 2What does a requirement serves as between the development team and the customer?It serves as a contract between the development team and
the customer - 3What does requirements focus on in terms of system completion of tasks?It focuses on what the system will do, not how it will do it
- 4What level should requirements be written at?Should be written at a level that the customer understands
- 5List the software life cycle?Requirements
Analysis
Architecture/ Design
Code and Unit testing
Subsystem testing
System testing - 6What should requirements document include?a general description of the context and domain
the scope of the product
a set of SHALL statements prescribing what the system will do
both functional and non-functional - 7What considerations should be taking into account when writing requirements?use simple precise text
don’t make assumptions about the reader’s knowledge
involve as many stakeholders as possible
be aware that English is an ambiguous language - 8Describe non functional requirements in software user documentation?Constraints on how the SUD should behave
- 9Typical examples of constraints in software user documentation? availability
performance
security
usability and accessibility
reliability
NFRs are SHALL statements that precisely specify these constraints
Informationen
- Beschreibung
- Karteikarten am SCC 204 - Requirements Engineering , erstellt von Ayo Olutobi am 27/03/2017.
- Erstellt von
- Ayo Olutobi
- Aufrufe
- 1
- Bewertung