This introduction is not part of ieee std 10611998, ieee standard for a software quality metrics methodology. Use of this standard is not restricted by size, complexity, criticality, or application of the software product. Ieee standard 1045, software productivity measurement 2 describes the calculation of productivity in terms of effort combined with counts of lines of code or function points. Software requirements specification and ieee standards. Ieee membership offers access to technical innovation, cuttingedge information, networking opportunities, and exclusive member benefits. Jul 18, 2008 the documentation elements for each type of test documentation can then be selected. Use the standard to understand what makes for a good software requirement, as well as how to apply these requirements throughout the software s lifecycle. Harmonization in isoieee software engineering standards article pdf available in journal of software 72.
When ieee initiated development of ieee 1471, there were four stated goals for the standard ellis, et. History in february 1984, a project to develop a standard for a software quality metrics methodology was approved, and a working group was formed, because there was no existing ieee standard covering the. Standard for software productivity metrics draft p1045 d5. This standard defines a framework for measuring and reporting productivity of the software process. The ieee standard glossary of software engineering terminology defines. It recommends variations to address software reuse and maintenance scenarios. Computeraided software engineering case technologiesspl minusespecially repositorybased, integrated casespl minushave the potential to support the automation of this measurement. Finally, section 5 concludes the paper and provides some suggestions for the improvement of the current iso 91264 and ieee std. Ieee 1045 1993, ieee standard for software productivity metrics, ieee std 1045 1992, approved by ieee standards board on 17 september 1992. It was implemented in software, in the form of floatingpoint libraries, and in hardware. A conceptual model of architecture description is established.
It is merely a list of those groups who have publicly viewable web areas. Ieee communications standards magazine aims to be a platform for presenting and discussing a broad variety of standardsrelated topics in the area of communications. From ieee software engineering standards collection. This ieee standard suggests the following structure for requirements documents. Ieee recommended practice for software requirements speci. Ieee std 91, ieee standard graphic symbols for logic functions. Ieee standard for software project management plans sponsor software engineering standards committee of the ieee computer society approved 8 december 1998 ieee sa standards board abstract. During its 23 years, it was the most widely used format for floatingpoint computation. A methodology for establishing quality requirements and identifying, implementing, analyzing, and validating the process and product software quality metrics is defined.
This introduction is not a part of ieee std 7301998, ieee standard for software quality assurance plans. Standards are published documents that establish specifications and procedures designed to maximize the reliability of the materials, products, methods, andor services people use every day. Ieee standards association ieee sa is a leading consensus building organization that nurtures, develops and advances global technologies, through ieee. The magazine will cover areas of communication and networking standards, as well as the role of standards in technical innovation in communications, the effect of intellectual property on communication technology standardization. A consistent way to measure the elements that go into computing software productivity is defined. Those interested in the functionality of the software should read section 2 overall description in. Table of required standards and recommended guidelines. Park 1992 provides an example checklist for measuring different variants of. Can be used where software is the total system or when it is part of a larger system 4. For a wider perspective on ieee standards projects, please refer to our ieee standards development lifecycle. Ieee standard for software and system test documentation. Ieee std 1045, standard for software productivity metrics. Applicability of metrology to information technology ncbi.
The institute of electrical and electronics engineers standards association ieee sa is an organization within ieee that develops global standards in a broad range of industries, including. Software productivity metrics terminology are given to ensure an understanding of measurement data for both source code and document production. Automating output size and reuse metrics in a repository. This process is hardly to optimize and does not re. Approved by american national standards institute on 23 march 1993. The very first published software engineering standard 1979. Maximum benefit by planning them early in the project life cycle 3. Applicability of metrology to information technology. A methodology for establishing quality requirements and identifying, implementing, analyzing and validating the process and product software quality metrics is defined. Section 4 introduces the enhanced software productivity model and the enhanced software productivity metrics.
This definition limits metrics to the software development process but it does connect. Ieee std 1044, standard classification for software anomalies. Use the standard to understand what makes for a good software requirement, as well as how to apply these requirements throughout the softwares lifecycle. This ieee standards product is part of the family on software engineering. Ieee standard for software project management plans sponsor software engineering standards committee of the ieee computer society approved 8 december 1998 ieeesa standards board abstract. Provides a framework for measuring and reporting software productivity. Standards address a range of issues, including but not limited to various protocols to help maximize product functionality and compatibility, facilitate. While it can be adopted independently, ieee 291482018 also includes information on how to. Sep 20, 2011 ieee standard classification for software anomalies ansi 18. Ieee 29148 covers the processes and information it recommends for a software requirements specification document, as well as its format. Ieee standards used in your everyday life ieee sa beyond. Ieee standard for software quality assurance plans ieee.
But, the manufacturing of software within the standard production process is just a very short process when bringing the binaries of the software to the device. This standard for software project management plans incorporates and subsumes the software development plans described in ansiieee std 7291983 1 and ansiieee std 7301984 2. They also foster interoperability, create uniform design, installation and testing methods, protect users and their environment and improve the quality of life of countless communities and individuals worldwide. Ieee 610,121990 standard glossary of software engineering terminologysemantics. Ieee standard for software project management plans ieee. This standard does not measure the quality of software. One might hope to look to the international standards community for guidance on a common industry problem such as productivity measurement. Ieee standards style manual may 2000 2 ieee std 911984 reaff 1994, ieee standard graphic symbols for logic functions. This standard applies to softwarebased systems being developed, maintained, or reused legacy, commercial offtheshelf, nondevelopmental items. Iso 90003 quality management and quality assurance standards part 3. Ieee 7302014 greatly expands on the previous version of 2002. Standard applies throughout the scope of any software lifecycle model 2. An overview of ieee software engineering standards and.
Ieee standard for software quality assurance plans ieee std. Ieee recommended practice for software requirements. Example of a report form for systemlevel milestone dates. With the examples we have given so far, the role of measurement in software. Ieee standard for software maintenance ieee std 12191998. Ieee guide for developing system requirements speci. Ieee 1993 ieee standard for software productivity metrics, ieee std 10451992.
Ieee sa is a central source of standards in traditional and emerging technologies, particularly in. The documentation elements for each type of test documentation can then be selected. Those interested in the functionality of the software should read section 2 overall description in order to learn more about the capabilities of the software. Members support ieees mission to advance technology for humanity and the profession, while memberships build a platform to introduce careers in technology to students around the world. The worlds largest technical professionalsociety, with a worldwide membership of morethan 375,000 electrical, electronics, computerengineers and computer scientists inapproximately 160. Focus on architectural practices for software intensive systems without precluding more general systems whenever possible. This document presents a consistent way of measuring the elements that go into computing software productivity. Ieee 7541985 was an industry standard for representing floatingpoint numbers in computers, officially adopted in 1985 and superseded in 2008 by ieee 7542008, and then again in 2019 by minor revision ieee 7542019.
Ansi board of standards approved its use as an american national standard in 2001. Although this standard prescribes measurements to characterize the software process, it does not establish software productivity norms, nor does it recommend productivity measurements as a method to evaluate software projects or software developers. The methodology spans the entire software life cycle. Defines a uniform approach to the classification and documentation of the variances found in software products. Although this ieee standard prescribes measurements to characterize the software process, it does not establish software productivity norms, nor does it. We bring together a broad range of individuals and organizations from a wide range of technical and geographic points of origin to facilitate standards development and standards related collaboration. Ieee standard classification for software anomalies ansi 18. Software requirements specification for page 2 intended audience, but it is likely that certain sections will be of more interest to each type of audience member.
Gives the details for the software quality assurance tasks outlined in the ieee 12207 standard for software life cycle processes. The existence of an ieee standard does not imply that there are no other ways to produce, test, measure, purchase, market, or provide other goods and services related to the scope of the ieee standard. Table of required standards and recommended guidelines and. Focus on architectural practices for softwareintensive systems without precluding more general systems whenever possible. From ieee software engineering standards collection ieee std 1058.
Software decision makers guide for predictable software development. The format and contents of software project management plans, applicable to any type or size of software project, are described. Ieee standard 1045, software productivity measurement 2. Ieee standard 7302014 software quality assurance processes. The institute of electrical and electronics engineers standards association ieeesa is an organization within ieee that develops global standards in a broad range of industries, including. Ieee standard for software project management plans. Software measurement for dod systems ftp directory listing. Test design specification template ieee 8291998 test design specification identifier some type of unique company generated number to identify this test case specification, its level and the level of software that it is related to. The scope of testing encompasses softwarebased systems, computer software, hardware, and their interfaces. The definition of productivity states that it is the ratio of a unit of output to a unit of. This standard assists in the preparation and content of software quality assurance plans and provides a standard against which such plans can be prepared and assessed. The application of ieee software and system engineering. The methodology spans the entire software lifecycle.
Ieee std 1045 ieee standard for software productivity. This introduction is not a part of ieee std 1233, 1998 edition, ieee guide for developing system requirements speci. This document presents a consistent way of measuring the elements that. This is not a comprehensive overview of active ieee standards working groups. The most widely known requirements document standard is ieee ansi 8301998 ieee, 1998. Of course, over the years there have been hundreds of individuals who have played pivotal roles on ieee 515. It does not specify the procedures or techniques to be used in the development of project management plans, or does it provide examples of project management plans, instead the standard sets a foundation for an organisation to build its. The staffhour unit we recommend is the one used by the ieee in its draft standard. Ieee std 270, ieee standard definitions for selected quantities, units, and related terms, with special attention to the. The scope of testing encompasses software based systems, computer software, hardware, and their interfaces. As an example, suppose that we have measured the productivity of two. Ieee standards association with collaborative thought leaders in more than 160 countries, ieee sa is a leading consensusbuilding organization that enables the creation and expansion of international markets, and helps protect health and public safety. Ieee std 10611998 revision of ieee std 10611992 ieee. Guidelines for the application of 9001 to the development, supply, installation and maintenance of computer software quality measurement.
Reliable software ansi, 10451992 ieee standard for software productivity. This standard for software project management plans incorporates and subsumes the software development plans described in ansi ieee std 7291983 1 and ansi ieee std 7301984 2. Measurement of software development productivity is needed in order to control software costs, but it is discouragingly laborintensive and expensive. However, the standards and measurement techniques needed to maintain the.
The purpose of this guide is to provide guidance for capturing system requirements. In this article, we briefly trace the history of the development of software metrics. Oct 29, 2011 technology standards ensure that products and services perform as intended. It is directed toward the development and maintenance of. It focuses on definitions of how to measure software process productivity and what to report when giving productivity results. This standard applies to software based systems being developed, maintained, or reused legacy, commercial offtheshelf, nondevelopmental items. Ieee standard concerning the evaluation of productivity are broadranging and. Technology standards ensure that products and services perform as intended. The most widely known requirements document standard is ieeeansi 8301998 ieee, 1998. While some help is available from this direction, it is limited. This standard specifies the format and contents of software project management plans. Jul 20, 2012 ieee 1045 1993, ieee standard for software productivity metrics, ieee std 1045 1992, approved by ieee standards board on 17 september 1992. Metrics in the software engineering curriculum springerlink.
549 267 156 13 435 496 1534 342 1293 376 1196 1505 592 938 1206 217 422 531 475 283 1275 1257 871 192 902 222 250 746 1381 1083 85 1313