These free IFPUG study guides introduce functional sizing through application boundaries, user requirements and traceable counting decisions. IFPUG CFPS means Certified Function Point Specialist; it is different from the NFPA fire-protection credential with the same abbreviation. Use an original service-request example to practise identifying what is being measured before attempting detailed counting. The catalogue lists the older I40-420 label with a general request destination. Confirm the target, reference edition and resource availability before treating that label as a current exam code.
Want free reference PDFs? Email freelearning@ciscoforall.com with your exam code and name. We will send an available older reference file free of charge. Availability varies. See the request section below.
Choose a IFPUG learning path
Choose the learning direction closest to your role and current knowledge. These orientations help you organise practice; they are not official exam objective lists. Compare your chosen target with the exact current syllabus and record any additional topics you need.
| Learning path | Who it suits | Topics to understand | First practice task |
|---|---|---|---|
| Sizing foundations | New sizing learners | Purpose, boundary and user view | Draw an application boundary |
| Requirement analysis | Analysts reviewing functions | Inputs, outputs and logical information | Annotate an original requirement |
| Counting review | CFPS learners | Traceability and source applicability | Write a counting rationale |
Explore IFPUG Premium study PDFs
Connect additional review material with a specific preparation gap. Open a relevant product to explore its details, confirm its code and version, and decide how it supports your learning goal.
| Premium resource | Preparation focus |
|---|---|
| IFPUG vendor catalogue — confirm resource availability | The IFPUG catalogue currently links the I40-420 entry to a general request page. No individual product destination is presented here as verified. Confirm availability, current target name and manual edition through the vendor catalogue. |
The IFPUG catalogue currently links the I40-420 entry to a general request page. No individual product destination is presented here as verified. Confirm availability, current target name and manual edition through the vendor catalogue.
Define why and what you are measuring
Functional sizing begins with the measurement purpose, scope and application boundary. A project estimate, an enhancement comparison and an application inventory may raise different scope questions. Describe the user view rather than beginning with physical implementation details. The first useful output is a measurement statement that another learner can review. Keep the selected Counting Practices Manual edition visible before applying specific counting rules.
Practice task: Write a sizing purpose and boundary for a fictional support portal. Expected result: A measurement statement identifying scope and reference edition. Common mistake to avoid: Counting before defining the application boundary
Distinguish user-visible functions from implementation detail
A physical database table or line of code is not automatically a separate user-recognisable function. Requirements describe the logical services and information relevant to the measurement. In an original example, two screens might support related work while several technical components implement it. Record the requirement and boundary question before deciding a category. Do not turn this orientation into a substitute for the selected formal counting rules.
Practice task: Compare a user requirement with a fictional screen and storage diagram. Expected result: A list separating functional requirements from physical components. Common mistake to avoid: Equating every screen or database table with a counted function
Examine logical information through the user view
A functional information group should be understood through the requirements and relationships relevant to the user. Similar labels or shared physical storage do not alone settle the classification. Use a fictional portal with request and reference information, then explain which relationships are stated and which need clarification. Preserve the unresolved question rather than forcing a confident count from incomplete documentation.
Practice task: Annotate request records and reference information in a fictional requirement set. Expected result: A logical-information map with unresolved classification questions. Common mistake to avoid: Using physical storage alone to decide logical information groups
Trace transactions to their stated purpose
A service request, status enquiry and management summary have different stated purposes. Identify the user, triggering event and described result before assigning a functional classification. A repeated technical step is not sufficient evidence of a distinct user function. Build a trace from requirement to rationale and consult the applicable manual for the actual rule. This makes disagreements reviewable instead of relying on intuition.
Practice task: Map three original portal requirements to purpose, boundary and classification questions. Expected result: A transaction analysis with a traceable rationale. Common mistake to avoid: Counting technical repetitions as separate user functions
Preserve assumptions and resolve disagreements transparently
Two learners may reach different preliminary classifications because they assumed different boundaries or requirement details. Compare the assumptions first. Write the disputed fact, relevant source and clarification needed, then revise the rationale when evidence resolves the issue. A defensible record explains why a decision changed. It does not hide uncertainty behind a precise-looking number or claim that confidence replaces source support.
Practice task: Review two fictional sizing notes with different assumed boundaries. Expected result: A disagreement log identifying the source of the difference. Common mistake to avoid: Reporting a precise count while hiding unresolved assumptions
Keep functional and non-functional sizing directions distinct
Functional sizing and non-functional sizing address different aspects of software. IFPUG FPA and SNAP should not be treated as interchangeable labels. Match the certification direction, source edition and measurement purpose before combining notes. An old I40-420 resource may support a foundation comparison while failing to describe current assessment arrangements. Keep applicability questions separate from the original learning exercises on this page.
Practice task: Build a source map separating functional and non-functional learning directions. Expected result: A preparation map with clearly labelled scope and edition. Common mistake to avoid: Assuming every IFPUG sizing method uses the same rules
Practical checklist: produce evidence you can review
Complete these activities as written exercises or in an authorised practice environment with fictional data. Define the expected outcome before starting and save a brief explanation of what the result establishes. Verify version-specific steps for your selected target.
| Activity | What to do | Expected result |
|---|---|---|
| Define why and what you are measuring | Write a sizing purpose and boundary for a fictional support portal. | A measurement statement identifying scope and reference edition. |
| Distinguish user-visible functions from implementation detail | Compare a user requirement with a fictional screen and storage diagram. | A list separating functional requirements from physical components. |
| Examine logical information through the user view | Annotate request records and reference information in a fictional requirement set. | A logical-information map with unresolved classification questions. |
| Trace transactions to their stated purpose | Map three original portal requirements to purpose, boundary and classification questions. | A transaction analysis with a traceable rationale. |
Common mistakes and better study habits
Use these comparisons to find an assumption worth revisiting. For each mistake, write a new example with different details and explain why the corrected principle still applies.
| Common mistake | Why it matters | Better approach |
|---|---|---|
| Counting technical repetitions as separate user functions | This assumption skips a relevant check in: Trace transactions to their stated purpose. | Map three original portal requirements to purpose, boundary and classification questions. Review the expected result: A transaction analysis with a traceable rationale. |
| Reporting a precise count while hiding unresolved assumptions | This assumption skips a relevant check in: Preserve assumptions and resolve disagreements transparently. | Review two fictional sizing notes with different assumed boundaries. Review the expected result: A disagreement log identifying the source of the difference. |
| Assuming every IFPUG sizing method uses the same rules | This assumption skips a relevant check in: Keep functional and non-functional sizing directions distinct. | Build a source map separating functional and non-functional learning directions. Review the expected result: A preparation map with clearly labelled scope and edition. |
An original IFPUG self-check scenario
A support portal uses two physical tables for one user-recognisable information group. Can you count two groups solely from the table count?
Explanation: No. Physical storage alone does not establish the logical user view. Examine requirements, boundary and the applicable counting rules before reaching a classification.
Write your own answer before reading the explanation. Identify the evidence supporting it, then change one detail and decide whether your answer should change. This is an original learning exercise, not an actual exam question.
A flexible four-week study plan
| Stage | Focus | Practice outcome |
|---|---|---|
| Week 1 | Select the target and foundations | Write a sizing purpose and boundary for a fictional support portal. A measurement statement identifying scope and reference edition. |
| Week 2 | Apply core concepts | Compare a user requirement with a fictional screen and storage diagram. A list separating functional requirements from physical components. |
| Week 3 | Investigate weak topics | Annotate request records and reference information in a fictional requirement set. A logical-information map with unresolved classification questions. |
| Week 4 | Review mixed examples | Map three original portal requirements to purpose, boundary and classification questions. A transaction analysis with a traceable rationale. |
Four weeks is an example schedule, not a promise of readiness. Adjust each stage to your experience and available time. Extend a stage when you cannot explain the topic without the notes or apply it to a fresh scenario. Revisit the exact target objectives so a familiar topic does not replace a relevant topic you have not practised.
Build a revision record that shows progress
Create a tracker with target topic, initial explanation, practice activity, observed result and next review date. Separate a topic you recognise from a topic you can apply. A useful record makes the remaining gap visible and helps you choose the next activity instead of repeatedly rereading the same material.
When an answer is wrong, preserve the initial assumption, the contradicting evidence and the corrected principle. Create a second example using different details. If the explanation works only for the first example, return to the concept before adding more resources. Review recurring errors together: they may reveal a missing foundation rather than several unrelated weaknesses.
| Tracker field | Example entry to write | Review question |
|---|---|---|
| Requirement | Write a sizing purpose and boundary for a fictional support portal. | What outcome am I trying to establish? |
| Evidence | A measurement statement identifying scope and reference edition. | Which observation supports my explanation? |
| Limitation | State what the exercise did not establish. | Am I making a broader claim than the evidence allows? |
| Next activity | Compare a user requirement with a fictional screen and storage diagram. | What new example will test the principle? |
Request free IFPUG reference PDFs
Email freelearning@ciscoforall.com with your exam code and name, the target and resource edition if known, and the topics you need. We will send an available older reference file free of charge. Availability varies; a file may not be available for every target. The original notes, tables and exercises on this page are free to read without requesting a file.
Keep the code and version visible when using an older reference. Terminology, objectives and product behaviour may differ from your current target. Compare the material with the scope you intend to study and verify version-specific information before applying it in an exercise. We share only resources we are permitted to distribute. If you are unsure of the target name, include the learning goal so the request can be understood.
Combine practical learning with Premium PDFs
Use this guide to organise foundations and identify weaker topics. Then choose a relevant IFPUG Premium PDF for additional review. Give the resource a clear purpose: explain a concept, compare alternatives or repeat a practical scenario. Track the exact target and version alongside your notes so useful older material is not mistaken for complete current coverage.
Build a preparation routine around topic review, original exercises and an error log. After reviewing a resource, close it and explain the principle in your own words. Apply that principle to an unfamiliar example and record any remaining uncertainty. The value comes from understanding and application, rather than the number of files collected.
Frequently asked questions
Is this guide free?
Yes. The learning notes, tables, study plan and original exercises here are free to read. Premium PDFs are available separately through the linked product pages.
Is IFPUG CFPS the same as NFPA CFPS?
No. Here CFPS means Certified Function Point Specialist for software sizing. NFPA uses CFPS for Certified Fire Protection Specialist. Match the vendor and full credential name before requesting a resource.
Can I request a free reference PDF?
Yes. Email freelearning@ciscoforall.com with your name, exact target and exam code. We will send an available older reference file free of charge. Availability varies.
Will an older reference match my current target?
It may explain useful foundations while describing an earlier version. Compare its code, objectives and source edition with your exact target before treating it as a complete preparation resource.
How should I choose a Premium PDF?
Use the product table to find a resource matching your target. Explore its details and version, then connect it with the concept or practice gap you want to strengthen.
Must I complete the plan in four weeks?
No. Adjust the schedule to your experience, available time and practice results. Repeat a stage until you can explain its concepts and apply them to a different example.
Are these actual exam questions?
No. The scenarios are original exercises for understanding and decision-making. They are designed to help you practise explanations and evidence-based reasoning.
Does this guide guarantee an exam result?
No. Results depend on your knowledge, practical skills and preparation.
Choose your next IFPUG study resource
Complete one small activity today and record its result. For an available older reference, email freelearning@ciscoforall.com. For additional preparation, choose a relevant Premium PDF above or browse the vendor selection below.