Standard Guide for Transition and Performance of Marine Software Systems Maintenance

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

Status
Historical
Publication Date
09-Jul-1996
Current Stage
Ref Project

Relations

Buy Standard

Guide
ASTM F1716-96(2002) - 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)


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
An American National Standard
Designation:F 1716–96 (Reapproved 2002)
Standard Guide for
Transition and Performance of Marine Software Systems
Maintenance
This standard is issued under the fixed designation F 1716; 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 (e) indicates an editorial change since the last revision or reapproval.
1. Scope MIL-STD 498 Software Development and Documentation
1.1 This guide covers a recommended plan for transition
3. Terminology
and acceptance of marine software that was developed by an
3.1 The terminology used in this guide is defined in Termi-
activity other than the maintaining activity. It further provides
nology E 1013 and Guide E 622.
a recommended iterative process model for managing and
3.2 Othercomputer-relatedtermsinthisguidearedefinedin
executing software maintenance activities.
IEEE 100 and IEEE 610.12.
2. Referenced Documents
4. Significance and Use
2.1 ASTM Standards:
2 4.1 This guide provides a recommended transition plan for
E 622 Guide for Developing Computerized Systems
a marine software maintainer, when the maintainer is other
E 919 Specification for Software Documentation for a
2 than the supplier, to develop the capability to make extensive
Computerized System
changes or extensions to the programs. Further, this guide
E 1013 Terminology Relating to Computerized Systems
3 provides a recommended interactive process model for man-
2.2 IEEE Standards:
aging and executing software maintenance activities. This
100 StandardDictionaryforElectricalandElectronicTerms
guide applies principally to the marine software that requires
610 Standard Glossary of Software Engineering Terminol-
design effort and for which the product requirements are stated
ogy
principally in performance terms.
1063 Standard for Software User Documentation
1074 Standard for Developing Software Life Cycle Pro-
5. Software Transition Plan
cesses
5.1 The software transition plan is developed when the
1219 Standard for Software Maintenance
software support concept calls for transition of responsibility
2.3 ANSI Standards:
from the developer to a separate support agent. The software
ANSI/ISO/ASQC Q 9000—3 Quality Management and
transition plan identifies hardware, software, and other re-
Quality Assurance Standards: Guidelines for the Applica-
sources needed for life cycle support of deliverable software
tion of ANSI/ISO/ASQC Q 9001 to the Development,
and describes the developer’s plans for transitioning deliver-
Supply and Maintenance of Software
able items to the support agent.The developer shall identify all
ANSI/ISO/ASQC Q 9001 Quality Systems—Model for
softwaredevelopmentresourcesneededbythesupportagentto
Quality Assurance in Design, Development, Production,
fulfill the support concept specified in the contract. The
Installation and Servicing
developer shall develop and record plans identifying these
2.4 Military Standards and Specifications:
resources and describing the approach to be followed for
transitioning deliverable items to the support agent. The
This guide is under the jurisdiction of ASTM Committee F25 on Ships and
planning shall include the following.
Marine Technology and is the direct responsibility of Subcommittee F25.05 on
5.1.1 Software Support Resources—Description of the re-
Computer Applications.
sources needed to support the deliverable software. These
Current edition approved July 10, 1996. Published September 1996.
Annual Book of ASTM Standards, Vol 14.01. resources shall include items needed to control, copy, and
Available from IEEE, 445 Hoes Lane, P.O. Box 1331, Piscataway, NJ
distribute the software and its documentation, and to specify,
08854-1331.
design, implement, document, test, evaluate, control, and
Available from American National Standards Institute (ANSI), 25 W. 43rd St.,
distribute modifications to the software. This includes needed
4th Floor, New York, NY 10036.
Available from Standardization Documents Order Desk, Bldg. 4, Section D,
700 Robbins Ave., Philadelphia, PA 19111-5098, Attn: NPODS.
Copyright © ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959, United States.
F 1716
compilers, linkers, locators, mappers, and tools such as con- 5.1.4.7 Privacy considerations and limitations.
figuration utilities. In addition, include as applicable, any
5.1.4.8 Certification of virus protection measures taken
special operating systems.
including identification and version of software used.
5.1.2 Facilities—Description of the facilities needed to
5.1.5 Other Documentation—Identification of any other
support the deliverable software. These facilities may include
documentation needed to support the deliverable software.
special rooms, mock-ups, special power requirements, and so
This list will include, for example, plans, reports, studies,
forth.
specifications, design descriptions, test cases/procedures, test
5.1.3 Hardware—Identification and description of the hard-
reports, user/operator manuals, and support manuals for the
ware and associated documentation needed to support the
deliverable software, including the following:
deliverable software. This hardware may include computers,
5.1.5.1 Names, identification numbers, version numbers,
peripheral equipment, hardware simulators, stimulators, emu-
and release numbers as applicable.
lators, diagnostic equipment, and non-computer equipment.
5.1.5.2 Rationale for including each document.
The description shall include:
5.1.5.3 Identification of each document as acquirer-
5.1.3.1 Specific models, versions, and configurations.
furnished, any item that will be delivered to the support agent,
5.1.3.2 Rationale for the selected hardware.
any item the support agent is known to have, any item the
5.1.3.3 Reference to user/operator manuals or instructions
support agent must acquire, or other description of status.
for each item, as applicable.
5.1.5.4 When a document must be acquired, information
5.1.3.4 Identification of each hardware item and document
about where to acquire it.
as acquirer-furnished, any item that will be delivered to the
5.1.5.5 Information about
...

Questions, Comments and Discussion

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