259
edits
Kilimanjaro/UseCases: Difference between revisions
m
→Set up Boot-2-Gecko Phone for Consumer
mNo edit summary |
|||
| Line 183: | Line 183: | ||
3b. Will the Browser have a "remind me later" feature that the consumer can return to later? | 3b. Will the Browser have a "remind me later" feature that the consumer can return to later? | ||
==Set up Boot-2-Gecko Phone for Consumer== | ==Set up a new Boot-2-Gecko Phone for a Consumer== | ||
''This one is in progress'' | |||
'''Level:''' Peak | |||
'''Scope:''' Black box | |||
'''Primary Actor:''' Clerk for a Mobile Phone Carrier | |||
'''Stakeholders and Interests:''' | |||
* The consumer wants | |||
** The new phone to contain their old contacts | |||
** A marketplace installed so they can download some new apps | |||
** The mobile equivalent of their desktop app to show up on the phone | |||
The clerk wants to import the users old contacts and get them signed into persona. | |||
The phone carrier wants to know that the phone as been properly activated so they can bill the consumer.l | |||
Precondition: | |||
* The user already has a persona account | |||
* The user has some apps installed on their desktop | |||
Minimal Guarantees:How the interests are protected under all exits | |||
Success Guarantees: The state of the world if the goal succeeds | |||
Trigger: What starts the use case, may be a time event | |||
Main Success Scenario: Steps of the scenario from trigger to goal delivery and any cleanup after | |||
Step number, action description | |||
Extensions: Put here there extensions, one at a time, each referring to the step of the main scenario. | |||
Step altered, condition: action or sub-use-case | |||
Technology & Data Variations List: Variations that will cause branching in the scenarios such as operating systems | |||