B. System Description
Identification and Analysis of Stakeholders - Users of the system – describe their
abilities/capabilities (technical, environmental and educational), approximately how many of
them will be using the system, what task(s) the system will support and what the
expectations of the users of the system are and the impact that will have on your design.






The abilities and capabilities of the system are improvements and additions in the
class registration process for college students.
Students will have a better grasp on registering only what they need, and in a timely
manner.
Roughly 25,000 students will be using this system, which embodies all current LSU
students.
The system will support tasks of facilitating students with searching and registering
for classes.
The user can have expectations of a quicker and easier registration. They can
expect to see classes that fit them based on their degree audit.
This impacts our design in a interface way. We will design the user interface to easily
direct the student into search options that are the most relevant to the user.
C. Functional and Non-functional Requirements
Functional Requirements
1. Log In Information
1.1 System will be accessed through each student’s PAWS account by their ID.
1.2 Once the system is open, they system will access the student’s degree audit.
2. Synchronization
2.1 The system must check previous courses taken to see if the student met prerequisite
requirements.
2.2 The system must obtain which classes the user must take in order to graduate, including
past
courses the student completed.
2.3 This information will be used to see if the student completed a pre-requisite to take the
course..
3. Setting search criteria
3.1 Once the classes are provided for the system the student will have the availability to begin
a
search query.
3.2 The search query will provide an option of searching by course of that current semester.
3.3 It will additionally give the user an option of finding their particular course by certain days
of the
week or time of the day
Non-Functional Requirements
1. Operational
1.1 This system can run on PC and Mac desktops, handheld devices, and PDA’s, and
work
on any Web browser.
1.2 The system must be able to integrate with the current system.
2. Performance
2.1 System won’t let the number of students registered to a certain course, will not
exceed
the limit of availability.
2.2 During open registration, system will update input information instantly.
2.3 After registration is open for each student it will be available to access, 24 hours per
day.
3. Security
3.1 System includes all safeguards against viruses, worms, etc.
3.2 Protects all of student’s personal info.
4. Cultural & Political
4.1 Only University personnel in the student’s particular college can access the student’s
registration information.
LSU System Service Request
Requested by: Sham-Wow (Team 9)
Date: October 21, 2011
Department: ISDS 3115 (3100)?
Location: LSU
Contact: Lauren Williams, Darriona Lee, Kameron Common, Seth Fontenot
Type of Request: System Enhancement
Urgency: Problems exist, but can be worked around
Problem Statement:
Students are having a harder than necessary time while registering for classes each
semester. 88% of students surveyed said they agree the registration process could be improved and
team Sham-Wow has identified key areas of improvement such as better search options and more up
to date information.
Service Request
In this proposal, we have carefully detailed our improvement idea. We are requesting access
and use of LSU’s IT programming personnel and to the current registration process.
********** TO BE COMPLETED BY LSU SYSTEMS APPROVAL BOARD**********
____ Request approved
Assigned to _________________________________
Start Date __________________________________
_____ Recommend Revision
Revision_________________________________________________________________
_____ Rejection
Reason __________________________________________________________________
Project Name:
Team ShamWow Project Manager:
Registration Made Easy
Seth Fontenot
Customer:
Project Sponsor:
Student Body
Andrea Houston
Project Start/End (projected):
9/1/11 – 12/1/11
TSW Development Staff Estimates (man-months):
Team ShamWow:
0.5
Programmers:
1.5
Supervisors:
1.0
----------------------TOTAL:
3.0
Project Description
Goal
The purpose of the system is provide the student body with an alternative way to schedule more
efficiently, and to create a more effective schedule each semester in order to prevent students from
wasting time and/or money on classes that are not required for their degree.
Objective



Create an easy to use application for students to access
Provide student with accurate, additional information once schedule is created
Be on standby to assist students through multiple means of communication
Phases of Work
The following tasks and deliverables reflect the current understanding of the project:




In Analysis, Team ShamWow was responsible for creating the idea of a better scheduling
system
In Design, the Programmers are responsible for creating the application that the students will
use to schedule their classes with.
In Implementation, coding, training procedures, and support capabilities will be managed by
the Programmers and the Supervisors
In Maintenance, the Supervisors are responsible for monitoring the system while it’s in
usage.