1. Amy Offill Chris Hunter Chris Stanfield Clint Nesmith Jeremy Dazzo Richie Robinson Victoria Thomason

2. 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.

3. 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

4. As-Is Work Order System

6. 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

7. As-Is Network Inventory System

8. 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.

9. 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 campus o The east side of campus o All of University Park. Students will report work orders directly to the computer techs via Internet. This cuts out the middlemen.

10. 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

11. 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

13. Logical Database Design

14. Context Diagram Level 0 Diagram

15. Data Flow Diagrams – Context

16. Data Flow Diagrams – Level 0

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

18. USE CASES LINK

19. Work Order System Functional 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.

20. Work Order System Nonfunctional Requirements Operational 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 priority Performance The system must respond quickly and reliably. The system must be available and accessible at all times.

21. Work Order System Security 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 Political The network inventory system must comply with existing computer standards specified for Louisiana Tech University.

22. Network Inventory System Functional 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.

23. Network Inventory System Nonfunctional 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. Performance The 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.

24. Network Inventory System Security 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 Political The network inventory system must comply with existing computer standards specified for Louisiana Tech University.

25. Legacy Knowledge Database Functional 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}

26. Legacy Knowledge Database Nonfunctional 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 Operational The system must be accessible at all times for the techs and student to gain any use from the system The digitalize knowledge database will be constructed to facilitate searches by keywords in published knowledge articles

27. Legacy Knowledge Database Security 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 Political No special cultural or political requirements

28. User and System Requirements User classes Student ID verification method Computer tech ID verification method Performance needs

29. System Requirements – ERD

30. In-House Development Packaged Software Outsourcing

31. Design Alternatives Matrix

32. Design Alternatives Matrix (cont.)

34. Implementation Plan

37. Lessons We Learned Have the following done and ready before Day 1: Group Project sponsor The group’s name The group’s logo Where the group plans to meet What the group members’ availability is like For presentations: Dress professionally Dress coordinating colors Actually know what you are talking about. You WILL be critiqued. AT LENGTH

38. Lessons Learned The “quizzes” are actually tests, just not worth as much CHECK YOUR E-MAIL Have a laptop, this is essential Read Peer Review BEFORE creating deliverables Deliverables need to be completed AT LEAST 24 hours in advance ALWAYS 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 numbers Starting this quarter, the CAB DOES close at 9 pm Color LaserJet prints look amazing

39. Lessons Learned Follow the group contract Meetings never end early Cenit is the perfect place to meet Do not schedule group meetings with Mrs. Blackman on Fridays Having a social life will not happen during this project TRY to enjoy or at least tolerate this project, it DOES help make it easier Data integrity Professionals or D.I.P., was based on a meal from Taco Bell Team members’ will not get along. That’s where the Facilitator comes in You will NEVER take more screenshots than you will for this project

40. Lessons Learned MS paint is invaluable Google Docs saves A LOT of paper Back up deliverables on a off-line storage, as Google Docs likes to mess up formatting Turnitin.com is the only website that will destroy a PDF The project is both drastic and dramatic. Dramastic YouTube is a life saver Caffeine…ESSENTIAL NEVER take CIS 444 concurrently with this class!

41. Lessons Learned About Each Other Clint is a ninja Richie likes to make noises during the meeting Chris Stanfield has a lot of laptops Chris Hunter is a print master Amy is an awesome editor Don’t call Jeremy 5 minutes before a meeting, just don’t Victoria likes audio books