1. Team Members

2. Introduction Group Contract Planning Phase: Systems Request
Project Plan
Work Plan
Gantt Chart
Conclusion

3. Group Contract Objective Group Policy Communication Policy
Group Policy
Communication Policy
Conflict Resolution Policy
Quality of Work
Disciplinary Policy

4. Objective
The objective of Technologic Solutions and its members is to learn and apply its collective knowledge of Systems Analysis and Design with precision in order to demonstrate excellence in the field of Computer Information Systems. Additionally, Technologic Solutions is dedicated to designing a state of the art information system for customers which will provide a competitive advantage through innovation and application of the newest available technologies.

5. Group Policy Language/Respect Cell phones Deliverables Team Decisions
Assignments

6. Communication Policy
Each group member must create a gmail account specifically for Technologic Solutions that will be the group and their first name
Members must have their schedules in their Google Calendars for all other group members to see
All members must have the cell phone number of every member in the group
Members must communicate daily, return calls, and respond to s as soon as possible

7. Conflict Resolution Policy
If a conflict arises, group members will be asked to take a 15 minute break to cool down
The Facilitator has the responsibility of resolving the conflict if it still remains after the break
If the Facilitator is involved in the conflict, the Scribe will serve as the mediator
If both the Scribe and the Facilitator are involved, the Scheduler will take responsibility
A strike will be issued to any team member involved in a conflict that severely violates the contract

8. Quality of Work Policy
All team members are expected to present work of professional quality by the scheduled deadline.
If a deliverable or portion of a deliverable which was assigned to a member is deemed unacceptable by any member of Technologic Solutions due to poor content, a vote will be held by the remainder of the group
Reasons for nonacceptance:
Grammatical Errors
Misspelled Words
Incompletion
Plagiarism
Failure to follow naming convention

9. Disciplinary Policy
Technologic Solutions has a three strike termination policy.
 A member will receive one warning, and then a strike for each recurring incident.
Members are allowed two excused absences from informal meetings. Each excused absence thereafter will result in a strike. 
Members are allowed one excused absence from a formal group meeting. Each excused absence thereafter will result in a strike. 
If a meeting is adjourned abruptly due to member conflict, a vote will be held to determine which of the involved members will receive a strike.  

10. Systems Request Project Name: Business Betterment Program
Version 1.0
Project Name: Business Betterment Program
Client: Louisiana Tech University
Sponsor: College of Business
Project Champion: Darrell Eddy

11. Systems Request Core Business:
The goal of the College of Business is educating and equipping undergraduates and graduates to succeed in entry-level professional positions in the area of their academic major and/or pursue entrepreneurial activities. The masters program of the College of Business addresses the continuing professional development needs of those preparing for mid-level general management positions, intrapreneurial/entrepreneurial leadership positions, and advanced specialist positions. The DBA program equips graduates to become scholars in their disciplines and to think beyond traditional boundaries. 

12. Systems Request Existing System:
Help requests are received by a secretary who then fills out a digital form and prints the forms using a printer located in the IT department. A digital copy is not saved for future reference. These requests are tended to by the IT department on a first in, first out basis.
When audited or in need of an updated list of assets and their locations, IT employees take inventory of assets using a spreadsheet which contains the assets ID, location, model, and type.
Software licenses are tracked using a spreadsheet which contains the software name and serial number. A piece of software called PatchLink generates a list of software currently installed on any given network computer.

13. Systems Request Business Need:
A better method for receiving, distributing, completing, and storing help request tickets.
A centralized location for keeping track of assets.
A centralized location for keeping track of software licenses available, in use, and purchased with receipts/invoices for each.

14. Systems Request Functionality:
A tiered support system for receiving and assigning help tickets will be created for the help desk.
A relational database will be used to record locations of assets within the College of Business which were valued at $1000 or more at the date of purchase.
A relational database will provide a centralized location for keeping track of how many software licenses are available, which assets are using the licenses, and how much each license costs. It will also keep track of all of the invoices/receipts for software purchased.  

15. Systems Request Expected Tangible Value:
Reduced paper and toner consumption
Paper - 30 pages x 244 days x $0.01 a page = $73.20
Toner - 30 pages x 244 days x $0.02 a page = $146.40
Reduction in lost help tickets
2 per wk x 2 hr of lost of work x $30 hr x 45 wks per year =$5400 per year
Reduction in manual ticket submission time
$0.2988/min x 10 min/ticket x 15 tickets/day x 244 days = $10, per year
Total Amount saved per year: $16,555.68

16. Systems Request Expected Intangible Value:
Increased faculty satisfaction
Increased faculty service
Reduction of stress levels for IT staff
Decreased IT staff idle time
Increased turnover for help tickets
12 tickets are completed with the as-is system, but 20 would be able to be handled with the to-be system. 
Elimination of incorrectly assigned tickets
Tickets which were assigned to the IT staff but should have been sent elsewhere would no longer be an issue.

17. Systems Request Special Issues or Constraints:
Project Deadline: May 7, 2009
All changes must be in compliance with the following standards
Louisiana Tech Policies
Policy 5302, Policy 1305, Policy 1304, Policy 1306, Policy 1434, Policy 1435, Policy 2302, Policy 2303, Policy 5201

18. Work Plan Estimated Hours Planning – 140 Analysis – 336 Design – 117
Implementation – 111
Total Hours – 749

19. Gantt Chart

20. Conclusion
With the information presented today we believe that this project is necessary to bring the level of support for the college of business that this university is operating in all of its other functions.
Bring up the things discussed. With the information presented to you today we believe that this project is necessary to bring the support for the college of business to the level that this university is operating in all of its other functions.