Facilimanage DynamicsFacilimanage Dynamicsaka “Facilies”aka “Facilies”

CS 499 Final PresentationCS 499 Final Presentation

Curtis McKayCurtis McKay

Manneet SinghManneet Singh

Brad Vonder HaarBrad Vonder Haar

Project Client: Facilities Management of Project Client: Facilities Management of Southern Illinois University Edwardsville.Southern Illinois University Edwardsville.

Primary UsersPrimary Users• Alicia Wainright – Departmental Business Alicia Wainright – Departmental Business

ManagerManager

• Lynda Pavia – Customer Service Lynda Pavia – Customer Service RepresentativeRepresentative

• Kyle Stunkel – Network AdministratorKyle Stunkel – Network Administrator

Organization Organization ResponsibilitiesResponsibilities• Curtis Curtis - plans meeting times and places- plans meeting times and places

- assigns what tasks need to be done- assigns what tasks need to be done - sets forth standards for - sets forth standards for

documentation documentation and programming and programming

• Brad Brad - head contact with client- head contact with client - responsible for appearance of - responsible for appearance of

interfaceinterface - in charge of testing and review- in charge of testing and review

• Manneet - responsible for understanding the Manneet - responsible for understanding the project in terms of data flow project in terms of data flow

- keeps meeting minutes- keeps meeting minutes- web-page designer- web-page designer

Customer’s ProblemCustomer’s Problem

Facilities Management would like to Facilities Management would like to track customer service satisfaction track customer service satisfaction

through the use of surveysthrough the use of surveys

There is currently no standardized There is currently no standardized system in place to create, conduct, system in place to create, conduct, and compare customer satisfaction and compare customer satisfaction

surveyssurveys

Customer’s Problem cont’d.Customer’s Problem cont’d.

The customer would like to be able to The customer would like to be able to compare historic survey responses.compare historic survey responses.

They want to show the strengths and They want to show the strengths and weaknesses of the department by weaknesses of the department by

examining the responses to individual examining the responses to individual questions.questions.

Requirements NeededRequirements Needed• Ability to add users, service departments, Ability to add users, service departments,

questions, attributes, spaces, locales, questions, attributes, spaces, locales, respondent types, and service typesrespondent types, and service types

• Create Surveys using these lists of itemsCreate Surveys using these lists of items• Provide an easy interface to store Provide an easy interface to store

responses when a survey is being responses when a survey is being conducted over the phoneconducted over the phone

• Ability to print a formatted surveyAbility to print a formatted survey• Method to keep track of follow up dates Method to keep track of follow up dates

and the history associated with those and the history associated with those follow upsfollow ups

• Process filter responses and generate Process filter responses and generate formatted reportsformatted reports

The Solution that was The Solution that was developeddeveloped• A Visual Basic 6 interface which A Visual Basic 6 interface which

retrieves and stores data in an Access retrieves and stores data in an Access 2000 database.2000 database.

• Main requirements were easily Main requirements were easily distributed into different VB forms for distributed into different VB forms for modularity and simultaneous progress.modularity and simultaneous progress.

DemonstrationDemonstration

Database relationshipsDatabase relationships

Interface Interface overviewoverview

Main

Conduct

Compare

Follow UpsSystem Utilities

Create

Login

Interface Specifics - Interface Specifics - LoginLogin

Facilimanage Access Database

Settings.ini File

Connect to the

database

Locate database file Authenticate

user

Populate global security variables

and continue to form Main

Close the database

connection

Interface Specifics - Interface Specifics - MainMain

Facilimanage Access Database

Close the database

connection

Check the global security variables against the user’s request and proceed to the

requested form or deny access.

Interface Specifics - Interface Specifics - CreateCreate

Facilimanage Access Database

Get lists of Service Departments, Questions, Attributes, and Spaces

Add new list items

Add survey items to a temporary “Facilimanage

array”

Add a survey table entry

Add all survey items to the surveyquestions

table

return to main

Interface Specifics - Interface Specifics - CompareCompare

Facilimanage Access Database

Get lists of locales, respondent types, service types, service departments, questions, attributes, spaces, and

surveysQuery surveyquestions and answer table with the requested filters

return to main

Put returned recordset into a “Facilimanage

Array”

Format array into a report

Display tables in a data grid view control

Interface Specifics – System Interface Specifics – System UtilitiesUtilities

Facilimanage Access Database

Settings.ini File

Get Database location

Change Database location

Change SMTP Server

informationGet SMTP Server

information

Add Respondent Types, Service

Types, and Locales

Add/Modify Users

return to main

Interface Specifics - Interface Specifics - ConductConduct

Facilimanage Access Database

Get lists of locales, respondent types, and

service typesAdd new list items Query all needed

survey items into a “Facilimanage

array”

Add a response table

entryAdd all responses to the answers table

return to main

Display questions on screen

Save responses into the

“Facilimanage array”

Add a Follow Up

Interface Specifics – Follow Interface Specifics – Follow UpsUps

Facilimanage Access Database

Get list of pending follow ups

Query Followup table about the

currently selected followup

return to main

Display followup history and response

information

Add a followup

Resolve a followup

Generate Follow Up

report

““Facilimanage Array”Facilimanage Array”Array of a self defined Array of a self defined

type:type:arraypiecearraypiece{{

lngUniqueQuestionID As LonglngUniqueQuestionID As LongstrServiceDepartment As StringstrServiceDepartment As StringlngServiceDepartment As LonglngServiceDepartment As LongstrQuestion As StringstrQuestion As StringlngQuestion As LonglngQuestion As LongstrAttribute As StringstrAttribute As StringlngAttribute As LonglngAttribute As LongstrSpace As StringstrSpace As StringlngSpace As LonglngSpace As LongintQuestionType As IntegerintQuestionType As IntegerintType As IntegerintType As Integer

}}

The QuestionType variable identifies what type of question this array element corresponds to: 1-5, y/n, or comment only.

The Type variable identifies what type of array element this particular index represents: ServiceDepartment, Question, Attribute/Space, or Comment.

This value must be calculated since each row in the surveyquestions table could be entirely unique, or row “B” could be the same Question as row “A” but with a different Attribute and/or Space.

TestingTesting

Testing was performed in several Testing was performed in several stages:stages:

•Glass box testingGlass box testing•Black box testingBlack box testing•Client testingClient testing

Deployment and TrainingDeployment and Training

Our client was involved in the Our client was involved in the development process and aided us in development process and aided us in finding bugs. finding bugs.

They received 4 updates of the They received 4 updates of the compiled executable throughout compiled executable throughout development.development.

Training was provided to ensure that Training was provided to ensure that all features were properly understood.all features were properly understood.

The unfinished featureThe unfinished feature

RBase integration was going to be a RBase integration was going to be a convenient feature. It would have allowed the convenient feature. It would have allowed the user to not have to reference the JobCost user to not have to reference the JobCost database from another program. All needed database from another program. All needed information would be displayed in the information would be displayed in the Conduct interface.Conduct interface.

Unfortunately the dependencies on 3Unfortunately the dependencies on 3rdrd party party DLL files being registered using “regsvr32” DLL files being registered using “regsvr32” did not go smoothly.did not go smoothly.

Retrospective Thoughts - Retrospective Thoughts - BadBad• Database was very well designed in the Database was very well designed in the

System Design Document…should have System Design Document…should have done the same with VBdone the same with VB

• Every group member individually developed Every group member individually developed an array of types which were all very similar. an array of types which were all very similar. This could have been developed as a group This could have been developed as a group

• Many reporting features were added late in Many reporting features were added late in the development.the development.

• A senior project mapped drive letter would A senior project mapped drive letter would have been a great time saver! (1 hour 13 have been a great time saver! (1 hour 13 minutes and 41 seconds were spent minutes and 41 seconds were spent browsing to the folder)browsing to the folder)

Retrospective Thoughts - Retrospective Thoughts - GoodGood• Having separate source code files for Having separate source code files for

simultaneous development was very simultaneous development was very beneficial.beneficial.

• The modular design eliminated The modular design eliminated almost all dependencies among the almost all dependencies among the various components.various components.

• Suggestions and criticisms were Suggestions and criticisms were offered and often used with no hard offered and often used with no hard feelings.feelings.

Questions???Questions???