Level 4: Default Complexity Count

Level 4 Default Complexity Count Description

A default complexity count includes the following:

• application boundary is defined
• full functional decomposition to transaction level
• all files and transactions within scope are identified
• all files and transactions are classified according to type
• all files are defaulted to low complexity
• all transactions are defaulted to average complexity
• count is recorded and reported using the SCOPE Project Sizing Software^® software repository tool

Level 4 Default Complexity Count Attributes

Default Complexity Counts are:

• less detailed
• auditable
• reasonably accurate (within the limits of the FPA technique +/- 15%)
• documented
• maintainable

Best suited for the following count purposes:

• portfolio baseline assessment
• benchmarking development or support ratios
• quality metrics
• high level estimates
• as a baseline model for future enhancement project counting
• can be cost effective for large, legacy application baseline counts

Issues:

• efficient – counting rates up to 400 fps per day
• cost effective for large, legacy application baseline counts

Pre-requisites:

• average system documentation
• data model if possible
• access to system experts

SCOPE and Level 4 Counts

Use the Industry Default option when selecting the complexity of Processes and Data Groups in SCOPE