Software Engineering and Testing

Lab
17CS67L
Lab Manual
Course Syllabus
Exercise
No Title of the Exercise
1 Revision on Software Engineering-I
2 Introduction to UML: History, Goals, Object-Oriented concepts,

3 Building Blocks, Modeling Types and Basic Notations

4 Introduction to Rational Rose Software

5 Use case diagram: to perform the user’s view analysis

6 Interaction Diagram (Sequence and Collaboration Diagrams) : to draw the

behavioral view diagram
7 State chart and Activity diagrams: to draw the behavioral view diagram

8 Class and object diagrams: to draw the structural view diagram

9 Component diagram: to draw the implementation view diagram

10 Deployment diagram: to draw the environmental view diagram

Page 1 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 Course Description (As per course Specification)
This course is an advanced course in software engineering. Topics coves, software
quality and development, software metrics, measuring complexity, quality,
productivity, maintainability and usability. Object oriented principle. Object oriented
design and its practical applications. Software design using re-engineering approach.
 Lab Description
The student is expected to revise basic concepts of Software Engineering,
Introduction to UML, History, Goals, Object-Oriented concepts, Building Blocks,
Modeling Types and Basic Notations. The Lab experiments are done using the Rational
Rose Software, Use case diagram: to perform the user’s view analysis.
Interaction Diagram (Sequence and Collaboration Diagrams) to draw the behavioral
view diagram, State chart and Activity diagrams: to draw the behavioral view diagram the
take up about five mini- projects and model them and produce Use Cases, Analysis
Documents- both static & dynamic aspects, Sequence Diagrams and State- Charts,
Database design. The Class and object diagrams: to draw the structural view diagram,
Component diagram: to draw the implementation view diagram, Deployment diagram: to
draw the environmental view diagram. A sample collection of Ideas is given. Numerous
other ideas can be found in the pages from the list of references given.

Hardware / Software Requirements

 PC Configuration:

-Processor: Intel core Processor

-CPU: 2.0 GHz or above.

-System: 32 bit operating system.

-Installed memory (RAM) 1 GB.

 Rational Rose Software UML 1.0

Page 2 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 Week-wise Practical Schedule (15 weeks)

Week Exercise Title of the Experiment / Exercise Page No.

No
Week 1 1 Revision on Software Engineering-I
Week 2 & 2 Introduction to UML: History, Goals, Object-
Week 3 Oriented concepts,
Week 4 & 3 Building Blocks, Modeling Types and Basic
Week 5 Notations
Week 6 & 4 Introduction to Rational Rose Software
Week 7
Week 8 & 5 Use case diagram: to perform the user’s view
Week 9 analysis
Week10 & 6 Interaction Diagram (Sequence and Collaboration
Week 11 Diagrams) : to draw the behavioral view diagram
Week 12 7 Statechart and Activity diagrams: to draw the
behavioral view diagram
Week 13 8 Class and object diagrams: to draw the structural
view diagram
Week 14 9 Component diagram: to draw the implementation
view diagram
Week 15 10 Deployment diagram: to draw the environmental
view diagram

Lab Session 1 / Exercise 1 (Week 1)

Page 3 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 Title of the Exercise: Revision on Software Engineering-I

 Objectives / Statement Purpose:

 UML is a standard language for specifying, visualizing, constructing, and
documenting the artifacts of software systems.
 UML was created by Object Management Group (OMG) and UML 1.0
specification draft was proposed to the OMG in January 1997.
 OMG is continuously putting effort to make a truly industry standard.
 UML stands for Unified Modeling Language.
 UML is different from the other common programming languages
like C++, Java, and COBOL etc.
 UML is a pictorial language used to make software blue prints.
 So UML can be described as a general purpose visual modeling language
to visualize, specify, construct and document software system. Although
UML is generally used to model software systems but it is not limited
within this boundary. It is also used to model non software systems as well
like process flow in a manufacturing unit etc.
 UML is not a programming language but tools can be used to generate
code in various languages using UML diagrams. UML has a direct relation
with object oriented analysis and design. After some standardization UML
is become an OMG (Object Management Group) standard.
 Activity Outcomes:
 A picture is worth a thousand words, this absolutely fits while discussing
about UML. Object oriented concepts were introduced much earlier than
UML. So at that time there were no standard methodologies to organize
and consolidate the object oriented development. At that point of time
UML came into picture.
 There are a number of goals for developing UML but the most important is
to define some general purpose modeling language which all modelers can
use and also it needs to be made simple to understand and use.
 UML diagrams are not only made for developers but also for business
users, common people and anybody interested to understand the system.
The system can be a software or non software. So it must be clear that

Page 4 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 UML is not a development method rather it accompanies with processes to
make a successful system.

 Instructions for solving problems :

To understand conceptual model of UML first we need to clarify what is a conceptual
model? and why a conceptual model is at all required?
 A conceptual model can be defined as a model which is made of concepts
and their relationships.
 A conceptual model is the first step before drawing a UML diagram. It
helps to understand the entities in the real world and how they interact
with each other.

Page 5 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 Exercise 2 (Week 2 and Week 3)

Title of the Exercise: Introduction to UML: History, Goals, and

Object-Oriented concepts

 Objectives / Statement Purpose:

As UML describes the real time systems it is very important to make a conceptual
model and then proceed gradually. Conceptual model of UML can be mastered by
learning the following three major elements:
 UML building blocks
 Rules to connect the building blocks
 Common mechanisms of UML

Object oriented concepts:

UML can be described as the successor of object oriented analysis and design.
An object contains both data and methods that control the data. The data represents
the state of the object. A class describes an object and they also form hierarchy to
model real world system. The hierarchy is represented as inheritance and the classes
can also be associated in different manners as per the requirement.
The objects are the real world entities that exist around us and the basic concepts like
abstraction, encapsulation, inheritance, polymorphism all can be represented using
UML.
So UML is powerful enough to represent all the concepts exists in object oriented
analysis and design. UML diagrams are representation of object oriented concepts
only. So before learning UML, it becomes important to understand OO concepts in
details.

Following are some fundamental concepts of object oriented world:

 Objects: Objects represent an entity and the basic building block.
 Class: Class is the blue print of an object.
 Abstraction: Abstraction represents the behavior of a real world entity.
 Encapsulation: Encapsulation is the mechanism of binding the data
together and hiding them from outside world.

Page 6 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
  Inheritance: Inheritance is the mechanism of making new classes from
existing one.
 Polymorphism: It defines the mechanism to exist in different forms.
OO Analysis and Design:
Object oriented analysis can be defined as investigation and to be more specific it is
the investigation of objects. Design means collaboration of identified objects.
So it is important to understand the OO analysis and design concepts. Now the most
important purpose of OO analysis is to identify objects of a system to be designed.
This analysis is also done for an existing system. Now an efficient analysis is only
possible when we are able to start thinking in a way where objects can be identified.
After identifying the objects their relationships are identified and finally the design is
produced.
So the purpose of OO analysis and design can described as:

 Identifying the objects of a system.

 Identify their relationships.
 Make a design which can be converted to executables using OO
languages.

There are three basic steps where the OO concepts are applied and
implemented. The steps can be defined as

OO Analysis --> OO Design --> OO implementation using OO languages

Now the above three points can be described in details:

 During object oriented analysis the most important purpose is to identify

objects and describing them in a proper way. If these objects are identified
efficiently then the next job of design is easy. The objects should be
identified with responsibilities. Responsibilities are the functions
performed by the object. Each and every object has some type of
responsibilities to be performed. When these responsibilities are
collaborated the purpose of the system is fulfilled.

Page 7 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
  The second phase is object oriented design. During this phase emphasis is
given upon the requirements and their fulfilment. In this stage the objects
are collaborated according to their intended association. After the
association is complete the design is also complete.

 The third phase is object oriented implementation. In this phase the design
is implemented using object oriented languages like Java, C++ etc.

Role of UML in OO design:

UML is a modeling language used to model software and non-software systems.
Although UML is used for non-software systems the emphasis is on modeling object
oriented software applications. Most of the UML diagrams discussed so far are used
to model different aspects like static, dynamic etc. Now what ever be the aspect the
artifacts are nothing but objects.

If we look into class diagram, object diagram, collaboration diagram, interaction

diagrams all would basically be designed based on the objects.

So the relation between OO design and UML is very important to understand. The
OO design is transformed into UML diagrams according to the requirement. Before
understanding the UML in details the OO concepts should be learned properly. Once
the OO analysis and design is done the next step is very easy. The input from the OO
analysis and design is the input to the UML diagrams.

Page 8 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 Exercise 3 (Week 4 and Week 5)

Title of the Exercise: 3 Building Blocks, Modeling Types and Basic

Notations

 Objectives / Statement Purpose:

UML Building Blocks
As UML describes the real time systems it is very important to make a conceptual
model and then proceed gradually. Conceptual model of UML can be mastered by
learning the following three major elements:

 UML building blocks

 Rules to connect the building blocks
 Common mechanisms of UML

This chapter describes all the UML building blocks. The building blocks of UML can
be defined as:
 Things
 Relationships
 Diagrams

Things:
Things are the most important building blocks of UML. Things can be:
 Structural
 Behavioral
 Grouping
 Annotational

Structural things:

Page 9 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
The Structural things define the static part of the model. They represent physical and
conceptual elements. Following are the brief descriptions of the structural things.
Class:
Class represents set of objects having similar responsibilities.

Interface:
Interface defines a set of operations which specify the responsibility of a class.

Collaboration:
Collaboration defines interaction between elements.

Use case:
Use case represents a set of actions performed by a system for a specific goal.

Component:
Component describes physical part of a system.

Node:
A node can be defined as a physical element that exists at run time.

Page 10 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
Behavioral things:
A behavioral thing consists of the dynamic parts of UML models. Following are the
behavioral things:

Interaction:
Interaction is defined as a behavior that consists of a group of messages exchanged
among elements to accomplish a specific task.

State machine:
State machine is useful when the state of an object in its life cycle is important. It
defines the sequence of states an object goes through in response to events. Events are
external factors responsible for state change.

Grouping things:
Grouping things can be defined as a mechanism to group elements of a UML model
together. There is only one grouping thing available:

Package:
Package is the only one grouping thing available for gathering structural and
behavioral things.

Page 11 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
Annotational things:
Annotational things can be defined as a mechanism to capture remarks, descriptions,
and comments of UML model elements. Note is the only one Annotational thing
available.

Note:
A note is used to render comments, constraints etc of an UML element.

 Instructions for solving problems :

Relationship :
Relationship is another most important building block of UML. It shows how
elements are associated with each other and this association describes the
functionality of an application.

There are four kinds of relationships available.

Dependency:
Dependency is a relationship between two things in which change in one element also
affects the other one.

Association:
Association is basically a set of links that connects elements of an UML model. It also
describes how many objects are taking part in that relationship.

Page 12 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
Generalization:
Generalization can be defined as a relationship which connects a specialized element
with a generalized element. It basically describes inheritance relationship in the world
of objects.

Realization:

Realization can be defined as a relationship in which two elements are connected. One
element describes some responsibility which is not implemented and the other one
implements them. This relationship exists in case of interfaces.

 Activity Outcomes:

UML Diagrams:
UML diagrams are the ultimate output of the entire discussion. All the elements,
relationships are used to make a complete UML diagram and the diagram represents a
system.
The visual effect of the UML diagram is the most important part of the entire process. All
the other elements are used to make it a complete one.

UML includes the following nine diagrams and the details are described in the following
chapters.
1. Class Diagram
2. Object Diagram
3. Use Case Diagram
4. Sequence Diagram

Page 13 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
5. Collaboration Diagram
6. Activity Diagram
7. Statechart Diagram
8. Deployment Diagram
9. Component Diagram

UML Architecture
Any real world system is used by different users. The users can be developers, testers,
business people, analysts and many more. So before designing a system the architecture is
made with different perspectives in mind. The most important part is to visualize the
system from different viewer’s perspective. The better we understand the better we make
the system.

UML plays an important role in defining different perspectives of a system. These

perspectives are:
 Design
 Implementation
 Process
 Deployment

Page 14 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
And the center is the Use Case view which connects all these four. A Use case represents
the functionality of the system. So the other perspectives are connected with use case.
 Design of a system consists of classes, interfaces and collaboration. UML
provides class diagram, object diagram to support this.
 Implementation defines the components assembled together to make a
complete physical system. UML component diagram is used to support
implementation perspective.
 Process defines the flow of the system. So the same elements as used in
Design are also used to support this perspective.
 Deployment represents the physical nodes of the system that forms the
hardware. UML deployment diagram is used to support this perspective.

UML Modeling Types

It is very important to distinguish between the UML model. Different diagrams are used
for different type of UML modeling. There are three important type of UML modelings:
Structural modeling:
Structural modeling captures the static features of a system. They consist of the
followings:
 Classes Diagrams
 Objects Diagrams
 Deployment Diagrams
 Package Diagrams
 Composite Structure Diagram
 Component Diagram

Structural model represents the framework for the system and this framework is the place
where all other components exist. So the class diagram, component diagram and
deployment diagrams are the part of structural modeling. They all represent the elements
and the mechanism to assemble them.

But the structural model never describes the dynamic behavior of the system. Class
diagram is the most widely used structural diagram.

Page 15 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
Behavioral Modeling:
Behavioral model describes the interaction in the system. It represents the interaction
among the structural diagrams. Behavioral modeling shows the dynamic nature of the
system. They consist of the following:
 Activity Diagrams
 Interaction Diagrams
 Use Case Diagrams

All the above show the dynamic sequence of flow in a system.

Architectural Modeling:
Architectural model represents the overall framework of the system. It contains both
structural and behavioral elements of the system. Architectural model can be defined as
the blue print of the entire system. Package diagram comes under architectural modeling.

UML Basic Notations

UML is popular for its diagrammatic notations. We all know that UML is for visualizing,
specifying, constructing and documenting the components of software and non-software
systems. Here the Visualization is the most important part which needs to be understood
and remembered by heart.

UML notations are the most important elements in modeling. Efficient and appropriate
use of notations is very important for making a complete and meaningful model. The
model is useless unless its purpose is depicted properly.

So learning notations should be emphasized from the very beginning. Different notations
are available for things and relationships. And the UML diagrams are made using the
notations of things and relationships. Extensibility is another important feature which
makes UML more powerful and flexible.

The chapter describes the UML Basic Notations in more details. This is just an extension
to the UML building block section I have discussed in previous chapter.

Structural Things:
Page 16 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
Graphical notations used in structural things are the most widely used in UML. These are
considered as the nouns of UML models. Following are the list of structural things.

 Classes
 Interface
 Collaboration
 Use case
 Active classes
 Components
 Nodes

Page 17 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
Class Notation:
UML class is represented by the diagram shown below. The diagram is divided into four
parts.
 The top section is used to name the class.
 The second one is used to show the attributes of the class.
 The third section is used to describe the operations performed by the class.
 The fourth section is optional to show any additional components.

Classes are used to represent objects. Objects can be anything having properties and
responsibility.

Object Notation:
The object is represented in the same way as the class. The only difference is the name
which is underlined as shown below.

Page 18 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
As object is the actual implementation of a class which is known as the instance of a
class. So it has the same usage as the class. Interface Notation:
Interface is represented by a circle as shown below. It has a name which is generally
written below the circle.

Interface is used to describe functionality without implementation. Interface is the just

like a template where you define different functions not the implementation. When a class
implements the interface it also implements the functionality as per the requirement.

Page 19 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
Collaboration Notation:
Collaboration is represented by a dotted eclipse as shown below. It has a name written
inside the eclipse.

Collaborati on
represents responsibilities. Generally responsibilities are in a group.

Page 20 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
Use case Notation:
Use case is represented as an eclipse with a name inside it. It may contain additional
responsibilities.

Page 21 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
Use case is used to capture high level functionalities of a system.
Actor Notation:
An actor can be defined as some internal or external entity that interacts with the system.

Actor is used in a use case diagram to describe the internal or external entities.

Initial State Notation:

Initial state is defined to show the start of a process. This notation is used in almost all
diagrams.

The usage of Initial State Notation is to show the starting point of a process.

Page 22 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
Final State Notation:

Final state is used to show the end of a process. This notation is also used in almost all
diagrams to describe the end.

The usage of Final State Notation is to show the termination point of a process.

Active class Notation:

Active class looks similar to a class with a solid border. Active class is generally used to
describe concurrent behaviour of a system.

Active class is used to represent concurrency in a system.

Page 23 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
Component Notation:
A component in UML is shown as below with a name inside. Additional elements can be
added wherever required.

Component is used to represent any part of a system for which UML diagrams are made.

Node Notation:
A node in UML is represented by a square box as shown below with a name. A node
represents a physical component of the system.

Node is used to represent physical part of a system like server, network etc.

Page 24 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
Behavioural Things:
Dynamic parts are one of the most important elements in UML. UML has a set of
powerful features to represent the dynamic part of software and non software systems.
These features include interactions and state machines.
Interactions can be of two types:
 Sequential (Represented by sequence diagram)
 Collaborative (Represented by collaboration diagram)

Interaction Notation:
Interaction is basically message exchange between two UML components. The following
diagram represents different notations used in an interaction.

Page 25 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
Interaction is used to represent communication among the components of a system.

State machine Notation:

State machine describes the different states of a component in its life cycle. The notations
are described in the following diagram.

State machine is used to describe different states of a system component. The state can be
active, idle or any other depending upon the situation.

Page 26 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
Grouping Things:

Organizing the UML models are one of the most important aspects of the design. In UML
there is only one element available for grouping and that is package.

Package Notation:

Package notation is shown below and this is used to wrap the components of a system.

Page 27 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
Annotational Things:
In any diagram explanation of different elements and their functionalities are very
important. So UML has notes notation to support this requirement.

Note Notation:
This notation is shown below and they are used to provide necessary information of a
system.

Relationships
A model is not complete unless the relationships between elements are described
properly. The Relationship gives a proper meaning to an UML model. Following are the
different types of relationships available in UML.
 Dependency
 Association
 Generalization
 Extensibility

Dependency Notation:
Dependency is an important aspect in UML elements. It describes the dependent elements
and the direction of dependency.

Dependency is represented by a dotted arrow as shown below. The arrow head represents
the independent element and the other end the dependent element.

Page 28 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
Dependency is used to represent dependency between two elements of a system.

Association Notation:
Association describes how the elements in an UML diagram are associated. In simple
word it describes how many elements are taking part in an interaction.

Association is represented by a dotted line with (without) arrows on both sides. The two
ends represent two associated elements as shown below. The multiplicity is also
mentioned at the ends (1, * etc) to show how many objects are associated.

Association is used to represent the relationship between two elements of a system.

Generalization Notation:
Generalization describes the inheritance relationship of the object oriented world. It is
parent and child relationship.

Generalization is represented by an arrow with hollow arrow head as shown below. One
end represents the parent element and the other end child element.

Page 29 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
Generalization is used to describe parent-child relationship of two elements of a system.
Extensibility Notation:
All the languages (programming or modeling) have some mechanism to extend its
capabilities like syntax, semantics etc. UML is also having the following mechanisms to
provide extensibility features.
 Stereotypes (Represents new elements)
 Tagged values (Represents new attributes)
 Constraints (Represents the boundaries)

Extensibility notations are used to enhance the power of the language. It is basically
additional elements used to represent some extra behaviour of the system. These extra
behaviours are not covered by the standard available notations.

Page 30 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
UML Standard Diagrams

In the previous chapters we have discussed about the building blocks and other necessary
elements of UML. Now we need to understand where to use those elements.

The elements are like components which can be associated in different ways to make a
complete UML pictures which is known as diagram. So it is very important to understand
the different diagrams to implement the knowledge in real life systems.

Any complex system is best understood by making some kind of diagrams or pictures.
These diagrams have a better impact on our understanding. So if we look around then we
will realize that the diagrams are not a new concept but it is used widely in different form
in different industries.

We prepare UML diagrams to understand a system in better and simple way. A single
diagram is not enough to cover all aspects of the system. So UML defines various kinds
of diagrams to cover most of the aspects of a system.

You can also create your own set of diagrams to meet your requirements. Diagrams are
generally made in an incremental and iterative way.
There are two broad categories of diagrams and then are again divided into sub-
categories:
 Behavioral Diagrams
 Structural Diagrams

Behavioral Diagrams:
Any system can have two aspects, static and dynamic. So a model is considered as
complete when both the aspects are covered fully.

Behavioral diagrams basically capture the dynamic aspect of a system. Dynamic aspect
can be further described as the changing/moving parts of a system.

Page 31 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
UML has the following five types of behavioral diagrams:
 Use Case Diagram
 Sequence Diagram
 Collaboration Diagram
 Statechart Diagram
 Activity Diagram

Use case Diagram:

Use case diagrams are a set of use cases, actors and their relationships. They represent the
use case view of a system.

A use case represents a particular functionality of a system.

So use case diagram is used to describe the relationships among the functionalities and
their internal/external controllers. These controllers are known as actors.

Sequence Diagram:
A sequence diagram is an interaction diagram. From the name it is clear that the diagram
deals with some sequences, which are the sequence of messages flowing from one object
to another.

Interaction among the components of a system is very important from implementation

and execution perspective.

So Sequence diagram is used to visualize the sequence of calls in a system to perform a

specific functionality.

Page 32 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
Collaboration Diagram:
Collaboration diagram is another form of interaction diagram. It represents the structural
organization of a system and the messages sent/received. Structural organization consists
of objects and links.

The purpose of collaboration diagram is similar to sequence diagram. But the specific
purpose of collaboration diagram is to visualize the organization of objects and their
interaction.

Statechart Diagram:
Any real time system is expected to be reacted by some kind of internal/external events.
These events are responsible for state change of the system.

Statechart diagram is used to represent the event driven state change of a system. It
basically describes the state change of a class, interface etc.

State chart diagram is used to visualize the reaction of a system by internal/external

factors.

Activity Diagram:
Activity diagram describes the flow of control in a system. So it consists of activities and
links. The flow can be sequential, concurrent or branched.

Activities are nothing but the functions of a system. Numbers of activity diagrams are
prepared to capture the entire flow in a system.

Activity diagrams are used to visualize the flow of controls in a system. This is prepared
to have an idea of how the system will work when executed.

Note: Dynamic nature of a system is very difficult to capture. So UML has provided
features to capture the dynamics of a system from different angles. Sequence diagrams
and collaboration diagrams are isomorphic so they can be converted from one another
without losing any information. This is also true for statechart and activity diagram.

Page 33 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
Structural Diagrams:
The structural diagrams represent the static aspect of the system. These static aspects
represent those parts of a diagram which forms the main structure and therefore stable.

These static parts are represents by classes, interfaces, objects, components and nodes.
The four structural diagrams are:
 Class diagram
 Object diagram
 Component diagram
 Deployment diagram

Class Diagram:
Class diagrams are the most common diagrams used in UML. Class diagram consists of
classes, interfaces, associations and collaboration.

Class diagrams basically represent the object oriented view of a system which is static in
nature.

Active class is used in a class diagram to represent the concurrency of the system.

Class diagram represents the object orientation of a system. So it is generally used for
development purpose. This is the most widely used diagram at the time of system
construction.

Object Diagram:
Object diagrams can be described as an instance of class diagram. So these diagrams are
more close to real life scenarios where we implement a system.

Object diagrams are a set of objects and their relationships just like class diagrams and
also represent the static view of the system.

The usage of object diagrams is similar to class diagrams but they are used to build
prototype of a system from practical perspective.
Component Diagram:

Page 34 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
Component diagrams represent a set of components and their relationships. These
components consist of classes, interfaces or collaborations.

So Component diagrams represent the implementation view of a system.

During design phase software artifacts (classes, interfaces etc) of a system are arranged in
different groups depending upon their relationship. Now these groups are known as
components.

Finally, component diagrams are used to visualize the implementation.

Deployment Diagram:
Deployment diagrams are a set of nodes and their relationships. These nodes are physical
entities where the components are deployed.
Deployment diagrams are used for visualizing deployment view of a system. This is
generally used by the deployment team.
Note: If the above descriptions and usages are observed carefully then it is very clear
that all the diagrams are having some relationship with one another. Component
diagrams are dependent upon the classes, interfaces etc which are part of class/object
diagram. Again the deployment diagram is dependent upon the components which are
used to make a component diagrams.
Realization:
Realization can be defined as a relationship in which two elements are connected. One
element describes some responsibility which is not implemented and the other one
implements them. This relationship exists in case of interfaces.

(3) UML Diagrams:

UML diagrams are the ultimate output of the entire discussion. All the elements,
relationships are used to make a complete UML diagram and the diagram represents a
system.

The visual effect of the UML diagram is the most important part of the entire process.
All the other elements are used to make it a complete one.

UML includes the following nine diagrams and the details are described in the
following chapters.

Page 35 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
1. Class Diagram
2. Object Diagram
3. Use Case Diagram
4. Sequence Diagram
5. Collaboration Diagram
6. Activity Diagram
7. Statechart Diagram
8. Deployment Diagram
9. Component Diagram

UML Architecture
Any real world system is used by different users. The users can be developers, testers,
business people, analysts and many more. So before designing a system the
architecture is made with different perspectives in mind. The most important part is to
visualize the system from different viewer’s perspective. The better we understand the
better we make the system.
UML plays an important role in defining different perspectives of a system. These
perspectives are:
 Design
 Implementation
 Process
 Deployment

Page 36 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 Exercise 4 (Week 6 and Week 7)

Title of the Exercise: Introduction to Rational Rose Software

 Activity Outcomes:
Visual Modeling:
 Visual modeling is the process of graphically depicting the system to be
developed.
 Visual modeling allows you to present essential details of a complex
problem and filter out the nonessential details.
 It also provides a mechanism for viewing the system to be developed from
different perspectives.
 ROSE = Rational Object Oriented Software Engineering
 Rational Rose includes tools for reverse engineering as well as forward
engineering of classes and component architectures.
 You can gain valuable insights to your actual constructed architecture and
pinpoint deviations from the original design.
 Rose offers a fast way for clients and new employees to become familiar
with system internals
 Rational Rose helps the documents of the diagram as diagram is generated
and as per designer's request code is generated in VB, C++, Java.
 Rose can be extended and supports add ins like COM/DCOM, JavaBeans,
and CORBA (Common Object Request Broker Architecture).

Page 37 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
Rational Rose INTERFACE

Tool Bar to Class Diagram

Drag and Drop over the diagram canvas

Page 38 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 Page 39 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
Diagrams
Various types of diagram in Rational Rose

Page 40 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
Different Types of Views in Rose

Page 41 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 Page 42 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 Exercise 5 (Week 8 and Week 9)

Title of the Exercise: Use case Diagram: to perform the user’s view
analysis
 Objectives / Statement Purpose:
 To model a system the most important aspect is to capture the dynamic
behavior. To clarify a bit in details, dynamic behavior means the behavior
of the system when it is running /operating.
 So only static behavior is not sufficient to model a system rather dynamic
behavior is more important than static behavior. In UML there are five
diagrams available to model dynamic nature and use case diagram is one
of them. Now as we have to discuss that the use case diagram is dynamic
in nature there should be some internal or external factors for making the
interaction.
 These internal and external agents are known as actors. So use case
diagrams are consists of actors, use cases and their relationships. The
diagram is used to model the system/subsystem of an application. A single
use case diagram captures a particular functionality of a system.
 So to model the entire system numbers of use case diagrams are used.

Purpose:
 The purpose of use case diagram is to capture the dynamic aspect of a
system. But this definition is too generic to describe the purpose.
 Because other four diagrams (activity, sequence, collaboration and State
chart) are also having the same purpose. So we will look into some
specific purpose which will distinguish it from other four diagrams.
 Use case diagrams are used to gather the requirements of a system
including internal and external influences. These requirements are mostly
design requirements. So when a system is analyzed to gather its
functionalities use cases are prepared and actors are identified.

Page 43 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
  Now when the initial task is complete use case diagrams are modelled to
present the outside view.
 So in brief, the purposes of use case diagrams can be as follows:

 Activity Outcomes:
 Use case diagrams are considered for high level requirement analysis of a
system. So when the requirements of a system are analyzed the
functionalities are captured in use cases.
 So we can say that uses cases are nothing but the system functionalities
written in an organized manner. Now the second things which are relevant
to the use cases are the actors. Actors can be defined as something that
interacts with the system.
 The actors can be human user, some internal applications or may be some
external applications. So in a brief when we are planning to draw an use
case diagram we should have the following items identified.

 Use case diagrams are drawn to capture the functional requirements of a

system. So after identifying the above items we have to follow the
following guidelines to draw an efficient use case diagram.

in such a way so that it can identify the functionalities performed.

purpose of the diagram is to identify requirements.

 The following is a sample use case diagram representing the order

management system. So if we look into the diagram then we will find three

Page 44 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 use cases (Order, SpecialOrder and NormalOrder) and one actor which is
customer.
 The SpecialOrder and NormalOrder use cases are extended from Order
use case. So they have extends relationship. Another important point is to
identify the system boundary which is shown in the picture. The actor
Customer lies outside the system as it is an external user of the system.

 Instructions for solving problems :

1. As we have already discussed there are five diagrams in UML to model dynamic view
of a system. Now each and every model has some specific purpose to use. Actually these
specific purposes are different angles of a running system.

2. So to understand the dynamics of a system we need to use different types of diagrams.

Use case diagram is one of them and its specific purpose is to gather system requirements
and actors.
3. Use case diagrams specify the events of a system and their flows. But use case diagram
never describes how they are implemented. Use case diagram can be imagined as a black
box where only the input, output and the function of the black box is known.

Page 45 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
4. These diagrams are used at a very high level of design. Then this high level design is
refined again and again to get a complete and practical picture of the system. A well
structured use case also describes the pre condition, post condition, exceptions. And these
extra elements are used to make test cases when performing the testing.

5. Although the use cases are not a good candidate for forward and reverse engineering
but still they are used in a slight different way to make forward and reverse engineering.
And the same is true for reverse engineering. Still use case diagram is used differently to
make it a candidate for reverse engineering.

6. In forward engineering use case diagrams are used to make test cases and in reverse
engineering use cases are used to prepare the requirement details from the existing
application.
So the following are the places where use case diagrams are used:
Requirement analysis and high level design.
Model the context of a system.
Reverse engineering.
Forward engineering.

 Exercises (To be solved in Classroom):

 PROBLEM STATEMENT
At the beginning of each semester students may request a course catalogue containing
a list of course offerings for the semester. Information about each course, such as
professor, department, and prerequisites will be included to help students make
informed decisions. The new on-line registration system will allow students to select
four course offerings for the coming semester. In addition, each student will indicate
two alternative choices in case a course offering becomes filled or canceled. No
course offering will have more than ten students. No course offering will have fewer
than three students. A course offering with fewer than three students will be canceled.
Once the registration process is completed for a student, the registration system sends
information to the billing system, so the student can be billed for the semester. This
system is designed in such a way that Professors must be able to access the on-line
system to indicate which courses they will be teaching. They will also need to see
which students signed up for their course offering. For each semester, there is a period
of time that students can change their schedules. Students must be able to access the
Page 46 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 on-line system during this time to add or drop courses. The billing system will credit
all students for courses dropped during this period of time.’

Definition of Actors
 The following actors will be used in the Use Case Diagrams and the various roles in
which they play are explained.
Student: someone who is registered to take courses at the College.
Professor: someone who is licensed to teach at the College.
Registrar: someone who is responsible for the maintenance of the Registration
System.
Billing System: external system that bills students with respect to course enrolled
for per semester.

Definition of Use Cases

 The following use cases were elaborated for each actor, the Use cases are represented
in bold types.

o Register for courses

o Select courses to teach

o Request course offering roster

o Generate course catalogue.

o Maintain professor information.
o Maintain student information.
o Maintain curriculum

 Drawing Use Case Diagram

The Use Case diagram shown below illustrates the various actions taken by all of the
four (4) Actors during registration of course by student(s). These include the

Page 47 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
registrations of course by the student(s) to request for class roaster by Professors to
the Maintenance of both Prof. and student Information in the database. In the diagram,
the Actors are presented as Stickmen while the Use Cases are presented in round Oval
Shapes. This is show in figure II below:

 Exercises (To be solved in Classroom):

 Task 1
Using the following specification and Draw the Use case diagram: to
perform the user’s view analysis.
 Purpose: Domain model for a hospital to show and explain hospital
structure, staff, relationships with patients, and patient treatment
terminology.

Page 48 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
  Summary: The domain model for the Hospital Management System is
represented by several class diagrams.

 Ward is a division of a hospital or a suite of rooms shared by patients who need

a similar kind of care. In a hospital, there are a number of wards, each of which
may be empty or have on it one or more patients. Each ward has a unique
name.

 The doctors in the hospital are organized into teams (also called firms). Each
team has a unique name or code (e.g. Orthopedics or Pediatrics) and is headed
by a consultant doctor or an attending physician.

 Task 2
 Draw the Uses Case Diagram which deals with the Railway Reservation
System using the given specification.

 Railway Reservation System is a system used for booking tickets over internet.
Any Customer Can book tickets for different trains. Customer can book a ticket
only if the tickets are available. Customer searches for the availability of tickets
then if the tickets are available he books the tickets by initially filling details in a
form. Tickets can be booked in two ways by i-ticket or by e-ticket booking.
 In case of i-ticket booking customer can book the tickets online and the tickets
are couriered to Particular customer at their address. But in case of e-ticket
booking and cancelling tickets are booked and cancelled online sitting at the
home and customer himself has to take print of the ticket but in both the cases
amount for tickets are deducted from customers account .
 For cancellation of ticket the customer has to go at reservation office than fill
cancellation form and ask the clerk to cancel the ticket than the refund is
transferred to customer account. After booking ticket the customer has to
checkout by paying fare amount to clerk.

 Task 3
 Using the following specification and Draw the Use case diagram:
to perform the user’s view analysis.

The Online Library System provides online real time information about the books
available in the Library and the user information. The Product functions are more or
Page 49 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
less the same as described in the product perspective. The functions of the system
include the system providing different type of services based on the type of users
[Member/Librarian].

 The member should be provided with the updated information about the books
catalog.
 Provisions for the members to borrow the books they want, if all the other
required rules hold good.
 The member is given a provision to check his account information and change
the account information any time in the given valid period.
 The members are provided with the books available roster and allowed to
choose the books, which they want to use in the coming up days.
 The librarian can get the information about the members who have borrowed
or returned the books.
 The librarian is provided with interfaces to add/delete the books available in
the book catalog.
 The members when complete the book borrowing or returning process, the due
to be paid by the member must be calculated and the information about the
member and the due amount is sent to the university billing system.
 The system uses the University information security requirements to provide
the login facility to the users.

 Exercises for practice at home(Assignment):

Consider the following specification and Draw the Use case diagram: to
perform the user’s view analysis which corresponds to the above
specification.
 A video store has a stock of movies and video games for rent. It is
important to keep track of each movie title to know and to identify its
category (classical, drama, comedy, and so on), its rental type (new
release, standard), movie rating, and other general information such as
movie producer, release date, cost, and so forth. In addition to tracking
each title, the business must track each individual copy to note its
purchase date, its condition, and its rental status. User functions must be
provided to maintain this inventory information .

 Customers, the lifeblood of the business, are also tracked. The video store
system considers each family to be a customer, so special mailings and
Page 50 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 promotions are offered to each household. For any given customer,
several people may be authorized to rent videos and games. The primary
contact for each customer can also establish rental parameters for other
members of the household.

 Each time a movie is rented, the system must keep track of which copies
of which movies and games are rented; the rental date and time and the
return date and time; and the household and person renting the movie.
Each rental is considered to be open until all of the movies and games
have been returned. Customers pay for rentals when checking out videos
at the store.

Page 51 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 Exercise 6 (Week 10 and Week 11)
Title of the Exercise: Interaction Diagram (Sequence and
Collaboration Diagrams): to draw the behavioral view diagram

 Objectives / Statement Purpose:

 From the name Interaction it is clear that the diagram is used to describe
some type of interactions among the different elements in the model. So
this interaction is a part of dynamic behavior of the system.
 This interactive behavior is represented in UML by two diagrams known
as Sequence diagram and Collaboration diagram. The basic purposes of
both the diagrams are similar.
 Sequence diagram emphasizes on time sequence of messages and
collaboration diagram emphasizes on the structural organization of the
objects that send and receive messages.
Purpose:
 The purposes of interaction diagrams are to visualize the interactive behaviour
of the system. Now visualizing interaction is a difficult task. So the solution is
to use different types of models to capture the different aspects of the
interaction.
 That is why sequence and collaboration diagrams are used to capture dynamic
nature but from a different angle.
 So the purposes of interaction diagram can be describes as:
 To capture dynamic behaviour of a system.
 To describe the message flow in the system.
 To describe structural organization of the objects.
 To describe interaction among objects.

 Activity Outcomes:
 As we have already discussed that the purpose of interaction diagrams are to
capture the dynamic aspect of a system. So to capture the dynamic aspect we need
to understand what a dynamic aspect is and how it is visualized. Dynamic aspect
can be defined as the snap shot of the running system at a particular moment.

Page 52 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 We have two types of interaction diagrams in UML. One is sequence diagram and
the other is a collaboration diagram. The sequence diagram captures the time
sequence of message flow from one object to another and the collaboration
diagram describes the organization of objects in a system taking part in the
message flow.

Page 53 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
  So the following things are to identified clearly before drawing the
interaction diagram:
 Objects taking part in the interaction.
 Message flows among the objects.
 The sequence in which the messages are flowing.
 Object organization.

 Following are two interaction diagrams modeling order management system.

The first diagram is a sequence diagram and the second is a collaboration
diagram.

 Instructions for solving problems :

 We have already discussed that interaction diagrams are used to describe
dynamic nature of a system. Now we will look into the practical scenarios
where these diagrams are used. To understand the practical application we
need to understand the basic nature of sequence and collaboration diagram.
 The main purposes of both the diagrams are similar as they are used to
capture the dynamic behaviour of a system. But the specific purposes are
more important to clarify and understood.
 Sequence diagrams are used to capture the order of messages flowing from
one object to another. And the collaboration diagrams are used to describe the
structural organizations of the objects taking part in the interaction. A single
diagram is not sufficient to describe the dynamic aspect of an entire system so
a set of diagrams are used to capture is as a whole.
 The interaction diagrams are used when we want to understand the message
flow and the structural organization. Now message flow means the sequence
of control flow from one object to another and structural organization means
the visual organization of the elements in a system.
 In a brief the following are the usages of interaction diagrams:
To model flow of control by time sequence.
To model flow of control by structural organizations.
For forward engineering.
For reverse engineering.

Page 54 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
The Sequence Diagram:
 The sequence diagram is having four objects (Customer, Order, SpecialOrder and
NormalOrder).
 The following diagram has shown the message sequence for SpecialOrder object
and the same can be used in case of NormalOrder object. Now it is important to
understand the time sequence of message flows. The message flow is nothing but a
method call of an object.
 The first call is sendOrder () which is a method of Order object. The next call is
confirm () which is a method of SpecialOrder object and the last call is Dispatch ()
which is a method of SpecialOrder object. So here the diagram is mainly describing

Page 55 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 the method calls from one object to another and this is also the actual scenario when
the system is running.

 Exercises (To be solved in Classroom):

 Task 1
 Consider the following specification and Draw the Interaction Diagram
which corresponds to the given specification

The hotel reservation include following functionality:

 For the hotel guest – search available rooms – make a reservation (after
registration). Up to 2 reservations are possible for each guest – confirm
reservation – cancel reservation – pay through credit card or bank transfer

Page 56 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
  For the hotel manager – alter reservation list (remember to issue notice to the
future guests!) – Remove rooms (remember to alter reservation list!) – Add
rooms – change room details (remember to issue notice to the future guests!)
 For the system: – maintain list of rooms and reservations in the database –
interact with external payment system for guest payments – apply discounts
for long stays, unpopular periods of the year and for VIPs.

 Task 2
 Draw the Sequence and Collaboration Diagrams which deals with the
Railway Reservation System Using the given specification.

 Railway Reservation System is a system used for booking tickets over internet.
Any Customer Can book tickets for different trains. Customer can book a ticket
only if the tickets are available. Customer searches for the availability of tickets
then if the tickets are available he books the tickets by initially filling details in a
form. Tickets can be booked in two ways by i-ticket or by e-ticket booking.
 In case of i-ticket booking customer can book the tickets online and the tickets
are couriered to Particular customer at their address. But in case of e-ticket
booking and cancelling tickets are booked and cancelled online sitting at the
home and customer himself has to take print of the ticket but in both the cases
amount for tickets are deducted from customers account .
 For cancellation of ticket the customer has to go at reservation office than fill
cancellation form and ask the clerk to cancel the ticket than the refund is
transferred to customer account. After booking ticket the customer has to
checkout by paying fare amount to clerk.

 Task 3

 Using The Following Specification and Draw the Student’s

Registration Sequence Diagram and Collaboration Diagrams.

Page 57 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
  The second interaction diagram is collaboration diagram. It shows the object
organization as shown below. Here in collaboration diagram the method call
sequence is indicated by some numbering technique as shown below. The number
indicates how the methods are called one after another. We have taken the same
order management system to describe the collaboration diagram.
 The method calls are similar to that of a sequence diagram. But the difference is that
the sequence diagram does not describe the object organization where as the
collaboration diagram shows the object organization.
 Now to choose between these two diagrams the main emphasis is given on the type
of requirement. If the time sequence is important then sequence diagram is used and
if organization is required then collaboration diagram is used.

 Exercises for practice at home(Assignment):

 Consider the following specification Draw the Interaction

Diagram (Sequence and Collaboration Diagrams) : to draw the
behavioral view diagram

The Online Library System provides online real time information about the books
available in the Library and the user information. The Product functions are more or
less the same as described in the product perspective. The functions of the system
include the system providing different type of services based on the type of users
[Member/Librarian].

 The member should be provided with the updated information about the
books catalog.
 Provisions for the members to borrow the books they want, if all the other
required rules hold good.
 The member is given a provision to check his account information and
change the account information any time in the given valid period.
 The members are provided with the books available roster and allowed to
choose the books, which they want to use in the coming up days.

Page 58 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 The librarian can get the information about the members who have borrowed
or returned the books.
 The librarian is provided with interfaces to add/delete the books available in
the book catalog.
 The members when complete the book borrowing or returning process, the
due to be paid by the member must be calculated and the information about
the member and the due amount is sent to the university billing system.
 The system uses the University information security requirements to provide
the login facility to the users.

Page 59 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 Exercise 7 (Week 12)
Title of the Exercise: State chart and Activity diagrams: to draw the
behavioral view diagram
 Objectives / Statement Purpose:
 A Statechart diagram describes a state machine. Now to clarify it state machine
can be defined as a machine which defines different states of an object and these
states are controlled by external or internal events.
 Activity diagram explained in next chapter, is a special kind of a Statechart
diagram. As Statechart diagram defines states it is used to model lifetime of an
object.
 Purpose:
 Statechart diagram is one of the five UML diagrams used to model dynamic
nature of a system. They define different states of an object during its lifetime.
And these states are changed by events. So Statechart diagrams are useful to
model reactive systems. Reactive systems can be defined as a system that
responds to external or internal events.
 Statechart diagram describes the flow of control from one state to another state.
States are defined as a condition in which an object exists and it changes when
some event is triggered. So the most important purpose of Statechart diagram is to
model life time of an object from creation to termination.
 Statechart diagrams are also used for forward and reverse engineering of a system.
But the main purpose is to model reactive system.
 Following are the main purposes of using Statechart diagrams:
 To model dynamic aspect of a system.
 To model life time of a reactive system.
 To describe different states of an object during its life time.
 Define a state machine to model states of an object.

 UML Activity Diagram

Page 60 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
Activity diagram is another important diagram in UML to describe dynamic aspects
of the system.
Activity diagram is basically a flow chart to represent the flow form one activity to
another activity. The activity can be described as an operation of the system.
So the control flow is drawn from one operation to another. This flow can be
sequential, branched or concurrent. Activity diagrams deals with all type of flow
control by using different elements like fork, join etc.
Purpose:
The basic purposes of activity diagrams are similar to other four diagrams. It captures
the dynamic behaviour of the system. Other four diagrams are used to show the
message flow from one object to another but activity diagram is used to show
message flow from one activity to another.
Activity is a particular operation of the system. Activity diagrams are not only used
for visualizing dynamic nature of a system but they are also used to construct the
executable system by using forward and reverse engineering techniques. The only
missing thing in activity diagram is the message part.
It does not show any message flow from one activity to another. Activity diagram is
some time considered as the flow chart. Although the diagrams looks like a flow chart
but it is not. It shows different flow like parallel, branched, concurrent and single.
So the purposes can be described as:
 Draw the activity flow of a system.
 Describe the sequence from one activity to another.
 Describe the parallel, branched and concurrent flow of the system.

 Activity Outcomes:
 Statechart Diagrams:

Page 61 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 From the above discussion we can define the practical applications of a Statechart
diagram. Statechart diagrams are used to model dynamic aspect of a system like
other four diagrams disused in this tutorial. But it has some distinguishing
characteristics for modeling dynamic nature.
 Statechart diagram defines the states of a component and these state changes are
dynamic in nature. So its specific purpose is to define state changes triggered by
events. Events are internal or external factors influencing the system.
 Statechart diagrams are used to model states and also events operating on the
system. When implementing a system it is very important to clarify different
states of an object during its life time and statechart diagrams are used for this
purpose. When these states and events are identified they are used to model it and
these models are used during implementation of the system.
 If we look into the practical implementation of Statechart diagram then it is
mainly used to analyze the object states influenced by events. This analysis is
helpful to understand the system behaviour during its execution.
 So the main usages can be described as:
 To model object states of a system.
 To model reactive system. Reactive system consists of reactive objects.
 To identify events responsible for state changes.
 Forward and reverse engineering.

Page 62 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 Page 63 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 OutCome of Activity Diagram:
The basic usage of activity diagram is similar to other four UML diagrams. The
specific usage is to model the control flow from one activity to another. This control
flow does not include messages.
The activity diagram is suitable for modeling the activity flow of the system. An
application can have multiple systems. Activity diagram also captures these systems
and describes flow from one system to another. This specific usage is not available in
other diagrams. These systems can be database, external queues or any other system.
Now we will look into the practical applications of the activity diagram. From the
above discussion it is clear that an activity diagram is drawn from a very high level.
So it gives high level view of a system. This high level view is mainly for business
users or any other person who is not a technical person.
This diagram is used to model the activities which are nothing but business
requirements. So the diagram has more impact on business understanding rather
implementation details.
Following are the main usages of activity diagram:
 Modeling work flow by using activities.
 Modeling business requirements.
 High level understanding of the system's functionalities.
 Investigate business requirements at a later stage.

 Instructions for solving problems :

 Statechart Diagram:
 Statechart diagram is used to describe the states of different objects in its life
cycle. So the emphasis is given on the state changes upon some internal or
external events. These states of objects are important to analyze and implement
them accurately.

Page 64 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 Statechart diagrams are very important for describing the states. States can be
identified as the condition of objects when a particular event occurs.
 Before drawing a Statechart diagram we must have clarified the following points:
 Identify important objects to be analyzed.
 Identify the states.
 Identify the events.
 The following is an example of a Statechart diagram where the state of Order
object is analyzed.
 The first state is an idle state from where the process starts. The next states are
arrived for events like send request, confirm request, and dispatch order. These
events are responsible for state changes of order object.
 During the life cycle of an object (here order object) it goes through the following
states and there may be some abnormal exists also. This abnormal exit may occur
due to some problem in the system. When the entire life cycle is complete it is
considered as the complete transaction as mentioned below.
 The initial and final state of an object is also shown below.

 Instructions to draw Activity Diagram:

Activity diagrams are mainly used as a flow chart consists of activities performed by
the system. But activity diagram are not exactly a flow chart as they have some
additional capabilities. These additional capabilities include branching, parallel flow,
swimlane etc.
Before drawing an activity diagram we must have a clear understanding about the
elements used in activity diagram. The main element of an activity diagram is the
activity itself. An activity is a

Page 65 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
Function performed by the system. After identifying the activities we need to
understand how they are associated with constraints and conditions.
So before drawing an activity diagram we should identify the following elements:
 Activities
 Association
 Conditions
 Constraints

Once the above mentioned parameters are identified we need to make a mental layout
of the entire flow. This mental layout is then transformed into an activity diagram.
The following is an example of an activity diagram for order management system. In
the diagram four activities are identified which are associated with conditions. One
important point should be clearly understood that an activity diagram cannot be
exactly matched with the code. The activity diagram is made to understand the flow
of activities and mainly used by the business users.
The following diagram is drawn with the four main activities:
 Send order by the customer
 Receipt of the order
 Confirm order
 Dispatch order

After receiving the order request condition checks are performed to check if it is
normal or special order. After the type of order is identified dispatch activity is
performed and that is marked as the termination of the process.

Page 66 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 Exercises (To be solved in Classroom):
 Task 1
Using the following specification and Draw the State chart to perform the
user’s view analysis.

The hotel reservation include following functionality:

 For the hotel guest – search available rooms – make a reservation (after
registration). Up to 2 reservations are possible for each guest – confirm
reservation – cancel reservation – pay through credit card or bank transfer
 For the hotel manager – alter reservation list (remember to issue notice to the
future guests!) – Remove rooms (remember to alter reservation list!) – Add
rooms – change room details (remember to issue notice to the future guests!)

Page 67 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
  For the system: – maintain list of rooms and reservations in the database –
interact with external payment system for guest payments – apply discounts
for long stays, unpopular periods of the year and for VIPs.

 Task 2
Consider the following specification, Draw the State chart and Activity diagrams:
to draw the behavioral view diagram which corresponds to the above specification

 Purpose: Describe major services (functionality) provided by a hospital's

reception.
 Summary: Hospital Management System is a large system including
several subsystems or modules providing variety of functions. Hospital Reception
subsystem or module supports some of the many job duties of hospital
receptionist. Receptionist schedules patient's appointments and admission to the
hospital, collects information from patient upon patient's arrival and/or by
phone.
 For the patient that will stay in the hospital ("inpatient") she or he should have a
bed allotted in a ward. Receptionists might also receive patient's payments,
record them in a database and provide receipts, file insurance claims and medical
reports.

 Task 3
 Using the following specification and Draw the State chart
diagrams: to perform the user’s view analysis.
The Online Library System provides online real time information about the books
available in the Library and the user information. The Product functions are more or
less the same as described in the product perspective. The functions of the system
include the system providing different type of services based on the type of users
[Member/Librarian].

 The member should be provided with the updated information about the books
catalog.
 Provisions for the members to borrow the books they want, if all the other
required rules hold good.
Page 68 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
  The member is given a provision to check his account information and change
the account information any time in the given valid period.
 The members are provided with the books available roster and allowed to
choose the books, which they want to use in the coming up days.
 The librarian can get the information about the members who have borrowed
or returned the books.
 The librarian is provided with interfaces to add/delete the books available in
the book catalog.
 The members when complete the book borrowing or returning process, the due
to be paid by the member must be calculated and the information about the
member and the due amount is sent to the university billing system.
 The system uses the University information security requirements to provide
the login facility to the users.

 Exercises for practice at home(Assignment):

Consider the following specification and Draw the State chart diagram to
represent the above specification.
 A video store has a stock of movies and video games for rent. It is
important to keep track of each movie title to know and to identify its
category (classical, drama, comedy, and so on), its rental type (new
release, standard), movie rating, and other general information such as
movie producer, release date, cost, and so forth. In addition to tracking
each title, the business must track each individual copy to note its
purchase date, its condition, and its rental status. User functions must be
provided to maintain this inventory information .

 Customers, the lifeblood of the business, are also tracked. The video store
system considers each family to be a customer, so special mailings and
promotions are offered to each household. For any given customer,
several people may be authorized to rent videos and games. The primary
contact for each customer can also establish rental parameters for other
members of the household.

 Each time a movie is rented, the system must keep track of which copies
of which movies and games are rented; the rental date and time and the
return date and time; and the household and person renting the movie.
Each rental is considered to be open until all of the movies and games
have been returned. Customers pay for rentals when checking out videos
at the store.

Page 69 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 Exercise 8 (Week 13)
Title of the Exercise: Class and Object Diagrams: to draw the
structural view diagram

 Objectives / Statement Purpose:

 UML Class Diagram
 The class diagram is a static diagram. It represents the static view of an application.
Class diagram is not only used for visualizing, describing and documenting different
aspects of a system but also for constructing executable code of the software
application.
 The class diagram describes the attributes and operations of a class and also the
constraints imposed on the system. The class diagrams are widely used in the
modelling of object oriented systems because they are the only UML diagrams which
can be mapped directly with object oriented languages.
 The class diagram shows a collection of classes, interfaces, associations,
collaborations and constraints. It is also known as a structural diagram.
 Purpose:
 The purpose of the class diagram is to model the static view of an application. The
class diagrams are the only diagrams which can be directly mapped with object
oriented languages and thus widely used at the time of construction.
 The UML diagrams like activity diagram, sequence diagram can only give the
sequence flow of the application but class diagram is a bit different. So it is the most
popular UML diagram in the coder community.
 So the purpose of the class diagram can be summarized as:
 Analysis and design of the static view of an application.
 Describe responsibilities of a system.
 Base for component and deployment diagrams.
 Forward and reverse engineering.

Page 70 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 UML Object Diagram
 Object diagrams are derived from class diagrams so object diagrams are dependent
upon class diagrams.
 Object diagrams represent an instance of a class diagram. The basic concepts are
similar for class diagrams and object diagrams. Object diagrams also represent the
static view of a system but this static view is a snapshot of the system at a particular
moment.
 Object diagrams are used to render a set of objects and their relationships as an
instance.
 Purpose:
 The purpose of a diagram should be understood clearly to implement it practically.
The purposes of object diagrams are similar to class diagrams.
 The difference is that a class diagram represents an abstract model consisting of
classes and their relationships. But an object diagram represents an instance at a
particular moment which is concrete in nature.
 It means the object diagram is more close to the actual system behaviour. The purpose
is to capture the static view of a system at a particular moment.
 So the purpose of the object diagram can be summarized as:
 Forward and reverse engineering.
 Object relationships of a system
 Static view of an interaction.
 Understand object behaviour and their relationship from practical perspective

 Activity Outcomes:
 Class diagrams are the most popular UML diagrams used for construction of software
applications. So it is very important to learn the drawing procedure of class diagram.
 Class diagrams have lot of properties to consider while drawing but here the diagram
will be considered from a top level view.
 Class diagram is basically a graphical representation of the static view of the system
and represents different aspects of the application. So a collection of class diagrams
represent the whole system.

Page 71 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 The following points should be remembered while drawing a class diagram:
 The name of the class diagram should be meaningful to describe the aspect
of the system.
 Each element and their relationships should be identified in advance.
 Responsibility (attributes and methods) of each class should be clearly
identified.
 For each class minimum number of properties should be specified.
Because unnecessary properties will make the diagram complicated.
 Use notes when ever required to describe some aspect of the diagram.
Because at the end of the drawing it should be understandable to the
developer/coder.
 Finally, before making the final version, the diagram should be drawn on
plain paper and rework as many times as possible to make it correct.
 Now the following diagram is an example of an Order System of an application. So it
describes a particular aspect of the entire application.
 First of all Order and Customer are identified as the two elements of
the system and they have a one to many relationship because a
customer can have multiple orders.
 We would keep Order class is an abstract class and it has two concrete
classes (inheritance relationship) SpecialOrder and NormalOrder.
 The two inherited classes have all the properties as the Order class. In
addition they have additional functions like dispatch () and receive ().

 So the following class diagram has been drawn considering all the points mentioned
above:

Page 72 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
  Drawing Object Diagram: Activity Outcomes:
 We have already discussed that an object diagram is an instance of a class diagram. It
implies that an object diagram consists of instances of things used in a class diagram.
 So both diagrams are made of same basic elements but in different form. In class
diagram elements are in abstract form to represent the blue print and in object diagram
the elements are in concrete form to represent the real world object.
 To capture a particular system, numbers of class diagrams are limited. But if we
consider object diagrams then we can have unlimited number of instances which are
unique in nature. So only those instances are considered which are having impact on
the system.

Page 73 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 From the above discussion it is clear that a single object diagram cannot capture all
the necessary instances or rather cannot specify all objects of a system. So the
solution is:
 First, analyze the system and decide which instances are having important data
and association.
 Second, consider only those instances which will cover the functionality.
 Third, make some optimization as the numbers of instances are unlimited.

 Before drawing an object diagrams the following things should be remembered and
understood clearly:
 Object diagrams are consist of objects.
 The link in object diagram is used to connect objects.
 Objects and links are the two elements used to construct an object
diagram.

 Now after this the following things are to be decided before starting the construction
of the diagram:
 The object diagram should have a meaningful name to indicate its purpose.
 The most important elements are to be identified.
 The association among objects should be clarified.
 Values of different elements need to be captured to include in the object
diagram.
 Add proper notes at points where more clarity is required.

 The following diagram is an example of an object diagram. It represents the Order

management system which we have discussed in Class Diagram. The following
diagram is an instance of the system at a particular time of purchase. It has the
following objects
 Customer
 Order
 SpecialOrder
 NormalOrder

Page 74 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 Now the customer object (C) is associated with three order objects (O1, O2 and O3).
These order objects are associated with special order and normal order objects (S1, S2
and N1). The customer is having the following three orders with different numbers
(12, 32 and 40) for the particular time considered.
 Now the customer can increase number of orders in future and in that scenario the
object diagram will reflect that. If order, special order and normal order objects are
observed then we you will find that they are having some values.
 For orders the values are 12, 32, and 40 which implies that the objects are having
these values for the particular moment (here the particular time when the purchase is
made is considered as the moment) when the instance is captured.
 The same is for special order and normal order objects which are having number of
orders as 20, 30 and 60. If a different time of purchase is considered then these values
will change accordingly.
 So the following object diagram has been drawn considering all the points mentioned
above:

Page 75 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
  Instructions for solving problems :Class Diagrams:
 Class diagram is a static diagram and it is used to model static view of a system. The
static view describes the vocabulary of the system.
 Class diagram is also considered as the foundation for component and deployment
diagrams. Class diagrams are not only used to visualize the static view of the system
but they are also used to construct the executable code for forward and reverse
engineering of any system.
 Generally UML diagrams are not directly mapped with any object oriented
programming languages but the class diagram is an exception.
 Class diagram clearly shows the mapping with object oriented languages like Java,
C++ etc. So from practical experience class diagram is generally used for construction
purpose.
 So in a brief, class diagrams are used for:
 Describing the static view of the system.
 Showing the collaboration among the elements of the static view.
 Describing the functionalities performed by the system.
 Construction of software applications using object oriented languages.

Instructions to solve Object Diagrams:

 Object diagrams can be imagined as the snapshot of a running system at a particular
moment. Now to clarify it we can take an example of a running train.
 Now if you take a snap of the running train then you will find a static picture of it
having the following:
 A particular state which is running
 A particular number of passengers. Which will change if the snap is taken in a
different time.
 So here we can imagine the snap of the running train is an object having the above
values. And this is true for any real life simple or complex system. In a brief, object
diagrams are used for:
 Making the prototype of a system.
 Reverse engineering.
 Modeling complex data structures.
 Understanding the system from practical perspective.
Page 76 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 Exercises (To be solved in Classroom):
 Consider the following specification,
 Railway Reservation System is a system used for booking tickets over internet.
Any Customer Can book tickets for different trains. Customer can book a ticket
only if the tickets are available. Customer searches for the availability of tickets
then if the tickets are available he books the tickets by initially filling details in a
form. Tickets can be booked in two ways by i-ticket or by e-ticket booking.
 In case of i-ticket booking customer can book the tickets online and the tickets
are couriered to Particular customer at their address. But in case of e-ticket
booking and cancelling tickets are booked and cancelled online sitting at the
home and customer himself has to take print of the ticket but in both the cases
amount for tickets are deducted from customers account .
 For cancellation of ticket the customer has to go at reservation office than fill
cancellation form and ask the clerk to cancel the ticket than the refund is
transferred to customer account. After booking ticket the customer has to
checkout by paying fare amount to clerk.

Page 77 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 Task 1
 Draw the Class Diagram which deals with the Railway Reservation System
using the above specification.

 Task 2
Draw the Object Diagram which deals with the Ticket Booking Module only.

 Task 3
Draw the Class and Object Diagrams using the following specification of the
hotel reservation.

 For the hotel guest – search available rooms – make a reservation (after
registration). Up to 2 reservations are possible for each guest – confirm
reservation – cancel reservation – pay through credit card or bank transfer

 For the hotel manager – alter reservation list (remember to issue notice to the
future guests!) – Remove rooms (remember to alter reservation list!) – Add
rooms – change room details (remember to issue notice to the future guests!)
 For the system: – maintain list of rooms and reservations in the database –
interact with external payment system for guest payments – apply discounts
for long stays, unpopular periods of the year and for VIPs.

 Exercises for practice at home(Assignment):

 Consider the following specification and Draw the Class and Object
diagrams:
 A video store has a stock of movies and video games for rent. It is
important to keep track of each movie title to know and to identify its
category (classical, drama, comedy, and so on), its rental type (new
release, standard), movie rating, and other general information such as
movie producer, release date, cost, and so forth. In addition to tracking
each title, the business must track each individual copy to note its
purchase date, its condition, and its rental status. User functions must be
provided to maintain this inventory information .

Page 78 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 Customers, the lifeblood of the business, are also tracked. The video store
system considers each family to be a customer, so special mailings and
promotions are offered to each household. For any given customer,
several people may be authorized to rent videos and games. The primary
contact for each customer can also establish rental parameters for other
members of the household.

 Each time a movie is rented, the system must keep track of which copies
of which movies and games are rented; the rental date and time and the
return date and time; and the household and person renting the movie.
Each rental is considered to be open until all of the movies and games
have been returned. Customers pay for rentals when checking out videos
at the store.

Page 79 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 Exercise 9 (Week 14)

Title of the Exercise: Component diagram: to draw the

implementation view diagram

 Objectives / Statement Purpose:

 Component diagrams are different in terms of nature and behavior. Component
diagrams are used to model physical aspects of a system.
 Now the question is what are these physical aspects? Physical aspects are the
elements like executables, libraries, files, documents etc which resides in a node.
 So component diagrams are used to visualize the organization and relationships
among components in a system. These diagrams are also used to make executable
systems.
 Purpose:
 Component diagram is a special kind of diagram in UML. The purpose is also
different from all other diagrams discussed so far. It does not describe the
functionality of the system but it describes the components used to make those
functionalities.
 So from that point component diagrams are used to visualize the physical components
in a system. These components are libraries, packages, files etc.
 Component diagrams can also be described as a static implementation view of a
system. Static implementation represents the organization of the components at a
particular moment.
 A single component diagram cannot represent the entire system but a collection of
diagrams are used to represent the whole.
 So the purpose of the component diagram can be summarized as:
 Visualize the components of a system.
 Construct executables by using forward and reverse engineering.
 Describe the organization and relationships of the components.

Page 80 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 Activity Outcomes: Component diagrams are used to describe the physical
artifacts of a system. This artifact includes files, executables, libraries etc. So the purpose of
this diagram is different, Component diagrams are used during the implementation phase of
an application. But it is prepared well in advance to visualize the implementation details.
Initially the system is designed using different UML diagrams and then when the artifacts are
ready component diagrams are used to get an idea of the implementation.
 This diagram is very important because without it the application cannot be
implemented efficiently. A well prepared component diagram is also important for
other aspects like application performance, maintenance etc.

 So before drawing a component diagram the following artifacts are to be identified

clearly:
stem.

 Now after identifying the artifacts the following points needs to be followed:

 Use a meaningful name to identify the component for which the diagram is
to be drawn.
 Prepare a mental layout before producing using tools.
 Use notes for clarifying important points.

 The following is a component diagram for order management system. Here the
artifacts are files. So the diagram shows the files in the application and their
relationships. In actual the component diagram also contains dlls, libraries, folders
etc.
 In the following diagram four files are identified and their relationships are produced.
Component diagram cannot be matched directly with other UML diagrams discussed
so far. Because it is drawn for completely different purpose.
 So the following component diagram has been drawn considering all the points
mentioned above:

Page 81 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
  Instructions for solving problems :

 We have already described that component diagrams are used to visualize the static
implementation view of a system. Component diagrams are special type of UML
diagrams used for different purposes.
 These diagrams show the physical components of a system. To clarify it, we can say
that component diagrams describe the organization of the components in a system.
 Organization can be further described as the location of the components in a system.
These components are organized in a special way to meet the system requirements.
 As we have already discussed those components are libraries, files, executables etc.
Now before implementing the application these components are to be organized. This
component organization is also designed separately as a part of project execution.
 Component diagrams are very important from implementation perspective. So the
implementation team of an application should have a proper knowledge of the
component details.

Page 82 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 Now the usage of component diagrams can be described as:
 Model the components of a system.
 Model database schema.
 Model executables of an application.
 Model system's source code.

 Exercises (To be solved in Classroom):

 Task 1

 Using the following specification and Draw the Component diagram.

The Online Library System provides online real time information about the books
available in the Library and the user information. The Product functions are more or
less the same as described in the product perspective. The functions of the system
include the system providing different type of services based on the type of users
[Member/Librarian].

 The member should be provided with the updated information about the books
catalog.
 Provisions for the members to borrow the books they want, if all the other
required rules hold good.
 The member is given a provision to check his account information and change
the account information any time in the given valid period.
 The members are provided with the books available roster and allowed to
choose the books, which they want to use in the coming up days.
 The librarian can get the information about the members who have borrowed
or returned the books.
 The librarian is provided with interfaces to add/delete the books available in
the book catalog.
 The members when complete the book borrowing or returning process, the due
to be paid by the member must be calculated and the information about the
member and the due amount is sent to the university billing system.

Page 83 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
  The system uses the University information security requirements to provide
the login facility to the users.

 Task 2

 Consider the following specification and Draw the Component diagram

which corresponds to the given specification

The hotel reservation include following functionality:

 For the hotel guest – search available rooms – make a reservation (after
registration). Up to 2 reservations are possible for each guest – confirm
reservation – cancel reservation – pay through credit card or bank transfer
 For the hotel manager – alter reservation list (remember to issue notice to the
future guests!) – remove rooms (remember to alter reservation list!) – add
rooms – change room details (remember to issue notice to the future guests!)
 For the system: – maintain list of rooms and reservations in the database –
interact with external payment system for guest payments – apply discounts
for long stays, unpopular periods of the year and for VIPs.

 Task 3
 Consider the following specification, Draw the Component diagram which
corresponds to the above specification.

 Purpose: Describe major services (functionality) provided by a hospital's reception.

 Summary: Hospital Management System is a large system including several

subsystems or modules providing variety of functions. Hospital Reception subsystem
Page 84 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 or module supports some of the many job duties of hospital receptionist. Receptionist
schedules patient's appointments and admission to the hospital, collects information
from patient upon patient's arrival and/or by phone.

 For the patient that will stay in the hospital ("inpatient") she or he should have a bed
allotted in a ward. Receptionists might also receive patient's payments, record them in
a database and provide receipts, file insurance claims and medical reports.

 Exercises for practice at home(Assignment):

 Consider the following specification Draw the Component diagram: to

draw the implementation view which deals with Railway Reservation.

Railway Reservation System is a system used for booking tickets over internet. Any
Customer Can book tickets for different trains. Customer can book a ticket only if the
tickets are available. Customer searches for the availability of tickets then if the
tickets are available he books the tickets by initially filling details in a form. Tickets
can be booked in two ways by i-ticket or by e-ticket booking.

In case of i-ticket booking customer can book the tickets online and the tickets are
couriered to Particular customer at their address. But in case of e-ticket booking and
cancelling tickets are booked and cancelled online sitting at the home and customer
himself has to take print of the ticket but in both the cases amount for tickets are
deducted from customers account .

For cancellation of ticket the customer has to go at reservation office than fill
cancellation form and ask the clerk to cancel the ticket than the refund is transferred
to customer account. After booking ticket the customer has to checkout by paying
fare amount to clerk.

Page 85 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 Exercise 10 (Week 15)
Title of the Exercise: Deployment diagram: to draw the
environmental view diagram

 Objectives / Statement Purpose:

Deployment diagrams are used to visualize the topology of the physical components
of a system where the software components are deployed.
So deployment diagrams are used to describe the static deployment view of a system.
Deployment diagrams consist of nodes and their relationships.

Purpose:
The name Deployment itself describes the purpose of the diagram. Deployment
diagrams are used for describing the hardware components where software
components are deployed. Component diagrams and deployment diagrams are closely
related.
Component diagrams are used to describe the components and deployment diagrams
shows how they are deployed in hardware.

 Activity Outcomes:
 UML is mainly designed to focus on software artifacts of a system. But
these two diagrams are special diagrams used to focus on software
components and hardware components.
 So most of the UML diagrams are used to handle logical components but
deployment diagrams are made to focus on hardware topology of a system.
Deployment diagrams are used by the system engineers.
 The purpose of deployment diagrams can be described as:

components.

Page 86 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 Instructions for solving problems :
 Deployment diagram represents the deployment view of a system. It is
related to the component diagram. Because the components are deployed
using the deployment diagrams. A deployment diagram consists of nodes.
Nodes are nothing but physical hardware’s used to deploy the application.
 Deployment diagrams are useful for system engineers. An efficient
deployment diagram is very important because it controls the following
parameters

 So before drawing a deployment diagram the following artifacts should be

identified:

 The following deployment diagram is a sample to give an idea of the

deployment view of order management system. Here we have shown
nodes as:

 The application is assumed to be a web based application which is

deployed in a clustered environment using server 1, server 2 and server 3.
The user is connecting to the application using internet. The control is
flowing from the caching server to the clustered environment.
 So the following deployment diagram has been drawn considering all the
points mentioned

 Exercises (To be solved in Classroom):

 Task 1

Page 87 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 Draw the Deployment diagram which corresponds to the following specification,
 Purpose: Describe major services (functionality) provided by a hospital's reception.
 Summary: Hospital Management System is a large system including several
subsystems or modules providing variety of functions. Hospital Reception subsystem
or module supports some of the many job duties of hospital receptionist. Receptionist
schedules patient's appointments and admission to the hospital, collects information
from patient upon patient's arrival and/or by phone.
 For the patient that will stay in the hospital ("inpatient") she or he should have a bed
allotted in a ward. Receptionists might also receive patient's payments, record them in
a database and provide receipts, file insurance claims and medical reports.

 Task 2

 Using the following specification and Draw the Deployment

diagram:

The Online Library System provides online real time information about the books
available in the Library and the user information. The Product functions are more or
less the same as described in the product perspective. The functions of the system
include the system providing different type of services based on the type of users
[Member/Librarian].

 The member should be provided with the updated information about the books
catalog.
 Provisions for the members to borrow the books they want, if all the other
required rules hold good.
 The member is given a provision to check his account information and change
the account information any time in the given valid period.
 The members are provided with the books available roster and allowed to
choose the books, which they want to use in the coming up days.
 The librarian can get the information about the members who have borrowed
or returned the books.

Page 88 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
  The librarian is provided with interfaces to add/delete the books available in
the book catalog.
 The members when complete the book borrowing or returning process, the due
to be paid by the member must be calculated and the information about the
member and the due amount is sent to the university billing system.
 The system uses the University information security requirements to provide
the login facility to the users.

 Task 3

 Draw the Deployment diagram to view the environmental view related to the
following specification:

Each physical library item - book, tape cassette, CD, DVD, etc. could have its
own item number. To support it, the items may be barcoded. The purpose of
barcoding is to provide a unique and scannable identifier that links the
barcoded physical item to the electronic record in the catalog. Library has
some rules on what could be borrowed and what is for reference only. Rules
are also defined on how many books could be issued by librarians. This last
can order one or more publisher .

Library catalog provides access for the librarians about library items, allows
to search by a particular author, on a particular topic, or in a particular
format, that the library has. It tells the user where materials meeting their
specific needs can be found. It should be noted the user can be a faculty
member or a student.

 Exercises for practice at home(Assignment):

 Draw the Deployment diagram which deals with the Railway Reservation
System using the given specification.

Page 89 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN
 Railway Reservation System is a system used for booking tickets over internet.
Any Customer Can book tickets for different trains. Customer can book a ticket
only if the tickets are available. Customer searches for the availability of tickets
then if the tickets are available he books the tickets by initially filling details in a
form. Tickets can be booked in two ways by i-ticket or by e-ticket booking.
 In case of i-ticket booking customer can book the tickets online and the tickets
are couriered to Particular customer at their address. But in case of e-ticket
booking and cancelling tickets are booked and cancelled online sitting at the
home and customer himself has to take print of the ticket but in both the cases
amount for tickets are deducted from customers account .
 For cancellation of ticket the customer has to go at reservation office than fill
cancellation form and ask the clerk to cancel the ticket than the refund is
transferred to customer account. After booking ticket the customer has to
checkout by paying fare amount to clerk.

******* All The Best*******

Page 90 of 90
SET_Software Engineering and Testing Lab Manual new by: Dr.M.K. JAYANTHI KANNAN