March 10,
2005
Group 13: 9602759
0326978
-----------------------------------------------------------------------------------------------------------------------
Seng310 Project Deliverable
The Bus Mapper
TABLE OF CONTENTS
1.1 Purpose
1.2 Project Overview
1.3
Objectives
2. Stakeholders and
User Profiles
2.1 Stakeholders
2.2 User Profiles
3.1 User Requirement : Casual Users
3.1.1 Functional Requirement
3.1.2 Scenario
3.1.3 HTA
3.2 User Requirement : Frequent Users
3.2.1 Functional Requirement
3.2.2 Scenario
3.2.3 HTA
3.3 User Requirement : User Ability & Skills
3.3.1 Functional Requirement
3.3.2 Scenario
3.3.3 HTA
4.1 Member #1
4.2 Member #2
The purpose of this document is to provide requirement information involved in the bus mapper project.
The information will include the identification of stakeholders and user profiles, requirement analysis,
and task analysis using Hierarchical Task Analysis (HTA).
The bus mapper is a web based application which enables bus users to get
information about the bus transportation system. The bus mapper
will provide a feature that will automatically calculate shortest route and
display the series of buses one might take to travel from a desired source to a
destination and associated
estimated time.
¡¤
Identify user needs and establish user requirements
¡¤
Identify possible user profiles
¡¤
Analyze the requirements
¡¤
Create scenario based on the user profiles
¡¤
Hierarchical Task Analysis (HTA) on the scenarios
The stakeholders and their
goals are:
¡¤
Students
¨ª
The goal of students is mainly to get information of
transportation between school and their home.
¡¤
Commuters
¨ª
The goal of commuters is getting transportation
information during commuting hours.
¡¤
The project design members
¨ª
The goal of the project design member is to develop a
user friendly and efficient web based application design that allows users to
get bus information in more convenient and efficient way.
¡¤
Tourist / New Comer
¨ª
The goal of tourists is to getting more specific information
of transport system. They might want to know what buses to take and where to
get off.
¡¤
People with disability
¨ª
The people with disability might want to know when
wheelchair accessible bus is available.
¡¤
BC Transit
¨ª
The goal of BC Transit is to retrieve statistical
information, so that more buses are scheduled on busy bus line.
Two user profiles involved in
Bus transit system are:
¡¤
User Profile #1
Users who do not
have a good understanding of
Such users might want to know
how to get to a particular place. The system should enable users to search for
a certain well known place and get information how to get there. The search
result will have to show series of buses one might take and bus station one should get off at.
Persona approach:
Paul is a tourist who came to
¡¤
User Profile #2
Users who have a good
understanding of
Users who know places around
Persona approach:
Sean is a teenage high school
student who commutes between school and home by bus. He spends a couple of
hours playing game on computer or spends more than an hour for browsing websites per day. He tries
to carry a bus schedule with him all the time, but he always forgets or looses
it. He finishes his last class and he wants to go to downtown with his friends
and play with his friends before go home. He exactly knows which bus to take
but he wants to know what time he has to get on the bus, since he wants to get
home before his mother comes home from her work.
|
Requirement #: 1 |
Requirement
Type: Functional |
Event: search shortest
route |
|
|
Description: The
system searches information with given source and destination. |
|||
|
Rationale: Casual users,
such as tourists, might want to get transit information by searching source
and destination. |
|||
|
Source: The project
design members |
|||
|
Fit Criterion: When user
searches for source and destination, the system queries corresponding bus information. |
|||
|
Dependencies: None |
Conflicts: None |
||
|
Supporting
Materials: Specification of bus mapper Project |
|||
|
History: Raised
on March
9, 2005 |
|||
A user browses through the bus mapper website.
The bus mapper has a map which contains all the bus routes and bus stops as well
as well known landmarks. The user
studies the map closely to determine the location of the destination and the
source. Once the user has determined desired source and destination, he or she
clicks on the source bus stop icon and then click on the destination stop. The
system then highlight the shortest route in distinct color and displays
associated bus numbers on the route. Also, it displays the conjunction at which
the user might have to transfer to another bus line. At last, the total
estimated time is displayed on the destination bus stop. If the user wants to
see schedule information about associated buses, he or she might click on
¡°schedule¡± icon.
This scenario is relevant to user profile #1, users who do not have a good
understanding of
0. To retrieve information by source and destination
1. user loads the
bus mapper web application
2. user determines
source and destination bus stops
3. user clicks on
the source stop
4. clicked bus
stop icon is changed into different color
5. user clicks on
the destination stop
6. clicked bus
stop icon is changed into different color
7. the system determines
shortest route and highlights it and displays associated bus numbers
8. the system
calculates estimated time and displays it
9. the system
shows the conjunction point of transfer
Plan0: do 1-2-3-4-5-6-7-8. If transfer required do 1-2-3-4-5-6-7-8-9.
|
Requirement #: 1 |
Requirement
Type: Functional |
Event: display schedule |
|
|
Description: The
system displays the schedule for specified bus number. |
|||
|
Rationale: Frequent users
might want shortcuts to view wanted bus schedule. |
|||
|
Source: The project
design members |
|||
|
Fit Criterion: When user clicks
on bus number shortcut icon, the system displays associated bus schedule. |
|||
|
Dependencies: None |
Conflicts: None |
||
|
Supporting
Materials: Specification of bus mapper Project |
|||
|
History: Raised
on March
9, 2005 |
|||
A user browses through the bus mapper website.
The bus mapper website has shortcut icons for all bus
lines. The icons are represented by corresponding bus numbers. The user clicks
on desired bus number icon. The system then displays three categories :
weekdays, Saturday, and Sunday/holiday schedule. The user clicks on desired
category, then the system displays complete schedule for selected category.
This scenario is relevant to user profile #2, users who have a good
understanding of
0. To retrieve schedule information
1. user loads the
bus mapper web application
2. user clicks on
desired bus number
3. the system
displays schedule categories
4. user clicks on
desired schedule category
5. the system
displays selected schedule
|
Requirement #: 3.2 |
Requirement
Type: Functional |
Event: wheelchair access info |
|
|
Description: The
system displays transit information about wheelchair accessible bus. |
|||
|
Rationale: Users with
disability might want to know schedule information with wheelchair accessible
buses. |
|||
|
Source: The project
design members |
|||
|
Fit Criterion: When user browses
through the system, if the user presses little wheelchair shaped icon, the
system filters schedule for wheelchair accessible buses only. |
|||
|
Dependencies: None |
Conflicts: None |
||
|
Supporting
Materials: Specification of bus mapper Project |
|||
|
History: Raised
on March
9, 2005 |
|||
A user loads the bus mapper website. The user
checks schedule in traditional way, selecting bus numbers. He or she wants to
know schedule for wheelchair accessible buses only. When the user presses
wheelchair shaped icon on top of the schedule information, the system filters
schedule so that only lower floor bus schedule is visible. If the user wants to
see the complete schedule, clicking on ¡°complete schedule¡± icon displays the
complete schedule.
This scenario is relevant to both user profile #1 and user profile #2, user
might or might not have a good understanding of
0. To retrieve wheelchair accessible bus schedule
1. user loads the
bus mapper website
2. user select bus
number and following schedule category
3. the system
displays requested schedule information
4. user presses
wheelchair button
5. the system
filters only wheelchair accessible bus schedule
6. user presses
complete schedule button
7. the system
displays the complete schedule
Plan 0: do 1-2-3-4-5. If complete schedule wanted do 6-7
¡¤
Identification of stakeholders and their goals
¡¤
Identification of user profile #2 and persona approach
¡¤
Develop scenario 3.2.2 based on user requirement
¡¤
Get information of Volere
template
¡¤
Hierarchical Task Analysis based on scenarios
¡¤
Identification of user requirements
¡¤
Identification of user profile #1 and persona approach
¡¤
Develop scenario 3.1.2 and 3.3.2 based on user
requirement
¡¤
Typing and formatting the document
Jennifer Preece, Yvonne Rogers, and Helen Sharp, Interaction Design:
beyond human-computer interaction, Wiley,
James & Suzanne Robertson. "Volere Requirements Specification Template¡±, Atlantic
Systems Guild. 2001.
< http://tinf2.vub.ac.be/~dvermeir/courses/software_engineering/SpecTemplate8.pdf>.