Prototyping in Development

Questions and Answers

What is the primary purpose of creating a throwaway prototype?

To test the system's scalability

To build the final system

To determine the final system design

To validate requirements or determine design options (correct)

What is a key characteristic of evolutionary prototypes?

They are only used for user testing

They are not revised after creation

They are created and then discarded

They are revised continuously as precision increases (correct)

What is an important consideration when writing user stories?

Writing them in a way that is technical

Writing them in a way that is vague

Writing them in a way that is valuable to the customer/end user (correct)

Writing them in a way that is valuable to the developers

Why is it important for user stories to be estimatable?

So that the developers know how long it will take to implement Signup and view all the answers

What is a key characteristic of iterative prototypes?

They are revised continuously as precision increases Signup and view all the answers

What happens when a user story is too large to fit within a timebox?

It is split into smaller stories Signup and view all the answers

What determines whether a user story is appropriately sized?

The team, its capabilities, and technologies in use Signup and view all the answers

Why is it important to have conversations with developers when they lack domain knowledge?

So that they can clarify the requirements Signup and view all the answers

What is a key benefit of using horizontal prototypes in user interface design?

They offer a comprehensive overview of the system, ensuring coverage and consistency. Signup and view all the answers

Which of the following is NOT a characteristic of an effective user story in Agile development?

It should be complex and encompass multiple functionalities to ensure comprehensive development. Signup and view all the answers

Why is it important to define acceptance criteria for user stories?

To ensure that the story meets the user's needs and expectations. Signup and view all the answers

Which of the following statements is TRUE regarding the testability of user stories?

Stories for non-functional requirements are more difficult to test. Signup and view all the answers

What is a key advantage of using an evolutionary prototyping approach?

It allows for rapid and iterative development of the system. Signup and view all the answers

What is the purpose of using a throwaway prototype in the early stages of development?

To explore and validate design concepts and functionalities. Signup and view all the answers

Which of the following best describes the relationship between user stories and acceptance criteria?

Acceptance criteria are used to verify that a user story has been implemented correctly. Signup and view all the answers

Which of the following is an example of a testable acceptance criterion for a user story?

A screen should appear within 2 seconds of clicking a button. Signup and view all the answers

What characteristic of a good story is represented by the statement: "Stories should be self-contained and can be implemented in any order."

Independent Signup and view all the answers

Which fidelity level of a prototype is best suited for illustrating the details of data elements and their arrangement in a user interface?

High fidelity Signup and view all the answers

What is the primary focus of acceptance criteria in the context of agile development?

Describing the desired behavior of a feature Signup and view all the answers

Which statement best describes the purpose of a storyboard in prototyping?

To illustrate the user workflow and interactions with the system Signup and view all the answers

Which of the following is NOT a characteristic of a good user story in an agile development context?

Detailed design specifications Signup and view all the answers

Which fidelity level of a prototype would be most suitable for testing user interaction with a particular feature or workflow?

High fidelity Signup and view all the answers

What is the main advantage of using a rule-based format for documenting system behavior?

It facilitates the automation of tests Signup and view all the answers

Which of the following is an example of an acceptance criterion for a user story related to searching for suppliers?

The search function should allow users to refine their search based on specific criteria Signup and view all the answers

Study Notes

Evolution of Prototypes

Describes the expected lifecycle of a prototype, including throwaway, iterative, and evolutionary prototypes
Prototypes may be revised continuously as precision increases, with details of user interaction refined in each iteration

Types of Prototypes

Throwaway prototypes: created for a specific purpose and then discarded, used to determine requirements or validate design options
Iterative prototypes: revised continuously as precision increases, with details of user interaction refined in each iteration
Evolutionary prototypes: iterative prototypes that eventually become the final system, with tightly coupled design and implementation

User Stories

Write stories in a way that is valuable to the customer/end user
Stories should not be written for the developers
Estimatable: developers must be able to determine the time it will take to implement the story
Small: a fixed time period is allocated for each iteration in the development process
Template: context/scenario, action is carried out, set of observable consequences are expected
Examples:
- Given that I am a registered user, When I input my username and password, Then I get logged in to the system
- As a user, I want to have a search field to match a name or address in the list of suppliers

Characteristics of a Good Story (INVEST)

Independent: avoid dependencies between stories
Negotiable: allows room for negotiation through conversations
Valuable: write stories in a way that is valuable to the customer/end user
Estimatable: developers must be able to determine the time it will take to implement the story
Small: a fixed time period is allocated for each iteration in the development process
Testable: acceptance criteria must be set

User-Centered Approach

User participation is very beneficial
Horizontal prototypes provide an overview of the system to check consistency and coverage
Vertical prototypes focus on a specific feature or function to check feasibility

Physical Card and Other Formats

Physical card: a physical representation of a story or prototype
Other formats: rule-based or plain English, e.g., bulleted list of rules that describe the behavior of the system

Studying That Suits You

Use AI to generate personalized quizzes and flashcards to suit your learning preferences.

Description

Learn about the different types of prototypes, including throwaway and iterative, and their role in the development process.