BS ISO/IEC 24570:2018
$215.11
Software engineering. NESMA functional size measurement method. Definitions and counting guidelines for the application of function point analysis
Published By | Publication Date | Number of Pages |
BSI | 2018 | 82 |
1.1 Purpose
This International Standard specifies the set of definitions, rules and guidelines for applying the Nesma Function Point Analysis (FPA) method.
1.2 Conformity
This International Standard is conformant with all mandatory provisions of ISO/IEC 14143‑1:2007.
1.3 Applicability
This International Standard can be applied to all functional domains.
1.4 Focus
The International Standard focuses on how the functional size of an application is determined. The International Standard does not go into any of the aspects that play a role when project budgets are established on the basis of this functional size (e.g. productivity standards and productivity attributes).
The figure below indicates what this International Standard will and will not cover.
Figure 1 Scope of the International Standard
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | National foreword |
7 | Foreword |
8 | Introduction to this Standard |
11 | 1 Scope 1.1 Purpose 1.2 Conformity 1.3 Applicability 1.4 Focus |
12 | 2 Introduction to FPA 2.1 Brief description of FPA 2.1.1 Background, purpose and application of FPA 2.1.2 Rationale behind FPA |
13 | 2.2 Use of FPA: application versus project functional size 2.3 Types of function point analyses 2.4 Function point analyses during a project |
14 | 2.5 Scope of the analysis and boundary of the application to be analyzed 2.6 Users 2.7 Functions and function types |
15 | 2.8 The complexity of a function |
16 | 2.9 The valuing of functions 2.10 The functional size |
17 | 3 Guidelines to perform an FPA 3.1 Step-by-step plan to perform an FPA 3.2 Types of function point analyses and their accuracy |
18 | 3.2.1 Indicative function point analysis |
19 | 3.2.2 High level function point analysis 3.2.3 Detailed function point analysis |
20 | 3.3 Role of the quality of the specifications 3.4 FPA during a project |
21 | 3.5 Determining the functional size of an application 3.5.1 Determining the application boundary |
22 | 3.5.2 Functional size of new applications 3.5.3 Functional size of enhanced applications 3.5.4 Functional size of re-built applications |
23 | 3.6 Determining the functional size of a project 3.6.1 Determining the scope of a project function point analysis |
24 | 3.6.2 Functional size of development projects |
25 | 3.6.3 Functional size of enhancement projects 3.6.4 The project function point analysis during the replacement of an application |
26 | 3.7 Definition of functional change 3.7.1 General 3.7.2 Modification of a transactional function 3.7.3 Modification of a data function 3.7.4 Modification of a DET |
27 | 3.8 FPA in specific situations 3.8.1 Analyzing on the basis of traditional design 3.8.2 Analyzing packaged software |
29 | 3.8.3 Analyzing screens or windows |
30 | 3.8.4 Analyzing when prototyping |
31 | 3.9 Illustration: FPA and the application life cycle 3.9.1 FPA during the requirements phase |
32 | 3.9.2 FPA during the analysis phase |
33 | 3.9.3 FPA during the functional design phase |
34 | 3.9.4 FPA during the construction phase 3.9.5 FPA during the implementation phase 3.9.6 FPA during the operation and maintenance phase |
35 | 4 General FPA guidelines 4.1 Analyzing from a logical perspective 4.2 Applying the rules 4.3 No double counting 4.4 Built functionality, non-requested functionality |
36 | 4.5 Production of re-usable code 4.6 Re-use of existing code 4.7 Screens, windows and reports 4.8 Input and output records 4.9 Security and authorization |
37 | 4.10 Operating systems and utilities 4.11 Report generators and query facilities 4.12 Graphs 4.13 Help facilities |
38 | 4.14 Messages 4.15 Menu structures 4.16 List functions 4.17 Browse and scroll functions |
39 | 4.18 Cleanup functions 4.19 Completeness check on the function point analysis 4.20 FPA tables |
40 | 4.21 Deriving logical files (data functions) from a normalized data model 4.21.1 Introduction 4.21.2 Denormalization rules |
41 | 4.21.3 The nature of the relationship (cardinality and optionality) 4.21.4 Independence or dependence of an entity type |
43 | 4.21.5 Conversion table: from normalized entity types to logical files 4.22 Shared use of data |
46 | 4.23 Generic rule for counting data element types |
47 | 5 Internal Logical Files 5.1 Definition of an internal logical file |
48 | 5.2 Identifying internal logical files |
49 | 5.3 Determining the complexity of internal logical files |
50 | 6 External Logical Files 6.1 Definition of an external logical file |
51 | 6.2 Identifying external logical files |
53 | 6.3 Determining the complexity of external logical files 7 External Inputs |
54 | 7.1 Definition of an external input |
55 | 7.2 Identifying external inputs |
56 | 7.3 Determining the complexity of external inputs |
58 | 8 External Outputs 8.1 Definition of an external output |
60 | 8.2 Identifying external outputs |
62 | 8.3 Determining the complexity of external outputs |
63 | 9 External Inquiries |
64 | 9.1 Definition of an external inquiry |
65 | 9.2 Identifying external inquiries |
66 | 9.3 Determining the complexity of external inquiries |
68 | Annex A (normative) Summary features for valuing function types |
73 | Annex B (normative) Function Point Analysis glossary |