Requirementsto Concept

ysdn3006

Form

BehaviourContent

What does it look like?

How does itwork?

What is it?

Visualize

StructureUnderstand

Visualize

StructureUnderstand

Requirements

• generated by conducting user research

• develop a list of “needs” not features

• move from requirements to conceptual design

How and Why?

Requirements

People’sActivities inContexts

Requirements

User Research

Conceptual Design

Requirements

• functional requirements - what the system should do

• data requirements - accuracy, size, amount, persistence

• environmental requirements - physical, social, organizational, technical

• user characteristics - skills, abilities, culture, language, novice, expert (user profile)

MoSCoW Rules

• Help determine priority of requirements

• Must have - fundamental requirements needed otherwise system would be unworkable and useless

• Should have - essential given time and resources, but system would still function without

• Could have - of lesser importance, can be left out

• Want to have but Won’t - can wait till later

Evaluating Requirements

Requirement Rationale Priority

Data Requirement

The system will need to provide

frequent updates toinformation

Will promote better integration with

current events to foster community

building

Should have

Requirement to Concept

Requirement Content Function

Data Requirement

The system will need to provide

frequent updates toinformation

- calendar of events, news

-member and community news- political events

A user generated note that indexes

to a system calendar

Another way to think about it....

• make a list of all the “actions” of participants

• verbs (eg. reading, touching, walking, learning, thinking, understanding, experiencing, observing)

• make a list of all associated “objects”

• nouns (eg. historical information, maps, signage, books, photos)

• Then try to imagine functions to support the connections (eg. a photo timeline that displays on a map)