Chapter 11 - Documenting and Managing Requirements Flashcards
What are three reasons for keeping good requirement documentation?
Communication
Validation
Further testing
What sections are included in a Requirements document?
Intro and Background
Business process models
Function models
Data model
Requirements catalogue
Glossary
What are the four types of requirement in a Requirements Catalogue?
General
Technical
Functional
Non-functional
What categories would fall into General in a Requirements Catalogue?
Business constraints
Business policies
Legal
Branding
Cultural
Language
What categories would fall under Technical in a Requirements Catalogue?
Hardware
Software
Interoperability
Internet
What categories would fall under Functional in a Requirements Catalogue?
Data entry
Data maintenance
Procedural
Retrieval
What type of categories would fall under Non-Functional in a Requirements Catalogue?
Performance
Security
Access
Backup and Recovery
Archiving and retention
Maintainability
Business Continuity
Availability
Usability
Accessibility
Capacity
What needs to be documented for a requirement?
Requirement Identifier
Requirement Name
Requirement Description
(User verb object)
Source
Owner
Author
Type of requirement
Priority
Business Area
Stakeholders
Associated non-functional requirements
Acceptance Criteria
Related requirements
Related documents
Comments
Rationale
Resolution
Version History
What is “Backwards from” traceability?
Origins of the requirement.
What is “Forwards to” traceability?
What happened to the requirement
What is vertical traceability?
Alignment with business values, strategy and objectives.
What are the six components of Requirements Management?
Requirements identification
Requirements cross-referencing
Requirements origin and ownership
Software support
Change control
Configuration management
What is Requirements identification?
Each requirement needs to be identified uniquely
What is Requirements cross-referencing?
Related requirements and documents should be cross-referenced to allow analyst to identify whether changing a requirement will impact other requirements.
What is Requirements origin and ownership?
Origin of the requirement.
The owner will need to make decisions about the requirement.
What is Configuration Management?
Controlling changes made to project deliverables such as documents.
What sort of problems can occur without effective Configuration Management?
Difficulty in identifying latest version
Re-introduction of out of date requirements
Using wrong set of requirements for testing
What is Configuration identification concerned with?
Defining which deliverables will be brought under configuration control
Identifier and version numbering scheme to be applied.
What is Configuration control?
The version control process
What possibilities are the for baselining during Agile development?
Baselining every prototype before demonstration
Baselining daily
Baselining at the end of a timebox
What are the stages for Change Control?
Documenting the proposed change
Consulting the stakeholders
Deciding on the change
What features can software support give to Requirements Management?
Documentation creation and storage
Secure storage and access
Documents linkage
Version numbering