Page 78 - DCAP305_PRINCIPLES_OF_SOFTWARE_ENGINEERING

Principles of Software Engineering

Notes
4. Heavily used How heavily used is the current hardware
configuration platform where the application will be executed?
5. End-user efficiency How frequently are transactions executed daily,
weekly, monthly, etc.?
6. On-Line data entry What percentage of the information is entered
On-Line?
7. End-user efficiency Was the application designed for end-user
efficiency?
8. On-Line update How many ILF’s are updated by On-Line
transaction?
9. Complex processing Does the application have extensive logical or
mathematical processing?
10. Reusability Was the application developed to meet one or
many user’s needs?
11. Installation ease How difficult is conversion and installation?
12. Operational ease How effective and/or automated are start-up,
back-up, and recovery procedures?
13. Multiple sites Was the application specifically designed,
developed, and supported to be installed at
multiple sites for multiple organizations?
14. Facilitate change Was the application specifically designed,
developed, and supported to facilitate change?

Once all the 14 GSC’s have been answered, they should be tabulated using the IFPUG Value
Adjustment Equation (VAF) 14 where: Ci = degree of influence for each General System
Characteristic
VAF = 0.65 + [ (Ci) / 100] .i = is from 1 to 14 representing each GSC.
i =1 Ã¥ = is summation of all 14 GSC’s.
The final Function Point Count is obtained by multiplying the VAF times the Unadjusted
Function Point (UAF).
FP = UAF * VAF
4.1.2 Software Quality Metrics

We best manage what we can calculate measurement enables the association to get better the
software process; assist in planning, tracking and controlling the software project and assess
the quality of the software thus produced. It is the measure of such specific attributes of the
process, project and product that are used to compute the software metrics. Metrics are analyzed
and they provide a dashboard to the management on the overall health of the process, project
and product. Generally, the validation of the metrics is a continuous process spanning multiple
projects. The kind of metrics employed generally account for whether the quality requirements
have been achieved or are likely to be achieved during the software development process. As
a quality assurance process, a metric is needed to be revalidated every time it is used. Two
leading firms namely, IBM and Hewlett-Packard have placed a great deal of importance on
software quality. The IBM measures the user satisfaction and software acceptability in eight
dimensions which are capability or functionality, usability, performance, reliability, ability to be
installed, maintainability, documentation, and availability. For the Software Quality Metrics the
Hewlett-Packard normally follows the five general quality parameters namely the functionality,
the usability, the reliability, the performance and the serviceability. In general, for most software

72 LOVELY PROFESSIONAL UNIVERSITY