Project Milestone 1

Project Milestone 1
The first deliverable will consist of presenting the overall architecture of the
system in terms of UML diagrams. Additionally, you should present and
explain the technology stack you are going to employ for the project
implementation. The stack description should list benefits and drawbacks of
the proposed solution, and fitness of the given approach towards the
hospital system implementation.
The task expects the followings deliverables:
1) Class diagram.
2) Use case diagram.
3) Activity diagram.
4) The technology stack with description and general explanation why it
fits the given system.
There are different online tools that you can use to draw UML diagrams:
https://creately.com/
https://www.smartdraw.com/uml-diagram/uml-diagram-tool.htm
https://staruml.io/
Class diagrams
The class diagram depicts a static view of an application. It represents the types
of objects residing in the system and the relationships between them. A class
consists of its objects, and also it may inherit from other classes. A class diagram
is used to visualize, describe, document various different aspects of the system,
and also construct executable software code.
It shows the attributes, classes, functions, and relationships to give an overview

of the software system. It constitutes class names, attributes, and functions in a
separate compartment that helps in software development. Since it is a collection
of classes, interfaces, associations, collaborations, and constraints, it is termed as
a structural diagram.
The main purpose of class diagrams is to build a static view of an application. It

is the only diagram that is widely used for construction, and it can be mapped
with object-oriented languages. It is one of the most popular UML diagrams.
Following are the purpose of class diagrams given below:
1. It analyses and designs a static view of an application.
2. It describes the major responsibilities of a system.
3. It is a base for component and deployment diagrams.
4. It incorporates forward and reverse engineering.
Benefits of Class Diagrams
1. It can represent the object model for complex systems.

2. It reduces the maintenance time by providing an overview of how an
application is structured before coding.
3. It provides a general schematic of an application for better understanding.
4. It represents a detailed chart by highlighting the desired code, which is to
be programmed.
5. It is helpful for the stakeholders and the developers.
Figure 1. Example of the class diagram.

Use case diagram
A use case diagram is used to represent the dynamic behavior of a system. It

encapsulates the system's functionality by incorporating use cases, actors, and
their relationships. It models the tasks, services, and functions required by a
system/subsystem of an application. It depicts the high-level functionality of a
system and also tells how the user handles a system.
The main purpose of a use case diagram is to portray the dynamic aspect of a
system. It accumulates the system's requirement, which includes both internal as
well as external influences. It invokes persons, use cases, and several things that
invoke the actors and elements accountable for the implementation of use case
diagrams. It represents how an entity from the external environment can interact
with a part of the system.
Following are the purposes of a use case diagram given below:
1. It gathers the system's needs.

2. It depicts the external view of the system.
3. It recognizes the internal as well as external factors that influence the
system.
4. It represents the interaction between the actors.
After that, we will enlist the actors that will interact with the system. The actors
are the person or a thing that invokes the functionality of a system. It may be a
system or a private entity, such that it requires an entity to be pertinent to the
functionalities of the system to which it is going to interact.
Once both the actors and use cases are enlisted, the relation between the actor and
use case/ system is inspected. It identifies the no of times an actor communicates
with the system. Basically, an actor can interact multiple times with a use case or
system at a particular instance of time.
Following are some rules that must be followed while drawing a use case
diagram:
1. A pertinent and meaningful name should be assigned to the actor or a use

case of a system.
2. The communication of an actor with a use case must be defined in an
understandable way.
3. Specified notations to be used as and when required.
4. The most significant interactions should be represented among the multiple
no of interactions between the use case and actors.
Figure 2. Example of the use case diagram.
Activity diagram
In UML, the activity diagram is used to demonstrate the flow of control within
the system rather than the implementation. It models the concurrent and
sequential activities.
The activity diagram helps in envisioning the workflow from one activity to
another. It put emphasis on the condition of flow and the order in which it occurs.
The flow can be sequential, branched, or concurrent, and to deal with such kinds
of flows, the activity diagram has come up with a fork, join, etc.
It is also termed as an object-oriented flowchart. It encompasses activities
composed of a set of actions or operations that are applied to model the behavioral
diagram.
Activities
The categorization of behavior into one or more actions is termed as an activity.

In other words, it can be said that an activity is a network of nodes that are
connected by edges. The edges depict the flow of execution. It may contain action
nodes, control nodes, or object nodes.
The control flow of activity is represented by control nodes and object nodes that
illustrates the objects used within an activity. The activities are initiated at the
initial node and are terminated at the final node.
Activity partition /swimlane
The swimlane is used to cluster all the related activities in one column or one row.
It can be either vertical or horizontal. It used to add modularity to the activity
diagram. It is not necessary to incorporate swimlane in the activity diagram. But
it is used to add more transparency to the activity diagram.
Forks
Forks and join nodes generate the concurrent flow inside the activity. A fork node
consists of one inward edge and several outward edges. It is the same as that of
various decision parameters. Whenever a data is received at an inward edge, it
gets copied and split crossways various outward edges. It split a single inward
flow into multiple parallel flows.
Join Nodes
Join nodes are the opposite of fork nodes. A Logical AND operation is performed
on all of the inward edges as it synchronizes the flow of input across one single
output (outward) edge.
Pins
It is a small rectangle, which is attached to the action rectangle. It clears out all
the messy and complicated thing to manage the execution flow of activities. It is
an object node that precisely represents one input to or output from the action.
Notation of an Activity diagram
Activity diagram constitutes following notations:
Initial State: It depicts the initial stage or beginning of the set of actions.
Final State: It is the stage where all the control flows and object flows end.
Decision Box: It makes sure that the control flow or object flow will follow only
one path.
Action Box: It represents the set of actions that are to be performed.
Why use Activity Diagram?
An event is created as an activity diagram encompassing a group of nodes

associated with edges. To model the behavior of activities, they can be attached
to any modeling element. It can model use cases, classes, interfaces, components,
and collaborations.
It mainly models processes and workflows. It envisions the dynamic behavior of

the system as well as constructs a runnable system that incorporates forward and
reverse engineering. It does not include the message part, which means message
flow is not represented in an activity diagram.
It is the same as that of a flowchart but not exactly a flowchart itself. It is used to
depict the flow between several activities.
How to draw an Activity Diagram?
An activity diagram is a flowchart of activities, as it represents the workflow

among various activities. They are identical to the flowcharts, but they themself
are not exactly the flowchart. In other words, it can be said that an activity
diagram is an enhancement of the flowchart, which encompasses several unique
skills.
Since it incorporates swimlanes, branching, parallel flows, join nodes, control

nodes, and forks, it supports exception handling. A system must be explored as a
whole before drawing an activity diagram to provide a clearer view of the user.
All of the activities are explored after they are properly analyzed for finding out
the constraints applied to the activities. Each and every activity, condition, and
association must be recognized.
After gathering all the essential information, an abstract or a prototype is built,

which is then transformed into the actual diagram.
Following are the rules that are to be followed for drawing an activity diagram:
1. A meaningful name should be given to each and every activity.

2. Identify all of the constraints.
3. Acknowledge the activity associations.
Example of an Activity Diagram
An example of an activity diagram showing the business flow activity of order

processing is given below.
Here the input parameter is the Requested order, and once the order is accepted,
all of the required information is then filled, payment is also accepted, and then
the order is shipped. It permits order shipment before an invoice is sent or
payment is completed.
Figure 3. Example of activity diagram.

Project Milestone 1

Uploaded by

Copyright:

Available Formats

Project Milestone 1

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Project Milestone 1

Uploaded by

Copyright:

Available Formats

Project Milestone 1

It shows the attributes, classes, functions, and relationships to give an overview

The main purpose of class diagrams is to build a static view of an application. It

Benefits of Class Diagrams

1. It can represent the object model for complex systems.

Figure 1. Example of the class diagram.

A use case diagram is used to represent the dynamic behavior of a system. It

Following are the purposes of a use case diagram given below:

1. It gathers the system's needs.

1. A pertinent and meaningful name should be assigned to the actor or a use

Figure 2. Example of the use case diagram.

The categorization of behavior into one or more actions is termed as an activity.

Activity partition /swimlane

Activity diagram constitutes following notations:

Action Box: It represents the set of actions that are to be performed.

Why use Activity Diagram?

An event is created as an activity diagram encompassing a group of nodes

It mainly models processes and workflows. It envisions the dynamic behavior of

How to draw an Activity Diagram?

An activity diagram is a flowchart of activities, as it represents the workflow

Since it incorporates swimlanes, branching, parallel flows, join nodes, control

After gathering all the essential information, an abstract or a prototype is built,

1. A meaningful name should be given to each and every activity.

Example of an Activity Diagram

An example of an activity diagram showing the business flow activity of order

You might also like

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.