Use Case Diagram

0
USE CASE TOOLS & TESTING TOOL

1. Use Case Diagram:
The main actors of Library Management System in the use case diagram: Borrower and
Librarian who performs the different type of use cases such as Borrower and Librarian entity.
Text Description:
U1: Borrower and Librarian Entity
Using this use case, we can identify the relationship between the Borrower and work of
Librarian.
Mainline Sequence: Work of Librarian
 Make Reservation: Making the reservation for a Book.

 Remove Reservation: Removing the previous Reservation.
 Lend Item: Lending the book to the Reservation.
 Return of Idea: Updating the return idea of the Book.
U2: Librarian Entity
Using the use case, the Librarian can include the details of the borrower for maintenance.
Sub Sequence: Maintenance of the Librarian
 Remove/Update Title: Removing or updating the title of the book on Racks.

 Add Title: Adding the title for the new book on Racks.
 Remove Item: Removing the old edition books on Racks.
 Add Item: Adding the new edition books to Racks.
 Add Borrower: Adding the borrower name for the books which they purchased/
lended.
 Remove/Update Borrower: Removing/Updating the borrower details in their
account.
EX.NO: 1 LIBRARY MANAGEMENT SYSTEM
1
DATE: ..................
----------------------------------------------------------------------------------------------------------------------------
AIM:
To develop a UML diagram to maintenance Library Management system.
Use Case Diagram
2
2. Class Diagram:
This diagram describes the structure of a Library management System classes, their attributes
and the methods and the relationship among the objects.
Text Description:
Classes:
The main classes of the Library Management System are :
 Book Class: manage all the operations of Books, with attributes (ID, Author, Name,
price, Rack no, Status, Edition, Date of Purchase), and Methods (Display Book
Details ( ), Update status ( )).
 Librarian Class: Manage all the operations of Librarian, with attributes (Name,
Password) and methods (Search book ( ), Verify member ( ), Issue book ( ),
Calculate fine ( ), create bill ( ), Return book ( )).
 Transaction Class: Manage all the operations of Transaction, with attributes (Trans id,
Member id, Book id, Date of issue, Due date) and Methods (Create Transaction ( ),
Retrieve Transaction ( ), Delete Transaction ( )).
 Member Record Class: Manage all the operations of Member records, with attributes
(Member id, Type, Date of Membership, no book issued, max book limit, name,
address, phone no) and methods (Retrieve Member ( ), Date of book issued ( ), Date
of return book ( ), Pay Bill ( )).
 Bill Class: Manage all the operations of Bills, with attributes (Bill No, Date, Member
ID, Amount) and Methods (Bill Create ( ), Bill Update ( )).
The Derived classes which are derived from Base Classes are:
 Journals, Magazines, Study Books from Book Class,
 Student and Faculty from Member Record Class.
Association and Link:
 Issues: Librarian can issue the book with their attributes.
 Request: To issue the book, librarian should request the member record with their
attributes.
 Creates: To create a bill with member record with their attributes.
 Creates: To create the transaction Id of the bill paid by the lender using the member
record with their attributes.
 Refers: To verify the bill refer the member with Transaction and their attributes.
 Pays: To pay the bill for lending the books with their member Record attributes.
3
Class Diagram
4
3. Sequence Diagram :
This is the Librarian Sequence Diagram of Library Management System, where

librarian will able to access the Member Record, Book, Transaction ID, Bill.
Text Description:
1. Valid Member: Checks the validity of the member.

2. Get Issued details: Getting the issuing details of Books.
3. Get Member Type: Checking the type (membership) of the Member.
4. Create: Creates the Bill for the book lended.
5. Calculate Fine: Calculating the fine for late return books.
6. Add fine and Member details: Adding fine to the members of late returns
with their records.
7. Fine Paid: Paying the fine by the member.
8. Update Book Details: Updating the return / lended book details.
9. Update Member Record: Updating the return/ lended books on Member
Record
5
Sequence Diagram
6
4. Collaboration Diagram:
The collaboration diagram shows the behavioural aspects of calculating the

fine by the librarian for the member by collaborating the other objects with the
main object Calculate Fine.
Text Description:
 Librarian to Book: Update details by the Librarian object.

 Librarian to Member Record: validating member, get the member type,
updating the member type by Librarian.
 Librarian to Bill: Creating bill, adding fine and member details by
Librarian.
 Bill to Librarian: Fine paid to the Librarian by Bill.
 Librarian to Transaction: Getting the details of the Bill.
7
Collaboration Diagram
8
5. State Chart Diagram
This diagram shows the transition of Library Management System by the

events followed by the states from start to the stop.
Text Description:
Step 1: By using user ID and password, enter into login page.
Step 2: For finding book, on search box enter the book name/id.
Step 3: Request librarian for the book on request box.
Step 4: Return back the book on receive box.
Step 5: Pay fine (if any) while returning back the book.
Step 6: Stop the process by updating the profile and sign out.
9
State Chart Diagram
10
6. Activity Diagram
This diagram shows the activities done when the borrower enquiry for a
books, validate member or not, checking the member record whether the book issued
before or not.
Text Description:
Enquiry Book:
Step 1: Enquire a book.
Step 2: Check availability of the book.
Step 3: if book not available.
Step 4: End Enquiry.
Step 5: If enquired book is available continue with next step.
Validate Member:
Step 6: If valid member, check the no. of books issued.
Step 7: Maximum quota exceeded for issuing books.
Step 8: Book not issued.
Step 9: End the enquire.
If not valid member and Quota available:
Step 10: If not a valid member, register the member by their details.
Step 11: Check the quota available.
Step 12: Add member, book and its issuing detail.
Step 13: Update the status of book.
Step 14: End the Enquire by signing out.
11
Activity Diagram
12
7. Component Diagram
The component diagram represents the independent and subsystems with the ability of
interfaces. Components and artifacts (packages) are wired together with lines representing assembly
and delegation.
Text Description
 LMSDB: Stores the member record/ Database.
Stores the book data base.
Searches from the LMS database.
 Transaction
(Artifact) : Interface between the book database and member record database.
8. Deployment Diagram
The deployment diagram is interrelated with both hardware and software components.
Text Description:
 Client Tier: This node focuses on web browsing by the clients.

 Web Tier: This node focuses on user interfaces on web browsing pages.
 Application Tier: This node focuses on accessing the data by applications.
 Data Tier: This node focuses on procedures which is stored with data’s.
13
Component Diagram
Deployment Diagram
Result:
14
1. Use Case Diagram
The main actors of Automatic Teller Machine in the use case diagram: Operator,
Customer and Bank.
Text Description:
U1: Operator Entity

Using this use case, we can identify the work of operator.
Mainline sequence: work of operator.
 System start up: To start up the system.
 System shutdown: To shutdown the system.
 Maintenance: To maintain the system.
U2: Transaction Entity

Sub line Sequence: Transaction between Customer and Bank.
 Session: customer includes the session for Deposit, Transfer, Inquiry, and Withdrawal.
 Invalid PIN: Extends the duration while getting the invalid PIN.
 Transaction: Acts as a intermediate between the Customer and Bank for Withdraw,
Deposit, Transfer, Inquiry.
15
EX.NO: 2 AUTOMATIC TELLER MACHINE
DATE: ..................
-------------------------------------------------------------------------------------------------------------------------
AIM:
To develop a UML diagram to maintenance Automatic Teller Machine (ATM).
Use Case Diagram:
16
2. Class Diagram:
This diagram describes the structure of Automatic Teller Machine classes, their attributes and
the methods and the relationship among objects.
Text Description:
Classes:
The main classes of Automatic Teller Machine are:
 Bank Class: Manage the operations perform by Bank, with attributes code, Address
and methods Manages ( ), Maintenance ( ).
 Customer Class: Manage all the operations of the customer and their details, with
their attributes Name, Address, DOB and method owns ( ).
 ATM INFO Class: Manage all the operations of the ATM with attributes of their
Location, Managed by and with method Identifies ( ).
 Debit Card Class: Manage all the operations of the Debit card with attributes card
no, owned by and method Access ( ).
 ATM Transaction Class: Manage all the operations of the ATM Transaction with
attributes Transaction ID, date, type and method Modifies ( ).
 Savings Account Class: Manages the operations on savings account with attributes
Account no, balance and methods Debit ( ), Credit ( ).
 Current Account Class: Manages the operations on savings account with attributes
Account no, balance and methods Debit ( ), Credit ( ).
 Transfer class: Manages the operations on Transfer with attributes Amount,
Account No.
 Withdrawal Class: Manages the operations on Withdrawal with attributes Amount
and method Withdrawal ( ).
 Query Class: Manages the operations on Query with attributes Query ID, Type and
method with Processing ( ).
 PIN Validation Class: Manages the operations on PIN Validation with attributes
Old PIN, New PIN and method PIN change ( ).
 Maintains: Bank can maintain the ATM info with their attributes.
 Access/Owns: Customer/Bank can access/owns with the bank/customer details.
 Modifies: modifies by account class the transaction with their attributes.
 Identifiers: identifies the transactions with ATM transaction attributes
17
Class Diagram:
18
3. Sequence Diagram:
This is the ATM sequence diagram where showing the relationship between
CUSTOMER, ATM, ACCOUNT.
Text Description:
1. Insert ATM Card: Inserting the debit/Credit card into ATM.

2. Request PIN: Requesting the PIN to the Customer.
3. PIN Entered: PIN was entered by the Customer.
4. Verify PIN: Bank is verifying the PIN on ATM.
5. PIN OK: Bank extends the message PIN OK for the PIN entered.
6. Request Option: Requesting the option for language/ other details by ATM to the
customer.
7. Option Entered: Option are entered by the customer for the requested option.
8. Request Amount: Requesting the Amount by ATM which the customer wanted.
9. Amount Entered: Amount Entered by the customer to the ATM.
10. Process Transaction: Process the Transaction by the Bank.
11. Transaction successful: Bank extends message Transaction Successful.
12. Dispense Cash: dispensing the cash to the customer on ATM.
13. Request to take cash: ATM machine requesting the customer to take the cash.
14. Take Cash: Customer taking the cash.
15. Request Continuation: ATM requests the customer for further continuation.
16. Terminate: if further no transactions terminate the process.
17. Print Receipt: Printing the receipt by ATM.
19
Sequence Diagram:
20
The collaboration diagram shows the behavioural aspects of Customer, ATM, and Account by
collaborating with other objects.
Text Description:
Customer to ATM: Inserting ATM card, Entering Amount, Taking Cash,

Terminating . to the ATM.
ATM to Customer: Requesting PIN, Requesting option, Requesting the
Amount, . Dispense Cash, Request to take the
cash.
ATM to ACCOUNT: Verifying PIN, Processing the transaction.
ACCOUNT to ATM: Extends the message PIN OK, Transaction Successful.
21
Collaboration Diagram:
22
5. State Chart Diagram:
This diagram shows the transition of Automatic Teller Machine by the events followed by the
events from start to the stop nodes.
Text Description:
Reading Card:
Step1: Reading the card, if card is read successfully, Enter into next step.
Step 2: if card not readable, eject the card.
Reading PIN:
Step 3: After read the card, Read the PIN if PIN read successfully, choose the
transaction.
Step 4: if PIN not Readed press cancel, Eject the card.
Choosing Transaction:
Step 5: After reading PIN, Choose the transaction.
Step 6: Perform the transaction, execute another transaction, and finish the transaction.
Step 7: if Transaction not chosen, press cancel, Eject card.
23
State Chart Diagram:
24
6. Activity Diagram:
This diagram shows the activities done for Customer, ATM machine, Bank.
Text Description:
Invalid Card
Step 1: Insert ATM card.
Step 2: Validate ATM card.
Step3: If card is invalid.
Step 4: Eject and Take the card.
Valid card:
Step 5: If card is valid, Enter PIN.
Step 6: If invalid PIN, eject the card.
Step 7: If PIN is valid, enter the amount.
Step 8: Check the balance, if balance<= amount Take /Debit amount from the account.
Step 9: If balance< amount, show the balance and eject the card.
Step10: After debit the amount, show the balance amount and eject the card.
25
Activity Diagram:
26
7. Component Diagram:
The component diagram represents the independent and subsystems with the ability of interfaces.
Components and artifacts (packages) are wired together with lines representing assembly and
delegation.
Text Description
ATM Module: focuses on cash dispense, card validator, card reader, ATM network.
Card Dispenser: focuses on dispensing cash, according to their demand.
Card validator: focuses on validating the card, by accessing ATM network.
Card Reader: focuses on reading the card.
Text Description:
Nodes:
Card Reader: This node focuses on reading the customer’s card.
Receipt Printer: This node focuses on printing the receipt.
Log Device: This node focuses on Log in/out the device.
Cash dispenser: This node focuses on dispensing the cash to the customer.
Display: this node focuses on the display screen of the ATM.
Keypad: This node focuses on the keyboard by entering the amount/ other details.
Network Interface: This node focuses on interface between the bank and ATM
using . Network.
New Device: This node focuses on the New ATM machine which is connected with the.
Same network.
Bank Server: This node focuses on the bank server which stores the customer’s details.
Artifacts/Packages:
Processor: This package focuses on processor of machine with 200 MHZ Pentium
and . Memory 64 MB.
Network Interface: This package focuses on T1 network.
27
Component Diagram:
Deployment Diagram:
Result:
28
1. Use case Diagram
The main actors of Student Information Management in the use case diagram: Admin,
Staff, Server, DBA.
Text Description:
Student:
Using this use case, we can identify the work of Student by,
Login: To login into student database as a Student.
View details: To view details of Students.
Logout: To logout the student database as a Student.
Server:
Using this use case, we can identify the work of server by,
Allow access: By allowing accessing the database.
Request access: Request for displaying the student database which is stored in server.
Staff:
Using this use case, we can identify the work of staff by,
Login: To login into student database as a staff.
Display: To display the total details of student’s database.
Enter Profile: To enter into the profile of student’s database.
Enter mark: To enter the mark of the student.
DBA:
Using this use case, we can identify the work of Database by,
Update details: By updating the details in students database.
Store data: To store the updated details in the database.
Logout: To logout from the student database.
29
EX.NO: 3 STUDENT INFORMATION MANAGEMENT
DATE: ..................
-------------------------------------------------------------------------------------------------------------------------
AIM:
To develop a UML diagram to maintenance Student Information Management (SIM).
Use Case Diagram:
30
2. Class Diagram:
This diagram describes the structure of Student Information Management classes, their
attributes and the methods and the relationship among objects.
Text Description:
Classes:
The main classes of Student Information Management are:
 Student Class: Manage the operations perform on Student, with attributes Reg no,
Name, and method Login ( ), view details ( ), Logout ( ).
 Staff Class: Manage all the operations of the Staff with their attributes Name, ID
and method Login ( ), Enter Profile ( ), Enter mark ( ) Logout ( ).
 Server Class: Manage all the operations of the server with their attributes ID,
password and methods allow access ( ), display ( ).
 DBA Class: Manage all the operations of the DBA with their attributes ID,
password and method store details ( ), update details ( ).

 Student details: Displays the details of students through system.
 Mark details: Requesting the marks from staff.
 Server: Saves the changes on the server.
 DBA: Accessing the changes from the server and stores in DBA.
31
Class Diagram:
32
This is the Student Information Management sequence diagram where showing the
relationship between Student, Staff, System, Server, DBA.
Text Description:
Login by the student:
1. Login: Login into the system to enter into the student database.
2. Request access: Request to access from the server.
3. Allow access: Allowing to access from the Database.
4. Display: Displays the student details.
5. View details: view their details from the database.
6. Logout: Logout form the system.
Login by the Staff:
1. Login: Login into the system to enter into the student database.
2. Request access: Request to access from the server.
3. Allow access: Allowing to access from the Database.
4. Display: Displays the student details.
5. Enter profile: Enter into the students profile by entering their (Reg. no.).
6. Enter mark: Enter the mark in the student by entering into their profile.
7. Store data: Stores the data, enter by the staff in student database.
8. Update data: Update the data enter by the staff in student database.
9. Provides data: Provides the updated data from the student database.
10.Logout: Logout from the system.
33
Sequence Diagram:
34
The collaboration diagram shows the behavioural aspects of Student, Staff, Server, and DBA by
collaborating with other objects.
Text Description:
Student to SIM: 1: Login, 5: View details, 6: Logout.

SIM to student: 4: Display
Staff to SIM: 10: display
SIM to Staff: 7: Login, 11: Enter Profile, 12: Enter Mark, 16:Logout.
SIM to Server: 2: Request access, 8: Request access.
SIM to DBA: 14: store data
DBA to SIM: 9: Provides data
DBA to Server: 3: Allow access, 13: Allow access
DBA: 15: Update
35
36
This diagram shows the transition of Student Information Management by the events followed
by the events from start to the stop nodes.
Text Description:
Step1: Login into the Student Database.
Step 2: Enter into Profile of the students
Step 3: Enter into view details of the profile.
Step 4: Enter marks on their profile.
Step 5: Update the details on profile.
Step 6: Store the updated details in database.
Step 7: Logout the student Database.
37
38
This diagram shows the activities done for Student, Staff, System, Server, DBA.
Text Description:
Student Accessing from Database
Step 1:Login into database.
Step 2: Requesting access from the server.
Step3: Allowing access from the Database.
Step 4: Displaying their details.
Step 5:View the details of their profile..
Step 6: Logging out from the database.
Staff Accessing from Database
Step 1: Login into database.
Step 2: Requesting access from the server.
Step 4: Displaying their details.
Step 5: Enter the Marks to the student’s profile.
Step 6: Stores the data into database.
39
Activity Diagram:
40
and delegation.
Text Description
Student Information Management component represents the other components such

as Student, Staff, from Database.
Text Description:
Student Information Management node represents the other nodes such as Student,
Staff, from Database.
41
Component Diagram:
Deployment Diagram:
Result:
42
1. Use case Diagram
The main actors of Student Information Management in the use case diagram: Admin,
Member and Visitor.
Text Description:
Admin:
Using this use case, we can identify the work of Admin by,
Login: To login into member database as an Admin.
Active/Deactive Accounts: To activate/ deactivate the accounts of member and visitor.
View profile: To view the profile of the member and visitor.
Member:
Using this use case, we can identify the work of Member by,
Registration: To Register on matrimonial site.
Login: To Login into the matrimonial site.
Search: To search on the matrimonial site.
My Account: To see the Account of the Member in site.
View Profile: To view the Profile of the member in the account.
Partner Alert: To check the alert from the partner.
Online chat: To chat with other member of the site.
Messages: To view the message from other member on site.
Change password: To change the password on the account.
Visitor:
Using this use case, we can identify the work of visitor by,
Registration: To Register on matrimonial site.
Login: To Login into the matrimonial site.
Search: To search on the matrimonial site.
My Account: To see the Account of the Member in site.
View Profile: To view the Profile of the member in the account.
Partner Alert: To check the alert from the partner.
Change password: To change the password on the account.
43
EX.NO: 4 MATRIMONY SERVICE
DATE: ..................
-------------------------------------------------------------------------------------------------------------------------
AIM:
To develop a UML diagram to maintenance Matrimony Service.
Use Case Diagram:
44
2. Class Diagram:
This diagram describes the structure of Matrimony Service classes, their attributes and the
methods and the relationship among objects.
Text Description:
Classes:
The main classes of Student Information Management are:
 Visitor/User Class: Manage the operations perform on Visitor/ User, with attributes
User ID, Matrimony ID, Gender, Age and method Login ( ), Register ( ), Search
Profile ( ), Calculate Moon Sign- Star ( ).
 Calculate Moon sign - star Class: Manage all the operations of the Calculate Moon
sign- Star with their attributes Date, Time zone, Longitude, Latitude, Moon sign,
Star and method Get Result( ).
 Admin Class: Manage all the operations of the Admin with their methods Search
Profile ( ), Add services ( ), Update services ( ).
 Service Class: Manage all the operations of the services with their attributes service
Name, Service no, Service Address.
 Customer Class: Manage all the operations of the customer with their methods
View Profile ( ), Search Profile ( ), View Services ( ), Update Profile ( ).
 Calculate: To calculate the moon sign- star for the User.
 Details: To give the details of customer to the visitor.
 Searches for: To search for the profiles of customer.
 Add services: To add services in the site.
 View services: To view the service by customers.
 View own profile: To view their own profile by the customer.
 Searches for: To search on other profiles.
 Gives: To give feedback for matrimony site.
45
Class Diagram:
46
(a) Profile Registration:
This is the Profile Registration on Matrimony Service sequence diagram where showing
the relationship between User/Visitor, Home, Registration person, Registration physical,
Profile, Database.
Text Description:
Login for Registration:
Step1: Click on Registration on Home.
Step 2: Fill up the data’s of the person for Registration.
Step 3: Fill up the physical data’s of the person on physical registration.
Step 4: Store the data’s on the database.
Step 5: Profile is created on database, now user can login by User ID.
Step 6: Login page opens for the user
Step 7: Login into the site using User ID and Password.
Step 8: Check the username and password of the user.
Step 9: User name and password is valid or not valid.
Step 10: Entered username and password is not valid.
Step 11: Enter valid username and password.
Step 12: Welcome user, now you can edit/ update the profile.
47
Sequence Diagram:
(a) For Profile Registration:
48
Sequence Diagram:
(b) For Edit Profile:
This is the Edit Profile on Matrimony Service sequence diagram where showing the
relationship between User/Visitor, Registration, Photo Upload, Profile, Database.
Text Description:
Login for Edit Profile:
Step1: Login into the site using User ID and Password.
Step 2: Click on the edit profile.
Step 3: Update the information which the user wants.
Step 4: Giving other remaining registration screen.
Step 5: Fill up the form and click update.
Step 6: After updating, it will be stored on database.
Step 7: System displays the message profile updated.
Step 8: Click on photo Upload to upload the photo in the profile.
Step 9: click browse to upload photo from the gallery.
Step 10: Click on upload to upload the browsed photo.
Step 11: After uploading the photo, message displays as photo uploaded.
49
Sequence Diagram:
(b) For Edit Profile:
50
Sequence Diagram:
(c) For Search Profile:
This is the Search Profile on Matrimony Service sequence diagram where showing the
relationship between User/Visitor, Search, Database.
Text Description:
Login for Search Profile:
Step1: Click on search to search the match.
Step 2: Click on the search option.
Step 3: Select the option which the user wants.
Step 4: Giving from matches according to the search of user.
Step 5: Fill up the information which requires in the given form .
Step 6: Search according to the given information given in the form .
Step 7: Gives the result as selected profiles according to the information.
51
Sequence Diagram:
(c) For Search Profile:
52
The collaboration diagram shows the behavioural aspects of Member, Visitor, Admin, Database
by collaborating with other objects.
Text Description:
Member to Database: 1: Registration, 3: Photo, 4: Document to the database.

Database to Member: 2: Search profile from database.
Visitor to Database: 1: Search Profile from database.
Database to Visitor: 2: Document from the database.
Admin to Database: 1: Registration, 2: Photo, 3: Document.
53
54
This diagram shows the transition of Matrimonial site by the events followed by the events from
start to the stop nodes.
Text Description:
Step1: Login into the Matrimony Database.
Step 2: Enter into Profile of the Member
Step 3: Enter into view Photo of the profile.
Step 4: Make payment for the photo which the visitor download.
Step 5: Download the photo from the database.
Step 6: Logout from the Matrimony Database.
55
56
This diagram shows the activities done by Admin to the Visitor and Member Account.
Text Description:
(a) Admin verifies the Member and Visitor account:
Step 1: Login into database.
Step 2: Authenticates the Admin by logging in.
Step3: Verifies the Admin ID and Password.
Step 4: View Member and Visitor Account.
Step 5: Activate and Deactivates the account for both can done by Admin.
57
Activity Diagram:
(a) Admin verifies the Member and Visitor account:
58
Activity Diagram:
This diagram shows the activities done by Admin to the Visitor and Member Account.
Text Description:
(b) Activities of Member account:
Step 1: Login into the database.
Step 2: Authenticates by Admin by logging in.
Step3: Verifies the Member ID and Password.
Step 4: (i). Search for the profile → View the profile → Message them→ Logout.
(ii). View the Partner Alert→ View their profile→ Message them→ Logout.
(iii). View My Account→ Edit Account/Upgrade Account→ Logout.
(iv). Online chat→ Logout.
(v). Change password (if needs) → Logout.
59
Activity Diagram:
(b) Activities of Member account:
60
and delegation.
Text Description:
 Matrimony Service Module: Accessing the site from the database with other modules.
 Search Patterns: Accessing data and includes throughout the site from database for
searching.
 Registration: Accessing data and includes throughout the site from Registration.
 Profile: Accessing data and includes throughout the site on Profile.
 Photograph: Accessing data and includes throughout the site with Photo.
 Document: Accessing data and includes throughout the site with other Documents.
 Security: Accessing the control and encrypts the security purpose for site.
 Persistence: Accessing the control and encrypts the Persistence purpose from the Database.
Text Description:
Matrimony Service node represents the other nodes such as Admin, Member, Visitor.
61
Component Diagram:
Deployment Diagram:
Result:
62
1. Use case Diagram
The main actors of Stock Management System in the use case diagram: Admin,
Customer, Supplier and Database.
Text Description:
Admin:
Using this use case, we can identify the work of Admin by,
 Payment Info: To deal with the payment info of the customer.
 Request access: To access the request of the customer.
 Product available or not: To reply the customer whether the Product is
available or not.
 Product not available: To deal with product is not available.
Customer:
Using this use case, we can identify the work of Customer by,
 Login: To Login into the site.
 Make order: To make order on the site.
 Order confirmed and enters info: To confirm the order and enter the
information of the product.
 Paying Bill: To pay the bill for the purchased order.
 Logout: To Logout from the site.
Supplier:
Using this use case, we can identify the work of supplier by,
 Product available: To deal with, whether the purchase order is available.
 Deliver the product: To deals with, delivering the ordered product.
Database:
Using this use case, we can identify the work of Database by,
 Allow access: To allow the accessing into the stock database.
 Return product info: To return the product available information.
63
EX.NO: 5 STOCK MANAGEMENT SYSTEM
DATE: ..................
----------------------------------------------------------------------------------------------------------------------------
AIM:
To develop a UML diagram to maintenance Stock Management system.
Use Case Diagram
64
2. Class Diagram:
This diagram describes the structure of a Stock management System classes, their attributes and
the methods and the relationship among the objects.
Text Description:
Classes:
The main classes of the Stock Management System are:
 Customer Class: manage all the operations of Customer, with attributes (ID, Name,
Password), and Methods (Op name ( ), make order ( ), Order confirmed ( ), Enter
details ( ), Paying Bill ( ), Logout ( )).
 Admin Class: Manage all the operations of Admin, with attributes (ID, Password) and
methods (Enter customer details ( ), Product info ( ), Check product available ( )).
 Supplier Class: Manage all the operations of Supplier, with attributes (Name, ID) and
Methods (Delivery product ( ), Payment info ( )).
 Data baseClass: Manage all the operations of Database, with attributes (Database No,
password) and methods (Allow access ( ), return product info ( )).
 Ordering Product: To order the product by customer.
 Stores the info: To store the information of stock’s in the database.
 Supplier details: To show the details of supplier.
65
Class Diagram:
66
This sequence diagram where showing the relationship between Customer, Supplier,
Admin and Database.
Text Description:
Step1: Login into the site by the customer.
Step 2: Requesting for access into database by Admin.
Step 3: Allowing to access from the database.
Step 4: Display the page of the site.
Step 5: Making an order of the product by the customer.
Step 6: Status of the product is available or not, by Admin.
Step 7: Checking the product status in database.
Step 8: Returns the Product ID from the database to Admin.
Step 9: Order confirmed and producing customer information by customer.
Step 10: Delivering the product by accessing the information of customer to the
Supplier.
Step 11: Deliver the product to the customer by the supplier.
Step 12: Paying the bill to supplier by the customer.
Step 13: Payment information to the Admin by the supplier.
Step 14: Logging out from the Site.
67
Sequence Diagram:
68
The collaboration diagram shows the behavioural aspects of Customer, Supplier, Admin and
Database by collaborating with other objects.
Text Description:
Customer to Admin: 1: Login into site, 5: Make order of the product,

. 9: Order confirmed &customer info, 15: Logout.
Admin to Customer: 4: Display page, 8: Product available, 14: Product not available.
Customer to Supplier: 12: Paying bill.
Supplier to Customer: 11: Deliver the product
Admin to Supplier: 10: customer info and product delivery.
Supplier to Admin: 13: Payment info.
Admin to Database: 2: Request access, 6: Check the product available.
Database to Admin: 3: Allow access, 7: Return the product info.
69
70
This diagram shows the transition of Stock Management System by the events followed by the
events from start to the stop nodes.
Text Description:
Step1: Login into the Stock Management System Database.
Step 2: Make order of the product.
Step 3: If order of the product is confirmed.
Step 4: Enter the details of customer.
Step 5: Deliver the product to the address.
Step 6: Shares the payment info to the Admin.
Step 7: Logout from the Database.
71
72
This diagram shows the activities done for Customer, Admin, Supplier and Database.
Text Description:
Customer Accessing from Database &check product is available or not:
Step 1: Login into Site by entering Admin page.
Step 2: Admin Request the access from the server.
Step 4: Displaying the Stock on Admin page.
Step 5: Make order by Customer.
Step 6: Check the product availability, if product is not available cancel order.
Step 7: Logout from the site.
Confirm order and paying:
Step 8: If product is available confirm the order by enter the product details.
Step 9: Enter the customer information for product delivery to supplier .
Step10: Deliver the product to customer.
Step 11: Paying the bill for the purchased/delivered product to the supplier.
Step 12: Share the payment information to the Admin.
73
Activity Diagram:
74
The component diagram represents the independent and subsystems with the ability of interfaces.
Components and artifacts (packages) are wired together with lines representing assembly and
delegation.
Text Description
Stock Management System Module: focuses on Customer, Admin, Supplier,
Database
Customer: Focuses on operations done by Customer on site.
Admin: focuses on operations done by Admin on site.
Supplier: focuses on operations done by supplier with admin on site
Database: focuses on database of the site.
Text Description:
Stock Maintenance Node focuses on Customer node, Admin node, Supplier node,
Database node.
75
Component Diagram:
Deployment Diagram:
Result:
76
77
78
Ex.No: STUDY OF OPEN AUTOMATED TESTING TOOL
DATE: (SELENIUM)
To Download Selenium IDE:

 Launch Google Chrome.
 Search for selenium IDE in Google Search.
 Click Selenium IDE and click to add chrome.
79
 Click on the dialog box opens with add extension.
 Go to the top right corner of the chrome and click on the extension for Selenium IDE to
launch the IDE for testing.
80
1. Recording First Test Case:
 Launch Google Chrome and click on Selenium Icon present on the top right corner on the
browser.
 It will launch the default interface of Selenium IDE and Click Record a new test page in a new
project.
 Rename the project as “DEMO TEST”.
81
 Rename the Test Case Base URL as https://www.javatpoint.com/selenium-tutorial .
 Click on the “start recording” button present on the top right corner on the IDE to start
recording the test case.
 It will redirect to “Selenium Tutorial-JavaTpoint” which was provided on the base URL.
82
 Now go to the IDE and click on the “Stop Recording” button to stop the recording actions.
 Now the Text editor box contains the list of all the interactions with the browser.
2. Playing Back the Test Case

 Click on the “Run Current Test” button present on the tool bar menu of the IDE.
 The log pane displays the overall summary of the executed scripts.
83
3. Saving the Test suite
 Click on the save button present on the extreme right corner of the menu bar.
 Save the entire test suite as “Demo Test”.

 The test suite can be found at the location provided in the above steps and the test script
is saved in .SIDE format.
RESULT:
84

Use Case Diagram

Uploaded by

Copyright:

Available Formats

Use Case Diagram

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Use Case Diagram

Uploaded by

Copyright:

Available Formats

0

USE CASE TOOLS & TESTING TOOL

Mainline Sequence: Work of Librarian

 Make Reservation: Making the reservation for a Book.

U2: Librarian Entity

Sub Sequence: Maintenance of the Librarian

 Remove/Update Title: Removing or updating the title of the book on Racks.

EX.NO: 1 LIBRARY MANAGEMENT SYSTEM

Use Case Diagram

This is the Librarian Sequence Diagram of Library Management System, where

1. Valid Member: Checks the validity of the member.

The collaboration diagram shows the behavioural aspects of calculating the

 Librarian to Book: Update details by the Librarian object.

This diagram shows the transition of Library Management System by the

Step 1: By using user ID and password, enter into login page.

Step 3: Request librarian for the book on request box.

Step 4: Return back the book on receive box.

 Client Tier: This node focuses on web browsing by the clients.

U1: Operator Entity

U2: Transaction Entity

Use Case Diagram:

1. Insert ATM Card: Inserting the debit/Credit card into ATM.

Customer to ATM: Inserting ATM card, Entering Amount, Taking Cash,

Step 2: if card not readable, eject the card.

Step 4: if PIN not Readed press cancel, Eject the card.

Step 7: if Transaction not chosen, press cancel, Eject card.

Step 1: Insert ATM card.

Step 2: Validate ATM card.

Step3: If card is invalid.

Step 4: Eject and Take the card.

Step 5: If card is valid, Enter PIN.

Step 6: If invalid PIN, eject the card.

Step 7: If PIN is valid, enter the amount.

Receipt Printer: This node focuses on printing the receipt.

Log Device: This node focuses on Log in/out the device.

Display: this node focuses on the display screen of the ATM.

Network Interface: This package focuses on T1 network.

Use Case Diagram:

Association and Link:

Login by the student:

Login by the Staff:

Student to SIM: 1: Login, 5: View details, 6: Logout.

Step 2: Enter into Profile of the students

Step 3: Enter into view details of the profile.

Step 4: Enter marks on their profile.

Step 5: Update the details on profile.

Step 6: Store the updated details in database.

Step 7: Logout the student Database.

Student Accessing from Database

Step 1:Login into database.

Step 2: Requesting access from the server.

Step3: Allowing access from the Database.

Step 4: Displaying their details.

Step 5:View the details of their profile..

Step 6: Logging out from the database.

Staff Accessing from Database

Step 1: Login into database.

Step 2: Requesting access from the server.

Step3: Allowing access from the Database.