BS ISO/IEC 29881:2010

Foreword
Introduction
1 Scope
2 Normative references
3 Terms and definitions
4 BFC Classes and BFC Types of FiSMA 1.1
5 FiSMA 1.1 Measurement process
6 Counting rules for each BFC type class
7 Functional size measurement unit
8 Calculation of the FiSMA 1.1 functional size of a
   piece of software
9 Measurement reporting
10 Convertibility from FiSMA 1.1 to other FSM Methods
Annex A (informative) - Glossary of terms relevant to
        FiSMA 1.1
Bibliography

Describes the set of definitions, conventions and activities of FiSMA 1.1.

This International Standard specifies the set of definitions, conventions and activities of FiSMA 1.1.

The target audience of this International Standard includes anyone who applies FiSMA 1.1 to measure the functional size of a piece of software. FiSMA 1.1 is intended for use by those persons associated with the acquisition, development, use, support, maintenance, and audit of software. FiSMA 1.1 is based on an assessment of the Functional User Requirements. It measures the functional size of a piece of software from the perspective of the users.

1.1 Field of application for FiSMA 1.1

FiSMA 1.1 is applicable to measure all software in any functional domain.

1.2 Limitations of FiSMA 1.1

FiSMA 1.1 has no limitations related to the type or quality of software to be measured.

1.3 Scope of FSM for FiSMA 1.1

The scope of the Functional Size Measurement for FiSMA 1.1 is determined by the purpose for measuring the software. When using FiSMA 1.1, the set of FUR to be included depends on the purpose of the count and thus may include the FUR for one piece of software or a set of pieces of software. Each piece of software within the scope is measured separately and if more than one piece of software is included within a project, all of the functional sizes may be added together. The scope of the FSM instance is always a subset of the overall user requirements and includes purely the Functional User Requirements, in other words, “what” in terms of services and tasks that the software must perform. The purpose of the FSM determines which FUR will be included in the FSM instance.

NOTE 1 For example, if the purpose of the FSM is to determine the size of the first release of a piece of software, then the size using FiSMA 1.1 will include only the FUR for the first release of the software.

NOTE 2 As another example, if the purpose of the FSM is to determine the supported size of an installed package, only those functional user requirements in the package that are used by the organization will be included in the instance of the FSM.

NOTE 3 FiSMA 1.1 only measures the size of the Functional User Requirements included within the scope as outlined above.