Skip to content

MK II FPA

The MK II Method is one of the software sizing methods in functional point group of measurements.

Version
v1 · 2026-09-28 · History
Domain-specific #
10744
Domain group
Applied Sciences & Engineering
Origin domain
Computer Science & Software Engineering
Subdomains
Software Metrics, Function Point Analysis → Computer Science & Software Engineering

Core Idea

MK II FPA is treated here as the recurring computer_science_and_information identity summarized by this source-grounded definition: The MK II Method is one of the software sizing methods in functional point group of measurements.

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.

The functional user requirements of the software are identified and each one is categorized into one of there types: inputs, exits and objects. UK Software Metrics Association is now responsible for the method and its continuing development. In order to determine functional size of system these functional requirements are counted.

For MK II FPA, the abstraction is narrower than the article's general subject matter: a positive case must preserve The MK II Method is one of the software sizing methods in functional point group of measurements. Retaining only the name, a familiar example, or a downstream effect is insufficient. The specialist roles and tests remain anchored in computer_science_and_information, which is why this identity is domain-specific rather than prime.

Structural Signature

Sig role-phrases:

  • Defining carrier — The MK II Method was defined by Charles Symons in book published in 1991.
  • Constitutive relation — 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.
  • Operating condition — This is a method for analysis and measurement of information processing applications based on end user functional view of the system.
  • Recognition evidence — UK Software Metrics Association is now responsible for the method and its continuing development.
  • Admissible variation — The functional user requirements of the software are identified and each one is categorized into one of there types: inputs, exits and objects.
  • Characteristic consequence — In order to determine functional size of system these functional requirements are counted.
  • Failure boundary — Determine the ViewPoint, Purpose and Type of the CountDefine the Boundary of the Count.

What It Is Not

  • Not the whole field of computer_science_and_information. The node requires the specific identity stated by The MK II Method is one of the software sizing methods in functional point group of measurements.
  • Not an over-broad reading. The MK II Method was defined by Charles Symons in book published in 1991.
  • Not an over-broad reading. UK Software Metrics Association is now responsible for the method and its continuing development.
  • Not an over-broad reading. The functional user requirements of the software are identified and each one is categorized into one of there types: inputs, exits and objects.
  • Not automatically Function point. Retrieval proximity does not establish equivalence; the two identities must be compared by carrier, operation, and failure boundary.

Scope of Application

MK II FPA applies literally inside computer_science_and_information wherever the source-defined carrier and relation can be established. Its documented habitats include:

  • Documented setting. This is a method for analysis and measurement of information processing applications based on end user functional view of the system.
  • Documented setting. 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.
  • Documented setting. The MK II Method is one of the software sizing methods in functional point group of measurements.
  • Introduction. The MK II Method was defined by Charles Symons in book published in 1991.
  • Introduction. UK Software Metrics Association is now responsible for the method and its continuing development.
  • Introduction. The functional user requirements of the software are identified and each one is categorized into one of there types: inputs, exits and objects.

Outside computer_science_and_information, the name should be retained only when these same operational conditions survive; otherwise the comparison belongs to the broader parent Measurement or should be marked as analogy.

Clarity

A clear use of MK II FPA names the carrier, the operative relation, and the conditions under which the source treats the identity as present. The minimal definition is The MK II Method is one of the software sizing methods in functional point group of measurements. The strongest recognition evidence in the frozen account is: UK Software Metrics Association is now responsible for the method and its continuing development. A report should distinguish that evidence from a proxy, consequence, or common implementation. It should also state the qualification The MK II Method was defined by Charles Symons in book published in 1991. so that a reader can reproduce the classification rather than infer it from topical resemblance.

Manages Complexity

MK II FPA compresses multiple computer_science_and_information details into a stable diagnostic relation. The source shows both the central mechanism—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.—and the practical consequence—in order to determine functional size of system these functional requirements are counted. This compression makes cases comparable while leaving parameters, conventions, exceptions, and evidential quality explicit. It is lossy by design: local history and implementation details may be omitted only when they do not alter the defining relation.

Abstract Reasoning

  1. Type the carrier. Identify the computer_science_and_information entities to which the claim applies.
  2. State the relation. Use the source-grounded identity: The MK II Method is one of the software sizing methods in functional point group of measurements.
  3. Check operation and conditions. This is a method for analysis and measurement of information processing applications based on end user functional view of the system.
  4. Demand recognition evidence. UK Software Metrics Association is now responsible for the method and its continuing development.
  5. Test variation. Change an implementation or setting while preserving the functional user requirements of the software are identified and each one is categorized into one of there types: inputs, exits and objects.
  6. Run the collapse test. Remove the defining operation; if the label still seems equally apt, only a topic or correlate was retained.
  7. Reduce cautiously. When the specialist conditions cannot be carried, route the residual comparison to Measurement.

Knowledge Transfer

Within the home domain. Knowledge about MK II FPA transfers literally when a new case preserves the same carrier type, relation, and recognition test. 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.

Beyond the home domain. No canonical parent is asserted for MK II FPA. An outside case receives the specialist name only when the same typed roles and rejection conditions can be filled literally; otherwise the comparison remains an analogy pending later graph densification.

Examples

Canonical

It is used to determine logical transactions such as inputs and exits that crosses boundary during the interaction between user and system. This case is canonical because it supplies a concrete carrier and lets the defining relation be checked rather than merely named.

Mapped back: carrier → the entities in the documented case; operation → The MK II Method is one of the software sizing methods in functional point group of measurements; recognition evidence → UK Software Metrics Association is now responsible for the method and its continuing development

Applied / In Practice

The MK II Method was defined by Charles Symons in book published in 1991. The applied case shows how the identity is used under a second setting or qualification while keeping the same operative relation.

Mapped back: changed setting → Introduction; invariant → The MK II Method is one of the software sizing methods in functional point group of measurements; boundary → the case exits the class when the MK II Method was defined by Charles Symons in book published in 1991

Structural Tensions

T1 — Stable identity versus admissible variation. The MK II Method was defined by Charles Symons in book published in 1991. The tension matters because emphasizing only one side either dissolves the identity or overstates what the evidence and domain conventions warrant.

Diagnostic: Which changes preserve the defining relation, and which replace it?

T2 — Recognition versus proxy. UK Software Metrics Association is now responsible for the method and its continuing development. The tension matters because emphasizing only one side either dissolves the identity or overstates what the evidence and domain conventions warrant.

Diagnostic: Does the cited evidence establish the identity or only a correlated sign?

T3 — Definition versus implementation. The functional user requirements of the software are identified and each one is categorized into one of there types: inputs, exits and objects. The tension matters because emphasizing only one side either dissolves the identity or overstates what the evidence and domain conventions warrant.

Diagnostic: Is the observed implementation constitutive, optional, or merely common?

T4 — Scope versus overextension. In order to determine functional size of system these functional requirements are counted. The tension matters because emphasizing only one side either dissolves the identity or overstates what the evidence and domain conventions warrant.

Diagnostic: Can every claimed application fill the same typed roles without metaphor?

T5 — Transfer versus domain accent. The MK II Method was defined by Charles Symons in book published in 1991. The tension matters because emphasizing only one side either dissolves the identity or overstates what the evidence and domain conventions warrant.

Diagnostic: Does the receiving case instantiate MK II FPA literally, co-instantiate Measurement, or only resemble it?

T6 — Autonomy versus reduction. 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. The tension matters because emphasizing only one side either dissolves the identity or overstates what the evidence and domain conventions warrant.

Diagnostic: What does MK II FPA distinguish that the broader parent Measurement leaves together?

Terminal boundary synthesis. For MK II FPA, the terminal identity test begins with the definition The MK II Method is one of the software sizing methods in functional point group of measurements.. A reviewer must then establish the carrier and operation described by The MK II Method was defined by Charles Symons in book published in 1991. and 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.. Recognition is constrained by This is a method for analysis and measurement of information processing applications based on end user functional view of the system., while admissible variation is limited by UK Software Metrics Association is now responsible for the method and its continuing development. and the collapse boundary The functional user requirements of the software are identified and each one is categorized into one of there types: inputs, exits and objects.. The source-domain setting in computer science and information matters because This is a method for analysis and measurement of information processing applications based on end user functional view of the system. and 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. specify where those roles have literal occupants. The strongest negative controls are The node requires the specific identity stated by The MK II Method is one of the software sizing methods in functional point group of measurements. and The MK II Method was defined by Charles Symons in book published in 1991.; a case satisfying either exclusion should not be rescued merely because its label or examples look familiar.

Terminal adjudication sequence. First, bind the claimed instance to a concrete carrier and state the criterion by which The MK II Method is one of the software sizing methods in functional point group of measurements. is recognized. Second, vary implementation, scale, notation, and example while holding 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. fixed; persistence supports one identity rather than several topic fragments. Third, remove This is a method for analysis and measurement of information processing applications based on end user functional view of the system. or trigger The functional user requirements of the software are identified and each one is categorized into one of there types: inputs, exits and objects. and verify that the classification fails. Fourth, compare the result with the two negative controls instead of relying on name similarity. Fifth, check scope against This is a method for analysis and measurement of information processing applications based on end user functional view of the system. and record any qualification supplied by computer science and information. Finally, audit the graph claim. The approved unparented placement prevents a weak lexical resemblance from becoming a false ontological claim; a later edge must preserve every constitutive role stated here. This sequence makes the entry rejectable, keeps analogy separate from literal transfer, and exposes which fact would require revision.

Structural–Framed Character

MK II FPA is structural-leaning. Its structural side is the repeatable organization summarized by The MK II Method is one of the software sizing methods in functional point group of measurements. Its framed side is the computer_science_and_information vocabulary that fixes the carrier, evidence, exceptions, and admissible transformations.

Evaluative weight: the identity can be stated descriptively even when applications carry practical stakes. Human-practice dependence: the source-grounded carrier determines whether the relation exists independently or is constituted by a practice. Institutional origin: disciplinary conventions stabilize the name and test. Vocabulary portability: This is a method for analysis and measurement of information processing applications based on end user functional view of the system. Import versus recognition: literal transfer requires the same mechanism; shape alone is analogy.

Its portable skeleton is Measurement. Its character: a recurring specialist identity whose thin organization can be abstracted, while its operational meaning remains domain-bound.

Structural Core vs. Domain Accent

What is skeletal. The MK II Method is one of the software sizing methods in functional point group of measurements. The stable skeleton is the typed relation expressed in that definition and the entry's recognition and collapse tests. The source identifies these operative conditions: The MK II Method was defined by Charles Symons in book published in 1991. 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. It further constrains recognition and variation through: This is a method for analysis and measurement of information processing applications based on end user functional view of the system. UK Software Metrics Association is now responsible for the method and its continuing development.

What is domain-bound. computer science and information supplies the operative entities, technical vocabulary, warrants, and exceptions that make MK II FPA literal. Its documented scope includes the condition that This is a method for analysis and measurement of information processing applications based on end user functional view of the system. Another bounded application condition is that 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. These are not decorative examples; they determine which carrier and evidence can fill the abstraction's roles.

Why no parent is asserted. Removing those specialist details does not currently yield one live catalog node that is a necessary genus for every instance. The entry is therefore approved as unparented rather than attached by topical resemblance. Its collapse evidence remains specific—The functional user requirements of the software are identified and each one is categorized into one of there types: inputs, exits and objects.—and future graph densification may discover a defensible relation only if it preserves that boundary.

  • Approved unparented node. No current live node supplies a defensible necessary genus or structural prerequisite for MK II FPA. The reviewed identity is: The MK II Method is one of the software sizing methods in functional point group of measurements. The accelerated suggestion was declined because topical or lexical similarity does not establish hierarchy; the node is admitted without a parent pending later graph densification.
  • Related reasoning operations. Evidence, representation, comparison, classification, transformation, or evaluation may participate in particular cases, but participation does not make any one of them a necessary parent of every instance.

Neighborhood in Abstraction Space

MK II FPA sits in a sparse region of the domain-specific corpus (71st percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Unclustered & Miscellaneous (2551 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-08

Not to Be Confused With

  • Measurement. The parent omits the specialist differentia. Tell: Can the case establish The MK II Method is one of the software sizing methods in functional point group of measurements?
  • Function point. A standardized unit estimating software functional size from user-visible inputs, outputs, inquiries, data groups and interfaces. Tell: Which entry's carrier, operation, and failure condition are satisfied?
  • AWPP. A counting-complexity class whose language decisions are represented by GapP functions that approximate a normalized acceptance indicator within bounded error. Tell: Which entry's carrier, operation, and failure condition are satisfied?
  • Halstead complexity measures. A family of static software metrics derived from counts of distinct and total operators and operands. Tell: Which entry's carrier, operation, and failure condition are satisfied?
  • A measurement, proxy, or consequence. Those may provide evidence without being the identity. Tell: Would MK II FPA remain present if the detector or downstream effect changed?
  • A metaphorical analogue. A similar shape outside computer_science_and_information lacks the specialist mechanism. Tell: Do the native roles transfer literally, or only the parent Measurement?

References

  • Frozen Wikipedia discovery revision: https://en.wikipedia.org/wiki/MK_II_FPA (revision 1316837475).
  • Preserved source candidate: http://www.iso.org/iso/catalogue_detail.htm?csnumber=35603
  • Preserved source candidate: http://www.uksma.co.uk/
  • Preserved source candidate: https://web.archive.org/web/20191021070910/http://www.uksma.co.uk/
  • Preserved source candidate: https://web.archive.org/web/20091203120309/http://www.uksma.co.uk/mk2.asp

The frozen Wikipedia revision is discovery provenance. The retained source set was reviewed for identity, formal or operational relation, and scope. The encyclopedia's structural synthesis is bounded to those claims; a thin authority surface is recorded as a nonblocking source-strengthening repair rather than concealed.