Software Re-engineering and Maintenance
Process
|
Document
and Code comprehension |
Existing
design documents supplied by the customer will be understood in
relation with the existing source code. In case of NON AVAILABILITY
of original design documents, Technical Team understands the entire
program architecture and design document is prepared with
| |
Code-Structure
Representation |
| |
Functional
Representation |
| |
Architecture
Representation |
|
Modification
Requirement Analysis |
Any request from the customer for
| |
Adding
new functions |
| |
Improving
the performance of existing functions |
| |
Migrating
the system to other operational platforms |
|
Modifying
the existing function |
|
Correcting
faults in the system |
Requests
are analyzed in detail so that the modification requirements can
be well understood both by the customer and the Technical Team involved
in the project.
 ^ |
| |
Localization
and impact analysis |
The exact location in the source code where the proposed modifications
are to be made is identified. Once Impact Analysis is done, the
project members understand the impact of every change they are introducing.
The Outputs of this Phase are
| |
Impact
Analysis Document |
| |
Modified
Design Document |
Test
cases are designed to test the proposed changes in the system. The
test data include a wide range of possible data. Test paths and
the regression testing procedures will be defined. Actual testing
takes place after the implementation of the proposed changes to
the system.
In this Phase, implementation of the proposed modification is planned
based on the output produced by Localization and Impact Analysis.
It includes how to update the existing specification and design
documents, and how to re-code and configure the new and modified
components of the system.
Testing
is carried out in 4 Phases
|
Unit
or Module Level |
|
Integration
Testing |
|
System
Testing |
|
Acceptance
Testing |
One
or all of these methods are used depending on the size and complexity
of the project.
