1、Designation: F 1716 96 (Reapproved 2008)An American National StandardStandard Guide forTransition and Performance of Marine Software SystemsMaintenance1This standard is issued under the fixed designation F 1716; the number immediately following the designation indicates the year oforiginal adoption
2、or, in the case of revision, the year of last revision. A number in parentheses indicates the year of last reapproval. Asuperscript epsilon () indicates an editorial change since the last revision or reapproval.1. Scope1.1 This guide covers a recommended plan for transitionand acceptance of marine s
3、oftware that was developed by anactivity other than the maintaining activity. It further providesa recommended iterative process model for managing andexecuting software maintenance activities.2. Referenced Documents2.1 ASTM Standards:2E 622 Guide for Developing Computerized Systems3E 919 Specificat
4、ion for Software Documentation for aComputerized System3E 1013 Terminology Relating to Computerized Systems32.2 IEEE Standards:4100 Standard Dictionary for Electrical and Electronic Terms610 Standard Glossary of Software Engineering Terminol-ogy1063 Standard for Software User Documentation1074 Stand
5、ard for Developing Software Life Cycle Pro-cesses1219 Standard for Software Maintenance2.3 ANSI Standards:5ANSI/ISO/ASQC Q 90003 Quality Management andQuality Assurance Standards: Guidelines for the Applica-tion of ANSI/ISO/ASQC Q 9001 to the Development,Supply and Maintenance of SoftwareANSI/ISO/AS
6、QC Q 9001 Quality SystemsModel forQuality Assurance in Design, Development, Production,Installation and Servicing2.4 Military Standards and Specifications:6MIL-STD 498 Software Development and Documentation3. Terminology3.1 The terminology used in this guide is defined in Termi-nology E 1013 and Gui
7、de E 622.3.2 Other computer-related terms in this guide are defined inIEEE 100 and IEEE 610.12.4. Significance and Use4.1 This guide provides a recommended transition plan fora marine software maintainer, when the maintainer is otherthan the supplier, to develop the capability to make extensivechang
8、es or extensions to the programs. Further, this guideprovides a recommended interactive process model for man-aging and executing software maintenance activities. Thisguide applies principally to the marine software that requiresdesign effort and for which the product requirements are statedprincipa
9、lly in performance terms.5. Software Transition Plan5.1 The software transition plan is developed when thesoftware support concept calls for transition of responsibilityfrom the developer to a separate support agent. The softwaretransition plan identifies hardware, software, and other re-sources nee
10、ded for life cycle support of deliverable softwareand describes the developers plans for transitioning deliver-able items to the support agent. The developer shall identify allsoftware development resources needed by the support agent tofulfill the support concept specified in the contract. Thedevel
11、oper shall develop and record plans identifying theseresources and describing the approach to be followed fortransitioning deliverable items to the support agent. Theplanning shall include the following.5.1.1 Software Support ResourcesDescription of the re-sources needed to support the deliverable s
12、oftware. Theseresources shall include items needed to control, copy, anddistribute the software and its documentation, and to specify,1This guide is under the jurisdiction of ASTM Committee F25 on Ships andMarine Technology and is the direct responsibility of Subcommittee F25.05 onComputer Applicati
13、ons.Current edition approved May 1, 2008. Published July 2008. Originally approvedin 1996. Last previous edition approved in 2002 as F 1716 - 96(2002).2For referenced ASTM standards, visit the ASTM website, www.astm.org, orcontact ASTM Customer Service at serviceastm.org. For Annual Book of ASTMStan
14、dards volume information, refer to the standards Document Summary page onthe ASTM website.3Withdrawn.4Available from Institute of Electrical and Electronics Engineers, Inc. (IEEE),445 Hoes Ln., P.O. Box 1331, Piscataway, NJ 08854-1331, http:/www.ieee.org.5Available from American National Standards I
15、nstitute (ANSI), 25 W. 43rd St.,4th Floor, New York, NY 10036, http:/www.ansi.org.6Available from Standardization Documents Order Desk, DODSSP, Bldg. 4,Section D, 700 Robbins Ave., Philadelphia, PA 19111-5098, http:/www.dodssp.daps.mil.1Copyright ASTM International, 100 Barr Harbor Drive, PO Box C70
16、0, West Conshohocken, PA 19428-2959, United States.design, implement, document, test, evaluate, control, anddistribute modifications to the software. This includes neededcompilers, linkers, locators, mappers, and tools such as con-figuration utilities. In addition, include as applicable, anyspecial
17、operating systems.5.1.2 FacilitiesDescription of the facilities needed tosupport the deliverable software. These facilities may includespecial rooms, mock-ups, special power requirements, and soforth.5.1.3 HardwareIdentification and description of the hard-ware and associated documentation needed to
18、 support thedeliverable software. This hardware may include computers,peripheral equipment, hardware simulators, stimulators, emu-lators, diagnostic equipment, and non-computer equipment.The description shall include:5.1.3.1 Specific models, versions, and configurations.5.1.3.2 Rationale for the sel
19、ected hardware.5.1.3.3 Reference to user/operator manuals or instructionsfor each item, as applicable.5.1.3.4 Identification of each hardware item and documentas acquirer-furnished, any item that will be delivered to thesupport agent, any item the support agent is known to have, anyitem the support
20、agent must acquire, or other description ofstatus.5.1.3.5 When items must be acquired, information about acurrent source of supply, including whether the item is cur-rently available and whether it is expected to be available at thetime of delivery.5.1.3.6 Information about manufacturer support, lic
21、ensing,and data rights, including whether the item is currentlysupported by the manufacturer, whether it is expected to besupported at the time of delivery, whether licenses will beassigned to the support agent, and the terms of such licenses.5.1.3.7 Privacy considerations or limitations.5.1.4 Softw
22、areIdentification and description of the soft-ware and associated documentation needed to support thedeliverable software. This software may include computer-aided software engineering (CASE) tools, data in these tools,compilers, test tools, test data, simulations, emulations, utili-ties, configurat
23、ion management tools, databases and data filesand other software. The description shall include:5.1.4.1 Specific names, identification numbers, versionnumbers, release numbers, and configurations, as applicable.5.1.4.2 Rationale for the selected software.5.1.4.3 Reference to user/operator manuals fo
24、r instructionsfor each item, as applicable.5.1.4.4 Identification of each software item and document asacquirer-furnished, any item that will be delivered to thesupport agent, any item the support agent is known to have, anyitem the support agent must acquire, or other description ofstatus.5.1.4.5 W
25、hen items must be acquired, information about acurrent source of supply, including whether the item is cur-rently available and whether it is expected to be available at thetime of delivery.5.1.4.6 Information about vendor support, licensing, anddata rights, including whether the item is currently s
26、upportedby the vendor, whether it is expected to be supported at thetime of delivery, whether licenses will be assigned to thesupport agent, and the term of such licenses.5.1.4.7 Privacy considerations and limitations.5.1.4.8 Certification of virus protection measures takenincluding identification a
27、nd version of software used.5.1.5 Other DocumentationIdentification of any otherdocumentation needed to support the deliverable software.This list will include, for example, plans, reports, studies,specifications, design descriptions, test cases/procedures, testreports, user/operator manuals, and su
28、pport manuals for thedeliverable software, including the following:5.1.5.1 Names, identification numbers, version numbers,and release numbers as applicable.5.1.5.2 Rationale for including each document.5.1.5.3 Identification of each document as acquirer-furnished, any item that will be delivered to
29、the support agent,any item the support agent is known to have, any item thesupport agent must acquire, or other description of status.5.1.5.4 When a document must be acquired, informationabout where to acquire it.5.1.5.5 Information about licensing and data rights.5.1.5.6 Privacy and limitations.5.1
30、.5.7 Beta Testing and Verification and ValidationRecordsRecords of Beta Testing and Verification and Vali-dation shall be provided if applicable.5.1.5.8 Description of significant problems and changesmade during the development process.5.1.6 PersonnelDescription of the personnel needed tosupport the
31、 deliverable software, including anticipated numberof personnel, and types and levels of skills and expertise.5.1.7 Other ResourcesIdentify any other resourcesneeded to support the deliverable software, including consum-ables.5.1.8 Interrelationship of ComponentsIdentify interrela-tionships of the c
32、omponents identified above. Figures may beused to show interrelationships.5.1.9 Recommended ProceduresDescribe any procedures,including advice and lessons learned, that the developer maywish to recommend to the support agent for supporting thedeliverable software and associated support environment.5
33、.1.10 TrainingDescribe the developers plans for train-ing support personnel to support the deliverable software.5.1.11 Anticipated Areas of ChangeDescribe anticipatedareas of change to the deliverable software.5.1.12 Transition PlanningPlanning shall be performedfor all activities to transition the
34、deliverable software to thesupport agent. Plans for transitioning the deliverable softwareto the support agent shall address the following:5.1.12.1 The activities to be performed to transition thedeliverable software to the support activity. These activitiesmay include planning/coordination meetings
35、; preparation ofitems to be delivered to the support agent; packing, shipment,installation, and checkout of the software support environment;packing, shipment, installation and checkout of the operationalsoftware; and training of the support personnel.5.1.12.2 Designation of the roles and responsibi
36、lities foreach activity.F 1716 96 (2008)25.1.12.3 The resources needed to carry out the transitionactivities and which party will perform each activity.5.1.12.4 Schedules and milestones for conducting the tran-sition activities.5.1.12.5 Procedures for installation and checkout of thedeliverable item
37、s of the support environment.6. Software Maintenance6.1 System software maintenance commences after thetransition and acceptance of the developed software by thesoftware support activity. Software maintenance can be iden-tified by either user/customer or system maintainer. Theprocesses of IEEE 1219
38、are recommended as a model forsoftware maintenance.7. Support Agent Software Process Maturity7.1 The processes of the software support agent are recom-mended to be certified to at least Level Two as defined in theSoftware Engineering Institute (SEI) Capability MaturityModel for Software Version 1.1,
39、7equivalent to ANSI/ISO/ASQC Q 9000-3.8. Keywords8.1 computerized systems; marine technology; ships; soft-ware; software maintenance; software supportASTM International takes no position respecting the validity of any patent rights asserted in connection with any item mentionedin this standard. User
40、s of this standard are expressly advised that determination of the validity of any such patent rights, and the riskof infringement of such rights, are entirely their own responsibility.This standard is subject to revision at any time by the responsible technical committee and must be reviewed every
41、five years andif not revised, either reapproved or withdrawn. Your comments are invited either for revision of this standard or for additional standardsand should be addressed to ASTM International Headquarters. Your comments will receive careful consideration at a meeting of theresponsible technica
42、l committee, which you may attend. If you feel that your comments have not received a fair hearing you shouldmake your views known to the ASTM Committee on Standards, at the address shown below.This standard is copyrighted by ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken,
43、 PA 19428-2959,United States. Individual reprints (single or multiple copies) of this standard may be obtained by contacting ASTM at the aboveaddress or at 610-832-9585 (phone), 610-832-9555 (fax), or serviceastm.org (e-mail); or through the ASTM website(www.astm.org).7Available from Research Access, Inc. (RAI), 800 Vinial Street, Pittsburgh, PA15212.F 1716 96 (2008)3
