The document summarizes a student project to redevelop a patient tracking application. It describes completing the project with three use cases after losing two weeks to a hardware failure. It discusses redesigning pages, installing new software, and completing documentation and testing. Charts show work breakdown and contributions from group members. Feedback from medical staff praised improved functionality for recording compliance on tablets. The group thanked their project owner for guidance that helped their learning experience.

1. Milestone Report 3
Patient Tracking Application
IT 4983
KSU CSE
April 21st, 2017
Stephen Cain, Chris Cheveresan, Jun-Hao Kuah, Victoria McDonald, Aline Moche Chatue

2. Project Summary
The overall goal was to redevelop and improve a web-based software application
as a tool which can be used to measure the effectiveness of health care delivery.
Project Status: Completed. Original five use-cases were replaced by three critical
use-cases after team lost two weeks due to hardware failure. Documentation is
complete. User acceptance testing is 90% complete.
Group Accomplishments -
◦ Installed DBMS (SQL Server 2008)
◦ Managed work assignment to account for server concurrency limitations
◦ Delivered user acceptable application and documentation
◦ Learned to work together as an effective software development team

3. Final Project Deliverables
Add/Change Patient
Add/Change Compliance
Print Turnaround Document
Design documentation
◦ Wireframes
◦ Database documentation
◦ Tutorial/user manual
Application Website
http://capstone.pensmail.net
Class Website
https://victoriacapstone.wixsite.com/capstone2017/

4. Add/Change Patient Before and After
Redesigned both sections to look
more pleasing.

5. Add/Change Patient Before and After
We improved the functionality of
add and change patient by replacing
the date of birth with a datepicker
which does not allow the user to
choose a future date.
Redesigned both sections to look
more pleasing.

6. Add/Change Compliance Before and After
The page now has the Chart
Number displayed instead of it
needing to be typed in

7. Add/Change Compliance Before and After
There is a datepicker
instead of a field for the
date section
The page now has the Chart
Number displayed instead of it
needing to be typed in

8. Add/Change Compliance Before and After
The status section now
has two radio buttons for
compliant and not
compliant instead of a
dropdown
There is a datepicker
instead of a field for the
date section
The page now has the Chart
Number displayed instead of it
needing to be typed in

9. Add/Change Compliance Navigation
Each record has a “Record
Compliance” button next to them
that will take the user to the
Record Compliance Page.

10. Turnaround Document Before and
After
Changed the numbers displayed in the
status column to the words “Compliant”
and “Not Compliant”

11. Turnaround Document Before and
After
Changed the numbers displayed in the
status column to the words “Compliant”
and “Not Compliant”
Added “Telephone” number and Email to
the personal information fields

12. Turnaround Document Before and
After
Changed the numbers displayed in the
status column to the words “Compliant”
and “Not Compliant”
Added “Telephone” number and Email to
the personal information fields
Added a “Print this Page” and “Return to
Menu” buttons that are not obstructive
when printing the page

13. Turnaround Document Before and
After
Changed the numbers displayed in the
status column to the words “Compliant”
and “Not Compliant”
Added “Telephone” number and Email to
the personal information fields
Added a “Print this Page” and “Return to
Menu” buttons that are not obstructive
when printing the page
Removed the grey from the background to
save ink when printing

14. Menu Page Before and After
We chose to remove the Menu for the
Patient List Page which allows the user
to navigate the website while keeping
its functionality.

15. Design Documentation - Wireframes
The wireframe began with discovering how to best accommodate the work flows.
The initial design began with deconstructing the vertical box into small boxes with
appropriate categories.
After recovery we now had to build off of an older version of the site.
The design was to switch the layout from a vertical based design to a horizontal
based design. Along with that to remove any unnecessary fields and to resize
fields.

16. Design Documentation - Database
Documentation
Created database documentation for the web application that explains each
table, table properties, columns, indexes, stored procedures and where each
is used

17. Design Documentation - Tutorial / User
Manual
1. Created a user manual for the web application that highlights each page
and its functionalities.
2. Each page includes a screenshot of the whole page as well as a few
sentences about what its purpose is and navigation to and from the page.

18. Workload Summary
Analysis 20% 67 Hours
Design 6% 19.5 Hours
Development 40% 132.75 Hours
Testing 10% 33.75 Hours
Documentation 24% 83 Hours
Breakdown by work

19. Testing
Navigation
User Experience and
Application Functionality
17 cases of testing completed with more than one more person testing
each aspect of the application.

20. User Feedback
● "We can now record compliance or order a Hedis chart from my tablet
which will save me a lot of time and is great if it gets busy" - Patty
Hoey - Nurse Practitioner All Care
● "I love the dropdown with the correct Hedis measures. I often enter
these at night and it makes it so much easier". Marion Korbey - Lab
Tech / Wife of Practice Owner

21. Major Contributions
Stephen Cain
Installed DBMS after crash, managed the project, coded substantial
pieces of use-cases, coordinated presentations
Cristian Cheveresan
Designed SQL commands, wrote HTML code for header/footer, worked
on design and functionality improvements, worked on documentation
Victoria McDonald
Worked on project class site, helped design the wireframe, assisted
with testing the functionality of the test site.
Jun Hao-Kuah
Designed the wireframe, assisted with design and functionality, and
testing.
Aline Moche Chatue Designed wireframe Prototype and helped with Disaster Recovery.

22. Gantt Chart

23. Project Experience
The overall project experience has been very educational
Applied everyone’s individual skillsets to tasks best suited for them
Overcame a hardware failure
Project highlight was coordinating with the team and coming up with ideas
and solutions to problems along the way.
Rewarding and challenging to work remotely and within a unified platform
which is a common practice in a real-world scenario for developers.

24. Lessons Learned
Communication is key in making sure that tasks are completed
Team learned to adapt to evolving project conditions
Dividing work based on each person’s skillset enabled good team building and was
critical to our success
Hurdles are part of most projects and knowing they can and will happen was
valuable project experience = “Be prepared for a complete crash”

25. Special Thanks
The group would like to thank the project
owner, John Alders, for being a significant help
to the overall outcome of the project. He
provided the perfect balance between
occasionally helping the group in dire situations
and leaving other critical situations to be
handled by the group so we could learn on our
own. We are extremely grateful for having the
opportunity to work with such a helpful and
interactive client!