Misplaced Pages

IFPUG

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.

The International Function Point Users Group ( IFPUG ) is a US -based organization with worldwide chapters of Function point analysis metric software users. It is a non-profit , member-governed organization founded in 1986.

#840159

10-524: IFPUG owns Function Point Analysis (FPA) as defined in ISO 20296 which specifies the definitions, rules and steps for applying the IFPUG's functional size measurement (FSM) method. FPA can be traced to the work of Allan Albrecht of IBM who pioneered functional sizing in 1979 which derived a functional size of product value distinct and disassociated from lines of code, technology, or software language. IFPUG maintains

20-488: A type, it is then assessed for complexity and assigned a number of function points. Each of these functional user requirements maps to an end-user business function, such as a data entry for an Input or a user query for an Inquiry. This distinction is important because it tends to make the functions measured in function points map easily into user-oriented requirements, but it also tends to hide internal functions (e.g. algorithms), which also require resources to implement. There

30-487: Is a "unit of measurement" to express the amount of business functionality an information system (as a product) provides to a user. Function points are used to compute a functional size measurement (FSM) of software. The cost (in dollars or hours) of a single unit is calculated from past projects. There are several recognized standards and/or public specifications for sizing software based on Function Point. 1. ISO Standards The first five standards are implementations of

40-639: Is currently no ISO recognized FSM Method that includes algorithmic complexity in the sizing result. Recently there have been different approaches proposed to deal with this perceived weakness, implemented in several commercial software products. The variations of the Albrecht-based IFPUG method designed to make up for this (and other weaknesses) include: The use of function points in favor of lines of code seek to address several additional issues: Albrecht observed in his research that Function Points were highly correlated to lines of code, which has resulted in

50-399: Is deployed. The IFPUG membership, functional and non-functional assets and certifications, and IFPUG partners assist in fulfilling IFPUG's mission: to be the recognized leader in promoting and encouraging the effective management of application software development and maintenance activities through the use of software product and process metrics. Function point The function point

60-510: The CFPS has a certification extension program. IFPUG offers individual , corporate , countrywide , worldwide, and academic memberships spanning six continents. The annual International Software Measurement & Analysis (ISMA) conferences, access to standards documents, certification support, white papers, the semi-annually produced MetricViews, and educational events represent some of the membership benefits. FPA allows organizations to understand

70-798: The Function Point Counting Practices Manual (CPM), and the SNAP Assessment Practices Manual, the recognized industry standards for functional and non-functional sizing . IFPUG provides testing and certification for the Certified Function Point Specialist (CFPS), the Certified Function Point Practitioner (CFPP), and the Certified SNAP Practitioner (CSP). Generally, certification is for three years although

80-496: The box, without some upfront configuration. Function points were defined in 1979 in Measuring Application Development Productivity by Allan J. Albrecht at IBM . The functional user requirements of the software are identified and each one is categorized into one of five types: outputs, inquiries, inputs, internal files, and external interfaces. Once the function is identified and categorized into

90-437: The functional size of an application prior to its development. As a result, Requests for quotations can be evaluated based on the "richness" of the functionality in addition to its cost and schedule parameters. Several national governments have adopted the use of functional sizing as a prerequisite for bidding on their contracts. Functional sizing can also contribute to determining the level of effort warranted once an application

100-675: The over-arching standard for Functional Size Measurement ISO/IEC 14143. The OMG Automated Function Point (AFP) specification, led by the Consortium for IT Software Quality , provides a standard for automating the Function Point counting according to the guidelines of the International Function Point User Group ( IFPUG ) However, the current implementations of this standard have a limitation in being able to distinguish External Output (EO) from External Inquiries (EQ) out of

#840159