Information technology — Object Management Group Automated Function Points (AFP), 1.0

1.1 Purpose This International Standard defines a method for automating the counting of Function Points that is generally consistent with the Function Point Counting Practices Manual, Release 4.3.1 (IFPUG CPM) produced by the International Function Point Users Group (IFPUG). Guidelines in this International Standard may differ from those in the IFPUG CPM at points where subjective judgments have to be replaced by the rules needed for automation. The IFPUG CPM was selected as the anchor for this International Standard because it is the most widely used functional measurement specification with a large supporting infrastructure maintained by a professional organization. 1.2 Applicability This International Standard is applicable to the functional sizing of transaction-oriented software applications, and in particular those with data persistency. To be consistent with the IFPUG CPM, the International Standard provides details on the support of applications using relational databases. However, the International Standard can be used and extended for any type of transactional application with data persistency. 1.3 Limitations This International Standard does not address the sizing of enhancements to an application or maintained functionality (often called Enhancement Function Points). Extensions of the automated counting methods described in this International Standard such as Automated Enhancement Function Points will be addressed in future addendums to this International Standard. This International Standard does not address sizing for the non-functional components of a software application. Non-functional components (as defined by IFPUG) include: — Structural Quality Constraints Reliability, Security, Performance Efficiency, Maintainability, etc. — Organizational Constraints locations for operations, target hardware, compliance to standards, etc. — Environmental Constraints interoperability, security, privacy, safety, etc. — Implementation Constraints development language, delivery schedule, etc.

Titre manque

General Information

Status
Published
Publication Date
05-May-2019
Current Stage
9060 - Close of review
Start Date
02-Dec-2029
Ref Project

Buy Standard

Standard
ISO/IEC 19515:2019 - Information technology — Object Management Group Automated Function Points (AFP), 1.0 Released:5/6/2019
English language
28 pages
sale 15% off
Preview
sale 15% off
Preview
Standard
ISO/IEC 19515:2019 - Information technology -- Object Management Group Automated Function Points (AFP), 1.0
English language
28 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


INTERNATIONAL ISO/IEC
STANDARD 19515
First edition
2019-05
Information technology — Object
Management Group Automated
Function Points (AFP), 1.0
Reference number
©
ISO/IEC 2019
© ISO/IEC 2019
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting
on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address
below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO/IEC 2019 – All rights reserved

Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
1.1 Purpose . 1
1.2 Applicability . 1
1.3 Limitations . 1
2 Conformance and Compliance . 1
2.1 Conformance . 1
2.2 Compliance . 2
2.3 Consistency with IFPUG CPM . 2
3 References . 3
3.1 Normative . 3
3.2 Non-normative . 3
4 Terms and Definitions . 3
5 Symbols (and abbreviated terms) . 5
6 Additional Information . 5
6.1 Overview of Function Points . 5
6.2 Function Point Usage Scenarios . 6
6.3 Inputs to Automated Function Point Counting . 7
6.4 Outline of the Function Point Counting Process . 7
6.5 The Application Model . 8
6.5.1 The Application Model Elements . 8
6.5.2 Detection of Data Functions . 9
6.5.3 Detection of Transactional Functions .14
6.5.4 Detection of Internal Versus External Logical Files .15
7 Determine Functional Size (Normative) .17
7.1 Entering Application Model Elements into Functional Sizing.17
7.1.1 Representation of the Application Model in KDM .17
7.1.2 Translating KDM Application Model Elements into SMM Inputs .18
7.2 Determine Data Function Size .18
7.3 Determine Transactional Function Size .19
7.4 Determine Function Point Size.22
7.5 Output Generation .22
7.6 Structured Metrics Meta-Model (SMM) Representation .23
7.6.1 Computing Automated Function Point Size .23
7.6.2 Computing External Output Size .24
7.6.3 Computing External Input Size .25
7.6.4 Computing Internal Logical File Size and External Interface File Size .26
8 References .27
© ISO/IEC 2019 – All rights reserved iii

Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that
are members of ISO or IEC participate in the development of International Standards through
technical committees established by the respective organization to deal with particular fields of
technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other
international organizations, governmental and non-governmental, in liaison with ISO and IEC, also
take part in the work.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the
different types of document should be noted (see www .iso .org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject
of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent
rights. Details of any patent rights identified during the development of the document will be in the
Introduction and/or on the ISO list of patent declarations received (see www .iso .org/patents) or the IEC
list of patent declarations received (see http: //patents .iec .ch).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to the
World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see www .iso
.org/iso/foreword .html.
This document was prepared by the Object Management Group (OMG) (as the OMG specification for
Automated Function Points (AFP), v1.0) and drafted in accordance with its editorial rules. It was
adopted, under the JTC 1 PAS procedure, by Joint Technical Committee ISO/IEC JTC 1, Information
technology.
This document is related to:
— ITU-T Recommendation X.902 (1995) | ISO/IEC 10746-2:1995, Information Technology — Open
Distributed Processing — Reference Model: Foundations
— ITU-T Recommendation X.903 (1995) | ISO/IEC 10746-3:1995, Information Technology — Open
Distributed Processing — Reference Model: Architecture
— ITU-T Recommendation X.920 (1997) | ISO/IEC 14750:1997, Information Technology — Open
Distributed Processing — Interface Definition Language
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www .iso .org/members .html.
iv © ISO/IEC 2019 – All rights reserved

Introduction
The rapid growth of distributed processing has led to a need for a coordinating framework for this
standardization and ITU-T Recommendations X.901-904 | ISO/IEC 10746, the Reference Model of Open
Distributed Processing (RM-ODP) provides such a framework. It defines an architecture within which
support of distribution, interoperability and portability can be integrated.
RM-ODP Part 2 (ISO/IEC 10746-2) defines the foundational concepts and modeling framework for
describing distributed systems. The scopes and objectives of the RM-ODP Part 2 and the UML, while
related, are not the same and, in a number of cases, the RM-ODP Part 2 and the UML specification use the
same term for concepts which are related but not identical (e.g., interface). Nevertheless, a specification
using the Part 2 modeling concepts can be expressed using UML with appropriate extensions (using
stereotypes, tags, and constraints).
RM-ODP Part 3 (ISO/IEC 10746-3) specifies a generic architecture of open distributed systems,
expressed using the foundational concepts and framework defined in Part 2. Given the relation between
UML as a modeling language and Part 3 of the RM-ODP standard, it is easy to show that UML is suitable
as a notation for the individual viewpoint specifications defined by the RM-ODP.
This International Standard defines a method for automating the counting of Function Points that is
generally consistent with the Function Point Counting Practices Manual, Release 4.3.1 (IFPUG CPM)
produced by the International Function Point Users Group (IFPUG). Guidelines in this specification may
differ from those in the IFPUG CPM at points where subjective judgments have to be replaced by the
rules needed for automation. The IFPUG CPM was selected as the anchor for this specification because
it is the most widely used functional measurement specification with a large supporting infrastructure
maintained by a professional organization.
© ISO/IEC 2019 – All rights reserved v

INTERNATIONAL STANDARD ISO/IEC 19515:2019(E)
Information technology — Object Management Group
Automated Function Points (AFP), 1.0
1 Scope
1.1 Purpose
This International Standard defines a method for automating the counting of Function Points that is
generally consistent with the Function Point Counting Practices Manual, Release 4.3.1 (IFPUG CPM)
produced by the International Function Point Users Group (IFPUG). Guidelines in this International
Standard may differ from those in the IFPUG CPM at points where subjective judgments have to be
replaced by the rules needed for automation. The IFPUG CPM was selected as the anchor for this
International Standard because it is the most widely used functional measurement specification with a
large supporting infrastructure maintained by a professional organization.
1.2 Applicability
This International Standard is applicable to the functional sizing of transaction-oriented software
applications, and in particular those with data persistency. To be consistent with the IFPUG CPM, the
International Standard provides details on the support of applications using relational databases.
However, the International Standard can be used and extended for any type of transactional application
with data persistency.
1.3 Limitations
This International Standard does not address the sizing of enhancements to an application or
maintained functionality (often called Enhancement Function Points). Extensions of the automated
counting methods described in this International Standard such as Automated Enhancement Function
Points will be addressed in future addendums to this International Standard. This International
Standard does not address sizing for the non-fun
...


INTERNATIONAL ISO/IEC
STANDARD 19515
First edition
2019-05
Information technology — Object
Management Group Automated
Function Points (AFP), 1.0
Reference number
©
ISO/IEC 2019
© ISO/IEC 2019
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting
on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address
below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO/IEC 2019 – All rights reserved

Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
1.1 Purpose . 1
1.2 Applicability . 1
1.3 Limitations . 1
2 Conformance and Compliance . 1
2.1 Conformance . 1
2.2 Compliance . 2
2.3 Consistency with IFPUG CPM . 2
3 References . 3
3.1 Normative . 3
3.2 Non-normative . 3
4 Terms and Definitions . 3
5 Symbols (and abbreviated terms) . 5
6 Additional Information . 5
6.1 Overview of Function Points . 5
6.2 Function Point Usage Scenarios . 6
6.3 Inputs to Automated Function Point Counting . 7
6.4 Outline of the Function Point Counting Process . 7
6.5 The Application Model . 8
6.5.1 The Application Model Elements . 8
6.5.2 Detection of Data Functions . 9
6.5.3 Detection of Transactional Functions .14
6.5.4 Detection of Internal Versus External Logical Files .15
7 Determine Functional Size (Normative) .17
7.1 Entering Application Model Elements into Functional Sizing.17
7.1.1 Representation of the Application Model in KDM .17
7.1.2 Translating KDM Application Model Elements into SMM Inputs .18
7.2 Determine Data Function Size .18
7.3 Determine Transactional Function Size .19
7.4 Determine Function Point Size.22
7.5 Output Generation .22
7.6 Structured Metrics Meta-Model (SMM) Representation .23
7.6.1 Computing Automated Function Point Size .23
7.6.2 Computing External Output Size .24
7.6.3 Computing External Input Size .25
7.6.4 Computing Internal Logical File Size and External Interface File Size .26
8 References .27
© ISO/IEC 2019 – All rights reserved iii

Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that
are members of ISO or IEC participate in the development of International Standards through
technical committees established by the respective organization to deal with particular fields of
technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other
international organizations, governmental and non-governmental, in liaison with ISO and IEC, also
take part in the work.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the
different types of document should be noted (see www .iso .org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject
of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent
rights. Details of any patent rights identified during the development of the document will be in the
Introduction and/or on the ISO list of patent declarations received (see www .iso .org/patents) or the IEC
list of patent declarations received (see http: //patents .iec .ch).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to the
World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see www .iso
.org/iso/foreword .html.
This document was prepared by the Object Management Group (OMG) (as the OMG specification for
Automated Function Points (AFP), v1.0) and drafted in accordance with its editorial rules. It was
adopted, under the JTC 1 PAS procedure, by Joint Technical Committee ISO/IEC JTC 1, Information
technology.
This document is related to:
— ITU-T Recommendation X.902 (1995) | ISO/IEC 10746-2:1995, Information Technology — Open
Distributed Processing — Reference Model: Foundations
— ITU-T Recommendation X.903 (1995) | ISO/IEC 10746-3:1995, Information Technology — Open
Distributed Processing — Reference Model: Architecture
— ITU-T Recommendation X.920 (1997) | ISO/IEC 14750:1997, Information Technology — Open
Distributed Processing — Interface Definition Language
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www .iso .org/members .html.
iv © ISO/IEC 2019 – All rights reserved

Introduction
The rapid growth of distributed processing has led to a need for a coordinating framework for this
standardization and ITU-T Recommendations X.901-904 | ISO/IEC 10746, the Reference Model of Open
Distributed Processing (RM-ODP) provides such a framework. It defines an architecture within which
support of distribution, interoperability and portability can be integrated.
RM-ODP Part 2 (ISO/IEC 10746-2) defines the foundational concepts and modeling framework for
describing distributed systems. The scopes and objectives of the RM-ODP Part 2 and the UML, while
related, are not the same and, in a number of cases, the RM-ODP Part 2 and the UML specification use the
same term for concepts which are related but not identical (e.g., interface). Nevertheless, a specification
using the Part 2 modeling concepts can be expressed using UML with appropriate extensions (using
stereotypes, tags, and constraints).
RM-ODP Part 3 (ISO/IEC 10746-3) specifies a generic architecture of open distributed systems,
expressed using the foundational concepts and framework defined in Part 2. Given the relation between
UML as a modeling language and Part 3 of the RM-ODP standard, it is easy to show that UML is suitable
as a notation for the individual viewpoint specifications defined by the RM-ODP.
This International Standard defines a method for automating the counting of Function Points that is
generally consistent with the Function Point Counting Practices Manual, Release 4.3.1 (IFPUG CPM)
produced by the International Function Point Users Group (IFPUG). Guidelines in this specification may
differ from those in the IFPUG CPM at points where subjective judgments have to be replaced by the
rules needed for automation. The IFPUG CPM was selected as the anchor for this specification because
it is the most widely used functional measurement specification with a large supporting infrastructure
maintained by a professional organization.
© ISO/IEC 2019 – All rights reserved v

INTERNATIONAL STANDARD ISO/IEC 19515:2019(E)
Information technology — Object Management Group
Automated Function Points (AFP), 1.0
1 Scope
1.1 Purpose
This International Standard defines a method for automating the counting of Function Points that is
generally consistent with the Function Point Counting Practices Manual, Release 4.3.1 (IFPUG CPM)
produced by the International Function Point Users Group (IFPUG). Guidelines in this International
Standard may differ from those in the IFPUG CPM at points where subjective judgments have to be
replaced by the rules needed for automation. The IFPUG CPM was selected as the anchor for this
International Standard because it is the most widely used functional measurement specification with a
large supporting infrastructure maintained by a professional organization.
1.2 Applicability
This International Standard is applicable to the functional sizing of transaction-oriented software
applications, and in particular those with data persistency. To be consistent with the IFPUG CPM, the
International Standard provides details on the support of applications using relational databases.
However, the International Standard can be used and extended for any type of transactional application
with data persistency.
1.3 Limitations
This International Standard does not address the sizing of enhancements to an application or
maintained functionality (often called Enhancement Function Points). Extensions of the automated
counting methods described in this International Standard such as Automated Enhancement Function
Points will be addressed in future addendums to this International Standard. This International
Standard does not address sizing for the non-fun
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.