PRICES include / exclude VAT
Homepage>BS Standards>35 INFORMATION TECHNOLOGY. OFFICE MACHINES>35.080 Software development and system documentation>BS ISO/IEC TR 14759:1999 Software engineering. Mock up and prototype. A categorization of software mock up and prototype models and their use
Sponsored link
immediate downloadReleased: 2000-05-15
BS ISO/IEC TR 14759:1999 Software engineering. Mock up and prototype. A categorization of software mock up and prototype models and their use

BS ISO/IEC TR 14759:1999

Software engineering. Mock up and prototype. A categorization of software mock up and prototype models and their use

Format
Availability
Price and currency
English Secure PDF
Immediate download
180.00 EUR
You can read the standard for 1 hour. More information in the category: E-reading
Reading the standard
for 1 hour
18.00 EUR
You can read the standard for 24 hours. More information in the category: E-reading
Reading the standard
for 24 hours
54.00 EUR
English Hardcopy
In stock
180.00 EUR
Standard number:BS ISO/IEC TR 14759:1999
Pages:22
Released:2000-05-15
ISBN:0 580 34735 4
Status:Standard
DESCRIPTION

BS ISO/IEC TR 14759:1999


This standard BS ISO/IEC TR 14759:1999 Software engineering. Mock up and prototype. A categorization of software mock up and prototype models and their use is classified in these ICS categories:
  • 35.080 Software

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.