ISO IEC 29881-2010 Information technology - Systems and software engineering - FiSMA 1 1 functional size measurement method《信息技术 系统与软件工程 FiSMA 1 1功能规模测量方法》.pdf

《ISO IEC 29881-2010 Information technology - Systems and software engineering - FiSMA 1 1 functional size measurement method《信息技术 系统与软件工程 FiSMA 1 1功能规模测量方法》.pdf》由会员分享，可在线阅读，更多相关《ISO IEC 29881-2010 Information technology - Systems and software engineering - FiSMA 1 1 functional size measurement method《信息技术 系统与软件工程 FiSMA 1 1功能规模测量方法》.pdf（24页珍藏版）》请在麦多课文档分享上搜索。

1、 Reference number ISO/IEC 29881:2010(E) ISO/IEC 2010INTERNATIONAL STANDARD ISO/IEC 29881 Second edition 2010-08-15 Information technology Systems and software engineering FiSMA 1.1 functional size measurement method Technologies de linformation Ingnierie des systmes et du logiciel Mthode de mesure d

2、e la taille fonctionnelle FiSMA 1.1 ISO/IEC 29881:2010(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 embedded are licensed to and installed on the c

3、omputer 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 Incorporated. Details of the software products used to c

4、reate 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 problem relating to it is found, please inform

5、the Central Secretariat at the address given below. COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2010 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 mechanical, including photocopying and microfilm, withou

6、t 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.org Published in Switzerland ii ISO/IEC 2010 All r

7、ights reservedISO/IEC 29881:2010(E) ISO/IEC 2010 All rights reserved iiiContents Page Foreword iv Introduction.v 1 Scope1 1.1 Field 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 references1 3 Terms and definitions .2 4 BFC Classes and BFC T

8、ypes 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 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 se

9、rvices (d)7 4.7 Algorithmic and manipulation services (a).8 5 FiSMA 1.1 Measurement process 8 6 Counting rules for each BFC 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).11 6.4 Interface

10、 BFCs to other applications (t) .11 6.5 Interface BFCs from other applications (f) 11 6.6 Data storage services (d)12 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 software12 9 Measurement reporting

11、.13 10 Convertibility from FiSMA 1.1 to other FSM Methods .13 Annex A (informative) Glossary of terms relevant to FiSMA 1.114 Bibliography16 ISO/IEC 29881:2010(E) iv ISO/IEC 2010 All rights reservedForeword ISO (the International Organization for Standardization) and IEC (the International Electrote

12、chnical 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

13、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. In the field of information technology, ISO and IEC have established a joint technical c

14、ommittee, ISO/IEC JTC 1. 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 circulat

15、ed to national bodies for 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 res

16、ponsible for identifying any or all such patent rights. ISO/IEC 29881 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Software and systems engineering. This second edition cancels and replaces the first edition (ISO/IEC 29881:2008), of which it con

17、stitutes a minor revision. ISO/IEC 29881:2010(E) ISO/IEC 2010 All rights reserved vIntroduction Functional size is an essential measure for comparisons of software development activities and development alternatives. Besides its uses in estimating and productivity analysis, functional size has prove

18、n 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 management and change management effective, reliable and relatively easy to understan

19、d 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 technical circumstances and quality requirements. This kind of evaluation may indicate

20、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, parameterized FSM method for all types of software. It was developed by a working grou

21、p 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 than 600 software development projects were measured using that method between 1997 and 2003. The current

22、 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 FSM Method if the data collection and analysis demonstrate the need to do so. For readers who are unfamili

23、ar with FSM 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 Experience 2.0 FPA are largely convertible with each other, if the source data has been collected at the recommended detail level. FiS

24、MA 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 software must perform, including quality requirements). For FiSMA 1.1, the Functional User Requirements are the object of measurement.

25、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 piece of software. In contrast, service-oriented methods, such as FiSMA 1.1, require identification of all different services p

26、rovided 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 1. ISO/IEC 29881:2010(E) vi ISO/IEC 2010 All rights reservedFigure 1 Links between user and a piece of software While each audi

27、ence may have its own reasons for size measurement, 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 INTERNATIONAL STANDARD ISO/IEC 29881:2010(E) ISO/IE

28、C 2010 All rights reserved 1Information technology Systems and software engineering FiSMA 1.1 functional size measurement method 1 Scope This International Standard specifies the set of definitions, conventions and activities of FiSMA 1.1. The target audience of this International Standard includes

29、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.

30、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 softw

31、are 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

32、 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 requir

33、ements 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

34、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

35、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. 2 Normative references The following referenced documents are indispensable for the applicat

36、ion of this document. For dated references, only the 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 co

37、ncepts ISO/IEC 29881:2010(E) 2 ISO/IEC 2010 All rights reserved3 Terms and definitions For the purposes of 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 meth

38、od. NOTE For users who are unfamiliar with Functional Size Measurement terminology, and to increase the usability of this International Standard, a review of terms is provided in Annex A, together with definitions and explanations of the most important terms. 3.1 BFC class defined group of BFC types

39、 3.2 boundary conceptual interface between the software under 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 pers

40、pective. The boundary provides the measurement analyst(s) with 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

41、 NOTE 1 A data element can be a character string, or a digital or graphical element in a BFC. NOTE 2 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:2007 3.5 end-user any pers

42、on 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 manipulation BFC NOTE The number of operations is always greater than 0. 3.8 rea

43、ding reference data storage entity or record, or interface record from another software or system containing data retrieved in a BFC NOTE The number of reading references is greater than or equal to 0 for all BFC types where it is applicable. ISO/IEC 29881:2010(E) ISO/IEC 2010 All rights reserved 33

44、.9 user any person or thing that communicates or interacts with the software at any time 3.10 writing reference data storage entity or other record, or interface record to another software or system to which data is written in a BFC NOTE The number of writing references is greater than 0 with all BF

45、C types where it is applicable. 4 BFC Classes and BFC Types of FiSMA 1.1 FiSMA 1.1 identifies seven distinct BFC classes: Interactive end-user navigation and query services (q) Interactive end-user input services (i) Non-interactive end-user output services (o) Interface services to other applicatio

46、ns (t) Interface services from other applications (f) Data storage services (d) Algorithmic and manipulation services (a) Each BFC class of FiSMA 1.1 further decomposes into several BFC types. All together there are 28 BFC types. Figure 3 shows the relationships between the BFC classes and their com

47、ponent BFC types. Each BFC Class is explained in the clauses that follow. NOTE For ease of presentation, the following short form conventions have been used: Each of the seven BFC classes is denoted by a single alphabetic character as shown in Figure 3; Each BFC type is prefixed by its BFC class alp

48、habetic character and an integer number that has been assigned to it as denoted in Figure 3. ISO/IEC 29881:2010(E) 4 ISO/IEC 2010 All rights reservedFunctional Services of FiSMA 1.1 Interactive end user navigation and query services (q) Interactive end user input services (i) Non-interactive end use

49、r output services (o) Data storage services (d) Interface services from other applications (f) Interface services to other applications (t) Algorithmic and manipulations services (a) Messages in f1 Log-in, log-out functions q2 Function designator q1 Function List q3 Selection lists q4 Data inquiries q5 Generation indicators q6 Browsing lists q7 1-functional i1 2-functional i2 3-functional i3 Forms o1 Reports o2 Emails or text messages o3 Monitor screens o4 Entities/cl