Virtual Secretary

1
Virtual Secretary

• Software engineering
• Rossier Romain
• Jobé Nöel
• Lathion Christian
• Bourgeois Jean

2
Schedule

• Introduction
• Basic description
• Functional description
• Diagrams
• Use cases description
• Conclusion

3
Introduction

• The Idea a secretary
• does always the same actions
• Answer phone call
• Receive client request for appointment
• Answer client request
• Fill her directors calendar
• Why dont we replace a secretary by an
  application?

4
Basic description

• Application for Doctor - Patient
• There is two interfaces
• Doctor Interface
• Patient Interface

5
Doctor Interface
6
Patient interface
7
Functional description Doctor

• Doctor login
• Scenario 
• 1. The Doctor logs
• 2. The system authenticate the doctor
• 3. Choose one option Validate appointments,
  Calendar management, Patient Data
• Extension
• 2a. The doctor doesnt enter correct login/pass
• 2a.1. Return to the beginning

8
Functional description Doctor

• Validate appointment
• Scenario
• 1. The system gives the lists of waiting
  appointments
• 2. The doctor validates or rejects appointments
• 3. The system responds with a confirmations
  dialog
• 4. The system saves it in the calendars DB
• Extension
• 3a. The doctor doesnt confirm
• 3a1. go to step 1

9
Functional description Doctor

• Calendar management
• Scenario
• the doctor defines his calendar or modifies
  appointments or cancel appointments
• the system responds with a confirmations dialog
• the system saves it in the calendars DB
• Extension
• 2a. if the doctor doesnt confirm go
• 2a.1 go to step1

10
Functional description Doctor

• Patient data
• Scenario
• 1. the doctor chooses a patient
• 2. the system gives him the patients folder from
  de patients DB

11
Functional description Patient

• Patient login
• Scenario 
• 1. The Patient logs
• 2. The system authenticate the patient
• 3. Choose one options take, cancel , show
  appointments or manage some data
• Extension
• 1a. The Patient isnt subscribed
• 1a.1. The Patient enter its information and goes
  to the step 3
• 2a. The Patient doesnt enter correct login/pass
• 2a.1. Return to the beginning
• 3a. There is validation or rejection of
  appointments
• 3a.1 Window appears notification

12
Functional description Patient

• Take an appointment
• Scenario 
• 1) The patient can chooses a category of doctors
  or takes a doctor
• 2) The patient can give his dates and enter
  information
• 3) The patient chooses one proposition
• 4) Return to the options menu.
• Extension
• 3a. No result
• 3a.1 go to step 1
• 3b. Propositions dont match
• 3b.1 search more

13
Functional description Patient

• Cancel an appointment
• Scenario
• 1. The patient choose an appointment from his
  appointments list
• 2. The system responds with a confirmations
  dialog
• 3. The patient confirms it
• 4. The system deletes this appointment from the
  calendars DB
• Extension
• 3a. The patient doesnt confirm it
• 3a.1 go to step 1
• 3.b Appointment is to close
• 3b.1 Notification

14
Functional description Patient

• Show appointments
• Scenario
• The system responds with a list of his
  appointments
• Extension
• 1a. No appointment
• 1a.1 Notification
• Show information
• Scenario
• The patient enter this information
• The system saves it in the Patients DB

15
Conclusion

• An Idea up-to-date
• Database
• Network communication
• Security
• Web interface or application interface