For Better Software Systems Development A …

1 For Better Software Systems Development A Comparison of IEEE/EIA 12207, ISO/IEC 12207, J-STD-016, and MIL-STD-498 for Acquirers and Developers Lewis Gray, Abelia Corporation 12224 Grassy Hill Court Fairfax, Virginia 22033-2819 USA. (T) (F) Copyright 1999 by Abelia Corporation. All rights reserved worldwide. Lewis Gray - 1. For Better Software Systems Development For Further Information Lewis Gray Abelia Corporation 12224 Grassy Hill Court Fairfax, VA 22033-2819 USA. 703-591-5247 (F) 703-591-5005. Copyright 1999 by Abelia Corporation. All rights reserved worldwide. Lewis Gray - 2. For Better Software Systems Development Topics Significant similarities and differences between the requirements in IEEE/EIA 12207 (adopted by the DoD on 27 May 98). ISO/IEC 12207. J-STD-016, and MIL-STD-498 (canceled by the DoD on 27 May 98). Acquirer - developer relations as described in MIL-STD-498 / J-STD-016 and IEEE/EIA 12207.

2 Copyright 1999 by Abelia Corporation. All rights reserved worldwide. Lewis Gray - 3. For Better Software Systems Background: Development The Pedigree of IEEE/EIA 12207. ISO/IEC 12207. DOD-STD-2167A " Software Life "Defense system Cycle Processes,". Software Development ," ISO 12207 Aug '95 IEEE Stds Feb '88. 2167A. 498 016 12207. 7935A MIL-STD-498 J-STD-016-1995 IEEE/EIA " Software (Trial Use Std.) " Software Life Cycle Development and " Software Life Processes . DOD-STD-7935A Documentation," Cycle Processes, Mar 98. "DoD Automated Dec '94 Software Information Development " (Guides). Systems (AIS) Sep '95 IEEE/EIA Documentation IEEE/EIA Standards," Oct '88 Apr 98. Copyright 1999 by Abelia Corporation. All rights reserved worldwide. Lewis Gray - 4. For Better Software Systems Development Background: Traditions of Major Influences Military Standards ISO Standards created by organizations within created by committees of the Department of Defense national representatives authored by industry contractors inspire national authors guided by advisory implementations committees consisting both of used voluntarily individuals and of used by businesses representatives of military and used to simplify trade.

3 Industry organizations reviewed by military and IEEE Software Standards industry personnel created by committees of legally enforced on military professional individuals Software contractors used voluntarily used to compensate for shortage of technically-trained used by businesses government Software buyers. and individuals used for self-improvement. Copyright 1999 by Abelia Corporation. All rights reserved worldwide. Lewis Gray - 5. For Better Software Systems Development Background: All Four Standards are Most Define Planning Develop & Maintain Operate Concept funding Require's obtained Definition Request for Proposal Design (RFP). Implement Software Change Test Request (SCR) initial response etc. etc. What: WBS (contracted tasks, data). Who: people 498, 016, both 12207s When: schedule How: tasks, data, methods, suggest processes, data procedures, tools Copyright 1999 by Abelia Corporation.

4 All rights reserved worldwide. Lewis Gray - 6. For Better Software Systems Development Background: Similar Leadership Influences The Chair of the DoD Harmonization Working Group (HWG) that developed MIL-STD-498, the Editor of ISO/IEC 12207 during its Development , the IEEE Co-Chair of the Joint Industry Working Group on Software Development that developed J-STD-016-1995, and the IEEE Co-Chair of the Joint Industrial Standard Working Group (JISWG) that developed IEEE/EIA all were the same person, Dr. Raghu Singh (SPAWAR), who is now with the Federal Aviation Admin. in Washington, DC. Copyright 1999 by Abelia Corporation. All rights reserved worldwide. Lewis Gray - 7. For Better Software Systems Development Topics Significant similarities and differences between the requirements in IEEE/EIA 12207 (adopted by the DoD on 27 May 98). ISO/IEC 12207. J-STD-016, and MIL-STD-498 (canceled by the DoD on 27 May 98).

5 Acquirer - developer relations as described in MIL-STD-498 / J-STD-016 and IEEE/EIA 12207. Copyright 1999 by Abelia Corporation. All rights reserved worldwide. Lewis Gray - 8. For Better The Military Tradition: MIL-STD-498 to J-STD-016. Software Systems Development ISO/IEC 12207. DOD-STD-2167A " Software Life "Defense system Cycle Processes,". Software Development ," ISO 12207 Aug '95 IEEE Stds Feb '88. 2167A. 498 016 12207. 7935A MIL-STD-498 J-STD-016-1995 IEEE/EIA " Software (Trial Use Std.) " Software Life Cycle Development and " Software Life Processes . DOD-STD-7935A Documentation," Cycle Processes, Mar 98. "DoD Automated Dec '94 Software Information Development " (Guides). Systems (AIS) Sep '95 IEEE/EIA Documentation IEEE/EIA Standards," Oct '88 [formerly IEEE Apr 98. Std 1498 / EIA IS. 640] [formerly IEEE P1448]. Copyright 1999 by Abelia Corporation. All rights reserved worldwide.

6 Lewis Gray - 9. For Better Software Systems Development Why is There J-STD-016-1995? To bring MIL-STD-498's deliberately limited (2-year) life to a close. SecDef Perry's memo of 29 Jun 94 began the retirement of military Software Development standards. Despite the memo, MIL-STD-498 was adopted on 5 Dec 94 to provide a bridge to a suitable non-governmental Software life cycle processes standard yet to be developed. That replacement standard is now called IEEE/EIA 12207. J-STD-016-1995 was the first step toward it. Copyright 1999 by Abelia Corporation. All rights reserved worldwide. Lewis Gray - 10. For Better Software Systems Development Only Cosmetic Differences If this is ..this is J-STD-016-1995. J-STD-016. Copyright 1999 by Abelia Corporation. All rights reserved worldwide. Lewis Gray - 11. For Better Software Systems Development MIL-STD-498 vs. J-STD-016-1995.

7 Bottom Line . J-STD-016 is a demilitarized MIL-STD-498. J-STD-016-1995 adds a general requirement for traceability similar to the traceability elements in MIL-STD-498 DIDs. For each detailed requirement in MIL-STD-498 there is one in J-STD-016-1995 with the same technical content. Two additional activities in J-STD-016-1995 update system and Software requirements to match the as-built Software . For each MIL-STD-498 DID there is a product description in J-STD-016-1995 with the same content. Every data item in J-STD-016-1995 is also in MIL-STD-498. Copyright 1999 by Abelia Corporation. All rights reserved worldwide. Lewis Gray - 12. For Better Software Systems Development The Development of J-STD-016. Dropped military Ballot in June 98 - references 2nd ballot in Summer 99. Adopted ISO-style Backed away from contractual use clauses Redefined Tailoring Packaged data Assumed defined descriptions as organizational Software subclauses process Two Trends Compatibility with ISO.

8 498 016 016 standards Influence of MIL-STD-498 J-STD-016-1995 J-STD-016-1998 Software process " Software (Trial Use Std.) " Software Life Development and Sep '95 Cycle Processes: improvement Documentation," Software Dec '94 Development ". goals Copyright 1999 by Abelia Corporation. All rights reserved worldwide. Lewis Gray - 13. For Better Software Systems Development Should (and Will) J-STD-016 Survive? YES, J-STD-016 product descriptions have been cited by IEEE/EIA but not included in whole. Projects that use (or prefer to adopt) MIL-STD-498 language for contracts, or have process descriptions based on it, need J-STD-016. NO, Most of the J-STD-016 engineering requirements are already in IEEE/EIA , and the content of J-STD-016 product descriptions could be added to IEEE/EIA IEEE/EIA 12207 is compatible with a Software process description written in language from MIL-STD-498.

9 Most topics in J-STD-016 are covered by other IEEE or ISO standards. There is significant DoD interest in adopting J-STD-016. Copyright 1999 by Abelia Corporation. All rights reserved worldwide. Lewis Gray - 14. For Better The Business Tradition: Software Systems Development IEEE/EIA 12207. ISO/IEC 12207. DOD-STD-2167A " Software Life "Defense system Cycle Processes,". Software Development ," ISO 12207 Aug '95 IEEE Stds Feb '88. 2167A. 498 016 12207. 7935A MIL-STD-498 J-STD-016-1995 IEEE/EIA " Software (Trial Use Std.) " Software Life Cycle Development and " Software Life Processes . DOD-STD-7935A Documentation," Cycle Processes, Mar 98. "DoD Automated Dec '94 Software Information Development " (Guides). Systems (AIS) Sep '95 IEEE/EIA Documentation IEEE/EIA Standards," Oct '88 [formerly IEEE Apr 98. Std 1498 / EIA IS. 640] [formerly IEEE P1448]. Copyright 1999 by Abelia Corporation.

10 All rights reserved worldwide. Lewis Gray - 15. For Better Software Systems Development IEEE/EIA 12207 Structure at a Glance IEEE/EIA IEEE/EIA Industry Implementation of Guide to IEEE/EIA 12207 -- International Standard Software Life Cycle ISO/IEC 12207: 1995 Processes --Life Cycle Annexes Data . E-J. IEEE/EIA ISO/IEC Guide to IEEE/EIA 12207 -- Software Life Cycle 12207 Processes --Implementation Considerations . New Foreword Base Standar Guide d Copyright 1999 by Abelia Corporation. All rights reserved worldwide. Lewis Gray - 16. For Better ISO/IEC 12207 & IEEE/EIA 12207. Software Systems Development Share a Life Cycle Processes Model Key ORGANIZATION. 0 - the same points CM - Configuration Management MANAGEMENT INFRASTRUCTURE TRAINING IMPROVEMENT process E - execute M F. PROJECT E:n - execute supporting process n E:ACQ - execute the OPERATION. F F F E: 3 F Acquisition process F - feed back (verb).