Information System Development Project

Information System Development
And Implementation
MIS4173: Section 001
Project Manager: Tyler Benton
Systems Analyst: Tyler Overton
Business Analyst: Ryan Gupton
Database Coordinator: Dylan Sibbett

Table of Contents
Project Description.............................................................................................................................5
Executive Summary.........................................................................................................................6
Organization Description.................................................................................................................6
Description of Current Environment.................................................................................................7
Problems with Current System.........................................................................................................7
Appointment Scheduling..............................................................................................................7
System Objectives...........................................................................................................................8
Appointment Scheduling..............................................................................................................8
Constraints.....................................................................................................................................8
Expected Benefits of System............................................................................................................9
Reduce Human Error...................................................................................................................9
Stakeholders...................................................................................................................................9
Context Diagram...........................................................................................................................10
Analysis............................................................................................................................................11
Executive Summary.......................................................................................................................12
Use Case Diagram.........................................................................................................................12
Use Case Specifications.................................................................................................................13
UC.1 .........................................................................................................................................13
UC.2 .........................................................................................................................................14
UC.3 .........................................................................................................................................15
UC.4 .........................................................................................................................................17
UC. 5 ........................................................................................................................................19
Preliminary Non-Functional Requirements.....................................................................................21
Design..............................................................................................................................................23
Context Diagram...........................................................................................................................24
Level 0 Data Flow Diagram ............................................................................................................25
Level 1 Data Flow Diagrams...........................................................................................................26
(1) RequestAppointment.....................................................................................................26
(2) Review/Approve Appointment........................................................................................26
(3) Manage Login ................................................................................................................27
(4) Review Schedule ............................................................................................................27

(5) Perform System Maintenance.........................................................................................28
Entity Relationship Diagram...........................................................................................................28
Navigation Diagram......................................................................................................................29
Form Mockups..............................................................................................................................30
Customer Request From............................................................................................................30
Login Page ...............................................................................................................................32
Owner Page ..............................................................................................................................33
Employee Page..........................................................................................................................34
Sample Reports ............................................................................................................................35
Customer Request Form............................................................................................................35
Login Page ................................................................................................................................36
Hardware and Software Requirements...........................................................................................37
Non-Functional Requirements.......................................................................................................37
Training............................................................................................................................................39
Training Mode..............................................................................................................................40
Justification..................................................................................................................................40
Training: Owner............................................................................................................................40
Accessing Owner Page...............................................................................................................40
Review/Approve Schedule.........................................................................................................46
View All Maintenance Request...................................................................................................47
View Daily Schedule ..................................................................................................................48
Return Home ............................................................................................................................49
Training: Employee.......................................................................................................................50
Accessing Employee Page ..........................................................................................................50
View All Maintenance Request...................................................................................................55
View Daily Schedule ..................................................................................................................57
Return to Login .........................................................................................................................58
Training: Customer.......................................................................................................................59
Customer Maintenance Request ................................................................................................59
User Manual.................................................................................................................................63
Accessing the System.................................................................................................................63
Owner Portion ..........................................................................................................................64

Employee Portion......................................................................................................................65
Customer Portion......................................................................................................................65
Exit the System..........................................................................................................................66
Troubleshoot............................................................................................................................66

Project Description

Executive Summary
The purpose of this document is to create a vision and plan for the new system for
Southern Heating & A/C, Inc. This document will provide:
 Organization description and the current business environment
 Problems with system, new system objectives and expected benefits of the
system
 Stakeholders and hardware/software requirements
The organization description and current business environment describes what Southern
Heating & A/C customers are able to do through the Southern Heating & A/C, Inc. website. The
document will give a thorough evaluation of the problems with the current systemas well as
the objectives of the new system. The document will give a detailed summary of the expected
benefits of the system. After benefits, the hardware and software requirements will be given,
followed by the constraints that the systemmay encounter.
Organization Description
Southern Heating & A/C, Inc. was founded Lumberton, NC by JR. Ward in 1973 with one
goal in mind, “To keep the citizens or Robeson County comfortable”. For twelve years, JR built
his business and his reputation in the community as an honest, hard-working man who put
customer service first above all else. In 1985 JR’s son Ricky was ready to become the leader of
the company. Ricky is current president of Southern Heating & A/C, Inc. Southern Heating &

A/C, Inc. provides the citizens of Robeson County with residential and commercial heating and
air needs. From new instillations to urgent repairs, Southern Heating & A/C will be able to take
good care of its customers.
Description of Current Environment
All communication through Southern Heating & A/C, Inc. and its customers is done
through phone with the exception of general information being done through e-mail. The
current systeminvolves the customer calling the owner’s, Ricky Ward, cell phone number.
There is not much technology being taken advantage of in the way the system currently works.
With the way the current systemworks, there is great chance for human error and lost
appointment forms.
Problems with Current System
With today’s consumers all being so high tech, Southern Heating & A/C, Inc. needs to be
able to better schedule appointments with its customers.
Appointment Scheduling
Southern Heating & A/C, Inc.’s current scheduling systeminvolves the customer calling
the owner about their need. The owner writes down the customer’s information and reports it
to the workers. The way the system works now there is a possibility for information to get lost,
or mixed up to where the customer and the workers are not on the same page. This has been a
problem at Southern Heating A/C, Inc. for many years.

System Objectives
Appointment Scheduling
 Allows customers to schedule appointment from the website
 Customers will be able to submit a form that includes basic information such as:
o Name
o Address
o Phone
o Southern Heating & A/C, Inc. Account Number
o Problem Description
o Urgent? Y/N
 Customers will submit the form
 A confirmation email will be sent to the customer
 Owner will call customer to set up a time and date and form will be delivered to owner
and employees.
Constraints
Even with the pros outweighing the cons for this project, there are still issues that could
arise. The main problem that could occur in this project is communication errors between
our team and the owner of Southern Heating & A/C, Inc. This problem is due to the distance
between our team and the owner. We will be unable to personally visit the company and all
forms of communication will with be through phone or email.

Expected Benefits of System
Reduce Human Error
As previously stated, the appointment scheduling processes at Southern Heating & A/C,
Inc. are all done by hand. Our system will reduce the chance of human error. Almost all aspects
in the current systemare recorded by pen and paper. With the systemin place, incorrect inputs
will be virtually eliminated. Appointment information will be stored in one place and will be
easily accessible for the company. This will reduce confusion among employees when it comes
to any piece of information regarding appointment scheduling. This system will improve on the
already great customer service that Southern Heating & A/C offers.
Stakeholders
The development and implementation of this systemwill affect all aspects of Southern
Heating & A/C, Inc. The affect will be felt most by the employees and the customers. The
customers will have an easier way to schedule an appointment and the employees will be able
to view and prepare for their upcoming appointments. The system will also be beneficial for the
owner in a way that he will not have to stress over lost appointment information. This will also
greatly reduce call volume per day to the company.

Analysis

Executive Summary
Thisanalysiscapturesthe basicflowsforthe SouthernHeating&A/C,Inc. system.The purpose of this
documentisto outline the use casesandto displayall factorsrelatingtothe proposed systemfor
SouthernHeating&A/C,Inc. Thisanalysisof the businessrequirementsincludes:acontextdiagram,use
case diagramand use case specificationsforeachuse case.
Use Case Diagram

Use Case Specifications
UC.1
Use Case Name
RequestAppointment
ID
UC.1
Priority
High
Actor: Customer
Description:The purpose of thisuse case isto allow the customertorequestan
appointment/repair
Trigger:
Type: External □ Temporal
Preconditions
Customermustneedservice and/orrepair
Normal Course
i. User visitsthe SouthernHeating&A/C,Inc.
website.
ii. The user selects“RequestService”onthe
SouthernHeating&A/C,Inc. website
iii. The systemsrequestthe followinginformation:
a. FirstName
b. Last Name
c. Address
d. City
e. State
f. Zip
g. Phone Number
h. E-Mail Address
i. Urgent?Y/N
j. ProblemDescription
iv. The user will clickthe submitbuttononthe form
v. The systemwill sendane-mail confirmationto
userand ownerof SouthernHeating&A/C,Inc.
vi. The user will exitthe system
InformationforSteps
← RequestMaintenance
←CustomerInputInformation
→ ConfirmationE-mail

UC.2
AlternativeCourses
i. User leavesformincomplete
a. The systemwill displayanerrormessage
that requestthe usertoenterthe missing
information
← Incomplete Fields
→Error Message
Postconditions
User waitsto findoutscheduledmaintenancetime
Exceptions
Repairsaren’tneeded
SummaryInputs Source Outputs Destination
CustomerInput
Information
RequestMaintenance
ProblemDescription
Incomplete Fields
Customer ConfirmationE-mail
Error Message
Owner
Use Case Name
Review/Approve Appointment
ID
UC.2
Priority
High
Actor: Owner
Description:The purpose of thisuse case isto allow the ownerto view and approve a
requestedappointment
Trigger:
Preconditions
Customermusthave sentina requestform
Normal Course
i. Ownervisitsthe SouthernHeating&A/C,Inc.
website.
ii. Ownerwill selectLogin
iii. Ownerwill enterusernameandpassword
iv. The systemwill displaythe following information:
a. ViewPendingMaintenance Request
i. The systemwill display all pending
maintenance request
ii. Ownerwill be able toschedule a
time to performrequestedservice
b. Daily Maintenance Schedule
i. Systemwill displaymaintenance
schedule forthe currentday
ii. Ownerwill be able toview services
schedule tobe performedforthat
day
v. Once ownerhas completeddesiredactions,he will
logoutof the system
InformationforSteps
← OwnerLogin Information
→ Maintenance RequestForm
→ DailyMaintenance Schedule
Form

UC.3
vi. Ownerwill call andconfirmtime anddate
vii. The ownerwill exitthe system
→ TelephoneCall
AlternativeCourses
i. Ownerentersincorrectusername/password
a. The systemwill displayanerrormessage
that requestthe ownerre-enterusername
and password
b. Once correct informationisentered,
systemswill continue onnormal course
ii. Ownerhasnot receivedanyrequest
a. Ownerwill exitthe system
← IncorrectLogin Information
→Error Message
Postconditions
Ownerwritesdailyschedule oncompanywhiteboard
Exceptions
No scheduledrepairs
Ownerlogininformation
IncorrectLogin
Information
Owner Telephone Call
DailyMaintenance
Schedule Form
Maintenance
RequestForm
Schedule on
Whiteboard
Error Message
Employees
Customer
Use Case Name
Manage Login
ID
UC.3
Priority
High
Actor: Owner,Employee
Description:The purpose of thisuse case isto allow accessto the system
Trigger:
Preconditions
Users informationmustbe recognizedbythe system
Normal Course
i. User visitsthe SouthernHeating&A/C,Inc.website.
ii. The user selectsLogin
iii. The systemsperformsthe desiredfunctions:
a. Login
i. The systemrequestUsername andPassword
ii. User entersusername and password
iii. User selectsLogin
iv. Systemverifiesuserinformation
v. User ispermittedtoaccessthe system
1. Ownerwill have accessto:
a. View Maintenance Request
b. DailyMaintenance Schedule
2. Employee will have accessto:
a. View DailySchedule
b. Change Username/Password
i. The systemrequestforusername orpasswordand
email address
ii. The user entersthe requestedinformation
InformationforSteps
← Employee Login
Information
→ Requested
Information
←Useremail address
→Linktochange
username/password

iii. The systemverifiesthe usersaccessrights
iv. The systememailsthe useralinkto resettheir
password
v. The user entersnew username andpassword
vi. The systemverifiesthe usersaccessrights
vii. The systemdisplaysspecificinformationforthe
user
←New User
Information
AlternativeCourses
i. InvalidUser
a. User entersa Username thatis notregistered.
b. If error, contact Owner
ii. IncorrectUsername or Password
a. User entersincorrectUsername orPassword.
b. Systempromptsusertoreentertheirinformation.
c. Once correct information hasbeenentered,accesstothe
systemisgranted.
iii. User exceedsmaximumattemptstologin
a. User entersincorrectinformationmore than4 times.
b. Systemlocksuseraccount.
c. Systemsendsinstructionstousersemail for
unlocking/resettingaccountinformation.
d. User attemptstologinto systemafterunlocking/resetting
account information.
e. Accessto systemisgranted.
←InvalidUser
←Incorrect
Username or
Password
→AccesstoSystem
←ExceedsMax Login
Attempts
→AccesstoSystem
Postconditions
If informationisenteredcorrectly,the userhasaccessto the system.
Exceptions
N/A
Employee Login
Information
User Email Address
NewUserInformation
Owner
Employee
Accessto System Owner
Employee

UC.4
InvalidUser
IncorrectUsername or
Password
Exceedsmax login
attempts
Use Case Name
ReviewSchedule
ID
UC.4
Priority
High
Actor: Owner,Employee
Description:The purpose of thisuse case isto allow ownerandemployee toview theirschedule
Trigger:
Preconditions
Users informationmustbe recognizedbythe system
Normal Course
i. User visitsthe SouthernHeating&A/C,Inc.website.
ii. The user selects Login
iii. The user entersusername andpassword
a. The owner will have access to:
i. View Maintenance Request
1. The systemwill displayall current
maintenance request
ii. Daily Maintenance Schedule
1. Systemwill displaymaintenanceschedule
for the currentday
b. The employee will have accessto:
i. Daily Maintenance Schedule
InformationforSteps
← Employee Login
Information
→ Requested
Information

1. Systemwill displaymaintenanceschedule
for the currentday
iv. Once userhas completeddesiredactions,theywill logoutof the
system
v. User will exitthe system
AlternativeCourses
i. InvalidUser
a. User entersa Username thatis notregistered.
b. Accesswill notbe granted
c. If error, contact owner
ii. IncorrectUsername or Password
a. User entersincorrectUsername orPassword.
b. Systempromptsusertoreentertheirinformation.
c. Once correct informationhasbeenentered,accesstothe
systemisgranted.
iii. User exceedsmaximumattemptstologin
a. User entersincorrectinformationmore than4 times.
b. Systemlocksuseraccount.
c. Systemsendsinstructionstousersemail for
unlocking/resettingaccountinformation.
d. User attemptstologinto systemafterunlocking/resetting
account information.
e. Accessto systemisgranted.
←InvalidUser
←Incorrect
Username or
Password
→AccesstoSystem
←ExceedsMax Login
Attempts
→AccesstoSystem
Postconditions
If informationisenteredcorrectly,the userhasaccessto the systemandbe able to view preferred
documents
Exceptions
N/A
Employee Login
Information
Owner
Employee
Accessto System Owner
Employee

UC. 5
InvalidUser
Incorrect
Username/Password
ExceedsMax Login
Attempts
Requested
Information
Use Case Name
PerformSystemMaintenance
ID
UC.5
Priority
High
Actor: Admin,Technical Support(SupportingActor)
Description:The purpose of thisuse case is to performsystemmaintenance
Trigger:
Preconditions
The systemrequiresmaintenance
Normal Course
i. The user wantsto performmaintenance tothe system
ii. The user selects Login
iii. The user logsinas Administrator
iv. The adminnow hasaccess to:
a. Add user to system
i. The admincan inputnew userinformationintothe
systemanddetermine whattype of usertheyare
(i.e.Owner,Customer,Employee,Admin).
b. Remove user from system
InformationforSteps
→Maintenance
←LoginInformation
←AddUser
←Remove User

i. The admincan erase previoususerinformation
fromthe system.Thiswill resultinthe specified
userno longerhavingaccessto the system.
c. Contact Technical Support
v. The adminperformsthe desiredactionfromthe optionsprovided.
vi. The adminsavesall changesto the system.
vii. The adminlogsout of the system.
viii. Once userhas completeddesiredactions,theywill logoutof the
system
ix. User will exitthe system
→Save Changes
AlternativeCourses
i. The user informationwas notfound.
a. Systemwasunable tolocate userinformationprovided
b. Systempromptsusertoreenterinformation
ii. Systemupdate failed
a. Systemwasunable toperformupdate
b. Systemdisplayserrormessage
c. Systempromptsusertorestart update
d. User performsrequested action
e. If update failsagain,contact technical support
←InvalidUser
→AccesstoSystem
←RetryUpdate
→ContactTechnical
Support
→AccesstoSystem
Postconditions
If informationisenteredcorrectly,the userhasaccessto the systemandbe able to view preferred
documents
Exceptions
Maintenance isn’tneeded
LoginInformation
AddUser
Admin Maintenance
Save Changes
Technical Support

Preliminary Non-Functional Requirements
Non-functional Requirements Brief Description
Performance Systemmustbe able to execute the desired
functional requirementsably
HighAvailability Systemneedstobe available all time of the day
Compatibility Systemshall allow integrationwiththe current
userinterface
Usability All usersmustbe able to proficiently operate the
system
Documentation Systemmustbe able to processdocuments
efficientlyandeffectivelyinordertosatisfythe
user’sneeds
Remove User
InvalidUser
RetryUpdate
Accessto System
Contact Technical
Support

Design

Executive Summary
The purpose of thisdocumentisto provide anoverview of the designof the proposedinformation
systemthatour teamis currentlydesigningforSouthernHeating&A/C,Inc. The documentisbroken
downintomultiple sections. Itbeginswiththe contextlevel diagram,showingahighlevel of dataflows.
It thengoesintolevel 0and level 1DFD’sto show the more brokendowndataflows.The document
concludeswithanavigationdiagramandsample formsandreportmock ups.Thiswill be the firstlookat
whatthe userinterface of the systemwill looklike.
Context Diagram

Level 0 Data Flow Diagram
Pending
Appointments
1
Request
Appointment
Customer Appointment Information Repair Request
2
Review/
Approve
Appointment
Confirmed Appointment Pending Request
Owner
Appointment Approvial
Scheduled
Appointments
Scheduled Appointments
3
Manage Login
Owner Login Information
Stakeholder
Login
Information
Login Information
Employee
EmployeeLogin Information
4
Review Schedule
System
Administrator
5
Perform
System
Maintenance
Admin Login Information
Login Information

Level 1 Data Flow Diagrams
(1) Request Appointment
Customer
Customer
1.1
Receive
Customer
Rrequest
Requested
Apointments
Request Information
Customer Information
Requested Appointment
(2) Review/Approve Appointment
2.1
Review
Requested
Appointment
Owner
2.2
Approve
Requested
Appointment
Scheduled
Appointments
Requested
AppointmentsAppointment Information
Appointment Approvial
Requested Appointment Information
Approved appointment Information

(3) Manage Login
3.1
Verify User
Information
Owner
3.2
Update User
Information
Stakeholder
Information
Employee
Stakeholder Login Information
Updated Login Information
Updated Login Information Updated Stakeholder Login Information
Access to System
Access to System
(4) Review Schedule
4.1
Daily
Appointments
4.2
All
Appointments
Owner
Employee
Scheduled
Appointments
Daily Appointment Information
Appointment Information
Request Daily Schedule
Daily Schedule Information
Request All Appointments
Request Daily Schedule
Daily Schedule Information
Request All Appointments

(5) Perform System Maintenance
System
Adminstrator
5.1
Edit Users
5.2
Technical
Support
Stakeholders
InformationAdd User
Remove User
User Information
Updated User Information
Contact Technical Support
Entity Relationship Diagram

Form Mockups
The forms are to be made usingHTML and PHP.
Customer Request From
Thisis the CustomerRequestFormmockup.The userwill entertheirrequestinformationandhit
submit.Once the informationissubmitted,the informationwill be transferred tothe database where
the ownerwe be allowedtoschedule atime tocomplete the request.
SubmitButtonIPO
Input Procedure Output

AccountNumber
FirstName
Last Name
Address
City
State
Zip
ProblemDescription
Urgent?
Systemsendsthe requesttothe
pendingrequestpage forthe
Ownerto view
A pendingrequestonthe owner
page

Login Page
Thisis the loginpage of the system.The ownerandthe employee will have the accesstothisportionof
the system.Once userentersinformation,the systemwill directthemtothe appropriate page.
SubmitButtonIPO
Inputs Procedures Outputs
Username
Password
Systemverifiesthatthe usersis
valid
Systemrecognizesinformation
as Owner,Employee orneither
Systemdirectsuserto
appropriate page

Owner Page
Thisis the ownerportionof the system.Fromhere the ownerwill be able toview pendingrequestas
well all requestandthe dailyschedule.The Ownerwill alsohave the optiontoreturnto login,whichwill
logthemout of the system.

Employee Page
Thisis the employeeportionof the system.Once the employee logsintothe systemthisscreenwill be
shown. The employeewillhave the optiontoview all maintenancerequests,View the dailyschedule,or
returnto login.

Sample Reports
Customer Request Form
Thisis an example of the CustomerRequestform.

Login Page
Thisis an example of the loginpage

Hardware and Software Requirements
SouthernHeating&A/C will needtoobtainacomputerwithWindows7or 8 as the operatingsystem.
The computerwill needtobe equippedwithMicrosoftOfficeProfessional 2010 or 2013. Southern
Heating& A/Cwill needtoobtainaninternetconnectionwithWi-Fi capabilitiesinordertobe able to
use theircomputeronthe network.The computerwill needto have agood firewall inordertoensure
that there will be nolossof customerinformationdue tothe online service requestthatisgoingtobe
implemented.Once the systemstartsbeingdeveloped,there willbe furtherhardware andsoftware
needs.
Non-Functional Requirements
Non-functional Requirements Brief Description
Performance Systemmustbe able to execute the desired
functional requirementsably
HighAvailability Systemneedstobe available all time of the day
Compatibility Systemshall allow integrationwiththe current
userinterface
Usability All usersmustbe able to proficientlyoperate the
system
Documentation Systemmustbe able to processdocuments
efficientlyandeffectivelyinordertosatisfythe
user’sneeds

Training

Executive Summary
Thisportionof the documentisdevotedtotrainingthe usersof the system. Trainingisacrucial part of
the developmentprocessbecauseitteachesthe mainusersthe functionsof the system.Inthis
documentthere will be narrative andscreenshotsthat will walkthe eachuserthroughthe systemona
stepby stepbasis. Thisdocumentwill actas a reference tothe usersasa wayfor themto grow
comfortable operatingthe systemwhenthe teamof developersisnotthere toact as an aid.
Training Mode
The trainingmode usedforthisprojectisa documentbased,stepbysteptraining.
Justification
The reasonfor the choice of documentbased,stepbysteptrainingistogive the usersa hard copyof
the trainingdocumentation. Beingthatthe ownerof the companyisthe onlystakeholderinthe
companywithcomputerexperience,otherthanbasicskills,he requestedthe trainingbe in
documentation.Thiswill give the usersaguide thattheycan access whentheyhave a question about
howto accomplish a taskusingthe system.Inconjunctionwiththe usermanual,thisisthe team’sway
of assuringthatthe stakeholdersare able touse the systemassmoothlyaspossible.
Training: Owner (From Presentation)
Accessing Owner Page
1. Ownerwill clickthe “Login”linkonthe SouthernHeating&A/C,Inc. website.(Linkwill be added
to website once the projecthasbeencompleted)
2. The followingscreenwill appear:

3. Ownerwill selectthe “Owner”option

5. User entersusername andpassword andclicksthe submitbutton

Review/Approve Schedule
1. Havingaccessedthe Ownerpage,the Ownerwill select“ViewPendingRequest”
3. From thispoint,the ownerwill be able toview the pendingrequestandcontactthe customers
whenhe isreadyto schedule anappointment.

View All Maintenance Request
1. Once the Ownerpage is accessed,the ownerwill select“View AllMaintenance Request”
3. From thisposition.The ownercanview all of the appointmentsthathave beenscheduled.

View Daily Schedule
1. Once the Ownerpage is accessed,the ownerwill select“View AllMaintenance Request”
3. From thisscreenthe ownerwill be able toview all maintenance requestthatare scheduled
for that day

Return Home
1. Once the Ownerpage is accessed,the ownerwill select“ReturntoLogin”

3. Thiswill successfullylogthe owneroutof the system.Itdirectsthe ownertothe mainlog in
page.
Training: Employee
Accessing Employee Page
1. Employee will clickthe “Login”linkonthe SouthernHeating&A/C,Inc.website.(Linkwill be
addedto website once the projecthasbeencompleted)

3. Employee will selectthe “Employee”option

5. User entersusername andpasswordandclicksthe submitbutton

7. Employee hasnowaccessedthe Employeepage
View All Maintenance Request

1. Once the employee accessesEmployee page,theywillselect“View All Maintenance Request”
3. From thisscreenthe employee will be able toview all of the maintenance request

View Daily Schedule
1. Once the employee accessesEmployee page,theywillselect“View DailySchedule”
3. From thisscreenthe employee isable toview all maintenance requestforthatparticularday

Return to Login
1. Once the employee accessesEmployee page,theywillselect“ReturntoLogin”

3. Thiseffectivelylogsthe useroutof the systemandreturnsthemto the mainloginpage
Training: Customer
Customer Maintenance Request
1. User will visitSouthernHeating&A/C,Inc.website wheretheywill click a“Maintenance
RequestForm”link.(Thislinkwill be availableonce the systemiscompletedandreadytobe
implemented.

3. User will fill ininformation andclickthe submitbutton

5. Thisis the confirmationscreenthatthe customersees.Thistellsthe customerthatthe Southern
Heating& A/C,Inc. hasreceived the requestandthe ownerwill reachouttothemregarding
scheduling.

User Manual
Accessing the System
Owner
1. Visitthe SouthernHeating&A/C,Inc.website
2. Clickon the “Login”link
3. Select“Owner”optiononthe mainloginpage
4. Enter Username andPassword
5. ClickSubmit
6. User isnow loggedintothe system
Employee
2. Clickon the “Login”link
3. Select“Employee”optiononthe mainloginpage
4. Enter Username andPassword
5. ClickSubmit
6. User isnow loggedintothe system
Customer
2. Click“Maintenance RequestForm”
3. User nowhas accessto the Maintenance RequestForm

At thispointthe systemusershave accessto theirportionof the system.
Owner Portion
1. User musthave access to the system. Please see “Accessingthe System”portionof the User
Manual forany trouble accessingthe system
View PendingRequest
1. On the Ownerpage,clickthe link“View PendingRequest”
2. Systemdisplaysdatabase thatshows all pendingrequest
3. From thispoint.Itisimportantfor the ownerto contact the customerto schedule an
appointment.
4. Once appointmentisscheduled,don’tforgettoupdate the accessdatabase
View All MaintenanceRequest
1. On the Ownerpage,clickthe link“View All Maintenance Request”
2. Systemdisplaysdatabase thatshowsall maintenance requestthathave beenscheduled
View Daily Schedule
1. On the Ownerpage,clickthe link“View DailySchedule”
2. Systemdisplaysdatabase thatshowsall maintenance requestthathave beenscheduledforthat
day
Return to Login
1. On the Ownerpage,clickthe link“Returnto Login”
2. Systemdisplaysthe mainloginpage
3. User isnow loggedoutof the system

Employee Portion
View All MaintenanceRequest
1. On the Employee page,clickthe link“View AllMaintenance Request”
2. Systemdisplaysdatabase thatshowsall maintenance requestthathave beenscheduled
View Daily Schedule
1. On the Employee page,clickthe link“View DailySchedule”
2. Systemdisplaysdatabase thatshowsall maintenance requestthathave beenscheduledforthat
day
Return to Login
1. On the Employee page,clickthe link“ReturntoLogin”
2. Systemdisplaysthe mainloginpage
3. User isnow loggedoutof the system
Customer Portion
CustomerMaintenanceRequest
1. Fill outMaintenance RequestFormandclicksubmit
2. Systemwill displayaconfirmationmessage toensure requesthasbeenreceived

Exit the System
1. If user wishestoexitthe system, clickthe red“X”inthe topright portionof the browser
2. Thiswill close the internetbrowserandterminate the system
Troubleshoot
IncorrectUsernameorPassword
1. See Owner
2. Ownerrequestedthatall employeepasswordsbe the same toavoidthisproblem
Page Not Found
1. Try reloadingthe page again
2. If problempersists,have ownercontact technical support
Other
1. For all otherproblem,have ownercontacttechnical support.

Appendix
Project Assessment
TylerBenton
MIS 4173
ProjectAssessment
Thisprojecthas beena valuable learningexperience.IfeellikeIhave learnedmanylessonsthat
I will take withme throughoutmycareer.Fristthingisthat I feel like ProjectManagementissomething
that I am not toofondof. I feel likeforthisprojectIwasfacedwitha teamthat wasnot too interested
inactuallyhelping.Giventhatthisisthe case our projectsufferedanddidnotlive uptothe potential.I
knowI personallygave itmybestshotand didall I can do to. Aside fromthatitwas enjoyableworking
to buildasystemthat will soonbe usedbya familybusiness.Myuncle wasveryopentowhat he
wantedandgave my teama lotof leewaytodowhatwe thoughtwouldwork.I am verythankful forthe
opportunitytodevelopthisprojectforhimandI hope that itwill addvalue tothe business.
I feel like ourprojectisof excellentquality.The amountof time andeffortthatwentintothis
projectismore than I have had to do forany classin mycollege career.Ifeel like the complexityof this
projectwill payhuge dividendsthroughoutmycareer.Ihave thoroughlyenjoyedthisclassandI am
thankful forthe opportunity.

ProjectAssessment
TylerOverton
Overall Ithinkthatour projectfor SouthernHeating&Airwas a success. We gave thema new element
to theircompanythat theydidnothave before. Byaddingthisnew elementof maintenance totheir
company,we not onlyaddedvalue tothe business,buthelpedeasethe processof maintenanceand
repairsfornot onlythe customers,but the ownersas well. Itcreateda mucheasierwayto go online
and requestamaintenance orderfortheirairconditioningandheatinganytime of the day. Before,a
customerwouldhave tocall the company,hope someone wouldanswerthe phone,thenhave to
schedule anappointment. Thisrestrictedthe time thatone couldschedule help.Oursystemisonline,
allowingone tohave accessto the system24/7. My group that I workedwithwasalwayspreparedand
on time tomeetings. We workedveryefficientlywiththe deadlineswe weregiven. We made sure that
everyaspectof our projectmetor exceededourstandards. Overall,Ibelieve thatourprojectwasa
great successandI am proud of the work we

Ryan Gupton - Personal Assessment:
Duringthe projectI servedthe role as the BusinessAnalyst.Ifeel like thiswasn’takeyrole for
our project,soI triedto helpoutinotherareas. I washeavilyinvolvedwiththe technical aspectsof the
project,whichincludedthe technical specificationsanddesigningthe database.The technical areaismy
strongpointand duringthisprocessI triedtomake a consciousefforttoprovide thisstrengthtothe
project.
As a whole the teamoperatedverywelltogetherandcollaboratedonall phasesof the project.
There were certainsituationsandchallengeswe werefacedasa group,but we collectivelycame
togetherandworkedtoeach otherstrengths.While we facedmanyhurdles,Ibelieve we overcame
everychallenge placedinfrontof us. I cannot stressthe importance of communicationwhenworkingin
groups.It’simperative totalkwitheachotherto complete certainobjectives.

MIS 4173 Project Assessment
Dylan Sibbett
As the semester is coming to a close, I realize that the project is almost done. Overall,
this project has taught me a lot this semester. I learned how to redefine use cases, make better
designs for our system, and make up a training manual for how to use our system. I feel like I
worked with the best group in the class. Our team chemistry was very strong. We worked very
well together throughout the semester. Everyone showed up to all the group meetings and
helped complete all tasks that were necessary for the project.

Lessons Learned
The importance of teamworkwaslearnedduringthisproject.There were timeswhenthe projectwas
facedwithmanyhurdlesandwe were able toaccomplishthe tasks.The abilitytoworktogetherisa
goodlessonlearned.Anotherthingthatwe learnedisthe importance of determiningthe scope of a
project.We were notcertainon the scope of the projectand therefore there were manysurprisesthat
happenedalongthe way.

Information System Development Project

Information System Development Project

Recommended

Recommended

More Related Content

Similar to Information System Development Project

Similar to Information System Development Project (20)

Information System Development Project