Amy OffillChris Hunter

Chris StanfieldClint NesmithJeremy Dazzo

Richie RobinsonVictoria Thomason

Project Name and Sponsor• Project Name: Layer Three

Housing.

• 3 methods of Improved Efficiency• Automated Online Work Order System• Legacy Knowledge Database• Network Inventory System

• Sponsor: Melanie Peel, Director of Housing.

As-is Work Order System• Paper-based ticket system• "Middlemen" - RA or housing front

desk worker• Ways this system is inefficient

• Data discrepancies• Lengthy processing times• Overuse of paper• Solution not recorded• Lost work orders

As-Is Network Inventory System

• Also paper-based system

• Changes in network device locations are NOT

documented  

• Inventory discrepancies 

• Manual search for devices on command of Mr.

Tony Tryon

• The information is never recorded and is lost

every time

As-Is Network Inventory System

As-Is Legacy Knowledge Database

• No existing database

• Word-of-mouth training only 

• A legacy knowledge database would be useful for the new computer tech to use as he or she encounters similar problems as other past computer techs.

To-Be Work Order System• Web-based and accessible from any on-

campus computer.• E-mail notification for new work orders• Assignment to computer tech regionally o The west side of campuso The east side of campuso All of University Park. 

• Students will report work orders directly to the computer techs via Internet.

• This cuts out the middlemen.

To-Be Network Inventory System• A database will be created that

will have the location of all Louisiana Tech Housing computers and related equipment. 

• Accessible to director of maintenance 

• Query capabilities• Five year information turnover

To-Be Legacy Knowledge Database• Articles that are searchable

through the Internet.  • With an input of a generic

question or keyword, a list of answers will be displayed. 

• The user will have access to view, edit, or delete the answer.• Change process will be in place

Logical Database Design

• Context Diagram• Level 0 Diagram

Data Flow Diagrams – Context

Data Flow Diagrams – Level 0

• Use Cases• Functional and Nonfunctional Requirements• Entity Relationship Diagram• Logical Database Design

USE CASES LINK

Work Order SystemFunctional Requirements:

Student must still be able to contact residential advisor or housing front desk worker to report technical issues.

Student work orders can be categorized or eliminated by a Frequently Asked Questions tier before entering the work order submission form.

Newly submitted work orders must be stored in a database queue until handled by the appropriate personnel such as computer techs.

The stored work order queue database must notify the computer techs via e-mail.

The system must consult with the Legacy Knowledge Database for solutions to Frequently Asked Questions and display solution(s) to the student on the Internet webpage.

Work Order SystemNonfunctional RequirementsOperational

Student must be able to access the system through the Student Housing Homepage by a hyperlink called “Residential Student Technical Support Link.”

Student must be able to access system from any work station on campus.

The housing director should have total access to this system.

Orders must be completed on a first in first out priorityPerformance

The system must respond quickly and reliably. The system must be available and accessible at all times.

Work Order SystemSecurity

The system must verify student status by using provided campus wide ID number from student and verifying student status through University records.

The systems must verify housing user login with user providing unique login information.

The system security must be strong enough to prevent unauthorized access to student information

Cultural and PoliticalThe network inventory system must comply with

existing computer standards specified for Louisiana Tech University.

Network Inventory SystemFunctional Requirements:

The maintenance director must be able to access the database through his computer in his office.

Computer Tech must be able to access the database through the Housing computers.

Computer Tech must be able to update the database as the need arises.

The database needs to be able to record every network device Housing is responsible for overseeing and the following attributes: State ID Location Serial number Device type Brand

The network inventory system must have the ability for all fields to be updated as needed.

Network Inventory SystemNonfunctional Requirements:Operational

The network inventory system can be accessed from the maintenance director and computer tech’s computers.

The system should not interfere with the computer systems that will be implemented for the Housing Department.

The maintenance director should have total access to this system. 

PerformanceThe network inventory system should be updated in real

time.The network inventory system will be available during

regular working hours on Monday-Friday and occasionally on the weekends.

Network Inventory SystemSecurity

The maintenance director must enter his ID number to view incoming work orders.

The maintenance director will only view information that is specifically for him.

The network inventory system will constantly monitored by threats such as viruses and worms.

Cultural and PoliticalThe network inventory system must comply

with existing computer standards specified for Louisiana Tech University.

Legacy Knowledge DatabaseFunctional Requirements:

The computer tech must be able to access the Legacy Knowledge Database through his or her computer in the Housing Office.

Computer Tech must be able to add, update, or delete the Legacy Knowledge Database as needed

The computer tech needs to be able to navigate and search the Legacy Knowledge Database with ease.

An FAQ should be provided for all of students to access prior to filling out a work order

The following attributes should be maintained in the database and used to classify articles in the Legacy Knowledge Database: Problem_ID P-type Operating System Solutions Date Posted FAQ {Y/N} Article {Y/N}

Legacy Knowledge DatabaseNonfunctional Requirements:Performance

The system must have enough bandwidth for the student to search the FAQ section

All students must be able to access the system at all times

For any given network traffic load, the system should remain in operation

OperationalThe system must be accessible at all times for the

techs and student to gain any use from the systemThe digitalize knowledge database will be

constructed to facilitate searches by keywords in published knowledge articles

Legacy Knowledge DatabaseSecurity

The system needs to be able to audited by the techs to make sure information is still relevant and also limit the control of access to the system

Cultural and PoliticalNo special cultural or political requirements

User and System RequirementsUser classesStudent ID verification methodComputer tech ID verification method Performance needs

System Requirements – ERD

• In-House Development• Packaged Software• Outsourcing

Design Alternatives Matrix

Design Alternatives Matrix (cont.)

Implementation Plan

Lessons We LearnedHave the following done and ready before Day 1:

Group Project sponsorThe group’s name The group’s logoWhere the group plans to meetWhat the group members’ availability is like

For presentations:Dress professionallyDress coordinating colorsActually know what you are talking about. You WILL be

critiqued. AT LENGTH

Lessons LearnedThe “quizzes” are actually tests, just not worth as muchCHECK YOUR E-MAILHave a laptop, this is essentialRead Peer Review BEFORE creating deliverablesDeliverables need to be completed AT LEAST 24 hours in

advanceALWAYS have deliverables checked by a second set of eyes!Get the corrections to a deliverable fixed and turned back in

soon. THE QUARTER IS REALLY SHORT AND THE SIGNATURES CAN BE DIFFICULT.

Get all the group members’ phone numbersStarting this quarter, the CAB DOES close at 9 pmColor LaserJet prints look amazing

Lessons LearnedFollow the group contractMeetings never end earlyCenit is the perfect place to meetDo not schedule group meetings with Mrs. Blackman on FridaysHaving a social life will not happen during this projectTRY to enjoy or at least tolerate this project, it DOES help make

it easierData integrity Professionals or D.I.P., was based on a meal from

Taco BellTeam members’ will not get along. That’s where the Facilitator

comes inYou will NEVER take more screenshots than you will for this

project

Lessons LearnedMS paint is invaluableGoogle Docs saves A LOT of paperBack up deliverables on a off-line storage, as

Google Docs likes to mess up formattingTurnitin.com is the only website that will destroy a

PDFThe project is both drastic and dramatic.

DramasticYouTube is a life saverCaffeine…ESSENTIAL NEVER take CIS 444 concurrently with this class!

Lessons Learned About Each OtherClint is a ninjaRichie likes to make noises during the

meetingChris Stanfield has a lot of laptopsChris Hunter is a print masterAmy is an awesome editorDon’t call Jeremy 5 minutes before a meeting,

just don’tVictoria likes audio books