Facilimanage Dynamics aka “Facilies” CS 499 Final Presentation

1. Facilimanage Dynamicsaka “Facilies”CS 499 Final Presentation Curtis McKay Manneet Singh Brad Vonder Haar

2. Primary Users Project Client: Facilities Management of Southern Illinois University Edwardsville. • Alicia Wainright – Departmental Business Manager • Lynda Pavia – Customer Service Representative • Kyle Stunkel – Network Administrator

3. Organization Responsibilities • Curtis - plans meeting times and places - assigns what tasks need to be done - sets forth standards for documentation and programming • Brad - head contact with client - responsible for appearance of interface - in charge of testing and review • Manneet - responsible for understanding the project in terms of data flow - keeps meeting minutes - web-page designer

4. Customer’s Problem Facilities Management would like to track customer service satisfaction through the use of surveys There is currently no standardized system in place to create, conduct, and compare customer satisfaction surveys

5. Customer’s Problem cont’d. The customer would like to be able to compare historic survey responses. They want to show the strengths and weaknesses of the department by examining the responses to individual questions.

6. Requirements Needed • Ability to add users, service departments, questions, attributes, spaces, locales, respondent types, and service types • Create Surveys using these lists of items • Provide an easy interface to store responses when a survey is being conducted over the phone • Ability to print a formatted survey • Method to keep track of follow up dates and the history associated with those follow ups • Process filter responses and generate formatted reports

7. The Solution that was developed • A Visual Basic 6 interface which retrieves and stores data in an Access 2000 database. • Main requirements were easily distributed into different VB forms for modularity and simultaneous progress.

8. Demonstration

9. Database relationships

10. Interface overview Login Conduct Create Main Follow Ups System Utilities Compare

11. Interface Specifics - Login Locate database file Authenticate user Facilimanage Access Database Connect to the database Settings.ini File Populate global security variables and continue to form Main Close the database connection

12. Interface Specifics - Main Facilimanage Access Database Check the global security variables against the user’s request and proceed to the requested form or deny access. Close the database connection

13. Interface Specifics - Create Get lists of Service Departments, Questions, Attributes, and Spaces Facilimanage Access Database 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

14. Interface Specifics - Compare Get lists of locales, respondent types, service types, service departments, questions, attributes, spaces, and surveys Facilimanage Access Database Query surveyquestions and answer table with the requested filters Put returned recordset into a “Facilimanage Array” Format array into a report Display tables in a data grid view control return to main

15. Interface Specifics – System Utilities Get Database location Facilimanage Access Database Change Database location Add Respondent Types, Service Types, and Locales Settings.ini File Change SMTP Server information Get SMTP Server information Add/Modify Users return to main

16. Interface Specifics - Conduct Get lists of locales, respondent types, and service types Facilimanage Access Database Add new list items Query all needed survey items into a “Facilimanage array” Display questions on screen Save responses into the “Facilimanage array” Add a response table entry Add all responses to the answers table Add a Follow Up return to main

17. Interface Specifics – Follow Ups Get list of pending follow ups Add a followup Facilimanage Access Database Resolve a followup Query Followup table about the currently selected followup Display followup history and response information Generate Follow Up report return to main

18. “Facilimanage Array” 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. Array of a self defined type: arraypiece { lngUniqueQuestionID As Long strServiceDepartment As String lngServiceDepartment As Long strQuestion As String lngQuestion As Long strAttribute As String lngAttribute As Long strSpace As String lngSpace As Long intQuestionType As Integer intType As Integer }

19. Testing Testing was performed in several stages: • Glass box testing • Black box testing • Client testing

20. Deployment and Training Our client was involved in the development process and aided us in finding bugs. They received 4 updates of the compiled executable throughout development. Training was provided to ensure that all features were properly understood.

21. The unfinished feature RBase integration was going to be a convenient feature. It would have allowed the user to not have to reference the JobCost database from another program. All needed information would be displayed in the Conduct interface. Unfortunately the dependencies on 3rd party DLL files being registered using “regsvr32” did not go smoothly.

22. Retrospective Thoughts - Bad • Database was very well designed in the System Design Document…should have done the same with VB • Every group member individually developed an array of types which were all very similar. This could have been developed as a group • Many reporting features were added late in the development. • A senior project mapped drive letter would have been a great time saver! (1 hour 13 minutes and 41 seconds were spent browsing to the folder)

23. Retrospective Thoughts - Good • Having separate source code files for simultaneous development was very beneficial. • The modular design eliminated almost all dependencies among the various components. • Suggestions and criticisms were offered and often used with no hard feelings.

24. Questions???