ASTM F1716-96(2008)
(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
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
Relations
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 2008) An American National Standard
Standard Guide for
Transition and Performance of Marine Software Systems
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 ANSI/ISO/ASQC Q 9001 Quality Systems—Model for
Quality Assurance in Design, Development, Production,
1.1 This guide covers a recommended plan for transition
Installation and Servicing
and acceptance of marine software that was developed by an
2.4 Military Standards and Specifications:
activity other than the maintaining activity. It further provides
MIL-STD 498 Software Development and Documentation
a recommended iterative process model for managing and
executing software maintenance activities.
3. Terminology
2. Referenced Documents
3.1 The terminology used in this guide is defined in Termi-
2.1 ASTM Standards:
nology E1013 and Guide E622.
E622 GuideforDevelopingComputerizedSystems(Discon-
3.2 Othercomputer-relatedtermsinthisguidearedefinedin
tinued 2000) (Withdrawn 2000)
IEEE 100 and IEEE 610.12.
E919 Specification for Software Documentation for a Com-
puterizedSystem(Discontinued2000)(Withdrawn2000)
4. Significance and Use
E1013 Terminology Relating to Computerized Systems
3 4.1 This guide provides a recommended transition plan for
(Withdrawn 2000)
4 a marine software maintainer, when the maintainer is other
2.2 IEEE Standards:
than the supplier, to develop the capability to make extensive
100 Standard Dictionary for Electrical and Electronic Terms
changes or extensions to the programs. Further, this guide
610 Standard Glossary of Software Engineering Terminol-
provides a recommended interactive process model for man-
ogy
aging and executing software maintenance activities. This
1063 Standard for Software User Documentation
guide applies principally to the marine software that requires
1074 Standard for Developing Software Life Cycle Pro-
design effort and for which the product requirements are stated
cesses
principally in performance terms.
1219 Standard for Software Maintenance
2.3 ANSI Standards:
5. Software Transition Plan
ANSI/ISO/ASQC Q9000—3 Quality Management and
5.1 The software transition plan is developed when the
Quality Assurance Standards: Guidelines for the Applica-
software support concept calls for transition of responsibility
tion of ANSI/ISO/ASQC Q 9001 to the Development,
from the developer to a separate support agent. The software
Supply and Maintenance of Software
transition plan identifies hardware, software, and other re-
sources needed for life cycle support of deliverable software
This guide is under the jurisdiction of ASTM Committee F25 on Ships and
and describes the developer’s plans for transitioning deliver-
Marine Technology and is the direct responsibility of Subcommittee F25.05 on
able items to the support agent.The developer shall identify all
Computer Applications.
softwaredevelopmentresourcesneededbythesupportagentto
CurrenteditionapprovedMay1,2008.PublishedJuly2008.Originallyapproved
in 1996. Last previous edition approved in 2002 as F1716 - 96(2002). DOI: fulfill the support concept specified in the contract. The
10.1520/F1716-96R08.
developer shall develop and record plans identifying these
For referenced ASTM standards, visit the ASTM website, www.astm.org, or
resources and describing the approach to be followed for
contact ASTM Customer Service at service@astm.org. For Annual Book of ASTM
transitioning deliverable items to the support agent. The
Standards volume information, refer to the standard’s Document Summary page on
the ASTM website.
planning shall include the following.
The last approved version of this historical standard is referenced on
www.astm.org.
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. Available from Standardization Documents Order Desk, DODSSP, Bldg. 4,
Available fromAmerican National Standards Institute (ANSI), 25 W. 43rd St., Section D, 700 Robbins Ave., Philadelphia, PA 19111-5098, http://
4th Floor, New York, NY 10036, http://www.ansi.org. www.dodssp.daps.mil.
Copyright © ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959. United States
F1716 − 96 (2008)
5.1.1 Software Support Resources—Description of the re- 5.1.4.5 When items must be acquired, information about a
sources needed to support the deliverable software. These current source of supply, including whether the item is cur-
rentlyavailableandwhetheritisexpectedtobeavailableatthe
resources shall include items needed to control, copy, and
time of delivery.
distribute the software and its documentation, and to specify,
5.1.4.6 Information about vendor support, licensing, and
design, implement, document, test, evaluate, control, and
data rights, including whether the item is currently supported
distribute modifications to the software. This includes needed
by the vendor, whether it is expected to be supported at the
compilers, linkers, locators, mappers, and tools such as con-
time of delivery, whether licenses will be assigned to the
figuration utilities. In addition, include as applicable, any
support agent, and the term of such licenses.
special operating systems.
5.1.4.7 Privacy considerations and limitations.
5.1.2 Facilities—Description of the facilities needed to
5.1.4.8 Certification of virus protection measures taken
support the deliverable software. These facilities may include
including identification and version of software used.
special rooms, mock-ups, special power requirements, and so
5.1.5 Other Documentation—Identification of any other
forth.
documentation needed to support the deliverable software.
5.1.3 Hardware—Identification and description of the hard-
This list will include, for example, plans, reports, studies,
ware and associated documentation needed to support the
specifications, design descriptions, test cases/procedures, test
deliverable software. This hardware may include computers,
reports, user/operator manuals, and support manuals for the
peripheral equipment, hardware simulators, stimulators, emu-
deliverable software, including the following:
lators, diagnostic equipment, and non-computer equipment.
5.1.5.1 Names, identification numbers, version numbers,
The description shall include:
and rele
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.