-
Notifications
You must be signed in to change notification settings - Fork 6
/
SIOM.html
executable file
·220 lines (177 loc) · 16 KB
/
SIOM.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
<!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>SIOM</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 a full identification of the system and the software to which this document applies, including, as applicable, identification number(s), title(s), abbreviation(s), version number(s), and release number(s).</p>
<h2>1.2 System overview. </h2>
<p>This paragraph shall briefly state the purpose of the system and the software to which this document applies. It shall describe the general nature of the system and software; summarize the history of system development, operation, and maintenance; identify the project sponsor, acquirer, user, developer, and support agencies; identify current and planned operating sites; and list other relevant documents.</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. Software summary. </h1>
<p>This section shall be divided into the following paragraphs. </p>
<h2>3.1 Software application.</h2>
<p>This paragraph shall provide a brief description of the intended uses of the software. Capabilities, operating improvements, and benefits expected from its use shall be described.</p>
<h2>3.2 Software inventory.</h2>
<p>This paragraph shall identify the software files, if any, including databases and data files, that the user is responsible for requesting in order to access the software described in this manual. The identification shall include security and privacy considerations for each file and identification of the software necessary to continue or resume operation in case of an emergency.</p>
<h2>3.3 Software environment.</h2>
<p>This paragraph shall identify the hardware, software, manual operations, and other resources needed to access and use the software. This paragraph shall be based on the assumption that the software is installed in a computer center or other centralized or networked environment and shall focus on the resources that a user must have to access and use the software in that environment. Included, as applicable, shall be identification of:
<ol type="a">
<li>Computer equipment that must be present, such as terminals, printers, or other input/output devices</li>
<li>Communications equipment that must be present</li>
<li>Other software that must be present, such as networking software</li>
<li>Forms, procedures, or other manual operations that must be present</li>
<li>Other facilities, equipment, or resources that must be present</li>
</ol>
</p>
<h2>3.4 Software organization and overview of operation.</h2>
<p>This paragraph shall provide a brief description of the organization and operation of the software from the user's point of view. The description shall include, as applicable:
<ol type="a">
<li>Logical components of the software, from the user's point of view, including databases and data files the user can access, Database Management Systems (DBMSs), and communications paths, and an overview of the purpose/operation of each component</li><br/>
<li>Performance characteristics that can be expected by the user, such as:
<ol>
<li>Types, volumes, rate of inputs accepted</li>
<li>Types, volume, accuracy, rate of outputs that the software can produce</li>
<li>Typical response time and factors that affect it </li>
<li>Typical processing time and factors that affect it</li>
<li>Limitations, e.g, restrictions on what data may be queried and from what location</li>
<li>Error rate that can be expected </li>
<li>Reliability that can be expected</li>
</ol>
</li><br/>
<li>Relationships of the functions performed by the software with interfacing systems and with the organizations or stations that are sources of input or recipients of output</li><br/>
<li>Supervisory controls that can be implemented (such as passwords) to manage the software</li><br/>
</ol>
</p>
<h2>3.5 Contingencies and alternate states and modes of operation. </h2>
<p>This paragraph shall explain the differences in what the user will be able to do with the software at times of emergency and in various states and modes of operation, if applicable.</p>
<h2>3.6 Security and privacy. </h2>
<p>This paragraph shall contain an overview of the security and privacy considerations associated with the software. A warning shall be included regarding making unauthorized copies of software or documents, if applicable.</p>
<h2>3.7 Assistance and problem reporting. </h2>
<p>This paragraph shall identify points of contact and procedures to be followed to obtain assistance and report problems encountered in using the software.</p>
<h1>4. Using the software. </h1>
<p>This section shall be divided into the following paragraphs to describe how to prepare inputs to, and interpret output from, the software. If the software has a query capability, this paragraph shall reference section 5 for a description of this capability. If the software can be accessed via terminal, this paragraph shall reference Sections 6 through n to describe terminal processing procedures. Safety precautions, marked by WARNING or CAUTION, shall be included where applicable.</p>
<h2>4.1 Initiation procedures. </h2>
<p>This paragraph shall contain the procedures that must be followed to initiate use of the software. Included may be information such as sample job request forms or sample control statements. </p>
<h2>4.2 Description of inputs.</h2>
<p>This paragraph shall be divided into the following subparagraphs.</p>
<h3>4.2.1 Input conditions.</h3>
<p>This paragraph shall describe the conditions to be observed in preparing each type or class of input to the software. The conditions shall include the following, as applicable:
<ol type="a">
<li>Reason for input, such as normal status report, need to update data</li>
<li>Frequency of input, such as monthly, on demand </li>
<li>Origin of input, such as the organization or station authorized to generate the input</li>
<li>Medium of input, such as magnetic tape</li>
<li>Related inputs that are required to be entered at the same time as this input</li>
<li>Other applicable information, such as priority; security and privacy considerations</li>
</ol>
</p>
<h3>4.2.2 Input formats. </h3>
<p>This paragraph shall illustrate the layout formats to be used in the preparation of inputs to the software and shall explain the information that may be entered in the various sections and lines of each format. </p>
<h3>4.2.3 Composition rules.</h3>
<p>This paragraph shall describe any rules and conventions that must be observed to prepare inputs. The rules of syntax, usage of punctuation, etc., shall be explained. The rules shall include the following, as applicable:
<ol type="a">
<li>Input transaction length, such as 100 characters maximum</li>
<li>Format conventions, such as all input items must be left-justified</li>
<li>Labeling, such as usage of identifiers to denote major data sets to the software</li>
<li>Sequencing, such as order and placement of items in the input</li>
<li>Punctuation, such as spacing and use of symbols (virgule, asterisk, character combina-tions, etc.) to denote start and end of input, of data groups, and of fields</li>
<li>Restrictions, such as rules forbidding use of particular characters or parameter sets </li>
</ol>
</p>
<h3>4.2.4 Input vocabulary.</h3>
<p>This paragraph shall explain the legal character combinations or codes that must be used to prepare inputs. An appendix may be provided containing an ordered listing of these codes.</p>
<h3>4.2.5 Sample inputs. </h3>
<p>This paragraph shall provide examples that illustrate and explain each type or class of input acceptable by the software. Included shall be information on the following types of inputs, as applicable:
<ol type="a">
<li>Headers denoting the start of input </li>
<li>Text or body of the input </li>
<li>Trailers denoting the end of input </li>
<li>Portions of the input that may be omitted </li>
<li>Portions of the input that may be repeated </li>
</ol>
</p>
<h2>4.3 Description of outputs. </h2>
<p>This paragraph shall be divided into the following subparagraphs.</p>
<h3>4.3.1 General description.</h3>
<p>This paragraph shall provide the following information, as applicable, for each type or class of output:
<ol type="a">
<li>Reasons why the output is generated</li>
<li>Frequency of the output, such as monthly, on demand </li>
<li>Any modifications or variations of the basic output that are available</li>
<li>Media, such as printout, display screen, tape</li>
<li>Location where the output will appear, such as in the computer area or remotely</li>
<li>Any additional characteristics, such as priority, security and privacy considerations, associated outputs that complement the information in this output</li>
</ol>
</p>
<h3>4.3.2 Output formats.</h3>
<p>This paragraph shall illustrate and explain the layout of each type or class of output from the software. The following aspects shall be explained, as applicable:
<ol type="a">
<li>Security and privacy markings</li>
<li>Data that may appear in headers</li>
<li>Information that may appear in the body or text of the output, including column headings and subsets or sections in the output format</li>
<li>Data that may appear in trailers </li>
<li>Additional characteristics, such as the meaning of special symbols</li>
</ol>
</p>
<h3>4.3.3 Sample outputs.</h3>
<p>This paragraph shall provide illustrations of each type or class of output from the software. A description of each sample shall be provided, including, as applicable:
<ol type="a">
<li>Meaning and use of each column, entry, etc.</li>
<li>Source, such as extracted from database, calculated</li>
<li>Characteristics, such as when omitted, range of values, unit of measure</li>
</ol>
</p>
<h3>4.3.4 Output vocabulary.</h3>
<p>This paragraph shall describe any codes or abbreviations that appear in the output that differ from those used in the input described in paragraph 4.2.4.</p>
<h2>4.4 Use of outputs. </h2>
<p>This paragraph shall explain the use of the output by the operational area or activity that receives it. </p>
<h2>4.5 Recovery and error correction procedures.</h2>
<p>This paragraph shall list the error codes generated by the software, give their meanings, and describe the corrective actions to be taken by the user. Also included shall be the procedures to be followed by the user with respect to restart, recovery, and continuity of operations in the event of emergencies.</p>
<h2>4.6 Communications diagnostics.</h2>
<p>This paragraph shall describe the diagnostic procedures available to the user for validating communications and for identifying and classifying problems. </p>
<h1>5. Query procedures. </h1>
<p>This section shall be prepared for software with a query capability. It shall be divided into the following paragraphs.</p>
<h2>5.1 Database/data file format.</h2>
<p>This paragraph shall provide a user's view of the format and content of each database and data file that can be queried. Figure 1 provides an example. Information such as the following shall be provided for each data element, as applicable:
<ol type="a">
<li>Data element name</li>
<li>Synonymous names</li>
<li>Definition</li>
<li>Format</li>
<li>Range and enumeration of values</li>
<li>Unit of measurement</li>
<li>Data item names, abbreviations, and codes</li>
</ol>
</p>
<h2>5.2 Query capabilities. </h2>
<p>This paragraph shall identify and describe the preprogrammed and ad hoc query capabilities provided by the software. An example of preprogrammed queries is shown in Figure 2.</p>
<h2>5.3 Query preparation. </h2>
<p>This paragraph shall provide instructions for preparing queries. Figure 3 shows an example of the format for a preprogrammed query. Figure 4 shows an example of a query statement. </p>
<h2>5.4 Control instructions.</h2>
<p>This paragraph shall provide instructions for the sequencing of runs and other actions necessary to extract responses to query requests. These instructions shall include control statements that may be required by the computer system or software. </p>
<h1>6. User terminal processing procedures.</h1>
<p>This section shall be divided into the following paragraphs to provide the user with information on the use of terminals to accomplish processing. If the procedures are complicated or extensive, Sections 7 through n may be added in the same paragraph structure as this section and with titles meaningful to the sections selected. The organization of the document will depend on the characteristics of the software being documented. For example, sections might be based on the organizations in which users work, their assigned positions, work sites, or the tasks they must perform. For other software, it may be more appropriate to have Section 6 be a guide to menus, Section 7 be a guide to the command language, and Section 8 be a guide to functions. Detailed procedures are intended to be presented in paragraphs 6.2 through 6.5. Depending on the design of the software, the subparagraphs might be organized on a function by function, menu by menu, transaction-by-transaction, or other basis. Safety precautions, marked by WARNING or CAUTION, shall be included where applicable.</p>
<h2>6.1 Available capabilities.</h2>
<p>This paragraph shall describe in general terms the capabilities for retrieval, display, and update of data through terminal operations. </p>
<h2>6.2 Access procedures.</h2>
<p>This paragraph shall present the sequence of steps and any applicable rules pertaining to accessing the software to initiate software operations. </p>
<h2>6.3 Display, updates, and retrieval procedures. </h2>
<p>This paragraph shall be divided into subparagraphs to provide the step-by-step procedures necessary to produce the displays, updates, and retrievals that are available through the use of a terminal. Each procedure shall include the name of the operation, input formats, and sample responses, as applicable.</p>
<h2>6.4 Recovery and error correction procedures. </h2>
<p>This paragraph shall identify error messages that may be displayed and shall indicate their meanings and any corrective actions that should be taken. Also included shall be any procedures to be followed by the user with respect to restart, recovery, and continuity of operations in the event of emergencies.</p>
<h2>6.5 Termination procedures.</h2>
<p>This paragraph shall present the sequence of steps necessary to terminate the processing.</p>
<h1>7. 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. If section 6 has been expanded into section(s) 7,..., this section shall be numbered as the next section following section n.</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>