PRINCE SHRI BALAJI ARTS AND

SCIENCE COLLEGE
PONMAR, CHENNAI-600127

(AFFILIATED TO THE UNIVERSITY OF MADRAS)

DEPARTMENT OF COMPUTER SCIENCE

CASE TOOLS AND TESTING

TOOLS LAB
Academic Year: 2023-2024

Name:

Class:
 PRINCE SHRI BALAJI ARTS AND
SCIENCE COLLEGE
PONMAR, CHENNAI-600127

(AFFILIATED TO THE UNIVERSITY OF MADRAS)

REGISTER NUMBER:

This is to certify that Studying

in III B.Sc. (Computer Science) in this college has successfully completed his/her

“CASE TOOLS AND TESTING TOOLS LAB” record for the Semester-VI

during the academic year 2023 – 2024.

Faculty In-Charge Head of the Department

Submitted for the practical examination held on at

Prince Shri Balaji Arts and Science College.

EXTERNAL EXAMINERS:

1.

2.
 INDEX
Ex.No. DATE TOPICS Pg.No. SIGN
DESIGN AND ANALYSIS OF UML TOOLS
1.
1 10.01.2024 LIBRARY MANAGEMENT
SYSTEM
i. 10.01.2024 Class Diagram
ii. 10.01.2024 Use Case Diagram
iii. 10.01.2024 Deployment Diagram
iv. 10.01.2024 Component Diagram
v. 10.01.2024 State chart Diagram
vi. 10.01.2024 Collaboration Diagram
vii. 10.01.2024 Sequence Diagram
viii. 10.01.2024 Activity Diagram

2 29.01.2024 AUTOMATIC TELLER MACHINE

i. 29.01.2024 Class Diagram
ii. 29.01.2024 Use Case Diagram
iii. 29.01.2024 Sequence Diagram
iv. 29.01.2024 Collaboration Diagram
v. 29.01.2024 State chart Diagram
vi. 29.01.2024 Activity Diagram
vii. 29.01.2024 Component Diagram
viii. 29.01.2024 Deployment Diagram

3 09.02.2024 STUDENT INFORMATION

MANAGEMENT
i. 09.02.2024 Class Diagram
ii. 09.02.2024 Collaboration Diagram
iii. 09.02.2024 Sequence Diagram
iv. 09.02.2024 Component Diagram
v. 09.02.2024 Use Case Diagram
vi. 09.02.2024 Deployment Diagram
vii. 09.02.2024 State Chart Diagram
viii. 09.02.2024 Activity Diagram

4 19.02.2024 MATRIMONY SERVICE

i. 19.02.2024 Class Diagram
ii. 19.02.2024 Use Case Diagram
iii. 19.02.2024 Sequence Diagram
iv. 19.02.2024 Collaboration Diagram
v. 19.02.2024 State Chart Diagram
vi. 19.02.2024 Activity Diagram
vii. 19.02.2024 Component Diagram
viii. 19.02.2024 Deployment Diagram

5 29.02.2024 STOCK MANAGEMENT SYSTEM

i. 29.02.2024 Class Diagram
ii. 29.02.2024 Use Case Diagram
iii. 29.02.2024 Component Diagram
iv. 29.02.2024 Deployment Diagram
v. 29.02.2024 Sequence Diagram
vi. 29.02.2024 Collaboration Diagram
vii. 29.02.2024 Activity Diagram
viii. 29.02.2024 State Chart Diagram

6. 05.03.2024 STUDY OF OPEN SOURCE

TESTING TOOLS
i. 05.03.2024 Selenium
ii. 05.03.2024 Apache JMeter
iii. 05.03.2024 WATIR
iv. 05.03.2024 Test NG
v. 05.03.2024 WATIN
Ex. No:1
LIBRARY MANAGEMENT SYSTEM
Date :10.01.2024

AIM:

To design an object oriented model for Library Management System using the
ArgoUML software and to implement it using Java.

PROBLEM STATEMENT:
The library management system is a software system that issues books and magazines to
registered students only. 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.
CLASS DIAGRAM:
.
USE CASE DIAGRAM:

login

enter name and password

<<actor>>
projection of

display page

requesting for book

user

display book details

search for book

librarian

issue book

return book

DBA
maintain database

logout
DEPLOYMENT DIAGRAM:

library management
system

DBA
user

librarian
COMPONENT DIAGRAM:

library
managem
entsystem

user
DBA
librarian
STATECHART DIAGRAM:

enter requesting display book

details for book details

logout return book issue book search

book
COLLABORATION DIAGRAM:

13: if valid
1: login
2: enter details
11: logout
12: requesting book

user
system

5: display page
14: display page
6: requesting book 15:
10: return book 3: check details
9: issue book 7: search book

4: if valid

8: display
details

libra ian

dba
SEQUENCE DIAGRAM:

librarian dba
user system
ACTIVITY DIAGRAM:

user system librarian DBA

login

enter details check details

display page if valid

request book

search book

display book
details
issue book

logout
OUTPUT:
//Source file: C:\Users\HP\Downloads\lab1\Dba.java

public class Dba

private string

dbaName;private

integer dbPwd;

public void maintainDatabase()

}
//Source file: C:\Users\HP\Downloads\lab1\Librarian.java
public class Librarian

private string lname;

private integer lid;

private string lpwd;

public Librarian

theLibrarian;public

System theSystem;

public Librarian()
{

public void searchBook()

}
public void issueBook()

{
 }

}
//Source file: C:\Users\HP\Downloads\lab1\System.java
public class System

private integer sysNo;

public Dba theDba;

public System()

public void displayPage()

public void displayBookDetails()

}
//Source file: C:\Users\HP\Downloads\lab1\User.java
public class User

private string username;

private integer userid;

private string userdept;

public System theSystem;

public Librarian

theLibrarian;public

User()
 {

public void login()

public void enterDetails()

public void requestingBook()

public void returnBook()

public void logout()

}
 RESULT:

Thus, the various UML diagrams for library management system was drawn
and the code was generated successfully.
 EX.NO:2
AUTOMATIC TELLER MACHINE

Date :29.01.2024

AIM:
To develop the project of an Automatic Teller Machine using the ArgoUML software and to
implement the software in JAVA.

PROBLEM STATEMENT:
A user may withdraw as much as many amounts as he wants until his account holds a sum greater
than his withdrawal amount. This ATM system can use any kind of interface. But it should be user friendly
and not confusing.

The system will retain information on the entire customer who has necessity rights to access the
service. It will contain the balance amount in the account, rate of interest, any special allowance for that
customer and most of all pin number of the customer. The ATM system should be compatible with any kind
of database such as MS-ACCESS, DB2, ORACLE, SQL, SERVER etc. the emphasis here is on consistency.
The ATM should provide easy access to the data for the customer. It should also have a highly secure
interface so that one can take money one behalf of others. So the security is one of the main aspects in ATM.
CLASS DIAGRAM:-
.
USE CASE DIAGRAM:

uc Use Case Model

Check Exceeding
Balance

Withdraw Cash
«include»

«include»

Transfer Money

Check balance

Print Receipt
Log Out
«extend»

Bank
Customer

Deposit a Check

Deposit Cash

Log in

Depit Card Login Credit Card Login

SEQUENCE DIAGRAM:
COLLABORATION DIAGRAMS:

CHECK BALANCE COLLABORATION DIAGRAM:

DEPOSIT CASH COLLABORATION DIAGRAM:

STATECHART DIAGRAM:
ACTIVITY DIAGRAM:
COMPONENT DIAGRAM:

maintain customer

DEPLOYMENT DIAGRAM:
 OUTPUT:
//Source File: C:\Users\HP\Downloads\lab2\Account.java

import java.util.Vector;

public class Account

public String type;

public String Owner;

public Vector provides access to;

public Vector owns;
public Vector owns;

public void check_balance()

{

//Source File: C:\Users\HP\Downloads\lab2\ATM Transaction.java

public class ATM Transaction

public Integer transaction_id;

public String date;

public String type;

public Vector myAccount;

public Vector identifies;

public void update()

{

//Source File: C:\Users\HP\Downloads\lab2\ATM Transaction.java

public class ATM

public String location;

public String managed by;

public Vector myBank;

public Vector maintains;
public Vector identifies;

public void identifies() { }

public void transactions() { }

//Source File: C:\Users\HP\Downloads\lab2\Bank.java

public class Bank

public Integer code;

public String Address;

public Vector myATM;
public Vector maintains;
public Vector manages;
public Vector has;

public void manages() { }

public void maintains() { }

//Source File: C:\Users\HP\Downloads\lab2\Checking Account.java

public class Checking Account

public Integer account_no;

public Vector mySaving Account;

 public void debit() { }

public void credit() { }

//Source File: C:\Users\HP\Downloads\lab2\Customer.java

public class Customer

{

public String name;

public String Address;

public String dob;

public Vector has;

public Vector owns;

public void owns() { }

public void newOperation() { }

//Source File: C:\Users\HP\Downloads\lab2\Debit_card.java

public class Debit_card

{
public Integer card_no;
public String owned_by;
public Vector manages;
public Vector provides access to;
public Vector owns;
public void access() { }
}
//Source File: C:\Users\HP\Downloads\lab2\Saving Account.java

public class Saving Account

{
public Integer account_no;
public Vector myChecking Account;
public void debit() { }
 public void credit() { }
}
//Source File:C:\Users\HP\Downloads\lab2\Transfer Transaction.java
public class Transfer Transaction
{
public Integer amount;
public Integer acc_no;
public Vector myWithdrawal Transaction;
public void payment_info() { }
}
//Source File: C:\Users\HP\Downloads\lab2\Withdrawal Transaction.java
public class Withdrawal Transaction
{
public Integer amount;
public Vector myTransfer Transaction;
public void withdraw() { }
}
RESULT:

Thus the various UML diagrams for automatic Teller Machine have been
created and the code was generated successfully.
EX NO: 3
Date :09.03.2024 STUDENT INFORMATION MANAGEMENT

AIM:
To develop a project Student information system using the ArgoUML Software and to
implement the software in Java.

PROBLEM STATEMENT:
The student must register by entering the name and password to login the form. The admin
selects the particular student to view the details about that student and maintaining the student
details. This process of student information system is described sequentially through following
steps. The student registers the system. The admin login to the student information system.
He/she searches for the list of students. Then select the particular student. Then view the details
of that student. After displaying the student details then logout.
CLASS DIAGRAM:
COLLABORATION DIAGRAM:

staff
student
1: login
10: display
6: logout

7: login
4: display 11: enter profile
12: enter mark
system 16: logout

14: store data

2: request access
8: request access 15: update data

13: provide data

server DBA

3: allow access
9: allow access
SEQUENCE DIAGRAM:

student staff system server DBA

login
request access

allow access

display

view details
logout

login

allow access

mark

data
update data

logout
COMPONENT DIAGRAM:
USE CASE DIAGRAM:

logout
DEPLOYMENT DIAGRAM:
STATE CHART DIAGRAM:

login enter enter

marks profile

view details

logout store update

details details
ACTIVITY DIAGRAM:
OUTPUT:
//Source file: C:/Users/IT/Desktop/kj/DBA.java

public class DBA

private integer ID;

private string password;

public DBA() {

public void storeDetails() {

public void updateDetails() {

//Source file: C:/Users/IT/Desktop/kj/Server.java

public class Server {

private integer ID;

private string password;

public DBA theDBA;

public Server() { }

public void allowAccess() {

public void display() {

}
//Source file: C:/Users/IT/Desktop/kj/Staff.java

public class Staff

private integer name;

private string ID;

public System theSystem;

public Staff() {

public void login() {

public void enterProfile() { }

public void enterMark() {

public void logout() {

//Source file: C:/Users/IT/Desktop/kj/System.java

public class System

private integer systemno;

private string password;

public Server theServer;

public System() {

public void display() {

}
 public void requestAccess()

}
RESULT:
Thus the various UML diagrams for student information system was
drawn and code was generated successfully.
EX.NO:4
Date :19.03.2024 MATRIMONY SERVICE

AIM:

To develop a project of matrimony service system using the ArgoUML software and to
implement the software in JAVA.

PROBLEM STATEMENT:
Matrimonial Websites are a variation of the standard dating websites. It is popular in
India and it is an alternative to the Traditional Marriage Broker. Matrimonial Services is an
application which will provide all Marriage related services and collect all the service providers
from all over the India at one platform to help parents looking for marriage to their sons and
daughters anywhere in the India. Matrimonial website has similar functionalities like Bharat
matrimony, Shadi.com. It allows user to register his/her profile and search his or her matching
profile and supports quick and advance profile search.
The main objective of Matrimonial Web Application is to provide grooms and brides
with excellent match making experience by exploring the opportunities and resources to meet
true potential partner. Keeping our objective in mind, a world renowned match making service
has been created that will touch the souls of millions of people all over the globe.
CLASS DIAGRAM :-

.
USE CASE DIAGRAM:
SEQUENCE DIAGRAM:
COLLABORATION DIAGRAM:
STATE DIAGRAM:-
ACTIVITY DIAGRAM:-

MEMBER SIDE-ACTIVITY DIAGRAM:

ADMIN SIDE - ACTIVITY DIAGRAM:
COMPONENT DIAGRAM:
DEPLOYMENT DIAGRAM:

Matrimony
Registration
System

Login Server

User
Database
Search
OUTPUT:

//Source File: C:\Users\HP\Downloads\lab4\Contact_Profile.java

public class Contact profile class {

public Integer Contact_profile_id;

public String Contact_profile_name;

public String Contact_profile_type;

public String Contact_profile_description;

public Integer Contact_partner_id;

public Vector myPartner Class;

public Vector access;

public void addContact_Profile() { }

public void edit_Contact_Profile() { }

public void delete_Contact_Profile() { }

public void search_Contact_Profile() { }

//Source File: C:\Users\HP\Downloads\lab4\Multiple_types.java

public class Multiple types class {

public Integer multiple_type_id;

public String multiple_type_name;

public String multiple_type_description;

public Vector login;

public void addMultipleTypes() { }

public void edit_multiple_types() { }

public void delete_multiiple_types() { }

 public void search_multiple_types() { }

//Source File: C:\Users\HP\Downloads\lab4\Partner.java

public class Partner Class {

public Integer Partner_id;

public String Partner_name;

public String Partner_mobileno;

public String Partner_email;

public String Partner_username;

public String Partner_address;

public String Partner_password;

public Vector myContact profile class;

public Contact profile class access;

public void add_Partner() {

}

//Source File: C:\Users\HP\Downloads\lab4\Permission.java

public class Permission Class {

public Integer permission_id;

public Integer permission_role;

public String permission_title;

public String permission_module;

public String permission_description;

public Vector login;

 public void addPermission() { }

public void editPermission() { }

public void deletePermission() { }

public void searchPermission() { }

//Source File: C:\Users\HP\Downloads\lab4\Photograph.java

public class Photogragh Class {

public Integer photogragh_id;

public String photogragh_name;

public String photogragh_type;

public String photogragh_description;

public Integer photogragh_partner_id;

public String photogragh_upload;

public Vector upload;

public void addPhotograph() { }

public void editPhotograph() { }

public void deletePhotograph() { }

public void searchPhotograph() { }

//Source File: C:\Users\HP\Downloads\lab4\Registration.java

public class Registration Class {

public Integer Registration_id;

 public String Registration_name;

public String Registration_type;

public String Registration_description;

public Integer Registration_userid;

public String Registration_no;

public String Registration_date;

public Vector access;

public void addRegistration() { }

public void editRegistration() { }

public void deleteRegistration() { }

public void searchRegistration() { }

//Source File: C:\Users\HP\Downloads\lab4\Role.java

public class role class {

public Integer role_id;

public String role_title;

public String role_description;

public Vector myPermission Class;

public void addrole() { }

public void editrole() { }

public void deleterole() { }

public void searchrole() { }

 public void assignrole() { }

//Source File: C:\Users\HP\Downloads\lab4\User.java

public class User class {

public Integer user_id;

public Integer user_role;

public String user_name;

public String user_email;

public String user_dob;

public String user_address;

public Vector myrole class;

public void addUser() { }

public void editUser() { }

public void deleteUser() { }

public void searchuser() { }

}
RESULT:

Thus the various UML diagrams for matrimony service system have been created and the
code was generated successfully.
EX: NO: 5 STOCK MANAGEMENT SYSTEM

Date:29.03.2024

AIM:

To develop a project of stock maintenance system using the ArgoUML software

and to implement the software in JAVA.

PROBLEM STATEMENT:

The stock maintenance system initial requirement is to develop a project about the
mechanism of the stock maintenance system is caught from the customer. The requirement
are analyzed and refined which enables the end-users to efficiently use stock-maintenance
system. The complete project is developed after the while project analysis explaining about
the scope and the project statement is prepared. The process of stock maintenance is that the
customer login to the particular site to place the order for the customer login to the
particular site to place the order for the customer product. The stock maintenance system is
described sequentially through steps. These steps are a customer login to the particular site.
They fill the customer details. They place the order for their product. The vendor login and
views the customer details and orders.
USE CASE DIAGRAM:
CLASS DIAGRAM:
COMPONENT DIAGRAM:

DEPLOYMENT DIAGRAM:
SEQUENCE DIAGRAM:
COLLABORATION DIAGRAM:
ACTIVITY DIAGRAM:
STATECHART DIAGRAM:
OUTPUT:

//Source File: C:\Users\HP\Downloads\lab5\Admin.java

public class Admin {

public Integer ID;

public String password;

public void enter_customer_details() { }

public void product_info() { }

public void check_product_availability() { }

//Source File: C:\Users\HP\Downloads\lab5\Customer.java

public class Customer {

public Integer ID;

public String Name;

public String Password;

public Vector enroll details;

public void opname() {

}

public void makeOrder() { }

public void orderconfirmed() { }

public void enterDetails() { }

public void payingBill() { }

public void logout() {

 }

}
//Source File: C:\Users\HP\Downloads\lab5\Database.java
public class Database {

public Integer db.no;

public String password;

public Vector search data;

public void allow_access() { }

public void return_productinfo() { }

//Source File: C:\Users\HP\Downloads\lab5\Supplier.java

public class Supplier {

public String Name;

public Integer ID;

public Vector deliver the product;

public void delivery_product() { }

public void payment_info() { }

}
RESULT:

Thus the various UML diagrams for stock maintenance system have been created and
the codewas generated successfully.
Ex.No: 6
STUDY OF OPEN-SOURCE TESTING TOOLS
Date:05.03.2024

AIM:

To study the framework of open source testing tools such as Selenium, Apache
JMeter,TestNG,WATIS and their implementation.

OPEN- S O U R C E TESTING TOOLS:

1) SELENIUM:
Selenium is one of the most widely used open source Web UI (User Interface)
automation testing suite.It was originally developed by Jason Huggins in 2004 as an internal
tool at Thought Works.
Selenium supports automation across different browsers, platforms and programming
languages.Selenium can be easily deployed on platforms such as Windows, Linux, Solaris
and Macintosh. Moreover, it supports OS (Operating System) for mobile applications like
iOS, windows mobile and android.
Selenium supports a variety of programming languages through the use of drivers
specific to each language.Languages supported by Selenium include C#, Java, Perl, PHP,
Python and Ruby.Currently, Selenium Web driver is most popular with Java and C#.
Selenium test scripts can be coded in any of the supported programming languages
and can be run directly in most modern web browsers.
Browsers supported by Selenium include Internet Explorer, Mozilla Firefox, Google
Chrome and Safari.
Selenium can be used to automate functional tests and can be integrated with
automation test tools such as Maven, Jenkins, & Docker to achieve continuous testing. It can
also be integrated with tools such as TestNG, & JUnit for managing test cases and generating
reports.
 2) APACHE JMETER:
JMeter is a software that can perform load test, performance-oriented business
(functional) test, regression test, etc., on different protocols or technologies.
Stefano Mazzocchi of the Apache Software Foundation was the original developer of
JMeter. He wrote it primarily to test the performance of Apache JServ . Apache later
redesigned JMeter to enhance the GUI and to add functional testing capabilities.
JMeter is a Java desktop application with a graphical interface that uses the Swing
graphical API. It can therefore run on any environment / workstation that accepts a Java
virtual machine, for example − Windows, Linux, Mac, etc.
The protocols supported by JMeter are −
⚫ Web − HTTP, HTTPS sites 'web 1.0' web 2.0 (ajax, flex and flex-ws-amf)
⚫ Web Services − SOAP / XML-RPC
⚫ Database via JDBC drivers
⚫ Directory − LDAP
⚫ Messaging Oriented service via JMS
⚫ Service − POP3, IMAP, SMTP
⚫ FTP Service
 Features of JMeter:
1. Being an open source software, it is freely available.
2. It has a simple and intuitive GUI.
3. JMeter can conduct load and performance test for many different server types − Web
- HTTP, HTTPS, SOAP, Database via JDBC, LDAP, JMS, Mail - POP3, etc.
4. It is a platform-independent tool. On Linux/Unix, JMeter can be invoked by clicking
on JMeter shell script. On Windows, it can be invoked by starting the jmeter.bat file.
5. It has full Swing and lightweight component support .JMeter store its test plans in
XML format. This means you can generate a test plan using a text editor.
6. Its full multi-threading framework allows concurrent sampling by many threads and
simultaneous sampling of different functions by separate thread groups.
7. It is highly extensible.
8. It can also be used to perform automated and functional testing of the applications.

Working of JMeter:
JMeter simulates a group of users sending requests to a target server, and returns
statistics that show the performance/functionality of the target server/application via tables,
graphs, etc.
 3) WATIR:
Watir is an open-source web application testing framework that is designed to
make writing Selenium tests simple and efficient. Built on Selenium's Ruby language
bindings, Watir is able to drive the browser in the same way humans do.
Unlike Selenium, Watir does not have an official IDE for recording and editing test
scripts. To use Watir Webdriver one needs to write test scripts by hand using Ruby. The
architecture of Watir Webdriver does not differ from Selenium Webdriver, as Watir
Webdriver is a wrapper of Selenium Webdriver.

4) TEST NG:
TestNG is a testing framework inspired from JUnit and NUnit but introducing some
new functionalities that make it more powerful and easier to use, such as:
⚫ Annotations.
⚫ Run your tests in arbitrarily big thread pools with various policies available (all
methods in their own thread, one thread per test class, etc...).
⚫ Test that your code is multithread safe.
⚫ Flexible test configuration.
⚫ Support for data-driven testing (with @DataProvider).
⚫ Support for parameters.
⚫ Powerful execution model (no more TestSuite).
⚫ Supported by a variety of tools and plug-ins (Eclipse, IDEA, Maven, etc...).
⚫ Embeds BeanShell for further flexibility.
⚫ Default JDK functions for runtime and logging (no dependencies).
⚫ Dependent methods for application server testing.
TestNG is designed to cover all categories of tests: unit, functional, end-to-end,
integration, etc…
 5) WATIN:
WatiN is an open-source library for automating web browsers using . NET. WatiN,
inspired by the popular Ruby-based Watir project, facilitates automated testing of web
applications through browser interaction. WatiN is written in C#, but tests can be expressed
in . NET language.
Version 1.0 was feature-rich in comparison to most other .NET solutions and
moderately popular as a user interface and user acceptance testing tool, but without
customization, it only supported automating Internet Explorer. Though still in
development, version 2.0 of WatiN supports automating IE and FireFox 2.0 & 3.0.
WatiN relies on browser interaction and uses DOM manipulation and verification to
assert conditions, but WatiN 2.0 has an abstraction layer that facilitates writing cross-
browser tests. The IE test and FireFox test could easily be refactored to a single test that
works against either browser.
Because writing WatiN tests by hand can be tedious, another open-source project
exists to record WatiN tests in a browser. WatiN Test Recorder does not have a new release
available, but version 2.0 is currently in development and promises major enhancements.
SELENIUM TESTING TOOL EXECUTION :
Step 1: Install Selenium IDE from chrome web store

Step 2: Add Extension to Selenium IDE

Step 3: Choose Selenium IDE from Extension

Step 4: Create a new Project and name the title for the project

Step 5: Program Output is executed

Step 6: Copy the base URL and Start the recording

RESULT:

Thus, the framework of various open source testing tools have been studied and the
testing tools are implemented.