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.
Levels for Mozilla Use Cases
Cockburn suggests an ocean metaphor to help give an idea about the granularity of user stories. Since we're "climbing Kilimanjaro," the following might make a better fit:
Peak - The highest-level stories describing our ecosystem in an abstract sense across the whole of Mozilla. 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 - These stories are high-level but are mostly high-level within a team. These use cases will also consist primarily of a few other use cases. Altitude use cases map mostly to business or system use cases. They can also be user-goals that stretch across teams.
Base Camp - These are bread and butter use cases that describe the main scenarios and work flows. They likely have steps that are use cases in other teams, but will mainly consist of implementation steps for a team. This maps 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.
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. These will only get a fully dressed use case if clarity is needed particularly across teams. Most often these end up being implementation details.
Install app from tech blog link
Level: Peak
Primary Actor: app consumer
Links:
- Casual user story
- Tracking bug
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