
Software Metrics/Quality Metrics. Software “Quality” Metrics: Product Pre-Release and Post-Release Process Project Data Collection. Product Characteristics. Project Characteristics. Process Characteristics. Software Metrics. Software Product All the deliverables
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Product
Characteristics
Project
Characteristics
Process
Characteristics
Will talk about this
more
Function point
Meantime to failure for install problem should probably be close to 0
---- counted with -- MTTF -- means more to users?
Separate Segment
What kind of validity problem might you encounter?
– “construct”: applicability, “predictive”: relational ; “content” : coverage?
Note: - What about “tough” algorithms and other function oriented stuff?
(We take of that separately in a separate 14 “Degree of Influences”)
For Logical Files and External Interfaces (DATA):
# of RET1-19 DET20-50 DET50+ DET
1 Low Low Ave
2 -5 Low Avg High
6+ Avg High High
For Input/Output/Query (TRANSACTIONS):
# of FTR1-4 DET5 -15 DET16+ DET
0 - 1 Low Low Ave
2 Low Avg High
3+ Avg High High
Low
Average
High
3
4
6
Input
5
7
Output
4
3
Inquiry
4
6
Logical files
7
10
15
Ext. Interface
7
5
10
all basic entities
Continuing the Example of adding new employee:
- 1 external interface (average) = 7
- 1 external interface (low) = 5
- 1 external interface (low) = 5
- 1 input (high) = 6
Initial Function Point = 1x7 + 1x5 + 1x5 + 1x6 = 23
Function Point (FP) = Initial FP x TCF
Finishing the Example:
Suppose after considering 14 DI’s, our TCF = 1.15, then:
Function Point = Initial FP x TCF = 23 x 1.15 = 26.45
Be careful of this type of claims – use it with caution
Separate Segment
defects found (by severity) per time period ( per dev. phase)