PANIMALAR ENGINEERING COLLEGE

DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS

REGISTER NO:211422244137

EX NO.: 1 INTRODUCTION ABOUT UML DIAGRAMS

DATE:

CASE tools known as Computer-aided software engineering tools is a kind of component-

based development which allows its users to rapidly develop information systems. The main
goal of case technology is the automation of the entire information systems development life
cycle process using a set of integrated software tools, such as modeling, methodology and
automatic code generation. Component based manufacturing has several advantages over
custom development. The main advantages are the availability of high quality, defect free
products at low cost and at a faster time. The prefabricated components are customized as per
the requirements of the customers. The components used are pre-built, ready-tested and add
value and differentiation by rapid customization to the targeted customers. However, the
products we get from case tools are only a skeleton of the final product required and a lot of
programming must be done by hand to get a fully finished, good product.
CHARACTERISTICS OF CASE
Some of the characteristics of case tools that make it better than customized
development are;
 It is a graphic oriented tool.
 It supports decomposition of process.
Some typical CASE tools are:
 Unified Modeling Language Data modeling tools,
 Source code generation tools.

INTRODUCTION TO UML (UNIFIED MODELING LANGUAGE)

The UML is a language for specifying, constructing, visualizing, and documenting the
software system and its components. The UML is a graphical language with sets of rules and
semantics. The rules and semantics of a model are expressed in English in a form known as
OCL (Object Constraint Language). OCL uses simple logic for specifying the properties of a
system. The UML is not intended to be a visual programming language. However, it has a
much closer mapping to object-oriented programming languages, so that the best of both can
be obtained. The UML is much simpler than other methods preceding it. UML is appropriate
for modeling systems, ranging from enterprise information system to distributed web-based
application and even to real time embedded system. It is a very expensive language
addressing all views needed to develop and then to display system even though understand to
use. Learning to apply UML effectively starts forming a conceptual mode of languages which
requires learning.
Three major language elements:
 UML basic building blocks
 Rules that dictate how this building blocks put together

1
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

 Some common mechanism that apply throughout the language .

The primary goals in the design of UML are:

1.Provides users ready to use, expressive visual modeling language as well so they can
develop and exchange meaningful models.
2.Provide extensibility and specialization mechanisms to extend the core concepts.
3.Be independent of particular programming languages and development processes.
4.Provide formal basis for understanding the modeling language.
5.Encourage the growth of the OO tools market.
6.Support higher-level development concepts.
7.Integrate best practices and methodologies.

1.UML class diagram:

The UML class diagram is also known as object modeling. It is a static analysis diagram.
These diagrams show the static structure of the model. A class diagram is a connection of
static model elements, such as classes and their relationships, connected as a graph to each
other and to their contents.
2. Use Case Diagram
The functionality of a system can be described in a number of different use-cases, each of
which represents a specific flow of events in a system. It is a graph of actors, a set of use-
cases enclosed in a boundary, communication, associations between the actors and the use-
cases, and generalization among the use-cases.
3.Behavior diagram:
It is a dynamic model unlike all the others mentioned before. The objects of an object-
oriented system are not static and are not easily understood by static diagrams. The behavior
of the class’ s instance (an object) is represented in this diagram. Every use-case of the
system has an associated behavior diagram that indicates the behavior of the object. In
conjunction with the use-case diagram we may provide a script or interaction diagram to
show a time line of events. It consists of sequence and collaboration diagrams.
4.Interaction diagram
It is the combination of sequence and collaboration diagram. It is used to depict the flow of
events in the system over a timeline. The interaction diagram is a dynamic model which
shows how the system behaves during dynamic execution.

2
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

5.State Chart diagram:

It consists of state, events and activities. State diagrams 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 how the object's state changes as a result of events that reach the object. In most
OO techniques, state diagrams are drawn for a single class to show the lifetime behavior of a
single object.
6.Activity diagram:
It shows organization and their dependence among the set of components. These diagrams are
particularly useful in connection with workflow and in describing behavior that has a lot of
parallel processing. An activity is a state of doing something: either a real-world process, or
the execution of a software routine.
7. Implementation diagram:
It shows the implementation phase of the systems development, such as the source code
structure and the run-time implementation structure. These are relatively simple high-level
diagrams compared to the others seen so far. They are of two sub-diagrams, the component
diagram and the deployment diagram.
8.Component diagram:
These are organizational parts of a UML model. These are boxes to which a model can be
decomposed. They show the structure of the code itself. They model the physical components
such as source code, user interface in a design. It is similar to the concept of packages.
9.Deployment diagram:
The deployment diagram shows the structure of the runtime system. It shows the
configuration of runtime processing elements and the software components that live in them.
They are usually used in conjunction with deployment diagrams to show how physical
modules of code are distributed on the system.
NOTATION ELEMENTS:
These are explanatory parts of UML model. They are boxes which may apply to describe and
remark about any element in the model. They provide the information for understanding the
necessary details of the diagrams.
Relations in the UML:
These are four kinds of relationships used in an UML diagram, they are:
 Dependency
 Association
 Generalization
 Realization
Conceptual model be UML:

3
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

UML you need to form the conceptual model of UML. This requires three major
elements:
 UML basic building blocks
 Rules that dictate how this building blocks are put together.
 Some common mechanism that apply throughout the language.

Building blocks of the UML:

The vocabulary of UML encompasses these kinds of building blocks.
Use CASE definition:
Description:
A use case is a set of scenarios tied together by a common user goal. A use case is a
behavioral diagram that shows a set of use case actions and their relationships.
Purpose:
The purpose of use case is login and exchange messages between sender and receiver (Email
client).
Main flow:
First, the sender gives his id and enters his login. Now, he enters the message to the receiver
id.
Alternate flow:
If the username and id by the sender or receiver is not valid, the administrator will not allow
entering and “ Invalid password” message is displayed.
Pre-condition:
A person has to register himself to obtain a login ID.
Post-condition:
The user is not allowed to enter if the password or user name is not valid.
Class diagram:
Description:
A class diagram describes the type of objects in system and various kinds of relationships that
exists among them.
Class diagrams and collaboration diagrams are alternate representations of object models.
A class diagram is represented as:
<<Class name>>
<<Attribute 1>>

4
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

<<Attribute n>>
<<Operation ()>>
Relationship used:
A change in one element affects the other
Generalization:
It is a kind of relationship
State chart: Description:
The state chart diagram made the dynamic behavior of individual classes. State chart shows
the sequences of states that an object goes through events and state transitions.
A state chart contains one state ‘ start’ and multiple ‘ end’ states.
Decision:
It represents a specific location state chart diagram where the work flow may branch based
upon guard conditions.
Synchronization:
It gives a simultaneous workflow in a state chart diagram. They visually define forks and
joints representing parallel workflow.
Forks and joins:
A fork construct is used to model a single flow of control. Every work must be followed by a
corresponding join.
Joints have two or more flow that unit into a single flow.
State
A state is a condition or situation during a life of an object in which it satisfies condition or
waits for some events.
Start state:
A start state shows the beginning of a workflow or beginning of a state machine on a state
chart diagram.
End state:
It is a final or terminal state.

Activity diagram:
Description:

5
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

Activity diagram provides a way to model the workflow of a development We can also model
this code specific information such as class operation using diagram. Activity diagrams can
model different types of diagrams. There are tools involved in the activity diagram.
Activity:
An activity represents the performance of a task on duty. It may also represent execution of a
statement in a procedure.
Decision:
A decision represents a condition on situation during the life of an object, which it satisfies
some condition or waits for an event.
Start state:
It represents the condition explicitly the beginning of a workflow on an activity.
Object flow:
An object on an activity diagram represents the relationship between activity and object that
creates or uses it.
Synchronization:
It enables us to see a simultaneous workflow in an activity.
End state:
An end state represents a final or terminal state on an activity diagram or state diagram.

Sequence diagram:
Description:
A sequence diagram is a graphical view of scenario that shows object interaction in a time-
based sequence what happens first what happens next. Sequence diagrams are closely related
to collaboration diagram.
The main difference between sequence and collaboration diagram is that sequence diagram
shows time-based interaction while collaboration diagram shows objects associated with each
other.

Collaboration diagram:
Description:
Collaboration diagram 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. Collaboration diagram is an interaction diagram that
shows the order of messages that implement an operation or a transaction.

6
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

Collaboration diagram shows object s, their links and their messages. They can also contain
simple class instances and class utility instances.
During, analysis indicates the semantics of the primary and secondary interactions. Design,
shows the semantics of mechanisms in the logical design of system.
Toggling between the sequence and collaboration diagrams
When we work in either a sequence or collaboration diagram, it is possible to view the
corresponding diagram by pressing F5 key.

7
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

EX NO:2 BOOK BANK SYSTEM

DATE:

AIM:
To draw the UML diagrams for the Book bank system.
PROJECT DESCRIPTION:
A Book Bank lends books and magazines to members who are registered in the system.
It also handles the purchase of new titles for the Book Bank. Popular titles are bought in
multiple copies. Old books and magazines are removed when they are outdated or in poor
condition. A member can reserve a book or magazine that is not currently available in the
book bank, so that when it is returned or purchased by the book bank, that person is notified.
The book bank can easily create, replace, and delete information about the titles, members,
loans, and reservations from the system.

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 Borrower, Librarian.
CLASS DIAGRAM:
The class diagram, also referred to as object modeling, is the main static analysis
diagram. The main task of object modeling is to graphically represent what each object will
do in the problem domain. The problem domain describes the structure and relationships
among objects.
ACTIVITY DIAGRAM:
It shows organization and their dependence among the set of components. These
diagrams are particularly useful in connection with workflow and in describing behavior that
uses a lot of parallel processing. An activity is a state of doing something either a real-world
process, or the execution of a software routine
SEQUENCE DIAGRAM:
A sequence diagram represents the sequence and interactions of a given USE-CASE or
scenario. Sequence diagrams can capture most of the information about the system. Most
object-to-object interactions and operations are considered events. Events include signals,

8
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

inputs, decisions, interrupts, transitions, and actions to or from users or external devices. An
event is also considered to be any action by an object that sends information.

STATE CHART DIAGRAM:

A State chart diagram describes a state machine. A state machine can be defined as a
machine which defines different states of an object, and these states are controlled by external
or internal events.
COLLABORATION DIAGRAM:
The diagrams show the PIN number entered and check the PIN. Get no and validate
password. Check the condition based on condition. Book issue and return are done. Pay the
online and renewed.
DEPLOYMENT DIAGRAM:
Deployment diagrams are used to visualize the topology of the physical components of
a system where the software components are deployed.
COMPONENT DIAGRAM
Component diagrams are used to describe the physical artifacts of a system. This
artifact includes files, executables, libraries, etc. Component diagrams are used during the
implementation phase of an application. However, it is prepared well in advance to visualize
the implementation details.
UML DIAGRAMS:
USECASE:

9
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

CLASS:

ACTIVITY:

10
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

11
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

SEQUENCE :

STATECHART:

12
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

COLLABORATION:

DEPLOYMENT:

13
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

COMPONENT:

RESULT:

14
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

EX. NO: 3 EXAM REGISTRATION SYSTEM

DATE:

AIM:
To draw the UML diagrams for the Exam registration system.
PROJECT DESCRIPTION:
The Exam Registration System is used in the effective dispatch of registration forms to
all of the students. This system adopts a comprehensive approach to minimize manual work
and schedule resources in a cogent manner. The core of the system is to get the online
registration form (with details such as name, reg no, etc.) filled by the student, whose
testament is verified for its genuineness by the Exam Registration System with respect to the
already existing information in the database.
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 Student Educational officer
CLASS DIAGRAM:
The class diagram, also referred to as object modeling, is the main static analysis
diagram. The main task of object modeling is to graphically represent what each object will
do in the problem domain. The problem domain describes the structure and relationships
among objects
ACTIVITY DIAGRAM:
It shows organization and their dependence among the set of components. These
diagrams are particularly useful in connection with workflow and in describing behavior that
uses a lot of parallel processing. An activity is a state of doing something either a real-world
process, or the execution of a software routine.
SEQUENCE DIAGRAM:
A Sequence Diagram represents the sequence and interactions of a given use case or
scenario. Sequence Diagram capture most of the information about the system. It is also
represented 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 the book has been selected the next half of sequence starts between
librarian and user followed by database

15
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

COLLABORATION DIAGRAM:
Like sequence diagram collaboration diagrams are also called as Interaction Diagram.
Collaboration diagram convey the same information 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.
DEPLOYMENT DIAGRAM:
Deployment diagrams are used to visualize the topology of the physical components of
a system where the software components are deployed.
COMPONENT DIAGRAM:
Component diagrams are used to visualize the organization and relationships among
the components of a system. Component diagram shows the dependencies and interactions
between software components.
UML DIAGRAMS:
USECASE:

16
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

CLASS:

ACTIVITY:

17
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

SEQUENCE:

COLLABORATION:

18
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

DEPLOYMENT:

COMPONENT:

RESULT:

EX.NO:4 PASSPORT AUTOMATION SYSTEM

DATE:
19
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

AIM:
To draw the UML diagrams for the Passport automation system.
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 the applicant and provide approval to
the office. Then the passport will be issued from the office to the applicant.
USE CASE DIAGRAM:
This diagram will contain the actors and use cases which are given below:
 Actors: Applicant, Enquiry Officer
 Use Cases: Applicant Details, Applicant Proof, Verification of Proof, Issue of
Passport, Cancellation of the Passport
CLASS DIAGRAM:
This diagram consists of the following classes, attributes, and their operations.

CLASSES ATTRIBUTES OPERATIONS

Verify Details, Store

Passport Management System Proof VerificationOfProof()

Enquiry Officer Applicant Details IssueOfPassport()

Applicant Name, Details ApplyPassport()

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
SEQUENCE DIAGRAM:
This diagram consists of the objects, messages, and return messages.
 Objects: Applicant, Enquiry Officer, Passport Management System

20
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

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.

DEPLOYMENT DIAGRAM:
Deployment diagrams are used to visualize the topology of the physical components of a
system where the software components are deployed.
COMPONENT DIAGRAM:
Component diagrams are used to visualize the organization and
relationships among the components of a system. Component diagram shows the
dependencies and interactions between software components.
UML DIAGRAMS:
USECASE:

21
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

CLASS:

ACTIVITY:

SEQUENCE:
COLLABORATION:

DEPLOYEMENT:

22
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

COMPONENT:

RESULT

EX NO: 5 STOCK MAINTENANCE SYSTEM

DATE:

23
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

AIM:
To draw the UML diagrams for the Stock maintenance system.
PROJECT DESCRIPTION:
This software is designed for supporting the computerized stock maintenance
System. In this system, the customer can place order and purchase items with the aid of the
stock dealer and central stock system. These 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.
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()
ACTIVITY DIAGRAM:
This diagram will have the activities as Start point, End point, Decision boxes as
given below:
Activities: Purchase order, payment, and delivery of items.
Decision box: Valid or not
SEQUENCE DIAGRAM:
This diagram consists of the objects, messages and return messages.
Object: Customer, Stock dealer, Central stock system.
STATE CHART DIAGRAM:
The purpose of state chart diagram is to understand the algorithm involved in
performing a method. It is also called as state diagram. A state is represented as a round box,
which may contain one or more compartments. An initial state is represented as small dot. A
final state is represented as circle surrounding a small dot.
COLLABORATION DIAGRAM:

24
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

Collaboration diagram 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
DEPLOYMENT DIAGRAM:
Deployment diagrams are used to visualize the topology of the physical
components of a system where the software components are deployed.
COMPONENT DIAGRAM:
Component diagrams are used to visualize the organization and relationships
among components in a system.
UML DIAGRAMS:
USECASE:

CLASS:

ACTIVITY:
25
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

SEQUENCE:

26
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

STATE CHART:

COLLABORATION:

27
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

DEPLOYMENT:

COMPONENT:

RESULT:

28
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

EX NO: 6 ONLINE COURSE RESERVATION SYSTEM

DATE:

AIM:
To draw the UML diagrams for the Online course reservation system.
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.
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()
ACTIVITY DIAGRAM:
This diagram will have the activities as Start point, End point, Decision boxes as
given below:
Activities: Bro wse course, select course, register course, submit details
Decision box: check availability or not.
SEQUENCE DIAGRAM:
This diagram consists of the objects, messages and return messages.
Object: Student, University, Central management system.
STATE CHART DIAGRAM:
The purpose of state chart diagram is to understand the algorithm involved in
performing a method. It is also called as state diagram. A state is represented as a round box,
which may contain one or more compartments. An initial state is represented as small dot. A
final state is represented as circle surrounding a small dot.

29
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

COLLABORATION DIAGRAM:
Collaboration diagram 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
DEPLOYMENT DIAGRAM:
Deployment diagrams are used to visualize the topology of the physical
components of a system where the software components are deployed.
COMPONENT DIAGRAM:
Component diagrams are used to visualize the organization and relationships
among components in a system.
UML DIAGRAMS:
USECASE:

30
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

CLASS:

ACTIVITY:

31
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

SEQUENCE:

STATE CHART:

32
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

COLLABORATION:

DEPLOYMENT:

33
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

COMPONENT:

RESULT:

34
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

EX NO: 7 STUDENT INFORMATION SYSTEM

DATE:

AIM:
To draw the UML diagrams for the Student Information system.
PROJECT DESCRIPTION:
The student must register by entering the name and password to login the form. The
admin selects the particular student to view the details about that student and maintaining the
student details. This process of student information system is described sequentially through
following steps. The student registers the system. The admin login to the student information
system. He/she 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.
USE CASE DIAGRAM:
This diagram will contain the actors, use cases which are given below
Actors: student, staff, system, DBA and server.
Use case: Login, display, enter profile, enter mark, view details, update details, allow access,
request access, store details, logout.
CLASS DIAGRAM:
This diagram consists of the following classes- student, staff, system, DBA and server.
ACTIVITY DIAGRAM:
This diagram will have the activities as Start point, End point, Decision boxes as given
below:
Activities: student, staff, system, DBA and server.
SEQUENCE DIAGRAM:
This diagram consists of the objects, messages and return messages.
Object: student, staff, system, DBA and server.
STATE CHART DIAGRAM:
The purpose of state chart diagram is to understand the algorithm involved in
performing a method. It is also called as state diagram. A state is represented as a round box,
which may contain one or more compartments. An initial state is represented as small dot. A
final state is represented as circle surrounding a small dot.
COLLABORATION DIAGRAM:

35
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

Collaboration diagram 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
DEPLOYMENT DIAGRAM:
Deployment diagrams are used to visualize the topology of the physical
components of a system where the software components are deployed.
COMPONENT DIAGRAM:
Component diagrams are used to visualize the organization and relationships
among components in a system.
UML DIAGRAMS:
USECASE:

CLASS:

36
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

ACTIVITY:

SEQUENCE:

37
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

STATE CHART:

COLLABORATION:

38
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

DEPLOYMENT:

COMPONENT:

39
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

RESULT:

EX NO: 8 SOFTWARE PERSONNEL MANAGEMENT SYSTEM

DATE:

AIM:
To draw the UML diagrams for Software personnel management system
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
USECASE 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
CLASS DIAGRAM:
This diagram consists of the following classes, attributes and their operations.

CLASSES ATTRIBUTES OPERATIONS

40
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

Central management system Emp_name Tax()

Emp_num Loan()

Employee 1 Emp_details LeaveTaken()

HR Check_details LossOfPay()
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

SEQUENCE DIAGRAM:

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

Object: Employee, HR, Central system
STATE CHART DIAGRAM:
The purpose of state chart diagram is to understand the algorithm involved in
performing a method. It is also called as state diagram. A state is represented as a round box,
which may contain one or more compartments. An initial state is represented as small dot. A
final state is represented as circle surrounding a small dot.
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.
DEPLOYMENT DIAGRAM:
Deployment diagrams are used to visualize the topology of the physical
components of a system where the software components are deployed.
COMPONENT DIAGRAM:
Component diagrams are used to visualize the organization and relationships
among components in a system.
UML DIAGRAMS:
USECASE:

41
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

CLASS

ACTIVITY:

42
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

SEQUENCE:

STATECHART:

43
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

COLLABORATION:

DEPLOYMENT:

COMPONENT:

44
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

RESULT:

45
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

EX NO: 9 CREDIT CARD MANAGEMENT SYSTEM

DATE:

AIM:
To draw the UML diagrams for credit card management system
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.
USECASE 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
CLASS DIAGRAM:
This diagram consists of the following classes, attributes and their operations
CLASSES ATTRIBUTES OPERATIONS
Central system Product_name PrintBill()
Product_details ValidateCard()
Cashier Product_name Amount()
Product_cost SwipeCard()
PrintBill()
DeliverProduct()
Card holder Items_purchased GiveCard()
Validate_card SignBill()

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
SEQUENCE DIAGRAM:
This diagram consists of the objects, messages and return messages.
Object: Card Holder,Cashier , Central system
STATE CHART DIAGRAM:

46
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

The purpose of state chart diagram is to understand the algorithm involved in

performing a method. It is also called as state diagram. A state is represented as a round box,
which may contain one or more compartments. An initial state is represented as small dot. A
final state is represented as circle surrounding a small dot.
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.
DEPLOYMENT DIAGRAM:
Deployment diagrams are used to visualize the topology of the physical
components of a system where the software components are deployed.
COMPONENT DIAGRAM:
Component diagrams are used to visualize the organization and relationships
among components in a system.
UML DIAGRAMS:

USECASE:

47
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

CLASS:

ACTIVITY:

48
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

SEQUENCE:

STATECHART:

49
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

COLLABORATION:

DEPLOYMENT:

50
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

COMPONENT:

RESULT:

51
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

EX NO: 10 RECRUITMENT SYSTEM

DATE:

AIM:
To draw the UML diagrams for Recruitment System
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
USECASE 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
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()

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
SEQUENCE DIAGRAM:
This diagram consists of the objects, messages and return messages.
Object: Candidate, HR, Central system
STATE CHART DIAGRAM:
The purpose of state chart diagram is to understand the algorithm involved in
performing a method. It is also called as state diagram. A state is represented as a round box,
which may contain one or more compartments. An initial state is represented as small dot. A
final state is represented as circle surrounding a small dot.
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.

52
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

DEPLOYMENT DIAGRAM:
Deployment diagrams are used to visualize the topology of the physical
components of a system where the software components are deployed.
COMPONENT DIAGRAM:
Component diagrams are used to visualize the organization and relationships
among components in a system.
UML DIAGRAMS:
USECASE:

CLASS:

53
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

ACTIVITY:

SEQUENCE:

54
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

STATECHART:

COLLABORATION:

55
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

DEPLOYMENT:

COMPONENT:

RESULT:

56
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

EX.NO: 11 LIBRARY MANAGEMENT SYSTEMS

DATE:

AIM:
To design an object oriented model for Library Management Systems using Argo UML.
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:
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.
CLASS DIAGRAM:
A Class Diagram in the unified modeling language is a type of static structure diagram
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.
ACTIVITY DIAGRAM:
It shows organization and their dependence among the set of components. These
diagrams are particularly useful in connection with workflow and in describing behavior that
uses a lot of parallel processing. An activity is a state of doing something either a real-world
process, or the execution of a software routine.
SEQUENCE DIAGRAM:
A Sequence Diagram represents the sequence and interactions of a given use case or
scenario. Sequence Diagram capture most of the information about the system. It is also
represented 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 the book has been selected the next half of sequence starts between
librarian and user followed by database.
STATECHART DIAGRAM:
Statechart 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 states such as Login, Enter Details, requesting for Book, Display Book Details,
Search Book, Issue Book, Return Book and Logout.

57
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

COLLABORATION DIAGRAM:
Like sequence diagram collaboration diagrams are also called as Interaction
Diagram. Collaboration diagram convey the same information 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.
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 syatsm 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.
UML DIAGRAMS:
USECASE:

58
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

CLASS:

ACTIVITY DIAGRAM:

59
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

SEQUENCE:

STATECHART:

60
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

COLLABORATION:

DEPLOYMENT:

61
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

COMPONENT:

RESULT:

62
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

EX.NO: 12 ATM BANKING SYSTEMS

DATE:

AIM:
To design an object-oriented model for ATM Banking System using Argo UML.
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
CLASS DIAGRAM:
A Class Diagram in the unified modeling language is a type of static structure
diagram 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.
ACTIVITY DIAGRAM:
It shows organization and their dependence among the set of components. These
diagrams are particularly useful in connection with workflow and in describing behavior that
uses a lot of parallel processing. An activity is a state of doing something either a real-world
process, or the execution of a software routine.
SEQUENCE DIAGRAM:
A Sequence Diagram represents the sequence and interactions of a given use case or
scenario. Sequence Diagram capture most of the information about the system. It is also
represented 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 the book has been selected the next half of sequence starts between
librarian and user followed by database.
STATE CHART DIAGRAM:
Statechart 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 states such as Login, Enter Details, requesting for Book, Display
Book Details, Search Book, Issue Book, Return Book and Logout.
COLLABORATION DIAGRAM:
Like sequence diagram collaboration diagrams are also called as Interaction
Diagram. Collaboration diagram convey the same information 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.

63
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

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 syatsm and execution environment nodes are user, librarian, system and
DBA.
COMPONENT DAIGRAM:
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.
UML DIAGRAMS:
USECASE:

CLASS:

64
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

ACTIVITY:

SEQUENCE:

65
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

STATECHART:

COLLABORATION:

66
 PANIMALAR ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER SCIENCE AND BUSINESS SYSTEMS
REGISTER NO:211422244137

DEPLOYEMENT:

COMPONENT:

RESULT:

67