OOAD LAB

OBJECTIVE:

To design a mini-project on any two of the given suggested domains by following the exercises
listed below.

1. To develop a problem statement.

2. Identify Use Cases and develop the Use Case model.
3. Identify the business activities and develop an UML Activity diagram.
4. Identity the conceptual classes and develop a domain model with UML Class diagram.
5. Using the identified scenarios find the interaction between objects and represent them using
UML Interaction diagrams.
6. Draw the State Chart diagram.
7. Draw the partial layered, logical architecture diagram with UML package diagram notation.

Suggested domains for Mini-project are:

1. Passport automation system.

2. Book bank
3. Exam Registration
4. Stock maintenance system.
5. Online course reservation system
6. E-ticketing
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
 1. PASSPORT AUTOMATION SYSTEM

AIM

To design the Passport Automation System using UML diagrams.

PROBLEM ANALYSIS AND PROJECT PLAN

To simplify the process of applying passport, software has been created by

designing through rational rose tool, using visual basic as a front end and
Microsoft access as a back end. Initially the applicant login the passport
automation system and submits his details. These details are stored in the database
and verification process done by the passport administrator, regional administrator
and police the passport is issued to the applicant.

PROBLEM STATEMENT

1. Passport Automation System is used in the effective dispatch of passport to

all of the applicants. This system adopts a comprehensive approach to
minimize the manual work and schedule resources, time in a cogent manner.

2. The core of the system is to get the online registration form (with details
such as name, address etc.,) filled by the applicant whose testament is
verified for its genuineness by the Passport Automation System with respect
to the already existing information in the database.

3. This forms the first and foremost step in the processing of passport
application. After the first round of verification done by the system, the
information is in turn forwarded to the regional administrator's (Ministry of
External Affairs) office.

4. The application is then processed manually based on the report given by the
system, and any forfeiting identified can make the applicant liable to penalty
as per the law.

5. The system forwards the necessary details to the police for its separate
verification whose report is then presented to the administrator. After all the
necessary criteria have been met, the original information is added to the
database and the passport is sent to the applicant.
1. USECASE DIAGRAM

DOCUMENTATION OF USECASE DIAGRAM

a. The actors in use case diagram are Applicant, regional administrator,

database, passport Administrator, Police.

b. The use cases are Login, givedetails, logout, collectdetails,

verification, issue.

c. The actors use the use case are denoted by the arrow

d. The login use case checks the username and password for applicant,
regional administrator, passport administrator and police.

e. The submit details use case is used by the applicant for submitting his
details

f. The check status use case is used by the applicant for checking the
status of the application process.
 g. The get details, verify and store verification use case is used by
passport administrator, regional administrator, and police.

h. The details use case is used for getting the details form the database
for verification

2. The verify use case is used for verifying the details by comparing the data in
the database.

a. The store verification use case is to update the data in the database

b. And finally the issue passport use case is used by the passport
administrator for issuing passport who’s application verified
successfully by all the actor .

2. CLASSDIAGRAM

A class is drawn as rectangle box with three compartments or components

separated by horizontal lines. The top compartment holds the class name and
middle compartment holds the attribute and bottom compartment holds list of
operations.
DOCUMENTATION OF CLASS DIAGRAM

a. APPLICANT-The applicant has attribute such as name and password

and operations are login, givedetails and logout. The applicant login
and fill the details that are required for applying the passport .After
applying the person can view the status of the passport verification
process

b. THE DATABASE-The database has attributed such as name and

operation is store. The purpose is to store the data.

c. REGIONAL ADMINISTRATOR- The regional administrator has

attribute such as name and operation are get details, verify details and
send. The regional administrator get the details form database and
verify with their database

d. PASSPORT ADMINISTRATOR-The passport administrator has

attributed such as name and operation are get details, verify details
and issue. The passport administrator get the details form database and
verify with their database , update the verification and issue the
passport

e. THE POLICE-The police has attribute such as name and operation

are get details, verify details and send. The police get the details form
database and verify with their database , update the verification in the
database
3. SEQUENCE DIAGRAM

A sequence diagram shows an interaction arranged in time sequence,

It shows object participating in interaction by their lifeline by the message they
exchange arranged in time sequence. Vertical dimension represent time and
horizontal dimension represent object.

DOCUMENTATION OF SEQUENCE DIAGRAM.

a. The applicant login the database and give his details and database
store the details.

b. The passport administrator get the details from the database and do
verification and the forward to regional administrator.

c. The regional administrator get details form passport administrator and

perform verification and send report to passport administrator.
 d. The police get the details form passport administrator and perform
verification and send report to passport administrator

4. STATE CHART DIAGRAM

The state chart diagram contains the states in the rectangle boxes and starts in
indicated by the dot and finish is indicated by dot encircled. The purpose of state
chart diagram is to understand the algorithm in the performing method.

DOCUMENTATION OF STATE CHART DIAGRAM

a. The states of the passport automation system are denoted in the state
chart diagram

b. Login state represent authentication for login the passport automation

system.

c. In this state, it checks whether the applicant has provided all the
details that is required.

d. Police, regional administrator and passport administrator get

necessary details and verification of the applicant are denoted from
the Get detail state and verification state
5. ACTIVITY DIAGRAM
An activity diagram is a variation or special case of a state machine in which the
states or activity representing the performance of operation and transitions are
triggered by the completion of operation. The purpose is to provide view of close
and what is going on inside a use case or among several classes. An activity is
shown as rounded box containing the name of operation

DOCUMENTATION OF ACTIVITY DIAGRAM

a. The activities in the passport automation system are login, submit

details, get details, issue passport and penalty and verification.

b. In the login activity applicant give username and password and then
login into the passport automation system after then fill the details that
are required for application.

c. After the verification procedure completed successfully the passport is

issued to the applicant.
6. COMPONENT DIAGRAM

The component diagram is represented by figure dependency and it is a graph of

design of figure dependency. The component diagram's main purpose is to show
the structural relationships between the components of a systems. It is represented
by boxed figure. Dependencies are represented by communication assosiation.

DOCUMENTATION OF COMPONENT DIAGRAM

a. The components in the passport automation system are passport

automation system, applicant, passport administrator, regional
administrator, and police.

b. Applicant ,passport administrator, regional administrator and police

are dependent on passport automation system are shown by the dotted
arrow
7. PACKAGE DIAGRAM

A package diagram is represented as a folder shown as a large rectangle with a top

attached to its upper left corner. A package may contain both sub ordinate package
and ordinary model elements. All uml models and diagrams are organized into
package. A package diagram in unified modeling language that depicts the
dependencies between the packages that make up a model. A Package Diagram
(PD) shows a grouping of elements in the OO model, and is a Cradle extension to
UML. PDs can be used to show groups of classes in Class Diagrams (CDs), groups
of components or processes in Component Diagrams (CPDs), or groups of
processors in Deployment Diagrams (DPDs).
There are three types of layer. They are

o User interface layer

o Domain layer

o Technical services layer

DOCUMENTATION OF PACKAGE DIAGRAM

The three layer in the passport automation system are user interface layer, domain
layer, technical service layer

a. The user interface layer- represents the user interface components

such as web, applicant, passport administrator, police, and regional
administrator.

b. The domain layer- has major actions such as give and get details,
verification and issues.

c. Technical service layer- authenticated user only can access the

technical services.
 2. E-BOOK MANAGEMENT SYSTEM

AIM
To design a project on E-Book Management system unsing UML diagrams.

PROBLEM ANALYSIS AND PROJECT PLANNING

Ebook Management System gives an idea about how books are maintained in the
particular websites. The books that are to be purchased, the books that are to be
sold are maintained here. . Further some additional details of the current books that
is available in the store are also given. Ebook Management System in this project
is done in an authorized way. The password and user id has been set here.

PROBLEM STATEMENT
The website has to be maintained properly since the whole ebook purchase process
can be improved. Ebook management in this project gives the idea about how
ebooks are maintained in a particular concern. The book details which includes the
number of books available ,no of pages and price. Ebook management system the
Ebook management in this project is understood by going through the modules that
is being involved.

1. 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 modelled. It is
represented using stick figure.
DOCUMENTATION OF USE CASE DIAGRAM

The actors in this use case diagram are Supplier, Store Keeper and Database. The
usecases are the activities performed by actors.

• The website will give the books available.

• Customer will login and check the list of ebooks in the database.
• The database will be updated according to the purchase done and it will be up to
date.The use cases in the use case diagram are Quotation & Purchase, login,
stock, purchase.
• Select books will gives us the status of the purchasing order details
• Login will gives us the entry for the customer of this project.
• Database will gives us the details about the total ebook available.
• Purchase will gives us the details about the details and the history of ebooks
purchased.

2. 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 applicant, recruiter and database.
• Customer – is the class name. Its attributes are name, address and cont no. The
operations performed in the Supplier class are get order, supply goods and get
money.

• Books – is the class name. Its attributes are operating system, computer
architecture,dbms,web technology and ooad. The operations performed are select
and buy.

• Database – is the class name. Its attribute is operation. The operations performed
is store .

3. 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.

DOCUMENTATION OF SEQUENCE DIAGRAM

The sequence diagram describes the sequence of steps to show
• The Customer enters the Ebook website.
• The list of books available are listed.
• Customer checks the book list.
• Database provides user id and pass.
• Customer selects the book.
• Pay money to the Website.
4. COLLABORATION 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 versa. 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

DOCUMENTATION OF COLLABORATION DIAGRAM

The first collaboration diagram is to show how the customer login and getting
details of ebooks in the ebook management system. Here the sequence is numbered
according to the flow of execution.
5. 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.

DOCUMENTATION OF STATE CHART DIAGRAM

This state diagram describes the behavior of the system.
• First state is login where the customer login to the ebook management system.
• The next state is check the list of books in order.
• Then select buy the book.
• Enter the account detail and purchase the book.
6. 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.
• First Customer login then checks books available.
• The book list are verified and is given in a ordered format.
• The needed book is selected.
• Enter your account details and purchase the book .

7. COMPONENT DIAGRAM
The component diagram's main purpose is to show the structural relationships
between the components of a systems. It is represented by boxed figure.
Dependencies are represented by communication association.
DOCUMENTATION OF COMPONENT DIAGRAM
The main component in this component diagram is online recruitment systems.
And Supplier, storekeeper and database are the components come under the main
component.

8. PACKAGE DIAGRAM
A package diagram in unified modeling language that depicts the dependencies
between the packages that make up a model. A Package Diagram (PD) shows a
grouping of elements in the OO model, and is a Cradle extension to UML.
PDs can be used to show groups of classes in Class Diagrams (CDs), groups of
components or processes in Component Diagrams (CPDs), or groups of processors
in Deployment Diagrams (DPDs).
There are three types of layer. They are
• User interface layer: consists of the form and login. This layer describes how
the customer logins and books maintained in website.
• Domain layer: shows the activities that are performed in the ebook management
system. The activities are books are purchased from the websote
• Technical services layer: the update the account details and buy the book by
payment through the account