The phases spelt out are Obvious.
It would help if we looked at the steps involved in the Preparation & Planning phase, the Document creation phase and in the Modification phase.
Preparation & Planning phase: 0) Deciding the audience and the characteristics of the audience 1) Studying the problem - Field study, related document collection, categorisation and Problem de-composition. Looking at these toopics from the perspective of the sudience. 2) Deciding the presentation format.
Document creation phase: Deciding the contents, the headings, the sub-headings and the Introduction.
Formulating a flow. Validating the stated hypotheses. Inferring conclusions. Summing up
Modification phase: Maintaining links between concepts and activities, so that a modification has its required ramifications.
One of the issues I've encountered is system life cycle consideration. Too many times documents only exist and are managed as a part of a project life cycle. Many of these controlled documents should be managed for the life of the system so planning must include maintenance and control of these past the projects end date. This becomes critical for global projects that may have a three or four year deployment life and a ten year sustain requirement.
First, the preparation phase should establish what 'gen' of the document this is, such as Gen I, II. Organizations often loose track of the generations of a Requirements document. Secondly, perhaps there should be an 'Archive' phase, in which the document is retired and no longer accessible or replaced by a later 'Gen', or just no longer relevant.
- Keyboard Shortcuts: