The Value of Executable Artifacts |
 |
| Sunday, 08 April 2007 11:11 |
|
We have been taught that the best way to solve the tough challenges inherent in software development efforts is to treat software development as an engineering discipline. Stabilize requirements early, and then follow by analysis and design, implementation, verification, and deployment. Throughout each of these lifecycle phases, teams produce traceable artifacts where changes to one artifact is ideally traced through to other artifacts, eventually leading to the source code modules that must...
We have been taught that the best way to solve the tough challenges inherent in software development efforts is to treat software development as an engineering discipline. Stabilize requirements early, and then follow by analysis and design, implementation, verification, and deployment. Throughout each of these lifecycle phases, teams produce traceable artifacts where changes to one artifact is ideally traced through to other artifacts, eventually leading to the source code modules that must change. But traceability is fundamentally flawed due to the manual effort required to synchronize artifacts. As deadlines loom and pressure mounts, we do not possess the discipline to ensure consistency across all artifacts. Slowly, requirements specifications and design models diverge and no longer offer an accurate view of current system behavior or structure. Avoiding the issues inherent to traceability demands we shift from traceable artifacts to executable artifacts.
Read more >>
Set as favorite
Bookmark
Email this
Hits: 1447 Trackback(0)Comments (0)
|
TrackBack URI for this entry
Subscribe to this comment's feed