 Information
describing the CIS computer
lab needs to be centralized and easily
accessible.
 CIS students and faculty can’t easily find
out when the lab is available for a class
or lab work
 Lab
must be accessible from on and off
campus
 Ms. Moore should maintain lab schedules
 Faculty should be able to reserve the
room through the system
 Students should be able to see current
streaming video of the lab
 Ms. Moore should be able to access the
lab remotely, and securely
 Dr. Henson, Dr. Kesh, Dr. Sam, and
Ms.
Moore will be the primary users of this
system
 The
network contains
• Servers
 Domain Controller, File Server, Web Server
• Client computers
• Wired access
• Wireless access
• VoIP
• Mobile access
• Remote access via VPN
• Streaming webcam access
• Network printing
 Router
problems
• IP Configuration issues
 Server
problems
• Blue screen of death
 Device
problems
• Camera, VoIP
 For
security, we set up a firewall
 For storage services, we have shared
drives and server back-up
 Identity services are covered by setting
up user accounts via Windows Server
2008
 Windows
XP
 Windows Vista
 Windows
7 Enterprise
 Windows
Server 2008
A
video delivery system has been set up
to provide a real-time view of the lab.
 VoIP
is also set up so calls can be made
between professors/administrators.
 Server-side
tools such as a calendar,
shared drives, and email exchange have
been set up in the collaboration layer
 The
applications developed for this
project address the needs for the CIS
department.
 They can be easily accessed from many
locations, using several different
devices.
 Open-source: free
of cost
 Works well with other technologies used
 Easily accessed from remote locations as
well as mobile platforms
 Lightweight
 Handles all required functionalities
 Easy to code/manipulate
• i.e. Dreamweaver, Notepad, TextPad

Previous Experience
• Faster Development time
 Windows, Apache, MySQL, PHP
 Technologies
work very well together
 Quick and simple to install and setup
 Easy to configure
 Previous experience
• Faster Development Time
The following diagrams will explain our
design decisions.
 Used
as a non-web based application.
 Problems encountered during
development
• ODBC
• Updating Database
 Solution
• Configured ODBC for MySQL
• Added Buttons to take user to PHP site where
user can view, add, delete, update from there.
 Problems
encountered:
• Getting off schedule
• Hardware and OS difficulties
• Needing additional equipment
 Solutions
• Develop scrum tactics, sprint the last two weeks
• Spent extra time overcoming hardware issues
• A few of us made extra trips to Dr. Henson to
gather additional equipment