
- •Version 4.1 Revision e5
- •Index 70
- •Preface
- •Revisions
- •Revision 4.1 5/1/1998
- •Notices
- •Brief cosmos Product Description
- •Cosmos Capabilities and Theory of Operation
- •Cosmos Project Level Estimation
- •Cosmos System Level Estimation
- •Cosmos Versions and Development History
- •Cosmos Personnel
- •Chapter 2: Function Point Model
- •Introduction to Function Points
- •Function Point Analysis
- •Application Boundary
- •Functionality
- •Data Functionality
- •Transaction Functionality
- •Complexity
- •Complexity Weights
- •Value Adjustment Factor and Adjusted Function Points
- •Backfire Method
- •Added, Changed, and Deleted Functionality
- •Comparison of Function Points and sloc
- •Cosmos and Function Point Analysis
- •Function Point Formulae Unadjusted Function Point Count
- •Total Degree of Influence
- •Value Adjustment Factor
- •Adjusted Function Point Count
- •Source Lines of Code: Backfire Method
- •Differences in Function Point Terminology
- •Chapter 3: cocomo Model cocomo Model Description
- •Cocomo Equations
- •Sloc and Delivered Source Instructions
- •Cocomo Modes
- •Cocomo Cost Drivers
- •Product Attributes
- •Hardware Attributes
- •Personnel Attributes
- •Project Attributes
- •Cocomo Complexity Influence Assignments
- •Cocomo Phase Distribution
- •Cocomo Formulae
- •Rayleigh Equations – General Description
- •Putnam’s Analysis: Software Equation
- •Manpower Buildup Index
- •Rayleigh Model
- •Development Phases
- •Application Type and Productivity
- •Rayleigh Formulae Software Equation
- •Manpower Buildup Index Equation
- •Chapter 5: Project Estimation Overview
- •Model Interrelationships
- •Import and Export of Models
- •Project Report
- •Chapter 6: System Estimation System Description
- •System Development Phases
- •System-LevelEffortEstimates
- •System-LevelScheduleEstimates
- •System-Level Manpower Buildup Index Level
- •System-Level Project Specification and Management
- •Schedule Compression
- •System Development and cocomo
- •System Output Report
- •References
- •Glossary
- •Customizing
Complexity
Each function identified in the function point analysis – EI, EO, EQ, ILF, or EIF – is weighted according to its complexity.
For data functions (IFLs and EIFs), the complexity is determined and rated by the numbers of Record Element Types (RETs – distinct record formats) and the number of Data Element Types (DETs – distinct fields) contained within the logical group of data.
For Internal Logical Files:
-
1 to 19 DET
20 to 50 DET
51 or more DET
1 RET
Low
Low
Average
2-5 RET
Low
Average
High
6 or more RET
Average
High
High
-
Where
DET =
Number of data element types (fields)
RET =
Number of Record Element Types (Subgroups of Internal Logical Files based on logical/user view of the data)
For External Interface Files
-
1 to 19 DET
20 to 50 DET
51 or more DET
1 RET
Low
Low
Average
2-5 RET
Low
Average
High
6 or more RET
Average
High
High
-
Where
DET =
Number of data element types (fields)
RET =
Number of Record Element Types (Subgroups of External Logical Files based on logical/user view of the data)
For transaction functions (EIs, EOs, and EQs), the complexity is determined and rated by the numbers of File Types Referenced (FTRs – number of ILFs and EIFs used by the process) and the number of Data Element Types (DETs – distinct fields) added, changed, deleted, or produced in outputs.
For External Inputs
-
1 to 4 DET
5 to 15 DET
16 or more DET
0-1 FTR
Low
Low
Average
2 FTR
Low
Average
High
3 or more FTR
Average
High
High
-
Where
DET =
Number of data element types (fields)
FTR =
Number of Internal Logical Files maintained or referenced plus number of External Interface files referenced during processing of the External Input
For External Outputs
-
1 to 5 DET
6 to 19 DET
20 or more DET
0-1 FTR
Low
Low
Average
2-3 FTR
Low
Average
High
4 or more FTR
Average
High
High
-
Where
DET =
Number of data element types (fields)
FTR =
Number of Internal Logical Files referenced plus number of External Interface files referenced during processing of the External Output
For External Inquiries
Compute the input side of the External Inquiry (just like an External Input)
Compute the output side of the External Inquiry (just like an External Output)
Use the higher of the two results