MozillaWiki

Kilimanjaro/UseCases: Difference between revisions

Page Discussion

Kilimanjaro/UseCases (view source)

Revision as of 21:03, 26 April 2012

8,816 bytes added ,  26 April 2012
m
→‎Set up Boot-2-Gecko Phone for Consumer
m (Created page with "We are in the process of writing fully dressed use cases and are reserving this page as an index for them. If you want to know what a fully dressed use case is, Alistair Cockbur...")
 
 
(27 intermediate revisions by the same user not shown)
Line 2: Line 2:


If you want to know what a fully dressed use case is, Alistair Cockburn defines it and gives lots of examples in, [http://www.amazon.com/Writing-Effective-Cases-Alistair-Cockburn/dp/0201702258 his book, Writing Effective Use Cases].
If you want to know what a fully dressed use case is, Alistair Cockburn defines it and gives lots of examples in, [http://www.amazon.com/Writing-Effective-Cases-Alistair-Cockburn/dp/0201702258 his book, Writing Effective Use Cases].
==Use Cases by level==
'''Peak''' - The highest-level stories for Kilimanjaro.  The steps for the main success scenarios in these cases will consist of other use cases.  Peak use cases map to enterprise or business level.
* [https://wiki.mozilla.org/Kilimanjaro/UseCases#Introduce_Firefox_Consumer_to_HTML5_apps_and_the_Mozilla_Marketplace Introduce Firefox Consumer to HTML5 apps and the Mozilla Marketplace - Existing Firefox User]
* [https://wiki.mozilla.org/Kilimanjaro/UseCases#Install_app_from_tech_blog_link Install app from tech blog link - Android Power User]
* [https://wiki.mozilla.org/Kilimanjaro/UseCases#Create_an_app_from_an_idea_in_5_Minutes Create an app from an idea in 5 Minutes - Web Developer]
'''Altitude''' - Also high-level and likely involving more than 1 area of Mozilla.  Altitude use cases map mostly to business or system use cases, but can also be user-goals that stretch across teams.
* [https://wiki.mozilla.org/Kilimanjaro/UseCases#Set_up_apps_ecosystem_to_obtain_a_specific_app Set up apps ecosystem to obtain a specific app]
'''Base Camp''' - Bread and butter use cases which map to user-goals and are actions that can be completed in one sitting.  Anything that can't be completed at a sitting or a few steps is an altitude or summary level goal.  Expect to see these on a notecard.
'''Gear''' - These are low-level, technical use cases that go all the way down to implementation details.  These types of use cases are at the task level.  Don't expect to see them written up.
==Install app from tech blog link==
'''Level:''' Peak
'''Primary Actor:''' apps consumer a.k.a. android power user
'''Links:'''
* [https://wiki.mozilla.org/Kilimanjaro/ProductDraft#Android_Power_User Casual user story in the Kilimanjaro Product Page]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=746446 Meta bug 746446]
'''Scope:''' System
'''Stakeholders and Interests:'''
* External site with a link to an app wants to serve working links
* User wants the app on their device quickly
* App developer wants to monitor the stampede of users downloading their app from the tech blog
'''Precondition:'''
* App is present and downloadable for the user's device in the Marketplace.
* Consumer is performing this use case with an Android phone.
* Consumer already has Marketplace set up for main success flow.
* Firefox and Marketplace are rockmelted together.
'''Minimal Guarantees:''' Marketplace shows an error page, request from user is logged.
'''Success Guarantees:''' app consumer gets the app on their device and can open it.
'''Main Success Scenario:'''
# User opens Firefox on their device
# on Techcrunch page, click link that says "New York Times app"
# link opens Marketplace details page for app
# Consumer installs app from Marketplace
# Consumer opens app
'''Extensions:'''
1a. User does not have Firefox installed
    1b. User  [https://wiki.mozilla.org/Kilimanjaro/UseCases#Set_up_apps_ecosystem_to_obtain_a_specific_app sets up apps ecosystem to obtain a specific app]
4a. App cannot be installed
    4b. User sees a Marketplace page saying app can't be installed
==Set up apps ecosystem to obtain a specific app==
'''Level:''' Altitude
'''Primary Actor:''' Apps Consumer
'''Scope:''' Black Box
'''Precondition:'''
* Consumer does not have Firefox installed on their device
* Consumer does not have a BrowserID/Persona account
* Consumer has Google Play installed on their device and is logged in
'''Minimal Guarantees:''' How the interests are protected under all exits
'''Success Guarantees:'''
* Consumer has Firefox installed on their device
* Consumer has app installed that they initially read about on the tech blog
* Consumer has a Persona account
'''Main Success Scenario:'''
# User installs Firefox from Google play
# User opens Firefox
# Firefox loads Marketplace page for app
# User clicks download
# Marketplace asks user to login/register through BrowserID/Persona
# BrowserID/Persona returns user to app details page in Marketplace
# User downloads app
'''Extensions:''' ''Each extension refers to a branch in behavior, good or bad, from the steps in the main success scenario.''
Number of step altered followed by action or sub-use-case
==Create an app from an idea in 5 Minutes==
'''Level: Peak'''
'''Meta Bug:''' [https://bugzilla.mozilla.org/show_bug.cgi?id=746446 746446]
'''Primary Actor:''' Web Developer
'''Stakeholders and Interests:'''
* Web Developer wants to build an app quickly
* MDN wants to serve documents that explain tools the developer can use to developer an app and how to upload their app
* Marketplace wants to be sure the app meets the minimum requirements  and host a pointer to the app in Marketplace
'''Preconditions:'''
* Developer has an idea for an HTML5 app but has not written the app yet.
* Developer has written HTML5 apps before.
* Developer has a place to host an app
* Developer has an account with Paypal
'''Minimal Guarantees:''' MDN shows a page that it is unavailable, unsuccessful request is logged.
'''Success Guarantees:''' Developer's app is listed in the Marketplace 5 minutes after initially reading the MDN pages.  Developer can see statistics of people downloading her app from the Marketplace
'''Main Success Scenario:'''
* Web developer clicks link that says "Go from idea to app in 5 minutes"
* A page on MDN titled "Go from idea to app in 5 minutes" opens
* Developer uses tools to create an app including hosting it somewhere
* Developer uploads the app to the Marketplace for $0.99
* After a week, the Developer reads reviews left of her app
Extensions: List the extensions, one at a time, each referring to the step of the main scenario.
Step altered, action or sub-use-case
Technology & Data Variations List:  Variations that will cause branching in the scenarios such as operating systems
==Introduce Firefox Consumer to HTML5 apps and the Mozilla Marketplace==
'''Level:''' Peak
'''Meta bug:''' Bug [https://bugzilla.mozilla.org/show_bug.cgi?id=746480 746480]
'''Primary Actor:''' Firefox Browser
'''Secondary Actors:'''
* Firefox Consumer
* Mozilla Marketplace
'''Scope:'''  Black box
'''Stakeholders and Interests:'''
Firefox wants to successfully update and give the user a pleasant introduction to HTML5 apps and the Mozilla Marketplace
The Firefox Consumer wants their browser to update successfully.
'''Precondition:'''
* The consumer already has Firefox installed
* Firefox is at the latest version.
Minimal Guarantees:How the interests are protected under all exits
'''Success Guarantees:'''
* Consumer's Firefox browser is updated. 
* Consumer has a BrowserID/Persona account
* Consumer has an app on their desktop
* Consumer has an app on a mobile device
* Statistics for the app's downloads are updated
Trigger: Update to Firefox 14
'''Main Success Scenario:'''
# The consumer opens Firefox
# Firefox updates itself
# <ins>Desktop Firefox helps the consumer discover Firefox, mobile, apps and ID</ins>
# <ins>Consumer explores the Marketplace</ins>
# <ins>Consumer installs an app to his Desktop</ins>
# <ins>Consumer registers for BrowserID/Persona</ins>
# <ins>Consumer installs the Marketplace</ins> on a separate device
'''Extensions:'''
3a. Consumer does not want to be introduced at this moment in time
Technology & Data Variations List:  Variations that will cause branching in the scenarios such as operating systems
  3b. Will the Browser have a "remind me later" feature that the consumer can return to later?
==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
Marlenac
259

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/420025...424792"