6. Use Case
What?
A use case is made up of a set of possible sequences of
interactions between systems and users in a particular
environment and related to a particular goal
7. Use Case
- A use case is a written description of how users/object will perform tasks.
-It outlines, from a user’s point of view, and a system’s behavior.
8. Use Case
When and Why ?
When you want to describe the criteria of something – it may
include how your day will be organized, or what the main steps
to achieve your life goals.
9. Use Case
- to explain your specialized idea to an audience with fragile background.
- to analyze your project/ idea, trying to predict the potential obstacles, and
find an optimal solution for it.
- -Engineering sense
11. Use Case
2- Actor:
Someone/thing that use the system to achieve a goal.
a- Primary actor:
-Initiate the use of the system.
b- Secondary actor:
-Reactionary
12. Use Case
3- Use Case:
Represents an action that accomplishes some sort of tasks
within the system.
Types: Base use case included use case, extended use case
16. Component Diagram
What ?
Component diagrams are model the physical or logical
aspects of a system.
It visualize the organization and relationships among
components in a system.
17. Component Diagram
When ?
- When you design a hardware Systems it could be help for
applying reverse engineering
- Interior/exterior Design
- Embedded system
- Engineering sense
24. Sequence diagram
Sequence diagrams describes interactions among
classes in terms of an exchange of messages over
time.
Simply, It shows different parts of a system work in a
‘sequence’ to get something done.
25. Sequence diagram
Sequence diagrams are sometimes known as event
diagrams or event scenarios.
“sequence of events”
interactions occur when a particular use case is
executed.
27. Sequence diagram
Actor: Shows entities that interact with or are external to the
system.
Object: Represents class or object in UML.
Activation box: Represents the time needed for object to
complete a task.
28. Sequence diagram
Lifeline : Represents the passage of time as it extends
downward. This dashed vertical line shows the sequential
events that occur to an object during the charted process.
29. Sequence diagram
Messages: showing information being sent between objects
Alternative symbol: Symbolizes a choice (that is usually
mutually exclusive) between two or more message sequences.
30. Sequence diagram
When&why
Represent the details of a UML use case.
See how objects and components interact with each other to
complete a process.
31. Sequence diagram
Plan and understand the detailed functionality of an existing or
future scenario.
Engineering sense
32. Sequence diagram
Best Practice
Manage complex interactions with sequence fragments.
Draw smaller sequence diagrams that capture the essence of
the use case.
Do not Adding too much details.
40. Deployment diagram
Shows how the software and hardware work together !!!!!!!
But it almost show nodes (hardware nodes)
41. Deployment diagram
As it describes the physical deployment of information
generated by the software program on hardware components.
Maps the system software artifacts to the hardware that
will execute them.
42. Deployment diagram
The information that software generates is called artifact.
In another words shows How software will be installed on
system .
43. Deployment diagram
Tools
Node: hardware or software object, shown by a three-
dimensional box.
Node as container: node that contains another node inside of
it.
Artifact: product developed by the software
44. Deployment diagram
Artifacts: A box with the header "<<artifact>>" and then the
name of the file.
Communication path: A straight line that represents
communication between two device nodes.
45. Deployment diagram
Component: rectangle with two tabs that indicates a software
element.
Dependency: dashed line that ends in an arrow, which
indicates that one node or component is dependent on
another.
46. Deployment diagram
When&why
Show which software elements are deployed by which
hardware elements.
Illustrate the runtime processing for hardware.
Provide a view of the hardware system’s topology.
Engineering sense
47. Deployment diagram
To model the embedded system.
To model the hardware details for a client/server system.
For Forward and Reverse engineering.
49. Deployment diagram
Do you have all the nodes you need? Do you know how they
are all connected?
Do you know which components are going to be on which
nodes?
