25:
129:(PMBOK). The document "MIL-STD-498 Overview and Tailoring Guidebook" is 98 pages. The "MIL-STD-498 Application and Reference Guidebook" is 516 pages. Associated to these were document templates, or Data Item Descriptions, described below, bringing documentation and process order that could scale to projects of the size humans were then conducting (aircraft, battleships, canals, dams, factories, satellites, submarines, etcetera).
163:, a file or document that describes the system or some aspect of the system life cycle. These documents could take many forms, from source code, to installation scripts, to various electronic and paper reports, and the government contracting party is encouraged to specify acceptable formats. Any software development project (effort) was expected to make selections from the 22 possible documents and list the selections in the
171:
for a specific contract, meaning sections in the standard DID which are not desired for that contract will be identified in the section of the CDRL form provided for that purpose. Exactly which DIDs and what parts of the DIDs are required for a particular system depends on the nature of the project
478:
In the latter '90's and early 2000's, DO-178B gradually eclipsed MIL-STD-498 for numerous reasons including avionics commonality between civil and military applications, re-use, improved supplier management, improved schedule and cost performance ... and tighter integration with provable safety
159:(DIDs), which were standardized documents for recording the results of each the development and support processes, for example, the Software Design Description DID was the standard format for the results of the software design process. Each DID generically describes the required content of a
140:. Several programs outside of the U.S. military continued to use the standard due to familiarity and perceived advantages over alternative standards, such as free availability of the standards documents and presence of process detail including contractually-usable Data Item Descriptions.
113:
Unlike previous efforts like the seminal DOD-STD-2167A which was mainly focused on the risky new area of software development, MIL-STD-498 was the first attempt at comprehensive description of the
167:(CDRL) form within the Uniform Contract Format. A CDRL lists the data items which are to be produced and delivered by a contractor as part of that contract. Any Data Item Description is
132:
It was one of the few military standards that survived the "Perry Memo", then U.S. Secretary of
Defense William Perry's 1994 memorandum commanding the discontinuation of
497:
329:
423:
136:. However, it was canceled on May 27, 1998, and replaced by the essentially identical demilitarized version EIA J-STD-016 as a process example guide for
502:
260:
Software Center
Operator Manual (SCOM) - Instructions for operators of a batch or interactive software system that is installed in a computer center
94:
whose purpose was to "establish uniform requirements for software development and documentation." It was released Nov. 8, 1994, and replaced
257:
Software Input/Output Manual (SIOM) - Instructions for users of a batch or interactive software system that is installed in a computer center
445:
126:
46:
400:
385:
370:
355:
378:
125:) that followed it. It also contains much of the material that the subsequent professionalization of project management covered in the
311:
68:
507:
164:
133:
114:
286:
Software
Product Specification (SPS) - The executable software, the source files, and information to be used for support
206:
Software
Requirements Specification (SRS) - The requirements to be met by a Computer Software Configuration Item (CSCI)
110:. It was meant as an interim standard, to be in effect for about two years until a commercial standard was developed.
39:
33:
143:
In military airborne software, MIL-STD-498 was gradually eclipsed by the civilian airborne software guideline, RTCA
363:
50:
118:
431:
156:
348:
103:
340:
107:
449:
318:
300:
209:
Interface
Requirements Specification (IRS) - The requirements for one or more interfaces
289:
Software
Version Description (SVD) - A list of delivered files and related information
491:
95:
187:
Software
Installation Plan (SIP) - A plan for installing the software at user sites
99:
241:
Software Test
Description (STD) - Test cases/procedures for qualification testing
190:
Software
Transition Plan (STrP) - A plan for transitioning to the support agency
184:
Software
Development Plan (SDP) - A plan for performing the software development
155:
MIL-STD-498 standard describes the development and documentation in terms of 22
301:"MIL-STD-498 PDF Roadmap, documents types mentioned in order or life-cycle use"
203:
System/Subsystem Specification (SSS) - The requirements to be met by the system
393:
200:
Operational Concept Description (OCD) - The operational concept for the system
137:
122:
276:
Firmware Support Manual (FSM) - Instructions for programming firmware devices
254:
Software User Manual (SUM) - Instructions for hands-on users of the software
312:"Abelia example DID, System/Subsystem Specification as used in MIL-STD-498"
273:
Computer Programming Manual (CPM) - Instructions for programming a computer
228:
Interface Design Description (IDD) - The design of one or more interfaces
263:
Computer Operation Manual (COM) - Instructions for operating a computer
144:
91:
238:
Software Test Plan (STP) - A plan for conducting qualification testing
219:
System/Subsystem Design Description (SSDD) - The design of the system
244:
Software Test Report (STR) - Test results of qualification testing
466:
394:"MIL-STD-498, APPLICATION AND REFERENCE GUIDEBOOK (section 5)"
18:
225:
Database Design Description (DBDD) - The design of a database
117:. MIL-STD-498 was the baseline for industry standards (e.g.
424:"MIL-STD-498, J-STD-016, and the U.S. Commercial Standard"
222:
Software Design Description (SDD) - The design of a CSCI
87:
Military Standard Software Development and Documentation
454:
J-STD-016 is the "demilitarized" version of Mil-STD-498
172:
and how parts of it are being produced by contract(s).
349:"MIL-STD-498, SOFTWARE DEVELOPMENT AND DOCUMENTATION"
467:"Aviation Development & Certification Tech Info"
379:"MIL-STD-498, APPLICATION AND REFERENCE GUIDEBOOK"
341:"DOD-STD-2167 DEFENSE SYSTEM SOFTWARE DEVELOPMENT"
330:"Software Standards Evolution and Current State"
364:"MIL-STD-498, OVERVIEW AND TAILORING GUIDEBOOK"
8:
16:US military standard for software projects
69:Learn how and when to remove this message
32:This article includes a list of general
498:Military of the United States standards
414:
7:
127:Project Management Body of Knowledge
401:United States Department of Defense
386:United States Department of Defense
371:United States Department of Defense
356:United States Department of Defense
38:it lacks sufficient corresponding
14:
503:Software engineering publications
23:
165:Contract Data Requirements List
115:systems development life-cycle
1:
422:Reed Sorensen (June 1996).
281:Software product definition
233:Qualification test products
524:
53:more precise citations.
508:Software documentation
335:. CrossTalk. Dec 1999.
157:Data Item Descriptions
151:Data Item Descriptions
90:, was a United States
249:User/operator manuals
446:"Software Standards"
195:Concept/requirements
428:CrossTalk Magazine
134:defense standards
92:military standard
79:
78:
71:
515:
482:
481:
475:
474:
463:
457:
456:
448:. Archived from
442:
436:
435:
430:. Archived from
419:
404:
398:
389:
383:
374:
368:
359:
353:
344:
336:
334:
325:
323:
317:. Archived from
316:
307:
305:
123:IEEE 122077-2017
74:
67:
63:
60:
54:
49:this article by
40:inline citations
27:
26:
19:
523:
522:
518:
517:
516:
514:
513:
512:
488:
487:
486:
485:
472:
470:
465:
464:
460:
452:on 2013-03-17.
444:
443:
439:
421:
420:
416:
411:
396:
392:
381:
377:
366:
362:
351:
347:
339:
332:
328:
321:
314:
310:
303:
299:
296:
283:
270:
268:Support manuals
251:
235:
216:
197:
181:
153:
75:
64:
58:
55:
45:Please help to
44:
28:
24:
17:
12:
11:
5:
521:
519:
511:
510:
505:
500:
490:
489:
484:
483:
458:
437:
434:on 2004-12-16.
413:
412:
410:
407:
406:
405:
390:
375:
360:
345:
337:
326:
324:on 2021-09-26.
308:
295:
294:External links
292:
291:
290:
287:
282:
279:
278:
277:
274:
269:
266:
265:
264:
261:
258:
255:
250:
247:
246:
245:
242:
239:
234:
231:
230:
229:
226:
223:
220:
215:
212:
211:
210:
207:
204:
201:
196:
193:
192:
191:
188:
185:
180:
177:
175:The DIDs are:
152:
149:
77:
76:
31:
29:
22:
15:
13:
10:
9:
6:
4:
3:
2:
520:
509:
506:
504:
501:
499:
496:
495:
493:
480:
468:
462:
459:
455:
451:
447:
441:
438:
433:
429:
425:
418:
415:
408:
403:. 1996-01-31.
402:
395:
391:
388:. 1996-01-31.
387:
380:
376:
373:. 1996-01-31.
372:
365:
361:
358:. 1994-12-05.
357:
350:
346:
343:. 1994-12-05.
342:
338:
331:
327:
320:
313:
309:
302:
298:
297:
293:
288:
285:
284:
280:
275:
272:
271:
267:
262:
259:
256:
253:
252:
248:
243:
240:
237:
236:
232:
227:
224:
221:
218:
217:
213:
208:
205:
202:
199:
198:
194:
189:
186:
183:
182:
178:
176:
173:
170:
166:
162:
158:
150:
148:
146:
141:
139:
135:
130:
128:
124:
120:
119:IEEE 828-2012
116:
111:
109:
105:
104:DOD-STD-7935A
101:
97:
96:DOD-STD-2167A
93:
89:
88:
83:
73:
70:
62:
52:
48:
42:
41:
35:
30:
21:
20:
477:
471:. Retrieved
461:
453:
450:the original
440:
432:the original
427:
417:
319:the original
174:
168:
160:
154:
142:
131:
112:
108:DOD-STD-1703
100:DOD-STD-2168
86:
85:
81:
80:
65:
56:
37:
479:guidelines
82:MIL-STD-498
51:introducing
492:Categories
473:2022-08-08
409:References
138:IEEE 12207
59:April 2009
34:references
469:. AFuzion
161:data item
169:tailored
145:DO-178B
47:improve
214:Design
106:, and
36:, but
397:(PDF)
382:(PDF)
367:(PDF)
352:(PDF)
333:(PDF)
322:(PDF)
315:(PDF)
304:(PDF)
179:Plans
121:,
494::
476:.
426:.
399:.
384:.
369:.
354:.
147:.
102:,
98:,
84:,
306:.
72:)
66:(
61:)
57:(
43:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.