《GEIA-IEEE-EIA-12207.1-1998.pdf》由会员分享,可在线阅读,更多相关《GEIA-IEEE-EIA-12207.1-1998.pdf(38页珍藏版)》请在三一文库上搜索。
1、ADOPTION NOTICE IEEEEIA 12207.1, “Guide for ISO/IEC 12207, Standard for Information Technology - Software life cycle processes - Life cycle data,” was adopted on May 27, 1998, for use by the Department of Defense (DoD). The guide provides guidance on life cycle data resulting from the processes of I
2、EEEEIA 12207.0. It describes the relationship among the following: the content of the life cycle data information items, references to documentation of life cycle data in IEEEEIA 12207.0, and sources of detailed software product information. Proposed changes by DoD activities must be submitted to th
3、e Commander, Space and Naval Warfare Systems Command, 4301 Pacific Highway, ATTN: Norma Stopyra, Code 05 1-2, San Diego, CA 92 1 10-3 127. DoD activities may obtain copies of this standard fi-om the Standardization Order Desk, 700 Robbins Avenue, Building 4/D, Philadelphia, PA 191 11-5094. The priva
4、te sector and other Government agencies may purchase copies fi-om the Institute of Electrical and Electronics Engineers, Inc. (IEEE), IEEE Service Center, 445 Hoes Lane, P. O. Box 1331, Piscataway, NJ 08855-1331. Custodians: Navy - EC Air Force - 10 Army - CR Review Activities: Navy - AS, MC, OM, SA
5、, SH, TD Air Force-02,06, 11, 13, 19 Other - DC3, DS, MP, NA, NT Army - A R , AV, CM, MI OSD - DO, IR, SE Adopting .Activity: Navy - EC (Project IPSC-0052) AREA IPSC Copyright Government Electronics (508) 750-8400. Permission to photocopy portions of any individual standard for educational classroom
6、 use can also be obtained through the Copyright Clearance Center. i Copyright Government Electronics b) Assist usability and maintainability of a software product; c) Define and control life cycle processes; d) Communicate information about the system, software product or service, and project to tho
7、se who need it; e) Provide a history of what happened during development and maintenance to support management and process improvement; f) Provide evidence that the processes were followed. GUIDANCE: Additionally, the life cycle data should support the following actions: g) Assist the software logis
8、tics planning (.e., replication, distribution, installation, training) for a h) Provide data change history. software product; 4.2.2 Operations on software life cycle data H.2 Operations on software life cycle data The life cycle data should be supported by the following operations: a) Create; b) Re
9、ad; c) Update; d) Delete. GUIDANCE: Additionally, life cycle data should be supported by the following operations: e) Archive; f) Distribute; g) Transition (transfer of data and ownership/usage rights). 3 Copyright Government Electronics b) Support the retrieval and review of data of a software item
10、 during its life cycle; c) Support the basic operations on data of a software item during its life cycle; d) Be selected subject to concurrence of the users of the data. NOTE-ln preparing or finalizing the contract, the acquirer should specify the requirements for data delivery, taking into account
11、the maintenance strategy. Some of the choices are 1) Raw data-Repositories of the development tools such as CASE tools, databases, file systems, and other 2 ) On-line publishing systems-Data assembled and formatted for presentation by systems such as: word 3) Hard copy print-Traditional paper docume
12、nt form. tool repositories. processors, World Wide Web publishing and display systems, SGML viewers. 5 Copyright Government Electronics others address related topics. NOTES 1 -The standards/guides/technical reports listed in the References column of table 1 were developed by various standards groups
13、 at different times and according to different underlying principles of software development. Consequently, many of the references will not completely satisfy the generic or specific information item content guidelines in clauses 5 and 6. Care must be exercised when using the references to identify
14、missing, conflicting, or unnecessary information not called for by this guide. 2“Throughout IEEE/EIA 12207.0, there is reference to “the contract“ and a “Request For Proposal“ (RFP). Table 1 includes some information items that would typically be part of “the contract“ and the “Request For Proposal“
15、 (e.g., Acceptance strategy and conditions), but the full contents of these items are beyond the scope of this guide. Some of the key information items that are not included in the table include Statement of Work, Contract Data Requirements List, Contract Line Items, and Contract Clauses. Table 1 -I
16、nformation item matrix Information item(s) Acceptance strategy Acquisition plan and conditions record IEEE/EIA 12207.0 Clause 5.1.1.9 5.1.1.8 Acquisition 5.1.2.1 I Change request 15.4.4, 5.5.1, Concept of operations description Conceptheed determination record Database design description Detailed de
17、sign evaluation record Development process plan 6.2.3 5.1.1.1 5.1.1.1 5.3.5.3, 5.3.6.3, 5.3.7.1 5.3.6.7 5.3.1.4 I IEEE/EIA Kind Of 12207.1 Clause References documentation (See annex A.) Record (5.4) IEEE 1062 - Plan 6.1 ASTM E731, E1206, IEEE 1062 Record (5.4) Record (5.4) IEEE 1062, 1220 - - - Proc
18、edure 6.2 Request (5.3) - - - Description 6.3 IEEE 1362, EIA/IEEE J-STD-O16 F.2. l. Also see IS0 5806, 5807, 8631, 8790, and 1 141 1 for guidance on use of notations. Record (5.4) IEEE 1062, 1220 - Description 6.4 - 6.6 Record IEEE 1016, ASTM E622, E1340, 6.5 Plan EIA/IEEE J-STD-O16 G.2.3 EIA/IEEE J
19、-STD-O16 E.2.1, IEEE 1074, 1074.1 6 Copyright Government Electronics d) Support the life cycle data characteristics from annex H of IEEE/EIA 12207.0 (see 4.2 of this guide). NOTE-The references provided in column 5 of table 1 are only advisory. 4.4.2 Organizational process compliance An organization
20、 may claim that one or more organizational processes comply with IEEE/EIA 12207.1 by documenting that those processes would produce documents or document groups complying with the corresponding rows of table 1. For this use, it is presumed that the organization has already made a claim of compliance
21、 with one or more processes of IEEE/EIA 12207.0 in accordance with annex F of that standard: that claim of compliance implies that the organizational processes satisfy the requirements of a set of clauses of IEEE/EIA 12207.0. A row of table 1 is selected if one of the cross-references appearing in c
22、olumn 2 of the table corresponds to a clause of IEEE/EIA 12207.0 satisfied by the organizational process(es). The claim of compliance shall be documented by designating which organizational template(s), information model(s), or other procedures contain the requirements sufficient to prescribe the pr
23、oduction of documents or document groups compliant with the selected rows (see 4.4.1 of this guide). 11 Copyright Government Electronics Scope; Issuing organization; References; Context; Notation for description; Body; Summary; Glossary; Change history. 5.2 Plan-generic content guidelines 5.2.1 Purp
24、ose: Define when, how, and by whom specific activities are to be performed, including options and alternatives, as required. 5.2.2 A plan should include Date of issue and status; Scope; Issuing organization; References; Approval authority; Planned activities and tasks; Macro references (policies or
25、laws that give rise to the need for this plan); Micro references (other plans or task descriptions that elaborate details of this plan); Schedules; Estimates; Resources and their allocation; Responsibilities and authority; Risks; Quality control measures; cost; Interfaces among parties involved; Env
26、ironment/infrastructure, including safety needs; Training; Glossary; Change procedures and history. 5.3 Procedure-generic content guidelines 5.3.1 Purpose: Define in detail when and how to perform certain jobs, including needed tools. 5.3.2 A procedure should include Date of issue and status; Scope;
27、 Issuing organization; References; Approval authority; Relationship to other procedures; Macro references (policies or laws that give rise to the need for this procedure); Copyright Government Electronics j) Ordered description of the steps to be taken by each participant; k) Glossary; I) Change his
28、tory. procedure); 5.4 Record-generic content guidelines 5.4.1 Purpose: Describe the materials an organization retains (e.g., quality records, legal records, fiscal records, historical records). 5.4.2 A record should include a) Date recorded; b) Scope; c) Subject; d) Issuing organization; e) Referenc
29、es; f) Datehime frame; g) Body; h) Glossary. 5.5 Report-generic content guidelines 5.5.1 Purpose: Describe the results of activities such as investigations, assessments, and tests. 5.5.2 A report should include a) Date of issue and status; b) Scope; c) Issuing organization; d) References; e) Summary
30、; f) Introduction; g) Context; h) Message; i) Contributors; i) Body; k) Conclusions and recommendations; I) Bibliography; m) Glossary; n) Change history. 5.6 Request-generic content guidelines 5.6.1 Purpose: Record information needed to solicit a response. 5.6.2 A request should include a) Date of i
31、nitiation; b) Scope; c) Subject; d) Originator of request; e) Identification of requested item, service, or response; f) Detailed description of requested item, service, or response, including suspense date; g) Justifications. 5.7 Specification “generic content guidelines 5.7.1 Purpose: Specify a re
32、quired function, performance, or process (e.g., requirements specification). 5.7.2 A specification should include a) Date of issue and status; 13 Copyright Government Electronics Issuing organization; References; Approval authority; Body; Delivery instructions; Assurance requirements; Conditions, co
33、nstraints, and characteristics; Glossary; Change history. 14 Copyright Government Electronics schedule information given in specific plans should relate to this master schedule by activities rather than calendar dates to allow for schedule variation without requiring change to each plan. Some inform
34、ation is duplicated across multiple information items, for example, input/output and computer resource information. The Software Development Standards Description, 6.17, may include the type of information and level of detail to be provided in each information item where duplications exist. 6.1 Acqu
35、isition plan 6.1 .I Purpose: Define the technical and managerial processes necessary to satisfy acquisition requirements. 6.1.2 IEEE/EIA 12207.0 reference: 5.1.1.8. 6.1.3 Content: The acquisition plan should include a) Generic plan information (see 5.2 of this guide) for the following activities: 1)
36、 Acquisition process initiation: 2) Request-for-proposal -tender preparation; 3) Contract preparation and update: 4) Supplier monitoring; 5) Acceptance and completion. b) Requirements for the system; c) Planned employment of the system; d) Type of contract to be employed; e) Responsibilities of the
37、organizations involved; f) Support concept to be used; g) Risks considered as well as methods to manage the risks. 6.1.4 Characteristics: The acquisition plan should a) Support the life cycle data characteristics from annex H of IEEE/EIA 12207.0 (see 4.2 of this guide). NOTE-Further information on a
38、cquisition plan contents (e.g., definition of project acquisition process, relationship of project acquisition process to organizations acquisition process, description of software measurement plan) may be found in IEEE/EIA 12207.2 guidance for 5.1.1.8. 6.2 Change request or modification request 6.2
39、.1 Purpose: Identify and record the implementation of a change or modification in a software item. 6.2.2 IEEE/EIA 12207.0 reference: 5.4.4, 5.5.1, 5.5.2.4, 6.2.3. 6.2.3 Content: The change or modification request should include a) Generic request information (see 5.6 of this guide); b) Justification
40、 for and nature of change, including 1) New or modified capability(ies)/function(s) or other change(s1 needed; 2) Priority(ies) of changek); 3) Assumptions/constraints that affect change(s); 4) Change to correct software error; 5) Impact to schedules, cost, products, and test. c) Originator of chang
41、e request; d) Information regarding receipt, recording, and tracking change request from the users; e) Configuration control of change request, including 15 Copyright Government Electronics 2) Analysis and evaluation of change; 3) Approval or disapproval of change request; 4) Verification of the imp
42、lementation and release of modified system. 6.2.4 Characteristics: The change or modification request should a) Support the life cycle data characteristics from annex H of IEEE/EIA 12207.0 (see 4.2 of this guide). NOTE-Some organizations have found it convenient to combine Change Request (6.2) and P
43、roblem Report (6.10). 6.3 Concept of operations description 6.3.1 Purpose: Describe, in users terminology, how the system should operate to meet the users needs for the system. 6.3.2 IEEE/EIA 12207.0 reference: 5.1.1 .l. 6.3.3 Content: The concept of operations description should include a) Generic
44、description information (see 5.1 of this guide); b) Description of current situation or system; c) Justification for and nature of changes; dl Concepts for the proposed system; e) Operational scenarios; f) Summary of impacts; g) Analysis of the proposed system; h) Priorities, assumptions, constraint
45、s, advantages, limitations, alternatives, and trade-offs considered. 6.3.4 Characteristics: The concept of operations description should a) Support the life cycle data characteristics from annex H of IEEE/EIA 12207.0 (see 4.2 of this guide). 6.4 Database design description 6.4.1 Purpose: Describe th
46、e design of a database, that is, a collection of related data stored in one or more computerized files in a manner that can be accessed by users or computer programs via a database management system (DBMS). May also describe the software units used to access or manipulate the data. Used as the basis
47、 for implementing the database and related software units. 6.4.2 IEEE/EIA 12207.0 reference: 5.3.5.3, 5.3.6.3, 5.3.7.1. 6.4.3 Content: The database design description should include a) Generic description information (see 5.1 of this guide); b) Database overview and identification; c) Design of the
48、database, including descriptions of applicable design levels (e.g., conceptual, internal, logical, physical); d) Reference to design description of software used for database access or manipulation; e) Rationale for database design. 6.4.4 Characteristics: The database design description should a) Su
49、pport the life cycle data characteristics from annex H of IEEE/EIA 12207.0 (see 4.2 of this b) Define types of errors that are not specified in the software requirements and the handling of guide); those errors. 6.5 Development process plan 6.5.1 Purpose: Define the objectives, standards, and software life cycle models to be used in the software development processes. 6.5.2 IEEE/EIA 12207.0 reference: 5.3.1 -4. 6.5.3 Content: The development process plan should include 1 6 Copyright Government Electronics 2) System requirements analysis; 3) System architectural design; 4) So
链接地址:https://www.31doc.com/p-3764710.html