- Requirements. Encompasses definition,
statement of objectives, preliminary analysis, functional
specifications, design constraints.
- Design. Includes outline
definition, format definition, etc.
- Implementation. Entails writing,
editing, integration of various components, and
- Testing. Includes verification
and evaluation against the requirements.
and Maintenance. Begins upon delivery and user
maintenance process can be divided into the following
Determination of need for change
Submission of change request
Review of proposed changes
Approval/rejection of change request
Scheduling of task(s)
Design analysis and review
Writing and editing
process of changing documentation is frequently
complex and may involve many people. The steps
above outline the maintenance process which begins when the
need for change arises and ends after the user accepts the
Although the maintenance process above is
presented as linear, there are many steps and iterative
loops. For example, the change
request may need clarification; the design
reviews may require more analysis; the
standards audit may require design changes
and rewriting; the users may fail to accept the results;
Maintainer must make changes within the context of the
existing documentation, often the most challenging
problem for maintenance people. The older the documentation,
the more challenging and time consuming the maintenance
maintenance effort is typically performed in less
time than a development effort.
development effort may span several
- corrective maintenance may be required
within hours and ...
- perfective maintenance is typically
performed in cycles of 1-6 months.