ASTM F1716-96(2015)
(Guide)Standard Guide for Transition and Performance of Marine Software Systems Maintenance
Standard Guide for Transition and Performance of Marine Software Systems Maintenance
SIGNIFICANCE AND USE
4.1 This guide provides a recommended transition plan for a marine software maintainer, when the maintainer is other than the supplier, to develop the capability to make extensive changes or extensions to the programs. Further, this guide provides a recommended interactive process model for managing and executing software maintenance activities. This guide applies principally to the marine software that requires design effort and for which the product requirements are stated principally in performance terms.
SCOPE
1.1 This guide covers a recommended plan for transition and acceptance of marine software that was developed by an activity other than the maintaining activity. It further provides a recommended iterative process model for managing and executing software maintenance activities.
General Information
Buy Standard
Standards Content (Sample)
NOTICE: This standard has either been superseded and replaced by a new version or withdrawn.
Contact ASTM International (www.astm.org) for the latest information
Designation: F1716 − 96 (Reapproved 2015) An American National Standard
Standard Guide for
Transition and Performance of Marine Software Systems
1
Maintenance
This standard is issued under the fixed designation F1716; the number immediately following the designation indicates the year of
original adoption or, in the case of revision, the year of last revision. A number in parentheses indicates the year of last reapproval. A
superscript epsilon (´) indicates an editorial change since the last revision or reapproval.
5
1. Scope 2.3 ANSI Standards:
ANSI/ISO/ASQC Q9000—3 Quality Management and
1.1 This guide covers a recommended plan for transition
Quality Assurance Standards: Guidelines for the Applica-
and acceptance of marine software that was developed by an
tion of ANSI/ISO/ASQC Q 9001 to the Development,
activity other than the maintaining activity. It further provides
Supply and Maintenance of Software
a recommended iterative process model for managing and
ANSI/ISO/ASQC Q 9001 Quality Systems—Model for
executing software maintenance activities.
Quality Assurance in Design, Development, Production,
1.2 This international standard was developed in accor-
Installation and Servicing
dance with internationally recognized principles on standard-
6
2.4 Military Standards and Specifications:
ization established in the Decision on Principles for the
MIL-STD 498 Software Development and Documentation
Development of International Standards, Guides and Recom-
mendations issued by the World Trade Organization Technical
3. Terminology
Barriers to Trade (TBT) Committee.
3.1 The terminology used in this guide is defined in Termi-
nology E1013 and Guide E0622.
2. Referenced Documents
2
3.2 Othercomputer-relatedtermsinthisguidearedefinedin
2.1 ASTM Standards:
IEEE 100 and IEEE 610.12.
E0622 Guide for Developing Computerized Systems (With-
3
drawn 2000)
4. Significance and Use
E919 Specification for Software Documentation for a Com-
3
puterized System (Withdrawn 2000) 4.1 This guide provides a recommended transition plan for
E1013 Terminology Relating to Computerized Systems a marine software maintainer, when the maintainer is other
3
(Withdrawn 2000) than the supplier, to develop the capability to make extensive
4
changes or extensions to the programs. Further, this guide
2.2 IEEE Standards:
provides a recommended interactive process model for man-
100 Standard Dictionary for Electrical and Electronic Terms
aging and executing software maintenance activities. This
610 Standard Glossary of Software Engineering Terminol-
guide applies principally to the marine software that requires
ogy
design effort and for which the product requirements are stated
1063 Standard for Software User Documentation
principally in performance terms.
1074 Standard for Developing Software Life Cycle Pro-
cesses
5. Software Transition Plan
1219 Standard for Software Maintenance
5.1 The software transition plan is developed when the
software support concept calls for transition of responsibility
1
This guide is under the jurisdiction of ASTM Committee F25 on Ships and
from the developer to a separate support agent. The software
Marine Technology and is the direct responsibility of Subcommittee F25.05 on
transition plan identifies hardware, software, and other re-
Computer Applications.
sources needed for life cycle support of deliverable software
Current edition approved May 1, 2015. Published June 2015. Originally
approved in 1996. Last previous edition approved in 2008 as F1716 – 96 (2008). and describes the developer’s plans for transitioning deliver-
DOI: 10.1520/F1716-96R15.
able items to the support agent.The developer shall identify all
2
For referenced ASTM standards, visit the ASTM website, www.astm.org, or
softwaredevelopmentresourcesneededbythesupportagentto
contact ASTM Customer Service at service@astm.org. For Annual Book of ASTM
Standards volume information, refer to the standard’s Document Summary page on
the ASTM website.
3 5
The last approved version of this historical standard is referenced on Available from American National Standards Institute (ANSI), 25 W. 43rd St.,
www.astm.org. 4th Floor, New York, NY 10036, http://www.ansi.org.
4 6
Available from Institute of Electrical and Electronics Engineers, Inc. (IEEE), Available from DLA Document Services, Building 4/D, 700 Robbins Ave.,
445 Hoes Ln., P.O. Box 1331, Piscataway, NJ 08854-1331, http://www.ieee.org. Philadelphia, PA 19111-5094, http://quicksearch.dla.mil.
Copyright © ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959. United States
1
---------------------- Page: 1 ----------------------
F1716 − 96 (2015)
fulfill the support concept specified in the contract. The supportagent,anyitemthesupportagentisknowntohave,any
developer shall develop and record plans identifying these item th
...
This document is not an ASTM standard and is intended only to provide the user of an ASTM standard an indication of what changes have been made to the previous version. Because
it may not be technically possible to adequately depict all changes accurately, ASTM recommends that users consult prior editions as appropriate. In all cases only the current version
of the standard as published by ASTM is to be considered the official document.
Designation: F1716 − 96 (Reapproved 2008) F1716 − 96 (Reapproved 2015)An American National Standard
Standard Guide for
Transition and Performance of Marine Software Systems
1
Maintenance
This standard is issued under the fixed designation F1716; the number immediately following the designation indicates the year of
original adoption or, in the case of revision, the year of last revision. A number in parentheses indicates the year of last reapproval. A
superscript epsilon (´) indicates an editorial change since the last revision or reapproval.
1. Scope
1.1 This guide covers a recommended plan for transition and acceptance of marine software that was developed by an activity
other than the maintaining activity. It further provides a recommended iterative process model for managing and executing
software maintenance activities.
2. Referenced Documents
2
2.1 ASTM Standards:
3
E622 Guide for Developing Computerized Systems (Discontinued 2000) (Withdrawn 2000)
3
E919 Specification for Software Documentation for a Computerized System (Discontinued 2000) (Withdrawn 2000)
3
E1013 Terminology Relating to Computerized Systems (Withdrawn 2000)
4
2.2 IEEE Standards:
100 Standard Dictionary for Electrical and Electronic Terms
610 Standard Glossary of Software Engineering Terminology
1063 Standard for Software User Documentation
1074 Standard for Developing Software Life Cycle Processes
1219 Standard for Software Maintenance
5
2.3 ANSI Standards:
ANSI/ISO/ASQC Q9000—3 Quality Management and Quality Assurance Standards: Guidelines for the Application of
ANSI/ISO/ASQC Q 9001 to the Development, Supply and Maintenance of Software
ANSI/ISO/ASQC Q 9001 Quality Systems—Model for Quality Assurance in Design, Development, Production, Installation and
Servicing
6
2.4 Military Standards and Specifications:
MIL-STD 498 Software Development and Documentation
3. Terminology
3.1 The terminology used in this guide is defined in Terminology E1013 and Guide E622.
3.2 Other computer-related terms in this guide are defined in IEEE 100 and IEEE 610.12.
4. Significance and Use
4.1 This guide provides a recommended transition plan for a marine software maintainer, when the maintainer is other than the
supplier, to develop the capability to make extensive changes or extensions to the programs. Further, this guide provides a
1
This guide is under the jurisdiction of ASTM Committee F25 on Ships and Marine Technology and is the direct responsibility of Subcommittee F25.05 on Computer
Applications.
Current edition approved May 1, 2008May 1, 2015. Published July 2008June 2015. Originally approved in 1996. Last previous edition approved in 20022008 as
F1716 - 96F1716 – 96 (2008).(2002). DOI: 10.1520/F1716-96R08.10.1520/F1716-96R15.
2
For referenced ASTM standards, visit the ASTM website, www.astm.org, or contact ASTM Customer Service at service@astm.org. For Annual Book of ASTM Standards
volume information, refer to the standard’s Document Summary page on the ASTM website.
3
The last approved version of this historical standard is referenced on www.astm.org.
4
Available from Institute of Electrical and Electronics Engineers, Inc. (IEEE), 445 Hoes Ln., P.O. Box 1331, Piscataway, NJ 08854-1331, http://www.ieee.org.
5
Available from American National Standards Institute (ANSI), 25 W. 43rd St., 4th Floor, New York, NY 10036, http://www.ansi.org.
6
Available from Standardization Documents Order Desk, DODSSP, Bldg. 4, Section D, 700 Robbins Ave., Philadelphia, PA 19111-5098, http://www.dodssp.daps.mil.
Copyright © ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959. United States
1
---------------------- Page: 1 ----------------------
F1716 − 96 (2015)
recommended interactive process model for managing and executing software maintenance activities. This guide applies
principally to the marine software that requires design effort and for which the product requirements are stated principally in
performance terms.
5. Software Transition Plan
5.1 The software transition plan is developed when the software support concept calls for transition of responsibility from the
developer to a separate support agent. The software transition plan identifies hardware, software, and other resources needed for
life cycle support of deliverable software and describes the developer’s plans for transitioning deliverable items to the support
agent. The developer shall identify all software development resources needed by the support agent to fulfill the support concept
specified in the contract. The developer shal
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.