1、BRITISH STANDARD Information Technology - Categorization of software ICs 35.080 BS ISO/IEC TR 12182:1998 NO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPRIGH LAW BS ISO/iEC TR 12182:1998 been prepared under the published under the authority of the Standards Committee and comes into effec
2、t on 15 October 1999 I direction of the DISC Board, was Amd. No. O BSI 10-1999 ISBN O 580 35200 5 National foreword Date Comments This British Standard reproduces verbahn ISO/IEC TR 121821998 and implements it as the UK national standard The UK participation in its preparation was entrusted to Techn
3、ical Committee IST/15, SoMare Engineering, which has the responsibility to: - aid enquirers to understand the text, - present to the responsible internalionalEuropean committee any enquiries on the interpretation, or proposais for change, and keep the UK interests informed - monitor related internat
4、ional and European developments and promulgate them in the UK A list of organizations represented on this committee can be obtained on request to its secretaqy. Cross-references The British Standards which implement international publications referred to in this document may be found in the BSI Stan
5、dards Catalogue under the section entitled “International Standards Correspondence Index”, or by using the “Find” facility of the BSI Standards Electronic Catalogue. A British Standard does not purport to include all the necessary provisions of a contract. Users of British Standards are responsible
6、for their correct application. Compliance with a British Standard does not of itself confer immunity from legal obligations. Summary of pages This document comprises a front cover, an inside front cover, the ISO/IEC title page, pages ii to v, a blank page, pages 1 to 14, an inside back cover and a b
7、ack cover. The BSI copyright notice displayed in this document indicates when the document was last issued. BS ISOAEC TR 12182:1998 TECHNICAL REPORT ISOAEC TR 12182 First edition 1998-11-01 Information technology - Categorization of software Technologies de linformation - Classement des logiciels Re
8、ference number ISOAEC TR 12182:1998(E) STD*BSI BS ISO/IEC TR LZLdZ-ENGL 1998 lb2qbb7 U79b870 b42 9 BS ISOAEC TR 12182:1998 Contents 1 2 3 4 5 6 6.1 6.2 7 7.1 7.2 7.3 7.4 7.5 7.6 7.7 7.8 7.9 7.1 O 7.1 1 7.12 7.1 3 7.14 Scope . 1 Conformance 1 Normative references . 2 Terms and definitions 2 Symbols (
9、and abbreviated terms) 2 Concept of a categorization of software 2 I Structure of views 3 Selection of views and categories 3 Scheme of categorization 4 Software function . 4 Application area of information system . 4 Operation mode 5 Scale of software 5 Data representation 6 Primary language . 6 So
10、ftware criticality . 6 User class . 7 Software stability 7 Software product availability 7 Usage of software data 7 Required performance . 8 Security requirement . 8 Reliability requirement . 9 . Descriptors: data processing. data processing equipment. computers. computer software. categories. descr
11、iption . ii 7.1 5 7.1 6 8 8.1 8.2 8.3 8.4 STD=BSI BS ISO/IEC TR 12182-ENGL 1998 = 1b2Fbb9 079b873 529 BS ISOEC TR 12182:1998 Computer system and environment . . . . 10 Computer resource requirement . . , . 1 O Application of the scheme . , 10 Application to scope of standards . . “. 10 Application t
12、o standards . . , 11 Application to software packages . . . , 11 Example Categorization of: Word Processing Package . 12 iii STD-BSI BS ISOiIEC TR 12182-ENGL 1778 Lb2qbbS 077b872 qb5 BS ISOAEC TR 12182:1998 Foreword IS0 (the International Organization for Standardization) and IEC (the International
13、Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of IS0 or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of t
14、echnical activity. IS0 and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with IS0 and IEC, also take part in the work. In the field of information technology, IS0 and IEC have established a joint te
15、chnical committee, ISOAEC JTC 1. The main task of technical committees is to prepare International Standards, 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
16、 for the publication of an International Standard, despite repeated efforts; - type 2, when the subject is still 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 commit
17、tee has collected data of a different kind from that which is normally published as an International Standard (“state 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 St
18、andards. Technical Reports of type 3 do not necessarily have to be reviewed until the data they provide are considered to be no longer valid or useful. ISOAECTR 12182, which is a Technical Report of type2, was prepared by Joint Technical Committee ISOAEC JTC 1, Infomation technology, Subcommittee SC
19、 7, Software engineering. iv Introduction This Technical Report has several purposes which are directed towards its various intended audiences: the software engineering community; the users of soitware engineering standards, specifically those developed by ISO/IEC JTC 1iSC 7; and developers of softw
20、are engineering standards, primarily SC 7. For the software engineering community, this document will identify the types of software to which particular software engineering standards apply. This will help the software engineer to establish the risk planning criteria, the adequate life-cycle model t
21、o apply, the specific effort required for specific lifecycle phases, and the tools needed. For the users and developers of software engineering Standards, it will establish a framework for discussing and identifying candidate software engineering standards based on the software categorization scheme
22、 and for using the scheme to relate software and software engineering standards. Specifically for SC 7, this Technical Report will provide an aid for positioning software engineering standards and work items within the structure of SC 7 and it is intended that new projects, working drafts, committee
23、 drafts, and drait intenrational standards will identify the target categorization(s) relevant to the area of application. With respect to the latter. it is understood that, in some documents, only part of this Technical Report will address the specified categorization. Examples are given to clarify
24、 the categorization scheme for software. For the standards developer, this Technical Report helps position existing standards and work items. For the software engineer, it provides a high level scheme with which to locate existing standards. 111 addition to the normal introductory clauses, this Tech
25、nical Report provides a Framewoik for Categorization of software, a Scheme of Categorization, and Examples of Application of the Standard. V .- BS ISOAEC TR 12182:1998 Information technology - Categorization of software 1 scope The scope of this Technical Report is the categories of software (includ
26、ing relevant software development products and data) that are produced by software engineering processes. It describes a categorization scheme for software that encompasses different points of view and significant characteristics and attributes that describe and define software and software categori
27、es. 1.1 Field of application The field of application of the Categorization of Software includes software engineering and its associated standards, software, data, and methodologies. 1.2 Audience and purpose This Technical Report is primarily directed towards several audiences: the software engineer
28、ing community; the users of software engineering standards, specifically those developed by ISOIIEC JTC 1ISC 7; and developers of software engineering standards, primarily SC 7. The purpose or usage of the Categorization of Software is the identifying of software categories, identifying of applicabl
29、e software engineering standards for software, and determining the relationship of software tasks, processes, or products to software engineering standards. The use of the Categorization of Software is defined as the generation of a justifiable entry for each of the views specified in Clause 7 for t
30、he given software product or in a mapping of a software engineering standard. In some circumstances a null entry is appropriate. It often occurs that the software engineering processes, and the products of those processes, apply to the procurement or development of certain kinds of software. For exa
31、mple, IS0 6592 applies to large application systems and IS0 91 27 applies to packaged software. This Technical Report provides a categorization scheme to assist in (1) the understanding of the area of application of a standard or software, (2) the identification and selection of standards applicable
32、 to a software application, and (3) the positioning of new standards. 1.3 Limitations Since software engineering is a fast changing field, the categorization outlined herein can only be a conceptual scheme. Users, therefore, should use judgement when applying it to applications. The categorization s
33、cheme in this Technical Report is empirical in nature. Its formulation is not based on well-defined user needs. The scheme has not been validated in field triais. 2 Conformance Vot applicable. 1 BS ISODEC TR 12182:1998 3 Normative references No normative references are made within the Categorization
34、 of Software. 4 Terms and definitions This clause provides definitions for terms used in this Technical Report. It does not define the concepts which are explained in the body of the document. It does not define terms which are not specific to the subject matter and are used in accordance with their
35、 ordinary English language usage. For the purposes of this Technical Report, the following terms and definitions apply. 4.1 categorization scheme an orderly combination of views and categories related to software 4.2 view a set of related categories 4.3 category a specifically defined division or gr
36、ouping of software based upon one or more attributes or characteristics 5 Symbols (and abbreviated terms) Not applicable. 6 The concept of a categorization of software is diagrammatically represented by Figure 1 Concept of a categorization of software Figure 1 - Categorization of software 2 As is im
37、plied by the figure, the categorization of software is composed of a number of views of software and each view contains categories relevant to the view. The various views are discussed in Clause 7. The selection of categories is at the discretion of the user. It should be noted that it may be approp
38、riate that a category exists in more than one view and, in several instances, the domain of one category overlaps that of another. 6.1 Structure of views The categorization scheme consists of 16 views. In use, views of software may be grouped into collections of views such as: Internal 0 Operation m
39、ode (7.3) 0 Scale of software (7.4) 0 Software stability (7.9) Functionality 0 Software function (7.1) o Security requirement (7.1 3) Reliability requirement (7.14) 0 Required performance (7.12) 0 Primary language (7.6) Environment O Application area of information system (7.2) 0 Computer system and
40、 environment (7.15) O User class (7.8) 0 Computer resource requirement (7.16) Software criticality (7.7) Software product availability (7.10) Data 0 Data representation (7.5) Usage of software data (7.11) 6.2 Selection of views and categories For any given instance, such as when the categorization s
41、cheme is applied to other software engineering standards, the use of all views may not be required. In these cases, one view or a selected set of views with 3 specific categories will be sufficient to characterize the software. Applications for which subsets of views may be desirable include charact
42、erization of software with respect to specific software engineering standards, selection of appropriate software engineering standards, selection of methods, definition of life cycle, determination of document structure, and quality rating. When applying the characterization scheme to applications f
43、or which subsets of views are desirable, all relevant views and related categories should be used. For example, if software is to be characterized with respect to its environment, the set of views contained in the Environment subset presented in 6.1 would be appropriate. Depending upon the particula
44、r circumstances of the application, it may be necessary to also include additional views such as security requirement or reliability requirement. In some applications of the categorization scheme, characterization with respect to a single primary view may be sufficient. For example, software critica
45、lity may be the primary view for quality assurance standards. For other uses of the categorization scheme, several views with specific categories can be combined to represent more specific characteristics of software. For example, software function and user class may be used to determine the documen
46、tation structure. i7 Scheme of categorization Associated with the description of each view of the categorization scheme is a list of the categories relevant to the view. In most cases, the lists are representative or open-ended rather than exhaustive or complete. The categories relevant to the views
47、 are not necessarily mutually exclusive. While in certain applications only one of these categories may apply, in other applications all may apply. Similarly, the categories relevant to a view are not necessarily at the same level of abstraction. Where required for clarity, examples are provided for
48、 the usage or application of a view. The examples provided are illustrative and provide only a representative set of possible applications. Users of the Categorization Scheme should apply judgement when selecting the relevant or appropriate categories for a given application or application area. 7.1
49、 Software function For the software function view, categories should be defined by the type function to which it is targeted. Examples of categories of software function are: 0 Business transaction processing 0 Compiler 0 Scientific calculation 0 Word processing 0 Medical systems 0 Control systems 7.2 Application area of information system For the application area view, categories should be defined by the type or class of external system in which they are contained. 4 STD.BS1 BS ISOIIEC TR L2182-ENGL 1798 lb2Libb 079b878 783 BS ISOAEC TR 12182:1998 For example, software which is an
