Exam 2

Question 1

What is a use case?

Answer 1

describes a sequence of interactions between a system and an external actor that results in the actor being able to achieve an outcome of value.

Question 2

Example of Use Case

Answer 2

Application | Use case

————-|———-

chemical | request

tracking sys-| a chemic

tem | -al

                | change a 

                | request

                | check  status of order

Question 3

difference between the main success(“sunny day”, “happy path”) scenario and alternative flows.

Answer 3

a user who says, “the default should be…” is describing the normal flow. a statement such as “the user should also be able to….” suggests an alternate flow

Question 4

difference between a use case and a scenario

Answer 4

a use case is a collection of related usage scenarios and a scenario is a specific instance of a use case

Question 5

describe some benefits that are derived directly from using Use Cases

Answer 5

• abstract outline of system code
• outline of user documentation
• provides for scenario analysis
• unit of panning (for work break down in project planning)

Question 6

describe the relationship between a use case and requirements

Answer 6

-requirements fall right out of the dialog steps between the actor and the system

Question 7

What is a user requirement?

Answer 7

user goals or business tasks that users need to perform (use case, scenarios, user stories)

Question 8

What is a system requirement?

Answer 8

describe the requirements for a product that is composed of multiple components or subsystems

Question 9

Main Success (sunny day, happy path)

Answer 9

a numbered list of steps indicating whic entity performs each step. the steps in a normal flow indicate where the user can branch into an alternative flow.

Question 10

IKIWISI

Answer 10

I’ll know it when I see it

Makes an image of the development teams best guess at the right software to build

Question 11

Prototype

Answer 11

a partial or possible implementation of a proposed new product. used to resolve uncertainty early in development

Question 12

Purpose of prototype

Answer 12

• clarify, complete, and validate requirements
• explore design requirements
• create a subset that will grow into the ultimate product

Question 13

horizontal prototype (mock-up)

Answer 13

demonstrates the functional options the user will have available w/o real functionality

Question 14

vertical prototype (proof of concept)

Answer 14

IMPLEMENTS application functionality; works like the real system is supposed to

Question 15

level of fidelity

Answer 15

the amount of detail in a prototype

Question 16

high fidelity

Answer 16

shows exactly what the prototype will look like (ex. screen layout)

Question 17

low fidelity

Answer 17

renditions with details missing(ex. storyboard)

Question 18

Storyboard with PowerPoint

Answer 18

1. add a shape with label
2. add a hyperlink
3. select place in document
4. create a slide for each page of app
5. add animation

Question 19

Elements of Business Process Model

Answer 19

• start event
• gateway
• task
• swimlane, pools
• end event

Question 20

the difference between storyboard and what we do in the course

Answer 20

Irise has the ability to take provided input and use it on the following pages

Question 21

trace links

Answer 21

allow you to follow the life of the requirements forward and backward

Question 22

trace suspect

Answer 22

when one of the linked artifacts are changed, its marked as suspect