forked from bradfa/MIL-STD-498
-
Notifications
You must be signed in to change notification settings - Fork 0
/
OCD.html
executable file
·139 lines (104 loc) · 11.9 KB
/
OCD.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
<!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>OCD</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 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 to which this document applies. It shall describe the general nature of the system; 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 document 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 document. This section shall also identify the source for all documents not available through normal Government stocking activities.</p>
<h1>3. Current system or situation.</h1>
<p>This section shall be divided into the following paragraphs to describe the system or situation as it currently exists.</p>
<h2>3.1 Background, objectives, and scope.</h2>
<p>This paragraph shall describe the background, mission or objectives, and scope of the current system or situation.</p>
<h2>3.2 Operational policies and constraints.</h2>
<p>This paragraph shall describe any operational policies and constraints that apply to the current system or situation.</p>
<h2>3.3 Description of current system or situation. </h2>
<p>This paragraph shall provide a description of the current system or situation, identifying differences associated with different states or modes of operation (for example, regular, mainte-nance, training, degraded, emergency, alternative-site, wartime, peacetime). The distinction between states and modes is arbitrary. A system may be described in terms of states only, modes only, states within modes, modes within states, or any other scheme that is useful. If the system operates without states or modes, this paragraph shall so state, without the need to create artificial distinctions. The description shall include, as applicable:
<ol type="a">
<li>The operational environment and its characteristics</li><br/>
<li>Major system components and the interconnections among these components</li><br/>
<li>Interfaces to external systems or procedures</li><br/>
<li>Capabilities/functions of the current system</li><br/>
<li>Charts and accompanying descriptions depicting inputs, outputs, data flow, and manual and automated processes sufficient to understand the current system or situation from the user's point of view</li><br/>
<li>Performance characteristics, such as speed, throughput, volume, frequency</li><br/>
<li>Quality attributes, such as reliability, maintainability, availability, flexibility, portability, usability, efficiency</li><br/>
<li>Provisions for safety, security, privacy, and continuity of operations in emergencies</li>
</ol>
</p>
<h2>3.4 Users or involved personnel.</h2>
<p>This paragraph shall describe the types of users of the system, or personnel involved in the current situation, including, as applicable, organizational structures, training/skills, responsibilities, activities, and interactions with one another.</p>
<h2>3.5 Support concept.</h2>
<p>This paragraph shall provide an overview of the support concept for the current system, including, as applicable to this document, support agency(ies); facilities; equipment; support software; repair/replacement criteria; maintenance levels and cycles; and storage, distribution, and supply methods.</p>
<h1>4. Justification for and nature of changes.</h1>
<p>This section shall be divided into the following paragraphs.</p>
<h2>4.1 Justification for change. </h2>
<p>This paragraph shall:
<ol type="a">
<li>Describe new or modified aspects of user needs, threats, missions, objectives, environ-ments, interfaces, personnel or other factors that require a new or modified system</li><br/>
<li>Summarize deficiencies or limitations in the current system or situation that make it unable to respond to these factors</li>
</ol>
</p>
<h2>4.2 Description of needed changes.</h2>
<p>This paragraph shall summarize new or modified capabilities/functions, processes, interfaces, or other changes needed to respond to the factors identified in 4.1. </p>
<h2>4.3 Priorities among the changes. </h2>
<p>This paragraph shall identify priorities among the needed changes. It shall, for example, identify each change as essential, desirable, or optional, and prioritize the desirable and optional changes.</p>
<h2>4.4 Changes considered but not included.</h2>
<p>This paragraph shall identify changes considered but not included in 4.2, and rationale for not including them.</p>
<h2>4.5 Assumptions and constraints.</h2>
<p>This paragraph shall identify any assumptions and constraints applicable to the changes identi-fied in this section.</p>
<h1>5. Concept for a new or modified system. </h1>
<p>This section shall be divided into the following paragraphs to describe a new or modified system.</p>
<h2>5.1 Background, objectives, and scope.</h2>
<p>This paragraph shall describe the background, mission or objectives, and scope of the new or modified system.</p>
<h2>5.2 Operational policies and constraints.</h2>
<p>This paragraph shall describe any operational policies and constraints that apply to the new or modified system.</p>
<h2>5.3 Description of the new or modified system. </h2>
<p>This paragraph shall provide a description of the new or modified system, identifying differences associated with different states or modes of operation (for example, regular, maintenance, train-ing, degraded, emergency, alternative-site, wartime, peacetime). The distinction between states and modes is arbitrary. A system may be described in terms of states only, modes only, states within modes, modes within states, or any other scheme that is useful. If the system operates without states or modes, this paragraph shall so state, without the need to create artificial distinctions. The description shall include, as applicable:
<ol type="a">
<li>The operational environment and its characteristics</li><br/>
<li>Major system components and the interconnections among these components</li><br/>
<li>Interfaces to external systems or procedures</li><br/>
<li>Capabilities/functions of the new or modified system</li><br/>
<li>Charts and accompanying descriptions depicting inputs, outputs, data flow, and manual and automated processes sufficient to understand the new or modified system or situation from the user's point of view</li><br/>
<li>Performance characteristics, such as speed, throughput, volume, frequency</li><br/>
<li>Quality attributes, such as reliability, maintainability, availability, flexibility, portability, usability, efficiency</li><br/>
<li>Provisions for safety, security, privacy, and continuity of operations in emergencies</li>
</ol>
</p>
<h2>5.4 Users/affected personnel. </h2>
<p>This paragraph shall describe the types of users of the new or modified system, including, as applicable, organizational structures, training/skills, responsibilities, and interactions with one another.</p>
<h2>5.5 Support concept.</h2>
<p>This paragraph shall provide an overview of the support concept for the new or modified system, including, as applicable, support agency(ies); facilities; equipment; support software; repair/replacement criteria; maintenance levels and cycles; and storage, distribution, and supply methods.</p>
<h1>6. Operational scenarios. </h1>
<p>This section shall describe one or more operational scenarios that illustrate the role of the new or modified system, its interaction with users, its interface to other systems, and all states or modes identified for the system. The scenarios shall include events, actions, stimuli, information, interactions, etc., as applicable. Reference may be made to other media, such as videos, to provide part or all of this information.</p>
<h1>7. Summary of impacts. </h1>
<p>This section shall be divided into the following paragraphs.</p>
<h2>7.1 Operational impacts.</h2>
<p>This paragraph shall describe anticipated operational impacts on the user, acquirer, developer, and support agency(ies). These impacts may include changes in interfaces with computer operating centers; change in procedures; use of new data sources; changes in quantity, type, and timing of data to be input to the system; changes in data retention requirements; and new modes of operation based on peacetime, alert, wartime, or emergency conditions.</p>
<h2>7.2 Organizational impacts.</h2>
<p>This paragraph shall describe anticipated organizational impacts on the user, acquirer, developer, and support agency(ies). These impacts may include modification of responsibilities; addition or elimination of responsibilities or positions; need for training or retraining; and changes in number, skill levels, position identifiers, or location of personnel in various modes of operation. </p>
<h2>7.3 Impacts during development. </h2>
<p>This paragraph shall describe anticipated impacts on the user, acquirer, developer, and support agency(ies) during the development effort. These impacts may include meetings/discussions regarding the new system; development or modification of databases; training; parallel operation of the new and existing systems; impacts during testing of the new system; and other activities needed to aid or monitor development.</p>
<h1>8. Analysis of the proposed system.</h1>
<p></p>
<h2>8.1 Summary of advantages.</h2>
<p>This paragraph shall provide a qualitative and quantitative summary of the advantages to be obtained from the new or modified system. This summary shall include new capabilities, enhanced capabilities, and improved performance, as applicable, and their relationship to deficiencies identified in 4.1.</p>
<h2>8.2 Summary of disadvantages/limitations.</h2>
<p>This paragraph shall provide a qualitative and quantitative summary of disadvantages or limitations of the new or modified system. These disadvantages and limitations shall include, as applicable, degraded or missing capabilities, degraded or less-than-desired performance, greater-than-desired use of computer hardware resources, undesirable operational impacts, conflicts with user assumptions, and other constraints.</p>
<h2>8.3 Alternatives and trade-offs considered.</h2>
<p>This paragraph shall identify and describe major alternatives considered to the system or its characteristics, the trade-offs among them, and rationale for the decisions reached.</p>
<h1>9. 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 any 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>