Permalink
Browse files

MIL-STD-498 HTML from kkovacs.eu

  • Loading branch information...
bradfa committed Jul 24, 2012
1 parent 99913c7 commit 2ed55b8562890708b0096b1abb84ea216ba83e25
Showing with 3,313 additions and 0 deletions.
  1. +82 −0 COM.html
  2. +96 −0 CPM.html
  3. +167 −0 DBDD.html
  4. +73 −0 FSM.html
  5. +116 −0 IDD.html
  6. +134 −0 IRS.html
  7. +139 −0 OCD.html
  8. +126 −0 SCOM.html
  9. +228 −0 SDD.html
  10. +369 −0 SDP.html
  11. +220 −0 SIOM.html
  12. +133 −0 SIP.html
  13. +91 −0 SPS.html
  14. +210 −0 SRS.html
  15. +159 −0 SSDD.html
  16. +211 −0 SSS.html
  17. +169 −0 STD.html
  18. +141 −0 STP.html
  19. +117 −0 STR.html
  20. +124 −0 STRP.html
  21. +145 −0 SUM.html
  22. +63 −0 SVD.html
View
@@ -0,0 +1,82 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<title>COM</title>
+</head>
+<body>
+
+<h1>1. Scope.</h1>
+<p>This section shall be divided into the following paragraphs.</p>
+
+<h2>1.1 Identification.</h2>
+<p>This paragraph shall contain the manufacturer's name, model number, and any other identifying information for the computer system to which this COM applies.</p>
+
+<h2>1.2 Computer system overview.</h2>
+<p>This paragraph shall briefly state the purpose of the computer system to which this COM applies.</p>
+
+<h2>1.3 Document overview.</h2>
+<p>This paragraph shall summarize the purpose and contents of this manual and shall describe any security or privacy considerations associated with its use.</p>
+
+<h1>2. Referenced documents.</h1>
+<p>This section shall list the number, title, revision, and date of all documents referenced in this manual. This section shall also identify the source for all documents not available through normal Government stocking activities.</p>
+
+<h1>3. Computer system operation.</h1>
+<p>This section shall be divided into the following paragraphs. Safety precautions, marked by WARNING or CAUTION, shall be included where applicable.</p>
+
+<h2>3.1 Computer system preparation and shutdown.</h2>
+<p>This paragraph shall be divided into the following subparagraphs.</p>
+
+<h3>3.1.1 Power on and off.</h3>
+<p>This paragraph shall contain the procedures necessary to power on and power off the computer system.</p>
+
+<h3>3.1.2 Initiation.</h3>
+<p>This paragraph shall contain the procedures necessary to initiate operation of the computer system, including, as applicable, equipment setup, pre operation, bootstrapping, and commands typically used during computer system initiation. </p>
+
+<h3>3.1.3 Shutdown.</h3>
+<p>This paragraph shall contain the procedures necessary to terminate computer system operation.</p>
+
+<h2>3.2 Operating procedures.</h2>
+<p>This paragraph shall be divided into the following subparagraphs. If more than one mode of operation is available, instructions for each mode shall be provided.</p>
+
+<h3>3.2.1 Input and output procedures.</h3>
+<p>This paragraph shall describe the input and output media (e.g., magnetic disk, tape) relevant to the computer system, state the procedures to read and write on these media, briefly describe the operating system control language, and list procedures for interactive messages and replies (e.g, terminals to use, passwords, keys).</p>
+
+<h3>3.2.2 Monitoring procedures.</h3>
+<p>This paragraph shall contain the procedures to be followed for monitoring the computer system in operation. It shall describe available indicators, interpretation of those indicators, and routine and special monitoring procedures to be followed.</p>
+
+<h3>3.2.3 Off line procedures.</h3>
+<p>This paragraph shall contain the procedures necessary to operate all relevant off line equipment of the computer system.</p>
+
+<h3>3.2.4 Other procedures.</h3>
+<p>This paragraph shall contain any additional procedures to be followed by the operator (e.g., computer system alarms, computer system security or privacy considerations, switch over to a redundant computer system, or other measures to ensure continuity of operations in the event of emergencies).</p>
+
+<h2>3.3 Problem-handling procedures.</h2>
+<p>This paragraph shall identify problems that may occur in any step of operation described in the preceding paragraphs in Section 3. It shall state the error messages or other indications accompanying those problems and shall describe the automatic and manual procedures to be followed for each occurrence, including, as applicable, evaluation techniques, conditions requiring computer system shutdown, procedures for on-line intervention or abort, steps to be taken to restart computer system operation after an abort or interruption of operation, and procedures for recording information concerning a malfunction.</p>
+
+<h1>4. Diagnostic features.</h1>
+<p>This section shall be divided into the following paragraphs to describe diagnostics that may be performed to identify and troubleshoot malfunctions in the computer system.</p>
+
+<h2>4.1 Diagnostic features summary.</h2>
+<p>This paragraph shall summarize the diagnostic features of the computer system, including error message syntax and hierarchy for fault isolation. This paragraph shall describe the purpose of each diagnostic feature.</p>
+
+<h2>4.2 Diagnostic procedures.</h2>
+<p>This paragraph shall be divided into subparagraphs as needed to describe the diagnostic proce-dures to be followed for the computer system, including:
+<ol type="a">
+ <li>Identification of hardware, software, or firmware necessary for executing each procedure</li><br/>
+ <li>Step by step instructions for executing each procedure</li><br/>
+ <li>Diagnostic messages and the corresponding required action</li><br/>
+</ol>
+</p>
+
+<h2>4.3 Diagnostic tools.</h2>
+<p>This paragraph shall be divided into subparagraphs as needed to describe the diagnostics tools available for the computer system. These tools may be hardware, software, or firmware. This paragraph shall identify each tool by name and number and shall describe the tool and its application.</p>
+
+<h1>5. Notes.</h1>
+<p>This section shall contain any general information that aids in understanding this document (e.g., background information, glossary, rationale). This section shall include an alphabetical listing of all acronyms, abbreviations, and their meanings as used in this document and a list of terms and definitions needed to understand this document.</p>
+
+<h1>A. Appendixes.</h1>
+<p>Appendixes may be used to provide information published separately for convenience in document maintenance (e.g., charts, classified data). As applicable, each appendix shall be referenced in the main body of the document where the data would normally have been provided. Appendixes may be bound as separate documents for ease in handling. Appendixes shall be lettered alphabetically (A, B, etc.).</p>
+
+</body>
+</html>
View
@@ -0,0 +1,96 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<title>CPM</title>
+</head>
+
+<body>
+
+<h1>1. Scope.</h1>
+<p>This section shall be divided into the following paragraphs.</p>
+
+<h2>1.1 Identification.</h2>
+<p>This paragraph shall contain the manufacturer's name, model number, and any other identifying information for the computer system to which this document applies.</p>
+
+<h2>1.2 Computer system overview.</h2>
+<p>This paragraph shall briefly state the purpose of the computer system to which this document applies.</p>
+
+<h2>1.3 Document overview.</h2>
+<p>This paragraph shall summarize the purpose and contents of this manual and shall describe any security or privacy considerations associated with its use.</p>
+
+<h1>2. Referenced documents.</h1>
+<p>This section shall list the number, title, revision, and date of all documents referenced in this manual. This section shall also identify the source for all documents not available through normal Government stocking activities.</p>
+
+<h1>3. Programming environment.</h1>
+<p>This section shall be divided into paragraphs as appropriate to provide the following information.
+<ol type="a">
+ <li>The components and configuration of the computer system</li><br/>
+ <li>Operating characteristics, capabilities, and limitations, including, as applicable:
+ <ol>
+ <li>Machine cycle time</li>
+ <li>Word length</li>
+ <li>Memory capacity and characteristics</li>
+ <li>Instruction set characteristics</li>
+ <li>Interrupt capabilities</li>
+ <li>Modes of operation (e.g., batch, interactive, privileged, non-privileged)</li>
+ <li>Operational registers</li>
+ <li>Error indicators Input/output characteristics</li>
+ <li>Input/output characteristics</li>
+ <li>Special features</li>
+ </ol>
+ </li><br/>
+ <li>Description of the equipment (e.g., tapes, disks, other peripheral equipment) necessary to perform compilations and assemblies on the computer system. Identify (as applicable) by name and version number the editor, linker, link editor, compiler, assembler, cross compilers, cross assemblers, and other utilities used, and reference appropriate manuals describing their use. Highlight any special flags or instructions necessary for loading, executing, or recording the results.</li>
+</ol>
+</p>
+
+<h1>4. Programming information.</h1>
+<p>This section shall be divided into paragraphs as appropriate to provide the following information.
+<ol type="a">
+ <li>Description of the programming features of the computer's instruction set architecture, including, as applicable:
+ <ol>
+ <li>Data representation (e.g., byte, word, integer, floating point, double precision)</li>
+ <li>Instruction formats and addressing modes</li>
+ <li>Special registers and words (e.g., stack pointer, program counter)</li>
+ <li>Control instructions (e.g., branch, jump, subroutine and procedure call instructions, privileged instructions, and the modes they operate in)</li>
+ <li>Subroutines and procedures (e.g., non reentrant, reentrant, macrocode routines, argument lists, parameter passing conventions)</li>
+ <li>Interrupt processing</li>
+ <li>Timers and clocks</li>
+ <li>Memory protection features (e.g., read only memory)</li>
+ <li>Additional features, such as instruction or data cache architecture</li>
+ </ol>
+ </li><br/>
+ <li>Description of each instruction, including, as applicable:
+ <ol>
+ <li>Use</li>
+ <li>Syntax</li>
+ <li>Condition codes set</li>
+ <li>Execution time</li>
+ <li>Machine code format</li>
+ <li>Mnemonic conventions</li>
+ <li>Other characteristics</li>
+ </ol>
+ </li><br/>
+ <li>Description of input and output control programming, including, as applicable:
+ <ol>
+ <li>Initial loading and verification of computer memory</li>
+ <li>Serial and parallel data channels</li>
+ <li>Discrete inputs and outputs</li>
+ <li>Interface components</li>
+ <li>Device numbers, operational codes, and memory locations for peripheral equipment</li>
+ </ol>
+ </li><br/>
+ <li>Additional, restricted, or special programming techniques associated with the computer system (e.g., a concise description of the microprogram control section)</li><br/>
+ <li>Examples that demonstrate the programming features described above, including examples of the proper use of all categories of instructions on the computer system</li><br/>
+ <li>Error detection and diagnostic features associated with the computer system, including condition codes, overflow and addressing exception interrupts, and input and output error status indicators</li><br/>
+</ol>
+</p>
+
+<h1>5. Notes.</h1>
+<p>This section shall contain any general information that aids in understanding this document (e.g., background information, glossary, rationale). This section shall include an alphabetical listing of all acronyms, abbreviations, and their meanings as used in this document and a list of terms and definitions needed to understand this document</p>
+
+<h1>A. Appendixes.</h1>
+<p>Appendixes may be used to provide information published separately for convenience in document maintenance (e.g., charts, classified data). As applicable, each appendix shall be referenced in the main body of the document where the data would normally have been provided. Appendixes may be bound as separate documents for ease in handling. Appendixes shall be lettered alphabetically (A, B, etc.).</p>
+
+</body>
+</html>
Oops, something went wrong.

0 comments on commit 2ed55b8

Please sign in to comment.