HOME

TheInfoList



OR:

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 ISO is the most common abbreviation for the International Organization for Standardization. ISO or Iso may also refer to: Business and finance * Iso (supermarket), a chain of Danish supermarkets incorporated into the SuperBest chain in 2007 * 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 In software development, effort estimation is the process of predicting the most realistic amount of effort (expressed in terms of person-hours or money) required to develop or maintain software based on incomplete, uncertain and noisy input. Effort ...
*
Software Sizing Software sizing or Software size estimation is an activity in software engineering that is used to determine or estimate the size of a software application or component in order to be able to implement other software project management activities ...


References


External links


Mk2 method explained


{{DEFAULTSORT:Mk Ii Fpa Software metrics Software engineering costs