Analysis and Design Homework

profilesinister670
analysisdesign.zip
Home>Computer Science homework help>Analysis and Design Homework

AnalysisDesign/.DS_Store

AnalysisDesign/Analysis_Design_Homework.docx

Minimum 250 Words.

Discussion Points

1. What is systems design and its activities? How is it different from systems analysis?

2. What is a three-layer architecture and what are the contents of each layer?

A web search for relevant articles and information could be employed to assist you in your response.

Forum Rubric 

 

Rubric for Learner Posts

Points

1. Synthesis of concepts in 250 or more words

(critical to class performance)

30

2. Applications of personal experience

20

3. Writing standards

10

AnalysisDesign/Assignment3.docx

Assignment 3

Instructions

1 Develop diagrams for use case" Make an Appointment"

1 1 Using the above case study specifications (Part 1 and Part 2),  create a fully developed use case description for the "Make an Appointment" use case.  Follow the  exact format in Figure 5-3 on p. 124 in your textbook for your fully developed use case description.

2 2  Create a UML activity diagram using your CASE tool.  Follow the detailed use case description you created in 1.1 above. for the "Make an Appointment" use case.

3 3  Create a UML SSD using your CASE tool.  Remember that the detailed steps in the use case description form the basis for the activity diagram.  The activity diagram and the class diagram (from Assignment 2) form the basis for the SSD (System Sequence Diagram).   We are not doing a full sequence diagram but rather just the SSD which will show the actor and the system object with essentially the inputs and outputs for the system.  See the examples on pp. 131, 133.

4 4  Include your class diagram from Assignment 2 for reference and create a list of the attributes for each class. Attributes are properties of a class.  For example, for the class Patient, we might have the attributes patientID, patientFirstname, patientLastname, patientAddress, patientCity, patientState, patientZipcode,patientPhone, patientBirthDate, etc.

5 5  Create a state diagram for the Appointment class.

I nclude a discussion of the models.  Discuss how they are related.  Identify messages from the SSD that need to be added to your class diagram.

2  Create a UML activity diagram using your CASE tool.  Follow the detailed use case description you created in 1.1 above. for the "Make an Appointment" use case.

3  Create a UML SSD using your CASE tool.  Remember that the detailed steps in the use case description form the basis for the activity diagram.  The activity diagram and the class diagram (from Assignment 2) form the basis for the SSD (System Sequence Diagram).   We are not doing a full sequence diagram but rather just the SSD which will show the actor and the system object with essentially the inputs and outputs for the system.  See the examples on pp. 131, 133.

Use Case Name

Make an appointment

Scenario

Book an appointment with your doctor, Request for medical refill or get lab results.

Triggering Event

The CPPS is notified of new Patient request

Brief Description

The CPPS gets the patient request then helps the patient find the convenient time to book an appointment with the doctor, or it gets the Patient request to get lab report it helps the client by checking if the lab report is ready, if its ready it retrieves the report. It also Helps the client see the available medication their details and dosage and then has option to request for refill.

Actors

Doctors

Related Use Cases

Stakeholders

Client ,Marketing ,Doctors, Deliveries guys, Lab technicians.

Precondition

Customer must first be registered

Customer must be logged in

Medicine for refill must be available first

Time for appointment must be made available according to doctors availability.

Post Condition

Appointment is created and associated with the client.

Date and time of appointment is updated as booked.

Lab report is availed and indicated that it was delivered.

Medicine are recorded as requested for refill.

Flow of activities

ACTOR System

Client wants to book an appointment.

The system looks for available doctors and their schedules and avails them to client.

Client books an appointment.

The system records it and notifies the doctor and updates the doctors schedule marking that time as booked so no other client can book that time.

Client want to order a refill.

The system avails available medicines and their details.

Client places the refill order.

The system records that and alerts the pharmacist.

Client wants to check/download their lab report.

The system checks for client details and related ready lab reports and avails them to the client.

After the client is done she/he confirms the order.

The systems reconfirms the request by client and places it after confirmation.

Exception conditions

If the client can’t find a convenient time in the doctor’s schedule in that day, the system allows them to select a future date when its available

If the client can’t find the medicine they want they can message the company notifying them.

4  Include your class diagram from Assignment 2 for reference and create a list of the attributes for each class. Attributes are properties of a class.  For example, for the class Patient, we might have the attributes patientID, patientFirstname, patientLastname, patientAddress, patientCity, patientState, patientZipcode,patientPhone, patientBirthDate, etc.

5  Create a state diagram for the Appointment class.

image1.emf

Microsoft_Word_Document1.docx

Client

System

RegisterClient(Names,phone ,emails)

custID ,Name,Phone,emails

Address details=enterAddress(address)

EnterCreditCardInfo(BankInfo)

Banking Details

Choose Type of portal to use=PortalChoice()

Verify info(CustID,Name,BankDetails,Address)

Make an appointment ()

DoctorsName,ScheduleTime,ScheduleDate

PickSchedule(DoctorsName,scheduleDate,scheduleTime,Reason)

Summary(Name,sceduleDate,scheduleTime,DoctorsName,Duration,Reason)