Beruflich Dokumente
Kultur Dokumente
LABORATORY MANUAL
CASE-TOOLS LAB
CLASS: III B. Tech(R07) II Semester
Page 1
1.a
Experiment
Introduction to uml
Use case diagram for LMS
Pg. No
3
6
1.b
2.a
2.b
12
3.a
13
3.b
18
21
4.a
29
4.b
5.a
32
5.b
35
6.a
37
38
6.b
7.a
39
41
Page 2
Things in UML:
Structural things
Classes
Interfaces
Collaborations
Use Cases
Active Classes
Components
Node
Behavioral things
Interactions
State machines
Grouping things
Packages
Annotational things
Notes
Relationships in UML:
Dependency
Association
Generalization
Realization
Diagrams in UML :
Class Diagram
Object Diagram
Use case Diagram
Sequence Diagram
Collaboration Diagram
State chart Diagram
Activity Diagram
Component Diagram
Deployment Diagram
Page 3
<<Interface>>
MouseListener
MyFrame() : MyFrame
open(void) : void
close(int status) : void
resize(int height, int width) : void
minimize(void) : void
maximize(void) : void
(from event)
mouseClicked()
mousePressed()
mouseReleased()
mouseEntered()
mouseExited()
Collaboration:
Use Case:
Place Order
Component:
Active Classes:
OrderForm.java
Node:
File Server
Interaction:
State Machine:
Page 4
Packages:
Grouping things are the organizational parts of UML models. These are
the boxes into which a model can be decomposed. In all, there is one primary
kind of grouping thing, namely, Packages.
java.swing.*
Notes:
Annotational things are the explanatory parts of UML Models. These are
the comments you may apply to describe and illuminate about any element in a
model.
return copy of self
Dependency:
-------------------------------->
Association:
_____________________
_
Generalization:
__________________
____
Realization:
------------------------------
Page 5
Week-1
A) Aim: implementation of use case diagrams for LMS
Description:
Use Case Diagrams:
A use case diagram is a diagram that shows a set of use cases and actors and their
relationships.
A use case diagram commonly contain
Use cases
Actors
Dependency
Page 6
Page 7
Week-2
BVC COLLEGE OF ENGINEERING, DEPT.OF CSE
Page 8
Description:
Class Diagrams:
Terms and Concepts:
A class is a description of a set of objects that share the same attributes,
operations, relationships and semantics. Graphically, a class is rendered as a rectangle.
Class diagram commonly contains the following things.
Classes,
Interfaces,
Collaboration,
Identify those things that users or implementers use to describe the problem or
solution.
Use CRC cards and use case-based analysis to help find these abstractions.
For each abstraction, identify a set of responsibilities. Make sure that each
class is crisply defined and that there is a good balance of responsibilities
among all your classes.
Provide the attributes and operations that are needed to carry out these
responsibilities for each class.
Modeling the Distribution of Responsibilities in a System
To model the distribution of responsibilities in a system,
Identify a set of classes that work together closely to carry out some behavior.
BVC COLLEGE OF ENGINEERING, DEPT.OF CSE
Page 9
If you want to distinguish these things from the UML's defined building
blocks, create a new building block by using stereotypes to specify these new
semantics and to give a distinctive visual cue.
If the thing you are modeling is some kind of hardware that itself contains
software, consider modeling it as a kind of node, as well, so that you can
further expand on its structure.
Page 10
Page 11
Page 12
Description:
Interaction Diagrams:
Terms and Concepts:
An interaction is a behavior that comprises a set of messages exchanged among a set
of Objects within a context to accomplish a purpose.
A message is a specification of a communication between objects that conveys
information with the expectation that activity will ensue.
A sequence diagram is an interaction diagram that emphasizes the time ordering of
messages.
A collaboration diagram is an interaction diagram that emphasizes the structural
organization of the objects that send and receive messages.
Interaction diagrams commonly contain
Objects
Links
Messages
Interaction diagrams are used in two ways:
Set the context for the interaction, whether it is the system as a whole, a class,
or an individual operation.
Set the stage for the interaction by identifying which objects play a role; set
their initial properties, including their attribute values, state, and role.
In time order, specify the messages that pass from object to object. As
necessary, distinguish the different kinds of messages; include parameters and
return values to convey the necessary detail of this interaction.
Also to convey the necessary detail of this interaction, adorn each object at
every moment in time with its state and role.
Page 13
Page 14
Page 15
Page 16
Page 17
Page 18
Withdrawal-usecase-successful-scenario:
Page 19
Page 20
Action states:
Action states represent the non interruptible actions of objects. You can draw an action
state in SmartDraw using a rectangle with rounded corners.
Action Flow: Action flow arrows illustrate the relationships among action states.
Object Flow:
BVC COLLEGE OF ENGINEERING, DEPT.OF CSE
Page 21
Initial State:
A filled circle followed by an arrow represents the initial action state.
Final State:
An arrow pointing to a filled circle nested inside another circle represents the final
action
Branching:
A diamond represents a decision with alternate paths. The outgoing alternates should
be labeled with a condition or guard expression. You can also label one of the paths "else.
Swimlanes:
Swimlanes group related activities into one column
BVC COLLEGE OF ENGINEERING, DEPT.OF CSE
Page 22
Transition:
A transition is a directed relationship between a source state vertex and a target state
vertex. It may be part of a compound transition, which takes the state machine from one state
configuration to another, representing the complete response of the state machine to a
particular event instance. A solid arrow represents the path between different states of an
object. Label the transition with the event that triggered it and the action that results from it.
A relationship between two states, indicating that an object in the first state will enter the
second state and perform certain specified actions when a specified event occurs, if specified
conditions are satisfied.
Synchronization:
A synchronization bar helps illustrate parallel transitions. Synchronization is also
called forking and joining.
Page 23
Page 24
Page 25
Page 26
Page 27
Activity Diagrams of LMS Add Book use case add Add Member use case
Page 28
Page 29
Page 30
Page 31
Final state:
A condition at the end of the life of an object or an interaction during which it
satisfies some condition, performs some action, or waits for some event.
State:
A condition during the life of an object or an interaction during which it satisfies
some condition, performs some action, or waits for some event.
History Indicator:
BVC COLLEGE OF ENGINEERING, DEPT.OF CSE
Page 32
Transition:
A relationship between two states, indicating that an object in the first state will
enter the second state and perform certain specified actions when a specified event
occurs, if specified conditions are satisfied.
Page 33
Page 34
Page 35
Page 36
Interface:
An interface describes a group of operations used or created by components.
Dependencies:
Draw dependencies among components using dashed arrows.
Page 37
Page 38
Week-7
Aim: Implementation of Deployment diagram for LMS
Description:
Deployment Diagram
Deployment diagrams depict the physical resources in a system including nodes,
components and connections.
Basic Deployment Diagram Symbols and Notations
Node:
A node is a physical resource that executes code components.
Association:
Association refers to a physical connection between nodes, such as Ethernet.
Components and Nodes: Place components inside the node that deploys them.
BVC COLLEGE OF ENGINEERING, DEPT.OF CSE
Page 39
Relationships:
Dependency:
A dependency is a semantic relationship between two things in which a change
to one thing may affect the semantics of the other thing. Graphically, a
dependency is rendered as a dashed line, possibly directed, and occasionally
including a label.
Association:
An association is a structural relationship that describes a set of links, a link
being a connection among objects. Graphically, an association is rendered as a
solid line, possibly directed, occasionally including a label, and often
containing other adornments.
Page 40
Page 41
Page 42