Function Point Analysis
- Derive from FP the size of planned, installed, or enhanced software by using McConnell’s table
- Estimate project effort, duration, and cost through the use of FP productivity history
- Compare different software projects in terms of the functionality they offer regardless of their relative sizes and complexities
Overview
Function Point Analysis (FPA) software estimation technique is an IFPUG estimation technique and is recognized as the most comprehensive way of estimating a software project, Our Function Point analysis program helps to provide the tools for individuals to learn and understand how to apply the function point technique. The rules defined in the Counting Practices Manual are incorporated into several introduction to Function Point Analysis. Introduction to Function Point Analysis courses are delivered by recognized experts who have practical experience in the software measurement industry.
Course outline
Concepts of software measurement
- Quantitative measurement techniques
- Process/product evaluation
- Basic indicators
- Composite indicators
- Benefits
Introduction to Function Point Analysis
- Principle of Functional Size
- Function types
- Steps of Functional Size Measurement
- Types of Function Point counts
- ISO standard
Alternative size indicators
- Lines of Code
- Mark II
- COSMIC FFP
- 3D
- FP+
IFPUG counting rules
- Identification of function types
- Complexity assignment
- Examples
- Measuring existing systems
- Guidelines
- Practices
- OO and GUI applications
- Counting strategies
Adjusting the initial Function Point count
- Implementation constraints
- General application attributes
- Degree of influence
- Example of Value Adjustment Factor calculation
Precision of Function Point measurements
- Error margins
- Verification of results
- Actual versus estimated size
Counting Function Points in maintenance
- Maintenance
- Enhancement
- Enhancement project Function Point count
- Application Function Point count
Hands-on Cases
- Existing applications
- Planned application
- Enhanced application
- Discussion of sample solutions
Applying Function Point results
- Work effort
- Evaluating productivity
- Estimating software costs
- Modification of Function Point counts
- Misuse
- Tools
- Benchmarking
- Installing Metric programs
- Function Point experiences
- Selecting indicators
- Certification
- Responsibilities
- Resources
- Key issues
Key Features
- 8 hours Instructor led Online Training
- Soft copy of training courseware
- 8 Hours of CCR PDU’s Certificate
- Course Completion Certificate
- Flexibility to choose classes
- 2 Case studies
- 100% Money Back Guarantee
- Post training support
- 10% discount on any other Course
Course Objectives
- Understand that Function Points are a measure of software functionality and not a measure of software size or complexity
- Derive from FP the size of planned, installed, or enhanced software by using McConnell’s table
- Estimate project effort, duration, and cost through the use of FP productivity history
- Compare different software projects in terms of the functionality they offer regardless of their relative sizes and complexities
- Use FP to compare alternative software architectural designs
- Quantify the productivity of their entire software development or enhancement process from the beginning of the requirements phase to the end of the roll-out phase
- Know NOT to use FP to judge any individual’s productivity
- Know NOT to use FP production rates to judge the productivity of a programming team
- Quantify the quality of their software products