J.E.D.I
5.8 Mapping Implementation Deliverables with the Requirements Traceability Matrix
Normally, no additional RTM elements are used for the implementation phase. Rather, we monitor the development of each software component defined under the Classes
column. However, during the course of the development, additional classes may have been developed. They should be entered in this column under the appropriate package.
We can use the RTM to determine how many of the classes have been implemented, integrated and tested.
5.9 Implementation Metrics
Since the program characteristics must correspond to design characteristics, the metrics used for implementation are the metrics for the design. Other metrics considered at
implementation phase are used for succeeding similar projects. They serve as history data that can be used for estimation for other projects.
1. Lines of Code LOC. This is the number of statement lines that was used. It can be for a program, component or entire software. It is basically used later
on in managing similar projects. 2. Number of Classes. This is the total number of classes created.
3. Number of Documentation Pages. The total number of documentation produced.
4. Cost. The total cost of developing the software. 5. Effort. This is the total number of days or months the project was developed.
Software Engineering 266
J.E.D.I
5.10 Exercises
5.10.1 Defining the Internal Documentation Format
1. Define the Header Comment Block that will be used for the Internal Documentation
of the program. As a guide, the following are the recommended components: • Component Name
• Author of the Component • Date the Component was last created or modified
• Place where the component fits in the general system • Details of the components data structure, algorithm and control flow
Sometimes, it would help to place historical information about the program. The recommended components are:
• Who modified the component? • When the component was modified?
• What was the modification? The format should include how it will be written such as spacing, labels are in upper
case etc. Provide a sample source file. 2. Using the Header Comment Block defined in number one for the Internal
Documentation, implement the AthleteRecordUI,
FindAthleteRecordUI, AthleteListUI
and FindAthleteRecord designed in the previous chapter. If the
database cannot be implemented at this point, all methods of the controller that use objects in the persistent and database layer are coded to display a message describing
what the method is supposed to do. As an example, for the public getAthleteRecordString searchCriteria
method the programmer simply displays a message dialog box to the user stating that this method returns a list of
athlete records as specified by the value of searchCriteria.
5.11 Project Assignment
The objective of the project assignment is to reinforce the knowledge and skills gained in this chapter. Particularly, they are:
1. Defining the header comment block 2. Tracking implementation using the Requirements Traceability Matrix
MAJOR WORK PRODUCTS: 1. Implemented Software
2. Installation and Configuration Files
Software Engineering 267
J.E.D.I
6 Software Testing
Software is tested to detect defects or faults before they are given to the end-users. It is a known fact that it is very difficult to correct a fault once the software is in use. In this
chapter, the methods and techniques to develop test cases will be discussed. Software testing strategies are also presented to help us understand the steps needed to plan a
series of steps that will result in the successful construction of the software.
6.1 Introduction to Software Testing
Kategori