ISO/IEC TR 14759:1999
(Main)Software engineering — Mock up and prototype — A categorization of software mock up and prototype models and their use
Software engineering — Mock up and prototype — A categorization of software mock up and prototype models and their use
Ingénierie du logiciel — Maquette et prototype — Un classement des maquettes et prototype logiciels et leur utilisation
General Information
Standards Content (Sample)
TECHNICAL ISO/IEC
REPORT TR
14759
First edition
1999-12-01
Software engineering — Mock up and
prototype — A categorization of software
mock up and prototype models and their
use
Ingénierie du logiciel — Maquette et prototype — Un classement des
maquettes et prototype logiciels et leur utilisation
Reference number
ISO/IEC TR 14759:1999(E)
©
ISO/IEC 1999
---------------------- Page: 1 ----------------------
ISO/IEC TR 14759:1999(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but shall not
be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this
file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat accepts no liability in this
area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters
were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event
that a problem relating to it is found, please inform the Central Secretariat at the address given below.
© ISO/IEC 1999
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic
or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISO's member body
in the country of the requester.
ISO copyright office
Case postale 56 � CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 734 10 79
E-mail copyright@iso.ch
Web www.iso.ch
Printed in Switzerland
ii © ISO/IEC 1999 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC TR 14759:1999(E)
Contents Page
1 Scope .1
1.1 Purpose.1
1.2 Field of Application.1
2 References.1
3 Abbreviation and definitions .1
3.1 Abbreviation.1
3.2 Definitions .2
4 Categorization of mock up and prototype models.2
5 Use of mock up and prototype models .3
5.1 Mock up versus prototype .3
5.2 Illustrative versus functional.5
5.3 Demonstrative versus operational.6
Annex A Examples of life cycle models for mock up and prototype production .8
© ISO/IEC 1999 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC TR 14759:1999(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission)
form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC
participate in the development of International Standards through technical committees established by the
respective organization to deal with particular fields of technical activity. ISO and IEC technical committees
collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in
liaison with ISO and IEC, also take part in the work.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 3.
In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting.
Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote.
In exceptional circumstances, when a technical committee has collected data of a different kind from that which is
normally published as an International Standard ("state of the art", for example), it may decide by a simple majority
vote of its participating members to publish a Technical Report. A Technical Report is entirely informative in nature
and does not have to be reviewed until the data it provides are considered to be no longer valid or useful.
Attention is drawn to the possibility that some of the elements of this Technical Report may be the subject of patent
rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
ISO/IEC TR 14759 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 7, Software engineering.
iv © ISO/IEC 1999 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC TR 14759:1999(E)
Introduction
Mock up and prototypes are commonly confused. This stems from the English word "prototype" which covers the
two French terms "maquette" (mock up) and "prototype" (prototype). An examination of the meaning given to the
two words mock up and prototype in the aeronautical industry reveals that the first stipulates a version of the plane
which cannot be piloted and the second a version which can be piloted. Using this analogy, a software mock up is
defined as a provisional product that cannot be piloted by users, is not intended to evolve into a fully operational
product and may be thrown away once its objective has been achieved. A software "prototype" is defined as
something that can be piloted, is developed as a part of the target product and may evolve into an operational
product.
Besides this first distinction between mock up and prototype, two additional distinctions have been introduced to
address specific features of software issues:
� "illustrative" (related to realistic graphic representation, as in HCIs) versus "functional" (capable of performing
computations) address the objective of the mock up and prototype development.
� "demonstrative" (serving to prove the relevance of a solution) versus "operational" (fit for proper functioning in
real conditions of operations) address the level of refinement of the deliverable.
© ISO/IEC 1999 – All rights reserved v
---------------------- Page: 5 ----------------------
TECHNICAL REPORT ISO/IEC TR 14759:1999(E)
Software engineering — Mock up and prototype —
A categorization of software mock up and prototype models and
their use
1 Scope
This Technical Report applies to any project which uses evolutionary development.
This Technical Report sets out the concepts associated with the production of mock ups and prototypes by
identifying and describing the various deliveries which result.
The Technical Report is written for user representatives, developers, managers, quality assurance practitioners of
systems and software products and services.
1.1 Purpose
The purpose of this Technical Report is to define the boundaries of mock up and prototype oriented projects.
The purpose of this Technical Report is to reduce risk in critical projects.
1.2 Field of Application
The purpose of this Technical Report does not provide the reader with a normative definition of a specific software
life cycle model.
The Technical Report applies to any project which involves uncertain conditions, e.g. safety critical software, user
interfaces, new algorithms.
2 References
This Technical Report includes references to other publications. The latest edition of the publication referred to
applies.
ISO/IEC 9126:1991, Information technology — Software product evaluation — Quality characteristics and
guidelines for their use.
ISO/IEC 12207:1995, Information technology — Software life cycle processes.
3 Abbreviation and definitions
3.1 Abbreviation
HCI Human-computer interface.
© ISO/IEC 1999 – All rights reserved 1
---------------------- Page: 6 ----------------------
ISO/IEC TR 14759:1999(E)
3.2 Definitions
a) Demonstrative
A demonstrative product is a product which proves the relevance of a solution.
b) Functional
A functional product is a product capable of performing computations.
c) Illustrative
An illustrative product is a non functional product.
d) Mock up
A mock up is a throw-away product. Note that it can be retained e.g. for verification, training and as a record.
e) Operational
An operational product is a product which functions in real conditions of operations.
f) Prototype
A prototype is a preliminary type, form, or instance of a system that serves as a model for later stages or for
the final, complete version of the system. A prototype is a usable product.
NOTE Refer to clause 4 and Figure 1 for further information about these definitions.
4 Categorization of mock up and prototype models
Mock up and prototype combine the following possible attributes: illustrative, functional, demonstrative and
operational, as shown in Figure 1.
product
mock up prototype
illustrative functional illustrative functional
demonstrative operational demonstrative operational demonstrative operational demonstrative operational
a) e) f) h)
b) c) d) g)
Figure 1 — Three pairs of terms, leading to eight possible types of products
2 © ISO/IEC 1999 – All rights reserved
---------------------- Page: 7 ----------------------
ISO/IEC TR 14759:1999(E)
The eight possible types of products identified in Figure 1 are described as follows:
a) A demonstrative illustrative mock up is a throw-away product representing the behaviour of the system,
running in the development environment.
EXAMPLE A slide-show, usually thrown away, unless it is used for training or marketing the product.
b) An operational illustrative mock up is a throw-away product representing the behaviour of the system,
running in the operational environment.
EXAMPLE A mock up of a HCI, tested in operational conditions, a situation which is frequently encountered in military
contexts. When an operational illustrative mock up is tested, the interface is realistic and usable, but the functional
environment is simulated.
c) A demonstrative functional mock up is a throw-away product showing the functional organization of the
system, running in the development environment.
EXAMPLE The first draft of a real-time algorithm, demonstrating a set of functions.
d) An operational functional mock up is a throw-away product showing the functional organization of the
system, running in the operational environment.
EXAMPLE The mock up of an algorithm, tested in operational conditions, to validate the reliability of a solution.
e) A demonstrative illustrative prototype is a usable product representing the behaviour of the system, running
in the development environment.
EXAMPLE A prototype of a HCI, tested in development conditions.
f) An operational illustrative prototype is a usable product representing the behaviour of the system, running in
the operational environment.
EXAMPLE A prototype of a HCI, tested by target users in operational conditions.
g) A demonstrative functional prototype is a usable product showing the functional organization of the system,
running in the development environment.
EXAMPLE The prototype of real-time software, still tested in development conditions.
h) An operational functional prototype is a usable product showing the functional organization of the system,
running in the operational environment.
EXAMPLE The prototype of real-time software, tested by target users in operational conditions.
5 Use of mock up and prototype models
Both mock up and prototype are helpful to analyse user’s software quality requirements and to investigate possible
risks on software quality characteristics, although they have differences and should be distinguished.
These software characteristics are, for example, interoperability of functionality, fault tolerant of reliability,
operability of usability or time behaviour or efficiency and so on, which may be found in ISO/IEC 9126.
5.1 Mock up versus prototype
The mock up does not provide a real version but a realistic version of the target product. The purpose of a mock up
is to give users a representative image of the target deliverable, enabling them to detect and correct deficiencies at
a time when the cost of such modifications is still quite low. Later, the software supporting the mock up is
discarded; the design of the mock up is terminated but its specification may be reused in any further development.
© ISO/IEC 1999 – All rights reserved 3
---------------------- Page: 8 ----------------------
ISO/IEC TR 14759:1999(E)
The software supporting the mock up may also be kept along with the design as a quality record and for use in
subsequent verification and validation.
The mock up is characterized by the following statements:
a) Not all features of the target product need be represented;
b) The development environment (machine, language, and tools) need not be that of the target product but it
must be representative of the target product;
c) The operating environment technical components need not be those of the target product but they must be
representative
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.