Changes between Initial Version and Version 1 of Diagrams_

Timestamp:

05/03/14 15:51:49 (10 years ago)

Author:

139037

Comment:

--

Diagrams_

@@ +1 @@
+     
+    '''    Use Case Diagram'''
+
+A use case diagram represents a set of use cases and actors and their relationships.
+The main actors that are involved in the first use case diagram are: administrator, doctor and nurse. Every actor is related to a certain number of use cases. Every use case represents the tasks that should be performed within the application by a certain actor. In figure 1 the actor Administrator is in relation with the same use cases that is the actor Doctor, this is done because the administrator at the same time can work as a doctor in a given health center. 
+ 
+
+ 
+[[Image(1.jpg)]]
+
+Figure 1.[[BR]]
+
+
+Use Case Diagram
+
+The use case diagram that is in the Figure 2 represent 2 main actors with 4 use cases. Here is described the tasks that the actors Doctor and Patient perform for making an appointment. 
+
+ 
+
+ [[Image(2.jpg)]][[BR]]
+
+Figure 2.[[BR]]
+
+ Appointment Use case Diagram
+
+
+
+
+
+
+Activity Diagram 
+
+The activity diagram addresses a dynamic view of the system, it also emphasizes the flow of objects and synchronization of the flow in support of parallel processing. Here are presented two activity diagrams the first one is the main activity diagram which represents the most important activities of the system, and the second one is the schedule-appointment activity diagram. 
+
+
+ [[Image(3.jpg)]][[BR]]
+Figure 3.[[BR]]
+ Activity Diagram 
+
+
+
+
+ 
+[[Image(4.jpg)]][[BR]]
+Figure 4. [[BR]]
+
+Schedule-Appointment Activity Diagram
+
+
+
+Sequence Diagram 
+A sequence diagram represents the interaction between different objects in the system. The important aspect of a sequence diagram is that it is time ordered which means that the exact sequence of the interactions between the objects is represented step by step as shown in figure 6.
+
+ 
+[[Image(5.jpg)]][[BR]]
+Figure 5.[[BR]]
+
+
+ Sequence- Diagram Schedule Appointment 
+
+
+This sequence diagram represents the timing and flow of information within the “make appointment” use case.  The summation of the appointment record is called the Doctors Schedule.  The System Controller verifies that the appointment time is available notifies the patient, who confirms the appointment and the system updates the database.
+
+
+ Collaboration Diagram
+
+A collaboration diagram describes interactions among objects in terms of sequenced messages. Collaboration diagrams represent a combination of information taken from class, sequence, and use case diagrams describing both the static structure and dynamic behavior of a system.
+
+
+ 
+ [[Image(6.jpg)]] [[BR]]          
+Figure 6.[[BR]]
+
+
+
+
+
+
+
+
+CLASS DIAGRAM
+
+Classes represent an abstraction of entities with common characteristics. Associations represent the relationships between classes.
+
+
+ 
+[[Image(7.jpg)]][[BR]]
+ Figure 7.[[BR]]
+
+
+
+
+
+
+STATE DIAGRAM
+
+A statechart diagram shows the behavior of classes in response to external stimuli. This diagram models the dynamic flow of control from state to state within a system.
+States represent situations during the life of an object. You can easily illustrate a state in SmartDraw by using a rectangle with rounded corners.
+
+ [[Image(8.jpg)]][[BR]]
+Figure 8.[[BR]]