1、BRITISH STANDARD BS ISO/IEC TR 14143-4:2002 Information technology Software measurement Functional size measurement Part 4: Reference model ICS 35.080 BS ISO/IEC TR 14143-4:2002 This British Standard, having been prepared under the direction of the DISC Board, was published under the authority of th
2、e Standards Policy and Strategy Committee on 24 October 2002 BSI 24 October 2002 ISBN 0 580 40635 0 National foreword This British Standard reproduces verbatim ISO/IEC TR 14143-4:2002 and implements it as the UK national standard. The UK participation in its preparation was entrusted to Technical Co
3、mmittee IST/15, Software engineering, which has the responsibility to: A list of organizations represented on this committee can be obtained on request to its secretary. Cross-references The British Standards which implement international publications referred to in this document may be found in the
4、 BSI Catalogue under the section entitled “International Standards Correspondence Index”, or by using the “Search” facility of the BSI Electronic Catalogue or of British Standards Online. This publication does not purport to include all the necessary provisions of a contract. Users are responsible f
5、or its correct application. Compliance with a British Standard does not of itself confer immunity from legal obligations. aid enquirers to understand the text; present to the responsible international/European committee any enquiries on the interpretation, or proposals for change, and keep the UK in
6、terests informed; monitor related international and European developments and promulgate them in the UK. Summary of pages This document comprises a front cover, an inside front cover, the ISO/IEC TR title page, pages ii to vi, pages 1 to 95 and a back cover. The BSI copyright date displayed in this
7、document indicates when the document was last issued. Amendments issued since publication Amd. No. Date Comments Reference number ISO/IEC TR 14143-4:2002(E)TECHNICAL REPORT ISO/IEC TR 14143-4 First edition 2002-08-15 Information technology Software measurement Functional size measurement Part 4: Ref
8、erence model Technologies de linformation Mesurage du logiciel Mesurage de la taille fonctionnelle Partie 4: Modle de rfrence BSISO/IECTR141434:2002BSISO/IECTR141434:2002iiIS/OIET CR -341414:02(20)E I SO/IE 2002 C All irhgts seredevr iiiContents Page 1. SCOPE 1 2. NORMATIVE REFERENCES 1 3. TERMS AND
9、 DEFINITIONS 2 4. ABBREVIATED TERMS 3 5. REFERENCE USER REQUIREMENTS. 3 5.1. General requirements . 3 5.2. Examples 5 6. REFERENCE FSM METHOD 6 6.1. General requirements . 6 6.2. Example Use of Reference FSM Methods. 6 ANNEX A: BUSINESS APPLICATION RUR (NORMATIVE) . 7 A.1 RUR A1: Hotel Accommodation
10、 System (Reservation) 7 A.2 RUR A2: Hotel Accommodation System (Reservations) - Initial Requirement 17 A.3 RUR A3: Hotel Accommodation System (Reservations) Mock-up 19 A.4 RUR A4: Adding automatic name look-up to Hotel Reservation System 19 A.5 RUR A5: Adding automatic name look-up to Hotel Reservat
11、ion System 19 A.6 RUR A6: Adding automatic name look-up to Hotel Reservation System 20 A.7 RUR A7: TRAX Transaction Reporting. 20 A.8 RUR A8: Requirements Paris Bourse Netting 38 ANNEX B: REAL TIME / CONTROL RUR (NORMATIVE) 46 B.1 RUR B1 : Basic Subtraction . 46 B.2 RUR B2: Significantly larger func
12、tion 46 B.3 RUR B3: Slightly larger function. 46 B.4 RUR B4: User requirement of a single display field 47 B.5 RUR B5: User requirement for error messages 47 B.6 RUR B6: User requirement of user maintained error messages 47 B.7 RUR B7: User requirement of an internal function. 47 B.8 RUR B8: Automat
13、ic line switching 48 B.9 RUR B9: Valve Control System . 50 B.10 RUR B10: Gateway System 52 B.11 RUR B11: L-Euchre card game (minimal implementation) 78 B.12 RUR B12: L-Euchre system (Usable system implementation) 90 B.13 RUR B13: Standard Euchre system 90 B.14 RUR B14: Super Euchre system 90 ANNEX C
14、: RUR REFERENCE LIST (INFORMATIVE) 91 C.1 RUR name: Sales/order system 91 C.2 RUR name: Travel arrangements 91 C.3 RUR name: Standing orders support 91 C.4 RUR name: Production Planning and control 91 BSISO/IECTR141434:2002iiiIS/OIET CR -341414:02(20)E vi I SO/IE 2002 C All irhgts seredevrC.5 RUR na
15、me: Marketing Information System.92 C.6 RUR name: Business Analysis92 C.7 RUR name: Accounting System.92 C.8 RUR name: Payroll .92 C.9 RUR name: Purchasing 92 C.10 RUR name: Accounts Payable .93 C.11 RUR name: Human Resources System .93 C.12 RUR name: Revised Human Resources System .93 C.13 RUR name
16、: Traffic Control System 93 C.14 RUR name: Student Selection System.93 C.15 RUR name: Stock Taking System94 C.16 RUR name: Accounts Payable System 94 C.17 RUR name: Enhanced Accounts Payable System 94 C.18 RUR name: Package Routing.94 C.19 RUR name: Simple Library System 94 C.20 RUR name: Library Sy
17、stem II.95 BSISO/IECTR141434:2002ivIS/OIET CR -341414:02(20)E I SO/IE 2002 C All irhgts seredevr vForeword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that
18、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 internati
19、onal 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. The main task of technical committees is to prepare International Standards
20、, but in exceptional circumstances a technical committee may propose the publication of a Technical Report of one of the following types: type 1, when the required support cannot be obtained for the publication of an International Standard, despite repeated efforts; type 2, when the subject is still
21、 under technical development or where for any other reason there is the future but not immediate possibility of an agreement on an International Standard; type 3, when a technical committee has collected data of a different kind than that which is normally published as an International Standard (“st
22、ate of the art”, for example). Technical Reports of types 1 and 2 are subject to review within three years of publication, to decide whether they can be transformed into International Standards. Technical Reports of type 3 do not necessarily have to be reviewed until the data they provide are consid
23、ered to be no longer valid or useful. Technical Reports are drafted in accordance with the rules given in the ISO/IEC Directives, Part 3. Attention is drawn to the possibility that some of the elements of this part of ISO/IEC 14143 may be the subject of patent rights. ISO and IEC shall not be held r
24、esponsible for identifying any or all such patent rights. ISO/IEC TR 14143-4, which is a Technical Report of type 2, was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Software engineering. ISO/IEC 14143 consists of the following parts, under the gene
25、ral title Information technology Software measurement Functional size measurement: Part 1: Definition of concepts Part 2: Conformity evaluation of software size measurement methods to ISO/IEC 14143-1:1998 Part 3: Verification of functional size measurement methods Part 4: Reference model Part 5: Det
26、ermination of functional domains for use with functional size measurement Annexes A and B form a normative part of this part of ISO/IEC 14143. Annex C is for information only. BSISO/IECTR141434:2002vIS/OIET CR -341414:02(20)E iv I SO/IE 2002 C All irhgts seredevrIntroduction The user of an FSM Metho
27、d must establish that the FSM Method is appropriate to quantify the functional size of the software. The conformity to ISO/IEC 14143-1:1998 will be necessary but may not be sufficient. An evaluation process of an FSM Method will have to consider practical evidence of the performance of the FSM Metho
28、d. Such an evaluation may require benchmarking the chosen FSM Method to compare its results for a collection of known Reference User Requirements (RUR) with those obtained from a Reference FSM Method. Part 4 of ISO/IEC 14143 provides standard RUR together with guidance on Reference FSM Methods. Figu
29、re 0.1 shows how these are used to establish reference results. The FSM Method to be evaluated determines functional size results for a collection of appropriate RUR. The same collection of RUR is measured by one or more Reference FSM Methods and these reference results are then compared with the re
30、sults obtained from the FSM Method to be evaluated. FSM Method to be evaluated RUR Collection Reference FSM Method(s) measurement according to FSM Method measurement according to Reference FSM Method(s) results reference results evaluationFigure 0.1: Use of RUR and Reference FSM Methods Clause 5 of
31、this part of ISO/IEC 14143 defines a framework for identifying, classifying and selecting RUR. Annexes A and B provide examples of such RUR in two different domains. While it would be desirable to have an exhaustive set of such RUR, the size of such collection would be prohibitive. Further RUR can b
32、e found in the RUR reference list presented in Annex C. Additional appropriate RUR may be constructed according to the basic guidelines stated in clause 5 RUR. Clause 6 of this part of ISO/IEC 14143 introduces the general requirements for Reference FSM Methods. The reference FSM Methods provide refe
33、rence points, against which other FSM Methods can be compared. BSISO/IECTR141434:2002viINHCETOPER LACTR IS/OIERT C -341414:02(20)EI SO/IE 2002 C All irhgts seredevr 1Information technology Software measurement Functional size measurement Part 4: Reference model 1. Scope Part 4 of ISO/IEC 14143 defin
34、es the reference model (Figure 0.1) to be used when verifying a Functional Size Measurement (FSM) method. The reference model consists of two components: - a classification framework of Reference User Requirements (RUR) which can be sized using an FSM Method. Included are examples of such RUR as wel
35、l as references to further publications of User Requirements (UR) which can be used for RUR, and - guidance on selecting Reference FSM Methods, against which an FSM Method can be compared. The reference model is an input to the evaluation process of an FSM Method. The formulation and execution of ev
36、aluation tests and the interpretation of their results is outside the scope of this Technical Report. The RUR and additional references contained in this Technical Report only represent examples of UR in some domains and situations. Additional RUR and RUR for domains and situations not covered by An
37、nex A, B, or C may be generated with the assistance of the framework described in this Technical Report. The requirements for Reference FSM Methods may assist in selecting Reference FSM Methods. 2. Normative references The following normative documents contain provisions which, through reference in
38、this text, constitute provisions of this part of ISO/IEC 14143. For dated references, subsequent amendments to, or revisions of, any of these publications do not apply. However, parties to agreements based on this part of ISO/IEC 14143 are encouraged to investigate the possibility of applying the mo
39、st recent editions of the normative documents indicated below. For undated references, the latest edition of the normative document referred to applies. Members of ISO and IEC maintain registers of currently valid International Standards. ISO/IEC 14143-1:1998, Information technology Software measure
40、ment Functional size measurement Part 1: Definition of concepts. ISO/IEC 9126:1991, Information technology Software product evaluation Quality characteristics and guidelines for their use. BSISO/IECTR141434:20021IS/OIET CR -341414:02(20)E 2 I SO/IE 2002 C All irhgts seredevr3. Terms and definitions
41、For the purposes of this Technical Report, the terms and definitions given in the normative references and the following apply. Figure 3.1 describes the composition of User Requirements, RUR, and RUR Collection. 3.1 Functional User Requirements (FUR) A sub-set of the User Requirements. The Functiona
42、l User Requirements represent the users practices and procedures that the software must perform to fulfil the users needs. They exclude Quality Requirements and any Technical Requirements. NOTE As defined by ISO/IEC 14143-1:1998. 3.2 Quality Requirements (QR) Any requirements relating to software qu
43、ality as defined in ISO/IEC 9126. NOTE As defined by ISO/IEC 14143-1:1998. Quality Requirements are a subset of the User Requirements. 3.3 Reference FSM Method An FSM Method to be used for comparison reasons when verifying the Functional Size Measurement results. It conforms to the requirements as s
44、pecified in 6.1. 3.4 Reference User Requirements (RUR) A standard set of User Requirements which conforms to the requirements as specified in 5.1.1. NOTE Figure 3.1 shows the relationship of UR and RUR. 3.5 Reference User Requirement Collection (RUR Collection) A subset of RUR which is selected to m
45、atch the purpose in a specific evaluation. The selection requirements are specified in 5.1.2. NOTE Figure 3.1 shows the relationship of RUR and RUR Collection. 3.6 Technical Requirements (TR) Requirements relating to the technology and environment, for the development, maintenance, support and execu
46、tion of the software. NOTE As defined by ISO/IEC 14143-1:1998. Technical Requirements are a subset of the User Requirements. 3.7 User Requirements (UR) The complete description of the set of user needs for the software to be provided. User Requirements include Functional User Requirements, Technical
47、 Requirements and Quality Requirements. BSISO/IECTR141434:20022IS/OIET CR -341414:02(20)E I SO/IE 2002 C All irhgts seredevr 3RUR Collection RUR FUR QR TR Selected for specific evaluation (Sec.5.1.2) Selected for general use (Sec.5.1.1) UR(RUR candidates) RUR RUR RUR RUR FUR QR TRFigure 3.1: Composi
48、tion of User Requirements and RUR (informative) 4. Abbreviated terms FSM Functional Size Measurement FUR Functional User Requirements QR Quality Requirements RUR Reference User Requirements TR Technical Requirements UR User Requirements 5. Reference User Requirements 5.1. General requirements To be
49、acceptable for the evaluation of an FSM Method, the RUR Collection shall consist of RUR complying with 5.1.1 and which are selected according to the rules stated in 5.1.2. BSISO/IECTR141434:20023IS/OIET CR -341414:02(20)E 4 I SO/IE 2002 C All irhgts seredevr5.1.1. RUR requirements Individual RUR shall: a) be documented in such a form that they can be understood by a human user specialised in the area
