Product Metrics
Arvind Kiwelekar
Software Quality
“ Software quality is conformance to explicitly stated functional and performance requirements, explicitly documented development standards, and implicit characteristics that are expected of all professionally developed software”
Quality Factors
●
Correctness(Extent), Product Operation Reliability(Extent) , Product Operation Efficiency(Amount) Product Operation Integrity(Extent), Product Operation Usability(Effort)Product Operation Maintainability(Effort) Product Revision Flexibility(Effort) Product Revision Testability(Effort) Product Revision Portability(Effort) Product Tranisition Reusability(Extent) Product Transition
●
●
●
●
●
●
●
●
●
●
Some Definitions
● ● ●
Measure Metric Indicators
Measurement Process
● ● ● ●
Formulation Collection Analysis Feedback
Types of Metrics
●
Metrics for the Analysis Model
– – –
Functionality Delivered System Size Specification Quality Architectural Metrics Component Level Metrics Interface Design Metrics Specialized OO Design Metrics
●
Metrics for Design Model
– – – –
Types of Metrics
●
Metrics for Source Code
– – –
Halstead Metrics Complexity Metrics Length Metrics Statement and Branch Coverage Metrics Defect Related Metrics Testing Effectiveness In process metrics
●
Metrics for Testing
– – – –
Function Point Based Metrics
●
To estimate the cost or effort required to design code and test the software. To predict number of errors that can be encountered during testing. Forecast the number of components or sourc line in the implementation.
●
●
Information Domain Values
● ● ● ● ●
Number of external inputs Number of external outputs Number of external enquiries Number of internal logical files Number of external interfaces
Value Adjustment Factor
●
Does the system require reliable backup and recovery Are specilaized data communications required to or from application? Is performance critical. Will the system run in an existing heavily utilized operational enviornment? Does the system require on-line data entry?
●
● ●
●
Value Adjustment Factor
●
Does the on-line data entry require the input transaction to be built over multiple screens. Are the ILF updated online? Are the inputs, outputs, or inquires complex? Is the internal processing complex? Is the code designed to reusable? Are conversion and installation included in the design? Is the system designed for multiple installations in different organization? Is the application designed to facilitate change and for ease of use by the user?
●
●
●
●
●
●
●
Example 1
Test Sensor Zone Setting Z o n e S e t t i n g
message Sensor status activate/deactivate Alaram alert
%PDF-1.4 %äüöß 2 0 obj <> stream x ��XM�#7# ��W�##G��# �0c�#r �ĐC �m? d# �����$U�[R �dY��m ���zOO=# �J�{ �* �x ���+�S ���> ��# �# �D, ߯[�SU# ���# # # # # � o _# �� #'1### �## �f��������gc��wa ��dj�c�zw73 ��¹��,�
Reading Assignment
●
Read the example that will calculate FP for SafeHome Application from RSP's SEPA book page number(474-476) Prepare a write up and submit it on 28th July 2009
●
Assignment 2
●
Take the application of Course Registration system (CRS) discussed in the last semester Develop an analysis model i.e. either DFD or usecase model Calculate FP for the CRS Deadline for submission 29th July 2009
●
●
●
Schedule for Submission
● ● ● ● ● ●
First 10 students from roll call 9.30 to 10.00 AM Second 11 to 20 Students from 10.00 to 10.30 21 to 30 -> 10.30 to 11.30 31 to 40-> 11.30 to 12.00 41 to 50-> 12.30 to 1.00 51 to 60-> 1 to 1.30