|
||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||
|
Tools to help you implement a mature Measurement Process |
Total Metrics
>
Products
>
Metrics Documentation Toolkit
>
FPA Validation Manual
FPA Validation Manual
BackgroundDespite the fact tens of hundreds of organizations worldwide have implemented function point based metrics into their software development and maintenance environments few have introduced a formal validation or verification process into the process. For other types of software measures, validation of data is not an issue, since with only minimal training people can usually record their time, costs and resource consumption accurately and reliably. In comparison the measure of the ‘work product produced’ is not so straightforward. The software product itself is intangible and the current IFPUG rules to measure it, whilst appearing simple are quite difficult to apply without considerable practice and even then may be open to variable interpretations. Counting function points takes practice before people count correctly and repeatably. Before their results can be accepted into the metrics repository they need to complete a formal review process. Total Metrics developed the first published formal review process for Validating Function Points in conjunction with the Canadian Company SELAM. We have since provided training in this area worldwide and at IFPUG conferences since 1997. DescriptionThe purpose of the Validation and Review manual is to provide a concise set of easy to read guidelines that would assist in:
AudienceThe intended audience for the manual/s would be:
Attendance at one-day Total Metrics training course in the audit and validation process is a highly recommended pre-requisite to performing FPA reviews. Price is available on application.
Contents DetailsFunction Point Count Review and Validation ProcedureTABLE OF CONTENTS 1 Introduction 1.1 Purpose 1.2 Scope 1.3 Background 1.4 References 1.5 Count Review Roles and Responsibilities 1.5.1 Function Point Coordinator 1.5.2 Application / Project Manager 1.5.3 Function Point Reviewer 1.5.4 Function Point Counter 1.5.5 Applications Expert 2 Planning for the Review 2.1 Review Scheduling 2.2 Conduct of Review 2.3 Review Source Information 2.3.1 Source Information 2.3.2 Count Background 2.3.3 Count Strategy 2.3.4 Results Documentation 2.3.4.1 Count Reports 2.3.4.2 Count Documentation 2.3.4.3 Software Attributes 3 Review Process 3.1 Review Scope 3.2 Review Start-up 3.3 High Level Validation 3.3.1 Check Count Strategy 3.3.1.1 Logical Not Physical Approach 3.3.1.2 Quality of Information Supplied to the Count 3.3.1.3 FPA Applicable for Functional Domain 3.3.1.4 Version of FPA Rules 3.3.2 Check Count Environment 3.3.2.1 Count Purpose 3.3.2.2 Application Boundary 3.3.2.3 Count Scope 3.3.2.4 Type of Count 3.3.3 Check Reasonableness of Size (Development and Baseline Counts Only) 3.3.3.1 Compare Size Predicted by other Similar Applications 3.3.3.2 Effort to Develop 3.3.3.3 Effort to Support 3.3.3.4 Volume of Documentation 3.3.4 Check the Value Adjustment Factor 3.3.5 Enhancement Projects 3.3.6 High Level Validation Result 3.4 Intermediate Level Validation 3.4.0.1 Examine the Relationship Between the Number of Logical Files and the Unadjusted Function Point Size 3.4.1 Examine the Ratio of Types of Functions 3.4.2 Examine the Percentage Contribution to Size of the Function Types 3.4.3Examine the Complexity of the Function Types 3.5 Low Level Validation 3.5.1 Examine the Data Business Functions 3.5.2 Low Level Validation of Data for Enhancement Counts 3.5.2.1 Check Changed Data Transactions 3.5.2.2 Check Deleted Transactions 3.5.2.3 Check the ‘Type’ of Impacted Transactions 3.5.2.4 Check the Complexity of Impacted Transactions 3.5.3 Examine the Elementary Processes 3.5.4 Low Level Validation of Processes for Enhancement Counts 3.5.4.1 Check Changed Data Processes 3.5.4.2 Check Deleted Processes 3.5.4.3 Check the 'Type' of Impacted Processes 3.5.4.4 Check the Complexity of Impacted Processes 3.5.5 Cross Check Impacted Data and Transaction Function Types 3.5.6 Re-count a Typical System Module 3.6 Completing the Review 3.7 Review the Updated Application Baseline Count 4 Reporting the Review 4.1 Review Report 4.2 Feedback to the Function Point Coordinator 4.3 Feedback to the Counter Appendix A - Count Review Planning Forms Appendix B - Development and Application Review Result Forms Appendix C – Enhancement Count Review Results
|
|||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||