Please enable JavaScript.
Coggle requires JavaScript to display documents.
C27-C28-C29-C30 (CHAPTER 27 Requirements management practices (Managing…
C27-C28-C29-C30
CHAPTER 27
Requirements management practices
version control
change control
activities
requirements status tracking
requirements tracing
Managing requirements on agile projects
Completed (the story is fully implemented)
Accepted (acceptance tests were passed)
In progress (the story is being implemented)
Defned (details of the story were discussed and understood, and acceptance tests were written)
In backlog (the story is not yet allocated to an iteration)
Blocked (the developer is unable to proceed until something else is resolved)
CHAPTER 29
Links in the requirements chain
Customer needs are traced forward to requirements, so you can tell which requirements will be affected if those needs change during or after development
forward from requirements by defning links between individual functional and nonfunctional requirements and specifc system elements
CHAPTER 30
Tools for requirements engineering
document-based
limitations
CHAPTER 28
Change happens
The change control board
CCB composition