COMP 246 GROUP PROJECT PART-B v.2

TABLE OF CONTENTSCOMP-246 SOFTWARE ENGINEERING
TERM PROJECT PART-B
DIABETES TRACKING SYSTEM
CENTENNIAL COLLEGE, TORONTO, ONTARIO, CANADA 2016
Team Members:
Lester Lachcik
Francis Lee
Rutvik Patel
SGurbinder

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 OfficeReport____________________________________________________________________________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
CRC Cards ______________________________________________________________________________________________________ 13
Patient Prescription___________________________________________________________________________ 14

TABLE OF CONTENTS
Use Cases _______________________________________________________________________________________________________ 16
Use Case Diagram _____________________________________________________________________________________________ 16
CRC Cards ______________________________________________________________________________________________________ 17
Patient Data Storage __________________________________________________________________________ 18
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
CRC Cards ______________________________________________________________________________________________________ 26
Patient Treatment_____________________________________________________________________________ 27
Use Cases _______________________________________________________________________________________________________ 29
Detailed Use Case – order diagnostic test ________________________________________________________________ 31
sequence diagram – order diagnostic test _______________________________________________________________ 32
state machine diagram – order diagnostic test __________________________________________________________ 32
CRC Cards ______________________________________________________________________________________________________ 35
E-Store Order Fulfillment_____________________________________________________________________ 37

TABLE OF CONTENTS
Use Cases _______________________________________________________________________________________________________ 39
Use Case Diagram _____________________________________________________________________________________________ 40
DESIGN Class Diagram________________________________________________________________________________________ 42
CRC CARDS _____________________________________________________________________________________________________ 43
E-Store Order Return__________________________________________________________________________ 47
Use Cases _______________________________________________________________________________________________________ 49
Domain Class Diagrams ______________________________________________________________________________________ 49
crc Cards________________________________________________________________________________________________________ 51
E-StoreReporting _____________________________________________________________________________ 52
Use Cases _______________________________________________________________________________________________________ 53
DOmain Class Diagram _______________________________________________________________________________________ 54
crc Cards________________________________________________________________________________________________________ 56
Real-Time Monitoring_________________________________________________________________________ 57
PATIENT DATA READINGS – REAL TIME MONITORING ACTIVITY DIAGRAM__________________________ 57
Use Cases _______________________________________________________________________________________________________ 59
Detailed Use Case – Set alert Conditions _________________________________________________________________ 61
Sequence Diagram – SEND MESSAGE TO PATIENT ______________________________________________________ 62
SEQUENCE DIAGRAM – SEND MESSAGE TO PATIENT____________________________________________________ 62

TABLE OF CONTENTS
CRC Cards ______________________________________________________________________________________________________ 65
Overview: Diabetes Tracking System_________________________________________________________ 67
Integrated Domain Class Diagram __________________________________________________________________________ 67
TechnologyTools for Software Devolopment________________________________________________ 68
Project Plan____________________________________________________________________________________ 69

PROBLEM STATEMENT
Page 1
Problem Statement
PROBLEM TO SOLVE
Diabetes has become one of the fastest growing diseases in Canada, but new
technologies haveopened a number of new approachesand opportunitiesto
manage the disease for both patients and doctors. Online information and
health tracking services can allow patients to managetheir conditionswith
unprecedented easeand peaceof mind. Doctorsand patients can take great
comfortin knowingthat they havea comprehensiveand up-to-datesource
for information as wellas completeand easy-to-access recordsof their
medical data for any caregiver they may require. The key challenge would
be in creating a fully integrated system whereby allthe information can be
gathered and easily passed to the relevantusers.
Inspiration: www.OneTouch.ca

PROBLEM STATEMENT
Page 2
SYSTEM CAPABILITIES
The new system should be capable of:
 Maintainingan integrated database of client medicalrecords(ie:
collecting, storing and displayingpatientdata) for medical caregivers:
o Blood sugar
o Blood pressure
o Body weight
o Temperature
o Nutrition intake.
o Fitness and exercise habits
 Providingaone-stop shop for both doctorsand patients:
o A webportal for diabetes, fitness and nutrition information
o E-commercefeatures to promote and sell medical supplies,
productsand services(diabetic devices, software, tablets and
pc/laptop computers, etc.)
BUSINESS BENEFITS
Deploymentof the new system is expected providethefollowingbenefits:
 Enhanced diagnosisand tracking of patient diabetes through timely
and accurate recordsfor medicalprofessionals
 Facilitation of communication between doctors and patients
 Consolidated information resourcesfor patientsand doctors
 Better managementof diabetes symptomson partof patients by
facilitating accurate tracking of their own medical data
 Improved patientexperiencethroughenabling their involvementin
the treatment process
 Facilitate patient retention and new patient acquisition for doctors
 Creation of an effective and convenientplatform for the marketing,
sales and delivery of diabetes related products and services

USER REGISTRATION
Page 3
User Registration
WORKFLOWDESCRIPTION
1.1 New usersstart their registration with our app.
1.2 System requestsfor the user category to know the type of users.
1.3 Users then identify their category.
1.4 System popsup the application form for specific users.
1.5 Users then fill up the information on the form.
1.6 System updatesthe 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 Userscan now login.

USER REGISTRATION
Page 4
ACTIVITY DIAGRAM

USER REGISTRATION
Page 5
USE CASES
ACTOR 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

USER REGISTRATION
Page 6
DOMAIN CLASS DIAGRAM
DESIGN CLASS DIAGRAM
CRC CARDS

PATIENTOFFICE REPORT
Page 7
Patient Office Report
WORKFLOWDESCRIPTION
2.1 System is updated withthe patient appointments.
2.2 System sendsappointmentnotificationsto the patients.
2.3 Patients visit the doctor.
2.4 Doctor checks the patients.
2.5 Doctor givesprescriptionsto the patients.
2.6 Doctor updatesthe system with patient’s health status.
2.7 Doctor fixes the nextappointmentfor the patient.
2.8 System database is updated automatically.

Page 8
ACTIVITY DIAGRAM

Page 9
USE CASES
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 appointment
Patient Modify an appointment The patient modifies an appointment
Patient Cancel an appointment The patient cancels an appointment
System Reviews the appointment
slot
The 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 10
USE CASE DIAGRAM
Please refer to User Registration diagram
CRC CARDS

PATIENTAPPOINTMENT
Page 11
Patient Appointment
WORKFLOWDESCRIPTION
3.1 Patient asks for appointment.
3.2 Receptionistchecks physician schedule.
3.3 Offersthe date.
3.4 Patient confirmsthe date.
3.5 Receptionistdoes the Bookingand the confirmation willgo into the
system.
ACTIVITY DIAGRAM

PATIENTAPPOINTMENT
Page 12
USE CASES
Patient Requests an appointment The appointment is requested by patient
Receptionist 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

PATIENTAPPOINTMENT
Page 13
CRC CARDS

PATIENTPRESCRIPTION
Page 14
Patient Prescription
WORKFLOWDESCRIPTION
4.1 Patient asks for appointment.
4.2 Receptionistchecks physician schedule.
4.3 Offersthe date.
4.4 Patient confirmsthe date.
4.5 Receptionistdoes the Bookingand the confirmation willgo into the
system.

PATIENTPRESCRIPTION
Page 15
ACTIVITY DIAGRAM

PATIENTPRESCRIPTION
Page 16
USE CASES
Patient Visits Doctor Patient visits the doctor for treatment
Doctor Checks the patient Doctor checks the patient
Doctor Runs some diagnosis test Doctor runs some diagnostic test
Doctor Views the reports Doctor views the reports
Doctor Determines whether
prescription is needed
Doctor decides whether a prescription is
needed to be given or not
Doctor Writes prescription Doctor provides a prescription
Patient Receives Prescription The patient receives his prescription and
leaves
USE CASE DIAGRAM

PATIENTPRESCRIPTION
Page 17
CRC CARDS

PATIENTDATASTORAGE
Page 18
Patient Data Storage
WORKFLOWDESCRIPTION
5.1 Doctor requests view of patient’s data readings
1.1.1 System Displayspatient’sdatareadings
1.1.2 Doctor viewspatient’s data readings
1.1.3 Doctorsexit patient’s data readingsview
5.2 Patient requeststo view own data
5.3 System displayspatient’sdata readings
5.4 Patient viewsown data readings
5.4.1 Patientschooses to enter new data readings
5.4.2 Patiententersnew data readings
5.5 System savespatient’s data
5.6 Patient viewsnewly saved data
5.7 Patient decidesto correct/updatedata instead of entering new data
5.7.1 Patientcorrects/updatesdata
5.8 System updatesthe corrected/updated data
5.9 Patient viewsthe corrected/updated data
5.10 Patientexits – closes or movesto other section of the website
5.11 Patientchooses notto correct/updatedata
5.12 Patientexits - closes or movesto other section of the website

PATIENTDATASTORAGE
Page 19
ACTIVITY DIAGRAM

PATIENTDATASTORAGE
Page 20
USE CASES
Doctor View patient’s data
readings
Doctor 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.

PATIENTDATASTORAGE
Page 21
USE CASE DIAGRAMS

PATIENTDATASTORAGE
Page 22
DETAILED USE CASE – ENTER NEW PATIENTDATA
USE CASE NAME: ENTER NEWPATIENT DATA
Scenario: Enter new patient data – manual monitoring
Triggering 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: Patient
Related use case: Might be invoked by doctor or medical personnel use case
Stakeholders: Patient, Doctor, Medical Personnel
Preconditions Login / authentication must be available
Patient manual data collection subsystem must be
available
Postcondtions: New manual data entry must be created and saved
New entry must be associated with the customer
New data must be available for viewing ,
correction/editing
Flow of Activities: Actor System
1.Patient wants to enter his
manually acquired data
readings
2.Patient enters his data
readings
3.Patient views,
corrects/edits his data
readings
1.1System creates new
entry for customer data
readings
2.1System associate patient
with his account and allows
patient to enter data
3.1System allows patient to
view, correct/edit data and
saves the corrected data
Exception conditions: 1.1Patient enters wrong login info
2.1Patient enters data with typos
3.1Patient enters edited data with typos – incorrect type.

PATIENTDATASTORAGE
Page 23
SEQUENCEDIAGRAM – ENTER NEWPATIENTDATA
STATEMACHINEDIAGRAM – ENTER NEW PATIENTDATA

PATIENTDATASTORAGE
Page 24

PATIENTDATASTORAGE
Page 25

PATIENTDATASTORAGE
Page 26
CRC CARDS
Crate 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 patient
Patient
Patient medicalRecordNumber, lastName,
Create patient info
Patient
Crate medical personnel
New medical personnel window screen designation, lastName, firstName
Accept doctor info Patient handler
Patient handler Id, designation, lastName, firstName
Create doctor account
Create doctor
Doctor
Doctor designation, lastName, firstName
Create 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 readings
Create patient readings info
Doctor
Doctor dateTime, bloodSugarLevel, bloodPressure,
pulse, temperature, nutrition, exerciseCreate new patient readings
Create patient readings
Doctor

PATIENTTREATMENT
Page 27
Patient Treatment
WORKFLOWDESCRIPTION
6.1 Patient visits doctor’soffice
6.2 Doctor requests to see patient data
6.3 System displayspatient’sdata
6.4 Doctor viewspatient’s data
6.5 Doctor performsdiagnosis – reviewspatient’s data readings
6.5.1 If yes, Doctor requests diagnostic test
6.5.2 If no, Doctor performstreatment
6.6 Doctor performstreatment
6.7 Decision Yes– Doctor decides prescription is needed
6.8 Doctor writes prescription
6.9 Doctor recordsdiagnosisand treatment
6.10 System updatespatient’srecord

PATIENTTREATMENT
Page 28
ACTIVITY DIAGRAM

PATIENTTREATMENT
Page 29
USE CASES
Patient Visit doctor’s office -
appointment
Patient 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.

PATIENTTREATMENT
Page 30
USE CASE DIAGRAMS

PATIENTTREATMENT
Page 31
DETAILED USE CASE – ORDER DIAGNOSTIC TEST
USE CASE NAME: ORDER DIAGNOSTIC TEST
Scenario: Order new diagnostic test for patient
Triggering event: Doctor performs diagnosis and wants to diagnostic tests
for patient
Brief description: Doctors logs into online system and orders new diagnostic
test(s) for the patient.
Actors: Doctor
Related use case: Might be invoked by Medical Personnel preparing info for
the doctor for the upcoming patient visit .
Stakeholders: Doctor, Medical Personnel
Preconditions Online website must be available
Login/authorization must be available
Patient treatment subsystem must be available
Postcondtions: Patient must exist or be created and saved
One or more diagnostic test entry must be created and
saved
Diagnostic test data must be available for review and
editing
1.Doctor wants to enter new
diagnosis test
2.Doctor enters one or more
diagnostic test
3.Doctor enters patient info
for the diagnostic test
diagnostic test entry
diagnostic test
2.2System check availability
of diagnostic test
3.1System associate patient
with the diagnostic test
Exception conditions: 1.1Login/authentication is incorrect
2.1Diagnostic test data is incorrect
3.1Customer data is incorrect

PATIENTTREATMENT
Page 32
SEQUENCEDIAGRAM – ORDER DIAGNOSTIC TEST
STATEMACHINEDIAGRAM – ORDER DIAGNOSTIC TEST

PATIENTTREATMENT
Page 33

PATIENTTREATMENT
Page 34

PATIENTTREATMENT
Page 35
CRC CARDS
Crate patient CRC
New patient window screen lastName, dateOfBirt, gender, race, height,
weightAccept patient info Patient handler
Create patient
Patient
Create patient info
Patient
Create doctor
Doctor
Create doctor info
Doctor
Create treatment CRC
New treatment window screen type, oralMeds, insulin, lifeStyle
Accept treatment info Patient handler
Patient handler Id, type, oralMeds, insulin, lifeStyle
Create new treatment
Create treatment info
Doctor
Doctor type, oralMeds, insulin, lifeStyle
Create doctor info
Doctor

PATIENTTREATMENT
Page 36
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 info
Doctor
Doctor type, urineTest, bloodTest, glucoseTest,
waterTestCreate new diagnostic test
Create diagnostic test
Doctor
Create prescription CRC
New prescription window screen type, medication, nutrition, exercise
Accept prescription info Patient handler
Patient handler Id, type, medication, nutrition, exercise
Create new prescription
Create prescription info
Doctor
Doctor type, medication, nutrition, exercise
Create prescription
Doctor

E-STORE ORDER FULFILLMENT
Page 37
E-Store Order Fulfillment
WORKFLOWDESCRIPTION
7.1 Patient selects a productor service from the E-store’s onlinecatalogue
7.2 E-Store catalogue queries the OEM’sinventory
7.3 OEM verifiesthe product/service’savailability
7.3.1 If there is availability, the item is reserved from theOEM’s
inventory
7.3.2 If the item is not available, the E-Store will suggest alternative
products/servicesfrom itscatalogue
7.4 Reserved item is entered into the E-Store’s shoppingcart
7.5 Patient checks out and transmitspaymentinformation to the
Credit/DebitCard Company and shippinginformation to the OEM
7.6 Credit/DebitCard Company verifiesthe payment
7.7 The OEM transmitsthe item shipmentto the FulfillmentCompany
7.8 FulfillmentCompanyreceivestheshipment,
7.9 FulfillmentCompanygeneratesshippingrecord
7.10 FulfillmentCompany sendstheitem shipment
7.11 E-Storestores the shippingrecord
7.12 E-Storeupdatesthe order status
7.13 Patientreceivestheir item

Page 38
ACTIVITY DIAGRAM

Page 39
USE CASES
Actor Use Case Description
Patients,Vendors Create User Account Prospective user registersan account through the
webstore/website
Patients,Vendors,
Doctors
User Logon Users logs on to webstore/website account
Patients,Vendors,
Doctors
Search for an item User searcheswebstore catalogue using search
function
Patients,Vendors,
Doctors
View item comments/ratings User viewsproduct reviewson product page
Patients,Vendors,
Doctors
View accessory products User viewscomplementaryproductson the product
page
Patients,Vendors,
Doctors
View alternative products User viewsalternative productson the product page
Patients, Doctors Fill shopping cart Add item from search or product page to shopping
cart
Patients, Doctors Emptyshopping cart Remove item from shoppingcart
Patients, Doctors Check out shopping cart User fills form to finalize payment and deliveryof
selected product
Patients, Doctors Fill wish list Add item from search or product page to wish list
Patients, Doctors Emptywish list Remove item from wish list
Patients, Doctors Transfer wish list to
shoppingcart
Transfer itemsfrom wish list to shopping cart
Patients,Doctors View order status Lookup an outstandingtime order
Patients, Doctors Track shipment Look up tracking number of an outstandingitem
order
Patients Rate/comment on product Fill short feedback form on a given product
Vendors Add/Update item
information
Request toAdd/Edit item description
Vendors Add/Update accessoryitems Request toAdd/Edit complementaryitems
Vendors Add/Update promotion Request toAdd/Edit item promotional deals
Patients,Vendors Edit user profile Add/Edit user information
Patients,Vendors User feedbackform Fill user feedbackform regardingthe webstore

Page 40
USE CASE DIAGRAM

Page 41

Page 42

Page 43
CRC CARDS
<<handler>> OrderHandler Attributes:
Responsibilities Collaborators
Initiates and handles customers’
sales orders and transactions
Customer
<<handler>> CartHandler Attributes:
shopping cart activities
Customer
<<handler>> FeedbackHandler Attributes:
feedback on store items
Customer
<<entity>> Customer Attributes:
- patientID
- firstName
- middleName
- lastName
- joinDate
- gender
- birthdate
- custEmail
- shipAddress
Stores and manages customer
account information
OrderHandler
CartHandler
FeedbackHandler
Order

Page 44
<<entity>> ProductFeedback Attributes:
- quality
- price
- delivery
- comments
- feedbackID
- feedbackDateTime
Stores and manages product
feedback information
Customer
Product
<<entity>> ShoppingCart Attributes:
- startDateTime
- noOfItems
- valueOfItems
- status
Stores and manages customers’
items to be reserved for sale
Customer
CartHandler
CartItem
<<entity>> CartItem Attributes:
- itemId
- itemQuantity
- itemCurrentPrice
Accounts and inventories the
items of a shopping cart; requests
backorder as necessary
ShoppingCart
Product
<<entity>> Order Attributes:
- orderID
- saleDateTime
- S&H
- taxAmt
- totalAmt
Stores and manages customers’
order information
Customer
OrderTrans
OrderItem
Delivery
<<entity>> Delivery Attributes:
- shipId
- shipDate
- shipCost
- shipStatus
Stores and manages delivery
information of an order
Order

Page 45
<<handler>> DeliveryHandler Attributes:
Initiates and handles delivery
tickets for orders
Delivery
<<entity>> OrderTrans Attributes:
- transId
- transDateTime
- paymentType
- paymentAmt
Stores and manages transaction
information of an order
Order
<<entity>> Employee Attributes:
- employeeID
- employeeType
Stores and manages information
on employees involvedin an
order
Order
<<entity>> Product Attributes:
- prodID
- prodDescription
- prodAvailability
- prodPrice
- prodImage
Stores and manages product item
information
orderItem
cartItem
ProductLine
<<entity>> ProductLine Attributes:
- brandID
- brandDescription
- brandName
Stores and manages product line
information
Product
OEM

Page 46
<<entity>> OEM Attributes:
- mfrID
- mfrName
- mfrPhone
- mfrEmail
- mfrWebsite
manufacturer information
ProductLine
Category
<<entity>> Category Attributes:
- categoryID
- categoryName
- categoryDescription
category information
OEM

E-STORE ORDER RETURN
Page 47
E-Store Order Return
WORKFLOWDESCRIPTION
8.1 Patient selects a transaction from their purchasehistory
8.2 E-Store database looks up transaction record
8.2.1 If found, OEM willgeneratea return ticket
8.2.2 If not, E-Store promptsthe Patientthat the transaction wasnot
found
8.3 Credit/DebitCard Company verifiesrefund
8.4 E-Store storesreturn ticket
8.5 Patient sendsreturn shipment

Page 48
ACTIVITY DIAGRAM

Page 49
USE CASES
Actor Use Case Description
Patients, Doctors User Logon Users logs on to webstore/website account
Patients View purchase history See list of previouslycompleted transactionson own
account
Doctors View Patient purchase
history
See list of previouslycompleted transactionson a
given Patient’saccount
Patients, Doctors Create item return Create item return ticket via form
Patients Contact Patient service Call a live Patient service representative
USE CASE DIAGRAMS
DOMAIN CLASS DIAGRAMS
Please refer to E-Store Order Fulfillment diagram

Page 50

Page 51
CRC CARDS
<<handler>> ReturnHandler Attributes:
Initiates and handles
customers’ order returns
Customer

E-STORE REPORTING
Page 52
E-Store Reporting
WORKFLOWDESCRIPTION
9.1 User requestreportby specifyingreportinformation
9.2 E-Store database generates the requested report
9.3 User receivesthe generated report
ACTIVITY DIAGRAM

E-STORE REPORTING
Page 53
USE CASES
Users Use Case Description
Vendors, Doctors User Logon Users logs on to webstore/website
account
Vendors, Doctors View sales data View aggregated sales data on
given items/item categories
Doctors View user feedback View aggregated feedback from
Patients and vendors
Doctors View/Edit vendor item
information
View/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

E-STORE REPORTING
Page 54
USE CASE DIAGRAMS
Please refer to E-Store Order Fulfillment diagram

E-STORE REPORTING
Page 55

E-STORE REPORTING
Page 56
CRC CARDS
<<handler>> ReportHandler Attributes:
Initiates and handles
relevant sales/site usage
reports for doctors and
vendors
Customer

REAL-TIME MONITORING
Page 57
Real-Time Monitoring
PATIENTDATA READINGS –REAL TIMEMONITORING ACTIVITY DIAGRAM
10.1 Patientviews / respondsto alert
10.1.1 System processesalert
10.1 Doctor views/ respondsto alert
10.1.1 System processesalert
10.2 Patientviews history
10.2.1 System showshistory
10.3 Doctor viewshistory
10.3.1 System showshistory
10.4 Patientmakes notes
10.4.1 System savesnotes
10.5 Doctor makesnotes
10.5.1 System savesnotes
10.6 Doctor sets alert conditions
10.6.1 System sets alert conditions
10.7 Patientsendsmessage from doctor
10.7.1 System sendsmessage
10.8 Patientviews message from doctor
10.8.1 System showsmessage
10.9 Doctor sendstext message to patient
10.9.1 System sendstext message to patient
10.10 Doctor viewsmessage from doctor
10.11 System showsmessage
10.12 Patientexits - closes or movesto other section of the website
10.13 Doctor exits – closes or moves to other section of the website

Page 58
ACTIVITY DIAGRAM

Page 59
USE CASES
Patient 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 60
USE CASE DIAGRAMS

Page 61
DETAILED USE CASE – SET ALERTCONDITIONS
USE CASE NAME: SETALERT CONDITIONS
Scenario: Set alert conditions for real time glucose monitoring
Triggering event: Doctor wants to set alert conditions for glucose
monitoring
Brief 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: Doctor
Related 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 created
Customer info must be created
Monitoring device must be available and set
Phone must be available and set to receive data and send
text
Alert conditions must be set
Monitoring data must be acquired and stored
1. Doctor creates new
patient account.
2. Doctor enters upper
and lower glucose
level bounds to be
monitored for
1.1 System Creates new
patient
1.2 System prompts doctor
for patient info
2.1System saves new alert
conditions for the patient
Exception conditions: 1.1Doctor enters wrong login information
2.1The patient name is invalid
3.1The alert conditions exceed allowed parameters
4.1There is a typo (numbers/letters) conditions are not
saved

Page 62
SEQUENCEDIAGRAM – SEND MESSAGETO PATIENT
SEQUENCEDIAGRAM – SEND MESSAGETO PATIENT

Page 63

Page 64

Page 65
CRC CARDS
Crate patient CRC
New patient window screen lastName, dateOfBirt, gender, race,
height, weightAccept patient info Patient handler
dateOfBirt, gender, race, height,
weight
Create patient account
Create patient
Patient
dateOfBirt, gender, race, height,
weight
Create patient account
Create patient info
Patient
Create doctor
Doctor
Create doctor info
Doctor
Create alert condition CRC
Patient handler alertConditionId, type, startHour,
endHour, upprBound, lowerBound,
dateTime, value
Create new alert condition Patient handler
Patient handler dateTime, value
Create alert condition Patient Handler

Page 66
Create glucose observation CRC
Patient alertConditionId, type, startHour,
endHour, upprBound, lowerBound,
dateTime, value
Create new glucose
observation
Patient
Create monitoring device CRC
Doctor serialNumber, manufacturer,
dateOfManufacture, firmwareVersionCreate new monitoring
device
Doctor
Create cell phone CRC
Doctor Id, phoneNumber, operatingSystem,
osVesion, appVersionCreate cell phone condition Doctor
Create message CRC
Doctor dateTime, text
Create message Patient, Doctor

OVERVIEW: DIABETES TRACKING SYSTEM
Page 67
Overview: DiabetesTracking System
INTEGRATED DOMAIN CLASS DIAGRAM

TECHNOLOGY TOOLS FOR SOFTWARE
DEVOLOPMENT
Page 68
Technology Tools for Software Devolopment
Visual Paradigm
MS Project
Google Docs
Google Drive
MS Word

PROJECT PLAN
Page 69
Project Plan

COMP 246 GROUP PROJECT PART-B v.2

Recommended

Recommended

More Related Content

Viewers also liked

Viewers also liked (8)

Similar to COMP 246 GROUP PROJECT PART-B v.2

Similar to COMP 246 GROUP PROJECT PART-B v.2 (20)

COMP 246 GROUP PROJECT PART-B v.2