ArticleslgStudy

computer science

MK II FPA

MK II FPA is a computer science topic covered in the lgStudy science library. This page brings together a partial reference excerpt, illustrations, worked examples, real-world applications and a short study plan, so you can understand MK II FPA rather than just read about it. In short: The MK II Method is one of the software sizing methods in functional point group of measurements. This is a method for analysis and measurement of information processing applications based on end user functional view of the system.

Key takeaways

  • MK II FPA belongs to computer science; place it in that map before memorising details.
  • Learn the definition first, then one example that makes the definition concrete.
  • Connect MK II FPA to a quantity you can measure, compute or draw — that is where exam questions come from.
  • Reproduce the core statement of MK II FPA from memory before moving on to harder problems.

Reference excerpt

The MK II Method is one of the software sizing methods in functional point group of measurements. This is a method for analysis and measurement of information processing applications based on end user functional view of the system. The MK II Method (ISO/IEC 20968 Software engineering—Mk II Function Point Analysis—Counting Practices Manual) is one of five currently recognized ISO standards for Functionally sizing software.

Introduction The MK II Method was defined by Charles Symons in book published in 1991. UK Software Metrics Association is now responsible for the method and its continuing development. The functional user requirements of the software are identified and each one is categorized into one of there types: inputs, exits and objects. In order to determine functional size of system these functional requirements are counted.

MkII FPA counting rules MkII counting procedure contains several steps described below.

Determine the ViewPoint, Purpose and Type of the Count

Define the Boundary of the Count Boundary of system represents logical line that separates users from a system. It is used to determine logical transactions such as inputs and exits that crosses boundary during the interaction between user and system.

Identify the Logical Transactions Each transaction is counted once even though it may be executed from more than one point in the application.

Identify and Categorise Data Entity Types Data entity types are logical data structures that contains information meaningful to the user. In MarkII method there is only one type of data entity types - Objects. Objects must be correctly identified so they can be counted.

Count the Input Data Element Types, the Data entity Types Referenced, and the Output Data Element Types This can be done by a simple spreadsheet and needs to be added up and applied a formula to find the exact MKII FPA value

Count the Functional Size Once the transactions and objects in the system are identified, they can be counted in order to find functional size of the system. Functional size of the system is represented as weighted counts of input/exit transactions and objects within the boundary of the system. Size can be expressed as following: Size = Wi*ΣNi+ We*ΣNe + Wo*ΣNo In the equation ΣNi, ΣNe and ΣNo are total numbers of unique inputs, exits and objects within the system. Currently recommended values for weighting coefficients are Wi = 0.58, We = 1.66, and Wo = 0.26.

See also Function point Software development effort estimation Software Sizing

References

External links Mk2 method explained ISO/IEC Standard

Worked examples

Example 1 — a first encounter with MK II FPA

Start with the simplest possible case. Write down what MK II FPA claims or describes in one sentence, then invent the smallest concrete situation in which that sentence is true. In computer science, the smallest case is usually a single object, a single equation or a single measurement. Check that every symbol or term in your sentence has a meaning in that case.

Example 2 — changing one variable

Take the situation from Example 1 and change exactly one quantity: double it, halve it, or set it to zero. Predict what should happen to MK II FPA before you calculate. Comparing your prediction with the result is the fastest way to find out whether you understand the idea or only the words.

Example 3 — an exam-style question

Typical questions about MK II FPA ask you to (a) state it precisely, (b) apply it to given data, and (c) explain a limitation. Practise writing all three answers in under five minutes; the third part is what separates a full-mark answer from an average one.

Applications of MK II FPA

In research
MK II FPA appears in computer science research whenever the underlying quantities have to be modelled precisely. Papers usually cite it as a starting assumption and then explore where it breaks down.
In technology and industry
Engineering practice reuses MK II FPA in design rules, simulations and safety margins. Knowing the idea lets you read a specification sheet and understand why the numbers look the way they do.
In the classroom
MK II FPA is common in secondary-school and first-year university syllabi. It links to neighbouring topics Software engineering costs, Software metrics, so understanding it makes those chapters shorter.
In everyday life
Look for MK II FPA outside the textbook — in sport, cooking, traffic, electronics or the sky above you. An example you found yourself is remembered far longer than one you were given.
Ask Teacher Smith questions about this articleOpens your AI tutor with a question about “MK II FPA” →

Affiliate

Preply — study more efficiently by working with a personal tutor. 50% off.

How to study MK II FPA in 20 minutes

  1. Read the reference excerpt below once, without taking notes.
  2. Close the page and write down what MK II FPA means in your own words.
  3. Compare your version with the excerpt and mark what you missed.
  4. Work through the three examples above with pen and paper.
  5. Explain MK II FPA out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is MK II FPA in simple terms?

The MK II Method is one of the software sizing methods in functional point group of measurements. This is a method for analysis and measurement of information processing applications based on end user functional view of the system.

Why does MK II FPA matter?

Because it connects several computer science ideas at once: it gives you a definition you can apply, a quantity you can calculate, and a way to check whether a result is plausible.

How should I study MK II FPA?

Read the excerpt, restate it from memory, then work through the examples and applications listed on this page. The five-step study plan above takes about twenty minutes.

What does this page cover?

It gives you a compact reference excerpt plus original lgStudy explanations, examples, applications and study material on MK II FPA.

Tags

  • Software engineering costs
  • Software metrics

Keep exploring