BS ISO IEC 25030-2007 Software engineering - Software product quality requirements and evaluation (SQuaRE) - Quality requirements《软件工程 软件产品质量要求和评定(SQuaRE) 质量要求》.pdf

1、BRITISH STANDARD BS ISO/IEC 25030:2007 Software engineering Software product Quality Requirements and Evaluation (SQuaRE) Quality requirements ICS 35.080 BS ISO/IEC 25030:2007 This British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 July 2007 BSI 2

2、007 ISBN 978 0 580 59324 6 National foreword This British Standard was published by BSI. It is the UK implementation of ISO/IEC 25030:2007. The UK participation in its preparation was entrusted to Technical Committee IST/15, Software and systems engineering. A list of organizations represented on th

3、is committee can be obtained on request to its secretary. This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. Compliance with a British Standard cannot confer immunity from legal obligations. Amendments issued si

4、nce publication Amd. No. Date Comments Reference number ISO/IEC 25030:2007(E)INTERNATIONAL STANDARD ISO/IEC 25030 First edition 2007-06-01 Software engineering Software product Quality Requirements and Evaluation (SQuaRE) Quality requirements Ingnierie du logiciel Exigences de qualit et valuation du

5、 produit logiciel (SQuaRE) Exigences de qualit BS ISO/IEC 25030:2007ii Contents Page 1 Scope . 1 2 Conformance .1 3 Normative references1 4 Terms and definitions . 2 5 Fundamental concepts for quality requirements. 2 5.1 Software and systems. 2 5.2 Stakeholders and stakeholder requirements 3 5.3 Sta

6、keholder requirements and system requirements 4 5.4 Software quality model . 5 5.5 Software properties. 7 5.6 Software quality measurement model . 7 5.7 Software quality requirements . 8 5.8 System requirements categorisation. 9 5.9 Quality requirements life cycle model . 10 6 Requirements for quali

7、ty requirements. 12 6.1 General requirements and assumptions . 12 6.2 Stakeholder requirements 12 6.3 Software requirements 14 Annex A (normative) Terms and definitions 19 Annex B (informative) Processes from ISO/IEC 15288 32 Bibliography . 35 Foreword v Introduction vi iii BS ISO/IEC 25030:2007iv F

8、oreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical 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 technic

9、al 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 international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part

10、in the work. In the field of information technology, ISO and IEC have established a joint technical committee, 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 Interna

11、tional Standards. Draft International Standards adopted by the joint technical committee are circulated 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

12、 the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. ISO/IEC 25030 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Software and systems engineer

13、ing. ISO/IEC 25030 is part of the ISO/IEC 25000 SQuaRE series of standards. The series consists of the following divisions under the general title Software product Quality Requirements and Evaluation (SQuaRE): ISO/IEC 2500n, Quality Management Division, ISO/IEC 2501n, Quality Model Division, ISO/IEC

14、 2502n, Quality Measurement Division, ISO/IEC 2503n, Quality Requirements Division, and ISO/IEC 2504n, Quality Evaluation Division. ISO/IEC 25050 to ISO/IEC 25099 are reserved to be used for SQuaRE extension International Standards, Technical Specifications, Publicly Available Specifications (PAS) a

15、nd/or Technical Reports: ISO/IEC 25051 and ISO/IEC 25062 are already published. BS ISO/IEC 25030:2007v Introduction It is important to identify and specify software quality requirements as part of specifying the requirements for a software product. Software is usually part of a larger system. System

16、 requirements and software requirements are closely related and software requirements can therefore not be considered in isolation. This International Standard focuses on software quality requirements, but takes a system perspective. Software quality requirements can be categorized by use of a quali

17、ty model, for example the quality model defined in ISO/IEC 9126-1 ISO/IEC 25010. Measures of attributes of these characteristics and their subcharacteristics can be used to specify software quality requirements and evaluate the quality of a software product. Software quality requirements address imp

18、ortant issues of quality for software products. Software product quality requirements are needed for: specification (including contractual agreement and call for tender); planning (including feasibility analysis and translation of external software quality requirements into internal software quality

19、 requirements); development (including early identification of potential quality problems during development); and evaluation (including objective assessment and certification of software product quality). If software quality requirements are not stated clearly, they may be viewed, interpreted, impl

20、emented and evaluated differently by different people. This may result in software which is inconsistent with user expectations and of poor quality; users, clients and developers who are unsatisfied; and time and cost overruns to rework software. This International Standard aims to improve the quali

21、ty of software quality requirements. It does this by providing requirements and recommendations for quality requirements, and guidance for the processes used to define and analyse quality requirements. Application of this International Standard should help ensure that software quality requirements a

22、re: in accordance with stakeholder needs; stated clearly and precisely; correct, complete, and consistent; and verifiable and measurable. This International Standard is intended to be used in conjunction with the other parts of the SQuaRE series of Standards (ISO/IEC 25000 ISO/IEC 25049), and with I

23、SO/IEC 14598 and ISO/IEC 9126, until superseded by the ISO/IEC 25000 series. This International Standard complies with the technical processes defined in ISO/IEC 15288:2002 related to quality requirements definition and analysis. BS ISO/IEC 25030:2007vi Figure 1 Organisation of the ISO/IEC 25000 SQu

24、aRE series of International Standards Figure 1 (copied from ISO/IEC 25000) illustrates the organisation of the ISO/IEC 25000 SQuaRE series representing families of International Standards, further called Divisions. The Divisions within SQuaRE model are: ISO/IEC 2500n, Quality Management Division. Th

25、e International Standards that form this division define all common models, terms and definitions referred to further by all other International Standards from the SQuaRE series. Referring paths (guidance through SQuaRE documents) and high level practical suggestions in applying proper International

26、 Standards to specific application cases offer help to all types of users. The division also provides requirements and guidance for a supporting function which is responsible for the management of software product requirements specification and evaluation. ISO/IEC 2501n, Quality Model Division. The

27、International Standard that forms this division presents a detailed quality model including characteristics for internal, external and quality in use. Furthermore, the internal and external software quality characteristics are decomposed into subcharacteristics. Practical guidance on the use of the

28、quality model is also provided. ISO/IEC 2502n, Quality Measurement Division. The International Standards that form this division include a software product quality measurement reference model, mathematical definitions of quality measures, and practical guidance for their application. Presented measu

29、res apply to internal software quality, external software quality and quality in use. Measurement primitives forming foundations for the latter measures are defined and presented. ISO/IEC 2503n, Quality Requirements Division. The International Standard that forms this division helps specify quality

30、requirements. These quality requirements can be used in the process of quality requirements elicitation for a software product to be developed or as input for an evaluation process. The requirements definition process is mapped to technical processes defined in ISO/IEC 15288. ISO/IEC 2504n, Quality

31、Evaluation Division. The International Standards that form this division provide requirements, recommendations and guidelines for software product evaluation, whether performed by evaluators, acquirers or developers. The support for documenting a measure as an Evaluation Module is also presented. IS

32、O/IEC 25050 to ISO/IEC 25099 are reserved to be used for SQuaRE extension International Standards and/or Technical Reports. Quality Requirements Division 2503n Quality Evaluation Division 2504n Quality Model Division 2501n Quality Measurement Division 2502n Quality Management Division 2500n BS ISO/I

33、EC 25030:20071 Software engineering Software product Quality Requirements and Evaluation (SQuaRE) Quality requirements 1 Scope This International Standard provides requirements and recommendations for the specification of software product quality requirements. This International Standard applies to

34、organisations in their role as both acquirers and suppliers. The quality model in ISO/IEC 9126-1 ISO/IEC 25010 is used to categorize software quality requirements and to provide a basis for quantifying the quality requirements in terms of software quality measures. This International Standard compli

35、es with the technical processes defined in ISO/IEC 15288:2002, which are relevant for identification of stakeholder product quality needs and for analysis of software product quality requirements. This International Standard does not cover specification of other requirements (such as functional requ

36、irements, process requirements, business requirements, etc.). This International Standard does not prescribe specific software quality measures nor does it prescribe any specific development process. 2 Conformance Software quality requirements conform to this International Standard if they fulfil th

37、e requirements specified in Clause 6. 3 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendment

38、s) applies. ISO/IEC 9126-1:2001, Software engineering Product quality Part 1: Quality model 1)ISO/IEC 25020, Software engineering Software product Quality Requirements and Evaluation (SQuaRE) Measurement reference model and guide 1) ISO/IEC 9126-1:2001 will be cancelled and replaced by ISO/IEC 25010

39、. BS ISO/IEC 25030:20072 4 Terms and definitions For the purposes of this International Standard, the terms and definitions given in ISO/IEC 25000 (repeated in Annex A for convenience) apply. There are no definitions specific to this International Standard. 5 Fundamental concepts for quality require

40、ments Clause 5 describes concepts related to software quality requirements that are used in this Interna- tional Standard. This clause does not include requirements. 5.1 Software and systems Software is the main focus of this International Standard. However, software usually appears as part of a lar

41、ger system. Therefore it can be useful to take a system view. A system is defined as a combination of interacting elements organised to achieve one or more stated purposes. This defini- tion allows a high degree of freedom to decide, what constitute a system and what the elements of the system are.

42、The boundaries of a system will depend on the point of view. Note 1 The boundary of a system depends on the point of view as illustrated by the following three examples. One example is the control system of an aircraft engine, the second example is the complete engine of an aircraft, and a third exa

43、mple is the complete aircraft. An aircraft can be considered as a combination of ele- ments (the engines, the wings, etc.). These elements can also be considered systems on their own. Figure 2 Example of a system model Figure 2 is an example of a system model showing hierarchies of systems including

44、 an information system, a mechanical system, human business processes and communication among them. Information system Computer Hardware Operating system Application software Data Computer system Computer Hardware Operating system Application software Data Computer system Human business processes Me

45、chanical system communication communication communication communication Enterprice system BS ISO/IEC 25030:20073 There may be several different appropriate ways of defining the elements of a system. Software may be considered one of the elements of a system. A computer system is an example of a syst

46、em, which includes software. The elements of a computer system include the computer hardware, op- erating system and data necessary to apply the software. A computer system represents an appli- cable model when discussing single user software like a word processor. Clientserver software or internet

47、applications need a more complex system model like an information system which includes more communicating computer systems. E-commerce applications often include human business processes as well. Many devices include both computer systems and mechanical systems such as an antilock braking system (A

48、BS) of a car. The luggage handling at an airport includes both computer systems, mechanical systems (such as conveyer belts), and human business processes. This example illustrates that humans can be part of a system. 5.2 Stakeholders and stakeholder requirements Systems have a variety of stakeholde

49、rs who have an interest in the system throughout its life cycle. The stakeholders of a system include all persons (for example end users), organisations (for ex- ample end user organisations or development organisations) and bodies (for example statutory and regulatory authorities or the general public) having a legitimate interest in the system. Stakeholders have different needs and expectations to the system. Their needs and ex