 |
Atom-Based Software Engineering |
ABSE Improves Requirements TraceabilityOne of the most common causes of runaway projects are unstable (ever changing?) requirements. When a project moves from the requirements phase to the design phase, the solution process's complexity will cause an explosion of derived requirements. This list of derived requirements for the design phase often becomes 50 times longer than the list of original requirements. This requirements explosion is partly why it is difficult to implement requirements traceability (tracing the original requirements through the application lifecycle), even if everyone agrees this is always useful and desirable. Software requirements are granular in its nature: they can become very small parts of the project's whole, but group at least some lines of code. ABSE is appropriate for requirements traceability because it is also granular in its nature: ABSE groups together code and/or features at varying abstraction levels. You can create Atoms that reflect the project's own requirements, making them easy to change, track, analyze or report.
|
|
Quick Tour |
Twitter |
| (c) 2006-2010 Isomeris | Send questions to r.curado [at] isomeris.com |
 |