1. Web-Based Information Management Program
December 9, 2010
Web-Based Information Management Program
Senior Design 2010
Group 10
Final Presentation

2. Group Members Students Advisor Client Nathan Dane Jamin Hitchcock
December 9, 2010
Group Members
Students
Nathan Dane
Jamin Hitchcock
Eric Tweedt
Advisor
Tien Nguyen
Client
Mary Greeley Medical Center
Chris Figland

3. December 9, 2010
Project Overview
Paramedics need to keep track of their certifications, immunizations, and continued education coursework
Certifications are proof of proficiency at a skill set
Many certifications have expiration dates
Client wants a system that will alert paramedics of upcoming certification expiration dates

4. Project Overview About 40 paramedics would use this system
December 9, 2010
Project Overview
About 40 paramedics would use this system
Client also would like to manage schedules using the system
Schedules should include work scheduling and continued education scheduling

5. Concept Overview Users Certs List Docs Exp. Schedule Dates Courses
December 9, 2010
Concept Overview
Users
Certs
List
Docs
Exp.
Schedule
Dates
Courses
Time

6. Concept Overview Administrators All User Functionality Management
December 9, 2010
Concept Overview
Administrators
All User Functionality
Management
Oversee Users
Modify User Attributes
User Accountability
Grant/Decline User Requests

7. Operating Environment
December 9, 2010
Operating Environment
Open source environment
Linux
Apache
MySQL
PHP
Runs in modern web browsers

8. Functional Requirements
December 9, 2010
Functional Requirements
User Information
Login
Contact information
Access level
Certifications
Name, description, serial number
Expiration date

9. Functional Requirements
December 9, 2010
Functional Requirements
Documents
Webpage link
Uploaded certification document
Continuing Education
Classes completed
Time completed

10. Functional Requirements
December 9, 2010
Functional Requirements
Scheduling – Standard Users
View their own schedules
Request time off
Request shifts
Scheduling – Administrators
View all schedules
Modify their schedules
Approve requests from standard users

11. Functional Requirements
December 9, 2010
Functional Requirements
Admin Abilities
View/modify their personal information
View all user certifications/docs
View all continuing education information
Upload/manage documents
Add/remove users
Manage schedules

12. Functional Requirements
December 9, 2010
Functional Requirements
User Abilities
View/modify their person information
View/modify their own certifications
View/modify their own continuing education information
Request scheduling
Time off
Specific shifts

13. Non-Functional Requirements
December 9, 2010
Non-Functional Requirements
Interface
Easy to use
Visually appealing
Intuitive
Compatibility
Works on Mary Greeley servers
Easy to install

14. Non-Functional Requirements
December 9, 2010
Non-Functional Requirements
Availability
Can be accessed from browsers anywhere
Notifications by
Security
Secure login
Separation between administrators and basic users

15. Market/Literature Survey
December 9, 2010
Market/Literature Survey
Based loosely on a program called NinthBrain™
NinthBrain™ is designed for large organizations
Very expensive for smaller application at Mary Greeley Medical Center
Our program uses free, open source frameworks
Low to zero cost for MGMC

16. December 9, 2010
Deliverables
A web project meeting the functional and non-functional requirements given by Mary Greeley
A tutorial on installing and using the system on their servers

17. Risks Security Fines HIPAA Other hospital information
December 9, 2010
Risks
Security
HIPAA
Other hospital information
Mitigation: Build a secure system
Fines
Missed certifications
Missed scheduling
Mitigation: Error checking, redundant notifications

18. System Design: Navigation
December 9, 2010
System Design: Navigation
Homepage with Login
Standard User
Standard User Navigation
Administrator
Administrator Navigation

19. System Design: Navigation
December 9, 2010
System Design: Navigation
Standard User Navigation
Personal Information
Edit Information
Certifications
Add Certifications
Update Certifications
Modify Expirations
Change Properties
Scheduling
View Schedule
Make Requests
Request for Time Off
Request for Specific Work Blocks

20. System Design: Navigation
December 9, 2010
System Design: Navigation
Administrator Navigation
Personal Information
Edit Information
Certifications
Add Certifications
Update Certifications
Modify Expirations
Change Properties
Scheduling
View Schedule
Make Requests
Take Time Off
Pick Up a Specific Work Block
Administration
Continued on Next Slide…

21. System Design: Navigation
December 9, 2010
System Design: Navigation
Administrator Navigation
Personal Information
Certifications
Scheduling
Administration
View Users
Modify User Certification Information
Modify User Certification Documentation
Add/Remove Users
View Requests
Accept/Reject Schedule Requests
View Event Log

22. System Design: Database
December 9, 2010
System Design: Database
Users
Personal Information
Certifications
Continuing Education
Access Level

23. System Design: Database
December 9, 2010
System Design: Database
Personal Information
Name
Phone Number(s)
Address
Address

24. System Design: Database
December 9, 2010
System Design: Database
Access Level
Administrator
Standard User

25. System Design: Database
December 9, 2010
System Design: Database
Continuing Education
Courses
Course Name
Complete or Being Taken
Time Completed

26. System Design: Database
December 9, 2010
System Design: Database
Certifications
Certification Type
Certification Documents
Certification Expiration Date
Certification Acquisition Date
Certification Serial Number

27. System Design: Sequence
December 9, 2010
System Design: Sequence

28. July 30, 2019
Implementation
We used Jamin’s personal server to implement the project
We first built a prototype and then grew the project into a functional release
Project uses the Symfony and Doctrine frameworks to make advanced PHP techniques easy
Symfony also allows for basic unit testing

29. Implementation: Screens
July 30, 2019
Implementation: Screens

30. Implementation: Screens
July 30, 2019
Implementation: Screens

31. Implementation: Schedule
July 30, 2019
Implementation: Schedule
Spring 2010 Schedule

32. Implementation: Schedule
July 30, 2019
Implementation: Schedule
Fall 2010 Schedule

33. Testing Manual testing
December 9, 2010
Testing
Manual testing
Navigated throughout the web application checking each page for proper functionality
Verified proper operation from different locations and different browsers

34. December 9, 2010
Testing
Unit testing
Used built in Symfony unit testing functions to verify correct operation

35. Testing Results All unit tests passed
July 30, 2019
Testing
Results
All unit tests passed
Project was able to be installed on more than one server with proper functionality
Developers were able to use the system correctly

36. Conclusions Development Gathered and created requirements with client
December 9, 2010
Conclusions
Development
Gathered and created requirements with client
Researched current web development practices
Designed system based on requirements

37. Conclusions Implementation
December 9, 2010
Conclusions
Implementation
Project was implemented and meets the requirements
Project was demonstrated to the Mary Greeley contact and made available for him to review
Actual uses of project will be determined by Mary Greeley IT staff and network administrators

38. Conclusions Work Specializations Eric Jamin Nathan
July 30, 2019
Conclusions
Work Specializations
Eric
Style/Aesthetics/Layout
Final Documentation
Jamin
Server Setup/Design
All-Around Application Functionality
Nathan
Web Application Schedule Module

39. July 30, 2019
Conclusions

40. Conclusions Lessons Learned Development Practices New Technologies
December 9, 2010
Conclusions
Lessons Learned
Development Practices
Teamwork strategies
Work delegation
New Technologies
PHP
Symfony
Doctrine
jQuery

41. Conclusions Lessons Learned Room for Improvement Leadership
December 9, 2010
Conclusions
Lessons Learned
Room for Improvement
Leadership
Communication
Scheduling

42. Conclusions For The Future
December 9, 2010
Conclusions
For The Future
Get the project installed at MGMC provided the network administrators cooperate
Re-evaluate requirements after staff has had a chance to use and improve on the project

43. Conclusions Innovations
December 9, 2010
Conclusions
Innovations
Designed the only known project modeling NinthBrain™ to use open source software and frameworks
Web application has useful features of NinthBrain™ while avoiding many unnecessary features that add undesirable cost

44. July 30, 2019
Questions
Demonstration to Follow