Kilimanjaro/UseCases
Jump to navigation
Jump to search
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.
Install app from tech blog link - Peak
Primary Actor: app consumer
Links:
- Casual user story
- Tracking bug
Scope: System
Level: Summary
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