LAB MANUAL

CASE TOOLS AND TESTING TOOLS LAB

Subject Code: SE261

B.Sc. (Computer Science) – III YEAR

VI SEMESTER

University of Madras 2022– 2023

Register Number :

Student Name :

Class :
 UNIVERSITY OF MADRAS
B.Sc. DEGREE COURSE IN COMPUTER SCIENCE
SYLLABUS WITH EFFECT FROM 2020-2021
BCE-DSC17
CORE-XVII: PRACTICAL - VII CASE TOOLS AND TESTING TOOLS LAB

III YEAR / VI SEM

OBJECTIVES:
 To get familiarized to the usage of UML tool kit
 To understand the requirements of the software and to map them appropriately to subsequent
phases of the software development
 To develop the ability to verify and validate their designs
OUTCOMES:
 Students must be able to analyze and design the problem at hand.
 Students should be able to use UML tools for the designing the software and test the correctness
and soundness of their software through testing tools.

LIST OF EXERCISES:
1. Using UML tools produce analysis and design models for
a. Library Management System
b. Automatic Teller Machine
c. Student Information Management
d. Matrimony Service
e. Stock Management System
2. Study of Open source testing tools (e.g. Selenium, WATIR, Apache JMeter, TestNG)

****
 INDEX
Teacher’s
Sl. No. Date Name of the Experiment Signature

1. (a) LIBRARY MANAGEMENT SYSTEM

(b) AUTOMATIC TELLER MACHINE

(c) STUDENT INFORMATION MANAGEMENT

(d) MATRIMONY SERVICE

(e) STOCK MANAGEMENT SYSTEM

2. STUDY OF OPEN SOURCE TESTING TOOLS

 UML Diagrams
1. Use Case Diagram
 A Use Case Diagram is used to represent the dynamic behavior of a system.
 Use Case Diagrams describe the high-level functions and scope of a system. These diagrams also
identify the interactions between the system and its actors.
 To create a Use Case Diagram:
1. Select first an element where a new Use Case Diagram to be contained as a child.
2. Select Model | Add Diagram | Use Case Diagram in Menu Bar or select Add Diagram |
Use Case Diagram in Context Menu.
 In Use Case Diagram, we can use the following elements: Package, Use Case Subject, Actor,
Use Case, Extension Point, Association, Dependency, Generalization, Include, and Extend.
2. Class Diagram
 The Class Diagram represents the static view of an application.
 The Class Diagrams are widely used in the modeling of object-oriented systems.
 Class Diagram shows a collection of classes, interfaces, associations, collaborations, and
constraints. It is also known as a structural diagram.
 To create a Class Diagram:
1. First select an element where a new Class Diagram to be contained as a child.
2. Select Model | Add Diagram | Class Diagram in the Menu Bar or select Add Diagram |
Class Diagram in Context Menu.
 In Class Diagram, we can use the following elements: Class, Attribute, Operation, Parameter,
Template Parameter, Interface, Association, Aggregation, Composition, Dependency,
Generalization, Interface Realization, Signal, Data Type, Primitive Type, Enumeration,
Association Class, Package, Model, Subsystem and Containment.
3. Sequence Diagram
 The Sequence Diagram represents the flow of messages in the system and is also termed as an
event diagram.
 A Sequence Diagram shows how different parts of a system work in a „sequence‟ to get
something done.
 To create a Sequence Diagram:
1. Select first an element where a new Sequence Diagram to be contained as a child.
2. Select Model | Add Diagram | Sequence Diagram in Menu Bar or select Add Diagram |
Sequence Diagram in Context Menu.
 In Sequence Diagram, we can use following elements: Lifeline, Message, Endpoint, Gate,
State Invariant, Continuation, Combined Fragment and Interaction Use.
4. Collaboration Diagram
 The Collaboration Diagram is used to show the relationship between the objects in a system.
 The Collaboration Diagram is also known as Communication Diagram.
 To create a Communication Diagram:
1. Select first an element where a new Communication Diagram to be contained as a child.
2. Select Model | Add Diagram | Communication Diagram in Menu Bar or select Add Diagram |
Communication Diagram in Context Menu.
 The components of a collaboration diagram are Objects, Actors, Links and Messages.

5. Statechart Diagram
 Statechart Diagram is one of the UML diagrams used to model the dynamic nature of a system.
 It is also called State Transition Diagram.
 Statechart Diagram describes the flow control from one state to another state.
 To create a Statechart Diagram:
1. Select first an element where a new Statechart Diagram to be contained as a child.
2. Select Model | Add Diagram | Statechart Diagram in Menu Bar or select Add Diagram |
Statechart Diagram in Context Menu.
 In Statechart Diagram, we can use the following elements: State, Internal Activity, Region,
Initial State, Final State, Choice, Join, Fork, Junction, Shallow History, Deep History,
Entry Point, Exit Point, Terminate, Connection Point Reference and Transition.
6. Activity Diagram
 An Activity Diagram is essentially a flowchart that shows activities performed by a system.
 An Activity Diagram is used by developers to understand the flow of programs on a high level.
 Activity Diagrams are often used in business process modeling.
 To create an Activity Diagram:
1. Select first an element where a new Activity Diagram to be contained as a child.
2. Select Model | Add Diagram | Activity Diagram in Menu Bar or select Add Diagram |
Activity Diagram in Context Menu.
 In Activity Diagram, we can use the following elements: Action, Event, Initial, Activity
Final, Fork, Join, Merge, Decision, Swimlane (Partition), Input Pin, Output Pin, Send
Signal, Accept Signal, Flow Final, Object Node, Control Flow and Object Flow.
7. Component Diagram
 Component Diagrams are used to visualize the organization and relationships among
components in a system.
 It models the physical view of a system such as executables, files, libraries, etc. that resides
within the node.
 It is like a black box whose behavior is explained by the provided and required interfaces.
 To create a Component Diagram:
 Select first an element where a new Component Diagram to be contained as a child.
 Select Model |Add Diagram | Component Diagram in Menu Bar or select Add
Diagram | Component Diagram in Context Menu.
 In Component Diagram, we can use the following elements: Component, Artifact,
Interface, Dependency, Interface Realization, Component Realization, Node,
Deployment, Communication, Path, Object, Artifact Instance, Component Instance,
Node Instance and Link.
8. Deployment Diagram
 The Deployment Diagram is a type of diagram that specifies the physical hardware on which
the software system will execute.
 It portrays the static deployment view of a system.
 To create a Deployment Diagram:
1. Select first an element where a new Deployment Diagram to be contained as a child.
2. Select Model | Add Diagram | Deployment Diagram in Menu Bar or select Add
Diagram | Deployment Diagram in Context Menu.
 In Deployment Diagram, we can use the following elements: Component, Artifact,
Interface, Dependency, Interface Realization, Component Realization, Node,
Deployment, Communication Path, Object, Artifact Instance, Component Instance,
Node Instance and Link.
 EX.NO:1 (a)
LIBRARY MANAGEMENT SYSTEM
Date:

AIM:
To produce analysis and design models for Library Management System using StarUML
Software.
PROBLEM STATEMENT:
The Library Management System is a software system used for the purpose of monitoring and
controlling the transactions in a library. This study gives us complete information about the
library and the daily transactions done in a library such as issuing books, magazines to the
registered Students and Staff. The student has to login after getting registered to the system. The
borrower of the book can perform various functions such as searching for desired book, get the
issued book and return the book.
Use Case Diagram for Library Management System
Class Diagram for Library Management System
 Sequence Diagram for Issuing Books

Sequence Diagram for Returning Books

Collaboration Diagram for Issuing Book

Statechart Diagram for Book

Statechart Diagram for Librarian

 Activity Diagram for Issuing Book in Library

Component diagram for Library Management System

 Deployment Diagram for Library Management System

RESULT:
Thus, the UML diagrams for Library Management System were designed successfully using
StarUML Software.
 EX.NO: 1 (b)
AUTOMATIC TELLER MACHINE
DATE:

AIM:
To produce analysis and design models for Automatic Teller Machine using StarUML
Software.

PROBLEM STATEMENT:
The Automatic Teller Machine is a software system used for the purpose of monitoring and
controlling the transactions in a banking system. An ATM (Automatic Teller Machine) is an
electronic machine used for financial transactions. This study gives us complete information about
a self-service banking outlet. It is an 'automated' banking platform that does not require any banking
representative/teller or a human cashier. In Automatic Teller Machine, the customer can withdraw
money, check your balance, or even transfer funds.
Use Case Diagram for Automatic Teller Machine
Class Diagram for Automatic Teller Machine
Sequence Diagram for Automatic Teller Machine
Collaboration Diagram for Automatic Teller Machine

Statechart Diagram for Automatic Teller Machine

Activity Diagram for Automatic Teller Machine
 Component Diagram for Automatic Teller Machine

Deployment Diagram for Automatic Teller Machine

RESULT:
Thus, the UML diagrams for Automatic Teller Machine were designed successfully using Star
UML Software.
EX.NO:1 (c)
STUDENT INFORMATION MANAGEMENT
DATE:

AIM:
To produce analysis and design models for Student Information Management using Star UML
Software.
PROBLEM STATEMENT:
A Student Information Management is a web-based platform that helps schools and colleges take
student data online for easier management and better clarity. It is a management information system
used for education sector establishments used to manage student data. It integrates students,
parents, teachers and the administration. The Student Information System provides capabilities
for registering students in courses, documenting grading, transcript of academic achievements
and the results of student assessments scores.
Use Case Diagram for Student Management System
 Class Diagram for Student Management System

Sequence Diagram for Student Management System

Collaboration Diagram for Student Management System

Statechart Diagram for Student Management System

Activity Diagram for Student Management System

 Component Diagram for Student Management System

Deployment Diagram for Student Management System

RESULT:
Thus, the UML diagrams for Student Information Management were designed successfully
using Star UML Software.
 EX.NO:1 (d)
MATRIMONY SERVICE
DATE:

AIM:
To produce analysis and design models for Matrimony Service using StarUML Software.
PROBLEM STATEMENT:
The Matrimony Service is an application which will provide
all Marriage related services and collect all the service providers includes admin, member and
visitor. The Matrimony Service provides registered users, after which they are able to upload their
profile on to a searchable database maintained by the websites. In the Matrimony Service website
people seeking to get married post their personal profiles, registration and uploading the photo in
the database.
Use Case Diagram for Matrimony Service
Class Diagram for Matrimony Service
Sequence Diagram for Matrimony Service
Collaboration Diagram for Matrimony Service

Statechart Diagram for Matrimony Service

Activity Diagram for Matrimony Service
 Component Diagram for Matrimony Service

Deployment Diagram for Matrimony Service

RESULT:
Thus, the UML diagrams for Matrimony Service were designed successfully using
StarUML Software.
EX.NO. 1(e)
STOCK MANAGEMENT SYSTEM
DATE:

AIM:
To produce analysis and design models for Stock Management System using StarUML
Software.
PROBLEM STATEMENT:
The Stock Management System is basically a computer based system for tracking inventory levels,
orders, sales and deliveries. It can also be used in the manufacturing industry to create a work order,
bill of materials and other production-related documents. By this process we can effectively oversee
the constant flow of the units into and out of a currently existing inventory. The Stock Management
System covers all operations involved in regulating the flow of goods or products within a
company.
Use Case Diagram for Stock Management System
Class Diagram for Stock Management System

Sequence Diagram for Stock Management System

Collaboration Diagram for Stock Management System

Statechart Diagram for Stock Management System

Activity Diagram for Stock Management System

 Component Diagram for Stock Management System

Deployment Diagram for Stock Management System

RESULT:
Thus, the UML Diagrams for Stock Management System were designed successfully using the
StarUML Software.
EX.NO. : 2
STUDY OF OPEN SOURCE TESTING TOOLS
DATE:

AIM:
To study about the Open Source Testing Tools like Selenium, WATIR, Apache JMeter and
TestNG.
PROBLEM STATEMENT:
Open Source Testing Tools are applications that support a range of testing activities. This software
enables us to plan, build, test execution, defect logging, and more. These testing tools are used for
testing software firmness and thoroughness.
1) Selenium
 Selenium is the most popular automated software testing tool.
 It specifically designed to support Automation Testing of functional aspects of web-based
applications, a wide range of platforms, and browsers.

Features:
 This open source testing tool offers the support for parallel test execution that reduces the
time taken in executing parallel tests.
 Selenium needs very lesser resources when compared to other testing tools.
 Test cases prepared using this testing tool can be executed on any OS.
 This website testing tool supports the many known programming languages like Java, Python,
C#, Perl, PHP, and JavaScript.
Link: https://www.selenium.dev/
2) WATIR (Web Application Testing in Ruby)
 WATIR is an open-source, cross-platform web application performance testing tool.
 It uses Ruby libraries for web browsers automation.
 It is one of the best open source test automation tools that interact with a browser just like a
human being, so it clicks links, filling out forms, and validating text.
Features:
 It is a free, so there are no costs to use the tool.
 This automated testing tool is supported by a very active and growing community.
 It supports multiple browsers on different platforms.
 It is a powerful and lightweight tool.
Link: http://watir.com/
3) Apache JMeter
 Apache JMeter is an open-source load testing tool.
 It is a Java desktop application designed to load functional test behavior and measure the
performance of websites.
 The tool was developed for the purpose of load testing web applications, but it is now
expanded to other test functions.

Features:
 JMeter allows performing load and performance tests for various server types.
 This load testing tool stores its test plans in XML format, which allows users to generate the
test plan using a text editor.
 The performance testing tool can be used to perform automated and functional testing of the
applications.
Link: https://jmeter.apache.org/
4) TestNG

 TestNG is an automation testing framework in which NG stands for “Next Generation”.

 This application is designed to make end-to-end testing easy.
 It enables us to generate test plans and test reports in various formats quickly
Features:
 It supports multiple projects
 We can export and import test cases without any hassle.
 Integration with many defect management tools.
 Automated test case execution through XML-RPC.
 Easy filtration of test cases with version, keywords, test case ID and version
 We can assign test cases to multiple users
 Provide credentials to multiple users and assign roles to them.
Link: https://testng.org/doc/
RESULT:
Thus, the Open Source Testing Tools like Selenium, WATIR, Apache JMeter and TestNG were
studied successfully.
********************************************************************************