Information Technology Reference
In-Depth Information
6. Data analysis of completed projects can reveal some anomalies which could
result in changing the requirements.
Ancillary functionality requirements also can change for the following reasons:
1. During design phase or construction phase, it may be uncovered that imple-
mentation of some requirements as frozen may not be possible due either to
technical reasons or cost considerations. This may necessitate a change of
requirements.
2. Some of the system software may release patches or service packs affecting the
software design causing the requirements to change.
3. A new threat or a security hole may be discovered in the system software
necessitating a revision of the requirements.
4. Someone may uncover a better way to achieve the functionality causing the
requirements to change.
Whatever the reason may be and whatever the requirement may be, some
changes become necessary during the project execution after the requirements are
frozen. Therefore, we need to equip ourselves with the means to handle changes in
an orderly manner ensuring that the smooth work flow continues without major
interruption. Normally this is covered in the SCMP and forms part of configuration
management of the project.
8.2 Communication of Changes
How are changes communicated to the project team? Changes can be communi-
cated to the project team either by telephonic information, in person, through an
email, through a software tool or more formal methods. Agile methods mandate
colocation of the customer with the project team and hence see no need for formal
or written methods for communicating change. In the agile projects the commu-
nication would be in person. In other projects, all the above methods would be
used. It is possible to communicate changes without written documents but, formal
methods have advantages. They are:
1. Formal methods help in keeping a record of the changes requested for analysis
later at the end of the project.
2. Formal methods facilitate tracking each change to its resolution and that no
requested change is forgotten.
3. Formal methods ensure that all required information is communicated along
with the requested change.
4. Formal methods enable analysis of changes and effect improvements in the
process to minimize changes as well as to improve the process of defining
project requirements more comprehensively.
 
Search WWH ::




Custom Search