Document-Weary? Try Chief Programmer Work Folders
Like this article? We recommend
Like this article? We recommend
Like this article? We recommend
Introduction
Over the last couple of years, many software development teams have started using Internet technologies to build project repositories. Imagine the possibilities of combining products like Together ControlCenter, tools like Javadoc, web-enabled version control systems, calendars, discussion areas, databases, and directory servers. This powerful combination provides a development team plenty of opportunities to capture, generate, and link documents and other artifacts created throughout a project. The question that the technology doesn't answer is exactly what documents to create and capture, and how best to link it all together. Therefore, this article provides a short set of notes exploring the recording of artifacts produced during the two engine-room processes of Feature-Driven Development (FDD), called Design by Feature (DBF) and Build by Feature (BBF).
The Design by Feature and Build by Feature activities form the construction engine room of the Feature-Driven Development process. Each of the two activities includes a number of tasks to be performed by the chief programmer or the feature team as a whole.
The Design by Feature activity contains seven tasks:
Form a feature team.
Domain walkthrough.
Study the referenced documents.
Build a sequence diagram.
Write class and method prologs.
Design inspection.
Log design-inspection action items.
The Build by Feature activity contains six tasks:
Implement classes and methods.
Code inspection.
Log code-inspection action items.
Unit test.
Develop a team model.
Check in and promote to the build process.