Get documents about "MIL-STD-498, J-STD-016, and the U.S. Commercial Standard
Document Sample
MIL-STD-498, J-STD-016, and the U.S. Commercial Standard http://stsc.hill.af.mil/crosstalk/1996/jun/jstd016.asp
MIL-STD-498, J-STD-016, and the
U.S. Commercial Standard
Reed Sorensen, Software Technology Support Center
Many readers have requested information regarding the U.S. Commercial Standard and J-STD-016-1995
and how they relate to MIL-STD-498. The following includes information presented to the Joint Industries
Standard Working Group (JISWG) March 4-6, 1996.
MIL-STD-498
MIL-STD-498 was approved for interim use December 1994 by the Defense Standards Improvement
Council. This standard harmonizes the predecessor standards DOD-STD-2167A and DOD-STD-7935A,
which were specific to embedded mission-critical software and automated information systems
respectively. The standard provides many advantages by incorporating the years of lessons learned from
using the predecessor standards on contracts. See articles in the February and March issues of CrossTalk
for more information, or see the Software Technology Support Center MIL-STD-498 subpage at
http://www.stsc.hill.af.mil.
IEEE-STD-1498 and J-STD-016-1995
Even before the approval of MIL-STD-498, the Institute of Electrical and Electronic Engineers, Inc. (IEEE)
and Electronic Industries Association (EIA) had begun to develop a commercial version of MIL-STD-498
[1] published in January 1996 as J-STD-016-1995. Prior to its publication, the working drafts were widely
referred to as 1498 a shortened term for "IEEE STD P1498 EIA IS 640." Some key differences between
MIL-STD-498 and J-STD-016-1995 are shown in Tables 1 and 2.
Changes Between MIL-STD-498 and J-STD-016-1995
· Computer software configuration items are now software items.
· Hardware configuration items are now hardware items.
· Support concept is now support strategy.
· Fielding is now distribution.
· Software support is now software maintenance.
· Privacy is now privacy protection.
· Requirements analysis is now requirements definition.
· Sections are now clauses, paragraphs are subclauses, subparagraphs are subordinante clauses, and
appendixes are annexes.
· Data Item Descriptions (DIDs) are now software product descriptions found in annexes to the standard.
Table 1: Terminology Differences [2].
1 of 5 28-Jun-00 16:48
MIL-STD-498, J-STD-016, and the U.S. Commercial Standard http://stsc.hill.af.mil/crosstalk/1996/jun/jstd016.asp
Changes Between MIL-STD-498 and J-STD-016-1995
· Added mandatory (binding) annex that requires tailoring.
· Allows developer to reference software practices, as well as standards, for software development in the
software development plan.
· Added requirement to ensure each element of the software development environment performs its
intended function prior to use.
· Added a traceability tasking clause that clarifies traceability is both upward and downward.
· Added requirement to update the system and software requirements descriptions to match the approved
"as built" system and software.
· Removes default application to deliverable software; standard now applies to all software on the project
whether deliverable or not.
· Deleted default time limit, i.e., duration of the contract, for record keeping and retention of other items
(software development library and software development file). (The acquirer must specify how long
records must be keptmay be shorter or longer than the duration of the contract.)
· Deleted requirement to obtain approval for any language not specified.
(If the contract is silent, the developer is free to use any language unless other provisions or laws apply).
· Deleted reuse requirements to
· Use reusable software that resulted from identifying software for reuse: developer now tasked only to
identify and evaluate for potential reuse.
· Identify opportunities for reuse and evaluate their benefits and costs.
· Interpret the standard when reusable software is incorporated according to Appendix B. (Appendix B
changed from mandatory [binding] to informative.)
Table 2: Requirements Differences [2].
J-STD-016-1995 is a trial-use version released by EIA and IEEE. Plans are that J-STD-016-1995 will be
converted to full use status after the respective EIA IEEE trial use periods have been met. J-STD-016-1995
is expected to remain available for use until 2001 when it will be eligible to become obsolete under EIA
and IEEE rules.
J-STD-016 can be used by commercial entities and may be invoked by the Department of Defense without
a waiver. The standard can be purchased from Global Engineering by calling 1-800-854-7179. It will be
used as a mechanism for international standards convergence as shown in Figure 1.
Figure 1: Long-Range Standards Transition Plan.
U.S. Commercial Standard (US 12207-1996)
2 of 5 28-Jun-00 16:48
MIL-STD-498, J-STD-016, and the U.S. Commercial Standard http://stsc.hill.af.mil/crosstalk/1996/jun/jstd016.asp
In August 1995, ISO/IEC 12207 was released as an approved international standard. The JISWG is
adapting 12207 for United States use to include the technical content found in J-STD-016. The working
group consists of representatives from commercial and government organizations. The co-chairmen are
Perry DeWeese of Lockheed Martin and Dr. Raghu Singh Space and Naval Warfare Systems Command;
editors are Myrna Olson and Stuart Campbell, Logicon, authors of MIL-STD-498 and its guidebooks. As
shown in Figure 2, US 12207-1996 will consist of ISO/IEC 12207 with additional materials. These
additional materials include a road map to US 12207-1996, clarifications, interpretations, and product
descriptions as shown in Figure 2. The scope of ISO/IEC 12207 is broader than the scope of J-STD-016.
J-STD-016-1995 focuses on the development process while ISO/IEC 12207 includes the acquisition,
supply, operation, and maintenance processes. Consequently, the additional materials in US 12207-1996
focus on those areas where the two standards overlap, i.e., development and the supporting processes such
as documentation, quality assurance, configuration management, and joint reviews.
Figure 2: Transition to Commercial Standards [3].
Acknowledgment
I thank Myrna Olson and Dr. Lewis Gray for their comments on this article.
Reed Sorensen
Software Technology Support Center
Ogden ALC/TISE
7278 Fourth Street
Hill AFB, UT 84056-5205
Voice: 801-775-5555 ext. 3049 DSN 775-5555 ext. 3049
Fax: 801-774-7996
E-mail: sorenser@software.hill.af.mil
References
1. October 1994.
3 of 5 28-Jun-00 16:48
MIL-STD-498, J-STD-016, and the U.S. Commercial Standard http://stsc.hill.af.mil/crosstalk/1996/jun/jstd016.asp
2. Olson, Myrna, Trial Use Standard J-STD-016-1995, presented at EIA/IEEE Joint Industries Standard
Working Group March 4, 1996.
3. DeWeese, Perry, U.S. Implementation of ISO/IEC 12207: U.S. Plan for Standardization , presented at
EIA/IEEE Joint Industries Standard Working Group March 4, 1996.
STSC MIL-STD-498 Workshop
The Software Technology Support Center is offering a one-day workshop on MIL-STD-498, Software
Development and Documentation. The workshop, provided on a fee-for-service basis to Department of
Defense (DoD) agencies and supporting contractors, is designed to bring all participants to a common level
of understanding regarding
· The need for MIL-STD-498.
· What is in MIL-STD-498.
· Hands-on tailoring of MIL-STD-498.
The workshop is performed at your location.
Who should attend? Anyone involved in the acquisition or management of software for DoD including
team leads, project managers, and program managers. The format of the workshop consists of lecture, brief
discussion exercises, and hands-on tailoring exercises. At the conclusion of the workshop, participants will
be able to understand
· DoD policies and standards that pertain to software development and documentation.
· Differences between MIL-STD-498 and DOD-STD-2167A.
· The requirements of MIL-STD-498.
· The relationship of MIL-STD-498 to J-STD-016 and US 12207.
· The relationship of MIL-STD-498 to the Software Engineering Institute's Capability Maturity Model
(CMM).
· Basic concepts of tailoring MIL-STD-498.
Participants are provided a copy of MIL-STD-498, the 22 DIDs, and the Overview and Tailoring
Guidebook developed by Logicon.
The workshop is organized in four sections:
1. Background on software standards.
2. Description of MIL-STD-498 and DIDs.
4 of 5 28-Jun-00 16:48
MIL-STD-498, J-STD-016, and the U.S. Commercial Standard http://stsc.hill.af.mil/crosstalk/1996/jun/jstd016.asp
3. MIL-STD-498 and the CMM.
4. Tailoring for MIL-STD-498.
This workshop can help you make MIL-STD-498 a useful interim steppingstone on the path to commercial
standards.
Reed Sorensen
5 of 5 28-Jun-00 16:48
