Information Technology Reference
In-Depth Information
general conclusions on existing data without looking at the specific circumstances.
Several product related metrics have been proposed and one is traceability. One
example to measure traceability is to measure how many of the original require-
ments are directly traceable to the use case model. Metrics are more appropriate
for object-oriented software (Jacobson et al.
1992
):
• Total number of classes
• Number classes reused
• Total number of operations
• Number of operations reused
• Total number of stimuli sent
• Number of classes inheriting
• Number of classes that are dependent
• Number of direct users of a class or operation
The activities of post-delivery maintenance essentially are analysis, design,
implementation, testing and documentation. Therefore, the metrics that measure
these activities are equally applicable to maintenance. Metrics specific to post-
delivery maintenance include measures relating to software defect reports with
total number of defect reports and classification of defects.
The challenge of post-delivery maintenance is that changing the maintenance is
harder than development, yet maintenance is looked down upon by developers and
is also paid less than developers (Schach
2007
).
11.14 Chapter Summary and Conclusions
The result of the presentation is the final activity in the project development
process. Section
11.1
shows the sample agenda for the presentation. During the
project termination and release phase, the product is delivered and the project
history is collected. A select few developers, the technical writers and the team
leaders are involved with wrapping up the project.
The end of the project is usually a good time to assess which techniques,
methods, and tools have worked and to decide which have been critical to the
success of the system. The post mortem phase concentrates on this. After post
mortem reviews, it is time to release the project. The post-delivery maintenance, is
used to either fix faults or extend the functionality of the product.
Once the product has passed its acceptance test, it is handed over to the client.
However, it is almost certain to undergo post-delivery maintenance, either to fix
faults or extend the functionality of the product.
Post-delivery maintenance is the most difficult of all aspects of software pro-
duction; a major reason is that post-delivery maintenance incorporates aspects of
all the other work-flows of the software process.
The defect report is filed by the user if the product appears to be functioning
incorrectly. The maintenance programmer should first consult the defect report
