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.  
1.2 This international standard was developed in accordance with internationally recognized principles on standardization established in the Decision on Principles for the Development of International Standards, Guides and Recommendations issued by the World Trade Organization Technical Barriers to Trade (TBT) Committee.

General Information

Status
Published
Publication Date
31-Jan-2022
Current Stage
Ref Project

Buy Standard

Guide
ASTM F1716-96(2022) - Standard Guide for Transition and Performance of Marine Software Systems Maintenance
English language
3 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


This international standard was developed in accordance with internationally recognized principles on standardization established in the Decision on Principles for the
Development of International Standards, Guides and Recommendations issued by the World Trade Organization Technical Barriers to Trade (TBT) Committee.
Designation: F1716 − 96 (Reapproved 2022) 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 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-
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 E622.
2. Referenced Documents
3.2 Othercomputer-relatedtermsinthisguidearedefinedin
2.1 ASTM Standards:
IEEE 100 and IEEE 610.12.
E622 Guide for Developing Computerized Systems (With-
drawn 2000)
4. Significance and Use
E919 Specification for Software Documentation for a Com-
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
(Withdrawn 2000) than the supplier, to develop the capability to make extensive
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
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 Feb. 1, 2022. Published April 2022. Originally
approved in 1996. Last previous edition approved in 2015 as F1716 – 96 (2015). and describes the developer’s plans for transitioning deliver-
DOI: 10.1520/F1716-96R22.
able items to the support agent.The developer shall identify all
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
F1716 − 96 (2022)
fulfill the support concept specified in the contract. The supportagent,anyitemthesupportagentisknowntohave,any
developer shall develop and record plans identifying these item the support agent must acquire, or other description of
resources and describing the approach to be followed for status.
transitioning deliverable items to the support agent. The
5.1.4.5 When items must be acquired, information about a
planning shall include the following.
current source of supply, including whether the item is cur-
5.1.1 Software Support Resources—Description of the re- rentlyavailableandwhetheritisexpectedtobeavailableatthe
time of delivery.
sources needed to support the deliverable software. These
resources shall include items needed to control, copy, and
5.1.4.6 Information about vendor support, licensing, and
distribute the software and its documentation, and to specify, data rights, including whether the item is currently supported
design, implement, document, test, evaluate, control, and
by the vendor, whether it is expected to be supported at the
distribute modifications to the software. This includes needed
time of delivery, whether licenses will be assigned to the
compilers, linkers, locators, mappers, and tools such as con-
support agent, and the term of such licenses.
figuration utilities. In addition, include as applicable, any
5.1.4.7 Privacy considerations and limitations.
special operating systems.
5.1.4.8 Certification of virus protection measures taken
5.1.2 Facilities—Description of the facilities needed to
including identification and version of software used.
support the deliverable software. These facilities may include
5.1.5 Other Documentation—Identification of any other
special rooms, mock-ups, special power requirements, and so
documentation needed to support the deliverable software.
forth.
This list will include, for example, plans, reports, studies,
5.1.3 Hardware—Identification and description of the hard-
specifications, design descriptions, test cases/procedures, test
ware and associated documentation needed to support the reports, user/operator manuals, and support manuals for the
deliverable
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.