Prototyping

What Is a Prototype?

1 pts

volume_mute

Which of the following best describes a prototype in software development?

A fully tested, production-ready version of the final system

A formal mathematical model of the system specification

An initial version of a system used to demonstrate concepts, try out design options, and find out more about the problem and its possible solutions

A detailed design document produced before any code is written

note_alt Add notes

flag Flag

Correct Answer

Explanation

Prototype Development Process — Correct Order

1 pts

Please drag and drop the options to sort them

A prototype is developed through four stages. The diagram below shows these stages. Sort them into the correct order, from first to last.

Evaluate prototype

Establish prototype objectives

Develop prototype

Define prototype functionality

note_alt Add notes

flag Flag

Correct Answer

Explanation

Two Uses of a Prototype

1 pts

volume_mute

A software prototype can be used in two ways to help anticipate changes that may be required. Select both correct uses.

In the project management process, to estimate the final cost of the system

In the requirements engineering process, to help with the elicitation and validation of system requirements

In the acceptance testing process, to replace testing with real customer data

In the system design process, to explore particular software solutions and to support user interface design

note_alt Add notes

flag Flag

Correct Answer

Explanation

Why Prototyping Supports Change Avoidance

1 pts

Complete the sentence.

System prototypes allow users to (1) with the system before delivery and so refine their requirements. The number of requirements change proposals made after delivery is therefore likely to be (2).

Please drag and drop the selected option in the right place or type it instead

experiment

reduced

note_alt Add notes

flag Flag

Correct Answer

Explanation

What to Leave Out of a Prototype

1 pts

volume_mute

To reduce prototyping costs and accelerate delivery, certain things may be left out or relaxed when building a prototype. Which of the following may be omitted or relaxed? Select all that apply.

Error handling and management (unless the objective is to establish a user interface)

Standards of reliability and program quality

Non-functional requirements such as response time and memory utilisation

The core user interface being prototyped

Some functional requirements

note_alt Add notes

flag Flag

Correct Answer

Explanation

Why Delivering a Throwaway Prototype Is Unwise

1 pts

volume_mute

Developers are sometimes pressured by managers to deliver a throwaway prototype as the final system. Which of the following are reasons why this is usually unwise? Select all that apply.

Organisational quality standards are normally relaxed for prototype development

The prototype structure will probably have degraded during development, making it difficult and expensive to maintain

Rapid change during development means the prototype is undocumented and not suitable for long-term maintenance

It may be impossible to tune the prototype to meet non-functional requirements such as performance, security, and reliability that were ignored during development

Prototypes always cost more to build than production systems

note_alt Add notes

flag Flag

Correct Answer

Explanation

Prototype Objectives Must Be Explicit

1 pts

volume_mute

Why is it important that the objectives of prototyping are made explicit from the start of the process?

Because explicit objectives allow the prototype to be used as the final delivered system

Because the same prototype can meet all possible objectives simultaneously

Because if objectives are left unstated, management or end-users may misunderstand the function of the prototype and not get the benefits they expected

Because implicit objectives always result in lower prototyping costs

note_alt Add notes

flag Flag

Correct Answer

Explanation

General Problem with Prototype Evaluation

1 pts

volume_mute

What is a general problem with the evaluation stage of prototype development?

Users always find prototypes too complex to evaluate

Prototype evaluation can only be carried out by the original developers

The prototype may not be used in the same way as the final system — the tester may not be typical, training time may be insufficient, and slow response may cause evaluators to adjust their working style

Evaluation always requires the prototype to meet all non-functional requirements

note_alt Add notes

flag Flag

Correct Answer

Explanation

Paper-Based Prototypes

1 pts

volume_mute

True or False: Prototypes must be executable software systems — paper-based mock-ups cannot be effective prototypes.

True

False

note_alt Add notes

flag Flag

Correct Answer

Explanation

Wizard of Oz Prototype

1 pts

Complete the sentence about the Wizard of Oz prototyping technique.

In a Wizard of Oz prototype, only the (1) is developed. Users interact with this interface, but their requests are passed to a (2) who interprets them and outputs the appropriate response.

note_alt Add notes

flag Flag

What Is a Prototype?

Correct Answer

Explanation

Prototype Development Process — Correct Order

Correct Answer

Explanation

Two Uses of a Prototype

Correct Answer

Explanation

Why Prototyping Supports Change Avoidance

Correct Answer

Explanation

What to Leave Out of a Prototype

Correct Answer

Explanation

Why Delivering a Throwaway Prototype Is Unwise

Correct Answer

Explanation

Prototype Objectives Must Be Explicit

Correct Answer

Explanation

General Problem with Prototype Evaluation

Correct Answer

Explanation

Paper-Based Prototypes

Correct Answer

Explanation

Wizard of Oz Prototype

Correct Answer

Explanation

Quran Recitation

Query Dictionary

Select a result: