Skip to content
Find file
Fetching contributors…
Cannot retrieve contributors at this time
executable file 125 lines (101 sloc) 10.8 KB
<!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>STRP</title>
</head>
<body>
<h1>1. Scope. </h1>
<p>This section shall be divided into the following paragraphs.</p>
<h1></h1>
<p></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 document and shall describe any security or privacy considerations associated with its use.</p>
<h2>1.4 Relationship to other plans. </h2>
<p>This paragraph shall describe the relationship, if any, of the STrP to other project management plans.</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. Software support resources. </h1>
<p>This section shall be divided into paragraphs to identify and describe the resources needed to support the deliverable software. These resources shall include items needed to control, copy, and distribute the software and its documentation, and to specify, design, implement, document, test, evaluate, control, copy, and distribute modifications to the software.</p>
<h2>3.1 Facilities. </h2>
<p>This paragraph shall describe the facilities needed to support the deliverable software. These facilities may include special buildings, rooms, mock-ups, building features such as raised flooring or cabling; building features to support security and privacy requirements (TEMPEST shielding, vaults, etc.), building features to support safety requirements (smoke alarms, safety glass, etc.), special power requirements, and so on. The purpose of each item shall be described. Diagrams may be included as applicable.</p>
<h2>3.2 Hardware. </h2>
<p>This paragraph shall identify and describe the hardware and associated documentation needed to support the deliverable software. This hardware may include computers, peripheral equipment, hardware simulators, stimulators, emulators, diagnostic equipment, and non-computer equipment. The description shall include:
<ol type="a">
<li>Specific models, versions, and configurations</li><br/>
<li>Rationale for the selected hardware</li><br/>
<li>Reference to user/operator manuals or instructions for each item, as applicable</li><br/>
<li>Identification of each hardware item and document as acquirer-furnished, an item that will be delivered to the support agency, an item the support agency is known to have, an item the support agency must acquire, or other description of status</li><br/>
<li>If items must be acquired, information about a current source of supply, including whether the item is currently available and whether it is expected to be available at the time of delivery</li><br/>
<li>Information about manufacturer support, licensing, and data rights, including whether the item is currently supported by the manufacturer, whether it is expected to be supported at the time of delivery, whether licenses will be assigned to the support agency, and the terms of such licenses</li><br/>
<li>Security and privacy considerations, limitations, or other items of interest</li>
</ol>
</p>
<h2>3.3 Software.</h2>
<p>This paragraph shall identify and describe the software and associated documentation needed to support the deliverable software. This software may include computer-aided software engineering (CASE) tools, data in these tools, compilers, test tools, test data, simulations, emulations, utilities, configuration management tools, databases and data files, and other software. The description shall include:
<ol type="a">
<li>Specific names, identification numbers, version numbers, release numbers, and configurations, as applicable</li><br/>
<li>Rationale for the selected software</li><br/>
<li>Reference to user/operator manuals or instructions for each item, as applicable</li><br/>
<li>Identification of each software item and document as acquirer-furnished, an item that will be delivered to the support agency, an item the support agency is known to have, an item the support agency must acquire, or other description of status</li><br/>
<li>If items must be acquired, information about a current source of supply, including whether the item is currently available and whether it is expected to be available at the time of delivery</li><br/>
<li>Information about vendor support, licensing, and data rights, including whether the item is currently supported by the vendor, whether it is expected to be supported at the time of delivery, whether licenses will be assigned to the support agency, and the terms of such licenses</li><br/>
<li>Security and privacy considerations, limitations, or other items of interest</li>
</ol>
</p>
<h2>3.4 Other documentation. </h2>
<p>This paragraph shall identify any other documentation needed to support the deliverable software. The list will include, for example, plans, reports, studies, specifications, design descriptions, test cases/procedures, test reports, user/operator manuals, and support manuals for the deliverable software. This paragraph shall provide:
<ol type="a">
<li>Names, identification numbers, version numbers, and release numbers, as applicable</li><br/>
<li>Rationale for including each document in the list</li><br/>
<li>Identification of each document as acquirer-furnished, an item that will be delivered to the support agency, an item the support agency is known to have, an item the support agency must acquire, or other description of status</li><br/>
<li>If a document must be acquired, information about where to acquire it</li><br/>
<li>Information about licensing and data rights</li><br/>
<li>Security and privacy considerations, limitations, or other items of interest</li>
</ol>
</p>
<h2>3.5 Personnel.</h2>
<p>This paragraph shall describe the personnel needed to support the deliverable software, including anticipated number of personnel, types and levels of skills and expertise, and security clearances. This paragraph shall cite, as applicable, actual staffing on the development project as a basis for the staffing needs cited.</p>
<h2>3.6 Other resources. </h2>
<p>This paragraph shall describe the personnel needed to support the deliverable software, including anticipated number of personnel, types and levels of skills and expertise, and security clearances. This paragraph shall cite, as applicable, actual staffing on the development project as a basis for the staffing needs cited.</p>
<h2>3.6 Other resources. </h2>
<p>This paragraph shall identify any other resources needed to support the deliverable software. Included may be consumables such as magnetic tapes and diskettes, together with an estimate of the type and number that should be acquired.</p>
<h2>3.7 Interrelationship of components. </h2>
<p>This paragraph shall identify the interrelationships of the components identified in the preceding paragraphs. A figure may be used to show the interrelationships.</p>
<h1>4. Recommended procedures. </h1>
<p>This section shall be divided into paragraphs as needed to describe any procedures, including advice and lessons learned, that the developer may wish to recommend to the support agency for supporting the deliverable software and associated support environment. </p>
<h1>5. Training. </h1>
<p>This section shall be divided into paragraphs as appropriate to describe the developer's plans for training support personnel to support of the deliverable software. This section shall include:
<ol type="a">
<li>The schedule, duration, and location for the training </li><br/>
<li>The delineation between classroom training and "hands on" training</li><br/>
<li>Provision (either directly or by reference) for:
<ol>
<li>Familiarization with the operational software and target computer(s)</li>
<li>Familiarization with the support software and host system</li>
</ol>
</li><br/>
</ol>
</p>
<h1>6. Anticipated areas of change.</h1>
<p>This section shall describe anticipated areas of change to the deliverable software.</p>
<h1>7. Transition planning.</h1>
<p>This section shall be divided into paragraphs as needed to describe the developer's plans for transitioning the deliverable software to the support agency. This section shall address the following:
<ol type="a">
<li>All activities to be performed to transition the deliverable software to the support agency. These activities may include planning/coordination meetings; preparation of items to be delivered to the support agency; packaging, shipment, installation, and checkout of the software support environment; packaging, shipment, installation, and checkout of the operational software; and training of support personnel.</li><br/>
<li>Roles and responsibilities for each activity</li><br/>
<li>The resources needed to carry out the transition activities and the source from which each resource will be provided</li><br/>
<li>Schedules and milestones for conducting the transition activities. These schedules and milestones shall be compatible with the contract master schedule. </li><br/>
<li>Procedures for installation and checkout of deliverable items in the support environment </li>
</ol>
</p>
<h1>8. 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>
Something went wrong with that request. Please try again.