Personal Drug Management System Software Product Line

1. Personal Drug Management System Software Product Line Android Team: Dennis Cornwell, Project Manager Matt Bowser, Customer Liaison John Richter, Artifacts Manager Steven Cornfeild, Project Facilitator iPhone Team: Patrick Nelson, Project Manager Mark Sun, Customer Liaison Rob Allie, Artifacts Manager Justin Hammack, Project Facilitator iPad Team: Neil Owen, Project Manager Brian Smith, Customer Liaison Adam Cook, Artifacts Manager Maurice Wong, Project Facilitator

2. Part I: Product Line Overview System provides the ability to manage medication dates and information Motivation includes… Elderly people that generally take multiple drugs at the same time Hard for them to manage all prescriptions at once

3. Overview of Common Features Enter drug information Enter miscellaneous medical notes Synchronize both notes and drug information in cloud View schedule of drug dosing times and follow up exam dates Backup information to an external computer

4. Overview of Variant Features Only iPhone and Android products will be able to include images in notes Due to lack of camera on iPad iOS products will authenticate with an Apple specific authentication system Android product authenticates with it’s own authentication system

5. Domain Research Investigated the Electronic Medical Record domain Needed to apply domain knowledge on topics including PDM ARMOR CCR Format Project Constraints Legal EMRs must not be compromised Products must operate on popular mobile devices Internet access time should be minimized

6. Unauthorized access to patient legal medical information • Dosing information is misrepresented or incomplete • General patient confusion Risk Analysis

7. Risks were mitigated in the following ways: • Authentication deferred to standard device authentication systems • Lock down legal medical records • Not allowed to edit at all • Make text large and legible • Stray from confusing/complicated medical terms Risk Analysis cont.

8. Part II: Model-based View of System

9. Description of Use Case Diagram

10. Description of Use Case Diagram Use case variance: Record Observation camera vs. no camera Authentication Android system vs. iOS Lists of Drugs and their details tablet screen size vs. phone screen size

11. Description of SPL Class Model

12. SPL Group PDM-iPhone Patrick Nelson - Project Manager Justin Hammack - Project Facilitator Mark Sun - Domain Expert/Customer Liaison Robert Allie - Artifacts Manager

13. Description of Application Class Model

14. Behavior Model PDM-iPhone: Sequence Diagram 1

15. Behavior Model PDM-iPhone: Sequence Diagram 2

16. Behavior Model PDM-iPhone: State Diagram 1

17. Behavior Model PDM-iPhone: State Diagram 2

18. Three main views • Drug list • Main screen • Sort, edit and add drugs • Calendar • Timeline • View drug details • Interactions • Shows interactions between drugs • Shows if multiple drugs have the same side effect(s) • View drug details Part III: Demo of PDM-iPhone Prototype

19. SPL Group PDM-Droid Project Manager - Dennis Cornwell Customer Liaison - Matt Bowser Artifacts Manager - John Richter Project Facilitator - Steven Cornfield

20. Description of PDM-Droid Class Model

21. Behavior Model PDM-Droid: Sequence Diagrams (Normal)

22. Behavior Model PDM-Droid: Sequence Diagrams (Exceptional)

23. Behavior Model PDM-Droid: State Diagrams

24. Behavior Model PDM-Droid: State Diagrams

25. High-Level features of User Interface • View List of Drugs • Sort • Edit • Add • Delete • Calendar/Schedule View • View List of Notes • Sort • Edit • Add Picture • Add • Delete Part III: Demo of PDM-Droid Prototype

26. SPL Group PDM-iPad Project Manager – Neil Owen Customer Liaison – Brian Smith Artifacts Manager – Adam Cook Project Facilitator – Maurice Wong

27. Variations • Authentication • Notes/Pictures • Calendar Description of PDM-iPad Class Model

28. SPL – Variant Authenticators • Application – Single Authenticator Description of PDM-iPad Class Model

29. SPL – Variant Notes • Application – No Camera, No Pictures Description of PDM-iPad Class Model

30. SPL – Variant Calendars • Application – Single Calendar Description of PDM-iPad Class Model

31. Add Medication The following will demonstrate adding medication in terms of the sequence diagram. Behavior Model PDM-iPad: Sequence Diagrams (Normal)

32. Add Medication • Adding drug brings a new user interface Behavior Model PDM-iPad: Sequence Diagrams (Normal)

33. Add Medication • Drug names get autopopulated when entering title from the LEXI database Behavior Model PDM-iPad: Sequence Diagrams (Normal)

34. Add Medication • Drug will be saved and synchronized to the ARMOR database Behavior Model PDM-iPad: Sequence Diagrams (Normal)

35. Exception Case • Adding medication when a drug already exists in ARMOR. Behavior Model PDM-iPad: Sequence Diagrams (Exceptional)

36. UI object defines: • AddDrug() • Drug object defines: NeedsUpdate() • ARMORDatabase object defines: • Synchronize() Behavior Model PDM-iPad: State Diagrams

37. User Interface States • State transitions caused by user interaction Behavior Model PDM-iPad: State Diagrams

38. Drugs • Add • Delete • Edit • View • Sort • Notes • Add • Delete • Edit • View Part III: Demo of PDM-iPad Prototype

39. Thank You