CS8582

OBJECT
ORIENTED
ANALYSIS
AND
DESIGN
LABORATORY
 INDEX

S. No Date Topic Mark Sign

1 20.10.2020 Passport automation system

2 20.10.2020 Book bank

3 20.10.2020 Exam registration

4 27.10.2020 Stock maintenance system

5 27.10.2020 Online course reservation system

6 27.10.2020 Airline/ Railway reservation system

Software personnel management

7 27.10.2020
system

8 03.11.2020 Credit card processing

9 03.11.2020 E-book management system

10 03.11.2020 Recruitment system

11 03.11.2020 Foreign trading system

12 10.11.2020 Conference management system

13 10.11.2020 BPO management system

14 10.11.2020 Library management system

15 10.11.2020 Student information system

Ex no:1 Date:20.10.2020

PASSPORT AUTOMATION SYSTEM

AIM:
To create an automated system to perform the Passport Process.
HARDWARE REQUIREMENTS:
 Intel Pentium Processor 3
SOFTWARE REQUIREMENTS:
 ArgoUML/Rational rose / Visual Basic
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 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.
HARDWARE INTERFACE:
The server is directly connected to the client systems. The client systems
have access to the database in the server.
USE CASE DIAGRAM:

Actors: Applicant, Administrator.

Use case: registration, check status, process applicant, dispatch passport.
CLASS DIAGRAM:
 CLASSES ATTRIBUTES OPERATIONS
Passport Automation - -
New Registration name,age,dateofbirth, register(),cancel()
placeofbirth,gender,fathername,
mothername,address
Application Status applicationidnumber getstatus()
Gender male,female -
Admin Authentication username,password login()
Admin Panel yettobeproceedapplication, process()
dispatchedapplicationid,
applicationid
ACTIVITY DIAGRAM:
New Registration:

Activities: Passport Automation System, New Registration, Enter Details,

Register.
Checking Status:

Activities: Passport Automation System, Check Status, Status Display, Enter

Valid Applicant Id.
Decision box:Check whether the Applicant id is found or not.
Administration:
Activities: Passport Automation System, Admin Pane;, Enter Username and
Password, Display the Admin Panel, Enter Valid Username and Password, Display
the yet to be processed and dispatched applications.
Decision box: Check whether Authentication Succeed or not.
SEQUENCE DIAGRAM:
New Registration:

Object: applicant, system, database.

Checking Status:
Object: applicant, system, database.
Administration:

Object: administrator, system, admin panel, database, application.

COLLABORATION DIAGRAM:
New Registration:

Object: applicant, system, database.

Checking Status:

Object: applicant, system, database.

Administration:

Object: administrator, system, admin panel, database, application.

STATE CHART DIAGRAM:

States: Login, Registration, Application form, Fill the form, Enquiry,

Verification, Payment, Getting the passport.
DEPLOYMENT DIAGRAM:
COMPONENT DIAGRAM:

RESULT:
Thus the mini project for passport automation system has been successfully
executed and codes are generated.
Ex no : 2
BOOK BANK
Date : 20/10/2020

AIM:
To create a system to perform book bank operation
HARDWARE REQUIREMENTS:
• Intel Pentium Processor 3
SOFTWARE REQUIREMENTS:
• ArgoUML / Rational rose / Visual Basic
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.
SOFTWARE REQUIREMENTS SPECIFICATION:
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 (OracleCorporation).
• 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.
USE CASE DIAGRAM:
This diagram will contain the actors, use cases which are given below
Actors: Student, Database, Administrator
Use case: registration, searchtools, getbooks, membershipstatus
CLASS DIAGRAM:
This diagram consists of the following classes, attributes and
their operations.
CLASSES ATTRIBUTES OPERA
TIONS
Book bank - -
manageme
nt system
Registratio name,age,address,college,yearofstudy,contactnumbe register()
n r,memberid,username,password
Authentica username, password login()
tion
Booksearc Title, author, publications, ISBN search()
h
Getbooks BookID,memberID,duration get(),
checkstat
us()
Membershi Status, lastrenewal, booksholding, Nextrenewal returnstat
pstatus us()

ACTIVITY DIAGRAM:
This diagram will have the activities as start point, end point, decision
boxes.
Activities : Book bank management system, register, enter details, details valid
, invalid reg, obtain member id, successful registration, authentication, enter
member id and password, valid, authentication failed, enter into panel,
authentication successful, book search, enter search criteria, display results, get
books, enter book id, enter duration, membership active, calculate bill, obtain
the book, status, enter member id, display membership status.
Decision box : check whether details valid or not, check whether
authentication
succeed or not, check whether membership active or not.

SEQUENCE DIAGRAM:
The sequence diagram for each USE-CASE that exists when a user
administrator, check status and new registration about bank book system are
given. This diagram consists of the objects, messages and return messages.
REGISTRATION:

Object : student, administrator, database

AUTHENTICATION:
Object : student, database

SEARCH BOOKS:

Object : student, database

GET BOOKS:

Object : student, administrator, database

MEMBERSHIP STATUS:

Object : student, database

COLLOBORATION DIAGRAM:
This diagram contains the objects and actors.
REGISTRATION:

Object : student, administrator, database

AUTHENTICATION:

Object : student, database

SEARCH BOOKS:

Object : student, database

GET BOOKS:

Object : student, administrator, database

MEMBERSHIP STATUS:

Object : student, database

STATE CHART DIAGRAM:

The state chart diagram define different states of an object during its
lifetime and these states are changed by events.

REGISTRATION:

States: Enter details, Get member id, successful registration, reenter details.
AUTHENTICATION:

States: enter member id, enter password, successful login, invalid username or
password.

SEARCH BOOKS:

States: enter book search criteria, display book suggestions,display book not
found.
GET BOOKS:

States: enter book id, enter member id, obtain books, display fine and prompt
for renewal.
DEPLOYMENT DIAGRAM:
Deployment diagrams are used to visualize the topology of the physical
components of a system where the software components are deployed.
COMPONENT DIAGRAM:
Component diagrams are used to visualize the organization and relationships.

RESULT :
Thus the mini project for Book Bank System has been successfully executed
and codes are generated.
EX NO: 3
EXAM REGISTRATION SYSTEM
DATE: 20/10/2020

AIM:
To create a system to perform the Exam registration system.
HARDWARE REQUIREMENTS:
1. Eclipse IDE (Integrated development environment)
2. Rational rose tool (for developing UML patterns)
SOFTWARE REQUIREMENTS:
1. HTML
2. JSP
3. Java Script
4. Java
PROBLEM STATEMENT:
Exam registration 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 exam
registration system with respect to the already existing information in the
database. This is the 1st and foremost step in processing of exam application. After
the 1st round the information is in turn forwarded to the exam controller. The
application also gives the list of exam dates for the students and the controller will
be provided with the fees details of the students. After all necessary criteria has
been met, the original information is added to the database and the hall ticket is
sent to the students.

SOFTWARE REQUIREMENT SPECIFICATION:

REFERENCE: IEEE Software requirement specification format.

SOFTWARE INTERFACE:
FRONT END CLIENT - The exporter online interface is built using JSP and
HTML.
WEB SERVER - Apache tomcat server (Oracle Corporation).
BACK END - Oracle 11g database
HARDWARE INTERFACE:
The hardware is directly connected to the client system. The client system
have access to the database in the server.
USE CASE DIAGRAM:
The following diagram contains actors and use case which are given
below

ACTORS : Student, System DB.

USE CASE : Login, view exam details, register, fee processing,
acknowledgement.

CLASS DIAGRAM:
This diagram contains classes, attributes and their operations.
CLASS ATTRIBUTES OPERATIONS
Login Username,password Verify(),login()

Student st_id,st_name,DOB,gender,qualification,address addStudent(),

details , updateStudent(),
mobile_no,email_id,username,password getlogin()
Exam Exam_code,exam_name,subject_id,subject_nam addExam()
details e,duration, updateExam(),
Dateofexam,fee,age_limit,criteria,exam_centren delExam()
ame,
Exam_centrecode
Register St_id,exam_code,subject_id,no_of_subjects,fee, getRegister(),
reg_date,DD_no, cancelReg(),
Reg_id,exam_centrecode verifyInfo()
Internet ID,password Allowaccess(),
explorer Display()

System DB ID,password Storedetails(),

Updatedetails()
ACTIVITY DIAGRAM:
This diagram will have the activities as start point, end point, decision
boxes.

ACTIVITIES:
Enter PWD, Search, Display, Get registration form, Fill registration form, Fees
Payment, Verification, Show error message, Store details and Display Register
number and acknowledgement.
SEQUENCE DIAGRAM:
The sequence diagram represents the sequence and interactions of a
given USE-CASE or scenario diagram can capture most of the informatio about
the system. Most object to object interactions and operations are considered events
and events include signals, inputs, decisions,transitions and actions to or from
users or external devices.
COLLABORATION DIAGRAM:
The sequence diagram and the collaboration diagram represents that
the student enter the information to get the hall ticket after verifying the
necessary items and this data are stored in database. It contains objects and
actors.
STATE CHART DIAGRAM
The State Chart Diagram for the Exam registration system is given
below

STATES: Student, login, viewdetails, getregform, fillregform, payment

DEPLOYMENT DIAGRAM:
The deployment diagrams are used to visualize the topology of
the physical components of a system where the software components are
deployed.
COMPONENT DIAGRAM:
Component diagrams are used to visualize the organization
and relationship among the components in system.

RESULT:

Thus the mini project for the Exam registration system has been
successfully executed and codes are generated.
Ex.No: 4
Date:27.10.2020

STOCK MAINTENANCE SYSTEM

Aim:
To create a system to perform the Stock maintenance.

HARDWARE REQUIREMENT :
❖ Intel Pentium Processor 3

SOFTWARE REQUIREMENT :
❖ ArgoUML / Rational Rose / Virtual Basic

PROBLEM STATEMENT :
This software is designed for supporting the computerized stock maintainence
System .In this system, the customer can place order and purchase items with the aid of the
stock dealer and central stock system. This orders are verified and the items are delivered to
the customer.

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

USE CASE DIAGRAM :

This diagram will contain the actors, use cases which are given below.

Actors:employee, manager, administrator, database, customer.

Use case: maintain stocks, login, purchase order, view report, view stock.
CLASS DIAGRAM :
This diagram consists of the following classes, attributes and their operations.

MAINTAIN STOCKS :
PURCHASE ORDERS :
 Classes Attributes Operations

Login customer details order( )

Purchase order quantity, price create( )

change( )

delete( )

Maintain stock product details, add( )

quantity
update( )

delete( )

View stock available stocks stock details( )

View report bill, transaction details report stock( )

View stock - verification( )

Report administrator details display( )

Stock details availability specification( )

display( )

Add stock stock information quantity( )

product( )

change( )

Update stock - enter id( )

change( )

update( )
 Delete stock retrieve details confirm ( )

verify ( )

delete ( )

ACTIVITY DIAGRAM :
This diagram will have the activities as Start point ,End point, Decision boxes as given below:
Activities: pay ,update ,take order, fill order, deliver order, collect order.
Decision box: Valid or not.

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.

SEQUENCE DIAGRAM

A sequence diagram is a graphical view of scenario that shows

object interaction in a time based sequence what happens first what

happens next.

LOGIN :
VIEW STOCK :
MAINTAIN STOCKS :
PURCHASE ORDER :
COLLABORATION DIAGRAM :
 A collaboration diagram is an interaction diagram that shows the

order of messages that implement an operation or a transaction.

MAINTAIN STOCKS :
PURCHASE ORDER :

PACKAGE DIAGRAM
DEPLOYMENT DIAGRAM
 Deployment diagram are used to visualize the topology of the

physical components of a system where the software components

are deployed.

COMPONENT DIAGRAM
 Component diagram are used to visualize the organization and

relationships among components in a system .

RESULT :

Thus the mini project for stock maintenance system has been successfully
executed and codes are generated.
 Ex no : 5
Online Course Reservation System

Date : 27/10/2020

AIM:
To create a system through which students can register to the courses desired
by them.

HARDWARE REQUIREMENTS:
• Intel Pentium Processor 3
SOFTWARE REQUIREMENTS:
• ArgoUML/Rational rose / Visual Basic

PROBLEM STATEMENT:
The system is built to be used by students and managed by an administrator. The
student and employee have to login to the system before any processing can be done.
The student can see the courses available to him/her and register to the course he/she
wants. The administrator can maintain the course details and view all the students who
have registered to any course.
SOFTWARE INTERFACE:

• Front End Client - The Student and Registrar online interface is built using
JSP and HTML. The Administrator's local interface is built using Java.

• Web Server – Tomcat Apache 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.

USE CASE DIAGRAM:

This diagram will contain the actors, use cases which are given below
Actors : Student, Registrar.

Use case : View course details, Login, Reserve for course, Pay fee, Check status.

CLASS DIAGRAM:
The class diagram is a graphical representation of all the classes used in the
system and their operations, attributes and relationships.
The course registration system makes use of the following classes:
1. Student
2. Course Catalog
3. Reserve Course

1) STUDENT:

It consists of the details of all the students present in the database. The attributes
present in this class are student id, student name, student qualification, student
address1, student address2, student address3, student mobile no, student emailed,,
student dob, student sex. The object of this class is created as soon as the student
registers to a course. The operations available to this class are add details (), modify
details (), del details (), reserve course().

2) COURSE CATALOG:

The course catalog class consist of course id, course name, course duration
course fee, course eligibility, total no of seat, course avail seat. The operations are add
course(), update course(), del course().

3) RESERVE COURSE:

The reserve catalog class consists of student id, course id, date, amt paid, reg id,
DD no. the operation are get course details(), check eligibility(), confirm registration().

ACTIVITY DIAGRAM:
This diagram will have the activities as Start point ,End point, Decision boxes.
 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 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 course registration system are given.
• Users have to first login to the system before performing any operation. The user has
to provide the necessary details to the system for login.
 COLLABORATION DIAGRAM:
This diagram contains the objects and actors.

• After login, the student has to register to a course of his choice. The student can view
all the courses available to him and register to a course suitable to him. The student
may view the course details before registration.
• A student may wish to view course details before registration. For this, the student has
to first login and select the course details he wishes to see.

STATE CHART DIAGRAM:

Every object undergoes through some state and on receiving some event the state
gets changed. This transition of the state can be represented by the state transition
diagram.
 States : View course, Select course, Fill form, Submit form, Gets confirmation,
Pay fees, Reserves Seat.

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

Result:
Thus the mini project for Course Reservation system has been successfully
executed and codes are generated.
EXNO:
6 AI
RLI
NE/
RAI
LWAYRESERVATI
ONSYSTEM

Dat
e:27/
10/
2020

AI
M:

Todev
elopt
heAi
rl
ine/
Rai
l
wayr
eser
vat
ionSy
stem usi
ngRat
ional
RoseSof
twar
e.

PROBLEMANALYSI
SANDPROJECTPLANNI
NG:

RailwayReser v
ationSy stem isasy st
em usedf orbookingti
cketsoverint
ernet.
Any
CustomerCanbookt i
cket sfordifferenttr
ains.
Cust omercanbookat i
cketonl
yifthet i
cket
sare
avai
lable.Customersear chesf ortheav ail
abil
it
yoft i
cketsthenift
het i
cketsar
eav ai
lablehe
bookst heticket
sbyi nit
iall
yf i
l
lingdet ai
lsinaform.Forcancel l
ati
onoft i
ckett
hecust omerhas
togoatr eservati
onof fi
cet hanf i
l
l cancell
ati
onf orm andasktheclerktocancelthetickett
han
therefundist r
ansferr
edt ocust omeraccount .
Afterbookingti
cketthecustomerhast o
checkoutbypay i
ngfareamountt oclerk.

USECASEDI
AGRAM:

Act
ors:
Cust
omer,
cler
k,websi
te.

Usecase:enqui
ryt
icketav
ail
abl
e,f
il
lfor
m,bookt
icket
,payf
airamount
,pr
intf
orm,
cancel
t
icket
,ref
undmoney.
CLASSDI
AGRAM:
ACTI
VITYDI
AGRAM FORBOOKI
NG:
ACTI
VITYDI
AGRAM FORCANCELLATI
ON:
SEQUENCEDI
AGRAM FORBOOKI
NG:
SEQUENCEDI
AGRAM FORCANCELLATI
ON:

l
COLLABORATI
ONDI
AGRAM FORBOOKI
NG:

COLLABORATI
ONDI
AGRAM FORCANCELLATI
ON:
DEPLOYMENTDI
AGRAM:
COMPONENTDI
AGRAM:

RESULT:

Thust
hemi
nipr
oject
for
Air
li
ne/
Rai
l
way
reser
vat
ionSy
stemhasbeensuccessf
ull
y

execut
edandcodesar
egener
ated.
EX NO: 7 SOFTWARE PERSONNEL MANAGEMENT

DATE: 27/10/2020

AIM:
To create a system to perform the Software Personnel Management system.

HARDWARE REQUIREMENTS:
1. Eclipse IDE (Integrated development environment)
2. Rational rose tool (for developing UML patterns)

SOFTWARE REQUIREMENTS:
1. HTML
2. JSP
3. Java Script
4. Java

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.

SOFTWARE REQUIREMENT SPECIFICATION:

REFERENCE: IEEE Software requirement specification format.

SOFTWARE INTERFACE:
FRONT END CLIENT- The exporter online interface is builtusing JSP and HTML.
WEB SERVER- Apache tomcat server (Oracle Corporation).
BACK END: Oracle 11g database

HARDWARE INTERFACE:
The serveris directly connected to the client systems. The client systems have access to the
database in the server.
USE CASE DIAGRAM:
The followingdiagram contains actors and use case whic
which aregiven below

ACTORS : HR and Employee.

USE CASE:Recruit, Training, Salary, Monitor, Performance, Increment, Time Management and
Motivation.
CLASS DIAGRAM:
This diagram contains classes, attributesand their operations
operations.

CLASS ATTRIBUTES OPERATIONS

HR Curriculam
ulam Vitae, Employee, Salary Increment and Monitor Recruit, Monitor,
Increment and
Motivation.
Employee Commitment, Accounts and Regularity Training, Salary
and Performance
Training Educated Trainees Training
Details
Salary Details Create Bank Account Salary
Time Time period timemanagement
management
ACTIVITY DIAGRAM:
This diagram will have the activities as start point, end point, decision boxes.

Activities:
HR Login, Employee Name, Performance and attendance, Fixed Salary, Salary increment and HR
logout.
SEQUENCE DIAGRAM
The sequence diagram represents the sequence and interactions of a
given USE-CASE
CASE or scenario diagram can capture most of the information about the
system. Most object to object interactions and operations are considered events and
events include signals,
s, inputs, decisions, transitions and actions to or from users external
Devices.

Object:
Employee, HR, Training details and Salary details.
COLLABORATION DIAGRAM:
The sequence diagram and the collaboration diagram represents that the employee get
the training details. It contains objects and actors.

Object:
Training details and Object details
etails
STATE CHART DIAGRAM:
The State Chart Diagram for the sorfware Personnel Management Systems is given below

States: Login, Enter Employee Name ,Check performance and attendance,Provide increment,
Do not provide increment, and logout
DEPLOYMENT DIAGRAM:
The deployment diagrams are used to visualize the topology of the physical
components of a system where the software components are deployed.

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

RESULT:
Thus the minii project for the Software Personnel Management
agement System has
been successfully executed and codes are generated.
Ex no:8
CREDIT CARD PROCESSING

Date:3/11/2020

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:

Insecure –there is a possibility that a skilled hacker could break into the
database and steal an entire list of credit card numbers, thereby damaging the
merchant’s reputation with current client.

· There is a higher risk of customer charge backs with no signature

· Higher risk of fraud for using stolen credit cards

· Many discerning online shoppers will not give their credit card to an
“untrusted” online merchant (you may want to consider being part of the Better
Business Bureau or similar organization to add credibility).

So there is a need of online and trusted credit card processing.

( II )SOFTWARE REQUIREMENTSPECIFICATION:
1.0INTRODUCTION

A credit cardis 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 theuser 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.
1.1PURPOSE
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.

1.2SCOPE

 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

1.3DEFINITIONS, 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.

1.4 REFERENCES
IEEE Software Requirement Specification format.

1.5TECHNOLOGIES TO BEUSED
 HTML

 JSP

 Javascript

 Java

1.6 TOOLS TO BE USED

 Eclipse IDE (Integrated Development Environment)

 Rational Rose tool (for developing UML Patterns)

1.7OVERVIEW
SRS includes two sections overall description and specific requirements –

Overall Description will describe major role of the system components and inter-

connections.

Specific Requirement swill describe roles & functions of the actors.

2.0 OVERALL DESCRIPTION
2.1 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.

2.2SOFTWARE 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 -Glass fish application server(SQL Corporation).

 Back End -SQL database.

2.3HARDWARE INTERFACE

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

2.4SYSTEM FUNCTIONS

1.Accept credit card numbers on the web, store them in a database, then process
them off-line

2.Credit card processing with CCP

3.Credit card processing with a third-party credit card processing company

2.5USER CHARACTERISTICS
1)User/Customer-They are the people who desires to purchase the goods using
credit card.

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

2.6 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

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

( III )USECASE DIAGRAM:
The Passport Automation system use cases are:

Creating Account: Used to create a account.

Credit card request: Used to send the request to credit card.

Bank Enquiry: Used to get the bank enquiry like pin code to verify your user
account.

Issuing card: Used to issuing the card to machine.

Purchase the item: Used to list out the purchase details in shop.

Prepare the bill: Used to issuing the bill for the purchased item.

Paying bill: Used to transaction of money to paying the bill.

ACTORS INVOLVED

Customer/user:The person who order for the item.

Banker: The person to check the account details.

Retailer: The person to preparing the bills.

USE-CASE NAME: PURCHASE PRODUCT

Customer purchases items from ecommerce site then proceeds to the site’s
secure checkout area.

USE-CASE NAME: AUTHORIZATION REQUEST

Credit card processor collects billing information from the customer via a
secure connection.
USE-CASE NAME: AUTHORIZATION RESPONSE

Billing information is verified and the transaction is completed by the credit

card issuer.

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

USECASE DIAGRAM FOR CREDIT CARD PROCESSING

SYSTEM:

(IV) 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 Credit Card Processing system class diagram consists of threeclasses.

They are

1.Banker

2.Customer

3.Retailer

CLASS DIAGRAM:
(V) 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.
SEQUENCEDIAGRAM:
COLLABORATION DIAGRAM:

(VI)State chart 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.
STATE CHART DIAGRAM:
(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.

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

COMPONENT DIAGRAM:

RESULT
Thus the mini project for credit card processingsystem has been successfully
executed and codes are generated.
Ex no:9
E-BOOK MANAGEMENT SYSTEM
Date:03/11/20

AIM:
To create an automated system to perform the E-Book Process.
HARDWARE REQUIREMENTS:
• Intel Pentium Processor 3
SOFTWARE REQUIREMENTS:
• ArgoUML/Rational rose / Visual Basic
PROBLEM STATEMENT:
E-Book Management System software is designed to manage the books that
were read through the internet.This consists of the details of the e-book that were
read by the user online.It will be controlled by the central system.thsi system act as
a backup of all details together.
SOFTWARE REQUIREMENT SPECIFICATION:
SOFTWARE INTERFACE:
• Front End Client - The applicant and Administrator online
interface is built usingJSP 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 clientsystems
have access to the database in the server.
USE CASE DIAGRAM:
This diagram will contain the actors, use cases which are given below

Actors:Registered user,vistor,Administrator.

Use case:register,login,search book,download,payment,publisher,update

CLASS DIAGRAM:
This diagram consists of the following classes, attributes and their
operations.
 Company
Userinfo person companyName : string
Product
username : string firstname : string companyAddress : string
userid : string lastname : string employeeList : list productid : string name :
1..*
password : string 1 1 emailaddress : string ebookCollection : list string price : double
contactNo : string 0..1
userinfo : UserInfo addProduct()
accountinfo : Accountinfo
suggestionGiven : List addEmployee() Operation1()
ChangePassword() findProduct()
suggestionAccepted : List Operation2()
followerList : List removeProduct() Operation3()
followingList : List removeEmployee() Operation4()
1

getFollowers() getEBookCollection() 1..*

getFollowing() 0..1
1 addFollower()
addFollowing() 0..1
AccountInfo
removerFolliower()
ebook : createdOn : Date removerFollowing() 0..1
lastModifiedOn : Date Suggestion EBook
1..* 0..1
billingInfo : BillingInfo
EBook suggestionFrom : filename : string title : string
purchasedEBooks : List
person suggestionTo : rating : int
person createdOn : date
message : string accepted :
bool

1
Operation1()
Operation2()
1 Operation3()
Operation4()
Billinginfo
billingAddress : string
shippingAddress : string
creditcardinfo : Creditcard

editBillingAddress()
editShippinAddress()

CLASSES ATTRIBUTES OPERATIONS

userinfo Username Changepassword()
Userid
Password
accountinfo
person Firstname Getfollower()
Lastname Getfollowing()
Emailaddress Addfollower()
Contact no Addfollowing()
Userinfo Removefollower()
Suggestiongiven Removefollowing()
 Suggestionaccepted
Followerlist
Following list
company Companyname Addproduct()
Companyaddress Addemployee()
Employeelist Findproduct()
ebookcollection Removeproduct()
Removeemployee()
Geteebookcollection()
product Productid Operation 1()
Name Operation 2()
price Operation 3()
Operation 4()
Account info Created on -
Lasrmodifiedon
Billinginfo
Purchaseebook
suggestion Ebook Operation 1()
Suggestionfrom Operation 2()
Suggestion to Operation 3()
Createdon Operation 4()
Message
accepted
Billing info Shippingaddress editbillingaddress()
 Billingaddress editshippingaddress()
Creditcardinfo
ebook File name -
Title
rating

ACTIVITY DIAGRAM:

This diagram will have the activities as start point,end point,decision

boxes.

LOGIN

WELCOME PAGE

SEARCH BOOK
ONLINE READING

DOWNLOAD

PAYMENT
Activities:Login,welcome page,search book,online reading,download,payment
SEQUENCE DIAGRAM:
The sequence diagram for each USE-CASE that exists when a about E-Book
Management system are given.This diagram consists of the objects, messages and
return messages.
Registrated User:

Object: ui,book,download
Vistor:
Object: book
COLLABORATION DIAGRAM:

This diagram contains the objects and actors.

Registrated user:
 1:seek login

/UI
/register user

login agreed

request download book payment

transaction submitted

search book

7:display payment
downloading

4:check availability of book

/DownIoad

Object: register user,ui,download

Vistor:
Object: visitor,book
STATE CHART DIAGRAM:
The state chart diagram of E-book Management system that the service of
Books like searching and downloading is available to the users .

States: Login State,view book,search book,downloads,Payment,

DEPLOYMENT DIAGRAM:

In the deployment diagram the object reference in component diagram is also

included the deployment diagram. In this authority and database server and web
server interact to the user.
COMPONENT DIAGRAM:
• Here the three components are datadase server,web server,client machine
 • The interface between people and database sever and client machine is web
server.
DB

RESULT:
 Thus the mini project for E-book Managaement System has been
successfully executed and codes are generated.
Ex.No: 10 RECRUITMENT SYSTEM
Date:

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

(I)PROBLEM STATEMENT:
The recruitment system allows the job seekers to enroll their names
through the process of registration. The employee also can get the list of
available candidates and shortlist for their company requirement. Once the
applicant enrolls he receives an id, which helps him in further
Correspondence. A fees amount is received from the job seekers for
enrollment. This system makes the task of the job seeker easier rather than
waiting in queue for enrollment. This also reduces the time consumption for
both for the job seeker and employee.

(II)SOFTWARE REQUIREMENT SPECIFICATION:

2.1 PRODUCT PERSPECTIVE

The PAS acts as an interface between the 'applicant' 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 recruitment.
2.2SOFTWARE 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.
2.3HARDWARE 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 Recruitment Automation system use cases are:

Fig.3. UML USE CASE DIAGRAM

(IV)ACTIVITY DIAGRAM:

Fig.4. ACTIVITY DIAGRAM

(V)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.
 Fig.5. UML CLASS DIAGRAM

(VI)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 specialized diagram.
Fig. 6.1SEQEUENCE DIAGRAM FOR Register:
 Fig.6.2. SEQUENCE DIAGRAM FOR STATUS

Fig.6.3. SEQUENCE DIAGRAM FOR Admin

(VII) 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.7.1COLLABRATION DIAGRAM For Register
 Fig.7.2. COLLABORATION DIAGRAM FOR Status

Fig.7.3.COLLABORATION DIAGRAM FOR Admin

(VIII) PARTIAL LAYERD LOGICAL ARCHITECTURE DIAGRAM:
UI

Swing Text

Recruitment Recruitment
system Form

Domain

Candidate Admin panel

Submit Cancel send delete

Status

Get status

Technical Services
 Persistence

DBFacade SOAP Log4J

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

<<databas <<client
e>> workstati
:MySQL on>>:Gen
ericPC
SQ H
L TT
<<server>
> :Tomca
t6
Fig.9.1.DEPLOYMENT DIAGRAM

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

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

Ex.No :12 FOREIGN TRADING SYSTEM

Date :

AIM
To design a project Foreign Trading System using Rational Rose
Software and to implement the software in Visual Basic

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

(II)SOFTWARE REQUIREMENT SPECIFICATION

ADMINISTRATOR One who coordinates the entire trading

process.
DATABASE All the transaction details are stored
here.
READER Person who is viewing the website. USER The traders and the
viewers are the
users.
SOFTWARE REQUIREMENT This software specification documents
SPECIFICATION full set of features and function for
foreign trading system.

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.

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

(III)USE CASE DIAGRAM

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

1. Vertical dimension-represents time.

2. Horizontal dimension-represent different object

TraderTraderAdministratorAdministratorDatabaseDatabaseLoginSourcingPl
ace orderUpdateorderPay update account details bill logout

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.
DOCUMENTATION OF COLLABORATION DIAGRAM
The collaboration diagram shows how the trader performs the sourcing and
places order for which the administrator provides the bill and updates it in the
database.

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

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 the
second state.

• The trader places the order in the third state.

• The trader receives the bill in the fourth state and pay the required amount
in fifth state.
• The trader logouts from the system in the sixth state

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

• The trader pays for the bill and logout from the system.

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.

DOCUMENTATION OF COMPONENT DIAGRAM

The main component in the component diagram is foreign trading system. The
trader who come to do the trading process and administrator who manages all
the other processes is the sub components.

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.
DOCUMENTATION OF DEPLOYMENT DIAGRAM
The processor in this diagram is the foreign trading system. The devices are
the trader and administrator who perform the main activities in the system.

PACKAGE DIAGRAM
A package diagram in the unified modeling language depicts the dependencies
between the packages that make up a model. It provides a way to 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 tracing order and
providing the bill. Technical services layer
General purpose objects and subsystems that provide supporting technical
services, such as interfacing with a database or error logging.These services
are usually application-independent.

DOCUMENTATION OF PACKAGE DIAGRAM

The three layers in the foreign trading system are

• User interface layer – consists of web and login. This layer describes
how the trader logins to the website and trades for the commodities.

• Domain layer – shows the activities that are performed inside the
trading system. The activities are place order, pay for the bill and logouts.

• Technical service layer – The sourcing and updating the details are
performed in this layer.

RESULT
Thus the mini project for foreign trading system has been successfully
executed and codes are generated.
Ex No. 11

FOREIGN TRADING SYSTEM

Date:
03/11/2020

AIM:

To develop foreign trading system project using Visual Basic

as front end and Microsoft as Access as back end.

HARDWARE REQUIREMENT:
● Intel Pentium Processor 3.

SOFTWARE REQUIREMENTS:
● ArgoUML/Rational rose/Visual Basic.
PROBLEM STATEMENT:
Foreign Trading systems allows customer to buy goods or forum from
other countries. The customer can see the list of available items and can
by according to their requirements. He can register those items through
the register number given. Finally, the payment is done through online.
This system makes the task of customer easier and reduces time
consumption.
SOFTWARE REQUIREMENT
SPECIFICATION: SOFTWARE
INTERFACE:
● Front End Client - The applicant and Administrator online
interface is built using JSP and HTML. The Administrator’s local
interface is built using JAVA.
● Web Server - Glassfish application server (Oracle Corporation).
● Back End - Oracle Corporation.
HARDWARE INTERFACE:
The server is directly connected to the client system. The client
systems have access to the database in the server.

USE CASE DIAGRAM:

This diagram will contain the actors, use cases which are given
below
 Actors: Buyer,Seller.
Use case: Register,login,forum,Payment.
CLASS DIAGRAM:
This diagram consists of the following classes, attributes and
their operations.

CLASSES ATTRIBUT OPERATIONS

ES
Foreign Trading - -
system
Register cust_name, city, register()
address,
phone_num,
designation
login register_num, pswd, login()
email
Forum item_id, item, price, forum()
quantity, item_selected
Payment cus_name, bank_name, payment()
pin_num, address,
trans_id, amount, ack
ACTIVITY DIAGRAM:
This diagram will have the activities as Start point, End point,
Decision boxes.
Registration:

Activities: foreign trading system, register, enter necessary

item, valid, invalid details, registration accepted.
 Login:

Activities: Foreign Trading system, login, enter reigster

num and password, valid pswd, invalid pswd, return forum.
 Forum:

Activities: Foreign Trading system, forum, select items,

select quantity, add and delete items, checks availability, confirmation
of order.
 Payment:

Activities: Foreign trading system, get document that contains

item and price, verify, invalid item, enter transaction Id and amt,
deliver item after transaction, ack from buyer to seller.
SEQUENCE DIAGRAM:
This diagram consists of the objects, messages and return messages.
REGISTERATION:

Object: buyer,seller.
LOGIN:

Object: buyer, seller.

FORUM:

Object: buyer, seller, database.

 PAYMENT:

Object: buyer, seller, database.

COLLABORATION DIAGRAM:
This diagram contains the objects and actors.
REGISTRATION:
 Object: buyer, seller.

LOGIN:

Object: buyer, seller.

FORUM:

Object:buyer, seller, database.

Payment:

Object: buyer, seller, database.

STATE CHART DIAGRAM:

 The state chart diagram of Foreign Trading system is
given below

REGISTRATION:

States: Registration, Enter details, Registration successful,

Reenter
details.

LOGIN:
 States: Login, Enter reg_no and pwd, login successful, Make
registration.

FORUM:

States: Select needed items, checking, add to database, no

stock.
 PAYMENT:

States: E_pay, Enter regno and pwd, Retrive payment wnd, Enter
trans_id and amt, Payment successful, Reenter reg_no and pwd.

COMPONENT DIAGRAM:
● Here the five components are Registration, Login, Forum,
Payment and Database.

DEPLOYMENT DIAGRAM:
 The deployment diagram for Foreign Trading system is
given below

RESULT:
Thus the mini project for Foreign Trading system has been
successfully executed and codes are generated.
EXNO :12 CONFERENCE MANAGEMENT SYSTEM

AIM:

To implement a software for conference management system​.

HARDWARE REQUIREMENTS:

​Intel Pentium processor 3​.

SOFTWARE REQUIREMENTS:

​ArgoUML/visual basic/rational rose.

PROBLEM STATEMENT:

​The Conference Management System is an online website in which

candidate can submit the paper and register themselves and then attend the

conference. The paper will be reviewed. The details of the conference, date

and time will be made available to them through the website. After getting the

confirmation details the candidate should submit the revised and camera

ready paper. Then the registration process will be done.

SOFTWARE INTERFACE

Front End Client - The exporter online interface is built using JSP and
HTML.

Web Server – Apache Tomcat Server (Oracle Corporation)

Back End - Oracle 11g 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 serve

EXNO :12 CONFERENCE MANAGEMENT SYSTEM

USECASE DIAGRAM:

This diagram will contain the actors, use case which are given below

ACTORS:

1.Candidate

2. Reviewer

USE CASE

1.Paper submission

2.Review the paper

EXNO :12 CONFERENCE MANAGEMENT SYSTEM

3.Send conformation details

4.Send revised paper

5.Registration

CLASS DIAGRAM

The class diagram is a graphical representation of all the classes

uses in the system and their operations ,attributes and relationships

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

EXNO :12 CONFERENCE MANAGEMENT SYSTEM

ACTIVITY DIAGRAM

​This diagram will have the activites as start point,end point, decision

boxes shown below

EXNO :12 CONFERENCE MANAGEMENT SYSTEM

SEQUENCE DIAGRAM:

A ​sequence diagram illustrates a kind of format in which each object interacts

via message. It is generalize between two or more specialized diagram.

EXNO :12 CONFERENCE MANAGEMENT SYSTEM

COLLABORATION DIAGRAM

​This diagram contains the objects and actors.

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.

EXNO :12 CONFERENCE MANAGEMENT SYSTEM

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.

.
EXNO :12 CONFERENCE MANAGEMENT SYSTEM

CONCLUSION:

Thus the mini project for conference management system has been
successfully executed and codes are generated.
EX.NO:13
DATE:10/11/2020 BPO MANAGEMENT SYSTEM
AIM:
To implement a software for BPO management system
SOFTWARE REQUIREMENTS:
 StarUML
HARDWARE REQUIREMENTS:
 Intel Pentium Processor 3
PROBLEM STATEMENT:
With the reduction in communication costs and improved
bandwidths and 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 to different
operators for processing.
SOFTWARE INTERFACE:
 Front End Client - The exporter online interface is built using
JSP and HTML.
 Web Server – Apache Tomcat Server (Oracle Corporation)
 Back End - Oracle 11g database
HARDWARE INTERFACE
The BPO system’s server is directly connected to the client
systems via ftp. Theclient systems have access to the database in the
server.
USE CASE DIAGRAM:
Actors: BPO Organization, Client
UseCase: search, negotiate, upload, perform conversion, QC,
shipment, payment
CLASS DIAGRAM:
CLASSES ATTRIBUTES OPERATIONS
Org_name, Address1,Address2,
Address3,State,
BPO Org addOrg(), updateOrg()
Contact_no,Emailid,
Total_no_of_emp
Project_name, Project_id,
Project_desc, Project_duration,
Projects addProject(),
Project_st_date,
Details delProject(),
Project_ship_date,
Total_amount, Client_id, Status
Client_name, Client_id, Address,
addClient(), delCLient(),
Clients State, Pincode, Contact no,
updateClient()
Client_emailid
performQC(),
Process Project_id, Emp_id performConversion(),
downladip(),

Emp_name, Emp_id, addEmp(),

Employee EmpAddress, Emp_phoneno, delEmp(),
details Emp_emailid, Salary, Dept, updateEmp(),
Project_id, design salCal()
SEQUENCE DIAGRAM:
SEARCH FOR CLIENT
Object: BPO Organization, UI , Client

PROCESS
Object: BPO Organization, Process, Client
SETTLEMENT
Object: BPO Organization, Client
ACTIVITY DIAGRAM:
Activities: Search for job, negotiate process with client, upload input,
feedback and quit, perform conversion, BPO Perform QC, Perform rework,
Shipment, Client perform QC, Feedback, Amount estimation, Final amount
Decision box: Check whether the client is satisfied or not, Check for therror,
check whether the client detects or not.
COLLABORATION DIAGRAM:
SEARCH FOR CLIENT
Object: BPO Organization ,UI ,CLIENT

PROCESS
Object: Organization ,CLIENT , PROCESS
SETTLEMENT

Object: BPO Organization, Client

DEPLOYMENT DIAGRAM:

RESULT:
Thus the mini project for BPO management system has been
successfully executed and codes are generated.
EXP.NO:14 LIBRARY MANAGEMENT SYSTEM
DATE: 10/11/2020
AIM:
To design an object oriented model for Library Management System using
agrouml software.

PROBLEM STATEMENT:
The library management system is a software system that issues books and
magazines to registered students only. The student has to login after getting
registered to the system. The borrower of the book can perform various functions
such as searching for desired book, get the issued book and return the book.

CLASS DIAGRAM:
A class diagram in the unified modelling language is a type of static
structure diagram that describes the structure of a system by showing the system’s
classes, their attributes, operations and the relationships among objects. The library
management system makes use of the following classes user, librarian, system and
DBA.

1
CLASS ATTRIBUTES OPERATION
Library usertype,username, login(),register().logout()
managem listofbooks,passwo
ent rd
system
User name,id,newAttr verify(),checkaccount(),getbookinfo()
Book title,author,publicat showduedate(),reservestatus(),book_req(),renew_
ion info(),newOperation()
Librarian name,id,password verifylibrarian(),search()
Library Listofbooks add(),delete(),update(),display(),search()
database
staff name,dept -
student name,dept -
Account no_of_borrowed_b calc_fine()
ooks,no_of_reserve
d_books,no_of_los
t_books,no_of_retu
rned_books,fine

USE CASE DIAGRAM:

Use case is a list of actions or events. Steps typically defining
the interactions between a role and a system to achieve a goal. The use case
diagram consists of various functionality performed by actors like user, librarian,
system and DBA.
 librarian

User

DBA

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

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.
States-student/faculty login,search book,request book,receive book,return book
and pay fine(if any),sign out

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.
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.
ACTIVITY DIAGRAM :
Activity diagram are graphical representation of workflows of stepwise
activities and actions with support for choice, iteration and concurrency. Here in
the activity diagram the user login to the system and perform some main activity
which is the main key element to the system.

Activities-Enqiry about books,Check availability of book,Validate

member,Register member,Check number of books issued to member,Issue
book,Add member,Issue details,Update book status.
Decision box-
1.Check whether the book is available or not
2.Check whether the member is valid or not valid
3.Check whether maximum quote exceeded

RESULT:
Thus the various UML diagrams for library management system was drawn
successfully.
Ex.
No:15 STUDENTI
NFORMATI
ONSYSTEM
Dat
e:10.11.
2020

AI
M:
Todesi
gnanobj
ector
ient
edmodel
forSt
udenti
nfor
mat
ionsy
stem usi
ng 
Argo
uml
soft
ware.

HARDWAREREQUI REMENTS:
Int
elPent
ium Pr
ocessor3

SOFTWAREREQUIREMENTS:
Ar
gouml
/Rati
onal
Rose/Vi
sual
basi
c

PROBLEM STATEMENT:
Thest udentmustregi sterbyenteringthenameandpasswor dtologinthe f
orm.
Theadmi nselectt
hepar t
icularstudenttov iewthedetail
saboutt hat 
studentand
maintainingthestudentdetails.Thisprocessofst udent 
i
nformationsystem is
descri
bedsequent ial
lythr
oughf oll
owingst eps.Thestudentregi
stersthesy st
em.The
adminlogi ntothestudentinfor mati
on system.He/ shesearchforthelistofstudents.
Thensel ecttheparti
cul
ar student.Thenv iewt hedetai
lsofthatstudent.Aft
erdisplayi
ng
thestudent  
detai
l
st henl ogout
.

USECASEDI AGRAM:
Act
ors: St
udent,
Ser
ver
,St
aff
,DBA

Usecase:
Logi
n,
Displ
ay,
Ent
erpr
ofi
l
e,Ent
ermar
k,Vi
ewdet
ail
s,
Updat
edet
ail
,
All
owaccess,

Request
Access,
Stor
edat
a,Logout
.
CLASSDI
AGRAM:

Cl
ass At
tri
but
es Oper
ati
ons

St
udent Reg_
no l
ogi
n()

Name v
iew_
det
ail
()

l
ogout
()

St
aff Name l
ogi
n()

I
d ent
erpr
ofi
l
e()

ent
ermar
k()

l
ogout
()
Sy
stem Sy
stemno di
spl
ay(
)

Passwor
d r
equest
Access(
)

Ser
ver I
d al
l
owAccess(
)

Passwor
d di
spl
ay(
)

v
iewOper
ati
on(
)

DBA I
d st
oreDet
ail
()

Passwor
d updat
eDet
ail
()
ACTI
VITYDI
AGRAM:
SEQUENCEDI
AGRAM:
COLLABORATI
ONDI
AGRAM:

STATECHARTDI
AGRAM:
DEPLOYMENTDI
AGRAM:

COMPONENTDI
AGRAM:
RESULT:
Thust
hevari
ousUMLdi agramsf
orst
udenti
nfor
mat
ion 
syst
em wer
edr
awnand
codewasgener
atedsuccessf
ull
y.