Please enable JavaScript.
Coggle requires JavaScript to display documents.
Requirements Engineering (roles (Business analysts, Domain experts,…
Requirements Engineering
definition of requirements engineering
framework
analysis
Types of Requirement
Functional requirements
Non-functional requirements
Technical requirements
General requirements
Business requirements
Stakeholder requirements
Solution requirements
Transition requirements
REQUIREMENTS ANALYSIS
Characteristics of Good Requirements
Categorised
Relevant
Prioritised
Achievable
Requirement not solution
Testable
Consistent
Understandable and unambiguous
Owned
Concise
Unique and atomic
Complete
Traceable
Correct
Conformant
Prioritisation of Requirements
Could have
Want to have (but not now)
Should have
Must have
validation
Verification
Validation
management
Change control
Traceability
Configuration management (version control)
documentation
Requirements catalogue
Business area/domain
Source
Version/status
Owner
Title
Stakeholders
ID
Requirement type
Acceptance or fit criteria
Description
Rationale/justification
Priority
Related documents
Associated non-functional requirements
Related requirements
User Stories
Resolution
elicitation
Primarily Qualitative Elicitation Techniques
Interviews
Workshops
Focus groups
observation
Scenarios
Shadowing
Prototyping
Primarily Quantitative Elicitation Techniques
Questionnaires and surveys
Special-purpose records
Record searching
Document analysis
Activity sampling
requirements engineering framework
roles
Business analysts
Domain experts
Testers
Managers
Developers
Users (process workers)
Project sponsor
requirements engineering and Agile development
requirements engineering and off-the-shelf solutions