OBJECT ORIENTED

SOFTWARE
ENGINEERING
PRACTICAL FILE

Aniket Singh
CSE (4th yr.)
04410402714
 S.
Title Date Signature
No.
 EXPERIMENT 1
Aim: Introduction to UML.
What is meant by UML?
UML stands for Unified Modeling Language. UML 2.0 helped extend the original UML specification to
cover a wider portion of software development efforts including agile practices.
 Improved integration between structural models like class diagrams and behavior models like
activity diagrams.
 Added the ability to define a hierarchy and decompose a software system into components and
sub-components.
The original UML specified nine diagrams; UML 2.x brings that number up to 13. The four new
diagrams are called: communication diagram, composite structure diagram, interaction overview
diagram, and timing diagram. It also renamed state chart diagrams to state machine diagrams, also
known as state diagrams.

Types of UML Diagrams

The current UML standards call for 13 different types of diagrams: class, activity, object, use case,
sequence, package, state, component, communication, composite structure, interaction overview,
timing, and deployment. These diagrams are organized into two distinct groups: structural diagrams
and behavioral or interaction diagrams.

Structural UML diagrams

 Class diagram
 Package diagram
 Object diagram
 Component diagram
 Composite structure diagram
 Deployment diagram

Behavioral UML diagrams

 Activity diagram
 Sequence diagram
 Use case diagram
 State diagram
 Interaction overview diagram

Class Diagram
Class diagrams are the backbone of almost every object-oriented method, including UML. They
describe the static structure of a system.

Use Case Diagram

Use case diagrams model the functionality of a system using actors and use cases.

Sequence Diagram
Sequence diagrams describes interactions among classes in terms of an exchange of messages over
time.
Interaction Overview Diagram
Interaction overview diagrams are a combination of activity and sequence diagrams. They model a
sequence of actions and let you deconstruct more complex interactions into manageable occurrences.
You should use the same notation on interaction overview diagrams that you would see on an activity
diagram.

Component Diagram
Component diagrams describe the organization of physical software components, including source
code, run-time (binary) code, and executables.

Deployment Diagram
Deployment diagrams depict the physical resources in a system, including nodes, components, and
connections.
 EXPERIMENT 2
Aim: Draw all UML diagrams for Automatic Teller Machine (ATM)

Problem Statement:
ATM system enhances the old banking system, the earlier method of banking was inconvenient for
the customers because it was in the hands of employees. ATM system provides security and safety to
the users. Customer uses a bank ATM to check balance of his/her bank accounts, deposit funds,
withdraw cash or transfer funds. ATM Technician provides maintenance and repairs to the ATM. This
system also helps the user to validate the pin. The ATM will service one customer at a time. A
customer will be required to insert an ATM card and enter a personal identification number (PIN) -
both of which will be sent to the bank for validation as part of each transaction. The customer will
then be able to perform one or more transactions. The card will be retained in the machine until the
customer indicates that he/she desires no further transactions, at which point it will be returned. The
ATM will communicate each transaction to the bank and obtain verification that it was allowed by the
bank. If the bank determines that the customer's PIN is invalid, the customer will be required to re-
enter the PIN before a transaction can proceed. If the customer is unable to successfully enter the PIN
after three tries, the card will be permanently retained by the machine, and the customer will have to
contact the bank to get it back. If a transaction fails for any reason other than an invalid PIN, the ATM
will display an explanation of the problem, and will then ask the customer whether he/she wants
to do another transaction.

Use Case:
Class Diagram:
Sequence Diagram:
Component Diagram:

Deployment Diagram:
 EXPERIMENT 3
Aim: Draw all UML diagrams for CET

Problem Statement:
Online CET is the process of conducting the common entrance test for the students online. This is to
help the students to write the common entrance test over the internet. This system helps student to
save time and reduces the workload for the examination conductor, evaluation of test is very less time
consuming and reduces error. This application will contain three use case modules: Admin, Staff and
Student. The job of the admin is to add the staff subjects and students information.
Admin assigns subject to staff, the staff adds the questions for the students. Student answers the
question. This helps students to save their time. When a student wants to apply for CET, the student
collects information from sources like newspaper, T.V etc. The student then fills the online
application form for the CET. It is an ambiguous process to fill the form manually. Hence the student
fills the online application form providing all the required details. The student then downloads the
admit card for the CET and to check the centre details for the exam. The examination conduction
authority should be able to retrieve all the answer sheets of the student who appeared for the exam.
The system should also be made in such a way that the test can be checked automatically and result
should be generated accordingly.

Use Case:
Class Diagram:
Sequence Diagram:
Component Diagram:

Deployment Diagram:
 EXPERIMENT 4
Aim: Draw all UML diagrams for Car Rental System
Problem Statement:
The Car Rental System is specialized in renting cars to customers. It is an online system through which
customers can view available cars, register, view profile and book car. A car rental is a vehicle that can
be used temporarily for a fee during a specified period. Getting a rental car helps people get around
despite the fact they do not have access to their own personal vehicle or don't own a vehicle at all.
The individual who needs a car must contact a rental car company and contract out for a vehicle. This
system increases customer retention and simplify vehicle and staff management. The advancement in
Information Technology and internet penetration has greatly enhanced various business processes
and communication between companies (services provider) and their customers of which car rental
industry is not left out. This E-Car Rental System is developed to provide the following services:
enhance business processes, online vehicle reservation, and customer’s registration and group
bookings.

Use Case:
Class Diagram:

Sequence Diagram:
Component Diagram:

Deployment Diagram:
 EXPERIMENT 5
Aim: Draw all the UML diagrams for Employee Management System.
Problem Statement:

The use of paper work in handling some of these processes could lead to human error, papers may
end up in the wrong hands and not forgetting the fact that this is time consuming. A number of
current systems lack employee self-service meaning employees are not able to access and manage
their personal information directly without having to go through their HR departments or their
managers. Another challenge is that multi-national companies will have all the employee information
stored at the headquarters of the company making it difficult to access the employee information
from remote places when needed at short notice. The aforementioned problems can be tackled by
designing and implementing a web based HR management system. This system will maintain
employee information in a database by fully privacy and authority access. The project is aimed at
setting up employee information system about the status of the employee, information about the
employee, salary, login information, the educational background and the work experience in order to
help monitor the performance and achievements of the employee through a password protected
system.

Class Diagram:
Use Case Diagram:

Sequence Diagram:

Deployment Diagram:
 EXPERIMENT 6
Aim: Draw all UML diagrams for order processing system

Problem Statement:
Customer can browse through the product catalogue. Customer can browse through the product
catalog and add the items to shopping cart. He can proceed to checkout as long as his shopping cart is
not empty. Customer will require to login to the system when he proceeds to checkout, or he can
create an account if he not yet have one. The order will charge to the credit card registered in
customers account. Customer needs to provide full name, email address, phone number, credit card
and billing address details when creating an account. Customer can login to the system to maintain his
account information, such as changing phone number, address and credit cards and check the status
of his orders. Upon order received, the sales staff will process the order by changing the customer’s
credit card. Once the order has been charged, he will then mark the order as paid and pass to Courier
Company and deliver them to customer. If the items customer ordered is out of stock, then the order
will be marked as on hold. Once the items arrived, the order will pass to Courier Company for delivery.
Here we are required to create modules for shopping catalog, shopping cart, online registration,
online payment, and payment processing.

Use Case:
Class Diagram:

Sequence Diagram:
Component Diagram:

Deployment Diagram:
 EXPERIMENT 7
Aim: Draw all UML diagrams for Clinic Management System

Problem Statement:
The Clinic Management System is designed for any clinic to replace their existing manual, paper based
system. The new system is to control the following information: patient information, room availability,
staff and operating room schedules, and patient invoices. These services are to be provided in an
efficient, cost effective manner, with the goal of reducing the time and resources currently required
for such tasks. A significant part for the operation of any hospital involves the acquisition,
management and timely retrieval of great volumes of information. This information typically involves
patient personal information and medical history, staff information, room and ward scheduling, staff
scheduling, operating theatre scheduling and various facilities waiting lists. All of this information
must be managed in an efficient and cost wise fashion so that an institution's resources may be
effectively utilized. CMS will automate the management of the clinic making it more efficient and
error free. It aims at standardizing data, consolidating data ensuring data integrity and reducing
inconsistencies.

Use Case:
Class Diagram:

Sequence Diagram:
Component Diagram:

Deployment Diagram:
 EXPERIMENT 8
Aim: Draw all the UML diagrams for Retail Management System.

Problem Statement:
In the retail management system, the retailer will have options for ordering goods, arranging goods
(on the basis of price or product), selling goods and preparing goods. The customer can buy items and
make payment by cash or card. Both the retailer and the customer can access catalogue to choose the
desired item. Once the customer chooses an item, the retailer will check for the availability of the
item. If the item is available with retailer it will be shipped otherwise the retailer will make a request
for the item from the supplier. When the retailer has all the items requested by the customer he will
prepare bill which can be paid by the customer on delivery or online. The items requested by the
retailer from the supplier will be updated in the database and the collective payment will be made in
the end.

Use Case:

Class Diagram:
Sequence Diagram:
Component Diagram:

Deployment Diagram:
 EXPERIMENT 9
Aim: Draw all UML diagrams for Result Management System

Problem Statement:
In a student Result management system the students are made to register first. In the registration the
student is asked to enter about personal details (such as name, phone number, address etc.),
academic year, courses enrolled, and pin for logging in. The teachers of the courses for which the
student has enrolled are asked to enter the marks obtained by the student in his course. The student
on the other hand can check his result by entering the password entered at the time of registration.
The student can see the complete result with various analysis graphs. Options for viewing results in
different formats such as semester wise, year wise, subject wise is available to the student. There
should be an option available to the student viewing the result for checking the result semester wise
and year wise. The percentage should also be shown accordingly i.e. Semester wise and year wise. The
major feature includes an option for student feedback. This is the benefit for the student as they can
give their feedback and also ask for the basic queries. The result should also be available separately as
branch wise and as whole for the complete batch of the same degree course irrespective of their
specific branches. The student can see their college as well as university rank and can compare the
result with other students.
Use Case:
Class Diagram:

Sequence Diagram:
Component Diagram:

Deployment Diagram:
 EXPERIMENT 10
Aim: Draw all the UML diagrams for Library Management System.

Problem Statement:
We have made a library management system in which the student and librarian will have to register
before accessing any information. Once the student has registered, he can issue book, return book,
view catalogue. The librarian can update books, issue books, update student information, and impose
fine. Student will have a choice for the duration of issue of book, based on the type of card used for
issuing book. The fine will be calculated if the student fails to return book on the registered return
date. The fine submitted by the students will be updated by the librarian.

Use Case:
Class Diagram:
Sequence Diagram:

Component Diagram:
Deployment Diagram: