Kilimanjaro/UseCases
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 Cockburn defines it and gives lots of examples in, 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.
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.
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: app consumer
Links:
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 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: 746446
Primary Actor: Apps Developer
Stakeholders and Interests:
- Apps 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:
- Apps 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