|
<p class="MsoNormal" align="center" style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; tab-stops: 36.0pt 72.0pt 108.0pt 144.0pt 180.0pt 216.0pt 252.0pt 288.0pt 324.0pt 360.0pt 396.0pt 432.0pt;"><b style="mso-bidi-font-weight: normal;"><span lang="EN-US"><font face="Times New Roman">Administrative Information</font></span></b></p><p class="MsoNormal" align="center" style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; tab-stops: 36.0pt 72.0pt 108.0pt 144.0pt 180.0pt 216.0pt 252.0pt 288.0pt 324.0pt 360.0pt 396.0pt 432.0pt;"><span lang="EN-US"><p><font face="Times New Roman"> </font></p></span></p><p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt; tab-stops: 36.0pt 72.0pt 108.0pt 144.0pt 180.0pt 216.0pt 252.0pt 288.0pt 324.0pt 360.0pt 396.0pt 432.0pt;"><span lang="EN-US"><font face="Times New Roman">This document is to be used<span style="mso-spacerun: yes;"> </span>as guidance for use by Software Project Managers<span style="mso-spacerun: yes;"> </span>at the Space and <placename wst="on">Naval</placename> <placename wst="on">Warfare</placename> <placename wst="on">Systems</placename> <placetype wst="on">Center</placetype>, <city wst="on"><place wst="on">San Diego</place></city> hereinafter referred to as SSC San Diego.<span style="mso-spacerun: yes;"> </span>SEPO assumes responsibility for this document and updates it as required to meet the needs of users within SSC San Diego.<span style="mso-spacerun: yes;"> </span>SEPO welcomes and solicits feedback from users of this document so that future revisions of this document will reflect improvements, based on organizational experience and lessons learned.<span style="mso-spacerun: yes;"> </span>SEPO provides copies of this document to students attending SEPO training courses and workshops as well as copies upon request to others in accordance with this document's distribution statement.</font></span></p><p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt; tab-stops: 36.0pt 72.0pt 108.0pt 144.0pt 180.0pt 216.0pt 252.0pt 288.0pt 324.0pt 360.0pt 396.0pt 432.0pt;"><span lang="EN-US"><font face="Times New Roman">If you have any questions or comments regarding this document please feel free to communicate them via the Document Change Request (DCR) form located at the back of this document.</font></span></p><p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt; tab-stops: 36.0pt 72.0pt 108.0pt 144.0pt 180.0pt 216.0pt 252.0pt 288.0pt 324.0pt 360.0pt 396.0pt 432.0pt;"><span lang="EN-US"><p><font face="Times New Roman"> </font></p></span></p><p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt; tab-stops: 36.0pt 72.0pt 108.0pt 144.0pt 180.0pt 216.0pt 252.0pt 288.0pt 324.0pt 360.0pt 396.0pt 432.0pt;"><span lang="EN-US"><p><font face="Times New Roman"> </font></p></span></p><p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt; tab-stops: 36.0pt 72.0pt 108.0pt 144.0pt 180.0pt 216.0pt 252.0pt 288.0pt 324.0pt 360.0pt 396.0pt 432.0pt;"><b style="mso-bidi-font-weight: normal;"><span lang="EN-US"><font face="Times New Roman">Approved for public release; distribution is unlimited.<p></p></font></span></b></p><p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt; tab-stops: 36.0pt 72.0pt 108.0pt 144.0pt 180.0pt 216.0pt 252.0pt 288.0pt 324.0pt 360.0pt 396.0pt 432.0pt;"><b style="mso-bidi-font-weight: normal;"><span lang="EN-US"><p><font face="Times New Roman"> </font></p></span></b></p><p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt; tab-stops: 36.0pt 72.0pt 108.0pt 144.0pt 180.0pt 216.0pt 252.0pt 288.0pt 324.0pt 360.0pt 396.0pt 432.0pt;"><b style="mso-bidi-font-weight: normal;"><span lang="EN-US"><p><font face="Times New Roman"> </font></p></span></b></p><p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt; tab-stops: 36.0pt 72.0pt 108.0pt 144.0pt 180.0pt 216.0pt 252.0pt 288.0pt 324.0pt 360.0pt 396.0pt 432.0pt;"><span lang="EN-US"><font face="Times New Roman">Brian Groarke, SEPO, SSC San Diego D13</font></span></p><p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt; tab-stops: 36.0pt 72.0pt 108.0pt 144.0pt 180.0pt 216.0pt 252.0pt 288.0pt 324.0pt 360.0pt 396.0pt 432.0pt;"><span lang="EN-US"><font face="Times New Roman">Voice 619)553-6248, Fax 619)553-6249, Internet: groarke@spawar.navy.mil</font></span></p><p><b style="mso-bidi-font-weight: normal;"><span lang="EN-US" style="FONT-SIZE: 10.5pt; TEXT-TRANSFORM: uppercase; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-size: 12.0pt; mso-fareast-font-family: 宋体; mso-ansi-language: EN-US; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA; mso-font-kerning: 1.0pt;"><br clear="all" style=" AGE-BREAK-BEFORE: always;"/></span></b> </p><p class="TOC-title" style="MARGIN: 0cm 0cm 0pt;"><span lang="EN-US"><strong><font face="Times New Roman"> reface</font></strong></span></p><p class="TOC-title" style="MARGIN: 0cm 0cm 0pt;"><span lang="EN-US"><p><strong><font face="Times New Roman"> </font></strong></p></span></p><p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt;"><span lang="EN-US"><font face="Times New Roman">The purpose of the Software Project Planning (SPP) Process is to satisfy the requirements of the Level 2 Software Project Planning (SPP) Key Process Area of the Software Capability Maturity Model. Updates to this process will be made as comments are received from the users.<span style="mso-spacerun: yes;"> </span>The flow diagram of this process is shown in Figure 1-1.<span style="mso-spacerun: yes;"> </span>The SPP process requires the use of several other SSC San Diego processes, including the Requirements Management Guidebook, the Software Size, Cost and Schedule Estimation process, the Formal Inspection process, the Software Configuration Management process, the Software Project Tracking and Oversight process, the Contractor Acquisition and Performance Monitoring (CAPM) process, the Software Product Engineering (SPE) Implementation Guide, and the Software Quality Assurance process.</font></span></p><p></p><p>全文阅读请打开附件:
qBwu7Ft7.doc
(192 KB, 下载次数: 9)
<br/></p><p></p> |
|