DOC PREVIEW
CU-Boulder CSCI 5828 - Gathering Requirements

This preview shows page 1-2-3-24-25-26-27-49-50-51 out of 51 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 51 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 51 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 51 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 51 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 51 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 51 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 51 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 51 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 51 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 51 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 51 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

© University of Colorado, 2010Gathering RequirementsKenneth M. AndersonUniversity of Colorado, BoulderCSCI 5828 — Lecture 5 — 01/26/20101GoalsReview material from Chapter 2 of Pilone & MilesConcepts includeRequirements and Requirements GatheringUser StoriesBrainstormingPlanningEstimation GameWill also review requirements-related info not from textbook2Requirements GatheringRequirements gathering begins with a problem statement from your customer. Example:We need a web site showing our current deals, and we want our users to be able to book shuttles and special packages, as well as pay for their bookings online. We also want to offer a luxury service that includes travel to and from the spaceport and accommodation in a local hotelCharacteristics?Loose, informal, unstructured, all over the place (deals, bookings, packages, payment, shuttle services, hotels)3Title: Description: 4Title: Description: Title: Description: Title: Description: First Step: Impose StructureIdentify all of the different things the system has to do.5In particular, find requirementsA requirement is a single thing that the software has to doTitle: Show Current DealsDescription: The website will show current deals to Orion's Orbits users.6Note:Title: Show Current DealsDescription: The website will show current deals to Orion's Orbits users.Written in User’s LanguageInformal: because we don’t have a lot of informationBut, allows us to validate initial understanding of domain7Translate Entire Problem Statement:Title: Show Current DealsDescription: The website will show current deals to Orion's Orbits users.Title: Book a shuttleDescription: An Orion's Orbits user will be able to book a shuttle between hotel and spaceport.Title: Book packageDescription: An Orion's Orbits user will be able to book a special package with extras online.Title: Pay onlineDescription: An Orion's Orbits user will be able to pay for their bookings online.Title: Arrange TravelDescription: An Orion's Orbits user will be able to arrange travel to and from the hotel.Title: Book a hotelDescription: An Orion's Orbits user will be able to book a hotel.8Then, return to customer and:Title: Show Current DealsDescription: The website will show current deals to Orion's Orbits users.Title: Book a shuttleDescription: An Orion's Orbits user will be able to book a shuttle between hotel and spaceport.Title: Book packageDescription: An Orion's Orbits user will be able to book a special package with extras online.Title: Pay onlineDescription: An Orion's Orbits user will be able to pay for their bookings online.Title: Arrange TravelDescription: An Orion's Orbits user will be able to arrange travel to and from the hotel.Title: Book a hotelDescription: An Orion's Orbits user will be able to book a hotel.•ask questions•Did I get this right?•What did you mean by…•and gather more requirements•Is this really all of the functionality that you need?•If we built all of this, what would you want in version 2.0?Title: New RequirementDescription: Pithy text describing new requirement...All this work will lead to new or clarified requirementsNote: iteration9Problem: Not Enough?One problem that you’ll encounter is that this back and forth may not be enough to get to crisp detailed requirementsor you feel that you just don’t have a good grasp on the big pictureThis can be especially true if “customer” ≠ “end user”Next step is to hold a brainstorming session with as many different stakeholders as possiblewhat the book calls a “bluesky session” and is sometimes called “shooting for the moon”Bluesky SessionBrainstorming sessionGoal: get stakeholders to generate tons of candidate requirements; not everything will make it into the final systemSecondary Goal: Capture everything for later analysisThings to AvoidThe Silent Tomb®: Leave job titles at the door, people should not feel afraid to speak up just because the boss is thereCriticizing people rather than ideasDeveloper jargon “NOT ‘AJAX’ but ‘rich user interface’”1011Air Traffic ControlFlight TrackingAirportsNationsShippingair traffic controlflight numbersGate SchedulingAirlinesEmployeesLuggageGovernmentsRegulationsPackagesAnimalsInvoicingMultiple Companies on Single Transactionphysics of flightAirportsAirportsLuggageAirlinesEmployeesSchedulingFlightsSchedulingAirline/Airport handoffBag numbersHandling of oversize itemsHandling of live animals1.a.i.1.ii.1.2.a.b.c.d.Make use of outliners and other types of note taking applications during brainstorming sessions to capture the generated ideas, domain knowledge, and requirements; to the right is an example generated by Curio, a note taking application from Zengobi.Tool SupportGray SkiesIf things go wrong during the bluesky session: “bad boss”Make use of other techniquesInterview end users and have them pretend to interact with their “ideal system”, what the book calls “role playing”Observe them working on tasks related to the systemhow would the task change if the system were present?Review the documents they use nowask if the document would go away if the system were presentor how would it change?12Next? User StoriesTransform requirements gathered so far into user storiesA user story describes how the user interacts with the software you’re buildingIt should be written from your customer’s perspective and describe what the software is going to do for the customerUser stories are essentially informal use casesSee CSCI 5448 for more details on use cases13User StoriesSHOULDdescribe one thing the system should do for the customerbe written using language that the customer understandsbe written by the customerbe short. No longer than three sentencesSHOULD NOTbe a long essayuse technical terms unfamiliar to the customermention specific technologies (save those for design)14Requirements Life CycleWe now have a life cycle for use at the start of a projectCapture basic ideas from problem statementReturn with first pass, ask questions, set-up bluesky sessionITERATEConstruct User StoriesFind holes with stories and fix them with customer feedback, find new requirements, ask questions to assess completenessFinish with initial set


View Full Document

CU-Boulder CSCI 5828 - Gathering Requirements

Documents in this Course
Drupal

Drupal

31 pages

Deadlock

Deadlock

23 pages

Deadlock

Deadlock

23 pages

Deadlock

Deadlock

22 pages

Load more
Download Gathering Requirements
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Gathering Requirements and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Gathering Requirements 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?