1、 Collection of SANS standards in electronic format (PDF) 1. Copyright This standard is available to staff members of companies that have subscribed to the complete collection of SANS standards in accordance with a formal copyright agreement. This document may reside on a CENTRAL FILE SERVER or INTRA
2、NET SYSTEM only. Unless specific permission has been granted, this document MAY NOT be sent or given to staff members from other companies or organizations. Doing so would constitute a VIOLATION of SABS copyright rules. 2. Indemnity The South African Bureau of Standards accepts no liability for any
3、damage whatsoever than may result from the use of this material or the information contain therein, irrespective of the cause and quantum thereof. ISBN 978-0-626-22973-3 SANS 29881:2009Edition 1 ISO/IEC 29881:2008Edition 1 SOUTH AFRICAN NATIONAL STANDARD Information technology Software and systems e
4、ngineering FiSMA 1.1 functional size measurement method This national standard is the identical implementation of ISO/IEC 29881:2008, and is adopted with the permission of the International Organization for Standardization and the International Electrotechnical Commission. Published by SABS Standard
5、s Division 1 Dr Lategan Road Groenkloof Private Bag X191 Pretoria 0001Tel: +27 12 428 7911 Fax: +27 12 344 1568 www.sabs.co.za SABS SANS 29881:2009 Edition 1 ISO/IEC 29881:2008 Edition 1 Table of changes Change No. Date Scope National foreword This South African standard was approved by National Com
6、mittee SABS SC 71C, Information technology Systems and software engineering, in accordance with procedures of the SABS Standards Division, in compliance with annex 3 of the WTO/TBT agreement. This SANS document was published in August 2009. Reference numberISO/IEC 29881:2008(E)ISO/IEC 2008INTERNATIO
7、NAL STANDARD ISO/IEC29881First edition2008-05-15Information technology Software and systems engineering FiSMA 1.1 functional size measurement method Technologies de linformation Logiciel et systmes dingnierie Mthode de mesure de la taille fonctionnelle FiSMA 1.1 SANS 29881:2009This s tandard may onl
8、y be used and printed by approved subscription and freemailing clients of the SABS .ISO/IEC 29881:2008(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are
9、 embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorpor
10、ated. Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a
11、 problem relating to it is found, please inform the Central Secretariat at the address given below. COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2008 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanic
12、al, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.or
13、g Published in Switzerland ii ISO/IEC 2008 All rights reservedSANS 29881:2009This s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .ISO/IEC 29881:2008(E) ISO/IEC 2008 All rights reserved iiiContents Page Foreword iv Introduction v 1 Scope 1 1.1 Fiel
14、d of application for FiSMA 1.11 1.2 Limitations of FiSMA 1.1 .1 1.3 Scope of FSM for FiSMA 1.1 .1 2 Normative references 2 3 Terms and definitions .2 4 BFC Classes and BFC Types of FiSMA 1.1.3 4.1 Interactive end-user navigation and query services (q) 4 4.2 Interactive end-user input services (i).5
15、4.3 Non-interactive end-user output services (o) .6 4.4 Interface services to other applications (t) .6 4.5 Interface services from other applications (f).6 4.6 Data storage services (d) 7 4.7 Algorithmic and manipulation services (a) .8 5 FiSMA 1.1 Measurement process.8 6 Counting rules for each BF
16、C type class .10 6.1 Interactive end-user navigation and query BFCs (q) 10 6.2 Interactive end-user input BFCs (i) .10 6.3 Non-interactive end-user output BFCs (o) .10 6.4 Interface BFCs to other applications (t) .11 6.5 Interface BFCs from other applications (f).11 6.6 Data storage services (d) 11
17、6.7 Algorithmic and manipulation services (a) .12 7 Functional size measurement unit.12 8 Calculation of the FiSMA 1.1 functional size of a piece of software 12 9 Measurement reporting.12 10 Convertibility from FiSMA 1.1 to other FSM Methods13 Annex A Glossary of terms relevant to FiSMA 1.1 14 SANS
18、29881:2009This s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .ISO/IEC 29881:2008(E) iv ISO/IEC 2008 All rights reservedForeword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form
19、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 tec
20、hnical 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. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
21、International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of the joint technical committee is to prepare International Standards. Draft International Standards adopted by the joint technical committee are circulated to national bodies for
22、 voting. Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote. 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
23、any or all such patent rights. ISO/IEC 29881 was prepared by the Finnish Software Measurement Association (FiSMA) and was adopted, under the PAS procedure, by Joint Technical Committee ISO/IEC JTC 1, Information technology, in parallel with its approval by national bodies of ISO and IEC. SANS 29881:
24、2009This s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .ISO/IEC 29881:2008(E) ISO/IEC 2008 All rights reserved vIntroduction Functional size is an essential measure for comparisons of software development activities and development alternatives.
25、Beside its uses in estimating and productivity analysis, functional size has proven to be useful in project planning, tracking, control and contracting. Because Functional Size Measurement (FSM) works best when there is a complete list of functional user requirements and services, it makes scope man
26、agement and change management effective, reliable and relatively easy to understand even to the end-user. The correctness of counting parameters and thus the usefulness of an FSM method can be evaluated based on the correlation between functional size and effort under similar environmental and techn
27、ical circumstances and quality requirements. This kind of evaluation may indicate a need to justify the counting parameters used to derive functional size. FiSMA Functional Size Measurement Method Version 1.1 (referred to throughout this International Standard as simply FiSMA 1.1) is a general, para
28、meterised functional size measurement method for all types of software. It was developed by a working group of Finnish Software Measurement Association (FiSMA), to replace the previous FSM method Experience 2.0 Function Point Analysis (FPA), which has been applied largely in Finland since 1997. More
29、 than 600 software development projects were measured using that method between 1997 and 2003. The current values of constraints used in FiSMA 1.1 are derived from its predecessor Experience 2.0 FPA, and were confirmed statistically to be correct. They may be updated in future releases of the FiSMA
30、FSM Method if the data collection and analysis demonstrate the need to do so. For readers who are unfamiliar with Functional Size Measurement terminology, a review of terms is provided in Annex A, together with definitions and explanations of the most important terms. Results from FiSMA 1.1 and Expe
31、rience 2.0 FPA are largely convertible with each other, if the source data has been collected at the recommended detail level. FiSMA 1.1 is based purely on Functional User Requirements (FUR). User requirements can be thought of as functional what the software does, and non-functional how the softwar
32、e must perform (including quality requirements). For FiSMA 1.1, the Functional User Requirements are the object of measurement. While some FSM methods are process oriented, FiSMA 1.1 is service oriented. Process oriented methods require the identification of all functional processes supported by the
33、 piece of software. In contrast, service oriented methods, such as FiSMA 1.1, require identification of all different services provided by the piece of software. The FiSMA 1.1 relationship chain between users and the developed piece of software involves user needs and services as presented in Figure
34、 1. SANS 29881:2009This s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .ISO/IEC 29881:2008(E) vi ISO/IEC 2008 All rights reservedFigure 1 Links between user and a piece of software While each audience may have their own reasons for size measuremen
35、t, the typical user viewpoint is to estimate the effort for a software project. Other important industry uses of FSM are presented in Figure 2. Figure 2 Common Purposes of Functional Size Measurement SANS 29881:2009This s tandard may only be used and printed by approved subscription and freemailing
36、clients of the SABS .INTERNATIONAL STANDARD ISO/IEC 29881:2008(E) ISO/IEC 2008 All rights reserved 1Information technology Software and systems engineering FiSMA 1.1 functional size measurement method 1 Scope This International Standard specifies the set of definitions, conventions and activities of
37、 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. F
38、iSMA 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
39、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 o
40、n 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. Th
41、e 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
42、. NOTE 1 For example if the purpose for 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 for the FSM is to determine the supported size
43、 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. SANS 29881:2009This
44、 s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .ISO/IEC 29881:2008(E) 2 ISO/IEC 2008 All rights reserved2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only t
45、he edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO/IEC 14143-1:2007, Information technology Software measurement Functional size measurement Part 1: Definition of concepts 3 Terms and definitions For the purposes of
46、 this document, the following terms and definitions apply. Whenever a term is already defined by ISO/IEC, such as “Functional Size Measurement”, the ISO definition has been adopted for this method. 3.1 BFC class defined group of BFC types 3.2 boundary conceptual interface between the software under
47、study and its users ISO/IEC 14143-1:2007, definition 3.3 NOTE The boundary of a piece of software to be sized using FiSMA 1.1 conceptually separates the piece and the environment in which it operates, perceived from the external user perspective. The boundary provides the measurement analyst(s) with
48、 a solid delimiter to distinguish, without ambiguity, what is included inside the measured software from what is part of the measured softwares operating environment. 3.3 data element unique, user recognizable, non-repeated field in a BFC NOTE 1 A data element can be a character string, or a digital
49、 or graphical element in a BFC. NOTE 2 When “data elements” are indicated for a BFC, the number of data elements is always greater than 0. 3.4 data store organized and persistent collection of data and information that allows for its retrieval ISO/IEC 15939:2002 3.5 end-user any person that communicates or interacts with the software at any time 3.6 Functional Services base functional components (BFC) defined by FiSMA 1.1 3.7 operation arithmetic or logical operation performed in an algorithmic and manipulat
