lOMoARcPSD|44294995

PCA20C07J- Object Oriented Analysis AND Design

Laboratory
Object Oriented Analysis And Design (SRM Institute of Science and Technology)

Scan to open on Studocu

Studocu is not sponsored or endorsed by any college or university

Downloaded by Rudra ([email protected])
 lOMoARcPSD|44294995

PCA20C07J - OBJECT ORIENTED ANALYSIS AND DESIGN LABORATORY

OBJECTIVES:
 To capture the requirements specification for an intended software system
 To draw the UML diagrams for the given specification
 To map the design properly to code
 To test the software system thoroughly for all scenarios
 To improve the design by applying appropriate design patterns.

Draw standard UML diagrams using an UML modeling tool for a given case study and
map design to code and implement a 3 layered architecture. Test the developed code and
validate whether the SRS is satisfied.

1. Identify a software system that needs to be developed.

2. Document the Software Requirements Specification (SRS) for the identified system.
3. Identify use cases and develop the Use Case model.
4. Identify the conceptual classes and develop a Domain Model and also derive a Class
Diagram from that.
5. Using the identified scenarios, find the interaction between objects and represent them
using
UML Sequence and Collaboration Diagrams
6. Draw relevant State Chart and Activity Diagrams for the same system.
7. Implement the system as per the detailed design
8. Test the software system for all the scenarios identified as per the usecase diagram
9. Improve the reusability and maintainability of the software system by applying
appropriate design patterns.
10. Implement the modified system and test it for various scenarios

SUGGESTED DOMAINS FOR MINI-PROJECT:

1. Passport automation system.

2. Book bank
3. Exam registration
4. Stock maintenance system.
5. Online course reservation system

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

TABLE OF CONTENTS

S.NO. DATE EXPERIMENT TITLE SIGNATURE

Case Tools

2 Passport automation system

3 Book bank

4 Exam Registration

5 Stock maintenance system

6 Online course reservation system

7 Airline/Railway reservation system

8 Software personnel management system

9 Credit card processing

10 E-book management system

Ex. No.: 1 CASE TOOLS

INTRODUCTION:

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
Downloaded by Rudra ([email protected])
 lOMoARcPSD|44294995

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, and
 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

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

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
 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.
Every complex system is best approached through a small set of
nearly independent views of a model. Every model can be expressed at
different levels of fidelity. The best models are connected to reality. The
UML defines nine graphical diagrams:

i. Class diagram
ii. Use-case diagram
iii. Behavior diagram
iv. Interaction diagram
v. sequence diagram
vi. collaboration diagram
vii. state chart diagram
viii. activity diagram

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

ix. Implementation
diagram 9.1component
diagram 9.2deployment
diagram

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.

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

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

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

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

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

Dependency:

It is a semantic relationship between two things in which a change one

thing affects the semantics of other things. Graphically a dependency is
represented by a non-continuous line.

Association:

It is a structural relationship that describes asset of links. A link is

being connected among objects. Graphically association is represented as a
solid line possibly including label.

Generalization:

It is a specialized relationship in which the specialized elements are

substitutable for object of the generalized element. Graphically it is a solid
line with hollow arrow head parent.

Realization:

It is a semantic relation between classifiers. Graphically it is

represented as a cross between generalization and dependency relationship.

Where UML can be used:

UML is not limited to modeling software. In fact it is expressive to

model non-software such as to show in structure and behavior of health case
system and to design the hardware of the system.

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

Conceptual model be UML:

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.

Once you have grasped these ideas, you may be able to read. UML
create some basic ones. As you gain more experience in applying conceptual
model using more advanced features of this 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.

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

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.

During analysis, we use class diagram to show roles and

responsibilities of entities that provide email client system behaviors design.
We use to capture the structure of classes that form the email client system
architecture.

A class diagram is represented as:

<<Class name>>
<<Attribute 1>>
<<Attribute n>>
<<Operation ()>>

Relationship used:

A change in one element affects the other

Generalization:

It is a kind of relationship

State chart:

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

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.

The important objectives are:

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.
Transition:

It is a relationship between two activities and between states and

activities.

Start state:

A start state shows the beginning of a workflow or beginning of a

state machine on a state chart diagram.

End state:

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

It is a final or terminal state.

Activity diagram

Description:

Activity diagram provides a way to model the workflow of a

development process. We can also model this code specific information
such as class operation using activity diagram. Activity diagrams can model
different types of diagrams. There are various tools involved in the activity
diagram.

Activity:

An activity represents the performance of a task on duty. It may also

represent the 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 chart diagram.

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

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 show time based interaction while collaboration
diagram shows objects associated with each other.

The sequence diagram for the e-mail client system consists of the
following objectives:

Object:

An object has state, behavior and identity. An object is not based is

referred to as an instance.
The various objects in e-mail client system are:
 User
 Website
 Login
 Groups

Message icon:

A message icon represents the communication between objects

indicating that an action will follow. The message icon is the horizontal
solid arrow connecting lifelines together.

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.

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

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.

CONCLUSION:
Thus the study for case tools was done.

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

Ex no:2
PASSPORT AUTOMATION SYSTEM

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

(I) PROBLEM STATEMENT:

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

( II )SOFTWARE REQUIREMENT SPECIFICATION:

2.1SOFTWARE INTERFACE
• Front End Client - The applicant and Administrator online
interface is built using
JSP and HTML. The Administrators's local interface is built using
Java.
•Web Server - Glassfish application server(Oracle Corporation).
•Back End - Oracle database.

2.2HARDWARE INTERFACE

The server is directly connected to the client systems. The client

systems have access to the database in the server.

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

( III ) USECASE DIAGRAM :

registration
enter applicant id

check status
administrator

applicant process applicant

dispatch passport

Fig.3. USECASE DIAGRAM FOR PASSPORT AUTOMATION SYSTEM

(IV) ACTIVITY DIAGRAM:

Fig.4.1. ACTIVITY DIAGRAM FOR REGISTER

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

Fig.4.2. ACTIVITY DIAGRAM FOR ADMINISTRATION

Fig.4.3. ACTIVITY DIAGRAM FOR CHECKING STATUS

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

(V) 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
show what each object will do in the problem domain. The problem domain
describes the structure and the relationships among objects.
The Passport Automation system class diagram consists of four
classesPassport Automation System
1. New registration
2. Gender
3. Application Status
4. Admin authentication
5. Admin Panel

Fig.5. CLASS DIAGRAM FOR PASSPORT AUTOMATION SYSTEM

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

(VI) INTERACTION 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 and events include signals, inputs,
decisions, interrupts, transitions and actions to or from users or external
devices.
An event also is considered to be any action by an object that sends
information. The event line represents a message sent from one object to
another, in which the “form” object is requesting an operation be performed
by the “to” object. The “to” object performs the operation using a method
that the class contains.
It is also represented by the order in which things occur and how the
objects in the system send message to one another.
The sequence diagram for each USE-CASE that exists when a user
administrator, check status and new registration about passport automation
system are given.

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

administrator
administrator system
system admin panel
admin panel application
application
database
database

1: 1.username\password

2: authetication suceed

3: details of application yet to be released

4: details of application dispatched

5: enter applicant id to process

6: give details

7: dispatch eligible passports

Fig.6.1.SEQUENCE DIAGRAM FOR ADMINISTRATOR

1: 1.username\password 2: authetication suceed

admin
administ rator system panel

5: enter applicant id to process4: details of application dispatched

7: dispatch eligible passports

6: give details

3: details of application yet to be released

databas applicati
e on

Fig.6.2.COLLABORATION DIAGRAM FOR ADMINISTRATOR

The diagrams show the process done by the administrator to the

Passport Automation system. The applicant has to enter his details. The

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

details entered are verified by the administrator and the applicant is

approved if the details match then the passport is dispatch, otherwise an
appropriate error message is displayed.

applicant system
system
applicant
database
database

1: enter applicant id

2: fetch details for the applicant

3: display the status

Fig.6.3.SEQUENCE DIAGRAM FOR CHECKING STATUS

1: enter applicant id
3: display the status
applicant
system

2: fetch details for the applicant

databas
e

Fig.6.4.COLLABORATION DIAGRAM FOR CHECKING STATUS

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

The diagrams show the applicant enters his id and the system fetch the
details from the database and display the status.

applicant
applicant database
database
system
system

1: request for registeration

2: registeration form

3: fill in details

4: submit

5: give applicatino id
6: store full deatils

Fig.6.5.SEQUENCE DIAGRAM FOR NEW REGISTRATION

1: request for registeration

3: fill in details
4: submit
applicant
5: give applicatino id
2: registeration form system

6: store full deatils

databas
e

Fig.6.6.COLLABORATION DIAGRAM FOR NEW REGISTRATION

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

The diagrams show the applicant request the system for registration
and the system provide the register form and applicant fill the form and
submit and the system give the applicant id. The database stores the full
details.
(VII) PARTIAL LAYERD LOGICAL ARCHITECTURE DIAGRAM

UI

Swing Text

Passport auto PassAuto

system Console

Domain

Registration Admin panel

Register Cancel Process Balance

Authentication

Login

Technical Services

Persistence Log4J
SOAP

DBFacade

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

(VIII) DEPLOYMENT DIAGRAM AND COMPONENT DIAGRAM

Deployment diagrams are used to visualize the topology of the
physical components of a system where the software components are
deployed.

<<client workstation>>
<<database>>
:GenericPC
:MySQL

SQL HTT

<<server>> :T omcat6

DEPLOYMENT DIAGRAM

COMPONENT DIAGRAM

Component diagrams are used to visualize the organization and relationship

among components in system

RESULT:
Thus the mini project for passport automation system has been
successfully executed and codes are generated.

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

Ex no:3
BOOK BANK SYSTEM

AIM:
To create a system to perform book bank operation

(I) PROBLEM STATEMENT:

A Book Bank lends books and magazines to member, who is registered

in the system. Also it handles the purchase of new titles for the Book Bank.
Popular titles are brought into multiple copies. Old books and magazines are
removed when they are out or date or poor in 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 tiles, members, loans and reservations from the system.

(II) SOFTWARE REQUIREMENTS SPECIFICATION:

2.1SOFTWARE INTERFACE

 Front End Client - The Student and Librarian online

interface is built using JSP and HTML. The Librarians local
interface is built using Java.
 Web Server - Glassfish application server (Oracle Corporation).
 Back End - Oracle database

2.2HARDWARE INTERFACE

The server is directly connected to the client systems. The client

systems have access to the database in the server.

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

(III) USE-CASE DIAGRAM:

Fig 3. USE-CASE DIAGRAM FOR BOOK BANK SYSTEM

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

(IV) ACTIVITY DIAGRAM:

Fig.4. ACTIVITY DIAGRAM

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

(V) 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
show what each object will do in the problem domain. The problem domain
describes the structure and the relationships among objects.

Fig.5. CLASS DIAGRAM FOR BOOK BANK SYSTEM

(VI) 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 and events include signals, inputs,
decisions, interrupts, transitions and actions to or from users or external
devices.

An event also is considered to be any action by an object that sends

information. The event line represents a message sent from one object to
another, in which the “form” object is requesting an operation be performed

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

by the “to” object. The “to” object performs the operation using a method
that the class contains.

It is also represented by the order in which things occur and how the
objects in the system send message to one another.

Fig. 6.1. SEQUENCE DIAGRAM FOR DEPOSIT PROCESS

The diagrams show the pin no is 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.

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

5: get valid pin

14: Renewed : Libraian

4: Validate Password
1: pin no :
BookBank
9: book issue

: Student no of books 12: Pay the line

7: check
13: book return 3: no

11:
8: no 2: Check pin
checkDate 10: yes

6: Yes
: BookReturn : BookIssue : validity

Fig. 6.2. COLLABORATION DIAGRAM FOR DEPOSIT PROCESS

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

(VII) PARTIAL LAYERD LOGICAL ARCHITECTURE DIAGRAM:

UI

Swing Text

BookBank BkBank
system Console

Domain

Student Book Bank

St Details Cancel Issue Return

Validity Book Details

Check Validity Display

(VIII) D
Technical Services

Persistence Log4J
SOAP

DBFacade

Deployment diagram
EDeployment diagrams are used to visualize the topology of the
Pphysical components of a system where the software components
L
Oare deployed.
Downloaded by Rudra ([email protected])
 lOMoARcPSD|44294995

YMENT

<<databas e>> <<client workstation

>>:

DIAGRAM SQ HTT

<<server>>
:To

A
Fig.8.1.DEPLOYMENT DIAGRAM
N
D
COMPONENT DIAGRAM
C
Comcomponent diagrams are used to visualize the organization and relationships

O
M Fig.8.2.COMPONENT DIAGRAM
RPESULT
:
T hus the mini project for Book Bank System has been successfully
O
executed
a nd codes are generated.
N
E
N
T

D
I
A
Ex no:4 EXAM REGISTRATION SYSTEM

AIM:
To create a system to perform the Exam Registration system
Downloaded by Rudra ([email protected])
 lOMoARcPSD|44294995

(I) PROBLEM STATEMENT:

Exam Registration system.is used in the effective dispatch of

registration form to all of the students. This system adopts a comprehensive
approach to minimize the manual work and schedule resources, time 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.

(II)SOFTWARE REQUIREMENT SPECIFICATION:

2.1SOFTWARE INTERFACE
• Front End Client - The student and Controller online interface is
built using JSP and HTML. The Exam Controller's local interface is
built using Java.
• Web Server - Glassfish application server(SQlCorporation).
• Back End - SQL database.

2.2HARDWARE INTERFACE
The server is directly connected to the client systems. The client
systems have access to the database in the server.

(III)USECASE DIAGRAM:

The Exam Registration use cases in our system are:

1. Login
2. View exam details
3. View fees details

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

4. Pay fee
5. Display details
6. Logout

USECASE DIAGRAM :

Fig. 3.USECASE DIAGRAM FOR EXAM REGISTRATION SYSTEM

(IV) ACTIVITY DIAGRAM:

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

Fig. 4.USECASE DIAGRAM FOR EXAM REGISTRATION SYSTEM

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

(V)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
show what each object will do in the problem domain. The problem domain
describes the structure and the relationships among objects.

Fig.5. CLASS DIAGRAM FOR EXAM REGISTRATION SYSTEM

(VI)INTERACTION 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 and events include signals, inputs,
decisions, interrupts, transitions and actions to or from users or external
devices.

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

An event also is considered to be any action by an object that sends

information. The event line represents a message sent from one object to
another

Database
Database ::
ExamController
ExamController

: student

1: login

2: confirmation

3: pay
4: register

5: conformation

6: view exam details

7: logout

Fig. 6.1. SEQUENCE DIAGRAM FOR REGISTRATION SYSTEM

5: conformation

3: pay
: ExamController

: student

1: login

2: confirmation 4: register

7: logout
6: view exam details

Database
Fig. 6.2. COLLABORATION DIAGRAM FOR REGISTRATION
SYSTEM

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

(VII) PARTIAL LAYERD LOGICAL ARCHITECTURE DIAGRAM:

UI

Swing Text

ExamReg ExamReg
System Console

Domain

Student ExamController

Register ViewFeeDetail Confirmation Display Fee

Authentication

Logout
Login

Technical Services

Persistence Log4J
SOAP

DBFacade

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

(VIII) DEPLOYMENT DIAGRAM AND COMPONENT DIAGRAM

Deployment diagrams are used to visualize the topology of the
physical components of a system where the software components are
deployed.

<<client
<<database>>
workstation>>:
:MySQL GenericPC
SQL HTTP

<<server>> :To
mcat6

Fig.7.1.DEPLOYMENT DIAGRAM

COMPONENT DIAGRAM

Component diagrams are used to visualize the organization and

relationships among components in a system.

Fig.7.2.COMPONENT DIAGRAM

RESULT:
Thus the mini project for Exam Registration system has been
successfully executed and codes are generated.
Ex no: 5 STOCK MAINTENANCE

AIM:

To create a system to perform the Stock maintenance

Downloaded by Rudra ([email protected])
 lOMoARcPSD|44294995

(I)PROBLEM STATEMENT
The stock maintenance system must take care of sales information of
the company and must analyze the potential of the trade. It maintains the
number of items that are added or removed.The sales person initiates this
Use case. The sales person is allowed to update information and view the
database.

(II) SOFTWARE REQUIREMENT SPECIFICATION

PURPOSE
The entire process of Stock maintenanceis done in a manual manner
Considering the fact that the number of customers for purchase is increasing
every year, a maintenance system is essential to meet the demand. So this
system uses several programming and database techniques to elucidate the
work involved in this process.

SCOPE
• The System provides an interface to the customer where they can fill
in orders for the item needed.
• The sales person is concerned with the issue of items and can use
this system.

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

• Provide a communication platform between the customer and the

sales person.

TOOLS TO BE USED
• Eclipse IDE (Integrated Development Environment)
• Rational Rose tool (for developing UML Patterns)
(III) 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
generalizationamong the use-cases

Place Order

Track order

Customer
Validate Customer
Ship Order

Ship Partial Order

Sales Person

Bill Customer

Fig.3. USE CASE DIAGRAM

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

(IV) 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.

Customer
Sales
Request Service

Pay Take Order Fill Order

Deliver Order

Collect Order

Fig.4. ACTIVITY DIAGRAM

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

(V) 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.

Fig.5. CLASS DIAGRAM

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

(VI)UML INTERACTION DIAGRAMS

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.

AnAn Order
Order AnAn Order
Order AnAnOrder Line A AStock
Order Line Item
Stock Item

Prepare

Prepare

Has Stock:=Check

[has Stock]:Remove

Needs reorder:=needs to reorder()

[needs reorder]:newAAReorder
Reorder
Item Item

A Delivery Item
A Delivery Item

[Has Stock]: new

Fig.6.1 SEQUENCE DIAGRAM

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

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.

ORDER ENTRY
WINDOW

1: prepare()

AN ORDER

2: *[for all order lines]prepare()

3: hasstock=check
needs Reorder=need to Reorder

4: [hasstock]remove()
ORDER LINE STOCK ITEM

5: [needs Reorder]:new
6: [hasstock]:new

DELIVERY ITEM REORDER ITEM

Fig.6.2 COLLABORATION DIAGRAM

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

(VII) PARTIAL LAYERD LOGICAL ARCHITECTURE DIAGRAM

UI

Swing Text

StMain System StMaint Console

Domain

Customer Order

Register Invoice Stock

Shipment
Product

Technical Services

Persistence SOAP Log4J

DBFacade

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

(VIII) DEPLOYMENT DIAGRAM AND COMPONENT DIAGRAM

Deployment diagrams are used to visualize the topology of the

physical components of a system where the software components are
deployed.

LAN
<<database>> <<client workstation>>: GenericPC
:MySQL

Fig.8.1 DEPLOYMENT DIAGRAM

Component Diagram

Component diagrams are used to visualize the organization and relationships

among components in a system.

Fig.8.2.COMPONENT DIAGRAM

RESULT:
Thus the mini project for stock maintenance system has been
successfully executed and codes are generated.

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

EX NO: 6 ONLINE COURSE RESERVATION SYSTEM

AIM
To design an object oriented model for course reservation system.

(I) PROBLEM STATEMENT

a. Whenever the student comes to join the course he/she should be

provided with the list of course available in the college.

b. The system should maintain a list of professor who is teaching

the course. At the end of the course the student must be
provided with the certificate for the completion of the course.

(II) SYSTEM REQUIEMENT SPECIFICATION

OBJECTIVES
a. The main purpose of creating the document about the
software is to know about the list of the requirement in the
software project part of the project to be developed.

b. It specifies the requirement to develop a processing

software part that completes the set of requirement.
SCOPE

a. In this specification, we define about the system

requirements that are about from the functionality of the
system.

b. It tells the users about the reliability defined in

usecase specification

FUNCTIONALITY
Many members of the process line to check for its occurrences and
transaction, we are have to carry over at sometimes

USABILITY
The user interface to make the transaction should be effectively

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

PERFORMANCE
It is the capability about which it can performed function for many user at
sometimes efficiently (ie) without any ever occurrences

RELIABILITY
The system should be able to the user through the day to day transaction

(III) USERCASE DIAGRAM

a. Use case is a sequence of transaction in a system whose task

is to yield result of measurable value to individual author of
the system

b. Use case is a set of scenarios together by a common user goal

c. A scenario is a sequence of step describing as

interaction between a user and a system

CLASS DIAGRAM:

A class diagram describes the type of objectors in the system the various
kinds of static relationship that exist among them.

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

SEQUENCE DIAGRAM

A sequence diagram is one that includes the object of the projects and tells
the lifetimes and also various action performed between objects.

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

COLLOBORATIION DIAGRAM

It is same as the sequence diagram that involved the project with the only
difference that we give the project with the only difference that we give
sequence number to each process.

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

ACTIVIY DIAGRAM

It includes all the activities of particular project and various steps using join
and forks

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 association

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

DEPLOYMENT DIAGRAM

It is a graph of nodes connected by communication association. It is

represented by a three dimensional box. A deployment diagram in the
unified modeling language serves to model the physical deployment of
artifacts on deployment targets. Deployment diagrams show "the allocation
of artifacts to nodes according to the Deployments defined between them. It
is represented by 3-dimentional box. Dependencies are represented by
communication association. The basic element of a deployment diagram is a
node of two types

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

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

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

a. User interface layer

b. Domain layer

c. Technical services layer

RESULT
Thus the mini project for online course reservation system has been
successfully executed and codes are generated.

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

EX NO: 7 AIRLINE/RAILWAY RESERVATION SYSTEM

AIM
To develop the Airline/Railway reservation System.

(I) PROBLEM ANALYSIS AND PROJECT PLANNING

In the Airline/Railway reservation System the main process is a applicant

have to login the database then the database verifies that particular username
and password then the user must fill the details about their personal details
then selecting the flight and the database books the ticket then send it to the
applicant then searching the flight or else cancelling the process.

(II)OVERALL DESCRIPTION
Functionality
The database should be act as an main role of the e-ticketing system it can be
booking the ticket in easy way.

Usability
The User interface makes the Credit Card Processing System to be efficient.

Performance
It is of the capacities about which it can perform function for many users
at the same times efficiently that are without any error occurrence.
Reliability
The system should be able to process the user for their corresponding
request.

(III) USE CASE DIAGRAM

The passenger can view the status of the reserved tickets. So the passenger
can confirm his/her travel.

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

Fig. USE-CASE DIAGRAM FOR AIRLINE RESERVATION

(IV) CLASS DIAGRAM

The online ticket reservation system makes use of the following classes:
1. ticketReservation
2. trainInfo
3. passengerInfo
4. seatAvailStatus

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

SEQUENCE DIAGRAM

A sequence diagram in Unified Modeling Language (UML) is a kind of

interaction diagram that shows how processes operate with one another and
in what order. It is a construct of a Message Sequence Chart. There are two
dimensions.
1. Vertical dimension-represent time.
2. Horizontal dimension-represent different objects.

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

COLLABRATION DIAGRAM

A collaboration diagram, also called a communication diagram or interaction

diagram,. A sophisticated modeling tool can easily convert a collaboration
diagram into a sequence diagram and the vice 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.

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

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

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.

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.

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

COMPONENT DIAGRAM

The component diagram's main purpose is to show the structural

relationships between the components of a system. It is represented by
boxed figure. Dependencies are represented by communication association.

RESULT
Thus the mini project for Airline/Railway reservation System has been
successfully executed and codes are generated.

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

Ex no: 8 SOFTWARE PERSONNEL MANAGEMENT SYSTEM

AIM:
To implement a software for software personnel management system.

(I) PROBLEM STATEMENT:

Human Resource management system project involves new and/or

system upgrades of software of send to capture information relating to the
hiring termination payment and management of employee. He uses system
to plan and analyze all components and performance of metrics driven
human resource functions, including recruitment, attendance, compensation,
benefits and education. Human resources management systems should align
for maximum operating efficiency with financial accounting operations
customer relationship management, security and business lines as
organization.

( II )SOFTWARE REQUIREMENT SPECIFICATION:

2.1SOFTWARE INTERFACE
• Front End Client - The applicant and Administrator online
interface is built using JSP and HTML. The HR's local interface
is built using Java.
• Server - Glassfish application server(SQL Corporation).
• Back End - SQL database.

2.2HARDWARE INTERFACE
The server is directly connected to the client systems. The client
systems have access to the database in the server.

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

( III )USECASE DIAGRAM:

The HR of an organization involves recruitment training, monitoring and

motivation of an employee. The HR also involves gives salary as observed
in the payroll sheet. The employee undergoes training, receives the salary ,
gives the expected performance and manages time in order to complete a
given task within the required period.

Fig.3. USE CASE DIAGRAM

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

(IV) ACTIVITY DIAGRAM:

The activity diagram notation is an action, partition, fork join and

object node. Most of the notation is self explanatory, two subtle points. Once
an action finished, there is an automatic outgoing transaction. The diagram
can show both control flow and data flow.

Fig.4. ACTIVITY DIAGRAM

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

(V) 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
show what each object will do in the problem domain. The problem domain
describes the structure and the relationships among objects.

Fig.5.CLASS DIAGRAM

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

(VI) INTERACTION 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 and events include signals, inputs,
decisions, interrupts, transitions and actions to or from users or external
devices.

Fig.6.1.SEQUENCE DIAGRAM

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

Fig.6.2.COLLABORATION DIAGRAM

(VII) State Transition Diagram

States of object are represented as rectangle with round corner, the
transaction between the different states. A transition is a relationship
between two state that indicates that when an event occur the object moves
from the prior state to the subsequent.

Fig.7.STATE TRANSITION DIAGRAM

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

(VIII) DEPLOYMENT DIAGRAM AND COMPONENT DIAGRAM

HR recruits employee for a company employee recruited by HR goes

under training before actually working. Training period is given to the
employee with the training details. The salary details for the employee are
provided.

Fig.8.1.DEPLOYMENT DIAGRAM

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

COMPONENT DIAGRAM

The HR recruits, motivate and monitor the employee, HR also update

the salary details and training details for reference. The employee are those
who are recruited by HR and work for the company. The training details
provide employees with training details which is updated by HR

Fig.8.2.COMPONENT DIAGRAM

RESULT:

Thus the mini project for software personnel management system has
been successfully executed and codes are generated.

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

Ex. No:9
CREDIT CARD PROCESSING

AIM:
To create a system to perform the credit card processing

(I) PROBLEM STATEMENT:

Credit card processing through offline involves the merchant

collecting order information (including credit card numbers), storing this in a
database on your site, and entering it using their on-site merchant credit card
processing system. Takes time to manually enter credit card information for
each order. This solution creates following cons:

( II )SOFTWARE REQUIREMENT SPECIFICATION:

PRODUCT PERSPECTIVE

This solution involves signing up for a free Business Account. Once

this is done and the e-commerce site is properly configured, you can accept
payments from Visa, MasterCard, Amex, and Discover cards payments.

SOFTWARE INTERFACE
• Front End Client - The applicant and Administrator online
interface is built using
JSP and HTML. The Administrators's local interface is built using
Java.
• Web Server - Glassfish application server(SQL Corporation).
• Back End - SQL database.

HARDWARE INTERFACE

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

The server is directly connected to the client systems. The client

systems have access to the database in the server.

( III )USECASE DIAGRAM:

USE-CASE NAME: PAYMENT APPROVAL

The transaction details are recorded by the credit card processor and
results are securely relayed to the merchant. Merchant’s site receives
transaction result and does appropriate actions (e.g. saves the order & shows
message).

Fig.3. USECASE DIAGRAM FOR PASSPORT AUTOMATION

SYSTEM
(IV) CLASS DIAGRAM:

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

The class diagram, also referred to as object modeling is the main

static analysis diagram. The main task of object modeling is to graphically
show what each object will do in the problem domain. The problem domain
describes the structure and the relationships among objects.
The Credit Card Processing system class diagram consists of three
classes.
They are
Cashier
User
Authorization Service

Fig.4.CLASS DIAGRAM

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

(V) INTERACTION DIAGRAM:

Fig.5.1.SEQUENCE DIAGRAM

Fig.5.2.COLLABORATION DIAGRAM

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

(VI) PARTIAL LAYERD LOGICAL ARCHITECTURE DIAGRAM

UI

Swing

CCP system

Domain

User Merchant

Purchase Account Info Request Receipt

AutherizationSerivi
c
e

Reply

Technical Services

Persistence
DBFacade Log4J
SOAP

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

(VII) DEPLOYMENT DIAGRAM AND COMPONENT DIAGRAM

Deployment diagrams are used to visualize the topology of the
physical components of a system where the software components are
deployed.

<<client
<<database>
workstation
>
>>:Generic
: SQL SQ

HT

<<server>>

Fig.7.1.DEPLOYMENT DIAGRAM

COMPONENT DIAGRAM
Component diagrams are used to visualize the organization and relationships
among components in a

Fig.7.2.COMPONENT DIAGRAM
RESULT:

Thus the mini project for credit card processing system has been
successfully executed and codes are generated.
Ex. No:10 AIM: BOOK MANAGEMENT SYSTEM

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

To create a system to perform E- book Management System.

(I)PROBLEM STATEMENT:

An E- Book lends books and magazines to member, who is registered in

the system. Also it handles the purchase of new titles for the Book Bank.
Popular titles are brought into multiple copies. Old books and magazines are
removed when they are out or date or poor in 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 tiles, members, loans and reservations from the system.

(II) SOFTWARE RESOURCE SPECIFICATION:

OVERALL DESCRIPTION

It will describe major role of the system components

and inter-connections.

PRODUCT PERSPECTIVE

The ORS acts as an interface between the user and the 'e-book
manager'. This system tries to make the interface as simple as possible and at
the same time not risking the security of data stored in. This minimizes the
time duration in which the user receives the books or magazines.

SOFTWARE INTERFACE

Front End Client - The Student and Librarian online interface is built
using JSP and HTML. The Librarians local interface is built using Java.

Web Server - Glassfish application server (Oracle Corporation).

Back End - Oracle database

HARDWARE INTERFACE

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

The server is directly connected to the client systems. The client

systems have access to the database in the server.

(III)USE-CASE DIAGRAM:

Fig.3.USE-CASE DIAGRAM FOR E-BOOK SYSTEM

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

(IV) ACTIVITY DIAGRAM:

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

(V)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
show what each object will do in the problem domain. The problem domain
describes the structure and the relationships among objects.

Fig.5.CLASS DIAGRAM FOR E-BOOK SYSTEM

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

(VI) INTERACTION 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 and events include signals, inputs,
decisions, interrupts, transitions and actions to or from users or external
devices.

An event also is considered to be any action by an object that sends

information. The event line represents a message sent from one object to
another, in which the “form” object is requesting an operation be performed
by the “to” object. The “to” object performs the operation using a method
that the class contains.

It is also represented by the order in which things occur and how the
objects in the system send message to one another.

The sequence diagram and collaboration diagram are given below.

Fig.6.1.SEQUENCE DIAGRAM

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

Fig.6.2.COLLABORATION DIAGRAM

(VII) PARTIAL LAYERD LOGICAL ARCHITECTURE DIAGRAM

UI

Swing

E-Book system

Domain

Client Order

bill Credit History Process Balance

Technical Services

Persistence
SOAP Log4J

DBFacade

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

(VIII) DEPLOYMENT DIAGRAM AND COMPONENT DIAGRAM

Deployment diagrams are used to visualize the topology of the
physical components of a system where the software components are
deployed.

<<client workstation>>: GenericPC

<<database>>
:MySQL

SQL HTTP

<<server>> :To mcat6

Fig.8.1.DEPLOYMENT DIAGRAM

COMPONENT DIAGRAM
Component diagrams are used to visualize the organization and relationships
among components in a system.

Fig.8.2.COMPONENT DIAGRAM
RESULT:
Thus the mini project for E-Book System has been successfully
executed and codes are generated.

Downloaded by Rudra ([email protected])

 lOMoARcPSD|44294995

Downloaded by Rudra ([email protected])