240 likes | 361 Views
Information Management. DIG 3563 – Lecture 3.5: Requirements – Example and Formulating the Project J. Michael Moshell University of Central Florida. Ferrit.com.au. Imagery is fromWikimedia except where marked with *. My Example: Pet Dating Service. dogsindepth.com.
E N D
Information Management DIG 3563 – Lecture 3.5: Requirements – Example and Formulating the Project J. Michael Moshell University of Central Florida Ferrit.com.au. Imagery is fromWikimedia except where marked with *.
My Example: Pet Dating Service dogsindepth.com • The problem: Dog owner wants • puppies, but not just ANY puppies. • * How to find the appropriate father? • * What’s in it for him? -2 -
The Steps paragonventures.com • Identify stakeholders • Write one “user story” per stakeholder • Identify use cases and provide written descriptions & diagrams • List requirements for each use case, and for overall system • Establish measurable goals • Sketch a wireframe “mock-up” to show the client -3 -
Stakeholder Identification Truelegends.coml • "Who cares?". • Owners of female dogs • Owners of male dogs • Veternarians who may conduct health exams • Breed associations who keep records • Site owner/operator -4 -
Stakeholder Identification: (Grading?) Truelegends.coml • Are all the obvious stakeholders identified? • Are they distinct? (e. g. not just “Dog owners”) -5 -
User Stories • Short enough to write on a 3" x 5" card. • As a <role>, I want <goal/desire>. • Example: • As an owner of a female dog “Princess Leia”, • I want a perfect litter of puppies, so that I • can keep one and sell five of them for $1000 • apiece. Cs.rochester.edul -6 - -6 -
User Stories • Short enough to write on a 3" x 5" card. • As a <role>, I want <goal/desire>. • Example: • As an owner of a male dog “Han Solo”, • I want a puppy and some income to • help pay for Han Solo’s vet bills. Cs.rochester.edul -7 - -7 -
User Stories • Short enough to write on a 3" x 5" card. • As a <role>, I want <goal/desire>. • Example: • As the site owner, I want to earn $50,000 or more • per year through the sales of advertising on • the site, and through user fees. • ((Also we need user stories for the other • two stakeholder classes)) Cs.rochester.edul -8 - -8 -
User Stories: Grading • Does it follow the pattern? • As an xxxx I want yyyy • Is it brief (30 words or less)? • Is it clear? (can you tell when it is achieved, • without complex judgement calls?) Cs.rochester.edul -9 - -9 -
Use cases: • It is a single KIND of interaction with a system • We define Use Cases to help design User Interfaces • The Use Case does NOT explain. It just identifies – • The actor or actors • The activity • UC is the first step in Analyzing the User Story -10 -
Use Cases: Written form • Female dog owner: • (1) enter description of my dog into the system • (2) scan descriptions of available male dogs • verify male dog’s pedigree • verify your own dog’s health • (5) negotiate a breeding contract • (6) carry out the breeding • (7) provide feedback for future users www.wikipedia.org -11 - -11 -
Use Cases: Grading • Female dog owner: • (1) enter description of my dog into the system • (2) scan descriptions of available male dogs • verify male dog’s pedigree • verify your own dog’s health • (5) negotiate a breeding contract • (6) carry out the breeding • (7) provide feedback for future users www.wikipedia.org Every stakeholder has at least one use case Use cases are well described and thoroughly cover the subject -12 - -12 -
Use Cases: Grading • Female dog owner: • (1) enter description of my dog into the system • (2) scan descriptions of available male dogs • verify male dog’s pedigree • verify your own dog’s health • (5) negotiate a breeding contract • (6) carry out the breeding • (7) provide feedback for future users www.wikipedia.org Every stakeholder has at least one use case Use cases are well described and thoroughly cover the subject -13 - -13 -
Use Case Diagram: Owner of Female Enter description of female dog Cs.rochester.edul • Association Scan male dog descriptions Verify pedigree • Vet • Owner of • Female dog Verify your dog’s health Negotiate Contract • Owner of • Male dog Carry out breeding Provide feedback -14 - -14 -
Correct users for each case Use Case Diagram: Grading Enter description of female dog • Association Scan male dog descriptions Verify pedigree • Vet • Owner of • Female dog Verify your dog’s health Negotiate Contract • Owner of • Male dog Carry out breeding Provide feedback -15 - -15 -
Draw little people (it’s part of the standard!) Use Case Diagram: Grading Enter description of female dog • Association Scan male dog descriptions Verify pedigree • Vet • Owner of • Female dog Verify your dog’s health Negotiate Contract • Owner of • Male dog Carry out breeding Provide feedback -16 - -16 -
Full text is NOT required (just titles of cases) Use Case Diagram: Grading Enter description of female dog • Association Scan male dog descriptions Verify pedigree • Vet • Owner of • Female dog Verify your dog’s health Negotiate Contract • Owner of • Male dog Carry out breeding Provide feedback -17 - -17 -
Requirements Lists • GENERAL requirements, and • CASE BY CASE requirements • GENERAL requirements for the dog breeding registry: • All users must register; e-mail addresses must be verified • Users must be offered clear guidance to classify themselves • owner of female; owner of male; vet • Costs to users (if any) must be clearly stated up-front • * Relations with AKC, other breed associations must be negotiated (they probably don’t want to be ‘registered users’. -18 -
Requirements Lists: An example • OWNER OF FEMALE: • Case=Enter description of female dog • Required fields: • Name • Breed (pulldown list of AKC recognized breeds+”mutt”) • Age • Temperament (pulldown list) • Name • Weight • Owner’s statement (text description of what is wanted.) -19 -
Requirements Lists: Grading • At least one requirement for every stakeholder and use case • Requirements are well thought out and thorough -20 -
Measurable Goals Lrn.usace.army.mil • Our site will have at least 100 registered users by 90 days • after site launch. • Our site will generate 500 hits a week by 120 days after • site launch. • Our site will generate $2000 a month in AddSense revenues • by 180 days after site launch. • User satisfaction will be 3.5/5 or better at all times. -21 -
Numbers to compare to measurable quantities Measurable Goals; Grading • Our site will have at least 100 registered users by 90 days • after site launch. • Our site will generate 500 hits a week by 120 days after • site launch. • Our site will generate $2000 a month in AddSense revenues • by 180 days after site launch. • User satisfaction will be 3.5/5 or better at all times. -22 -
Specific dates for measurement Measurable Goals; Grading • Our site will have at least 100 registered users by 90 days • after site launch. • Our site will generate 500 hits a week by 120 days after • site launch. • Our site will generate $2000 a month in AddSense revenues • by 180 days after site launch. • User satisfaction will be 3.5/5 or better at all times. -23 -
Mockups and Prototypes Not required for Round 1 (Cross-team) Requirements For Round 2 (presented in Oct) we want to see a simulated step-by-step of how each STAKEHOLDER would use the site to conduct two key USE CASES www.wikipedia.org