As for the new library management system I would
highly recommend Unit testing to be carried out. A unit is the smallest
possible testable software component. A unit is not of large scale, so it is
not difficult to design, execute, record and analyze the test outcomes for than
larger volumes of code are. They are numerous benefits of using Unit testing
which is further explained below:
· It simplifies the debugging process
whereby if a test fails, the only the recent change made in the code need to be
· It drastically reduces the cost
since the bugs are found early because bugs detected way later are usually a
result of numerous changes
· It produces a high quality code
because every defect that may occur would be identified and corrected before it
is taken up for integration testing
· Unit testing makes the whole coding process
agile(faster) because altering a tested code gives you the confidence to
proceed for refactoring confidently.
This state of the art library management system
that has been deployed also requires a maintenance program that suites it best.
I would strongly encourage Perfective maintenance than any other maintenance
method for Granite because of the numerous reasons listed below:
· It enhances the performance and the functionality
of the library management
· In most cases it extends the
lifecycle of the system reducing the need for capital replacement.
· It will enhance the customer service
because the maintenance teams have less unplanned maintenance calls and they
can respond promptly to new problems
Perfective maintenance mainly deals with
executing new or altered user requirements of the library system or any other
system. It consists of functional enhancements of the system in addition to the
activities to increase the overall system performance.