ASTM E1340-05

Standard Guide for Rapid Prototyping of Information Systems

SCOPE
1.1 This guide covers a rapid prototyping method for developing information systems that is particularly relevant to systems for the healthcare sector. Intended readers of this guide are people who develop information systems, and students and teachers of system development methods.
1.2 Rapid prototyping is an approach to developing information systems which produce a working model more quickly than conventional approaches. Where conventional methods concentrate on preparing Requirements and design documents that describe the needed system, rapid prototyping methods concentrate on preparing a working prototype. Users and developers learn the functional requirements and an appropriate system design by interacting with a series of prototypes, each of which is rapidly produced from a starting framework or from an earlier version. A prototype can evolve into an operational system, it can serve as an exact behavioral specification of an operational system, or it can be used to explore the feasibility of a new idea or design which can be incorporated in a larger system. The method is rapid in preparing each version of the prototype, but the overall time required for system development may be more or less than the time required with conventional methods.
1.3 Rapid prototyping is most appropriate when the Requirements or design for a system are not well understood, or when experimentation is required to explore some aspect of system behavior. It is not appropriate in hazardous settings, or when the requirements are well understood.
1.4 The guide recommends use of prototyping tools, but it is not a standard for the tools themselves. It does not cover executable specification tools. Transforming a prototype that is used to clarify Requirements into an operational system is discussed briefly in Section 8 and in detail in other referenced standards (see 2.1).
1.5 This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety and health practices and determine the applicability of regulatory limitations prior to use.

General Information

• Status: Historical
• Publication Date: 30-Apr-2005
• ICS: 35.080 - Software
• Technical Committee: E31 - Healthcare Informatics
• Drafting Committee: E31.25 - Healthcare Data Management, Security, Confidentiality, and Privacy

Relations

• Replaces: ASTM E1340-96 - Standard Guide for Rapid Prototyping of Computerized Systems
• Effective Date: 01-May-2005
• Replaced By: ASTM E1340-05(2010) - Standard Guide for Rapid Prototyping of Information Systems (Withdrawn 2017)
• Effective Date: 01-Mar-2010

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:E1340–05
Standard Guide for
1
Rapid Prototyping of Information Systems
This standard is issued under the fixed designation E1340; 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 priate safety and health practices and determine the applica-
bility of regulatory limitations prior to use.
1.1 This guide covers a rapid prototyping method for
developing information systems that is particularly relevant to
2. Referenced Documents
systemsforthehealthcaresector.Intendedreadersofthisguide
2.1 ANSI Standards:
are people who develop information systems, and students and
2
ANSI/MIL-STD-1815A Ada Programming Language
teachers of system development methods.
2
ANSI X3.9 Programming Language FORTRAN
1.2 Rapid prototyping is an approach to developing infor-
2
ANSI X3.159 Programming Language C
mation systems which produce a working model more quickly
2
ANSI/X11.1 MUMPS Programming Language
than conventional approaches. Where conventional methods
ANSI/IEEE 610.12 Glossary of Software Engineering Ter-
concentrate on preparing Requirements and design documents
2
minology
that describe the needed system, rapid prototyping methods
2
ANSI/IEEE 770 X3.97 Pascal Programming Language
concentrate on preparing a working prototype. Users and
ANSI/IEEE 830 Recommended Practice for Software Re-
developers learn the functional requirements and an appropri-
3
quirement Specifications
ate system design by interacting with a series of prototypes,
ANSI/IEEE 1016 Recommended Practice for Software De-
eachofwhichisrapidlyproducedfromastartingframeworkor
3
sign Descriptions
from an earlier version. A prototype can evolve into an
ANSI/IEEE 1058 Standard for Software Project Manage-
operational system, it can serve as an exact behavioral speci-
3
ment Plans
fication of an operational system, or it can be used to explore
ANSI/IEEE 1059 Guide for Software Verification and Vali-
the feasibility of a new idea or design which can be incorpo-
3
dation Plans
rated in a larger system. The method is rapid in preparing each
ANSI/IEEE 1063 User Documentation for Computer Soft-
version of the prototype, but the overall time required for
3
ware
system development may be more or less than the time
3
ANSI/IEEE 1074 Software Life Cycle Processes
required with conventional methods.
2.2 ISO Standards:
1.3 Rapid prototyping is most appropriate when the Re-
IS 12207 InformationTechnology-Software Life Cycle Pro-
quirements or design for a system are not well understood, or
cesses
when experimentation is required to explore some aspect of
IS 15288 System Life Cycle Processes
system behavior. It is not appropriate in hazardous settings, or
IS 15440 Guide for Life Cycle Processes
when the requirements are well understood.
IS 11756 MUMPS Programming Language
1.4 Theguiderecommendsuseofprototypingtools,butitis
not a standard for the tools themselves. It does not cover
3. Terminology
executable specification tools.Transforming a prototype that is
3.1 Definitions—For definitions of terms relating to infor-
used to clarify Requirements into an operational system is
4
mation systems, refer to ANDIP and ANSI/IEEE 610.12.
discussed briefly in Section 8 and in detail in other referenced
3.1.1 fourth generation language, n—a high-level computer
standards (see 2.1).
language that incorporates data structures and procedures for a
1.5 This standard does not purport to address all of the
specific problem domain.
safety concerns, if any, associated with its use. It is the
responsibility of the user of this standard to establish appro-
2
Available fromAmerican National Standards Institute (ANSI), 25 W. 43rd St.,
1
This guide is under the jurisdiction of ASTM Committee E31 on Healthcare 4th Floor, New York, NY 10036.
3
Informatics and is the direct responsibility of Subcommittee E31.25 on Healthcare Available from Institute of Electrical and Electronics Engineers, Inc. (IEEE),
Data Management, Security, Confidentiality, and Privacy. 445 Hoes Ln., P.O. Box 1331, Piscataway, NJ 08854-1331.
4
Current edition approved May 1, 2005. Published June 2005. Originally American National Dictionary for Information Processing Systems, Informa-
approved in 1990. Last previous edition approved in 1996 as E1340 – 96. DOI: tion Processing Systems Technical Report X3/TR-1-82, Dow Jones-Irwin, Home-
10.1520/E1340-05. wood, IL.
Copyright © ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959, United States.
1

---------------------- Page: 1 ----------------------
E1340–05
3.1.2 prototype, n—an original or model from w
...