DEPARTMENT OF COMPUTER SCIENCE

AND ENGINEERING

CCS356- OBJECT ORIENTED SOFTWARE ENGINEERING

LABORATORY

REG.NO…………………………………..…
NAME……………………………………….
 SRI RANGAPOOPATHI COLLEGE OF ENGINEERING
Alampoondi-604 151, Gingee - TK

BONAFIDE CERTIFICATE
NAME :

YEAR/SEM : Third / Sixth

BRANCH : Computer Science and Engineering

SUBJECT CODE : CCS356

SUBJECT NAME : OBJECT ORIENTED SOFTWARE ENGINEERING LAB

REGISTER NO. :

Certified that this is a bonafide record of work done by the above student in the
CCS356 – OBJECT ORIENTED SOFTWARE ENGINEERING LABORATORY during the
Academic year

Signature of Staff in charge Head of the Department

Submitted for the Practical Examination Held On

Internal Examiner External Examiner

 TABLE OF CONTENTS
MARKS/
S.NO. DATE EXPERIMENT TITLE SIGN.
10

1. PASSPORT AUTOMATION SYSTEM

2. BOOK MANAGEMENT SYSTEM

3. EXAM REGISTRATION

STOCK MAINTAINENCE SYSTEM

4.
ONLINE COURSE RESERVATION
5. SYSTEM

AIRLINE/RAILWAY RESERVATION
6. SYSTEM
7. SOFTWARE PERSONNEL
MANAGEMENT SYSTEM

8. CREDIT CARD PROCESSING

9. E-BOOK MANAGEMENT SYSTEM

10. RECRUITMENT SYSTEM

11. FOREIGN TRADING SYSTEM

12. CONFERENCE MANAGEMENT SYSTEM

13. BPO MANAGEMENT SYSTEM

14. LIBRARY MANAGEMENT SYSTEM

15. STUDENT INFORMATION SYSTEM

16. COLLEGE INFORMATON SYSTEM

17. HOSTEL MANGEMENT SYSTEM

18. ATM TRANSACTION

EX.NO: 1
PASSPORT AUTOMATION SYSTEM

AIM:
To create an automated system to perform the Passport Process.

HARDWARE REQUIREMENTS:

 Intel Pentium Processor 3

SOFTWARE REQUIREMENTS:

 StarUML

PROJECT DESCRIPTION:

This software is designed for the verification of the passport details of the applicant
by the central computer. The details regarding the passport will be provided to the central
computer and the computer will verify the details of applicant and provide approval to the
office. Then the passport will issue from the office to the applicant.

USE CASE DIAGRAM:

This diagram will contain the actors, use cases which are given below
Actors: Applicant, Enquiry officer.
Use case: Applicant details, Applicant proof, Verification of proof, Issue of
passport, Cancellation of the passport.

ACTIVITY DIAGRAM:

This diagram will have the activities as Start point ,End point, Decision boxes as
given below:
Activities: Enter applicant details, Submission of proof, Verification of details, issue
of passport.
Decision box: Check details whether it is correct or not.

CLASS DIAGRAM:
This diagram consists of the following classes, attributes and their operations.

CLASSES ATTRIBUTES OPERATIONS

Passport management system Verify details, store proof Verification of proof()
Enquiry officer Applicant Details Issue of passport()
Applicant Name, details Apply passport()
SEQUENCE DIAGRAM:

This diagram consists of the objects, messages and return messages.

Object: Applicant, Enquiry officer, Passport management system

COLLABORATION DIAGRAM:

This diagram contains the objects and actors. This will be obtained by the completion
of the sequence diagram and pressing the F5 key.

MERITS:

 Provides convenience.
 Easy usage.
 User friendliness.

DEMERITS:

 Need computer knowledge

 PASSPORT AUTOMATION SYSTEM

USE CASE DIAGRAM:

Applicant Details

Applicant Proof Passsport Management System

Applicant
Verification of Proof
Enquiry officer

Issue of Passport

Cancellation of Passport

CLASS DIAGRAM:

Passport Management System

Verify details
Store proof

Issue of passport()
Verification of proof()
Cancellation of passport()

Applicant
Enquiry Officer Applicant name
Verification of details Applicant details

Issue of passport() Apply passport()

Renewal of passport() Submission of proof()
ACTIVITY DIAGRAM

Details

Proof

Details no
reapply

no
yes
 SEQUENCE DIAGRAM:

Applicant Enquiry Passport

details Officer Management System
1.Appplicant details

Request for Proofs

Submission of Proof s
4.Check for valid Proof

5.Valid Proof

6. Issue Of Passport

COLLABORATION DIAGRAM:

1: Appplicant details
3: Submission of Proofs
Applicant Enquiry
details Officer
2: Request for Proofs
6: Issue Of Passport

5: Valid Proof

4: Check for valid Proof

Passport Management
System

RESULT:

Thus the diagrams for the passport automation system has been designed ,executed and
output is verified.
EX.NO: 2
BOOK MANAGEMENT SYSTEM

AIM:
To draw the diagrams for the Book management system.

HARDWARE REQUIREMENTS:

 Intel Pentium Processor 3

SOFTWARE REQUIREMENTS:

 StarUML

PROJECT DESCRIPTION:

This software is designed for the verification of the details of the student by the
central computer. The details regarding the student will be provided to the central computer
through the administrator in the book bank and the computer will verify the details of student
and provide approval to the office. Then the books that are needed by the student will issue
from the office to the him.

USE CASE DIAGRAM:

This diagram will contain the actors, use cases which are given below
Actors: Student, book bank admin.
Use case: Student details, register, verify student id, return previous books, request
of books, issue of books, check of book availability.

ACTIVITY DIAGRAM:

This diagram will have the activities as Start point, End point, Decision boxes as
given below:
Activities: Verify id, return books, request for books, enter book issue details in
system, issue books

Decision box: Check availability of books whether it is present or not.

 CLASS DIAGRAM:

This diagram consists of the following classes, attributes and their operations.

CLASSES ATTRIBUTES OPERATIONS

Computer Student record, booklist Enter issue(),check
availability()
Stud Student Details Request for books(),
register()
Admin Student Details, book list Verify student id(), issue
books()

SEQUENCE DIAGRAM:

This diagram consists of the objects, messages and return messages.

Object: Stud, admin, computer

COLLABORATION DIAGRAM:

This diagram contains the objects and actors. This will be obtained by the completion
of the sequence diagram and pressing the F5 key.

MERITS:

 Provides convenience.
 Easily understandable.
 User friendliness.

DEMERITS:

 Need computer knowledge.

 It is complex for large scale products.
 BOOK BANK RESISTRATION

USE CASE DIAGRAM:

Student details

Computer
Register

Student
Verify student id
Book bank Admin

Return previous books

Request of books

Check of book availability

Issue new books

CLASS DIAGRAM:
ACTIVITY DIAGRAM:
SEQUENCE DIAGRAM:

student admin computer

1: submit id

2: Verify id

3: Valid id

4: Return books

5: Request for books

6: Check for book availability

7: Book avilabilty Status

8: Enter the book issue

9: Issue new books

\
 COLLABORATION DIAGRAM:

1: submit id
4: Return books
5: Request for books
student admin

9: Issue new books

3: Valid id
2: Verify id
7: Book avilabilty Status
6: Check for book availability
8: Enter the book issue

computer

RESULT:

Thus the diagrams for the Book bank management system has been designed , executed
and output is verified.
EX.NO: 3
EXAM REGISTRATION

AIM:
To draw the diagrams for the Exam registration system.

HARDWARE REQUIREMENTS:

 Intel Pentium Processor 3

SOFTWARE REQUIREMENTS:

 StarUML

PROJECT DESCRIPTION:

This software is designed for the verification of the details of the candidate by the central
computer. The details regarding the candidate will be provided to the central computer
through the administrator and the computer will verify the details of candidate and provide
approval .Then the hall ticket will be issued from the office to the candidate..

USE CASE DIAGRAM:

This diagram will contain the actors, use cases which are given below
Actors: Student, educational officer..
Use case: Student details, student photo, student proof submission of proof
,verification of proof, payment of fees, issue of hall ticket.

ACTIVITY DIAGRAM:

This diagram will have the activities as Start point, End point, Decision boxes as
given below:
Activities: Enter student details , submit student proof and photo, payment of fees,
issue of hall ticket.
Decision box: Verification of proof.

CLASS DIAGRAM:

This diagram consists of the following classes, attributes and their operations.
CLASSES ATTRIBUTES OPERATIONS
Central educational system Student details Print hall ticket(), issue hall
ticket()
Stud Submit details(),submit Payment of fees()
photo()
Eduofficer Enter details Issue hall ticket(), verify
proof()

SEQUENCE DIAGRAM:

This diagram consists of the objects, messages and return messages.

Object: student, educational officer, central education system

COLLABORATION DIAGRAM:

This diagram contains the objects and actors. This will be obtained by the completion
of the sequence diagram and pressing the F5 key.

MERITS:

 Provides convenience for issuing the hall ticket for the candidate.
 Processing the request will be fast.

DEMERITS:
 Need computer knowledge.
.
. USE CASE DIAGRAM:

Student details

Student Photo

Central Education System

Student proof

Submission of Proof
Student Educational
Officer

Verification of Proof

Payment of fees

Issue of hall ticket

 CLASS DIAGRAM:

ACTIVITY DIAGRAM:
SEQUENCE DIAGRAM:

Student Educational Central Education

Officer System

1: Submit student details and photo

2: Enter Student details

3: Valid Proof

4: Pay fees

5: Payment of fees

6: Print hall ticket

7: Issue hall ticket

 COLLABORATION DIAGRAM:

1: Submit student details and photo

5: Payment of fees
Student Educational
Officer
4: Pay fees
7: Issue hall ticket

3: Valid Proof
6: Print hall ticket 2: Enter Student deta

Central Education
System

RESULT:

Thus the diagrams for the Exam registration system

has been designed ,executed and output is verified.
EX.NO: 4
STOCK MAINTAINENCE SYSTEM

AIM:
To create a system to perform the Stock maintenance

HARDWARE REQUIREMENTS:

 Intel Pentium Processor 3

SOFTWARE REQUIREMENTS:

 StarUML

PROJECT DESCRIPTION:

This software is designed for supporting the computerized stock maintainence

System .In this system, the customer can place order and purchase items with the aid of the
stock dealer and central stock system. This orders are verified and the items are delivered to
the customer.

USE CASE DIAGRAM:

This diagram will contain the actors, use cases which are given below
Actors: Customer, Stock dealer, central stock system.
Use case: purchase order, verification of order, payment ,delivery of items..

ACTIVITY DIAGRAM:

This diagram will have the activities as Start point ,End point, Decision boxes as
given below:
Activities: Purchase order, payment , delivery of items.
Decision box: Valid or not

CLASS DIAGRAM:

This diagram consists of the following classes, attributes and their operations.

CLASSES ATTRIBUTES OPERATIONS

Central stock system Store stock details Print bill()
Stock dealer Take order Deliver item()
Customer Place order Payment()

SEQUENCE DIAGRAM:

This diagram consists of the objects, messages and return messages.

Object: Customer, Stock dealer, Central stock system

COLLABORATION DIAGRAM:
 This diagram contains the objects and actors. This will be obtained by the completion
of the sequence diagram and pressing the F5 key.

MERITS:

 Provides convenience.
 Easy usage.
 User friendliness.

DEMERITS:

 Need computer knowledge

 STOCK MAINTAINENCE SYSTEM

USE CASE DIAGRAM:

Purchase order Central stocksystem

Verification of order
Customer

Stock dealer

Payment
Delivery of items

CLASS DIAGRAM:
ACTIVITY DIAGRAM

purchase order

verification ...

valid

Payment

deliver items

COLLABORATION DIAGRAM:

1: purchase order
5: Payment
Customer Stock
dealer
8: Deliver items
4: Give payment d3e:taOilrsder Valid
2: Verify order
7: Print bill
6: Enter payment

Centrak stock
system
SEQUENCE DIAGRAM:

Customer Stock dealer Central stock

system

1.Purchase order

2.Verify order

3.Order valid

4.Give payment details

5.Payment

6.Enter payment

7.Print bill

8.Delivery

RESULT:

Thus the diagrams for the Stock maintenance system has been designed ,executed and
output is verified.
EX.NO: 5
ONLINE COURSE RESERVATION SYSTEM

AIM:
To draw the diagrams for the Online course reservation system.

HARDWARE REQUIREMENTS:

 Intel Pentium Processor 3

SOFTWARE REQUIREMENTS:

 StarUML

PROJECT DESCRIPTION:

This software is designed for supporting online course reservation system.

This system is organized by the central management system . The student first browses and
select the desired course of their choice. The university then checks the availability of the seat
if it is available the student is enrolled for the course.

USE CASE DIAGRAM:

This diagram will contain the actors, use cases which are given below
Actors: Student, University.
Use case: Browse course, select course, register, submit details, verify details, pay
fees, enroll student..

ACTIVITY DIAGRAM:

This diagram will have the activities as Start point ,End point, Decision boxes as
given below:
Activities: Browse course, select course, register course, submit details
Decision box: check availability or not

CLASS DIAGRAM:

This diagram consists of the following classes, attributes and their operations.

CLASSES ATTRIBUTES OPERATIONS

Central management system Store details Verify()
Student Name and address Browse()
University Store details Verify()
SEQUENCE DIAGRAM:
This diagram consists of the objects, messages and return messages.
Object: Student, University, Central management system

COLLABORATION DIAGRAM:

This diagram contains the objects and actors. This will be obtained by the completion
of the sequence diagram and pressing the F5 key.

MERITS:

 Provides convenience.
 Easy usage.
 User friendliness.

DEMERITS:

 Need computer knowledge

 ONLINE COURSE RESERVATION SYSTEM

USE CASE DIAGRAM:

system

Pay fees

Enroll students
CLASS DIAGRAM:
ACTIVITY DIAGRAM:

Browse course

Select course

Check avaliblity

Avalible
Register Course

Submit details

Pay fee

Enroll
SEQUENCE DIAGRAM:

Student University Central management

system

1.Browse course

2.Select course

3.Check availability

4.Available

5.Register

6.Submit details

7.Verify details

8.Issue approval

9.Pay fee

10.Enroll
COLLABORATION DIAGRAM:

1: 1.Browse course
2: 2.Select course
5: 5.Register
6: 6.Submit details
9: 9.Pay fee
Student University

10: 10.Enroll

4: 4.Available
8: 8.Issue approval

3: 3.Check availability
7: 7.Verify details

Central management
system

RESULT:

Thus the diagrams for the Online course reservation system has been designed, executed and
output is verified.
EX.NO: 6 AIRLINE/RAILWAY RESERVATION SYSTEM

AIM:
To draw the diagrams for the E-ticketing system.

HARDWARE REQUIREMENTS:

 Intel Pentium Processor 3

SOFTWARE REQUIREMENTS:

 StarUML

PROJECT DESCRIPTION:

This software is designed for supporting the computerized e-ticketing. This is widely used by
the passenger for reserving the tickets for their travel. This E-ticketing is organized by the
central system. The information is provided from the railway reservation system.

USE CASE DIAGRAM:

This diagram will contain the actors, use cases which are given below
Actors: Passenger, Railway reservation system..
Use case: Status, reservation, cancellation, enter the train number, enter the number
of seats, availability of seats, acceptance of ticket.

ACTIVITY DIAGRAM:

This diagram will have the activities as Start point, End point, Decision boxes as
given below:
Activities: enter the train number, enter the number of seats, acceptance of ticket
,accept seat.
Decision box: Check availability of seats whether it is present or not.

CLASS DIAGRAM:

This diagram consists of the following classes, attributes and their operations.
)
CLASSES ATTRIBUTES OPERATIONS
Central computer Train name, passenger name Reservation(),login()
Passenger Passenger age Login()
R\ailway reservation system Train number Cancellation()
SEQUENCE DIAGRAM:

This diagram consists of the objects, messages and return messages.

Object: Passenger, Railway reservation system, Central computer

COLLABORATION DIAGRAM:

This diagram contains the objects and actors. This will be obtained by the completion
of the sequence diagram and pressing the F5 key.

MERITS:

 Provides convenience.
 Easily understandable.
 User friendliness.
DEMERITS:

 Need computer knowledge.

 It is complex for large scale products.

USE CASE DIAGRAM:

ENTER THE TRAIN NUMBER

CENTRAL COMPUTER

ENTER THE NUMBER OF SEATS

PASSENGER
CHECK FOR AVAILABILITY RAILWAY
RESERVATION SYSTEM

ACCEPTANCE OF
TICKET

CANCELLATION

ACCEPT SEAT
CLASS DIAGRAM:

ACTIVITY DIAGRAM:

N ENTER THE

ENTER THE

NOT AVAILABL
CHECK ACCEPTAN

CHECK
FOR
WAITING
LIST

YES

ACCEPT
SEQUENCE DIAGRAM:
COLLABORATION DIAGRAM:

1: ENTER THE TRAIN NUMBER

2: ENTER NUMBER OF SEATS
6: ACCEPT WAITING LIST
9: PASSENGER DETAILS ENTERED
PASSENG RAILWAY MANAGEMENT
ER SYSTEM

5: DO YOU WANT TO ACCEPT WAITING LIST

8: REQUEST PASSENGER DETAILS
12: ACCEPTANCE OF TICKET

3: CHECK AVAILABILITY OF SEATS

4: SEATS NOT AVAILABLE
10: SAVING DETAILS
7: SEATS ARE AVAILABLE
11: TICKET CONFIRMED

CENTRAL
COMPUTER

RESULT:
Thus the diagrams are successfully
desined,executed and output is verified
 EX.NO: 7
SOFTWARE PERSONNEL MANAGEMENT SYSTEM

AIM:
To draw the diagrams for Software personnel management system

HARDWARE REQUIREMENTS:

 Intel Pentium Processor 3

SOFTWARE REQUIREMENTS:

 StarUML

PROJECT DESCRIPTION:

This software is designed for the process of knowing the details of a person works in a
software company. The details are being stored in the central management system for the
crosschecking the person’s details.

USE CASE DIAGRAM:

This diagram will contain the actors, use cases which are given below
Actors: Employee, HR, Central system.
Use case: Name and address ,qualification ,experience, internet, loan, verification

ACTIVITY DIAGRAM:

This diagram will have the activities as Start point ,End point, Decision boxes as
given below:

Activities: Enter the option to check, enter the salary, enter the working days ,leave
taken ,loss of pay
Decision box: Option to check

CLASS DIAGRAM:

This diagram consists of the following classes, attributes and their operations.

CLASSES ATTRIBUTES OPERATIONS

Central management system Employeename, Tax()
Employeenumber Loan()
Employee1 Employee details Leave taken()
HR checkdetails Loss of pay()
SEQUENCE DIAGRAM:

This diagram consists of the objects, messages and return messages.

Object :Employee, HR, Central system
COLLABORATION DIAGRAM:

This diagram contains the objects and actors. This will be obtained by the completion
of the sequence diagram and pressing the F5 key.

MERITS:

 Provides convenience.
 Easily understandable.
 User friendliness.
DEMERITS:

 Need computer knowledge.

 It is complex for large scale products.

SOFTWARE PERSONNEL MANAGEMENT SYSTEM.

USE CASE DIAGRAM:

NAME AND ADDRESS

QUALIFICATION

EXPERIENCE
EMPLOYEE

HR CENTRAL MANAGEMENT
SYSTEM

INTEREST

LOAN

VERIFICATION

CLASS DIAGRAM:
ACTIVITY DIAGRAM:

SALARY DETAILS

ENTER THE OPTION TO

CHECK

ENTER NUMBER OF
ENTER THE WORKING DAYS
SALARY

LEAVE TAKEN

2%LOAN 5%LOAN

LOSS OF PAY CREDIT FULL

SALARY
SEQUENCE DIAGRAM:

EMPLOYEE HR CENTRAL
SYSTEM

ENTER THE OPTION

ENTER THE SALARY

WHETHER EXCEEDS 10000

SALARY EXCEEDS 10000

CALCULATE TAX AMOUNT

TAX CALCULATED

DISPLAY TAX AMOUNT

ENTER THE LOSS OF PAY

ENTER NUMBER OF LEAVE TAKEN

CALCULATE LOSS OF PAY

DISPLAY LOSS OF PAY

PRINT SALARY
COLLOBORATION DIAGRAM:

1: ENTER THE OPTION

2: ENTER THE SALARY
8: ENTER THE LOSS OF PAY
9: ENTER NUMBER OF LEAVE TAKEN
EMPLOYE HR
E
7: DISPLAY TAX AMOUNT
12: PRINT SALARY
4: SALARY EXCEEDS 10000
6: TAX CALCULATED
11: DISPLAY LOSS OF PAY

3: WHETHER EXCEEDS 10000

5: CALCULATE TAX AMOUNT
10: CALCULATE LOSS OF PAY

CENTRAL
SYSTEM

RESULT:

Thus the diagrams for the Software personnel management system has been designed
,executed and output is verified
EX.NO: 8
CREDIT CARD PROCESSING

AIM:
To draw the diagrams for Credit Card Processing system.

HARDWARE REQUIREMENTS:

 Intel Pentium Processor 3

SOFTWARE REQUIREMENTS:

 StarUML

PROJECT DESCRIPTION:

This software is designed for supporting the computerized credit card processing
System .In this system, the cardholder purchases items and pays bill with the aid of the credit
card. The cashier accepts the card and proceeds for transaction using the central system. The
bill is verified and the items are delivered to the cardholder.

USE CASE DIAGRAM:

This diagram will contain the actors, use cases which are given below
Actors: Cardholder, Cashier, Central system.
Use case: Receive bill, Give card, Enter card number, Enter amount, Transaction,
Receive Receipt

ACTIVITY DIAGRAM:

This diagram will have the activities as Start point ,End point, Decision boxes as
given below:

Activities: Receive Bill, Give card, Enter the card number, Enter the amount,
Transaction, Receive Receipt
Decision box: Verification of card

CLASS DIAGRAM:

This diagram consists of the following classes, attributes and their operations.
CLASSES ATTRIBUTES OPERATIONS
Central system Product name Print bill()
Product details Validate card()
Cashier Product name Enter amount()
Cost of the product Swipe Card()
Print Bill()
Deliver Product()
CardHolder Items Purchased Give card()
Validate Card Sign bill()

SEQUENCE DIAGRAM:

This diagram consists of the objects, messages and return messages.

Object: Card Holder,Cashier , Central system

COLLABORATION DIAGRAM:

This diagram contains the objects and actors. This will be obtained by the completion
of the sequence diagram and pressing the F5 key.

MERITS:

 Provides convenience.
 Easily understandable.
 User friendliness.

DEMERITS:

 Need computer knowledge.

 It is complex for large scale products.

USE CASE DIAGRAM:

 Deliver Product

CLASS DIAGRAM:
ACTIVITY DIAGRAM:
SEQUENCE DIAGRAM:

COLLABORATION DIAGRAM

1: Purchase Product
2: Give card
7: Sign the receipt
Card Cashier
Holder
6: Deliver bill
9: Deliver Product

5: Print bill
3: Swipe Card
4: Enter the amount
8: Accept Receipt

Central
System

RESULT:

Thus the diagrams for the credit card maintenance system has been designed ,executed
and output is verified.
EX.NO: 9
E-BOOK MANAGEMENT SYSTEM

AIM:

To draw the diagrams [usecase, activity, sequence, collaboration, class] for E-book
management system

HARDWARE REQUIREMENTS:

 Intel Pentium Processor 3

SOFTWARE REQUIREMENTS:

 StarUML.

PROJECT DESCRIPTION:

This software is designed to manage the books that were read through the internet. This
consists of the details of the e-book that were read by the user online. It will be controlled by
the central system. This system act as a backup of all details together.

USE CASE DIAGRAM:

This diagram will contain the actors, use cases which are given below
Actors: user, e-book management
Use case: login ,search books, download ,pay for the books, logout

ACTIVITY DIAGRAM:

This diagram will have the activities as Start point ,End point, Decision boxes as
given below:

Activities: Search for the e-book site,search for the book,download book
Decision box: check availability
 CLASS DIAGRAM:

This diagram consists of the following classes, attributes and their operations.

CLASSES ATTRIBUTES OPERATIONS

Internet Enter id Surf books()
Login, logout
User Login ,logout Surf books()
E-book management Verify user Check availability()

SEQUENCE DIAGRAM:

This diagram consists of the objects, messages and retur n messages.

Object: User ,E-book management ,Internet
COLLABORATION DIAGRAM:

This diagram contains the objects and actors. This will be obtai ned by the completion
of the sequence diagram and pressing the F5 key.

MERITS:

 Provides convenience.
 Easily understandable.
 User friendliness.
DEMERITS:

 Need computer knowledge.

 It is complex for large scale products.

USECASE DIAGRAM:

E-BOOK MANAGEMENT SYSTEM

USECASE DIAGRAM:
 E
M

Pay for the

book

Log out

CLASS
DIAGRAM:

B
O
O
K
S
C
E
N
T
R
A
L

S
Y
S
T
ACTIVITY DIAGRAM:
SEQUENCE DIAGRAM

USER INTERNET

LOGIN

CONNECT

DONE

AVAILABLE

BILL
COLLOBORATION DIAGRAM:

1: LOGIN
5: SEARCH BOOK
9: DOWNLOAD
USER E-BOOK
MANAGEMENT
4: DONE
8: DONE
12: SUCCESSFULLY DOWNLOADED
14: ISSUE BILL 2: CONNECT
6: AVAILABILITY
3: PROVIDED 10: VERIFICATION
7: AVAILABLE
11: DOWNLOAD
13: BILL

INTERNE
T

RESULT:
Thus the diagrams for the E-Book management system has been designed ,executed
and output is verified
EX.NO: 10
RECRUITMENT SYSTEM

AIM:
To draw the diagrams for Recruitment system.

HARDWARE REQUIREMENTS:

 Intel Pentium Processor 3

SOFTWARE REQUIREMENTS:

 StarUML

PROJECT DESCRIPTION:

This system is designed to recruit the particular job to the person in a company .It was
controlled by the central management system to manage the details of the particular candidate
that one has to be recruited for a company.

USE CASE DIAGRAM:

This diagram will contain the actors, use cases which are given below
Actors: Applicant, HR, Central management system.
Use case: Aptitude, Group discussion, Technical skills, Personal specification, Short
list, Result

ACTIVITY DIAGRAM:

This diagram will have the activities as Start point ,End point, Decision boxes as
given below:

Activities: Aptitude, Group discussion ,Technical skills,HR

Decision box: Verification of the qualities
CLASS DIAGRAM:

This diagram consists of the following classes, attributes and their operations.

CLASSES ATTRIBUTES OPERATIONS

Candidate Name, qualification Verify()
HR Verification ,resume Select()
Central system Store, update Update()

SEQUENCE DIAGRAM:

This diagram consists of the objects, messages and return messages.

 Object: Candidate, HR, Central system

COLLABORATION DIAGRAM:

This diagram contains the objects and actors. This will be obtained by the completion
of the sequence diagram and pressing the F5 key.

MERITS:

 Provides convenience.
 Easily understandable.
 User friendliness.
DEMERITS:

 Need computer knowledge.

 It is complex for large scale products.

RECRUITMENT SYSTEM

USECASE DIAGRAM:

APTITUD

GROUP SHORT LIST

HR
APPLICAN

TECHNICAL RESUL

CENTRAL

PERSONAL SPECIFICATIOMN
CLASS DIAGRAM:

ACTIVITY DIAGRAM:
SEQUENCE DIAGRAM
COLLOBORATION DIAGRAM:

1: APPLY FOR THE POST

5: APTITUDE
9: TECHNICAL SKILLS
13: ATTENDING GROUP DISCUSSION
17: ATTEND INTERVIEW
APPLICANT HR

4: CALL FOR THE ROUND1

8: CALL FOR ROUND 2
12: CALL FOR GROUP DISCUSSION
16: CALL FOR THE INTERVIEW
20: ISSUE APPOINTMENT ORDER

3: VALID
7: SELECTED
11: SELECTED 2: VERIFIED
15: GOOD 6: SECURE>50%
19: GOOD 10: SECURE>50%
14: CHECK COMMUNICATION SKILLS
18: CHECK CONFIDENCE

CENTRAL SYSTEM

RESULT:
Thus the diagrams for the Recruitment system has been designed ,executed and
output is verified
EX.NO: 11
FOREIGN TRADING SYSTEM

AIM:
To draw the diagrams for Foreign trading system

HARDWARE REQUIREMENTS:

 Intel Pentium Processor 3

SOFTWARE REQUIREMENTS:

 StarUML

PROJECT DESCRIPTION:

This software is designed to maintain the details about the trading system that exists between
the foreign countries. This details are hold by the trading management system.The details to
the system are provided by the customer and the supplier

USE CASE DIAGRAM:

This diagram will contain the actors, use cases which are given below
Actors: Customer, Supplier, Custom officer
Use case: Order of product, Quantity, Specify the amount

ACTIVITY DIAGRAM:

This diagram will have the activities as Start point ,End point, Decision boxes as
given below:

Activities: Order of the product, Specify amount, Payment, Money transfer

Decision box: Check for availability
CLASS DIAGRAM:

This diagram consists of the following classes, attributes and their operations.

CLASSES ATTRIBUTES OPERATIONS

Trading management system Verify product Transport()
Customer Quality Payment()
Supplier Product supply Money transfer()

SEQUENCE DIAGRAM:
 This diagram consists of the objects, messages and return messages.
Object: Customer, Supplier, Trading management system

COLLABORATION DIAGRAM:

This diagram contains the objects and actors. This will be obtained by the completion
of the sequence diagram and pressing the F5 key.

MERITS:

 Provides convenience.
 Easily understandable.
 User friendliness.

DEMERITS:

 Need computer knowledge.

 It is complex for large scale products.

FOREIGN TRADING SYSTEM

USECASE DIAGRAM:

ORDER OF PRODUCT

SUPPLIER TRADING MANAGEMENT

QUANTITY SYSTEM
CUSTOMER

SPECIFY THE AMOUNT

CONVERESION OF MONEY

PAYMENT

SHIP

CUSTOM
DELIVERY OFFICE

FLIGHT
CLASS DIAGRAM:
ACTIVITY DIAGRAM:

ORDER OF
PRODUCT

IF AVAILABLE

SPECIFY
AMOUNT

PAYMENT

MONEY
TRANSFER

MODE OF
TRANSPORT

SHIP FLIGHT

CUSTOM
OFFICE

DELIVERY
SEQUENCE DIAGRAM:

CUSTOMER SUPPLIER TRADING MANAGEMENT SYSTEM

ORDER THE PRODUCT

VERIFY THE PRODUCT

AVAILABILITY OF THE PRODUCT

REQUEST PAYMENT

PAYMENT

MONEY TRANSFE

MODE OF TRANSPORT

CUSTOMS CHECKING

DELIVERY OF THE PRODUCT

COLLOBORATION DIAGRAM:
1: ORDER THE PRODUCT
5: PAYMENT
CUSTOMER SUPPLIER

4: REQUEST PAYMENT
9: DELIVERY OF THE PRODUCT

3: AVAILABILITY OF THE PRODUCT

7: MODE OF TRANSPORT 2: VERIFY THE PRODUCT
8: CUSTOMS CHECKING 6: MONEY TRANSFE

TRADING MANAGEMENT
SYSTEM

RESULT:

Thus the diagrams [Use case, class, activity, sequence, collaboration] for the Trading
management system has been designed ,executed and output is verified
EX.NO: 12
CONFERENCE MANAGEMENT SYSTEM

AIM:
To draw the diagrams for Conference management system

HARDWARE REQUIREMENTS:

 Intel Pentium Processor 3

SOFTWARE REQUIREMENTS:

 StarUML

PROJECT DESCRIPTION:

This software is designed to manage the details of the process that will be taken place in the
conference in a place. It works along with the organizer ,who arranges all these program and
central management system, which consists of the all the details of the member who
participates in the presentation

USE CASE DIAGRAM:

This diagram will contain the actors, use cases which are given below
Actors: Member, Organizer, Central system
Use case: planning, invite delegates, allocate seats, presenting paper, prize
distribution

ACTIVITY DIAGRAM:

This diagram will have the activities as Start point ,End point, Decision boxes as
given below:

Activities: Invite delegates, Allocate seats, Presenting paper, Choose the winner
Decision box: Whether it is reserved or not, Whether the presentation is good or not

CLASS DIAGRAM:

This diagram consists of the following classes, attributes and their operations.

CLASSES ATTRIBUTES OPERATIONS

Member Name, id Presenting paper()
Organiser Member details Allocating seats()
Central management system Member details Updating()

SEQUENCE DIAGRAM:

This diagram consists of the objects, messages and return messages.

Object: Member, Organiser, Central management system

COLLABORATION DIAGRAM:
 This diagram contains the objects and actors. This will be obtained by the completion
of the sequence diagram and pressing the F5 key.

MERITS:

 Provides convenience.
 Easily understandable.
 User friendliness.

DEMERITS:

 Need computer knowledge.

 It is complex for large scale products.

CONFERENCE MANAGEMENT SYSTEM

USECASE DIAGRAM:

PRIZE DISTRIBUTION

CLASS DIAGRAM:
ACTIVITY DIAGRAM:

invite NO
deligates

if reserved

yes

allocate

presenting
paper

if presentation is
good
yes
no choose for
the winner
SEQUENCE DIAGRAM:

MEMBER ORGANIZER CENTRAL SYSTEM

PLANNING

INVITE DELEGATES

CHECK WHETHER THEY ARE RESERVED

RESERVED

ALLOCATION SEAT

PRESENTING PAPER

CHECK WHETHER PRESENTATION IS GOOD

GOOD PRESENTATION

SHORTLISTED

PRIZE DISTRIBUTION
COLLOBORATION DIAGRAM:
1: PLANNING
2: INVITE DELEGATES
6: PRESENTING PAPER
MEMBER ORGANIZER

5: ALLOCATION SEAT
9: SHORTLISTED
10: PRIZE DISTRIBUTION

4: RESERVED
8: GOOD PRESENTATION

3: CHECK WHETHER THEY ARE RESERVED

7: CHECK WHETHER PRESENTATION IS GOOD

CENTRAL
SYSTEM

RESULT:

Thus the diagrams for the Conference management system has been designed
,executed and output is verified
NO: 13
BPO MANAGEMENT SYSTEM

AIM:
To draw the diagrams for BPO management system

HARDWARE REQUIREMENTS:

 Intel Pentium Processor 3

SOFTWARE REQUIREMENTS:

 StarUML

PROJECT DESCRIPTION:

This software is designed to know about the process that were taking place in the
BPO office. This system holds the details of the customer who and all approaches to it. It is
managed by the central system..

USE CASE DIAGRAM:

This diagram will contain the actors, use cases which are given below
Actors: Customer, Server, Central system
Usecase: Product, Voice, NonVoice,Indianoffice,Employee,Feedback.

ACTIVITY DIAGRAM:

This diagram will have the activities as Start point ,End point, Decision boxes as
given below:

Activities: Purchase product, oncall, onchat

Decision box: Option to check

CLASS DIAGRAM:

This diagram consists of the following classes, attributes and their operations.

CLASSES ATTRIBUTES OPERATIONS

Central system Store, update Storing(),updating()
Dealer Employee name Delivery()
Customer details Feedback()
SEQUENCE DIAGRAM:

This diagram consists of the objects, messages and return messages.

Object :Customer, Dealer, Central system

COLLABORATION DIAGRAM:

This diagram contains the objects and actors. This will be obtained by the completion
of the sequence diagram and pressing the F5 key.

MERITS:

 Provides convenience.
 Easily understandable.
 User friendliness.
DEMERITS:

 Need computer knowledge.

 It is complex for large scale products.

BPO MANAGEMENT SYSTEM

USECASE DIAGRAM:

FEEDBACK

CLASS DIAGRAM
ACTIVITY DIAGRAM:

PURCH
ASE

VOICE NON-VOICE
N

ONCA ONCH

IF

ORDE
R

PAYME

DELIVE
SEQUENCE DIAGRAM:

CUSTOMER DEALER CENTRAL SYSTEM

PURCHASE PRODUCT

ENTER OPTION

VOICE CALL

ENQUIRY CUSTOMER DETAILS

IF VALID CUSTOMER

REQUEST FOR PURCHASE

ORDER PRODUCT

ENTER PRODUCT

DELIVER PRODUCT

REQUEST FOR PAYMENT

PAYMENT

REQUEST FOR FEEDBACK

FEEDBACK

REGARDS
COLLABORATION DIAGRAM:

1: PURCHASE PRODUCT
2: ENTER OPTION
3: VOICE CALL
7: ORDER PRODUCT
11: PAYMENT
13: FEEDBACK
CUSTOMER DEALER

6: REQUEST FOR PURCHASE

10: REQUEST FOR PAYMENT
12: REQUEST FOR FEEDBACK
14: REGARDS

4: ENQUIRY CUSTOMER DETAILS

CENTRAL
SYSTEM

RESULT:

Thus the diagrams for the BPO management system has been designed ,executed and
output is verified.
EX.NO: 14
LIBRARY MANAGEMENT SYSTEM

AIM
To design an object oriented model for Library Management System using StarUML
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
A class diagram in the unified modeling language is a type of static structurediagram that
describes the structure of a system by showing the system’s classes, their attributes,
operations and the relationships among objects. The library management system makes
use of the following classes user,
 librarian, system and DBA.

USE CASE DIAGRAM

Use case is a list of actions or events. Steps typically defining the interactions between a
role and a system to achieve a goal. The use case diagram consists of various
functionality performed by actors like user, librarian, system and DBA.

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
DEPLOYMENT DIAGRAM

Deployment diagram is a structure diagram which shows architecture

of the system as deployment of software artifacts to deployment target. It is
the graph of nodes connected by communication association. It is
represented by three dimensional box. The device node is library
management system and execution environment nodes are user, librarian,
system and DBA.

COMPONENT DIAGRAM

Component diagram shows the dependencies and interactions

between software components. Component diagram carries the most
important living actors of the system i.e, user, librarian and DBA.
 library management
system

user DBA
librarian

STATECHART DIAGRAM

State chart diagram is also called as state machine diagram. The state
chart diagram contains the states in the rectangular boxes and the states are
indicated by the dot enclosed. The state chart diagram describes the
behavior of the system. The state chart diagram involves eight stages such as
login, enter details, requesting for book, display book details, search book,
issuebook, return book and logout.

login enter requesting display book

details for book details

logout return book issue book search

book

COLLABORATION DIAGRAM
Like sequence diagram collaboration diagrams are also called as interaction diagram.
Collaboration diagram convey the same informations as sequence diagram but focus on
the object roles instead of the times that messages are sent. Here the actions between
various classes are represented by number format for the case of identification.
SEQUENCE DIAGRAM
A sequence diagram represent the sequence and interactions of a given use case or
scenario. Sequence diagram capture most of the information about the system. It is also
represent in order by which they occur and have the object in the system send message to
one another. Here the sequence starts with interaction between user and the system
followed by database. Once thebook have been selected the next half of sequence starts
between librarian and user followed by database.
.

RESULT
Thus the various UML diagrams for library management system was drawn
successfully.
EX.NO: 15
STUDENT INFORMATION SYSTEM

AIM
To design an object oriented model for Student information system using StarUML
software.

PROBLEM STATEMENT

The student must register by entering the name and password to login the form. The
admin select 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 search 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
The class diagram is the graphical representation of all classes used in the system. The
class diagram is drawn as rectangular box with three components or compartments like
class name, attributes and operations. The student information system makes use of the
following classes like student, staff, system, DBA and server.
COLLABORATION DIAGRAM
A Collaboration diagram represents the collaboration in which is a set of objects related
to achieve a desired outcome. In collaboration, the sequence is indicated by numbering
the message several numbering schemes are available. Login, request access, allow
access, display, view details, logout, login, request access, allow access, display, enter
profile, enter mark, provide data, logout, store data, update data.
SEQUENCE DIAGRAM

A Sequence diagram represent the sequence and interaction of a

given usecase or scenario. Sequence diagram capture most of the information
about the system. Here the sequence starts between the student and the
system. The second half of interactiontakes place between staff and system
then by police and followed
 by database. The student first login to the system and then viewthe details
of the details. Staff login to the system enter mark and enter the details of
the student. DBA store and update the detailsof the student.

COMPONENT DIAGRAM

Component diagram carries the major living actors of thesystem. The

component diagram main purpose is to show the structural relationship between
components of the system.The main component of the system is student information
system and the other components of the system are student, staff and DBA.

student information
system

student staff DBA

USE CASE DIAGRAM

Use case diagram is a graph of actors, a set of use cases, association betweenthe actors
and the use cases and generalization among the cases. Use case diagram is a list of
actions or events. Use case diagram was drawn to represent the static design view of the
system. Steps typically defined the interactions between a role and a system to achieve a
goal. The use case diagram consists of various functionality performed by the actors like
student, staff, system, DBA and server. The use case diagram consists of various
functionality like login, display, enter profile, enter mark, view details, update details,
allow access, request access, store details, logout.
 login

display

enter mark

s tudent
view details

update details

server

DEPLOYMENT DIAGRAM

Deployment diagram shows the configuration of runtime processing

elements and the software components processes and objects that live in
them. Component diagram are used in conjunction with deployment diagram
to show how physical modules code are distributed on various hardware
platform. The processor node in the system is student information system
andthe execution environment nodes or device nodes are student, staff and
DBA.
STATE CHART DIAGRAM
A State chart diagram is also called as state machine diagram. The state chart contains
the states in the rectangular boxes and the states are indicated by the dot enclosed. The
state chart diagram describes the behavior of the system. The state chart involves six
stages such as login, enter mark, enter profile, view details, provide details, update
details, store details and logout.

login enter enter

marks profile

view details

logout store update

details details
ACTIVITY DIAGRAM

Activity diagram are graphical representation of stepwise

activities and actions with support for choice, interaction and concurrency.
Here in the activity diagram the student login to the system and view the
details of the student. The staff login to the system for entering the student
details and update the details in thedatabase. The final interaction is the DBA
store the details of the student.

RESULT

Thus the various UML diagrams for student informationsystem were

drawn was generated successfully
 EX.NO: 16
COLLEGE INFORMATON SYSTEM

AIM
To develop a College Information System using StarUML Software and to implement the
software in Java.

PROBLEM ANALYSIS AND PROJECT PLANNING

A College Information System (CIS) is a software application for educational
establishments to manage university data. College Information System provide
capabilities for entering student test and other assessment scores, building schedules,
tracking student attendance, and managing many other university-related data needs in a
school, college or university.

PROBLEM STATEMENT
a. Effective for Administration Purpose
b. Cheap
c. Better Service

USE CASE DIAGRAM:

A use case is a methodology used in system analysis to identify, clarify, and organize
system requirements. The use case is made up of a set of possible sequences of interactions
between systems and users in a particular environment and related to a particular goal. It is
represented using ellipse. Actor is any external entity that makes use of the system being
modeled. It is represented using stick figure

For Administrator:

Admin

Add

Admin
Database
Delete

Update Student
College

DOCUMENTATION OF USE CASE DIAGRAM

The actors in this use case diagram are Admin, Student, Database. The use cases are the
activities performed by actors.
a. Admin register login, and store the student records details in database.
b. Student Register from the Student Login process.
c. Then the database is searched for details and verified.
d. Database stores the details and returns acknowledgement
CLASS DIAGRAM:
A class diagram in the unified modeling language (UML) is a type of static structure
diagram that describes the structure of a system by showing the system's classes, their
attributes, and the relationships between the classes. It is represented using a rectangle with
three compartments. Top compartment have the class name, middle compartment the
attributes and the bottom compartment with operations.
DOCUMENTATION OF CLASS DIAGRAM
This class diagram has three classes Login, Student details and Update details in database.
a. Students – is the class name. Its attributes are name, Address, DOB, Gender, College,
Subjects, Semester, Year, Degree, and Branch. The operations Performed in the students
class, Store database and Update.
b. Administration– is the class name. Its attributes are Login, Password and database.
The operations performed are Student Details store in database and send acknowledgement.
c. Database – is the class name. The operations performed are storing Search and storing
the values.
SEQUENCE DIAGRAM:
A sequence diagram in Unified Modeling Language (UML) is a kind of interaction diagram
that shows how processes operate with one another and in what order. It is a construct of a
Message Sequence Chart. There are two dimensions.
1. Veritcal dimension-represent time.
2. Horizontal dimension-represent different objects.
For Validity:
 Admin/Student Validation Database

1 : Request for validity()

2 : Check for validity()

3 : Validate()

4 : Successful validate()

For Administrator:

Login ReqAdd Student ReqUpdate Student Database

Admin

1 : Enter Credentials for login( )

2 : Check for validity()

3 : Valid user()

: Successful login()

: Enter details for adding a student()

6 : Add()

7 : Successful()

: Successfully added()

: Enter credentials for update student record()

10 : Update()

11 : Successful()

12 : Successfully Updated()
 For Student:

Student Login ReqView Profile

ReqView Details Database

1 : Enter credentials for login()

2 : Check for Validity()

3 : Valid()

: Valid login()
: Request for view profile()

6 : Request()

7 : Set Details()

: Get the details()

: Request for view Details()

10 : Request()

11 : Set Details()

12 : Get the Details()

DOCUMENTATION OF SEQUENCE DIAGRAM

The sequence diagram describes the sequence of steps to show
a. The Admin login and registering for add Student Details.
b. The verification done by the interface and sending acknowledgement for
registration.
c. Searching the database with login and displaying it for maintenance.

COLLABRATION DIAGRAM:
A collaboration diagram, also called a communication diagram or interaction diagram. A
sophisticated modeling tool can easily convert a collaboration diagram into a sequence
diagram and the vice. A collaboration diagram resembles a flowchart that portrays the roles,
functionality and behavior of individual objects as well as the overall operation of the system
in real time
For Validity:

Database
3 : Validate()

2 : Check for validity()

Validation

1 : Request for validity()

4 : Successful validate()

Admin/Student

For Administrator:
Database

3 : Valid user()
6 : Add()
10 : Update()

7 : Successful() 2 : Check for validity()

11 : Successful()
Login

ReqAdd Student ReqUpdate Student

1 : Enter Credentials for login()

8 : Successfully added()
4 : Successful login()
12 : Successfully Updated()

9 : Enter credentials for update student record()

5 : Enter details for adding a student()

Admin

For Student:
 Database

3 : Valid()
6 : Request() 2 : Check for Validity()

7 : Set Details1(0) : Request()

Login
11 : Set Details()

ReqView Profile

ReqView Details
8 : Get the details()

4 : Valid login()

1 : Enter credentials for login()

Object1
5 : Request for view profile()

9 : Request for view Details()

12 : Get the Details()

Student

DOCUMENTATION OF COLLABRATION DIAGRAM

The collaboration diagram is to show how the Student registers and the authorities maintain
the details of the registered students in the Information system. Here the sequence is
numbered according to the flow of execution.
ACTIVITY DIAGRAM:
Activity diagrams are graphical representations of workflows of stepwise activities and
actions with support for choice, iteration and concurrency. In the Unified Modeling
Language, activity diagrams can be used to describe the business and operational step- by-
step workflows of components in a system. An activity diagram shows the overall flow of
control. An activity is shown as an rounded box containing the name of the operation.

DOCUMENTATION OF ACTIVITY DIAGRAM

This activity diagram flow of stepwise activities performed in recruitment system.

a. The student details are Add and stored in database.

b. Select the course from the given Course by student.

c. Search Profile and Result with login and if data present in the database.

d. The searched data is displayed if available and then Log Out.

 Login

Student Registration

back to registration

If No
Yes

Select Course

Profile

Result

Fee

Library

Log Out

COMPONENT DIAGRAM:
The component diagram's main purpose is to show the structural relationships between the
components of a system. It is represented by boxed figure. Dependencies are represented by
communication association.
 User

IUser

<<application>>
Management <<infrastructure>>
Persistence

Request

IRequest

DB

JDBC

DOCUMENTATION OF COMPONENT DIAGRAM

The main component in this component diagram is Student Information system. And register,
User and Manage, Request details are the components comes under the main component.

DEPLOYMENT DIAGRAM:
A deployment diagram in the unified modeling language serves to model the physical
deployment of artifacts on deployment targets. Deployment Diagrams show "the allocation of
artifacts to nodes according to the Deployments defined between them. It is represented by 3-
dimentional box. Dependencies are represented by communication association.
DOCUMENTATION OF DEPLOYMENT DIAGRAM
The processor in this deployment diagram is the University Information System which is the
main part and the Student are the Admin, verify and search which are the some of the main
activities performed in the system.

RESULT:
Thus the various UML diagrams for college information system were drawn and code was
generated successfully.
 EX.NO:17 HOSTEL MANGEMENT SYSTEM

Hostel Management
AIM

To develop a Hostel Management using Staruml Software and to implement the software in
Java.
PROBLEM ANALYSIS AND PROJECT PLANNING

Hostel Management System is a Customize and user-friendly software for Hostel. It

has been designed to automate, manage and look after the over-all processing of even very
large hostel. It is capable of managing Enquiry details, Student Details, Payment Details etc.
Hostel Management System is a Customize and user-friendly software for
Hostel which provide hostel information, hostel room information, hostel accounts
information.

Hostel Management Software Systemis offering a maximum of stability, cost-

effectiveness and usability. It provides the most flexible and adaptable standards management
system software solutions for hostel.
PROBLEM STATEMENT
a. Effective for Administration Purpose
b. Cheap
c. Better Service
UML DIAGRAMS:
The following UML diagrams describe the process involved in the online system
1. Use case diagram
2. Class diagram
3. Sequence diagram
4. Collaboration diagram
5. Activity diagram
6. Component diagram
7. Activity diagram
8. Deployment Diagram

USE CASE DIAGRAM:

A use case is a methodology used in system analysis to identify, clarify, and organize
system requirements. The use case is made up of a set of possible sequences of interactions
between systems and users in a particular environment and related to a particular goal. It is
represented using ellipse. Actor is any external entity that makes use of the system being
modeled. It is represented using stick figure.
 collect& store the student details

store the availability of hostel&

room details

generate & update the attendance

details

calculate& generate report for

mess expenditure detail for ...
aadministrator
db manager

calculate & generate report for

mess expenditure detail for ...

request for mess bill report

check and verify mess bill report mess bill calculation

update the payment details

display the mess bill report to the

student

payment of mess bill

student
CLASS DIAGRAM:
A class diagram in the unified modeling language (UML) is a type of static structure

diagram that describes the structure of a system by showing the system's classes, their
attributes, and the relationships between the classes. It is represented using a rectangle with
three compartments.
Top compartment have the class name, middle compartment the attributes and the bottom
compartment with operations.

SEQUENCE DIAGRAM:
A sequence diagram in Unified Modeling Language (UML) is a kind of interaction diagram
that shows how processes operate with one another and in what order. It is a construct of a
Message Sequence Chart. There are two dimensions.
1. Vertical dimension-represent time.
2. Horizontal dimension-represent different objects
 student Administrator
DB manager
give details
enter student details

update

enter mess item & eexpenditure details

update

calculate(total mess expenditure)

enter attedance details

update

request for mess bill expenditure

calculate(total mess item expenditure/total no of student)

publish mess fees details

pay the fees enter the payment details

update

COLLABRATION DIAGRAM:
A collaboration diagram, also called a communication diagram or interaction diagram. A
sophisticated modeling tool can easily convert a collaboration diagram into a sequence
diagram and the vice. A collaboration diagram resembles a flowchart that portrays the roles,
functionality and behavior of individual objects as well as the overall operation of the system
in real time
 1: give details
13: pay the fees
student Administra
tor
11: publish

3: update
5: update12: mess fees details
6: calculate(total mess expenditure)
8: update

10: calculate(total mess item expenditure/t2o: taelnnteor osftusdtuednet ndte) tails

15: upda4t:eenter mess item & eexpenditure details

7: enter attedance details
9: request for mess bill expenditure
14: enter the payment details

DB manager

State Diagram:

State diagram are a familiar technique to describe the behavior of a system. They
describe all of the possible states that a particular object can get into and hoe the objects state
changes as a result of events that reach the object.
 get details

CHeking all details correct processing

update details

some details missing

mess details
details verified update
details obtained

Waiting missing calculating calculate

details obtained mess expenditure

mess bill

Reporting
generated report

stop

ACTIVITY DIAGRAM:
Activity diagrams are graphical representations of workflows of stepwise activities and
actions with support for choice, iteration and concurrency. In the Unified Modeling
Language, activity diagrams can be used to describe the business and operational step- by-
step workflows of components in a system. An activity diagram shows the overall flow of
control. An activity is shown as an rounded box containing the name of the operation.

RESULT
Thus the various UML diagrams for hostel management system were drawn and code was
generated successfully
 ATM TRANSACTION
EX.NO:18

AIM:
To create a system to perform Bank ATM transaction
Problem analysis and project planning
Introduction
Banking is one of the common and day to day attribute of life. Nowadays it is totally
different from that existed a few years ago banking has become completely computerized
new facilities such as credit cards, debit cards & ATM has been introduced. ATM is
automatic teller machine which is basically used to withdraw money from an account.

Class diagram for ATM system

Use Case Diagram
Activity Diagram

Insert
card

Enter
PIN

Connect Not connected

Enter
transition
Any more transaction

No more transaction

Remove
card
Sequence Diagram

A : Atm ac : B : Bank
machine account client
1: Insert card

Insert PIN

3 : Enter PIN

4 : Verification

5 : PIN ok

: Request for transaction

: Process transaction

8 : Enter amount

9 : Amount entered

10 : Withdrawal

: Withdrawal success

: Dispense cash

: take cash

: Terminate

: Print slip

16 : Eject card
Collaboration Diagram
 Component Diagram
ATM.exe

Card Reader Cash Dispenser

Card Reader ATM Screen

Card
dispenser

ATM Screen
Deployment Diagram
State Diagram

RESULT
Thus the various UML diagrams for ATM system were drawn and code was generated successfully.