Chapter 4 System Analysis Quiz Thompson UAB

Wireframe

A company developed an early-stage UI model for its customer-facing application using only a few simple elements to show the location of text blocks, images, and major controls on the screen. The models did not include any data nor any details of the controls. Therefore, it is a______

a. I independent of all other user stories

b. N negotiable - not a specific contract for features

c. V valuable

d. E estimable - lends itself to estimation, a good approximation

e. S small - so that it fits within an iteration, such as a single Sprint

f. T testable, at least in principle even if there is not yet a test for it yet.

1. A widely used model for analyzing the quality of user stories is INVEST. A good user story should be:

True

Each regular user story typically shares a relationship with many acceptance criteria.

True (epic)

Likewise, an epic user story typically shares a relationship with many regular user stories.

True (user stories and UI models)

1. The development of user stories and UI models benefits from the context specifications available in process models and domain models that were developed in an earlier phase of a typical software project.

Author

The _____ is not a key element of a user story since user stories are produced by teams typically.

Features

1. The purpose of user stories is to specify a system's _____

1. Process UI models are_______of the processes specified with activity diagrams

NOT Independent

a. Unstructured

b. Semi-structured

c.Structured

1. From more flexible to less flexible, the order of interview methods is:

a. Interviewing

b. Focus Groups

c. Observation

d. Prototyping

e. Surveys

1. Discovery methods for systems analysis and design include:

a. MH - Must Have

b. SH - Should Have

c. CH - Could Have

d. WH - Won't Have

1. In order of importance, the MoSCoW options for prioritizing software features is:

It is possible through UI modeling that the expected system capabilities are so welldefined that separate UI modeling for discovering features is not necessary

true (UI Modeling for discovering features)

Time spent on UI modeling should be aligned with the _________.

Expected Development Time

UI models can support the process of discovering necessary ________ _________

System Features

Business Analysis Phase

1. During the ______ _____ ______, UI modeling supports communication between various stakeholder groups within the development process.

The correct order of increasing level of details for user interface modeling approaches, from least to most detailed is:

a. Wireframes

b. Mockups

c. Prototypes

Planning and Analysis Phase

20. Even an agile project requires an initial _

________ and ______ _____that sets the stage for the rest of the project.

Epic User Stories

_____ ____ ____ provide an effective way to group related, regular user stories by utilizing a high level of abstraction.

Acceptance Criteria

a. are expressed in the context of a user story

b. can be seen as constraints that limit acceptable implementation options

c. provide additional specificity compared to the related, base user story

d. are the same as conditions of satisfaction

Systems Design(hows

1. The main difference between __________ and System Features is that the Features are about the "what's" , while the _____- are about the "how's" .

Systems Features (whats)

23. The main difference between System Designs and_____ ____ is that the ________ are about the "what's" , while the Designs are about the "how's" .

Survay

What is a discovery method you would choose if your goal was to collect data from a large number of prospective users in a relatively short amount of time?

Always prioritize the use of technically correct terminology, regardless of its familiarity to the Systems Analysis & Design process stakeholders

Which one of the following statements is not compatible with your textbook's guidance regarding Business Analyst communication practices

feasibility

1. For Systems Analysis & Design purposes, _____- is the extent to which it is likely that a project can be completed successfully.

Still learning (24)

You've started learning these terms. Keep it up!