INDEX

Sno. Date of program Title of program Page no. Teacher Sign

1 28/06/2024 ATM SYSTEM 05

2 05/07/2024 PAYROLL MANAGEMENT 10

SYSTEM

3 08/07/2024 STUDENT INFORMATION 14

SYSTEM

4 12/07/2024 QUIZ SYSTEM 17

5 15/07/2024 LIBRARY MANAGEMENT 20

SYSTEM

6 22/07/2024 HEALTH CARE SYSTEM 23

7 23/07/2024 RAILWAY RESERVATION 26

SYSTEM

8 29/07/2024 ONLINE BOOK SHOPPING 29

SYSTEM

9 05/08/2024 BANKING SYSTEM 32

10 12/08/2024 PASSPORT AUTOMATION 35

SYSTEM

11 20/08/2024 EXAM REGISTRATION 38

SYSTEM

12 28/08/2024 INVENTORY 41
MAINTAINANCE SYSTEM

13 05/09/2024 E – TICKETING SYSTEM 44

14 12/09/2024 CREDIT CARD 47

PROCESSING

15 19/09/2024 E - BOOK MANAGEMENT 50

SYSTEM

16 26/09/2024 RECRUITMENT SYSTEM 53

1
 INTRODUCTION TO OOAD LAB
CASE Tools

CASE stands for Computer Aided Software Engineering. It means development and
maintenance of software projects with help of various automated software tools.

CASE tools are set of software application programs, which are used to automate SDLC
activities. CASE tools are used by software project managers, analysts and engineers to
develop software system.

STAR UML

STAR UML is a software engineering tool for system modeling using the Unified Modeling Language,
as well as Systems Modeling Language, and classical modeling notations. It is published by
MKLabs and is available on Windows, Linux and MacOS.

Refer the link

http://www.dpi.ufv.br/projetos/geoprofile/tutoriais/StarUML_Tutorial_english.pdf

The Unified Modeling Language

The Unified Modeling Language™ (UML®) is a standard visual modeling language
intended to be used for modeling business and similar processes, analysis, design, and
implementation of software-based systems.

UML is a common language for business analysts, software architects and developers
used to describe, specify, design, and document existing or new business processes, structure
and behavior of artifacts of software systems.

UML can be applied to diverse application domains (e.g., banking, finance, internet,
aerospace, healthcare, etc.) It can be used with all major object and component software
development methods and for various implementation platforms (e.g., J2EE, .NET).

UML is a standard modeling language, not a software development process. UML 1.4.2
Specification explained that process:
• provides guidance as to the order of a team’s activities
• specifies what artifacts should be developed
• Directs the tasks of individual developers and the team as a whole, and offers criteria
for monitoring and measuring a project’s products and activities.

List of UML Diagram Types

Types of UML diagrams with structure diagrams coming first and behavioral diagrams
starting from position 8. Click on any diagram type to visit that specific diagram type’s
description.

2
 1. Class Diagram
2. Component Diagram
3. Deployment Diagram
4. Use Case Diagram
5. Activity Diagram
6. State Machine Diagram
7. Sequence Diagram

Use Case Diagram

Use-case diagrams graphically depict system behavior (use cases). These diagrams present a
high level view of how the system is used as viewed from an outsiders (actor’s) perspective.
A use-case diagram may depict all or some of the use cases of a system.

A use-case diagram can contain:

• Actors ("things" outside the system)
• Use cases (system boundaries identifying what the system should do) •
Interactions or relationships between actors and use cases in the
system.
• Including the associations, dependencies, and generalizations.
Use-case diagrams can be used during analysis to capture the system requirements and to
understand how the system should work. During the design phase, you can use use-case
diagrams to specify the behavior of the system as implemented.
You can display and modify the properties and relationships of a use case through the
Use-Case Specification.
ACTIVITY DIAGRAM
Activity diagrams provide a way to model the workflow of a business process. You can also use
activity diagrams to model code-specific information such as a class operation.

Activity diagrams are very similar to a flowchart because you can model a workflow from
activity to activity. An activity diagram is basically a special case of a state machine in which
most of the states are activities and most of the transitions are implicitly triggered by
completion of the actions in the source activities. The main difference between activity
diagrams and state charts is activity diagrams are activity centric, while state charts are state
centric. An activity diagram is typically used for modeling the sequence of activities in a
process, whereas a state chart is better suited to model the discrete stages of an objects
lifetime.
Activity diagrams provide a way to model the workflow of a business process. You can also use
activity diagrams to model code-specific information such as a class operation.
A
Activity Diagram Tools
You can use the following tools on the activity diagram toolbox to model activity diagrams:

3
 • Decisions
• Activity
• End State
• Object
• Object Flow
• Start State
• States
• Synchronizations
• Transitions
CLASS DIAGRAM
The class diagram class allows you to add, retrieve and delete classes and categories
to and from a class diagram. The class diagram class has a set of properties and methods that
apply specifically to class diagrams. In addition, it inherits all diagram class properties and
methods.
COLLABORATION DIAGRAMS
Collaboration diagrams and sequence diagrams are alternate representations of an
interaction. A collaboration diagram is an interaction diagram that shows the order of
messages that implement an operation or a transaction. A sequence diagram shows object
interaction in a time-based sequence.

Collaboration diagrams show objects, their links, and their messages. They can also
contain simple class instances and class utility instances. Each collaboration diagram provides
a view of the interactions or structural relationships that occur between objects and object-
like entities in the current model.

COMPONENT DIAGRAM
A component diagram shows the allocation of classes and objects to components in
the physical design of a system. A component diagram may represent all or part of the
component architecture of a system.
The dependency relationship indicates that one entity in a component diagram uses
the services or facilities of another. Dependencies in the component diagram represent
compilation dependencies. The dependency relationship may also be used to show calling
dependencies among components, using dependency arrows from components to interfaces
on other components.

4
Ex. No:1 ATM SYSTEM
Date :

AIM:
To model the "ATM System" using the software Star UML with various UML (Unified Modeling
Language) diagrams.

USECASE DIAGRAM

Deposit amount

Check PIN card

Withdraw amount

ATM

Review details
Client

Update details

System/bank

Terminate transaction

Cancel transaction

5
CLASS DIAGRAM

6
ACTIVITY DIAGRAM

START

WIthdraw

Insert Atm Card

Enter PIN

Check PIN

Valid

Enter Amount

Balance NO Terminate
sufficient transaction

Withdraw
Amount
STOP

Update
account

7
SEQUENCE DIAGRAM

:Client :ATM :Controller :Database

Insert Card

Verify PIN

Invalid PIN

Eject card

Request amount

Enter amount to deposit

Deposit amount

Update account
Enter amount to withdraw

Withdraw if balance is sufficient

Inform client if balance is sufficient

Close transaction

8
COLLABORATION DIAGRAM

1: Insert card
5: Enter amount to deposit
8: Enter amount to withdraw
: Client : ATM

4: Request amount
11: Close transaction

3: Invalid PIN

2: Very PIN 10: Inform client if balance is in sufficient

6: Deposit amount
7: Update account
: Controll
9: Withdraw if balance is sufficient
er

: Databas
e

COMPONENT DIAGRAM
ATM
Client

Deposit amount

RESULT: Thus the ATM System application was successfully designed and the output was
verified.

9
Ex. No: 2 PAYROLL MANAGEMENT SYSTEM
Date :

AIM :

To model the " PAYROLL MANAGEMENT SYSTEM" using the software Star UML with various
UML (Unified Modeling Language) diagrams.

USECASE DIAGRAM

Employee information

Time card information

Employee Administrator

Purcharse offres

Payment method details

Reports

Management and updation

Payroll generation

10
CLASS DIAGRAM

ACTIVITY DIAGRAM

Start

Maintain employee
Check for
info and assign project
Login schedule

Payroll
generation
Submit Id ,time card
and payment details

Stop

11
SEQUENCE DIAGRAM

1: Enter employee ID and information

3: Send details

4: Access and update database

5: Submit card information,hours worked,purchase orders and reports

6: Request Payment

7: If hourly employee then pay on hourly rate

8: Payment for who worked more than 8 hours on friday

9: Pay flat salary on the last day of the month

10: Submit time card and purchase orders

11: Pay commission based on sales

:Employee :AutomatedResponse :Project Manager :Administrator

(Adminnistrator)

2: Verify employee details 12: Access database to notify changes

12
COLLABORATION DIAGRAM

1: Enter employee ID and information

5: Submit card information,hours worked,purchase orders and reports
6: Request Payment
10: Submit time card and purchase orders
: Employ
ee : AutomatedResponse
( Adminnistrator )
7: If hourly employee then pay on hourly rate
8: Payment for who worked more than 8 hours on friday
9: Pay flat salary on the last day of the month
11: Pay commission based on sales

12: Access database to notify changes 4: Access and update database

2: Verify employee details

3: Send details : Adminis

trator
: Project
Manager

COMPONENT DIAGRAM

Automated
Employee
Response

Administrator

RESULT:
Thus the PAYROLL MANAGEMENT SYSTEM application was successfully designed and the
output was verified.

13
Ex. No: 3 STUDENT INFORMATION SYSTEM
Date :

Aim :
• To draw the diagrams [usecase,class,sequence] for the Student Information system.
• Student information systems provide capabilities for registering students in courses;
documenting grading, transcripts, results of student tests and other assessment
scores; building student schedules; tracking student attendance; and managing many
other student-related data needs in a school.

Use-Case Diagram :

14
Class Diagram :

15
Sequence Diagram :

Result :
Thus the diagrams [Use case, class, activity, sequence, collaboration, Activity] for the
Student Information system has been designed, executed and output is verified

16
Ex. No: 4 QUIZ SYSTEM
Date :

Aim :
• To draw the diagrams[ use case, class ,sequence] for the Quiz system.
• Quizzes are set up to actually test knowledge or identify a person's attributes. Some
companies use online quizzes as an efficient way of testing a potential hire's knowledge
without that candidate needing to travel.

Use-Case Diagram :

17
Class Diagram :

18
Sequence Diagram :

Result :
Thus the diagrams [Use case, class, activity, sequence, collaboration, Activity] for the
Quiz system has been designed, executed and output is verified

19
Ex. No: 5 LIBRARY MANAGEMENT SYSTEM
Date :

Aim :
• To draw the diagrams[usecase,class,sequence] for the Library Management system.
• The library system is used for uploading and downloading books.
• The books are categorized in a specific form which will help the user to refer his
required book easily.

Use-Case Diagram :

20
Class Diagram :

21
Sequence Diagram :

Result :
Thus the diagrams [Use case, class, activity, sequence, collaboration, Activity] for the
Library Management system has been designed, executed and output is verified

22
Ex. No: 6 HEALTH CARE SYSTEM

Date :

Aim :
• To draw the diagrams [usecase,sequence,class] for the Health Care system.
• Healthcare systems are complex and there are many things you need to know about
types of hospital systems, patient care, insurance, healthcare providers and legal
issues.

Use-Case Diagram :

23
Class Diagram :

24
Sequence Diagram :

Result :
Thus the diagrams [Use case, class, activity, sequence, collaboration, Activity] for the
Health Care system has been designed, executed and output is verified

25
Ex. No: 7 RAILWAY RESERVATION SYSTEM

Date :

Aim :
• To draw the diagrams [usecase,sequence,class] for the Railway reservation System.
• To describe the railway reservation system which provides the train timing details,
reservation, billing and cancellation on various types of reservation

Use-Case Diagram :

26
Class Diagram :

27
Sequence Diagram :

Result :
Thus the diagrams [Use case, class, activity, sequence, collaboration, Activity] for the
Railway Resrvation system has been designed, executed and output is verified

28
Ex. No: 8 ONLINE BOOK SHOPPING SYSTEM
Date :

Aim :
• To draw the diagrams[usecase,sequence,class] for the Online Book Shopping System.
• Site content for online textbook system that allows ordinary users to conveniently at
home, use the Internet features, easy to find books you want.

Use-Case Diagram :

29
Class Diagram :

30
Sequence Diagram :

Result :
Thus the diagrams [Use case, class, activity, sequence, collaboration, Activity] for the
Online Book Shopping system has been designed, executed and output is verified

31
Ex. No: 9 BANKING SYSTEM

Date :

Aim :
• To draw the diagrams [usecase,sequence,class] for the Banking System.
• It is an electronic payment system that enables customers of a bank or other financial
institution to conduct a range of financial transactions through the financial
institution's website.

Use-Case Diagram :

32
Class Diagram :

33
Sequence Diagram :

Result :
Thus the diagrams [Use case, class, activity, sequence, collaboration, Activity] for the
Banking system has been designed, executed and output is verified

34
Ex. No: 10 PASSPORT AUTOMATION SYSTEM
Date :

Aim :
• To draw the diagrams[usecase,sequence,class] for the Passport automation system.
• Passport Automation System is an interface between the Applicant and the Authority
responsible for the Issue of Passport

.Use-Case Diagram :

35
Class Diagram :

36
Sequence Diagram :

Result :
Thus the diagrams [Use case, class, activity, sequence, collaboration, Activity] for the
Passport Automation system has been designed, executed and output is verified

37
Ex. No: 11 EXAM REGISTRATION SYSTEM
Date :

Aim :
• To draw the diagrams[usecase,sequence,class] for the Exam Registration System.
• 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 :

38
Class Diagram :

39
Sequence Diagram :

Result :
Thus the diagrams [Use case, class, activity, sequence, collaboration, Activity] for the
Exam Registration system has been designed, executed and output is verified.

40
Ex. No: 12 INVENTORY MAINTAINANCE SYSTEM
Date :

Aim :
• To draw the diagrams[usecase,sequence,class] for the Inventory Maintainance system.
• The Inventory system is maintained the stock information,Transaction information,
customer information and Report.
• The Stock details contains overall information about items which performs adding the
item and tell information about the status of the items.
• The customer information is maintained customer personal and purchase information.
• The transaction information is used to prepare the bill.
• Finally, Inventory system is generated various types of report

.Use-Case Diagram :

41
Class Diagram :

42
Sequence Diagram :

Result :
Thus the diagrams [Use case, class, activity, sequence, collaboration, Activity] for the
Inventory Maintainance System has been designed, executed and output is verified.

43
Ex. No: 13 E – TICKETING SYSTEM
Date :

Aim :
• To draw the diagrams [use case, sequence, class] for the E-ticketing system.
• 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 :

44
Class Diagram :

45
Sequence Diagram :

Result :
Thus the diagrams [Use case, class, activity, sequence, collaboration, Activity] for the
E-Ticketing System has been designed, executed and output is verified.

46
Ex. No: 14 CREDIT CARD PROCESSING
Date :

Aim :
• To draw the diagrams [usecase, sequence, class] for Credit Card Processing.
• 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.

.Use-Case Diagram :

47
Class Diagram :

48
Sequence Diagram :

Result :
Thus the diagrams [Use case, class, activity, sequence, collaboration, Activity] for the
Credit Card System has been designed, executed and output is verified.

49
Ex. No: 15 E - BOOK MANAGEMENT SYSTEM
Date :

Aim :
• To draw the diagrams [usecase, activity, sequence, collaboration, class] for E-book
management system.
• 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 :

50
Class Diagram :

51
Sequence Diagram :

Result :
Thus the diagrams [Use case, class, activity, sequence, collaboration, Activity] for the
E-Book Management System has been designed, executed and output is verified.

52
Ex. No: 16 RECRUITMENT SYSTEM
Date :

Aim :
• To draw the diagrams [use case, activity, sequence, collaboration, class] for
Recruitment system.
• 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 :

53
Class Diagram :

54
Sequence Diagram :

Result :
Thus the diagrams [Use case, class, activity, sequence, collaboration, Activity] for the
Recruitment System has been designed, executed and output is verified.

55