Following the topic around Projects Aspect, my interest in FDD extensions and adaptations has grown. I've been doing it for a couple years, but in the last few weeks I've been looking for a more normalized approach to the issue that encompasses needs beyond the traditional PD, DM, UI and SI aspects (for instance to include Documentation).
Probably people have tried to do this before hence raising this issue on this forum. To jump start let me introduce what I've been thinking, so invite you to clarify and challenge these ideas so we can come to a conclusion that is satisfactory.
The problem that I have with FDD is that the method for tracking artifacts in use is "limited" the development phase (DBF/BBF iteration) has the process is defined. In other words, just because all features are marked 100% may not mean that the project is finished and the "product" is delivered. This because features are taken and defined over an overall domain model designed (Object Model) on the 1st phase, and the description of this (ETVX Template) phase does not take into account issues such as UI, Documentation, Installation etc, just to name a few things. Only the concepts that need to be developed in the PD layer are taken into account. Although we can argue that these are not issues from developer's point of view or that this layer is the most important (etc, etc) and I tend to agree, it means that FDD does not cover the SDL as whole. So this "tool" may not be adequate at first to some projects from the start. In spite of this, the underling concepts of the tracking strategy have the potential to be used not only to track de development of features but also other "things".