Information Management

24
1 Information Management DIG 3563 – Lecture 3.5: Requirements – Example and Formulating the Project J. Michael Moshell University of Central Florida Ferrit.com.a u. Imagery is fromWikimedia except where marked with *.

description

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. - PowerPoint PPT Presentation

Transcript of Information Management

Page 1: Information Management

1

Information Management

DIG 3563 – Lecture 3.5:

Requirements – Exampleand

Formulating the ProjectJ. Michael Moshell

University of Central Florida

Ferrit.com.au.

Imagery is fromWikimedia except where marked with *.

Page 2: Information Management

-2 - -2 -

My Example:Pet Dating Service

The problem: Dog owner wants

puppies, but not just ANY puppies.

* How to find the appropriate father?

* What’s in it for him?

dogsindepth.com

Page 3: Information Management

-3 - -3 -

The Steps

1. Identify stakeholders

2. Write one “user story” per stakeholder

3. Identify use cases and provide written descriptions & diagrams

4. List requirements for each use case, and for overall system

5. Establish measurable goals

6. Sketch a wireframe “mock-up” to show the client

paragonventures.com

Page 4: Information Management

-4 - -4 -

Stakeholder Identification

"Who cares?".

•Owners of female dogs

•Owners of male dogs

•Veternarians who may conduct health exams

•Breed associations who keep records

•Site owner/operator

Truelegends.coml

Page 5: Information Management

-5 - -5 -

Stakeholder Identification:(Grading?)

Are all the obvious stakeholders identified?

Are they distinct? (e. g. not just “Dog owners”)

Truelegends.coml

Page 6: Information Management

-6 - -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 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

Page 7: Information Management

-7 - -7 - -7 -

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

Page 8: Information Management

-8 - -8 - -8 -

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

Page 9: Information Management

-9 - -9 - -9 -

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

Page 10: Information Management

-10 - -10 -

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

Page 11: Information Management

-11 - -11 - -11 -

Use Cases: Written formFemale dog owner:

(1) enter description of my dog into the system

(2) scan descriptions of available male dogs

(3)verify male dog’s pedigree

(4)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

Page 12: Information Management

-12 - -12 - -12 -

Use Cases: GradingFemale dog owner:

(1) enter description of my dog into the system

(2) scan descriptions of available male dogs

(3)verify male dog’s pedigree

(4)verify your own dog’s health

(5) negotiate a breeding contract

(6) carry out the breeding

(7) provide feedback for future users

Everystakeholderhas atleast one use case

Use cases arewell describedand thoroughlycover the subject

www.wikipedia.org

Page 13: Information Management

-13 - -13 - -13 -

Use Cases: GradingFemale dog owner:

(1) enter description of my dog into the system

(2) scan descriptions of available male dogs

(3)verify male dog’s pedigree

(4)verify your own dog’s health

(5) negotiate a breeding contract

(6) carry out the breeding

(7) provide feedback for future users

Everystakeholderhas atleast one use case

Use cases arewell describedand thoroughlycover the subject

www.wikipedia.org

Page 14: Information Management

-14 - -14 - -14 -

Use Case Diagram: Owner of Female

Cs.rochester.edul

Owner of

Female dog

Enter description of

female dog

Scan male dog

descriptions

Verify your dog’s health

Vet

Association

Verify pedigree

Owner of

Male dogCarry out breeding

Negotiate Contract

Provide feedback

Page 15: Information Management

-15 - -15 - -15 -

Use Case Diagram: Grading

Owner of

Female dog

Enter description of

female dog

Scan male dog

descriptions

Verify your dog’s health

Vet

Association

Verify pedigree

Owner of

Male dogCarry out breeding

Negotiate Contract

Provide feedback

Correctusers for eachcase

Page 16: Information Management

-16 - -16 - -16 -

Use Case Diagram: Grading

Owner of

Female dog

Enter description of

female dog

Scan male dog

descriptions

Verify your dog’s health

Vet

Association

Verify pedigree

Owner of

Male dogCarry out breeding

Negotiate Contract

Provide feedback

Draw littlepeople (it’s part of the standard!)

Page 17: Information Management

-17 - -17 - -17 -

Use Case Diagram: Grading

Owner of

Female dog

Enter description of

female dog

Scan male dog

descriptions

Verify your dog’s health

Vet

Association

Verify pedigree

Owner of

Male dogCarry out breeding

Negotiate Contract

Provide feedback

Full text is NOT required(just titles ofcases)

Page 18: Information Management

-18 - -18 -

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’.

Page 19: Information Management

-19 - -19 -

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.)

Page 20: Information Management

-20 - -20 -

Requirements Lists: Grading

At least one requirement for every stakeholder and use case

Requirements are well thought out and thorough

Page 21: Information Management

-21 - -21 -

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.

Page 22: Information Management

-22 - -22 -

Measurable Goals; GradingNumbers tocompare tomeasurablequantities

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.

Page 23: Information Management

-23 - -23 -

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.

Specific datesfor measurement

Page 24: Information Management

www.wikipedia.org

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