IEEE 1016-2009 en Information Technology Systems Design Software Design Descriptions (IEEE Computer Society)《信息技术 系统设计 软件设计描述》.pdf
《IEEE 1016-2009 en Information Technology Systems Design Software Design Descriptions (IEEE Computer Society)《信息技术 系统设计 软件设计描述》.pdf》由会员分享,可在线阅读,更多相关《IEEE 1016-2009 en Information Technology Systems Design Software Design Descriptions (IEEE Computer Society)《信息技术 系统设计 软件设计描述》.pdf(40页珍藏版)》请在麦多课文档分享上搜索。
1、IEEE Std 1016-2009(Revision of IEEE Std 1016-1998) IEEE Standard for Information TechnologySystems Design Software Design DescriptionsIEEE3 Park Avenue New York, NY 10016-5997, USA20 July 2009IEEE Computer SocietySponsored by theSoftware +1 978 750 8400. Permission to photocopy portions of any indiv
2、idual standard for educational classroom use can also be obtained through the Copyright Clearance Center. iv Copyright 2009 IEEE. All rights reserved. Introduction This introduction is not part of IEEE Std 1016-2009, IEEE Standard for Information TechnologySystems DesignSoftware Design Descriptions.
3、 This standard specifies requirements on the information content and organization for software design descriptions (SDDs). An SDD is a representation of a software design that is to be used for recording design information, addressing various design concerns, and communicating that information to th
4、e designs stakeholders. SDDs play a pivotal role in the development and maintenance of software systems. During its lifetime, an SDD is used by acquirers, project managers, quality assurance staff, configuration managers, software designers, programmers, testers, and maintainers. Each of these stake
5、holders has unique needs, both in terms of required design information and optimal organization of that information. Hence, a design description contains the design information needed by those stakeholders. The standard also specifies requirements on the design languages to be used when producing SD
6、Ds conforming to these requirements on content and organization. The standard specifies that an SDD be organized into a number of design views. Each view addresses a specific set of design concerns of the stakeholders. Each design view is prescribed by a design viewpoint. A viewpoint identifies the
7、design concerns to be focused upon within its view and selects the design languages used to record that design view. The standard establishes a common set of viewpoints for design views, as a starting point for the preparation of an SDD, and a generic capability for defining new design viewpoints th
8、ereby expanding the expressiveness of an SDD for its stakeholders. This standard is intended for use in design situations in which an explicit SDD is to be prepared. These situations include traditional software design and construction activities leading to an implementation as well as “reverse engi
9、neering” situations where a design description is to be recovered from an existing implementation. This standard can be applied to commercial, scientific, military, and other types of software. Applicability is not restricted by size, complexity, or criticality of the software. This standard conside
10、rs both the software and its system context, including the developmental and operational environment. It can be used where software comprises the system or where software is part of a larger system characterized by hardware, software, and human components and their interfaces. This standard is appli
11、cable whether the SDD is captured using paper documents, automated databases, software development tools, or other media. This standard does not explicitly support, nor is it limited to, use with any particular software design methodology or particular design languages, although it establishes minim
12、um requirements on the selection of those design languages. This standard can be used with IEEE Std 12207-2008 B21;ait can also be used in other life cycle contexts. This standard consists of five clauses, as follows: Clause 1 defines the scope and purpose of the standard. Clause 2 provides definiti
13、ons of terms used within the context of the standard. aThe numbers in brackets correspond to those of the Bibliography in Annex A. v Copyright 2009 IEEE. All rights reserved. Clause 3 provides a framework for understanding SDDs in the context of their preparation and use. Clause 4 describes the requ
14、ired content and organization of an SDD. Clause 5 defines several design viewpoints for use in producing SDDs. Annex A provides a bibliography. Annex B defines how a design language to be used in an SDD is to be described in a uniform manner. Annex C contains a template for organizing an SDD conform
15、ing to the requirements of this standard. This standard follows the IEEE Standards Style Manual.bIn particular, the word shall identifies requirements that must be satisfied in order to claim conformance with this standard. The verb should identifies recommendations, and the verb may is used to deno
16、te that particular courses of action are permissible. This revision of the standard is modeled after IEEE Std 1471-2000 B20, extending the concepts of view, viewpoint, stakeholder, and concern from that standard to support high-level and detailed design and construction for software. The demarcation
17、 between architecture, high-level and detailed design varies from system to system and is beyond the scope of this standard. Notice to users Laws and regulations Users of these documents should consult all applicable laws and regulations. Compliance with the provisions of this standard does not impl
18、y compliance to any applicable regulatory requirements. Implementers of the standard are responsible for observing or referring to the applicable regulatory requirements. IEEE does not, by the publication of its standards, intend to urge action that is not in compliance with applicable laws, and the
19、se documents may not be construed as doing so. Copyrights This document is copyrighted by the IEEE. It is made available for a wide variety of both public and private uses. These include both use, by reference, in laws and regulations, and use in private self-regulation, standardization, and the pro
20、motion of engineering practices and methods. By making this document available for use and adoption by public authorities and private users, the IEEE does not waive any rights in copyright to this document. bThe IEEE Standards Style Manual can be found at http:/standards.ieee.org/guides/style/index.
21、html. vi Copyright 2009 IEEE. All rights reserved. Updating of IEEE documents Users of IEEE standards should be aware that these documents may be superseded at any time by the issuance of new editions or may be amended from time to time through the issuance of amendments, corrigenda, or errata. An o
22、fficial IEEE document at any point in time consists of the current edition of the document together with any amendments, corrigenda, or errata then in effect. In order to determine whether a given document is the current edition and whether it has been amended through the issuance of amendments, cor
23、rigenda, or errata, visit the IEEE Standards Association web site at http:/ieeexplore.ieee.org/xpl/standards.jsp, or contact the IEEE at the address listed previously. For more information about the IEEE Standards Association or the IEEE standards development process, visit the IEEE-SA web site at h
24、ttp:/standards.ieee.org. Errata Errata, if any, for this and all other standards can be accessed at the following URL: http:/standards.ieee.org/reading/ieee/updates/errata/index.html. Users are encouraged to check this URL for errata periodically. Interpretations Current interpretations can be acces
- 1.请仔细阅读文档,确保文档完整性,对于不预览、不比对内容而直接下载带来的问题本站不予受理。
- 2.下载的文档,不会出现我们的网址水印。
- 3、该文档所得收入(下载+内容+预览)归上传者、原创作者;如果您是本文档原作者,请点此认领!既往收益都归您。
下载文档到电脑,查找使用更方便
10000 积分 0人已下载
下载 | 加入VIP,交流精品资源 |
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- IEEE10162009ENINFORMATIONTECHNOLOGYSYSTEMSDESIGNSOFTWAREDESIGNDESCRIPTIONSIEEECOMPUTERSOCIETY 信息技术 系统

链接地址:http://www.mydoc123.com/p-1247989.html