JSOM-Smart Destination

University of Texas at Dallas

Mir Ali, Dorcas Sipoche, Juliet Akinkugbe, and Nhan Ha
Group 2

Table of Contents
Executive Summary ........................................................................................................................ 1
System Proposal and Project Statement ....................................................................................... 2
Project Charter.2
Scope Statement.3
Work Breakdown Structure5
Requirements Definition..6
User Stories6
Functional Requirements.6
Non-Functional Requirements..7
Structural Models..8
Behavioral Models.9
Use Case Descriptions..10
Dynamic Models..13
Design Documents..14
User-Interface Design..14
Control Mechanisms.15
Method Specification16
Testing.19
Test Cases.20
Project Management Documents23
Meeting Minutes.23
Lessons Learned26
Dorcas Sipoche.2x
Juliet Akinkugbe2x
Nhan Ha.2x
Mir Ali.2x

Executive Summary
The JSOM-Smart Destination is a system that is intended to improve navigation within the
Naveen Jindal School of Management (JSOM) at the University of Texas at Dallas (UTD). The
university currently provides color-coded campus maps but they do not provide interior
navigation and there is still a complexity for new incoming students, professors, current students
at the beginning of the semester, and guests of the school when locating their specific areas.
The objective of this system is to help users find their locations by providing accurate door to
door directions, not just the building. Also another objective is to encourage users to explore
campus resources that are available such as computer labs, tutoring labs, and professor offices.
Finally, our last objective is to identify problem locations by analyzing the data generated from
this system which will be vital for future campus planning and design projects.
The expected value realized by this system proposal will be greater use of campus resources by
students. No longer will students be discouraged to go out of their way to locate needed help
offered by the school, these resources will be easily accessible and grades will benefitted from
this new navigation system. This is a great opportunity for UT-Dallas to grow and distinguish
themselves from other schools by decreasing user confusing which is vital for incoming students
transitioning into the school.

System Proposal and Problem Statement

Project Title:

JSOM-Smart Destination

Project Start Date: 09/07/2015

Projected Finish Date: 11/30/2015

Budget Information:
The main budget requirement to complete this project is staff time. The app is free, so there is
no cost to implement it. We might need a small amount of funds to reimburse any students/
faculty for their time used for testing.
Project Manager: Dr. DO - 972 883 4901 - email: dawn.owens@utdallas.edu
Project Objectives:
Project Goal: help students (both incoming and current), professors, support staff and guests,
find their locations in an organized and timely manner.

Provide door to door navigation within UT Dallas Naveen Jindal School of

Management (JSOM).
Targets: students, instructors, support staff, visitors etc.
Encourage user exploration to utilize available resources e.g. labs, meeting
rooms and TA offices, within JSOM.
Future expansion to other schools within the university.
Will be integrated with, and launched through UT Dallas site
Success Criteria:
Comprehensive floor plan of JSOM
Determine restricted areas
Number of students currently enrolled
Number of instructors and support staff currently employed
Assigning tasks to the team members
Reviewing and doing a rework when needed
Managing project risks efficiently
Approach:
Ask students/ faculty for feedback after using the app

Comments:

Scope Statement
Project Title: JSOM Smart Destination
Date: Oct 14, 2015
Prepared by: Dorcas Sipoche
Project Justification: Group 2 opted for the UTD JSOM Smart Destination system due
to navigation difficulties within UTD experienced by students, faculty and visitors alike.
The system will reduce the number of minutes it takes for users to locate their destination
by providing interior navigation within UT Dallas Naveen Jindal School of Management
(JSOM)
Product Characteristics and Requirements:
1. The system will be downloaded through JSOM website
2. The system will be accessible on mobile devices e.g. phone, tablets etc.
3. The system will allow users to register their assigned credentials (user names and
passwords)
4. The system should launch within 3 seconds of signing in.
5. Main requirements of the JSOM Smart destination are to:
Enable users locate their class rooms and/or other locations with JSOM using the room
number
Allow users to save their destinations
Allow users to provide feedback by leaving a comment when the trip has ended
Track locations most sought (for JSOM Managements use only)

Acceptance Criteria:
1. A functional interior navigation
2. User registration ability

Summary of Project Deliverables

Project management-related deliverables: Executive Summary, charter, scope
statement, WBS, cost baseline, final project presentation, final project report, lessonslearned report.
Product-related deliverables:
UTD Smart Destination requires door-to-door navigation within JSOM. A survey from
a selection of students indicated that at the beginning of the semester, it takes several
weeks for some students to comfortably locate their class rooms.
1. Initial design of the new system will include JSOM floor plans, Class room
numbers, navigation graphics, and design of the required features like registration,
tracking, etc. There will also be a feature for user feedback in the final design.
2. The system will include a feature for registration, save destination, and user
feedback
3. Testing will include the development of test plans to document how the system
will be tested, who will do the testing, and how bugs will be reported
4. Training will be a simplified 5-Step, 5-minutes process that will launch
automatically after user registration and :
3

Show the user how to launch the system

Enter destination code (e.g. class room number)
Follow the directions to destination
End upon arrival at destination
Save destination (optional)

The users can also opt for staying Signed In.

During rollout the team will be on hand at (location to be determined) to assist new users as
needed. Additional support will also be available online and from some experienced users, as
needed.

Project Exclusions: At its initial launch the system will not provide navigation in other
schools within UT Dallas and the campus grounds.
Project Constraints:
1. Complexity of the project limits us to start the system at UT JSOM only
2. Time

Project Success Criteria: To complete this project within six months.

Our main goal is to successfully provide door-to-door navigation within UT Dallas
Naveen Jindal School of Management (JSOM). Receive feedback from end users, (an
indication of interaction with the system) by the users and an opportunity to see areas of
improvement.

Work Breakdown Structure

Requirements Definition
User Stories:
1. As a student, I want to navigate around the JSOM building, so that I can arrive at my
classes in a timely manner.
2. As a project manager, I want to build a system using resources provided, so that I can
help save time for our customers.
3. As a JSOM visitor, I want to be able to navigate through the building efficiently, so that I
dont get lost.
4. As a new JSOM student, I want to be able to find my classes using point by point
directions on the first day of school.
5. As a JSOM faculty, I want to be able to locate my assigned classes for the semester in a
timely manner.
Functional Requirements:

The system should be able to detect continuously the current position of the user within
20 seconds.

The system must be able to update the route (shortest) according to detected position of
user and dead ends. If the system encounters a dead end, the system recalculates a new
route to the end destination.

The system should be able to communicate the route to the user through voice
commands. It notifies of upcoming turns through hallways, doors, and upon arrival to
destination.

The system must be able to generate a shortest path according to the detected position of
user in hallway and the specified end destination

The user must be able to activate/deactivate voice commands anytime in the system

The user must be able to login using a UTD Net ID and password for validation

Non-Functional Requirements:
Performance

The mobile interface of the system must be compatible with Android and IOS
The system should be able to perform to reflect average walking speed, motion and
obstacles in the environment
Reliability

The system should be able to detect obstacles within the range of 1 meters

Usability

The features of the system should operate uniformly for all users

Structural Models
Class Diagram:

Behavioral Models
Use Case Diagram:
JSOM Smart Destination Use Case Diagram

Use Case Descriptions:

Use Case Name:
Primary Actor:
Brief Description:
Stakeholders:
Trigger:
Normal flow of events:

Subflows:
Alternate/Exception flow:

Use Case Name:

Primary Actor:
Brief Description:

Stakeholders:
Trigger:
Normal flow of events:

Subflows:
Alternate/Exception flow:

Sign Up

User - Guest
This use case describes how the system treats guest
accounts
Optional
User opens app and types location room
- The user signs into to the app.
- The user must login using a valid UTD ID.
+ If user is a guest, system prompts user to sign up
using a valid email
- The system checks the validity of the guest email
- The user picks location
- The user follows the map
Optional
The email address is invalid.

Follow the map

User (Student/ Professor/ Guest)

This use case describes how the app help students,
professors, and guests, find their locations in an
organized and timely manner.
Optional
User sign in to the app and type location room
- The user get into to the app.
- The user must sign in with a valid UTD ID.
+ If user is a guest, then need to sign up and sign in
+ If user is student/ professor, then just sign in
- The system checks the validity of the ID card/ guest
information.
- The system process and update guest information
- The user login using a ID and password for
validation
- The user picks location
- The user follows the map
Optional
The UTD ID is invalid.
The user has a wrong room number.

10

Use Case Name:

Primary Actor:
Brief Description:
Stakeholders:
Trigger:
Normal flow of events:

Subflows:
Alternate/Exception flow:
Use Case Name:
Primary Actor:
Brief Description:
Stakeholders:
Trigger:
Normal flow of events:

Subflows:
Alternate/Exception flow:

Use Case Name:

Primary Actor:
Brief Description:

Stakeholders:

Pick Location
User (Student, Professors, Guests)
This use case describes how the system helps users
navigate
Optional
User opens app and types destination room number or
room name
- The user logs into the system
- The system locates the users current location
- The system prompts user to enter their destination
- The user follows the navigation guide
The system doesnt recognize users location
Process Info

Application Manager
This use case describes how the system gathers and
authorizes user system access information
Optional
User requests for JSOM-Smart registration
- The user requests registration.
- Application Manager requests validity from user
(guest or student/staff)
+ If user is a guest, system prompts user to sign up
using a valid email
- The system checks the validity of the guest email
- The Application manager approves authorization of
user system access.
Optional
The Student or Staff members UTD identification is
invalid.

Update Info

Application Manager
This use case describes how the app will need users
most updated information for continuous access of the
app.
Optional
11

Trigger:
Normal flow of events:

Subflows:
Alternate/Exception flow:

Use Case Name:

Primary Actor:
Brief Description:
Stakeholders:
Trigger:
Normal flow of events:

Subflows:
Alternate/Exception flow:

User signs in the app and error occurs. Information

has expired. Updates needed.
- The user signs into to the app.
- The user must sign in with a valid UTD ID.
+ If user is a guest, then need to sign up and sign in
+ If user is student/ professor, then just sign in
- The system checks the validity of the ID card/ guest
information.
- The system processes information and returns error.
- User account information has changed in system.
- User contacts Application Manager to update
information.
Optional
The UTD ID is invalid.
The user access account password has expired.
The user has a new primary ID or email that needs to
be updated.

Sign In
User (Student, Professors, Guests)
This use case describes how the system helps users
navigate when signing in.
Optional
User opens app and types account information to access
room destination within JSOM.
- The user logs into the system by providing UTD NET ID or
guest validated email address.
- The system locates the users current location
- The system prompts user to enter their destination
- The user follows the navigation guide
The system doesnt recognize users location
User is unable to sign in with unauthorized account
access.

12

Dynamic Models
Sequence Diagram:
JSOM-Smart Destination -Sequence Diagram

13

Design Documents
User Interface Design

14

Control Mechanisms

User Interface Control:

The input field will only allow JSOM-specific classroom/building numerical data
information to be entered.
- The system control will distinguish the numerical class room numbers entered within only
the JSOM building and floors. For example, there is Old-JSOM, New-JSOM (1.002,
2.002, 11.001, and 12.001). This control will function by detecting an issue if a user does
not appropriately enter in the correct numerical destination in JSOM. The user will then be
redirected to an error message while stating to retry input data. These JSOM-specific
numerical values will help the system identify the users navigation route in a more
efficient manner without errors.

Business Control Rule:

Navigation route must include a minimum of one entered destination location.
- This system control will allow a user to navigate to only one specific location within
JSOM. For example, there will be a system error if more than one route is accidentally
entered or if no destination is entered at all. This control will function by correcting the
error by sending a message to the user stating please provide a sufficient JSOM location.
The minimum of one entered amount will help the system identify the users navigation
route in a more efficient manner without errors.

Flow Logic Control:

If user has entered an invalid username or password, redirect them to error screen
and warning message stating registration and authorization instruction access.

15

- This system control will allow only registered users to access the navigation system. For
example, if a guest of the campus downloads the app and inputs their personal email information,
the system will not allow it. The guest would have to register through UTD and receive a validated
username and password. This control will function by detecting, correcting, and preventing errors
when outsider users may try to access locations in JSOM and receiving a error and warning
message. There is a security issue that our team has focused in this project and this control is
designed to prevent any unauthorized user access.

Method Specification:
Method Name: createSignin
Class Name: Student
Triggers/Events: User opens JSOM Smart Destination App
Arguments Received:
Data type:
userName
VarChar
password

ID: 101

Arguments Returned:
Signin()
authenticatePassword()

Notes:

Data Type:

Notes:

Algorithm Specification:
if UTD Net ID and password provided matches the database
then complete login
else ask user to provide a correct user name or password
else ask user to sign up for a guest account

Class Name: Smart

ID: 102
Method Name:
authenticateRoom
Destination
Triggers/Events: User types in a destination address/room number
Arguments Received:
Data type:
Notes:
Room
Varchar

Arguments Returned:
room()

Data Type:

Notes:

16

Algorithm Specification:
if destination/room number provided doesnt correspond with database
then prompt user to type a correct destination/room number
else show list of rooms in database and prompt user to pick correct destination

Method Name: getRegistered Class Name: Registration

ID: 103
Triggers/Events: User attempts to use the JSOM Smart Destination App for the first time
Arguments Received:
Data type:
Notes:
Username
Varchar

Arguments Returned:
getRegistered(username)

Data Type:

Notes:

Algorithm Specification:
if user is logging into the app for the first time
then attempt to locate users information
if user is already registered
then authenticate user and complete login
else prompt user to register and complete login

Class Name: Smart

ID: 104
Method Name:
launchDirection
Destination
Triggers/Events: System finds users current location and user enters a destination
Arguments Received:
Data type:
Notes:
Destination
Varchar

Arguments Returned:

Data Type:

Notes:
17

launchDirection(destination)

Algorithm Specification:
if destination entered corresponds with database
then launch directions
else prompt user to enter correct destination

18

Testing
Test Cases for JSOM Smart Destination
Test case Follow the map for Software/Hardware testing

Purpose: This system will provide direction to the nearest parking lot, printer,
restroom, campus bookstore, and also guide the user right up to
classroom doors, and not just the building.
Prereq: User sign in to the app and type location room
Test Data: guestSignUpID = {Valid loginID,valid email, invalid email, empty}
loginID = {Valid loginID, invalid loginID, valid email, invalid email,
empty}
password = {valid, invalid, empty}
Steps: Steps to use the JSOM Smart Destination app.
1.
2.
3.
4.
5.
6.
7.
8.
9.

The user gets into to the app.

Guest sign up an userID
The user must sign in with a valid UTD user ID & password
Click login
See the terms of the app
Click agree radio button at page bottom
The user picks location
click submit button
The user follows the map

Notes and Questions:

Test Results:

Date
11/24/2015

Pass/Fail
Fail

11/24/2015

Fail

11/25/2015

Pass

Remarks
The system did not
process and update
guest information
Location not
available on the map
The user get the map

19

Problem: The system showed the class room is invalid number, the building is valid and the
student/ professor is belong to UTD school, when the student requests a navigation map.
Therefore, ensure the map to building is showed, and ensure the class is not exists.
Test case Sign In for application testing

Purpose: This case describes how the system helps users navigate when signing
in.
Prereq: Assumptions that "logged in", "guest login allowed" must be met
before the test case can be run.
Test Data: loginID = {Valid loginID, invalid loginID, valid email, invalid email,
empty}
password = {valid, invalid, empty}
Steps:

Test Input
Visit JSOM Smart Destination
The user logs into the system by
providing UTD NET ID or guest
validated email address.

Expected Output
EXPECTED-Welcome to the app
EXPECTED-Login Successful

The system locates the users

current location

EXPECTED-Location on the list

The system prompts user to

enter their destination

EXPECTED-Specific destination

The user follows the navigation

guide

EXPECTED-Specific direction

Notes and Questions: User opens app and types account information to access room
destination within JSOM.
Test Results:

Date
Time
11/24/2015 10:15 AM

Unit/Line
1

Pass/Fail
Fail

Remarks
The system
doesnt
recognize
users

20

location
11/24/2015 15:00 PM

Pass

11/25/2015 17:30 PM

Fail

Show clear
direction
User is
unable to
sign in with
unauthorized
account
access.

Test case Sign Up for software/hardware testing

Purpose: A guest registers to be UTD user app, so that she/he can use the JSOM
Smart Destination app.
Prereq: "sign up", "guest login allowed", "sign in".
Test Data: SignupID = {name, valid email, invalid email, phone number (optional),
empty}
password = {valid, invalid, empty}
Steps:

1. System displays guest information data entry form

2. Guest enters name, email address, phone number (optional).
3. System validates guest information, displays form for entry of
username and password.
4. Guest enters username and password for subsequent user
login.
5. System validates user name and password, and displays
confirmation form.
6. Guest confirms his/her user information.

Notes and Questions:

Test Results:

Date
11/24/2015
11/25/2015

Pass/Fail
Fail
Fail

11/25/2015

Pass

Remarks
Email not match
System did not
display correct info
after guest entered
System confirm info
21

User types the class room is correct number, the building is valid, and the user is not belong to
UTD when the guest requests a navigation map. Therefore, ensure the system get some general
information from guest, and then ensure the map to building is showed, and the map to class
room is showed. System is return to home page.

22