EX NO:

STUDY OF UML
DATE:

AIM

DESCRIPTION

The heart of Software Engineering problem solving is the construction of a model. The model abstracts
the essential details of the underlying problem from its usually complicated real world. Several
modeling tools are wrapped under the heading of the UML, which stands for Unified Modeling
Language. The purpose of this course is to present important highlights of the UML.
At the center of the UML are its nine kinds of modeling diagrams, which we describe here.
Use case diagrams
Class diagrams
Object diagrams
Sequence diagrams
Collaboration diagrams
State chart diagrams
Activity diagrams
Component diagrams
Deployment diagrams
Some of the sections of this course contain links to pages with more detailed information. And every
section has short questions. Use them to test your understanding of the section topic.

Why is UML important?

Let's look at this question from the point of view of the construction trade. Architects design
buildings. Builders use the designs to create buildings. The more complicated the building, the more
critical the communication between architect and builder. Blueprints are the standard graphical
language that both architects and builders must learn as part of their trade.

Writing software is not unlike constructing a building. The more complicated the underlying
system, the more critical the communication among everyone involved in creating and deploying the
software. In the past decade, the UML has emerged as the software blueprint language for analysts,
designers, and programmers alike. It is now part of the software trade. The UML gives everyone from
business analyst to designer to programmer a common vocabulary to talk about software design.

The UML is applicable to Software Engineering problem solving. Anyone interested in

learning UML must be familiar with the underlying tenet of Software Engineering problem solving -- it
all begins with the construction of a model. A model is an abstraction of the underlying problem. The
domain is the actual world from which the problem comes. Models consist of objects that interact by
sending each other message. Think of an object as "alive." Objects have things they know (attributes)
and things they can do (behaviors or operations). The values of an object's attributes determine their
state. Classes are the "blueprints" for objects. A class wraps attributes (data) and behaviors (methods or
functions) into a single distinct entity. Objects are instances of classes.

Name: Reg No:

Use case diagrams

Use case diagrams describe what a system does from the standpoint of an external observer. The
emphasis is on what a system does rather than how.

Use case diagrams are closely connected to scenarios. A scenario is an example of what happens when
someone interacts with the system. Here is a scenario for a medical clinic."A patient calls the clinic to
make an appointment for a yearly checkup. The receptionist finds the nearest empty time slot in the
appointment book and schedules the appointment for that time slot. "

A use case is a summary of scenarios for a single task or goal. An actor is who or what initiates the events
involved in that task. Actors are simply roles that people or objects play. The picture below is a Make
Appointment use case for the medical clinic. The actor is a Patient. The connection between actor and use
case is a communication association (or communication for short).

Actors are stick figures. Use cases are ovals. Communications are lines that link actors to use cases. A
use case diagram is a collection of actors, use cases, and their communications. We've put Make
Appointment as part of a diagram with four actors and four use cases. Notice that a single use case can
have multiple actors.

Use case diagrams are helpful in three areas.

 Determining features (requirements)- New use cases often generate new requirements as the
system is analyzed and the design takes shape.
 Communicating with clients- Their notational simplicity makes use case diagrams a good way for
developers to communicate with clients.
 Generating test cases- The collection of scenarios for a use case may suggest a suite of test cases
for those scenarios.

Name: Reg No:

Class diagrams

A Class diagram gives an overview of a system by showing its classes and the relationships among them.
Class diagrams are static -- they display what interacts but not what happens when they do interact. The
class diagram below models a customer order from a retail catalog. The central class is the Order.
Associated with it are the Customer making the purchase and the Payment. A Payment is one of three
kinds: Cash, Check, or Credit. The order contains OrderDetails (line items), each with its associated Item.

UML class notation is a rectangle divided into three parts: class name, attributes, and operations. Names
of abstract classes, such as Payment, are in italics. Relationships between classes are the connecting links.
Our class diagram has three kinds of relationships.

Association -- a relationship between instances of the two classes. There is an association between two
classes if an instance of one class must know about the other in order to perform its work. In a diagram,
an association is a link connecting two classes.

Aggregation -- an association in which one class belongs to a collection. An aggregation has a diamond
end pointing to the part containing the whole. In our diagram, Order has a collection of Order Details.
The multiplicity of an association end is the number of possible instances of the class associated with a
single instance of the other end. Multiplicities are single numbers or ranges of numbers. In our example,
there can be only one Customer for each Order, but a Customer can have any number of Orders.This table
gives the most common multiplicities.

Multiplicities Meaning
0..1 zero or one instance. The notation n . . m indicates n to m instances.
0..* or * no limit on the number of instances (including none).
1 exactly one instance
1..* at least one instance

Name: Reg No:

Every class diagram has classes, associations, and multiplicities. Navigability and roles are optional items
placed in a diagram to provide clarity.

Packages and object diagrams

To simplify complex class diagrams, you can group classes into packages. A package is a collection of
logically related UML elements. The diagram below is a business model in which the classes are grouped
into packages.

Packages appear as rectangles with small tabs at the top. The package name is on the tab or inside the
rectangle. The dotted arrows are dependencies. One package depends on another if changes in the other
could possibly force changes in the first.
Object diagrams show instances instead of classes. They are useful for explaining small pieces with
complicated relationships, especially recursive relationships. This small class diagram shows that a
university Department can contain lots of other Departments.
The object diagram below instantiates the class diagram, replacing it by a concrete example.

Name: Reg No:

Each rectangle in the object diagram corresponds to a single instance. Instance names are underlined in
UML diagrams. Class or instance names may be omitted from object diagrams as long as the diagram
meaning is still clear.

Sequence diagrams

Class and object diagrams are static model views. Interaction diagrams are dynamic. They describe how
objects collaborate.
A sequence diagram is an interaction diagram that details how operations are carried out what messages
are sent and when. Sequence diagrams are organized according to time. The time progresses as you go
down the page. The objects involved in the operation are listed from left to right according to when they
take part in the message sequence.
Below is a sequence diagram for making a hotel reservation. The object initiating the sequence of
messages is a Reservation window.

The Reservation window sends a makeReservation() message to a HotelChain. The HotelChain

then sends a makeReservation() message to a Hotel. If the Hotel has available rooms, then it makes a
Reservation and a Confirmation.
Each vertical dotted line is a lifeline, representing the time that an object exists. Each arrow is a message
call Each vertical dotted line is a lifeline, representing the time that an object exists. The activation bar
represents the duration of execution of the message.
In our diagram, the Hotel issues a self call to determine if a room is available. If so, then the Hotel creates
a Reservation and a Confirmation. The asterisk on the self call means iteration (to make sure there is
available room for each day of the stay in the hotel). The expression in square brackets, [ ], is a condition.

Name: Reg No:

Collaboration diagrams

Collaboration diagrams are also interaction diagrams. They convey the same information as sequence
diagrams, but they focus on object roles instead of the times that messages are sent. In a sequence
diagram, object roles are the vertices and messages are the connecting links.

The object-role rectangles are labeled with either class or object names (or both). Class names are
preceded by colons ( : ).

Each message in a collaboration diagram has a sequence number. The top-level message is numbered 1.
Messages at the same level (sent during the same call) have the same decimal prefix but suffixes of 1, 2,
etc. according to when they occur.

Statechart diagrams

Objects have behaviors and state. The state of an object depends on its current activity or condition. A
statechart diagram shows the possible states of the object and the transitions that cause a change in state.
Our example diagram models the login part of an online banking system. Logging in consists of entering
a valid social security number and personal id number, then submitting the information for validation.
Logging in can be factored into four non-overlapping states: Getting SSN, Getting PIN, Validating, and
Rejecting. From each state comes a complete set of transitions that determine the subsequent state.

Name: Reg No:

States are rounded rectangles. Transitions are arrows from one state to another. Events or
conditions that trigger transitions are written beside the arrows. Our diagram has two self- transition, one
on Getting SSN and another on Getting PIN.
The initial state (black circle) is a dummy to start the action. Final states are also dummy states that
terminate the action.
The action that occurs as a result of an event or condition is expressed in the form /action. While in its
Validating state, the object does not wait for an outside event to trigger a transition. Instead, it performs
an activity. The result of that activity determines its subsequent state.

Activity diagrams:

An activity diagram is essentially a fancy flowchart. Activity diagrams and statechart diagrams are
related. While a statechart diagram focuses attention on an object undergoing a process (or on a process
as an object), an activity diagram focuses on the flow of activities involved in a single process. The
activity diagram shows the how those activities depend on one another.
For our example, we used the following process.

"Withdraw money from a bank account through an ATM."

The three involved classes (people, etc.) of the activity are Customer, ATM, and Bank. The process
begins at the black start circle at the top and ends at the concentric white/black stop circles at the bottom.
The activities are rounded rectangles.

Name: Reg No:

Activity diagrams can be divided into object swimlanes that determine which object is responsible for
which activity. A single transition comes out of each activity, connecting it to the next activity.

A transition may branch into two or more mutually exclusive transitions. Guard expressions (inside [ ])
label the transitions coming out of a branch. A branch and its subsequent merge marking the end of the
branch appear in the diagram as hollow diamonds.

A transition may fork into two or more parallel activities. The fork and the subsequent join of the threads
coming out of the fork appear in the diagram as solid bars.

Name: Reg No:

Component and deployment diagrams:

A component is a code module. Component diagrams are physical analogs of class diagram. Deployment
diagrams show the physical configurations of software and hardware.

The following deployment diagram shows the relationships among software and hardware components
involved in real estate transactions.

The physical hardware is made up of nodes. Each component belongs on a node. Components are shown
as rectangles with two tabs at the upper left.

RESULT:

Name: Reg No:

EX NO:
PASSPORT AUTOMATION SYSTEM
DATE:
.

AIM:

To create an automated system to perform the Passport Process.

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.

SOFTWARE REQUIREMENT SPECIFICATION:

SOFTWARE INTERFACE

Front End Client - The applicant and Administrator onlineinterface is built using JSP and HTML.
The Administrators's local interface is built usingJava.
Web Server - Glassfish application server(Oracle Corporation).
Back End - Oracle database.

HARDWARE INTERFACE

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

1.USECASE DIAGRAM

Fig.1. USECASE DIAGRAM FOR PASSPORT AUTOMATION SYSTEM

Name: Reg No:

2. ACTIVITY DIAGRAM:

Fig.2.1. ACTIVITY DIAGRAM FOR REGISTER

Fig.2.2. ACTIVITY DIAGRAM FOR ADMINISTRATION

Name: Reg No:

 Fig.2.3. ACTIVITY DIAGRAM FOR CHECKING STATUS
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.3. CLASS DIAGRAM FOR PASSPORT AUTOMATION SYSTEM

Name: Reg No:

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

Fig. 4.1.SEQUENCE DIAGRAM FOR ADMINISTRATOR

Name: Reg No:

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

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

Fig 5.1.DEPLOYMENT DIAGRAM

Name: Reg No:

COMPONENT DIAGRAM

Component diagrams are used to visualize the organization and relationship among components in system

Fig 5.2.COMPONENT DIAGRAM

Name: Reg No:

OUTPUT :

Name: Reg No:

RESULT

Name: Reg No:

EX NO:
BOOK BANK SYSTEM
DATE:
2

AIM :

PROCEDURE :

1. Develop a problem statement.

2. Identify Use cases and develop the Use case Model.
3. Design activity diagram and sequence diagram for use case.
4. Draw state chart diagram.
5. Draw package, component and deployment diagrams.
6. Draw class diagram and generate code.

PROBLEM STATEMENT:

To promote effective sharing of books among students, book bank is used. Books purchased under
the book bank scheme are the property of that particular book bank. The users are entitled to borrow
books from the faculty. The faculty will determine duration of a loan for a book but that should in no case
exceed duration period. A user must return a borrowed book within the prescribed loan period. With the
exception of certain categories of books in the book bank, all books may be borrowed from the faculty
book bank by filling in the borrowing form. The date and the user’s name will be entered on the data card.
The book card will be removed from the book packet. The signing of the book card and borrowing form
constitute the loan. A user remains responsible for a book as long as borrowing records in the faculty
remain un-cancelled. A user is not authorized to loan a book to another reader. Borrowed books must be
returned to the faculty book bank. A user who loses a book or fails to return book will be required to pay
the fine.

PROJECT SCOPE:

The book bank deals with sharing of books among user like students and staffs. The faculty book bank
also provides membership to the user and it allows the member to take the book from the book bank.
Mainly, the students and staffs in colleges utilize these facilities.

PROJECT OBJECTIVES:

The aim of the book bank is to help in the selection of books for the university’s departments, schools and
Institutes. This book bank should provide limited funds allocated for text books.

SOFTWARE REQUIREMENT ANALYSIS:

The modules of the book bank are:

 Book details
Name: Reg No:
  Issue borrowing form and book card
 Issue book
 Return book
 Pay fine
 Issuing receipt

Book details:
The module of book details consists of certain book details such as Engineering books, medical books,
business management books etc,.

Issue borrowing form and book card

The faculty will issue the borrowing form which consists of data and the user’s name. The faculty will
also issue book card to get a sign from a user and these two constitute the loan.

Issue book:
This module is used by the faculty of the book bank to issue books to the user.

Return book:
This module is used by the user to return the books to the faculty of the book bank on or before duration
period.

Pay fine:
The user will pay fine to the accountant through this module.

Issuing Receipt:
After paying the fine, the accountant will give receipt to the user through this module.

SOFTWARE REQUIREMENTS SPECIFICATION

INTRODUCTION
Book Bank is the interface between the students and Librarian. It aims at improving the efficiency in the
Issue of books or magazines and reduce the complexities involved in it to the maximum possible extent.

PURPOSE
If the entire process of 'Issue of Books or Magazines' is done in a manual manner then it would take
several months for the books or magazines to reach the applicant. Considering the fact that the number of
students for Book Bank is increasing every year, an Automated System becomes essential to meet the
demand. So this system uses several programming and database techniques to elucidate the work involved
in this process. The system has been carefully verified and validated in order to satisfy it.

SCOPE
The System provides an online interface to the user where they can fill in their personal details and submit
the necessary documents (may be by scanning). The authority concerned with the issue of books can use
this system to reduce his workload and process the application in a speedy manner.

DEFINITIONS, ACRONYMS AND THE ABBREVIATIONS

Librarian - Refers to the super user who is the Central Authority who has been vested with the privilege to
manage the entire system

Student - One who wishes to obtain the Books or Magazines.

Name: Reg No:

 HTML - Markup Language used for creating web pages.
J2EE - Java 2 Enterprise Edition is a programming platform and it is the part of the java platform for
developing and running distributed java applications.
HTTP -Hyper Text Transfer Protocol
TCP/IP - Transmission Control Protocol/Internet Protocol is the communication protocol used to connect
hosts on the Internet.

REFERENCES
IEEE Software Requirement Specification format

TECHNOLOGIES TO BE USED
Visual Basic
Oracle 11g

TOOLS TO BE USED
Visual Basic Tools
ArgoUML (for developing UML Patterns)

OVERVIEW
SRS includes two sections overall description and specific requirements.
Overall description will describe major role of the system components and inter- connections. Specific
requirements will describe roles & functions of the actors.

OVERALL DESCRIPTION
It will describe major role of the system components and inter-connections.

PRODUCT PERSPECTIVE
The SRS acts as an interface between the 'Students' and the 'Librarian'. 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 Visual studio.
Back End - Oracle 11 g database

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

SYSTEM FUNCTIONS
Secure Registration of information by the Students.
Librarian can generate reports from the information and is the only authorized personnel to add the
eligible application information to the database

USER CHARACTERISTICS
Student - They are the people who desire to obtain the books and submit the information to the database.
Librarian - He has the certain privileges to add the books and to approval of the reservation of books.

CONSTRAINTS
The Students require a computer to submit their information.
Although the security is given high importance, there is always a chance of intrusion in the web world
Name: Reg No:
 which requires constant monitoring.
The Students has to be careful while submitting the information. Much care is required.

ASSUMPTIONS AND DEPENDENCIES

The Student and Librarian must have basic knowledge of computers and English Language.
The Students may be required to scan the documents and send.

1. USE-CASE DIAGRAM

Fig 1. USE-CASE DIAGRAM FOR BOOK BANK SYSTEM

Name: Reg No:

 2. ACTIVITY DIAGRAM:

Fig.2. ACTIVITY DIAGRAM

Name: Reg No:

 3. 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.3. CLASS DIAGRAM FOR BOOK BANK SYSTEM

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

Name: Reg No:

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

Name: Reg No:

 Fig. 4.2. COLLABORATION DIAGRAM FOR DEPOSIT PROCESS

5.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>>
:MySQL workstation>>:
GenericPC

SQL HTTP

<<server>> :To
mcat6

Name: Reg No:

 Component diagrams are used to visualize the organization and relationships

Fig.5.1.DEPLOYMENT DIAGRAM & COMPONENT DIAGRAM

Name: Reg No:

OUTPUT

Name: Reg No:

RESULT:

Name: Reg No:

EX NO:

FOREIGN TRADING SYSTEM

DATE:

AIM

PROBLEM STATEMENT

The steps involved in Foreign Trading System are:

The forex system begins its process by getting the username and password from the trader. After the
authorization permitted by the administrator, the trader is allowed to perform the sourcing to know about
the commodity details.After the required commodities are chosen, the trader places the order.The
administrator checks for the availability for the required commodities and updates it in the database. After
the commodities are ready for the trade, the trader pays the amount to the administrator.The administrator
in turn provides the bill by receiving the amount and updates it in the database.The trader logouts after the
confirmation message has been received.

SOFTWARE REQUIREMENT SPECIFICATION

ADMINISTRATOR One who coordinates the entire tradingprocess.

DATABASE All the transaction details are storedhere.

READER Person who is viewing the website.

USER The traders and the viewers are theusers.

FUNCTIONALITY
Transfer purchasing power between countries. Obtain credit for international trade transactions.
Minimize exposure to the risks of exchange rate changes.

FUNCTIONALITY REQUIREMENTS
Functional requirements refers to the functionality of the system. The services that are provided to the
trader who trades.

Name: Reg No:

 UML DIAGRAMS
The exporter submits the relevant documents to his buyer (banker) for getting the paymentfor the goods
exported.

1.USE CASE DIAGRAM

Fig 1.USE CASE DIAGRAM

2.CLASS DIAGRAM
A class diagram is a type of static structure diagram that describes the structure of a system. The
classes in the class diagram represent both the main objects and or interactions in the application.The
class diagram is represented using rectangular boxes each of which contains three parts:

Name: Reg No:

 Fig 2.CLASS DIAGRAM

3.SEQUENCE DIAGRAM

A sequence diagram in unified modeling language 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.
Sequence diagrams are sometimes called event diagrams, event scenarios, and timing diagrams. This
diagram shows a parallel vertical lines called lifelines. There are two dimensions in this diagram.
Vertical dimension-represents time.
Horizontal dimension-represent different object

Name: Reg No:

 Fig 3.SEQUENCE DIAGRAM
4.COLLABORATION DIAGRAM
A collaboration diagram belongs to a group of UML diagrams called Interaction Diagrams.
collaboration diagrams, like sequence diagrams, show how the objects interact over the course of
time. collaboration diagrams show the sequence by numbering the messages on the diagram.

Fig 4.SEQUENCE DIAGRAM

Name: Reg No:

 5. STATE CHART DIAGRAM
The state chart is used to model dynamic nature of a system. They define different states of an object
during its lifetime. And these states are changed by events. So these diagrams are useful for reactive
systems i.e.., a system that responds to external or internal events. It describes the flow of control
from one state to other state. The initial state is represented using the small dot. The final state is
represented using a circle surrounded by a small dot

6. DOCUMENTATION OF STATE CHART DIAGRAM

The state diagram represents the following states.
 The trader logins the register in the first state and performs sourcing in thesecond state. The trader
places the order in the third state.
 The trader receives the bill in the fourth state and pay the required amountin fifth state.
 The trader logouts from the system in the sixth state

7. ACTIVITY DIAGRAM
This diagram represents the graphical representation of workflows of stepwise activities and actions
with support for choice, iteration and concurrency. It shows the overall flow of control.

DOCUMENTATION OF ACTIVITY DIAGRAM

 This activity diagram represents the flow of stepwise activities performed in foreign trading
system.
 The first action represents the trader logins to the system.
 The second action is the place where the trader places the order.
 The decision state is the state where the trader decides to place the order.
 If the trader places the order, fill the form for the required commodities.
 The next activity is that the administrator provides the bill for thosecommodities.
 The trader pays for the bill and logout from the system.

8. COMPONENT DIAGRAM
A component diagram depicts how the components are wired together to form larger components and
or software systems. Components are wired together by using an assembly connector to connect the
required interface of one component with the provided interface of another component.

Fig 5.COMPONENT DIAGRAM

Name: Reg No:

 9. DEPLOYMENT DIAGRAM
A deployment diagram models the physical deployment of artifacts on nodes. The nodes appear as
boxes, and the artifacts allocated to each node appear as rectangles within the boxes. Nodes may have
sub nodes, which appear as nested boxes.

Fig 6.DEPLOYMENT DIAGRAM

10.PACKAGE DIAGRAM
A package diagram in the unified modeling language depicts the dependencies between the packages
that make up a model. It provides a wayto group the elements. There are three types of layers in
package diagram. They are

 User interface layer

 Domain layer

 Technical services layer

User interface layer

The user interface layer may call upon its directly subordinate application logic layer, and also upon
elements of a lower technical service layer, for logging and so forth.

Domain layer
Software objects representing domain concepts (for example, a software class administrator) that
fulfill application requirements, such as tracingorder and providing thebill..

Technical services layer

The sourcing and updating the details areperformed in this layer.

Name: Reg No:

OUTPUT:

Name: Reg No:

Name: Reg No:
Name: Reg No:
 RESULT:

Name: Reg No:

EX NO:

EXAM REGISTRATION SYSTEM

DATE:

AIM:

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.

SOFTWARE REQUIREMENT SPECIFICATION:

SOFTWARE INTERFACE

Front End Client –

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

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

1. USECASE DIAGRAM:
The Exam Registration use cases in our system are:
Login
View exam details
View fees details
Pay fee
Display details
Logout

Name: Reg No:

 Fig. 1.USECASE DIAGRAM FOR EXAM REGISTRATION SYSTEM

Name: Reg No:

 2. ACTIVITY DIAGRAM:

Fig. 2.ACTIVITY DIAGRAM FOR EXAM REGISTRATION SYSTEM

Name: Reg No:

 3. 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.3. CLASS DIAGRAM FOR EXAM REGISTRATION SYSTEM

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

Name: Reg No:

 Database :
ExamController

Fig. 4.1. Fig SEQUENCE DIAGRAM FOR REGISTRATION SYSTEM

Fig.4.2. COLLABORATION DIAGRAM FOR REGISTRATION SYSTEM

Name: Reg No:

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

Fig.5.1. DEPLOYMENT DIAGRAM

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

Fig.5.2. COMPONENT DIAGRAM

Name: Reg No:

OUTPUT:

Name: Reg No:

 RESULT:

Name: Reg No:

EX NO:
STOCK MAINTAINEANCE SYSTEM
DATE:

AIM

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.

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.
Provide a communication platform between the customer and the sales person.

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

Name: Reg No:

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

Name: Reg No:

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

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

An Order An Order An Order Line A Stock Item

Name: Reg No:

 SEQUENCE DIAGRAM

Name: Reg No:

 COLLABORATION DIAGRAM

5.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
<<client
<<database>
:MySQL workstation>>
: GenericPC

Name: Reg No:

 Component diagrams are used to visualize the organization and relationshipsamong components
in a system.

Name: Reg No:

OUTPUT:

Name: Reg No:

 RESULT:

Name: Reg No:

EX NO;

ONLINE COURSE RESERVATION SYSTEM

DATE:

AIM

PROBLEM STATEMENT

Whenever the student comes to join the course he/she should be provided with the list of course
available in the college.
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.

SYSTEM REQUIEMENT SPECIFICATION

OBJECTIVES
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. It specifies the requirement
to develop a processing softwarepart that completes the set of requirement.

SCOPE

In this specification, we define about the system requirements that are about from the functionality
of the system.It tells the users about the reliability defined in usecasespecification

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

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

Name: Reg No:

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

1.USERCASE DIAGRAM

 Use case is a sequence of transaction in a system whose task isto yield result of measurable value
to individual author of the system
 Use case is a set of scenarios together by a common user goal
 A scenario is a sequence of step describing as interactionbetween a user and a system.

2.CLASS DIAGRAM:

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

Name: Reg No:

 3.SEQUENCE DIAGRAM

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

Name: Reg No:

Name: Reg No:
 4.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.

Name: Reg No:

 5.ACTIVIY DIAGRAM
It includes all the activities of particular project and various steps using join and forks

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

Name: Reg No:

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

8.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
User interface layer
Domain layer
Technical services layer

Name: Reg No:

OUTPUT

RESULT

Name: Reg No:

EX NO:

SOFTWARE PERSONNEL MANAGEMENT SYSTEM

DATE:
AIM

PROCEDURE
 Develop a problem statement.
 Identify Use cases and develop the Use case Model.
 Design activity diagram and sequence diagram for use case.
 Draw state chart diagram.
 Draw package, component and deployment diagrams.
 Draw class diagram and generate code.

PROBLEM STATEMENT
If student mark analyzing system the students are allotted their respective marks. The actors for this
system include in the students, staff and the parents. The use case includes conducting the exam,
calculation of overall percentage, evaluation of mark and reporting. The mark obtained by each
student in a particular exam will be note by the staff and later stored in database. The student in all
the six papers will calculate the series exam mark as the basis pf the marks scored. Similarly the
series exam marks and model exam marks are calculated. These marks are needed to find out the
performance of a student in a particular batch. The details regarding the marks will be available to
the staff from the database. The staff will be able to analyze the marks of a particular student in
various exams and can assign the internal marks accordingly. The staff will send the report
concerning the marks of their parents. In the University Exam Mark calculation the marks will
be calculated with the help of database. The analysis of the mark in the database will help the staff
members to calculate the student overall pass percentage.

PROJECT SCOPE
This student mark analyzing system the students are allotted with their respective marks. The
student’s mark analyzing system is deals with exam result, calculation of overall percentage,
evaluation and reporting. The marks obtained by each student in a particular exam will be noted by
staff and later stored in database.

PROJECT OBJECTIVES
The aim of this student mark and analyzing system is to analyzing the mark of need features and to
design and test. This student analyzing system should provide required features of the student.

SOFTWARE REQUIREMENT ANALYSIS

The student mark analyzing system includes the following modules:
 Conducting exam
 Evaluating
 Calculating percentage
 Reporting
 Conducting exam

Name: Reg No:

 Initially the students should write the exams. The staff is preparing the questions for the exams and
using the question to students. The students are writing the exam and return back the answer sheet.
Finally the staff is checking the answer sheet.

Evaluating:
The staff members read the answer sheet. After reading the answer, issue the marks for each
question. Sum the mark of all the objects and the total is stored in the database.

Calculating Percentage:
Access the total mark details from the database. After, calculate the percentage using the
number of subjects. After calculation store the details to database. Reporting:- Staff member access
the mark details from the database. The mark details are sending to the parents. After that, access
feedback from the parents of the students for the mark details.

SOFTWARE REQUIREMENT SPECIFICATION

INTRODUCTION
This document aims at defining overall software requirement for ACADEMIC RESULT
MANAGEMENT SYSTEM .Efforts have been made to define the requirements exhaustively and
accurately. The final product will be having only features/functionalities mentioned in this
document and assumptions for any additional functionality/feature should not be made by any of the
parties involved in developing/testing/implementing /using this product .

PURPOSE
This specification document describes the capabilities that will be provided by the software
application STUDENT RESULT MANAGEMENT SYSTEM .It also states the various constraints
by which the system will abide. The intended audience for this document are the development team,
testing team and end users of the product.

SCOPE
The application will manage the information about various students enrolled in this course in
different years, the subjects offered during different semesters of the course, the marks obtained by
the various students in various subjects in different semesters. The application will greatly simplify
and speed up the result preparation and management process.

DEFINITIONS, ACRONYMS, AND ABBREVIATIONS IEEE-The Institute of Electrical and

Electronics Engineers
DFD- Data Flow Diagram
DB-Database
OS -Operating System

REFERENCES
IEEE 8301998 standard for writing SRS document.
Wikipedia
Software engineering by KK Agrawal
Software engineering by Roger S. Pressman

OVERVIEW
Student’s information is stored in mysql the authority is given to Administrator; he gives the
permission to instructor to enter the department data and student information. The security is
providing by giving password to each instructor.

Name: Reg No:

 GENERAL DESCRIPTION
This section of the SRS should describe the general factors that affect 'the product and its requirements.
It should be made clear that this section does not state specific requirements; it only makes those
requirements easier to understand.

PRODUCT PERSPECTIVE
The application will be windows based, selfcontained and independent software product.

PRODUCT FUNCTIONS
Information about the various Users
Information about subjects offered in various semesters
Marks obtain by Students in different semesters
Generation of Reports

USER CHARACTERISTICS
This subsection of the SRS should describe those general characteristics of the eventual users of the
product that will affect the specific requirements.

GENERAL CONSTRAINTS
Users at university will have to implement a security policy to safeguard the marks related information
being modified by unauthorized users.

ASSUMPTIONS AND DEPENDENCIES

The number of subjects to be taken by the student in each semester does not change.
The subject types do not change.
The number of semester do not change.
The users have sufficient knowledge of computers.
The users know the English language, as the user interface will be provided in English.

1.USECASE DIAGRAM

Name: Reg No:

 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 gives
the expected performance and manages time in order to complete a given task within the required
period.

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

Name: Reg No:

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

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

Name: Reg No:

 SEQUENCE DIAGRAM

COLLABORATION DIAGRAM

Name: Reg No:

 5. 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 movesfrom the prior state to the subsequent.

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

Name: Reg No:

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

Name: Reg No:

OUTPUT:

Name: Reg No:

 RESULT

Name: Reg No:

EX NO:

AIRLINE/RAILWAY RESERVATION SYSTEM

DATE:

AIM

PROCEDURE
 Develop a problem statement.
 Identify Use cases and develop the Use case Model.
 Design activity diagram and sequence diagram for use case.
 Draw state chart diagram.
 Draw package, component and deployment diagrams.
 Draw class diagram and generate code. employees

PROBLEM STATEMENT
The function of this system is we can reserve ticket through online. So for using this system we can
reserve from our house without going the reservation counter. For using online reservation system we
can reserve the railway tickets. In this reservation system we can reserve the starting station and
destination. For using this online reservation system we can reserve the tickets very easily.

PROJECT SCOPE
This e-ticketing system deals with reserving the tickets and views the details. If we want to cancel the
tickets we can cancel. The passenger and the station master utilize these facilities.

PROJECT OBJECTIVES
The aim of this e-ticketing system is to get the ticket through online reservation. This should provide
the required features to be passenger.

SOFTWARE REQUIREMENT ANALYSIS

This e-ticketing system includes the following modules:
Reservation
Cancel ticket
Update ticket
View train details

Reservation:-
The passenger will request to reserve ticket. The administrator checks whether seats is available or
not. Then the administrator conformed if seat is available otherwise administration gives the
information that there is no seat is available.
Cancel ticket:-
If the passenger wants to cancel the ticket, the administrator will check whether the ticket is reserved
or not. Then he cancel the ticket.

Name: Reg No:

 Update ticket:-
The passenger asks the administrator to show the update details. Then he show the update details to
the passenger.
View train details:-
The passenger will request to view the train details. The administrator will show the details to the
passenger.

SOFTWARE REQUIREMENT SPECIFICATION

INTRODUCTION
The manual system of ticket reservation takes more time and the number of reservations per day is
limited. To increase the efficiency of the process, we go for online ticket reservation system. This
system supports online ticket booking.

PURPOSE
If the entire process of reservation is done in a manual manner then it would takes several months for
reservation to reach the applicant. Considering the fact that the number of passenger is increasing
every year, an Automated System becomes essential to meet the demand. So this system uses several
programming and database techniques to elucidate the work involved in this process. As this is a
matter of National Security, the system has been carefully verified and validated in order to satisfy it.

SCOPE
 The System provides an online interface to the user where they can fill in their personal details and
submit the necessary documents (may be by scanning).
 The authority concerned with the issue of railway can use this system to reduce his workload and
process the application in a speedy manner.
 Provide a communication platform between the passenger and the administrator.
 Passenger will come to know their status of application and the date in which they must subject
themselves for manual document verification.

DEFINITIONS, ACRONYMS AND THE ABBREVIATIONS

Passenger – The person that who wishes to obtain the railway ticket.
PNR – Passenger Name Records
HTML - Markup Language used for creating web pages.
J2EE – Java 2 Enterprise Edition is a programming platform java platform for developing and
running distributed java applications.
HTTP - Hyper Text Transfer Protocol.
TCP/IP – Transmission Control Protocol/Internet Protocol is the communication protocol used to
connect hosts on the Internet.

REFERENCES
IEEE Software Requirement Specification format.

TECHNOLOGIES TO BE USED
HTML
JSP
Javascript
Java

TOOLS TO BE USED
ArgoUML

Name: Reg No:

 OVERVIEW
SRS includes two sections overall description and specific requirements –
Overall Description will describe major role of the system components and inter- connections.
Specific Requirements will describe roles & functions of the actors.

OVERALL DESCRIPTION
PRODUCT PERSPECTIVE
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 ticket.

SOFTWARE INTERFACE
Front End Client - The passenger and System online interface is built using JSP and HTML. The
Administrators's local interface is built using Java.
Web Server – Apache Tomcat Server (Oracle Corporation)
Back End - Oracle 11g database

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

SYSTEM FUNCTIONS
Secure Registration of information by the Passengers.
System can generate reports from the information and is the only authorized personnel to add the
eligible application information to the database.
Display the requested pages to the user.
Update the database after every successful process.

USER CHARACTERISTICS
Passenger - They are the people who desire to obtain the ticket and submit the information to the
database.

CONSTRAINTS
The passengers require a computer to submit their information.
Although the security is given high importance, there is always a chance of intrusion in the web
world which requires constant monitoring.
The user has to be careful while submitting the information. Much care is required

ASSUMPTIONS AND DEPENDENCIES

 The Passengers must have basic knowledge of computers and English Language.
 The passengers may be required to scan the documents and send.

Name: Reg No:

 UML DIAGRAM :
1. USE CASE DIAGRAM :

issue ticket
2. CLASS DIAGRAM

Name: Reg No:

 .
3.SEQUENCE DIAGRAM

Passengers Ticket agent Database

4.COLLABORATION DIAGRAM

Name: Reg No:

 5. ACTIVITY DIAGRAM

6. STATE DIAGRAM:

7. DEPLOYMENT DIAGRAM

ticket management System

O ticket
confirmation

Name: Reg No:

 8.COMPONENT DIAGRAM:

Name: Reg No:

OUTPUT

RESULT

Name: Reg No:

EX NO:

CREDIT CARD PROCESSING SYSTEM

DATE:

AIM

PROCEDURE
 Develop a problem statement.
 Identify Use cases and develop the Use case Model.
 Design activity diagram and sequence diagram for use case.
 Draw state chart diagram.
 Draw package, component and deployment diagrams.
 Draw class diagram and generate code.

PROBLEM STATEMENT
The credit card system includes actors such as customer and credit card controller. Also it includes
the use cases such as withdraw, membership ID. In the credit card system customer can easily
withdraw the money without any difficulties in order to use the credit card system, customer needs
the credit card. At first the card can be obtained by opening the account in any one of the bank,
after 15 days the credit card send to the house by corresponding authorities, the customer can
withdraw the money by inserting the credit card system into the credit machine. Then select the
option language, then it will ask the pin number. Then it will ask to enter the amount. After
entering the touch yes option. Then the corresponding amount will obtained from credit card
machine after getting the leave the credit card controller.

PROJECT SCOPE
The credit card system deals with the process of transaction the money to the customer and money
is to be deposited. The customer needs the credit card for withdrawing the money. The customers
who have the credit card utilize these facilities.

SOFTWARE REQUIREMENT ANALYSIS

It deals with following operations
Withdraw money
Verification and Updating Withdraw money:
Customer gets the membership card from the bank. Then the customer will use the membership
card to take money from the credit machine. The customer can perform withdraw of money in
account.
Verification and updating:
The credit controller accesses the id and after accessing it checks the pin number whether it is correct
or not.
If it is correct means then the requirement amount is transacted from the customer account.

Name: Reg No:

 SOFTWARE REQUIREMENT SPECIFICATION
INTRODUCTION
A credit card is a small plastic card issued to users as a system of payment. It allows its holder to
buy goods and services based on the holder's promise to pay for these goods and services. The
issuer of the card creates a revolving account and grants a line of credit to the consumer (or the
user) from which the user can borrow money for payment to a merchant or as a cash advance to
the user.
When a purchase is made the merchant swipes the card. The information goes to a gateway
processor, which either accepts or rejects the transaction. If it is accepted, the transaction is held
until the end of the business day. The merchant then reenters the transaction via the gateway
processor, the data is logged, and the debt is transferred to the account. The use of an ATM for
cash advance is a similar process.
If you are selling to consumers, merchant services will allow you to expand your customer base
and provide a more convenient method of payment than cash or checks. And if you are interested
in selling over the Internet, accepting credit card processing is a must. Accepting credit cards
allows funds to be transferred to your bank account in less than a week. This can be a welcome
relief for businesses that experience a tight cash flow.

The two purchase options for Credit Card Processing facility are:
Validation only
Credit card processing (which secures deposits at the time of booking)
With either option, credit card accounts entered during booking are validated to assure that the
account is active and in good standing. The credit card processing option also allows properties to
process credit card deposits.

PURPOSE
When customers complete their shopping cart, their credit card is preauthorized and the order is
entered into Sales Order. Credit Card Processing dials out and obtains a credit card payment.
Within five minutes the customer receives an e-mail receipt.

SCOPE
Automatically connects to your financial network for credit card authorizations and settlements
Integrates with Sales Order, Accounts Receivable, and e-Business Manager
Support for dial-up (modem) connections or secure Internet connections through TCP/IP and SSL
Compliant with Visa and MasterCard Electronic Commerce Indicator (ECI) regulations
Multiple address verification options available .

DEFINITIONS, ACRONYMS AND THE ABBREVIATIONS

Authorization service - The issuer of the card creates a revolving account and grants a line of
credit to the consumer (or the user) from which the user can borrow money for payment to a
merchant or as a cash advance to the user.
User- One who wishes to uses the credit card.
CCP - Refers to this Credit Card Processing.
HTML - Markup Language used for creating web pages.
J2EE – Java 2 Enterprise Edition is a programming platform java platform for developing and
running distributed java applications.
HTTP - Hyper Text Transfer Protocol.
TCP/IP – Transmission Control Protocol/Internet Protocol is the communication protocol used to
connect hosts on the Internet.
REFERENCES
IEEE Software Requirement Specification format.

Name: Reg No:

 TECHNOLOGIES TO BE USED
HTML
JSP
Javascript
Java

TOOLS TO BE USED
ArgoUML

OVERVIEW
SRS includes two sections overall description and specific requirements – Overall Description will
describe major role of the system components and inter- connections. Specific Requirements will
describe roles & functions of the actors.

OVERALL DESCRIPTION
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
The server is directly connected to the client systems. The client systems have access to the
database in the server.

SYSTEM FUNCTIONS
Accept credit card numbers on the web, store them in a database, then process them off-line
Credit card processing with CCP
Credit card processing with a third-party credit card processing company

USER CHARACTERISTICS
User/Customer - They are the people who desires to purchase the goods using credit card.
Authorization Service
Validate the credit card payments to ensure that the card number is valid and the card has not
expired
Deposit processing to apply the deposit payment to the card
Prepare Credit card transaction reports that show authorization codes, amounts, and error/success
messages

CONSTRAINTS
 Trusted if using a well known third-party processor
 Must suite for higher-volume sites
 Cheaper transaction rates
 Getting money transferred may be very fast
 Must provide fraud prevention measures and fraud protection programs

Name: Reg No:

 ASSUMPTIONS AND DEPENDENCIES
The Applicants and Administrator must have basic knowledge of computers and English
Language.
The applicants may be required to scan the documents and send.

UML DIAGRAMS
1.USE CASE DIAGRAM

2.CLASS DIAGRAM

Name: Reg No:

 3.INTERACTION DIAGRAM
SEQUENCE DIAGRAM

COLLABORATION DIAGRAM

Name: Reg No:

 4. COMPONENT AND DEPLOYMENT DIAGRAM
COMPONENT DIAGRAM

DEPLOYMENT DIAGRAM

Name: Reg No:

OUTPUT

Name: Reg No:

 RESULT

Name: Reg No:

EX NO:

CONFERENCE MANAGEMENT SYSTEM

DATE:

AIM

PROBLEM STATEMENT
The process of the candidates is to login the conference system and submit the paper through online.
Then the reviewer reviews the paper and sends the acknowledgement to the candidate either paper
selected or rejected. This process of on conference management system are described sequentially
through following steps,
 The candidate login to the conference management system.
 The paper title is submitted.
 The paper is been reviewed by the reviewer.
 The reviewer sends acknowledgement to the candidate.
 Based on the selection, the best candidate is selected.
 Finally the candidate registers all details.

SOFTWARE REQUIREMENT SPECIFICATION

CANDIDATE The candidate can login and submit the paper to the
reviewer. After getting acknowledgement the candidate will
submit the revised and camera ready paper then registration
process
will be carried out.

REVIEWER Reviewer will reviews the paper and sending

acknowledgement to the candidate
DATABASE Database is used to verify login and store the details of
selected candidates.

SOFTWARE This software specification documents full set of features

REQUIREMENT and function for conference management system.
SPECIFICATION

Name: Reg No:

 PURPOSE
The purpose of the conference management system is that the system can easily review the process.
The main process in this document is the submission of paper by the candidate, reviewing process by
the reviewer andsending of acknowledgement to the candidates whose paper is selected.

SCOPE
The scope of this conference management process is to select the best candidate from the list of
candidates based on their performance in the process.

FUNCTIONALITY
The main functionality of conference system is to select the candidate for thepresentation in
conference.

USABILITY
The user interface to make the process should be effective that is the system will help the candidates
to register easily. The system should be user friendly.

PERFORMANCE
It describes the capability of the system to perform the conference process ofthe candidate without
any error and performing it efficiently.

RELIABILITY
The conference system should be able to serve the applicant with correct information and day-to-day
update of information.

FUNCTIONAL REQUIREMENTS
Functional requirements are those that refer to the functionality of the system that is the services that
are provided to the candidate who register forthe conference.

UML DIAGRAMS
The following UML diagrams describe the process involved in the
conference management system.

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 modeled. It is represented using stick
figure.

DOCUMENTATION OF USE CASE DIAGRAM

The actors in this use case diagram are candidate, reviewer and database.The use cases are the
activities performed by actors.
The actors in this use case diagram are
Candidate - Logins the conference system and submits the paper then dothe
registration process.
Reviewer – Review the paper , select best candidate and
sendacknowledgement to them.

Databases - verify the login and register details and selected candidate details are
Name: Reg No:
 stored in it. The use cases in this use case diagram are
Login - Candidate enter their username and password to login to the conference
system.
Paper sumbission– Candidate submits the paper.
Review the paper– The paper is been reviewed by the reviewer and the paper is
selected.
Paper confirmation details – The reviewer can send the confirmation details to
the candidate.
Revised and camera ready paper – After the paper is selected and the camera ready
paper should be submitted to the reviewer by candidate.
Registration – After submitting the revised paper the candidate wants to register.

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

Name: Reg No:

 This class diagram has three classes candidate, reviewer and database.

Candidate – Its attributes are name ,collegename , department , paper title. The
operations performed in the candidate class are login, submit the paper, submit revised
and camera ready paper and registration.
Reviewer – Its attributes are name, department, reviewer ID The operations performed
are review the paper and send the paper confirmation details.
Database –The operations performed are storing candidate details and verifying login .

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.
Vertical dimension-represent time.
Horizontal dimension-represent different objects.

Name: Reg No:

 DOCUMENTATION OF SEQUENCE DIAGRAM LOGIN
 This sequence diagram describes the sequence of steps to show
 The candidate login in to the conference system and register for job.
 The verification done in the database .

PAPER SUBMISSION
 This sequence diagram shows steps to show
 The candidate sumbit the paper.
 The reviewer reviews the paper and sends acknowlegement to the candidate.
 The candidate submits revised and camera ready paper.
 This candidate will registers their detials.

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.

Name: Reg No:

 DOCUMENTATION OF COLLABRATION DIAGRAM LOGIN
This collaboration diagram is to show how the applicant login in the conference system. Here the
sequence is numbered according to the flow of execution.

PAPER SUBMISSION
This collaboration diagram is to show the submitting paper process of the candidate for the
conference. The flow of execution of this selection process is represented using the numbers.

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 behaviour of the system.

• First state is login where the candidate login to the conference system.

• The next state is submitting the paper .

• Then review the paper if it is selected the process will continue..

• The candidate should submit revised and camera ready paper.

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
Name: Reg No:
 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 recruitmentsystem.
 First the candidate login to the database.
 Then the candidate should submit the paper.
 If it is selected the acknowledgement will send to the candidate.
 After submitting revised paper the registration proces will be done.

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

DOCUMENTATION OF COMPONENT DIAGRAM

The main component in this component diagram is conference management system. And submit
the paper, review the paper and registration.

DEPLOYMENT DIAGRAM
A deployment diagram in the unified modeling language serves to model thephysical 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-dimensional
box. Dependencies are represented by com

Name: Reg No:

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

DOCUMENTATION OF PACKAGE DIAGRAM

The three layers in the online recruitment system are

The User interface layer - consists of the web and login. This layer describes how the
candidate login.

The Domain layer – shows the activities that are performed in the conference
management system. The activities are paper submission , reviewpaper , registration.

The Technical service layer - the verification details and the selected candidate details
will stored into the database.

Name: Reg No:

 OUTPUT

RESULT

Name: Reg No:

EX NO:

LIBRARY MANAGEMENT SYSTEM 90

DATE:

AIM

PROCEDURE
 Develop a problem statement.
 Identify Use cases and develop the Use case Model.
 Design activity diagram and sequence diagram for use case.
 Draw state chart diagram.
 Draw package, component and deployment diagrams.
 Draw class diagram and generate code. Problem statement
E-book includes the following functions:entering the user details,searching for the
books,selecting the books for purchase,paying the bill issued and delivery of books.The actors of
this system include the students,online bookshopping center and travel agent.The usecase
includes login,searching the list of books,selecting the books to be purchased,paying the bill and
delivery of books.
First the user logins using his name and password which is stored in the database,if it does not
exist previously.Otherwise, the id is accepted and the books are displayed.Now the user searches
for hi requirements from the books displayed.Then selecting the books is being done by the
user.The selected books are displayed along with their amount.The user orders and pays for the
books.The books are delivered to the user by the online bookshopping center through a travel
agent.

PROJECT SCOPE
The e-book deals with purchase and payment of books.The online bookshopping center allows the
user to search and purchase books available at that time.We can search the books in an efficient
manner.

PROJECT OBJECTIVES
The aim of this e-book system is to search and purchase books for the user’s requirements.The e-
book system should provide all the facilities required.
Software requirement analysis
The e-book system involves the following modules:

 Login
 Searching the books
 Selecting the books
 Purchasing the books
 Delivering the books

Name: Reg No:

 Login
This module is used to accept the user name and password if it is valid.

Searching the books

This module is used to search the books according to the user’s needs.

Selecting the books

This module is used to select a particular set of books from a large set.

Purchasing the books

This module is used to pay and purchase the books required.

Delivering the books

This module is used to deliver the books to the user through a travel agent.

SOFTWARE RESOURCE SPECIFICATION

INTRODUCTION
E-Book is the interface between the students and Librarian. It aims at improving the efficiency in
the Issue of books or magazines and reduces the complexities involved in it to the maximum
possible extent.

PURPOSE
If the entire process of 'Issue of Books or Magazines' is done in a manual manner then it would
take several months for the books or magazines to reach the applicant. Considering the fact that
the number of students for Book Bank is increasing every year, an Automated System becomes
essential to meet the demand. So this system uses several programming and database techniques
to elucidate the work involved in this process. The system has been carefully verified and
validated in order to satisfy it.

SCOPE
The System provides an online interface to the user where they can fill in their personal details
and submit the necessary documents (may be by scanning). The authority concerned with the
issue of books can use this system to reduce his workload.

DEFINITIONS, ACRONYMS AND THE ABBREVIATIONS

E-book manager
Refers to the super user who is the Central Authority who has been vested with the privilege to
manage the entire system.

User
who wishes to obtain the Books or Magazines.

Visitor
One who visits to obtain Books or Magazines.

Administrator
One who manages and maintain Books or Magazines.

REFERENCES
IEEE Software Requirement Specification format

TECHNOLOGIES TO BE USED
HTML - Markup Language used for creating web pages.
J2EE - Java 2 Enterprise Edition is a programming platform and it is the part of the java platform
for developing and running distributed java applications.
Name: Reg No:
 HTTP -Hyper Text Transfer Protocol
TCP/IP - Transmission Control Protocol/Internet Protocol is the communication protocol used to
connect hosts on the Internet.

TOOLS TO BE USED
ArgoUML(for developing UML Patterns)

OVERVIEW
SRS includes two sections overall description and specific requirements.
Overall description will describe major role of the system components and inter- connections.
Specific requirements will describe roles & functions of the actors.

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
Apache Tomcat application server (Oracle Corporation).
Back End
Oracle 11g database

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

Name: Reg No:

 UML DIAGRAMS

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

Name: Reg No:

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

3.STATECHART DIAGRAM
State chart 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 stages such as
login, enter details, requesting for book, display book details, search book, issue book, return book
and logout.

login enter requesting

details for book

return book search

book

4. COLLABORATION DIAGRAM
Like sequence diagram collaboration diagrams are also called as interaction diagram. Collaboration
diagram convey the same informations 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.

Name: Reg No:

 5.SEQUENCE DIAGRAM
A sequence diagram represent the sequence and interactions of a given use case or scenario.
Sequence diagram capture most of the information about the system. It is also represent 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 have been
selected the next half of sequence starts between librarian and user followed by database.

Name: Reg No:

Name: Reg No:
 6.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.

library management
system

7.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 system and execution environment nodes are user, librarian, system and
DBA.

Name: Reg No:

OUTPUT

Name: Reg No:

 RESULT

Name: Reg No:

EX NO:

AUTOMATION OF RECRUITMENT SYSTEM

DATE: AIM:

PROCEDURE
 Develop a problem statement.
 Identify Use cases and develop the Use case Model.
 Design activity diagram and sequence diagram for use case.
 Draw state chart diagram.
 Draw package, component and deployment diagrams.
 Draw class diagram and generate code.

PROBLEM STATEMENT
Recruitment system includes the following functions submitting the resume, conducting
aptitudes test, conducting group discussion display short list, conducting technical and personal
interview, display selected candidates. The actors of this system include job seek, clerk,
company team and HR Management. The use of the system include submit the resume, conduct
aptitude test, group discussion etc. They will display a short list. Then the HR Management will
conduct personal interview and they will display the selected candidates.

PROJECT SCOPE
The recruitment system deals with applying jobs through Online the company team will conduct
aptitude test, group discussion etc. They will display a short list. Then the HR
Management will conduct personal interview and they will display the selected candidates.

PROJECT OBJECTIVES
The objective of these websites is to serve as common meeting ground for jobseekers and
employers, both logically and globally, where the candidates find their dream job and recruiter
find the right candidate to full fill their needs.

SOFTWARE REQUIREMENT ANALYSIS

The recruitment system includes the following modules,
 Submit Resume
 Verify Resume
 Conduct Aptitude Test
 Conduct Group Discussion
 Display Short List

Name: Reg No:

 Conduct Technical and Personal Interview Submit Resume :
 First the user will submit the resume to the clerk.
 The clerk will verify the user’s resumed and store it in his database.
 This company team will conduct aptitude test to the user.
 This module is used to conduct group discussion to the user by the company team.
 This module is used to display the selected in the test conducted by the company team.
 This module is used to conduct final interview to the user by the HR management.

SOFTWARE REQUIREMENT SPECIFICATION

INTRODUCTION
Recruitment System is an interface between the Applicant and the Organization responsible for the
Recruitment. It aims at improving the efficiency in the Recruitment process and reduces the complexities
involved in it to the maximum possible extent.

PURPOSE
If the entire process of ‘Recruitment' is done in a manual manner then it would takes several days for the
recruitment. Considering the fact that the number of applicants for recruitment is increasing every year,
an Automated System becomes 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 online interface to the user where they can fill in their personal details and apply
for the job.
The Organization (HR-Department) concerned with the recruitment process can make use of this system
to reduce their workload and process the application in a speedy manner. Provide a communication
platform between the Applicant and the Organization.

DEFINITIONS, ACRONYMS AND THE ABBREVIATIONS

Organization
Refers to the super user who is the Central Authority with the privilege to manage the entire system. It
can be any higher official in the HR department.

Applicant
One who wishes to apply for the job.

RS-Refers to this Recruitment System.

HTML- Hypertext Markup Language used for creating web pages.
J2EE-Java 2 Enterprise Edition is a programming platform java platform for developing and running
distributed java applications.
HTTP- Hyper Text Transfer Protocol.
TCP/IP-Transmission Control Protocol/Internet Protocol is the communication protocol used to connect
hosts on the Internet.

REFERENCES
IEEE Software Requirement Specification format.

TECHNOLOGIES TO BE USED

Name: Reg No:

 HTML
JSP
Javascript
Java
TOOLS TO BE USED
ArgoUML (for developing UML Patterns)

OVERVIEW
SRS includes two sections overall description and specific requirements
Overall Description will describe major role of the system components and inter- connections. Specific
Requirements will describe roles & functions of the actors.

OVERALL DESCRIPTION
PRODUCT PERSPECTIVE
The RS acts as an interface between the ''Applicant and the 'Organization'. 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 for recruitment process.

SOFTWARE INTERFACE
Front End Client –The Applicants and Organization online interface is built using JSP and HTML. The
Administrators’ local interface is built using Java.
Web Server - Glassfish application server (SQL Corporation).
Back End - SQL database.

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

SYSTEM FUNCTIONS
 The applicant views the jobs through Advertisement.
 Applicants apply for the job.
 Test and Interview are conducted.
 Recruited Applicants are informed.
 HR Manager can generate reports from the information and he/she is the only authorized
personnel to add the eligible application information to the database.

USER CHARACTERISTICS
Applicant
These are the persons who desire to apply for the job.

Organization
These are the person with certain privileges to announce recruitment depending upon the organization
need. He/ She may contain a group of persons under him/her to publish advertisement and give
suggestion whether or not to approve the recruitment.

HR
He/ She is the person who upon receiving intimation from the RS, perform a personal verification of the
applicants and see if he/she has eligibility for the advertised job through a process of Test and Interview.

Name: Reg No:

 CONSTRAINTS
The Applicants require a computer to submit their information.

ASSUMPTIONS AND DEPENDENCIES

The Applicants and HR must have basic knowledge of computers and English Language.
UML Diagrams: Use case diagram:

1.USECASE DIAGRAM
The Recruitment Automation system use cases are:

Name: Reg No:

 2.ACTIVITY DIAGRAM

3.UML CLASS DIAGRAM:

The UML class diagram is to illustrate class interfaces and their actions. They are used for static
object modeling, we have already introduced andused their UML diagram while domain modeling.

Name: Reg No:

 4.UML SEQUENCE DIAGRAM
A sequence diagram illustrates a kind of format in which each object interacts via message. It is
generalize between two or more specializeddiagram.

Fig. 4.1SEQEUENCE DIAGRAM FOR Register

Name: Reg No:

 Fig.4.2. SEQUENCE DIAGRAM FOR STATUS

Fig.4.3. SEQUENCE DIAGRAM FOR Admin

Name: Reg No:

 Fig.4.4. SEQUENCE DIAGRAM FOR Notify vacancy

5.UML COLLABRATION DIAGRAM

Communication diagram illustrate that object interact on a graph or network format in which object
can be placed where on the diagram. In collaboration diagram the object can be placed in anywhere
on the diagram. The collaboration comes from sequence diagram.

Fig.5.1COLLABRATION DIAGRAM For Register

Name: Reg No:

 Fig.5.2. COLLABORATION DIAGRAM FOR Status

Fig.5.3.COLLABORATION DIAGRAM FOR Admin

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

Fig.6.1.DEPLOYMENT DIAGRAM

Name: Reg No:

 Fig.6.2 COMPONENET DIAGRAM

Name: Reg No:

 OUTPUT

Name: Reg No:

 RESULT

Name: Reg No:

 CONTENT BEYOND SYLLABUS

EX NO:

BPO MANAGEMENT SYSTEM

DATE:

AIM

PROBLEM STATEMENT
With the reduction in communication costs and improved bandwidthsand associated infrastructure, BPO
as a segment is witnessing a massive growth. One of the key challenges that BPO companies that provide
data entry/data validation services is an efficient and effective way of getting the source documents from
different customers and accurately route the same todifferent operators for processing.

SOFTWARE REQUIREMENT SPECIFICATION:

PRODUCT PERSPECTIVE
The BPOS acts as an interface between the 'client' and the'administrator'. 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 documents.

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
The BPO system’s server is directly connected to the client systems via ftp. The client systems have access to
the database in the server.

Name: Reg No:

1.USECASE DIAGRAM:
The BPO management system use cases are:

2.UML CLASS DIAGRAM

The UML class diagram is to illustrate class interfaces and their actions. They are used for static
object modeling, we have already introduced and used their UML diagram while domain
modeling.

Name: Reg No:

 Fig 2.UML CLASS DIAGRAM

3.UML SEQUENCE DIAGRAM

A sequence diagram illustrates a kind of format in which each object interacts via message. It is
generalize between two or more specializeddiagram.

Communication diagram illustrate that object interact on a graph or network format in which object
can be placed where on the diagram. In collaboration diagram the object can be placed in anywhere
on the diagram. The collaboration comes from sequence diagram.

Name: Reg No:

 Fig.3. SEQUENCE DIAGRAM

4.COLLABORATION DIAGRAM

Fig.4.COLLABRATION DIAGRAM

Name: Reg No:

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

DEPLOYMENT DIAGRAM

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

SQL FTP

<<server>
>

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

RESULT

Name: Reg No: