comp 246 group project part-b v.2
TRANSCRIPT
TABLE OF CONTENTSCOMP-246 SOFTWARE ENGINEERING TERM PROJECT PART-B
DIABETES TRACKING SYSTEM
CENTENNIAL COLLEGE, TORONTO, ONTARIO, CANADA 2016
Team Members: Lester Lachcik
Francis LeeRutvik PatelSGurbinder
TABLE OF CONTENTS
Contents
Problem Statement______________________________________________________________________________________1
Problem to solve___________________________________________________________________________________________________1
System Capabilities_______________________________________________________________________________________________2
Business Benefits_________________________________________________________________________________________________2
User Registration________________________________________________________________________________________3
Work Flow Description___________________________________________________________________________________________3
Activity Diagram___________________________________________________________________________________________________4
Use Cases___________________________________________________________________________________________________________5
Use Case Diagram_________________________________________________________________________________________________5
Domain Class Diagram___________________________________________________________________________________________6
Patient Office Report____________________________________________________________________________________7
Work Flow Description___________________________________________________________________________________________7
Activity Diagram___________________________________________________________________________________________________8
Use Cases___________________________________________________________________________________________________________9
Use Case Diagram________________________________________________________________________________________________10
Domain Class Diagram__________________________________________________________________________________________10
Design Class Diagram___________________________________________________________________________________________10
CRC Cards_________________________________________________________________________________________________________10
Patient Appointment___________________________________________________________________________________11
Work Flow Description_________________________________________________________________________________________11
Activity Diagram_________________________________________________________________________________________________11
Use Cases__________________________________________________________________________________________________________12
Use Case Diagram________________________________________________________________________________________________12
Domain Class Diagram__________________________________________________________________________________________13
Design Class Diagram___________________________________________________________________________________________13
CRC Cards_________________________________________________________________________________________________________13
Patient Prescription____________________________________________________________________________________14
Work Flow Description_________________________________________________________________________________________14
TABLE OF CONTENTS
Activity Diagram_________________________________________________________________________________________________15
Use Cases__________________________________________________________________________________________________________16
Use Case Diagram________________________________________________________________________________________________16
Domain Class Diagram__________________________________________________________________________________________17
Design Class Diagram___________________________________________________________________________________________17
CRC Cards_________________________________________________________________________________________________________17
Patient Data Storage___________________________________________________________________________________18
Work Flow Description_________________________________________________________________________________________18
Activity Diagram_________________________________________________________________________________________________19
Use Cases__________________________________________________________________________________________________________20
Use Case Diagrams_______________________________________________________________________________________________21
Detailed Use Case – enter new patient data________________________________________________________________22
sequence diagram – enter new patient data_______________________________________________________________23
state machine diagram – enter new patient data__________________________________________________________23
Domain Class Diagram__________________________________________________________________________________________24
Design Class Diagram___________________________________________________________________________________________25
CRC Cards_________________________________________________________________________________________________________26
Patient Treatment______________________________________________________________________________________27
Work Flow Description_________________________________________________________________________________________27
Activity Diagram_________________________________________________________________________________________________28
Use Cases__________________________________________________________________________________________________________29
Use Case Diagrams_______________________________________________________________________________________________30
Detailed Use Case – order diagnostic test___________________________________________________________________31
sequence diagram – order diagnostic test__________________________________________________________________32
state machine diagram – order diagnostic test____________________________________________________________32
Domain Class Diagram__________________________________________________________________________________________33
Design Class Diagram___________________________________________________________________________________________34
CRC Cards_________________________________________________________________________________________________________35
E-Store Order Fulfillment_____________________________________________________________________________37
Work Flow Description_________________________________________________________________________________________37
TABLE OF CONTENTS
Activity Diagram_________________________________________________________________________________________________38
Use Cases__________________________________________________________________________________________________________39
Use Case Diagram________________________________________________________________________________________________40
Domain Class Diagram__________________________________________________________________________________________41
DESIGN Class Diagram__________________________________________________________________________________________42
CRC CARDS________________________________________________________________________________________________________43
E-Store Order Return__________________________________________________________________________________47
Work Flow Description_________________________________________________________________________________________47
Activity Diagram_________________________________________________________________________________________________48
Use Cases__________________________________________________________________________________________________________49
Use Case Diagrams_______________________________________________________________________________________________49
Domain Class Diagrams_________________________________________________________________________________________49
DESIGN Class Diagram__________________________________________________________________________________________50
crc Cards__________________________________________________________________________________________________________51
E-Store Reporting_______________________________________________________________________________________52
Work Flow Description_________________________________________________________________________________________52
Activity Diagram_________________________________________________________________________________________________52
Use Cases__________________________________________________________________________________________________________53
Use Case Diagrams_______________________________________________________________________________________________54
DOmain Class Diagram__________________________________________________________________________________________54
DESIGN Class Diagram__________________________________________________________________________________________55
crc Cards__________________________________________________________________________________________________________56
Real-Time Monitoring_________________________________________________________________________________57
PATIENT DATA READINGS – REAL TIME MONITORING ACTIVITY DIAGRAM___________________________57
Activity Diagram_________________________________________________________________________________________________58
Use Cases__________________________________________________________________________________________________________59
Use Case Diagrams_______________________________________________________________________________________________60
Detailed Use Case – Set alert Conditions____________________________________________________________________61
Sequence Diagram – SEND MESSAGE TO PATIENT_________________________________________________________62
SEQUENCE DIAGRAM – SEND MESSAGE TO PATIENT______________________________________________________62
TABLE OF CONTENTS
Domain Class Diagram__________________________________________________________________________________________63
DESIGN Class Diagram__________________________________________________________________________________________64
CRC Cards_________________________________________________________________________________________________________65
Overview: Diabetes Tracking System________________________________________________________________67
Integrated Domain Class Diagram____________________________________________________________________________67
Technology Tools for Software Devolopment______________________________________________________68
Project Plan_____________________________________________________________________________________________69
PROJECT PLANPROJECT PLAN
Problem Statement
PROBLEM TO SOLVEDiabetes has become one of the fastest growing diseases in Canada, but new technologies have opened a number of new approaches and opportunities to manage the disease for both patients and doctors. Online information and health tracking services can allow patients to manage their conditions with unprecedented ease and peace of mind. Doctors and patients can take great comfort in knowing that they have a comprehensive and up-to-date source for information as well as complete and easy-to-access records of their medical data for any caregiver they may require. The key challenge would be in creating a fully integrated system whereby all the information can be gathered and easily passed to the relevant users.
Inspiration: www.OneTouch.ca
Page 1
PROJECT PLANPROJECT PLAN
SYSTEM CAPABILITIESThe new system should be capable of:
Maintaining an integrated database of client medical records (ie: collecting, storing and displaying patient data) for medical caregivers:
o Blood sugaro Blood pressureo Body weighto Temperatureo Nutrition intake.o Fitness and exercise habits
Providing a one-stop shop for both doctors and patients:o A web portal for diabetes, fitness and nutrition informationo E-commerce features to promote and sell medical supplies,
products and services (diabetic devices, software, tablets and pc/laptop computers, etc.)
BUSINESS BENEFITSDeployment of the new system is expected provide the following benefits:
Enhanced diagnosis and tracking of patient diabetes through timely and accurate records for medical professionals
Facilitation of communication between doctors and patients Consolidated information resources for patients and doctors Better management of diabetes symptoms on part of patients by
facilitating accurate tracking of their own medical data Improved patient experience through enabling their involvement in
the treatment process Facilitate patient retention and new patient acquisition for doctors Creation of an effective and convenient platform for the marketing,
sales and delivery of diabetes related products and services
Page 2
PROJECT PLANPROJECT PLAN
User Registration
WORK FLOW DESCRIPTION1.1 New users start their registration with our app.
1.2 System requests for the user category to know the type of users.
1.3 Users then identify their category.
1.4 System pops up the application form for specific users.
1.5 Users then fill up the information on the form.
1.6 System updates the user data.
1.7 Users are then asked for confirmation of their application.
1.8 System is then updated with the user information.
1.9 Users are then registered with the system.
1.10 Users can now login.
Page 3
PROJECT PLANPROJECT PLAN
ACTIVITY DIAGRAM
Page 4
PROJECT PLANPROJECT PLAN
USE CASESACTOR USE CASE DESCRIPTION
All Users User opens the app for registration
The user uses our biomedical application to register themselves according to their category.
All Users Users are then prompted to fill up the forms.
The users fill their forms respectively.
All Users Confirmation details. The users are then sent a verification email to verify themselves.
All Users The confirmation acceptance
Users then confirm all our policies and submits it.
USE CASE DIAGRAM
Page 5
PROJECT PLANPROJECT PLAN
DOMAIN CLASS DIAGRAM
DESIGN CLASS DIAGRAM
CRC CARDS
Page 6
PROJECT PLANPROJECT PLAN
Patient Office Report
WORK FLOW DESCRIPTION2.1 System is updated with the patient appointments.
2.2 System sends appointment notifications to the patients.
2.3 Patients visit the doctor.
2.4 Doctor checks the patients.
2.5 Doctor gives prescriptions to the patients.
2.6 Doctor updates the system with patient’s health status.
2.7 Doctor fixes the next appointment for the patient.
2.8 System database is updated automatically.
Page 7
PROJECT PLANPROJECT PLAN
ACTIVITY DIAGRAM
Page 8
PROJECT PLANPROJECT PLAN
USE CASESACTOR USE CASE DESCRIPTION
Patient Access patient account The patient can access his account by logging in on the link provided to log in
Patient Access requested appointment details
The patient views the appointment details as requested
Patient Create an appointment The patient creates a new appointmentPatient Modify an appointment The patient modifies an appointmentPatient Cancel an appointment The patient cancels an appointmentSystem Reviews the appointment
slotThe system checks the appointment slot
Patient Schedule the appointment If the required appointment slot is found, patient schedules the appointment
Patient Take alternative date/time If the required appointment slot is not found, patient chooses alternative time and date
Doctor Canceled appointment Gets notified about the canceled appointment
Doctor Changes in appointments Gets notified about the changes in appointments
Patient Patient logs out Patient is done making necessary changes in the respective appointments
Page 9
PROJECT PLANPROJECT PLAN
USE CASE DIAGRAM
DOMAIN CLASS DIAGRAMPlease refer to User Registration diagram
DESIGN CLASS DIAGRAM
CRC CARDS
Page 10
PROJECT PLANPROJECT PLAN
Patient Appointment
WORK FLOW DESCRIPTION3.1 Patient asks for appointment.
3.2 Receptionist checks physician schedule.
3.3 Offers the date.3.4 Patient confirms the date.3.5 Receptionist does the Booking and the confirmation will go into the
system.
ACTIVITY DIAGRAM
Page 11
PROJECT PLANPROJECT PLAN
USE CASESACTOR USE CASE DESCRIPTION
Patient Requests an appointment The appointment is requested by patientReceptionist Checks schedule The receptionist checks the doctor
schedule in the system.Receptionist Offers a date The receptionist offered a date to the
patient.Patient Confirms date Patient confirmed the appointment in the
system and system processes information.
USE CASE DIAGRAM
Page 12
PROJECT PLANPROJECT PLAN
DOMAIN CLASS DIAGRAM
DESIGN CLASS DIAGRAM
CRC CARDS
Page 13
PROJECT PLANPROJECT PLAN
Patient Prescription
WORK FLOW DESCRIPTION4.1 Patient asks for appointment.
4.2 Receptionist checks physician schedule. 4.3 Offers the date.
4.4 Patient confirms the date.
4.5 Receptionist does the Booking and the confirmation will go into the system.
Page 14
PROJECT PLANPROJECT PLAN
ACTIVITY DIAGRAM
Page 15
PROJECT PLANPROJECT PLAN
USE CASESACTOR USE CASE DESCRIPTION
Patient Visits Doctor Patient visits the doctor for treatmentDoctor Checks the patient Doctor checks the patientDoctor Runs some diagnosis test Doctor runs some diagnostic testDoctor Views the reports Doctor views the reportsDoctor Determines whether
prescription is neededDoctor decides whether a prescription is needed to be given or not
Doctor Writes prescription Doctor provides a prescriptionPatient Receives Prescription The patient receives his prescription and
leaves
Page 16
PROJECT PLANPROJECT PLAN
USE CASE DIAGRAM
Page 17
PROJECT PLANPROJECT PLAN
DOMAIN CLASS DIAGRAM
DESIGN CLASS DIAGRAM
CRC CARDS
Page 18
PROJECT PLANPROJECT PLAN
Patient Data Storage
WORK FLOW DESCRIPTION5.1 Doctor requests view of patient’s data readings
1.1.1 System Displays patient’s data readings
1.1.2 Doctor views patient’s data readings
1.1.3 Doctors exit patient’s data readings view
5.2 Patient requests to view own data
5.3 System displays patient’s data readings
5.4 Patient views own data readings
5.4.1 Patients chooses to enter new data readings
5.4.2 Patient enters new data readings
5.5 System saves patient’s data
5.6 Patient views newly saved data
5.7 Patient decides to correct/update data instead of entering new data
5.7.1 Patient corrects/updates data
5.8 System updates the corrected/updated data
5.9 Patient views the corrected/updated data
5.10 Patient exits – closes or moves to other section of the website
5.11 Patient chooses not to correct/update data
5.12 Patient exits - closes or moves to other section of the website
Page 19
PROJECT PLANPROJECT PLAN
ACTIVITY DIAGRAM
Page 20
PROJECT PLANPROJECT PLAN
USE CASESACTOR USE CASE DESCRIPTIONDoctor View patient’s data
readingsDoctor views patient data and identifies areas of concern needed for diagnosis and treatment. System processes the requests and displays patient’s data on the screen for viewing.
Patient View own data readings Patient views own data readings and decides whether to enter new data or to correct/update existing data. System processes the requests and displays patient’s data readings on the screen.
Patient Enter new data readings
Patient enters new data into data entry form and saves the data. System saves new patient’s data and updates the database with the new data readings entered.
Patient View newly saved data Patient views the newly updated, entered and saved data. System processes the requests and displays patient’s data readings on the screen.
Patient Correct/update data Patient corrects/updates data readings presented in a data entry form. System updates the corrected/updated data readings entered and saved by the patient.
Patient View corrected/updated data
Patient views corrected/updated data readings. System processes the requests and displays patient’s data readings on the screen.
Page 21
PROJECT PLANPROJECT PLAN
USE CASE DIAGRAMS
Page 22
PROJECT PLANPROJECT PLAN
DETAILED USE CASE – ENTER NEW PATIENT DATAUSE CASE NAME: ENTER NEW PATIENT DATAScenario: Enter new patient data – manual monitoringTriggering event: Patient logs into the system and wants to enter new
monitoring data form manually collected readings.Brief description: Online patient logs into website and enters new patient
data acquired from manual monitoring.Actors: PatientRelated use case: Might be invoked by doctor or medical personnel use caseStakeholders: Patient, Doctor, Medical PersonnelPreconditions Login / authentication must be available
Patient manual data collection subsystem must be available
Postcondtions: New manual data entry must be created and savedNew entry must be associated with the customerNew data must be available for viewing , correction/editing
Flow of Activities: Actor System1.Patient wants to enter his manually acquired data readings2.Patient enters his data readings3.Patient views, corrects/edits his data readings
1.1System creates new entry for customer data readings2.1System associate patient with his account and allows patient to enter data3.1System allows patient to view, correct/edit data and saves the corrected data
Exception conditions: 1.1Patient enters wrong login info2.1Patient enters data with typos3.1Patient enters edited data with typos – incorrect type.
Page 23
PROJECT PLANPROJECT PLAN
SEQUENCE DIAGRAM – ENTER NEW PATIENT DATA
STATE MACHINE DIAGRAM – ENTER NEW PATIENT DATA
Page 24
PROJECT PLANPROJECT PLAN
DOMAIN CLASS DIAGRAM
Page 25
PROJECT PLANPROJECT PLAN
DESIGN CLASS DIAGRAM
Page 26
PROJECT PLANPROJECT PLAN
CRC CARDSCrate patient CRC
New patient window screen lastName, dateOfBirt, gender, race, height, weightAccept patient info Patient handler
Patient handler Id, medicalRecordNumber, lastName, dateOfBirt, gender, race, height, weightCreate patient account
Create patientPatient
Patient medicalRecordNumber, lastName, dateOfBirt, gender, race, height, weightCreate patient account
Create patient infoPatient
Crate medical personnel
New medical personnel window screen designation, lastName, firstNameAccept doctor info Patient handler
Patient handler Id, designation, lastName, firstNameCreate doctor accountCreate doctor
Doctor
Doctor designation, lastName, firstNameCreate doctor accountCreate doctor info
Doctor
Create patient readings CRC
New patient readings window screen dateTime, bloodSugarLevel, bloodPressure, pulse, temperature, nutrition, exerciseAccept patient readings info Patient handler
Patient handler Id, dateTime, bloodSugarLevel, bloodPressure, pulse, temperature, nutrition, exercise
Create new patient readingsCreate patient readings info
Doctor
Page 27
PROJECT PLANPROJECT PLAN
Doctor dateTime, bloodSugarLevel, bloodPressure, pulse, temperature, nutrition, exerciseCreate new patient readings
Create patient readingsDoctor
Page 28
PROJECT PLANPROJECT PLAN
Patient Treatment
WORK FLOW DESCRIPTION6.1 Patient visits doctor’s office6.2 Doctor requests to see patient data6.3 System displays patient’s data6.4 Doctor views patient’s data6.5 Doctor performs diagnosis – reviews patient’s data readings
6.5.1 If yes, Doctor requests diagnostic test6.5.2 If no, Doctor performs treatment
6.6 Doctor performs treatment 6.7 Decision Yes– Doctor decides prescription is needed 6.8 Doctor writes prescription6.9 Doctor records diagnosis and treatment6.10 System updates patient’s record
Page 29
PROJECT PLANPROJECT PLAN
ACTIVITY DIAGRAM
Page 30
PROJECT PLANPROJECT PLAN
USE CASESACTOR USE CASE DESCRIPTIONPatient Visit doctor’s office -
appointmentPatient that has appointment with the doctor visits doctor’s office – treatment, prescription.
Doctor View patient’s data readings
Doctor views patient’s data readings and identifies areas of concern needed for diagnosis or treatment. Doctor enters the system and requests patient record and data readings entered by the patient. System processes the requests and displays patient’s data readings on the screen.
Doctor Request diagnostic test
Doctor makes decision to order a diagnostic test(s) based on patient data review. System requests a diagnostic test(s) for the doctor or on doctor’s behalf.
Doctor Performs treatment Doctor performs treatment on the patient or advises patient how to better manage the disease.
Doctor Record diagnosis and treatment
Doctor records diagnosis and treatment. System updates patient’s treatment and diagnostic test records.
Doctor Write prescription Doctor writes prescription for the patient and records it in the database. System processes the requests and records the prescription.
Page 31
PROJECT PLANPROJECT PLAN
USE CASE DIAGRAMS
Page 32
PROJECT PLANPROJECT PLAN
DETAILED USE CASE – ORDER DIAGNOSTIC TESTUSE CASE NAME: ORDER DIAGNOSTIC TESTScenario: Order new diagnostic test for patientTriggering event: Doctor performs diagnosis and wants to diagnostic tests
for patientBrief description: Doctors logs into online system and orders new diagnostic
test(s) for the patient.Actors: DoctorRelated use case: Might be invoked by Medical Personnel preparing info for
the doctor for the upcoming patient visit .Stakeholders: Doctor, Medical PersonnelPreconditions Online website must be available
Login/authorization must be availablePatient treatment subsystem must be available
Postcondtions: Patient must exist or be created and savedOne or more diagnostic test entry must be created and savedDiagnostic test data must be available for review and editing
Flow of Activities: Actor System1.Doctor wants to enter new diagnosis test2.Doctor enters one or more diagnostic test3.Doctor enters patient info for the diagnostic test
1.1System creates new diagnostic test entry2.1System creates new diagnostic test2.2System check availability of diagnostic test3.1System associate patient with the diagnostic test
Exception conditions: 1.1Login/authentication is incorrect2.1Diagnostic test data is incorrect3.1Customer data is incorrect
Page 33
PROJECT PLANPROJECT PLAN
SEQUENCE DIAGRAM – ORDER DIAGNOSTIC TEST
STATE MACHINE DIAGRAM – ORDER DIAGNOSTIC TEST
Page 34
PROJECT PLANPROJECT PLAN
DOMAIN CLASS DIAGRAM
Page 35
PROJECT PLANPROJECT PLAN
DESIGN CLASS DIAGRAM
Page 36
PROJECT PLANPROJECT PLAN
CRC CARDSCrate patient CRC
New patient window screen lastName, dateOfBirt, gender, race, height, weightAccept patient info Patient handler
Patient handler Id, medicalRecordNumber, lastName, dateOfBirt, gender, race, height, weightCreate patient account
Create patientPatient
Patient medicalRecordNumber, lastName, dateOfBirt, gender, race, height, weightCreate patient account
Create patient infoPatient
Crate medical personnel
New medical personnel window screen designation, lastName, firstNameAccept doctor info Patient handler
Patient handler Id, designation, lastName, firstNameCreate doctor accountCreate doctor
Doctor
Doctor designation, lastName, firstNameCreate doctor accountCreate doctor info
Doctor
Create treatment CRC
New treatment window screen type, oralMeds, insulin, lifeStyleAccept treatment info Patient handler
Patient handler Id, type, oralMeds, insulin, lifeStyleCreate new treatmentCreate treatment info
Doctor
Page 37
PROJECT PLANPROJECT PLAN
Doctor type, oralMeds, insulin, lifeStyleCreate doctor accountCreate doctor info
Doctor
Create diagnostic CRC
New diagnostic test window screen type, urineTest, bloodTest, glucoseTest, waterTestAccept diagnostic test info Patient handler
Patient handler Id, type, urineTest, bloodTest, glucoseTest, waterTestCreate new diagnostic test
Create diagnostic test infoDoctor
Doctor type, urineTest, bloodTest, glucoseTest, waterTestCreate new diagnostic test
Create diagnostic testDoctor
Create prescription CRC
New prescription window screen type, medication, nutrition, exerciseAccept prescription info Patient handler
Patient handler Id, type, medication, nutrition, exerciseCreate new prescriptionCreate prescription info
Doctor
Doctor type, medication, nutrition, exerciseCreate doctor accountCreate prescription
Doctor
Page 38
PROJECT PLANPROJECT PLAN
E-Store Order Fulfillment
WORK FLOW DESCRIPTION7.1 Patient selects a product or service from the E-store’s online catalogue
7.2 E-Store catalogue queries the OEM’s inventory
7.3 OEM verifies the product/service’s availability
7.3.1 If there is availability, the item is reserved from the OEM’s inventory
7.3.2 If the item is not available, the E-Store will suggest alternative products/services from its catalogue
7.4 Reserved item is entered into the E-Store’s shopping cart
7.5 Patient checks out and transmits payment information to the Credit/Debit Card Company and shipping information to the OEM
7.6 Credit/Debit Card Company verifies the payment
7.7 The OEM transmits the item shipment to the Fulfillment Company
7.8 Fulfillment Company receives the shipment,
7.9 Fulfillment Company generates shipping record
7.10 Fulfillment Company sends the item shipment
7.11 E-Store stores the shipping record
7.12 E-Store updates the order status
7.13 Patient receives their item
Page 39
PROJECT PLANPROJECT PLAN
ACTIVITY DIAGRAM
Page 40
PROJECT PLANPROJECT PLAN
USE CASESActor Use Case DescriptionPatients, Vendors Create User Account Prospective user registers an account through the
webstore/websitePatients, Vendors, Doctors
User Logon Users logs on to webstore/website account
Patients, Vendors, Doctors
Search for an item User searches webstore catalogue using search function
Patients, Vendors, Doctors
View item comments/ratings User views product reviews on product page
Patients, Vendors, Doctors
View accessory products User views complementary products on the product page
Patients, Vendors, Doctors
View alternative products User views alternative products on the product page
Patients, Doctors Fill shopping cart Add item from search or product page to shopping cart
Patients, Doctors Empty shopping cart Remove item from shopping cartPatients, Doctors Check out shopping cart User fills form to finalize payment and delivery of
selected productPatients, Doctors Fill wish list Add item from search or product page to wish listPatients, Doctors Empty wish list Remove item from wish listPatients, Doctors Transfer wish list to
shopping cartTransfer items from wish list to shopping cart
Patients, Doctors View order status Lookup an outstanding time orderPatients, Doctors Track shipment Look up tracking number of an outstanding item
orderPatients Rate/comment on product Fill short feedback form on a given productVendors Add/Update item
informationRequest to Add/Edit item description
Vendors Add/Update accessory items Request to Add/Edit complementary itemsVendors Add/Update promotion Request to Add/Edit item promotional dealsPatients, Vendors Edit user profile Add/Edit user informationPatients, Vendors User feedback form Fill user feedback form regarding the webstore
Page 41
PROJECT PLANPROJECT PLAN
USE CASE DIAGRAM
Page 42
PROJECT PLANPROJECT PLAN
DOMAIN CLASS DIAGRAM
Page 43
PROJECT PLANPROJECT PLAN
DESIGN CLASS DIAGRAM
Page 44
PROJECT PLANPROJECT PLAN
CRC CARDS<<handler>> OrderHandler Attributes:Responsibilities CollaboratorsInitiates and handles customers’ sales orders and transactions
Customer
<<handler>> CartHandler Attributes:Responsibilities CollaboratorsInitiates and handles customers’ shopping cart activities
Customer
<<handler>> FeedbackHandler Attributes:Responsibilities CollaboratorsInitiates and handles customers’ feedback on store items
Customer
<<entity>> Customer Attributes:- patientID- firstName- middleName- lastName- joinDate- gender- birthdate- custEmail- shipAddress
Responsibilities CollaboratorsStores and manages customer account information
OrderHandlerCartHandlerFeedbackHandlerOrder
Page 45
PROJECT PLANPROJECT PLAN
<<entity>> ProductFeedback Attributes:- quality- price- delivery- comments- feedbackID- feedbackDateTime
Responsibilities CollaboratorsStores and manages product feedback information
CustomerProduct
<<entity>> ShoppingCart Attributes:- startDateTime- noOfItems- valueOfItems- status
Responsibilities CollaboratorsStores and manages customers’ items to be reserved for sale
CustomerCartHandlerCartItem
<<entity>> CartItem Attributes:- itemId- itemQuantity- itemCurrentPrice
Responsibilities CollaboratorsAccounts and inventories the items of a shopping cart; requests backorder as necessary
ShoppingCartProduct
<<entity>> Order Attributes:- orderID- saleDateTime- S&H- taxAmt- totalAmt
Responsibilities CollaboratorsStores and manages customers’ order information
CustomerOrderTransOrderItemDelivery
<<entity>> Delivery Attributes:- shipId- shipDate- shipCost- shipStatus
Responsibilities CollaboratorsStores and manages delivery information of an order
Order
<<handler>> DeliveryHandler Attributes:
Page 46
PROJECT PLANPROJECT PLAN
Responsibilities CollaboratorsInitiates and handles delivery tickets for orders
Delivery
<<entity>> OrderTrans Attributes:- transId- transDateTime- paymentType- paymentAmt
Responsibilities CollaboratorsStores and manages transaction information of an order
Order
<<entity>> Employee Attributes:- employeeID- employeeType
Responsibilities CollaboratorsStores and manages information on employees involved in an order
Order
<<entity>> Product Attributes:- prodID- prodDescription- prodAvailability- prodPrice- prodImage
Responsibilities CollaboratorsStores and manages product item information
orderItemcartItemProductLine
<<entity>> ProductLine Attributes:- brandID- brandDescription- brandName
Responsibilities CollaboratorsStores and manages product line information
ProductOEM
Page 47
PROJECT PLANPROJECT PLAN
<<entity>> OEM Attributes:- mfrID- mfrName- mfrPhone- mfrEmail- mfrWebsite
Responsibilities CollaboratorsStores and manages product manufacturer information
ProductLineCategory
<<entity>> Category Attributes:- categoryID- categoryName- categoryDescription
Responsibilities CollaboratorsStores and manages product category information
OEM
Page 48
PROJECT PLANPROJECT PLAN
E-Store Order Return
WORK FLOW DESCRIPTION8.1 Patient selects a transaction from their purchase history
8.2 E-Store database looks up transaction record
8.2.1 If found, OEM will generate a return ticket
8.2.2 If not, E-Store prompts the Patient that the transaction was not found
8.3 Credit/Debit Card Company verifies refund
8.4 E-Store stores return ticket
8.5 Patient sends return shipment
Page 49
PROJECT PLANPROJECT PLAN
ACTIVITY DIAGRAM
Page 50
PROJECT PLANPROJECT PLAN
USE CASESActor Use Case DescriptionPatients, Doctors User Logon Users logs on to webstore/website accountPatients View purchase history See list of previously completed transactions on own
accountDoctors View Patient purchase
historySee list of previously completed transactions on a given Patient’s account
Patients, Doctors Create item return Create item return ticket via formPatients Contact Patient service Call a live Patient service representative
USE CASE DIAGRAMS
DOMAIN CLASS DIAGRAMSPlease refer to E-Store Order Fulfillment diagram
Page 51
PROJECT PLANPROJECT PLAN
DESIGN CLASS DIAGRAM
Page 52
PROJECT PLANPROJECT PLAN
CRC CARDS<<handler>> ReturnHandler Attributes:Responsibilities CollaboratorsInitiates and handles customers’ order returns
Customer
Page 53
PROJECT PLANPROJECT PLAN
E-Store Reporting
WORK FLOW DESCRIPTION9.1 User request report by specifying report information
9.2 E-Store database generates the requested report
9.3 User receives the generated report
ACTIVITY DIAGRAM
Page 54
PROJECT PLANPROJECT PLAN
USE CASESUsers Use Case DescriptionVendors, Doctors User Logon Users logs on to webstore/website
accountVendors, Doctors View sales data View aggregated sales data on
given items/item categoriesDoctors View user feedback View aggregated feedback from
Patients and vendorsDoctors View/Edit vendor item
informationView/Edit item description
Doctors View/Update vendor accessory items
View/Edit complementary items
Doctors View/Update vendor promotion
View/Edit item promotional deals
Doctors Produce daily transaction summary
System creates aggregated report on the day’s sales
Doctors Sales history report System creates historical sales report on a particular vendor
Vendors, Doctors Sales trends report System creates historical sales report across selected item catagories
Vendors, Doctors Patient usage report System creates report on Patient usage of the webstore over a given period of time
Doctors Shipment history report System creates report on completed/outstanding item shipments
Vendors, Doctors Promotional impact report System creates impact report regarding particular promotional deals hosted on the site
Doctors Vendor activity report System creates report on vendor usage of the webstore over a given period of time
Page 55
PROJECT PLANPROJECT PLAN
USE CASE DIAGRAMS
DOMAIN CLASS DIAGRAMPlease refer to E-Store Order Fulfillment diagram
Page 56
PROJECT PLANPROJECT PLAN
DESIGN CLASS DIAGRAM
Page 57
PROJECT PLANPROJECT PLAN
CRC CARDS<<handler>> ReportHandler Attributes:Responsibilities CollaboratorsInitiates and handles relevant sales/site usage reports for doctors and vendors
Customer
Page 58
PROJECT PLANPROJECT PLAN
Real-Time Monitoring
PATIENT DATA READINGS – REAL TIME MONITORING ACTIVITY DIAGRAM10.1 Patient views / responds to alert
10.1.1 System processes alert10.1 Doctor views / responds to alert
10.1.1 System processes alert10.2 Patient views history
10.2.1 System shows history10.3 Doctor views history
10.3.1 System shows history10.4 Patient makes notes
10.4.1 System saves notes10.5 Doctor makes notes
10.5.1 System saves notes10.6 Doctor sets alert conditions
10.6.1 System sets alert conditions10.7 Patient sends message from doctor
10.7.1 System sends message10.8 Patient views message from doctor
10.8.1 System shows message10.9 Doctor sends text message to patient
10.9.1 System sends text message to patient10.10 Doctor views message from doctor10.11 System shows message10.12 Patient exits - closes or moves to other section of the website10.13 Doctor exits – closes or moves to other section of the website
Page 59
PROJECT PLANPROJECT PLAN
ACTIVITY DIAGRAM
Page 60
PROJECT PLANPROJECT PLAN
USE CASESACTOR USE CASE DESCRIPTIONPatient View respond to alert Patient views / responds to medical alert (high
glucose level readings or low glucose level readings). Patient sends message to doctor. System processes view and response request.
Patient View history Patient requests to view data readings history. Patient views own data readings .System shows patient data readings history. Patients has an option of printing data readings history.
Patient Add notes on history Patient enters notes on some specific data readings of his concern. System processes request and saves the notes.
Patient Send message to doctor Patient requests messaging and sends message to doctor. System processes request and sends the text message to the doctor.
Patient View message from doctor Patient requests to view message from the doctor. System processes the request and shows doctor’s message to the patient.
Doctor View respond to alert Doctor views / responds to medical alert (high glucose level readings or low glucose level readings). Doctor sends message to patient. System processes view and response request.
Doctor View patient history Doctor requests to view data readings history. Doctor views patient’s data readings .System shows patient data readings history. Doctor has an option of printing data readings history.
Doctor Set alert conditions Doctor sets alert conditions for upper glucose levels and lower glucose levels. System processes request and sets the alert conditions.
Doctor Send message to patient Doctor requests messaging and sends message to patient. System processes request and sends the text message to the patient.
Doctor View message form patient
Doctor requests to view message from the patient. System processes the request and shows patient’s message to the doctor.
Page 61
PROJECT PLANPROJECT PLAN
USE CASE DIAGRAMS
Page 62
PROJECT PLANPROJECT PLAN
DETAILED USE CASE – SET ALERT CONDITIONSUSE CASE NAME: SET ALERT CONDITIONSScenario: Set alert conditions for real time glucose monitoringTriggering event: Doctor wants to set alert conditions for glucose
monitoringBrief description: Doctor creates new patient (or for existing patient) and
then sets alert conditions – upper and lower bounds alert conditions for glucose monitoring device.
Actors: DoctorRelated use case: Might be invoked by border line glucose level conditions
affected by meds or insulin therapy – the alert conditions need to re-set and re-adjusted to take into account meds.
Stakeholders: Doctor, patient.Preconditions Login must be available and working
Real time monitoring subsystem with alert setting features must be available.
Postcondtions: Patient must be createdCustomer info must be createdMonitoring device must be available and setPhone must be available and set to receive data and send textAlert conditions must be setMonitoring data must be acquired and stored
Flow of Activities: Actor System1. Doctor creates new
patient account.2. Doctor enters upper
and lower glucose level bounds to be monitored for
1.1 System Creates new patient1.2 System prompts doctor
for patient info2.1System saves new alert conditions for the patient
Exception conditions: 1.1Doctor enters wrong login information2.1The patient name is invalid3.1The alert conditions exceed allowed parameters4.1There is a typo (numbers/letters) conditions are not saved
Page 63
PROJECT PLANPROJECT PLAN
SEQUENCE DIAGRAM – SEND MESSAGE TO PATIENT
Page 64
PROJECT PLANPROJECT PLAN
SEQUENCE DIAGRAM – SEND MESSAGE TO PATIENT
Page 65
PROJECT PLANPROJECT PLAN
DOMAIN CLASS DIAGRAM
Page 66
PROJECT PLANPROJECT PLAN
DESIGN CLASS DIAGRAM
Page 67
PROJECT PLANPROJECT PLAN
CRC CARDSCrate patient CRC
New patient window screen lastName, dateOfBirt, gender, race, height, weightAccept patient info Patient handler
Patient handler Id, medicalRecordNumber, lastName, dateOfBirt, gender, race, height, weight
Create patient accountCreate patient
Patient
Patient medicalRecordNumber, lastName, dateOfBirt, gender, race, height, weight
Create patient accountCreate patient info
Patient
Crate medical personnelNew medical personnel window screen designation, lastName, firstNameAccept doctor info Patient handler
Patient handler Id, designation, lastName, firstNameCreate doctor accountCreate doctor
Doctor
Doctor designation, lastName, firstNameCreate doctor accountCreate doctor info
Doctor
Create alert condition CRCPatient handler alertConditionId, type, startHour,
endHour, upprBound, lowerBound, dateTime, value
Create new alert condition Patient handler
Page 68
PROJECT PLANPROJECT PLAN
Patient handler dateTime, valueCreate alert condition Patient Handler
Create glucose observation CRCPatient alertConditionId, type, startHour,
endHour, upprBound, lowerBound, dateTime, value
Create new glucose observation
Patient
Create monitoring device CRCDoctor serialNumber, manufacturer,
dateOfManufacture, firmwareVersionCreate new monitoring device
Doctor
Create cell phone CRCDoctor Id, phoneNumber, operatingSystem,
osVesion, appVersionCreate cell phone condition Doctor
Create message CRCDoctor dateTime, textCreate message Patient, Doctor
Page 69
PROJECT PLANPROJECT PLAN
Overview: Diabetes Tracking System
INTEGRATED DOMAIN CLASS DIAGRAM
Page 70
PROJECT PLANPROJECT PLAN
Technology Tools for Software Devolopment
Visual Paradigm
MS Project
Google Docs
Google Drive
MS Word
Page 71
PROJECT PLANPROJECT PLAN
Project Plan
Page 72
PROJECT PLANPROJECT PLAN
Page 73