UTD Student Organization Mobile App

Database - UTDSOMAD
Date: 3/3/2015
GROUP 3
Members:
Khiet Nguyen
Chris Nguyen
Anh Nguyen
Thurein Win
Elias Hernadez
Shelby Steaphen
Jordon McCurley

PHASE 1

What is UTDSOMAD?
This app helps students look at all the organizations
on campus, and spread awareness to on-campus life.
It will help students become more involved on
campus, and help find out more about the
organizations UTD offers.

Business Objectives/Goals
The business objectives/goals are to implement the web application in order
to:
Spread awareness of on-campus life
Increase student involvement on campus
Increase university attraction to potential students in the future
Provide a convenient access to all the student organizations including
Greek life.
Prevent students from transferring out of UTD due to lack of campus
social life
Increase accessibility of information within campus organizations
Greater overall experience as a college student

Project Perspective
Projected goals for our group:
Achieve business goals with satisfactory results
Allow users to easily access the database via phone
Ensure users have flexibility based on their own needs
Interface is not too complex where the user gets too
frustrated while implementing the project.

Assumptions
Users are students of the respective university in which the database
may be accessed
All organizations are keeping up the information provided during general
meetings/events
Each organization has an account in which monetary payment maybe
placed for events that require funding or membership fees
Students are interested in partaking in social events in which
organizations provide
The university will provide open access to its catalog of vast student
organizations
Additions/deletion of information pertaining to information in the
database may occur due to uncertainty

Constraints

Technical difficulties
Servers may not be able to uphold the mass amounts of user traffic
Capabilities of the project may not be compatible with certain mobile phones
Some organizations may not have an interest in working with this mobile web
application
Internet access
Limited language capabilities
Critical Constraints - constraints that are more devastating to the project if were
to come to realizations
University does not provide the needed information for the database
Insufficient funding

Scope

Beyond Scope of Project

The project will incorporate current

mobile technology including:
Automated organizations
announcements
Login within the university
system distinct to an individual
student
Instant messaging between
current members of student
organizations

The project does not include:

Special hardware attachments
Outlet to connect to computers
or laptops via USB
Bluetooth capabilities to
transfer files

Project Risk
Project Risk of Pursuing the Project

Scope of the project may be greater than

what was anticipated
Project cost and input may surpass the
benefits it provides
Information upkeep may be too much
Team knowledge may not be up to par
with design
Project may not be able to meet the
deadline
Satisfaction level may be low
Absence of commitment
Team availability may conflict with team
meetings/goals
What if no one is interested in using the
mobile web application?

Project Risk of Not Pursuing the

Project

Missed opportunity to improve campus

life
Decrease in student involvement
Student morale of social life may
affect incoming students
Student transfers out of respective
college
Potential decrease in enrollment due
to lack of awareness
Lack of working with HTML, CSS, PHP,
JavaScript experience
Difficult time adjusting to campus life
without guidance

Phase II

General Technologies

HTML5
CSS3
PHP
JavaScript

Technical Requirements

Laptops/desktops
Smartphones
Database
Devices supporting HTML/Jquery/CSS
Compatible with Apple Store and Google
Play

Non-Technical Requirements
User friendly
data conveyed in simple matter
User interface must be appealing and easy
to navigate

Risks
system overload of information
database may not be updated
Difficulty converting platforms (I.E mobile
to web)

System Architecture
1) iOS/Android mobile app
2) HTML5 web app,CSS,PHP
3) Server side applications
of Red Hat Services

Quality Control and Testing

1) Functional & Performance testing - used to test how
smooth the program or app will run after installed on
individual devices
2) Destructive Testing - this form of testing will be
performed to ensure that the integrity of the app is
good when in use and will not crash

Quality Control and Testing Cont.

3) Usability testing - a handful of volunteers from the UTD student body
will be sat down with the app will rate the app in certain categories
including a category that measures if the students themselves would
download and use the app.

4) Security testing - will be performed to ensure that no sensitive

information can be reached by those with malicious intent. Also security
testing will ensure that the program will not by hi-jacked by others and no
one has access to the app without our consent.

Phase III

Architecture Intro.
Strictly thin clients
Central and database server launch by the
same machine
Local to UTD
Proximity to servers will boost performance
n is maximum number of users

Distributed, Client-server

3-tier architecture
Client Tier:

Responsible for presentation of data, control UI,

receive users input

Application Server Tier:

Sets the boundaries of the

application and heavy coding will be focused in this section

Data Server Tier:

Acts as a repository for data storage. All

information is stored in this tier.

Top-Level Architecture

Data Model

UI (User Interface)
Log In Screen
Require NetID and password
View as Guest for future freshmen or transfer
students

UI (User Interface)
Home Page
Three clickable buttons that will help the user
refine their search
The user can choose Explore Organizations
to see all the organizations that are available
by type, or Organizations By School to view
organizations by the seven different schools at
UTD. They can also choose Upcoming Events
to see all the events that are happening on
campus.

UI (User Interface)
In My Account, registered UTD Students will
be able to view current clubs they are
associated with or have the option to log out.
Guests can not view clubs they are in and
would be prompted to log in when they click
My Account

UI (User Interface)
When the user click on Explore
Organizations in the home page and it will be
redirected to this page.
Under Browse By Organization Type seen in
the home screen, users can choose from the
many types of organizations that interest
them.
Clicking on any of the types will take users to
another screen that would refine their options
based on the type they had chosen.

UI (User Interface)
When the user click on Organizations By
School in the home page and it will be
redirected to this page.
Here the student will get an option to choose
an organization based on their degree.
Choosing the school they currently or
potentially belong to will redirect them to
another page that has results refined for that
specific school.

UI (User Interface)
If the user clicked School of Management from
the previous screen. It will open up to this page
that displays all the degree types offered under
the School of Management at UTD.
The user also has the option to return home or
click my account at any time.

UI (User Interface)
If the user clicked Information Technology from
the previous screen. It will open up this page
that displays the available organizations under
information technology.
The user can click any of those organizations to
view their information.

UI (User Interface)
If the user clicked SAP Users Group (SUG) from
the previous screen. It will open up to this page
which gives a brief description of that
organization.
The user can views any social media links such as
Facebook or twitter that is available.
The user can also click Upcoming Club Events
to view any upcoming events or contact club
representatives or even join the club.

Software Programs
Languages:
PHP
HTML5
CSS3
JavaScript

Organization.php
Attributes:
Club Name
Club ID
Advisor Name
Description
Constructor:
Public Organization (Club Name,
Advisor Name, Description, Club
ID)

Methods:
getClubName()
{returns Club Name}
getAdvisorName()
{returns Advisor Name}
getDescription()
{returns Description}
getClubID()
{returns ClubID}

Student.php
Attributes:
Student Name
NetID
Major
School
Clubs
Constructor:
Public Student (Name, NetID,
Major, School, Clubs)

Methods:

getStudentName()
{returns Student Name}
getNetId()
{returns NetId}
getMajor()
{returns Major}
getSchool()
{returns School}
getClubs()
{returns Clubs}
setClubs()
{sets Clubs in the database}
addClubs()
{getClubs(), adds new club, then
setClubs()}

Advisor.php
Attributes:
Advisor Name
Advisor ID
Club ID
Constructor:
Public Advisor(Name, ClubID,
AdvisorID)

Methods:
getAdvisorName()
{returns Advisor Name}
getAdvisorID()
{returns Advisor Id}
getClubID
{returns ClubID}

Registration.php
Attributes:
Date
Fee
Registration ID
Net ID
Club ID
Constructor:
Public Registration(Date, Fee,
Registration ID, NetID, ClubID)

Methods:

getDate()
{returns Date}
getFee()
{returns Fee}
getRegistrationID()
{returns registration ID}
getNetID()
{returns net Id}
getClubID()
{returns club ID}
setDate()
{sets date in database}
setFee()
{sets fee in database}

Database.php
Constructor:
Public Database()
Methods:
getStudent(NetId)
{returns student object}
getAdvisor(AdvisorID)
{returns advisor object}
getClub(ClubID)
{returns organization object}

getRegistration(RegistrationID)
{returns registration object}
getAllClubs()
{returns array of clubs in
database}
searchClub(club name)
{returns array of clubs with
name}
setClubDescription(ClubID, new
description)
{set new description for
club}

Database
The database software that will be used for this
mobile web app is MS SQL Server
Potentially thousands of students will be using this app
important to scale performance
protection against security threats

Database
A new database will be required to be made - storing
user input and organization data
An existing database will be used to integrate the log
in
o netID taken from UTDs student database
o school updates database every semester - easier to
obtain that data rather create

Database Tables

Student Table
Registration Table
Organization Table
Organization Type Table
Advisor Table

Student Table

Net_ID(PK)
Stu_Name
Stu_Major
Stu_Organizations

Organization Table

Org_ID(PK)
Org_Type(FK)
Org_Contact
Org_Events

Organization Info Table

Org_Type(PK)
Org_Services
Org_Schedule

Questions?