Exam 2 Flashcards
What is a use case?
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.
Example of Use Case
Application | Use case
————-|———-
chemical | request
tracking sys-| a chemic
tem | -al
| change a
| request
| check status of order
difference between the main success(“sunny day”, “happy path”) scenario and alternative flows.
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
difference between a use case and a scenario
a use case is a collection of related usage scenarios and a scenario is a specific instance of a use case
describe some benefits that are derived directly from using Use Cases
- abstract outline of system code
- outline of user documentation
- provides for scenario analysis
- unit of panning (for work break down in project planning)
describe the relationship between a use case and requirements
-requirements fall right out of the dialog steps between the actor and the system
What is a user requirement?
user goals or business tasks that users need to perform (use case, scenarios, user stories)
What is a system requirement?
describe the requirements for a product that is composed of multiple components or subsystems
Main Success (sunny day, happy path)
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.
IKIWISI
I’ll know it when I see it
Makes an image of the development teams best guess at the right software to build
Prototype
a partial or possible implementation of a proposed new product. used to resolve uncertainty early in development
Purpose of prototype
- clarify, complete, and validate requirements
- explore design requirements
- create a subset that will grow into the ultimate product
horizontal prototype (mock-up)
demonstrates the functional options the user will have available w/o real functionality
vertical prototype (proof of concept)
IMPLEMENTS application functionality; works like the real system is supposed to
level of fidelity
the amount of detail in a prototype
high fidelity
shows exactly what the prototype will look like (ex. screen layout)
low fidelity
renditions with details missing(ex. storyboard)
Storyboard with PowerPoint
- add a shape with label
- add a hyperlink
- select place in document
- create a slide for each page of app
- add animation
Elements of Business Process Model
- start event
- gateway
- task
- swimlane, pools
- end event
the difference between storyboard and what we do in the course
Irise has the ability to take provided input and use it on the following pages
trace links
allow you to follow the life of the requirements forward and backward
trace suspect
when one of the linked artifacts are changed, its marked as suspect
