AIR FORCE MIL-HDBK-347-1990 MISSION-CRITICAL COMPUTER RESOURCES SOFTWARE SUPPORT《关键任务计算机资源的软件支持》.pdf

1、MIL-HDBK-397 MC m 7777970 005b257 2 m Mi L-H DBK-347 22 MAY 90 MILITARY HANDBOOK M ISSION-CR ITICAL COMPUTER RESOURCES SOFTWARE SUPPORT AMSC (NIA) AREA MCCR -, Approved for public release: distribution is unlimited. Provided by IHSNot for ResaleNo reproduction or networking permitted without license

2、 from IHS-,-,-FOREWORD 1. and Agencies of the Department of Defense. This military handbook is approved for use by all Departments 2. Beneficial comments (recomraendations, additions, deletions) and any pertinent; data which may be of use in improving this document should be addressed to: HQ AFSC/EN

3、R, Andrews AFB, Maryland 20334 3. The Department of Defense is comittad to maintaining the operational viability of our weapons systems and at the same time keeping support costs under control. Historicallyr software support has been a major contributor to overall life cycle costs. This standardizat

4、ion document, short titled V!he Software Support Handbookt, is an attempt to improve this situation through stanardization of relatsd concepts and management procedures, The Software Support Handbook was developed by the Department of Defense with federal agencies, and industry. It is a cornerstone

5、document, covering In pre- and post-deployment software support operatione, addition to a standard definition and detailed description of 8oftwars support and the post-deplopent software support proaess, this handbook provides guidanoe in the areas of post- deployment software support and transition

6、 planning, post- deployment software support resource analysis, software support activity resaurce requirements planning, and post-deployment software support concept alternatives. 4. Each Service or agency needs to consult applicable software standards and directives for current DoD policy and repo

7、rting formats , the assistance of the military departments, ii Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-HDBK-347 MC m 7774770 005b257 b m MIL-HDBX-3 4 7 CONTENTS PARAGRAPH 1 1.1 1.2 3 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.0 3.9 3.10 3.11 3.13 3.13

8、 3.14 3.15 3*16 3.17 3.17.1 3.17.2 3 17.2 9 1 3 17.2 2 3b18 3.19 3420 3t21 3.22 3.23 3*24 3.25 3.26 3.27 4 4.1 4.2 SCOPE 1 Scope . t 0 0 O s b O 0 S t 1 Applicability 1 APPLICABLE DOCUMENTS e . o o t 2 Government Documents . 2 Other Goverment documents, drawings, and Specifications, skandards, and h

9、andbooks . . 2 publications . 2 DEFINITIONS s o s * t 4 Acronyms used in this handbook . . . b e . 4 Baseline. 5 Computer resources 6 Computer software (or software) . 6 Computer software configuration item . 6 Computer software documentation . . . . b . . 6 Configuration 6 CSCI development proaess

10、. 7 Firmware. 7 Independent verification and validation . . . 7 Mission-crikical Computer Resources . 7 Operational version . a Post-deployment software support . 0 PDCS environment . 9 Pre-deployment software support . 9 Release . 9 Software change categories 9 Software correction . 9 Software enha

11、ncement . 9 Adaptive. 9 Perfective 9 Software development process . 9 Software engineering environment . 10 Software support . 10 Software Support Activity 10 Software test environment 10 Software transfer 10 Software transition 10 Validation. . 10 Verification . 10 Version . 10 SOFTWARE SUPPORT CON

12、CEPTS e a o o J.2 . Purpose . 12 1nt.roduction . 12 iii Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-PARAGRAPH MIL-HDBK-347 CONTENTS . PAGE -.-. - MIL-HDBK-347 MC W 9777770 0056260 2 4.3 Software support principles . 12 4.4 E%olution of software s

13、upport 13 4.4.1 Software support and the acquisition procees . 13 4.4.2 Integrated logistics support . 14 4.5 Program Managers role 15 4.6 SSAisrole 16 4.7 SSAs charter 16 5 5.1 5.2 5.3 5.3.1 5.3.1.1 503.1.2 5.3.1.3 5.3.2 5.3.2.1 5.3.2.2 5.342-3 5.3.2.4 5.3e2-5 5.3.3 5.3.4 5.3.5 5.3.5.1 5.3.5.2 PRE-

14、DEPLOYMENT SOFTWARE SUPPORT o 18 Purpose . 18 Introduction . 18 PDSS concept planning 18 SSA resource requirements planning 19 Identify PDSS acquisition requirements 19 Software environment requirements 20 Technical data requirements . 20 Software quality requirements 21 Evaluation requirements . 22

15、 Transition requirements . 21 Ensure software supportability 21 Assure software quality . 22 Develop and implement transition plan 22 Software development transition . 22 SSA transition 23 Pre-deployment software support activities . . + . 18 PlanforPDSS 18 Computer Resources Life Cycle Management P

16、lan . . 19 6 6.1 6.2 6*2*1 6.2.2 6.2.3 6.2.4 6.2.5 602.6 6.2.7 6.3 6.3. 1 6*3r1*1 6.3.1.2 6.3.1.3 6.3.1.4 6.3.1.5 603.2 6.3.2.1 POST-DEPLOYMENT SOFTWARE SUPPORT Purpose General PDSS process Input . Initial analysis phase . . . Software (CSCI) development phase . System integration and testing phase

17、. Broduct logistics phase Support operations and maintenance . output . . . * * . Detailed PDSS process model Initial analysis phase . I . . . Activity: Status accounting . Activity: Configuration control decision Activity: Impact analyses . Activity: Status accounting Activity: Configuration contro

18、l decision Software (CSCI) development phase . . Activity: Softwara requirements analysis . 25 o 25 125 . 26 *.*e* 26 .*.* 26 . 27 *.DI 25 . 27 . 27. . 27 . 28 . 20 . 20 *o* 30 . 32 . 32- .*.o 32 . 73 iv Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-

19、,-MIL-HDBK-347 MC m 9999970 005b26L 4 m PARAGRAPH MIL-HDBK-34 7 CONTENTS - PACE 6.3.2.2 Activity: Preliminary design . . . . . . 35 6.3.2.3 Activity: Detailed design . . . . . . a 35 6.3.2.4 Activity: Code P computer software unit testing . 35 6.3.2.5 Activity: Computer software component integratio

20、n 2. involves cryptological activities related to national security i 3, involves the command and control of military forces.; 4. involves equipment which is an integral part of a weapon or weapons system; or 5, is critical to the direct fulfillment of military or intelligence missions, provided tha

21、t it does not include automatic data processing equipment used or routine administrative and business applications such as payroll, finance, logistics, and personnel management, c 7 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-i MIL-HDBK-347 MC W

22、9999970 005b2b9 7 W MIL-HDBK-347 B. Computer resources whose function, purpoee, or um are critical to the direct fulfillment of military or intelligence missions - include, but not be limited to: 1. 2. 3. 4. 5. 6. 7. a. 9. Warning, surveillance, reconnaissance, and electronic warfare systems: Missio

23、n-support systems deployed in combat environments: Classified systems and programs; Strategic and tactical military cornunications systems; Satellite systems supporting strategic or tactical military missions: Environment monitoring and prediction systems directly supporting military missions (e.g.

24、weather, and oceanographic); Locating, positioning, mapping, charting and geodesy syetem directly supporting military missions : Maintenance systems which provide direct support t weapon systems and software support facilities; Systems used internally within the Department of Defense for classified

25、analyses, research and development in direct support of military or intelligence missions. C. Computer resources used primarily for routine administrative and business applications such as payroll, finance, logistics, and personnel management shall not be considered military or intelligence mission-

26、critical, 3.12 Operational version. A software version which has been approved for release to the using community. 3.13 Post-deployment software support (PDSS) . Those software support activities that occur during the full-rate production and initial deployment and operations support phases of the a

27、cquisition process. 8 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-HDBK-3LI7 MC 9777770 005b270 5 W MIL-HDBK-347 3.14 PDSS environment. The PDCS environment includes the software engineering environment, software test environment, and other eq

28、uipment, material and documentation, including data rights, necessary to provide PDSC for a designated MCCR in accordance with the integrated logistics support concept. 3.15 Pre-deDiornent software sumort. Those software support activities that occur before initial deployment and operations 3.16 Rel

29、ease, DoP-STD-2167A: “A configuration management action whereby a particular version of software is made available for Q specific purpose (e.g., released for toet) .“ 3.37 Software chanse catesories. All software changes can be placed into one of the following categories: support e 3.17.1 Software c

30、orrection. A software correction is a software change implemented to correct a fault in the software. 3.17.2 Software enhancement. A software enhancement is any software change which is not a software correction. There are two types of software enhancements: 3.17.2.1 Adaptive. Adaptive enhancements

31、are software changes necessary to accommodate changs(s) in the operational or hardware environment, Software adaptations include changes to implement new system interface requirements, new system requirements (i.e., changes to the system requirements specification), or new hardware requirements. 3.1

32、7.2.2 Perfective. Perfective enhancements are software changes which improve software performance (eg., man-machine interface enhancements, maintainability or other software attributes. A perfective change does not implement a new system requirement , 3.18 Software development process, AS described

33、in DOD-STD- 216714, the software development process includes the following major aativities: (Note: The CSCI development process is a subset of the software development process,) e a. system Requirements Analysis/Design b. Software Requirements Analysis c. Preliminary Design d. Detailed Design e. C

34、oding and CSU Testing f. Computer Software Component (CSC) Integration and Testing 9 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,- _ MIL-HDBK-3Y7 MC m. 7977770 0056273 7 m MIL-HDBK-347 g. CSCI Testing h. System Integration and Testing 3.19 Softwar

35、e ensineerins environment (SEE). DOD-STD-2167A: “The set of automated tools, firmware devices, and hardware necessary to perform the software engineering effort. The automated tools may include but are not limited to compilers, assemblers, linkara, loaders, operating system, debuggers, simulators, e

36、mulators, test tools, documentation tools, and data base management system (8) , It 3.20 Software support. DoD-STD-2167A: “The sum of all activities that take place to ensure that implemented and fielded software continues to fully support the operational mission of the software.“ Software support i

37、ncludes pre-deployment software support and post-deployment-software support. 3.21 Software SUDDOitablish the principles upon which this document is based. They are: a. Software support activities occur throughout the system acquisition process. b. The evolution of software is a continuum of success

38、ive software development cycles beginning with initial software development and continuing with one or more follow-on software development cycles. C. Software should continue to evolve as long as essential requirements or cost-effective benefits can be derived through software change d. The SSA is t

39、he Governments agency responsible for providing PDSS requirements to the Program Manager and for cost effective PDSS operations following transition. e. Critical MCCR activities are performed by Government organizations to ensure 12 Provided by IHSNot for ResaleNo reproduction or networking permitte

40、d without license from IHS-,-,-MIL-HDBK-3g7 MC 7777770 0056274 2 m MIL-HDBK-347 accountability, responsiveness, control, continuity and compliance. Critical activities include the control and identification of Government controlled software baselines; defining and evaluating software quality require

41、ments; system level testing; managing and planning for BDSS. f. Direct communication between the using community and the SSA is important to help identify and isolate software problems, and to foster attitudes of support and cooperation. 4.4 Evolution of software suport. Software support, and hence

42、the role of the SSA, evolves as acquisition progresses. The SSAs capability to conduct PDCS and the eventual cost of PDSS closely depend on what occurs, or what fails to occur, during the pro-deployment stage. In general, during the pro-deployment software support stage the focus of software support

43、 should be to ensure software supportability and to plan for cost effective PDSS. During the PDSS stage, the focus of software support should be to ensure continued supportability, to manage PDSS, and to conduct efficient PDSS operations. - 4.4.1 Software sumort and the acquisition procesfi. In aoco

44、rdanae with DoD Directive 5000.1, the acquisition process is divisd into five phases: concept exploration/definition; concept demonctration/validation; full-scale development; full-rate production and initial deployment; and operations support. The chronological relationship between the acquisition

45、process and the evolution of software support can vary. Figure 1 identifies typical ILS and software support activities within the context of the acquisition process. Early in the acquisition process, program direction defines the responsibilities of the Program Manager and other acquisition partici

46、pants. (Note: The term “Program Managertt, as defined in DoD Directive 5000.1, is used throughout this handbook to designate the individual vested with the authority and responsibility for program direction and execution . ) Working within the Planning, Programing and Budgeting System, the Program M

47、anager provides direction and funds for development, production, and support of the system. 13 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-ACTIVITIES FOR INTEGRATED LOGISTIC SuPm ACTIVITIES FOR SORWARE SUPPORT i I_I._._-_ -_II- - MIL-HDBK-347 MC

48、m 7777770 0056275 4 m MIbHDBK-347 $Definition 3 Define lhe Design lor Declgn ole . Acquire the Provide the SUoooR suwofl sum A!Q?!EL sx!f2L oevefop ILS smtegy esipte the SCA Investigate alternative suppert conceptr Influence product dermition Identifylderinel assess bgisrics impricationc of eStiC su

49、pport logistics support items support system integral pan of design tradeolfs Ensure ILS is Test identifies SSA taskingc; and discusses organizational relationships (channels for management, support, and technical direction). Frequently, organizational relationships, responsibilities, lines of authority, and support channels are tailored to conform to a particuler PDSC concep