St.

PETER'S COLLEGE OF ENGINEERING AND TECHNOLOGY

AVADI , CHENNAI - 600054

DEPARTMENT OF COMPUTER SCIENCE ENGINEERING

CS8582 - OBJECT ORIENTED ANALYSIS AND DESIGN LABORATORY

RECORD

NAME :

REG.NO :

BRANCH :

YEAR/SEM :

2022-2023

i
 St. PETER'S COLLEGE OF ENGINEERING AND TECHNOLOGY
AVADI , CHENNAI - 600 054.

DEPARTMENT OF COMPUTER SCIENCE ENGINEERING

Bonafide Certificate

NAME…………………………………………………………………..…………………..
YEAR………………………………….SEMESTER…………..…………………………
BRANCH……………………..…………............................................................................
REGISTER NO. ………………………….……………………………………………….

Certified that this bonafide record of work done by the above student of the CS8582-OBJECT
ORIENTED ANALYSIS AND DESIGN LABORATORY during the year 2021 – 2022.

Faculty-in-Charge Head of the Department

Submitted for the practical Examination held on ………………. at St. PETER'S COLLEGE OF

ENGINEERING AND TECHNOLOGY

Internal Examiner External Examiner

 INDEX

E.NO EXPERIMENT NAME Pg. No.

1 Study of UML 1-5

2 Passport Automation System. 6-13

3 Book Bank Management System. 14-19

4 Exam Registration System. 20-26

5 Stock Maintenance System. 27-34

6 Online Course Reservation System 35-45

7 E-Ticketing. 46-51

8 Software Personnel Management System. 52-58

9 Credit Card Processing System. 59-64

10 E-Book Management System. 65-70

11 Online Recruitment System 71-78

12 Foreign Trading System 79-84

13 Conference management System 85-93

14 BPO Management System 94-103

15 Library Management System 104

EX.NO:1
DATE: STUDY OF UML

UML NOTATION
• Set of notations and conventions used to describe and model an application.
• Universal language for modeling systems.
• Standard notation for OO modeling systems.
• Does not specify methodology to develop an application.

UML DIAGRAMS

Class Diagram
Use Case Diagram
Behavioral Diagram
Interaction Diagram
• Sequence Diagram
• Collaboration Diagram
State Chart Diagram
Activity Diagram
Implementation Diagram
• Component Diagram
• Deployment Diagram

CLASS DIAGRAM

• Shows the static structure of the model.

• Collection of static modeling elements such as classes and their relationships connected as
a graph.
• Provides visual representation of objects, relationships and their structures.

Class:-
• A class is a set of objects that share a common structure and common behavior.
• It is represented as:

<Class>
<Attribute>
<Operations>
Interface:-
• Specifies the externally-visible operations of a class and/or component.

1
Association: -
• Model properties of associations.
• The properties are stored in a class and linked to the association relationship.
• Example
BANK
ACCOUNT PERSON

Generalization: -
• A generalize relationship is a relationship between a more general class or use case and a
more specific class or use case.
• Example,

TRUCK

USE CASE DIAGRAM

• Set of use cases enclosed by system boundary, communication association between actors
and use cases, and generalization among use cases.

Actors:-
• External factors that interacts with the system from the user's perspective.

Use Cases:-
• Set of scenarios that describe how actor uses the system.
• Represented as,

Relationship:-
• Communication – communications with the use case normally.
• Uses – Shown by generalization arrow from the use cases.
• Extends – Used when one case does more than another that is similar to it.

BEHAVIOR DIAGRAM

INTERACTION DIAGRAM

• Diagrams that describes how group of objects are collaborated.

2
 SEQUENCE DIAGRAM

• Describes the behavior of the system through interaction between the system and the
environment in time sequence.
• Two dimensions:
Vertical dimension – represents time.
Horizontal dimension – represents objects.
• Life line – Object's existence during the interaction
Relationship:-
• Communication – communications with the use case normally.
• Uses – Shown by generalization arrow from the use cases.
• Extends – Used when one case does more than another that is similar to it.

COLLABORATION DIAGRAM

An interaction diagram that shows the order of messages that implement an operation or a transaction.

• Collaboration diagrams show objects, their links, and their messages

Object :-
• An object has state, behavior and identity
• Objects interact through their links to other objects.
Link:-

• A link is an instance of an association, analogous to an object.

Message:-
• A message is the communication carried between two objects that trigger an event.

3
STATECHART DIAGRAM

• Models the dynamic behavior of individual classes or any other kind of object.
• Shows the sequences of states, events, and actions.

State:-
• Represents a condition or situation during the life of an object during which it satisfies
some condition or waits for some event.

<State>
Start State:-
• Shows the beginning of workflow.

End state:-
• Represents the final or terminal state.

ACTIVITY DIAGRAM

Used for modeling the sequence of activities in a process.

• Special case of a state machine in which most of the states are activities and most of the
transitions are implicitly triggered by completion of the actions in the source activities.

Activity:-
• Represents the performance of task or duty in a workflow.
<Activity>
Swim lanes:-
• Represents organizational units or roles within a business model.

IMPLEMENTATION DIAGRAM

• Shows the implementation phase of system development.

• Two types of implementation diagrams:
Component diagram
Deployment diagram

4
 COMPONENT DIAGRAM

• Models the physical components in the design.

• A graph of the design’s components connected by dependency relationships.
• Includes concept of packages.
• Package is used to show hoe classes are grouped together.

DEPLOYMENT DIAGRAM

• Shows the configuration of runtime processing elements and software components.

• It is a graph of nodes connected by communication association.
• Nodes are the components that are connected to other components through dependencies.
• Used in conjunction with component diagrams to show the distribution of physical modules

RESULT:

Thus the UML program as been created and verified successfully

5
EX. NO.:2
DATE:
PASSPORT AUTOMATION SYSTEM

AIM:
To create uml diagram for passport automation system and run the program

REQUIREMENTS:
SYSTEM REQUIREMENTS:
Processor: Pentium Core 2 Duo
RAM: 2 GB
Hard Disk: 40 GB

SOFTWARE REQUIREMENTS:
ArgoUML

PROBLEM ANALYSIS AND PROJECT PLAN:

To simplify the process of applying passport, software has been created by designing
through Argo UML tool. Initially the applicant login the passport automation system and
submits his details. These details are stored in the database and verification process done by
the passport administrator, regional administrator and police the passport is issued to the
applicant.
PROBLEM STATEMENT:
1. Passport Automation System is used in the effective dispatch of passport to all of the
applicants. This system adopts a comprehensive approach to minimize the manual work and
schedule resources, time in a cogent manner.
2. The core of the system is to get the online registration form (with details such as name,
address etc.,) filled by the applicant whose testament is verified for its genuineness by the
Passport Automation System with respect to the already existing information in the database.
3. This forms the first and foremost step in the processing of passport application. After the
first round of verification done by the system, the information is in turn forwarded to the
regional administrator's (Ministry of External Affairs) office.
4. The application is then processed manually based on the report given by the system, and
any forfeiting identified can make the applicant liable to penalty as per the law.
5. The system forwards the necessary details to the police for its separate verification whose
report is then presented to the administrator. After all the necessary criteria have been met,
the original information is added to the database and the passport is sent to the applicant.

6
 UML DIAGRAMS

USE CASE DIAGRAM:

CLASS DIAGRAM:

7
SEQUENCE DIAGRAM:

COLLABORATION DIAGRAM:

8
STATECHART DIAGRAM:

ACTIVITY DIAGRAM:

9
COMPONENT DIAGRAM:

DEPLOYMENT DIAGRAM:

10
OUTPUT:
SOURCE CODE:
applicant.java:
import java.util.Vector;

public class applicant {

public String name;

public String father_name; public

Integer date_of_birth; public

String parmanent_address; public

String temporary_address; public

String email_id;

public Integer phone_number;

public Integer pan_number;

public String applicant_number;

public String user_name;

public String password;

public Vector mydatabase;

public void login() {

}

public void submit_details() {

}

public void check_status() {

}

11
Database.java:

import java.util.Vector;

public class database {

public String name;

public Vector mypassport administrator;

public Vector myregional dministration;
public Vector mypolice;

public void store() {

}

Password administrator.java:
public class passport administrator {

public String user_name;

public String password;

public void login() {

}

public void verify() {

}

public void update() {

}

Police.java:

public class police {

public String user_name;

public String password;

public void login() {

}

12
 public void verify() {
}

public void update() {

}

Regional administrator.java:

public class regional dministration {

public String user_name;

public String password;

public void login() {

}

public void verify() {

}

public void update() {

}

RESULT:

Thus UML diagram for passport automation system as been created and output is verified successfully

13
EX. NO:3
DATE:
BOOK BANK MANAGEMENT SYSTEM

AIM:
To create UML diagram for book bank management system and run the program

REQUIREMENTS:
SYSTEM REQUIREMENTS:
Processor: Pentium Core 2 Duo
RAM: 2 GB
Hard Disk: 40 GB

SOFTWARE REQUIREMENTS:
ArgoUML

PROBLEM ANALYSIS AND PROJECT DESIGN:

The book bank management system is an application in which a member can register
themselves and then he can borrow books from the book bank. It mainly concentrates on
providing books for engineering students.

PROBLEM STATEMENT

The process of members registering and purchasing books from the book bank are
described sequentially through following steps:
a. First the member registers himself if he was new to the book bank.
b. Old members will directly select old member button.
c. They select their corresponding year.
d. After selecting the year they fill the necessary details and select the book and he will be
directed towards administrator
e. The administrator will verify the status and issue the book.

14
 UML DIAGRAMS

USE CASE DIAGRAM:

CLASS DIAGRAM:

15
SEQUENCE DIAGRAM:

COLLABORATION DIAGRAM:

16
STATECHART DIAGRAM:

ACTIVITY DIAGRAM:

17
COMPONENT DIAGRAM:

DEPLOYMENT DIAGRAM:

18
OUTPUT:
SOURCE CODE:
Book bank.java:
public class book bank {

public String name;

public String address;

public void checking() {

}

public void issueing() {

}

public void store() {

}

}
Student.java:
import java.util.Vector;

public class student {

public String name;

public String coll_name;

public String address;

public String department;

public Integer year;

public Vector mybook bank;

public void register() {

}

public void submit_book_information() {

}

public void collect_book() {

}
}

RESULT:
Thus UML diagram for book bank management system as been created and executed successfully

19
EX.NO:4
DATE:
EXAM REGISTRATION SYSTEM
AIM:

To create UML diagram for exam registration system and to run the program

REQUIREMENTS:
SYSTEM REQUIREMENTS:
Processor: Pentium Core 2 Duo
RAM: 2 GB
Hard Disk: 40 GB

SOFTWARE REQUIREMENTS:
ArgoUML

PROBLEM ANALYSIS AND PROJECT PLANNING:

The Exam Registration is an application in which applicant can register themselves

for the exam. The details of the students who have registered for the examination will be
stored in a database and will be maintained. The registered details can then be verified for any
fraudulent or duplication and can be removed if found so. The database which is verified can
be used to issue hall tickets and other necessary materials to the eligible students.

PROBLEM STATEMENT:

The process of students accessing the registration application and applying for the
examination by filling out the form with proper details and then the authorities verify those
details given for truth and correctness are sequenced through steps
a. The students access exam registration application.
b. They fill out the form with correct and eligible details.
c. They complete the payment process.
d. The authorities verify or check the details.
e. After all verification the exam registration database is finalized.

20
 UML DIAGRAMS
USECASE DIAGRAM:

CLASS DIAGRAM:

21
SEQUENCE DIAGRAM:

COLLABORATION DIAGRAM:

22
STATE DIAGRAM:

ACTIVITY DIAGRAM:

23
COMPONENT DIAGRAM:

DEPLOYMENT DIAGRAM:

24
OUTPUT:
SOURCE CODE:
Registration website.java:
import java.util.Vector;

public class registration website {

public String qualification;

public String login_details;

public Integer fee_details;

public Integer exam_dates;

public Vector myuniversity database;

public void verification() {

}

public void processing() {

}

public void registration() {

}

Student.java:
import java.util.Vector;

public class student {

public String name;

public String address;

public Integer DOB;

public String subjects;

public String college;

public Vector myregistration website;

public void form_filling() {

}

public void registration() {

25
 }

University database.java:
import java.util.Vector;

public class student {

public String name;

public String address;

public Integer DOB;

public String subjects;

public String college;

public Vector myregistration website;

public void form_filling() {

}

public void registration() {

}

RESULT:

Thus UML diagram for exam registration system as been created and executed successfully

26
EX.NO:5
DATE:
STOCK MAINTENANCE SYSTEM
AIM:
To create UML diagram for stock maintenance system and run the program

REQUIREMENTS:
SYSTEM REQUIREMENTS:
Processor: Pentium Core 2 Duo
RAM: 2 GB
Hard Disk: 40 GB

SOFTWARE REQUIREMENT:
ArgoUML

PROJECT ANALYSIS AND PLANNING:

The Stock Maintenance System, initial requirement to develop the project about the
mechanism of the Stock Maintenance System is caught from the customer. The requirement
are analyzed and refined which enables the end users to efficiently use Stock Maintenance
System. The complete project is developed after the whole project analysis explaining about
the scope and the project statement is prepared.

PROBLEM STATEMENT:
The stock has to be maintained properly since the whole marketing process can be improved.
a. The store keeper checks the stock.
b. Gives order to the supplier.
c. Supplier supplies the goods.
d. Store keeper checks the goods.
e. Database provides user id and pass.
f. Store keeper updates the stock and stores it in database.
g. Pay money to the Supplier.

27
 UML DIAGRAMS
USECASE DIAGRAM:

CLASS DIAGRAM:

28
SEQUENCE DIAGRAM:

COLLABORATION DIAGRAM:

29
STATECHART DIAGRAM;

ACTIVITY DIAGRAM:

30
COMPONENT DIAGRAM:

DEPLOYMENT DIAGRAM:

31
OUTPUT:
SOURCE CODE:
Agent.java:
import java.util.Vector;

public class agent {

public Integer purchase;

public Vector myorder;

public Vector mysystem;
public Vector mysystem;

public void request() {

}

public void bill() {

}

}
Credit card.java:
public class credit card {

public Integer number;

public String name;

public Integer validity;

public void number() {

}

public void name() {

}

public void validity() {

}

}
Cash.java:
public class cash {

public Integer amount;

public void amt() {

}

32
}

Item.java:
import java.util.Vector;

public class item {

public Integer expiry_date;

public Integer quantity;

public Integer price;

public Vector mysystem;

public void expiry_date() {

}

public void quantity() {

}

public void price() {

}

Order.java:
import java.util.Vector;

public class order {

public Integer item;

public Integer price;

public Vector mytotal profit;

public Vector myitem;

public void purchase() {

}

public void discount() {

}

public void product_count() {

}

33
System.java:
import java.util.Vector;

public class system {

public String associativity;

public Integer expiry_date;

public Vector myorder;

public void associativity() {

}

public void expiry_date() {

}

Total profit.java:
import java.util.Vector;

public class total profit {

public Integer amount;

public Integer double;

public Vector mycredit card;

public Vector mycash;

public void amt() {

}

RESULT:

Thus UML diagram for stock maintenance system as been created and executed successfully

34
EX. NO:6
DATE:
ONLINE COURSE RESERVATION SYSTEM

AIM:
To create UML diagram for online course reservation system and run the program

REQUIREMENTS:
SYSTEM REQUIREMENTS:
Processor: Pentium Core 2 Duo
RAM: 2 GB
Hard Disk: 40 GB

SOFTWARE REQUIREMENTS:
ArgoUML

PROJECT ANALYISIS AND PLANING:

The requirement form the customer is got and the requirements about the course
registration are defined. The requirements are analyzed and defined so that is enables the
student to efficiency select a course through registration system. The project scope is
identified and the problem statement is prepared.

PROBLEM STATEMENT:

a. Whenever the student comes to join the course he/she should be provided with the list of
course available in the college.
b. The system should maintain a list of professor who is teaching the course.
At the end of the course the student must be provided with the certificate for the completion
of the course.

35
 UML DIAGRAMS
USECASE DIAGRAM:

CLASS DIAGRAM:

36
SEQUENCE DIAGRAM:

37
38
COLLABORATION DIAGRAM:

39
40
STATECHART DIAGRAM:

ACTIVITY DIAGRAM:

41
COMPONENT DIAGRAM:

DEPLOYMENT DIAGRAM:

42
OUTPUT;
SOURCE CODE:
College.java:
public class college {

public Integer college_no.;

public String college_name;

public String course;

public void addmission() {

}

Student.java:
import java.util.Vector;

public class student1 {

public String name;

public Integer roll_no;

public Integer mark;

public Vector mycollege;

public void study() {

}

Course.java:
import java.util.Vector;

public class course {

public Integer mechanical;

public Integer EEE; public

Integer CSE;

public Vector mycollege;

public void newOperation() {

43
 }

cse.java:
import java.util.Vector;

public class CSE {

public Integer os_lab;

public Integer internet_lab;

public Integer casetool;

public Integer network;

public Vector mycourse;

public void terminate() {

}

}
eee.java:

import java.util.Vector;

public class EEE {

public Integer electronic_lab;

public Integer electrical_lab;

public Integer control_system;

public Vector mycourse;

public void newOperation() {

}

Mechanical.java:
import java.util.Vector;

public class mechanical {

public Integer lathe;

44
 public Integer workshop;

public Vector mycourse;

public void production() {

}

RESULT:

Thus UML diagram for online course reservation system as been created and executed
successfully

45
EX. NO: 7
DATE:

E-TICKETING
AIM:

to create UML diagram for E-ticketing and run the program

REQUIREMENTS:
SYSTEM REQUIREMENTS:
Processor: Pentium Core 2 Duo
RAM: 2 GB
Hard Disk: 40 GB

SOFTWARE REQUIREMENTS:
ArgoUML

PROBLEM ANALYSIS AND PROJECT PLANNING:

In the E-Ticketing system the main process is a applicant have to login the database
then the database verifies that particular username and password then the user must fill the
details about their personal details then selecting the flight and the database books the ticket
then send it to the applicant then searching the flight or else cancelling the process

PROBLEM STATEMENT:
The E-Ticketing system is the initial requirement to develop the project about the mechanism
of the E-ticketing system what the process do at all.
a. The requirement are analyzed and refined which enables the end users to efficiently use
the E-ticketing system.
b. The complete project is developed after the whole project analysis explaining about scope
and project statement is prepared.
c. The main scope for this project is the applicant should reserved for the flight ticket.
d. First the applicant wants to login to the database after that the person wants to fill their
details.
e. Then the database will search for ticket or else the person will cancelled the ticket if he/she
no need.

46
 UML DIAGRAMS
USECASE DIAGRAM:

CLASS DIAGRAM:

47
SEQUENCE DIAGRAM:

COLLABORATION DIAGRAM:

48
STATECHART DIAGRAM:

ACTIVITY DIAGRAM:

49
COMPONENT DIAGRAM:

DEPLOYMENT DIAGRAM:

OUTPUT:
SOURCE CODE:
appicant.java:
import java.util.Vector;
public class applicant {
public Integer npassport_code;

public string first_name;

public string lastname;
public string address;
public string nationality;
public Integer phone;
public string sex;

50
 public Integer passport_number;
public string resident_permit;
public Integer book_date; public
string destination;
public string depature;
public string flightname;
public Integer flightno;
public Vector myeticketing_database;
public void filling_details() {
}
public void selecthing_flight() {
}
public void book_ticket() {
}
public void cancel_ticket() {
}
}

e-ticketingdatabase.java
public class eticketing_database {
public string airlines;
public string hostel_res;
public void ticket_booking() {
}
public void hostel_booking() {
}
public void verifing_ticket() {
}
}

RESULT:

Thus UML diagram for e-ticketing as been created and executed successfully

51
 EX. NO:8
DATE:
SOFTWARE PERSONNEL MANAGEMENT SYSTEM

AIM:
To create UML diagram for software personnel management system and run the program

REQUIREMENTS:
SYSTEM REQUIREMENTS:
Processor: Pentium Core 2 Duo
RAM: 2 GB
Hard Disk: 40 GB

SOFTWARE REQUIREMENTS:
ArgoUML

PROJECT ANALYSIS AND PROJECT PLANNING:

The employee management system is used to manage our personnel things such as
maintaining databases in offices etc. This project is easy for the CEO to handle the details.
This is personally used for CEO.
PROBLEM STATEMENT:
The CEO must enter the name and password to login the form and select the particular
employee to view the details about that employee and maintaining the employee details
personally. This process of employee management system are described sequentially through
following steps,
• The CEO login to the employee management system.
• He/she search for the list of employees.
• Then select the particular employee.
• Then view the details of that employee.
• After displaying the employee details then logout.

52
 UML DIAGRAMS
USE CASE DIAGRAM:

CLASS DIAGRAM:

53
SEQUENCE DIAGRAM:

54
COLLABORATION DIAGRAM:

55
STATE CHART DIAGRAM:

ACTIVITY DIAGRAM:

56
COMPONENT DIAGRAM:

DEPLOYMENT DIAGRAM:

OUTPUT:
SOURCE CODE:
ceo.java:
import java.util.Vector;
public class ceo {
public string name;
public integer empno;

57
 public integer dob;
public Vector mydatabase;
public void view() {
}
public void update() {
}
public void login() {
}
}
database.java:
import java.util.Vector;
public class database {
public string products;
public string projects;
public Vector myemployee;
public void storedata() {
}
public void update() {
}
public void insert() {
}
public void enquiry() {
}
public void delete() {
}
public void verify() {
}
public void display() {
}
}
employee.java:
public class employee {
public string name;
public integer dob;
public integer salary;
public integer exp;
public integer phno;
}

RESULT:

Thus UML diagram for software personnel management system as been created and executed
successfully
58
EX. NO: 9
DATE:
CREDIT CARD PROCESSING SYSTEM
AIM:
To create UML diagram for credit card processing system and run the program

REQUIREMENTS:
SYSTEM REQUIREMENTS:
Processor: Pentium Core 2 Duo
RAM: 2 GB
Hard Disk: 40 GB

SOFTWARE REQUIREMENTS:
ArgoUML

PROBLEM ANALYSIS AND PROJECT PLANNING:

The Credit Card Processing System which is use to purchasing an item from any shop
mall, and it is used to maintain the limitation of credit card balance and current transaction
process could be update via credit card machine. This project mainly used for large amount
of item can be easy to buy from anywhere and required transaction process should be
maintained them.
PROBLEM STATEMENT: The customer should select the item to be purchase from the
shop by using credit card payment then the vendor should give a bill for the selected item .The
customer should give his card to swap and request for the kind of amount transaction. After
processing the transaction, the CREDIT CARD MACHINE should give the balance print
statement or receipt.
• Customer should select the item from the shop.
• Vendor makes the bill for the selected item.
• Customer gives the credit card to the vendor to swap the card.
• They required amount transaction is done by the card reader.
• Vendor will issue the balance statement to the customer.
• Customers put the signature in the receipt and return to the vendor.

59
 UML DIAGRAMS

USE CASE DIAGRAM:

CLASS DIAGRAM:

60
SEQUENCE DIAGRAM:

COLLABORATION DIAGRAM:

61
STATE CHART DIAGRAM:

ACTIVITY DIAGRAM:

62
COMPONENT DIAGRAM:

DEPLOYMENT DIAGRAM:

63
OUTPUT:
SOURCE CODE:
card reader.java:
public class card_reader {
public Integer machine_no;
public string software;
public string company_name;
public void make_transition() {
}
public void print_recipt() {
}
}
customer.java:
import java.util.Vector;
public class customer {
public string name;
public Integer age;
public string signature;
public Integer card_no;
public Vector myvendor;
public void purchase_item() {
}
public void swap() {
}
}
vendor.java:
import java.util.Vector;
public class vendor {
public string name;
public string address;
public Integer machine_no;
public Vector mycard_reader;
public void make_bill() {
}
public void delivery_item() {
}
public void purchase() {
}
}

RESULT:

Thus UML diagram for credit card processing system as been created and executed successfully

64
EX.NO:10
DATE:
E-BOOK MANAGEMENT SYSTEM
AIM:
To create a UML diagram for e-book management system and run the program

REQUIREMENTS:
SYSTEM REQUIREMENTS:
Processor: Pentium Core 2 Duo
RAM: 2 GB
Hard Disk: 40 GB

SOFTWARE REQUIREMENTS:
ArgoUML

PROBLEM ANALYSIS AND PROJECT PLANNING:

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

PROBLEM STATEMENT:

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

65
 UML DIAGRAMS
USE CASE DIAGRAM:

CLASS DIAGRAM:

66
SEQUENCE DIAGRAM:

COLLABORATION DIAGRAM:

67
STATECHART DIAGRAM

ACTIVITY DIAGRAM:

68
COMPONENT DIAGRAM:

DEPLOYMENT DIAGRAM:

69
OUTPUT:
SOURCE CODE:
books.java:
import java.util.Vector;
public class books {
public string computerarcitecture;
public string dbms;
public string webtechnology;
public string ooad;
public Integer newAttr;
public Vector mydatabase;
public void select() {
}
public void buy() {
}
}
customer.java:
import java.util.Vector;
public class customer {
public string name;
public string address;
public Integer no;
public Vector mydatabase;
public void login() {
}
public void payment() {
}
}
database.java:
public class database {
public string operation;
public void store() {
}
}

RESULT:

Thus UML diagram for e-book management system as been created and executed successfully

70
EX.NO:11
DATE:

ONLINE RECRUITMENT SYSTEM

AIM:
To create a UML diagram for online recruitment system and run the program

REQUIREMENTS:
SYSTEM REQUIREMENTS:
Processor: Pentium Core 2 Duo
RAM: 2 GB
Hard Disk: 40 GB

SOFTWARE REQUIREMENTS:
ArgoUML

PROBLEM ANALYSIS AND PROJECT PLANNING

The Online Recruitment System is an online website in which applicant can register
themselves and then attend the exam. Examination will be conducted at some venue. The
details of the examination, venue & Date of the examination will be made available to them
through the website. Based on the outcome of the exam the applicant will be short listed and
the best applicant is selected for the job.

PROBLEM STATEMENT:

The process of applicants is login to the recruitment system and register for the job through
online. The resume is processed by the company and the required applicant is called for the
test. On the basis of the test marks, they are called for next level of interview. Finally the
best applicant is selected for the job. This process of online recruitment system are
described sequentially through following steps,
• The applicant login to the online recruitment system.
• They register to the company for the job.
• They appear for examination.
• Based on the outcome of the exam, the best applicant is selected.
• The recruiter informs the applicant about their selection.

71
 UML DIAGRAMS

USE CASE DIAGRAM:

CLASS DIAGRAM:

72
SEQUENCE DIAGRAM:

73
COLLABORATION DIAGRAM:

74
STATE CHART DIAGRAM:

ACTIVITY DIAGRAM:

75
COMPONENT DIAGRAM:

DEPLOYMENT DIAGRAM:

76
OUTPUT:

SOURCE CODE:

applicant.java:
import java.util.Vector;

public class applicant {

public string username;

public strfing password;

private Integer phoneno;

public string address;

public string name;

public Vector mydatabase;

public void register() {

}

public void login() {

}

public void applicantdetails() {

}

database.java:

public class database {

public void aps_details() {

}

public void tech_details() {

}

public void selected_applicant_details() {

}

}
recruiter.java:
import java.util.Vector;

public class recruiter {

public string name;

77
 public string destination;

public Integer phoneno;

private Integer marksinaps;

public Integer marksintech;

public Vector mydatabase;

RESULT:
Thus UML diagram for online recruitment system as been created and executed
successfully

78
EX.NO:12
DATE: FOREIGN TRADING SYSTEM

AIM: To create a system to perform foreign trading system.

REQUIREMENTS:
SYSTEM REQUIREMENTS:
Processor: Pentium Core 2 Duo RAM: 2 GB
Hard Disk: 40 GB

SOFTWARE REQUIREMENTS:
ArgoUML

PROBLEM ANALYSIS AND PROJECT PLANNING:

• Individual and business firms intending to export and/or import goods and/or services
should obtain an Importer-Exporter Number from the regional licensing authorities

• Offer is a proposal submitted by an exporter expressing his intention to export specific

goods at a specific price with specific terms and conditions. Exporter usually makes an
offer in the form of a ‘Proforma Invoice’.

• The exporting house after obtaining a confirmed order should produce the goods exactly
as specified in the invoice. If the exporting house does not have facilities, it has to procure
the products from others.

• The exporter transports the goods to the buyer.

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

PROBLEM STATEMENT:

The main activity of international marketing is the export-import procedure. This

procedure involves the actual and operational procedure of export and import trade. It also involves
documentation, procedures, rules and regulations imposed by both the exporting and importing
countries. These procedures include excise clearance, foreign exchange, etc

79
 UML DIAGRAMS
USECASE DIAGRAM:

login

bill

sourcing

trader
administrator

place order

pay

update

logout

CLASS DIAGRAM:

SEQUENCE DIAGRAM:

80
 trader administrator item

login

sourcing

place_order

update_order

bill

pay

update_account_details

log_out

COLLABORATION DIAGRAM:
1: login
2: sourcing
3: place_order
6: pay
8: log_out
trader administrator

5: bill

4: update_order
7: update_account_details
item

81
ACTIVITY DIAGRAM:

login

sourcing

place order

bill

pay

log out

COMPONENT DIAGRAM:

Foreign Trading
system

Administrator
Trader

82
DEPLOYMENT DIAGRAM:

Foreign Trading
System

Trader Administrator

CODING:

Item.java
public class item

public string name;

public Integer id;

public Integer rate;

public Integer available;

public void getperfume()

{ }

public void getdolls() { }

Traders.java

import java.util.Vector;

public class traders

{
83
 public string username;

public string sourcing;

public integer account_no;

public Vector myadministrator_1;

public Vector myaccount;

public Vector myitem;

public void login() { }

public void sourcing() { }

public void place_order() { }

public void pay() { }

public void logout() { }

RESULT:
Thus UML diagram for foreign trading system as been created and executed successfully

84
EX NO: 13 CONFERENCE MANAGEMENT SYSTEM
DATE:

AIM: To implement a software for Conference management system

REQUIREMENTS:

SYSTEM REQUIREMENTS:
Processor: Pentium Core 2 Duo RAM: 2 GB
Hard Disk: 40 GB

SOFTWARE REQUIREMENTS:
ArgoUML

PROBLEM ANALYSIS AND PROJECT PLANNING:

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.

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.

85
 UML DIAGRAMS
USECASE DIAGRAM

paper Submission

Candidate review the paper Reviewer

send confirmation details

send revised paper

86
CLASS DIAGRAM

87
 ACTIVITY DIAGRAM

Submit
paper

Review
paper

Rejected
Selected
Reject
Send confirmation
paper
message

Send revised copy of

paper

Register

Send schedule

SEQUENCE DIAGRAM

88
 : registration
: Candidate : Reviewer

Regis

COLLABORATION DIAGRAM

2: review paper

COMPONENT DIAGRAM

89
DEPLOYMENT DIAGRAM

CODING
90
Registration.java

import java.util.Vector;
public class traders
{
public string username;

public string sourcing;

public integer account_no;

public Vector myadministrator_1;

public Vector myaccount;

public Vector myitem;

public void login() { }

public void sourcing() { }

public void place_order() { }

public void pay() { }

public void logout() { }

Reviewer.java
import java.util.Vector;
import String;
import Integer;
public class Reviewer {

public Integer reviewerId;

public String reviewerName;
public String status;
public Integer noofpaperreed;
public Vector myCandidateInfo;
public Vector myConferenceInfo;
public Vector myRegistration;

public void reviewPaper() { }

91
 public void sendConfirmMsg() { }
}

Conferenceinfo.java
import java.util.Vector;
import String;
import Integer;
public class ConferenceInfo
{
public String conferenceTitle;

public Date dateofConference;

public String conductingInsti;

public String address;

public String emailId;

public Integer contactNo;

public Vector myReviewer;

public void addConfInfo() { }

public void updateConf() { }

}
candidateInfo.java
import java.util.Vector;
import String;
import Integer;
public class CandidateInfo {

92
 public Integer candId;

public String canName;

public Integer age;

public String qualification;
public String institutionName;

public String gender;

public Integer phoneNo;

public String emailId;

public String paperTitle;

public Vector myReviewer;

public Vector myRegistration;

public void submitPaper() { }

public void sendCamReadyPaper() { }

public void register() { }

RESULT:
Thus UML diagram for conference management system as been created and executed successfully

93
EX NO: 14 BPO MANAGEMENT SYSTEM
DATE:

AIM: To implement a software for BPO management system

REQUIREMENTS:
SYSTEM REQUIREMENTS:
Processor: Pentium Core 2 Duo RAM: 2 GB
Hard Disk: 40 GB

SOFTWARE REQUIREMENTS:
ArgoUML

PROBLEM ANALYSIS AND PROJECT PLANNING:

PROBLEM STATEMENT:

The objective is to develop software for BPO management system. Business process outsourcing (BPO) is
a subset of outsourcing that involves the contracting of the operations and responsibilities of
specific business functions (or processes) to a third-party service provider. BPO management system
is used to effectively manage the business activities of a BPO organization. This system adopts
a comprehensive approach to minimize the manual work and schedule resources, time in a
cogent manner. It is designed for hiring any company, that is , it is generalized system for
business process management. The core of the system is to maintain employee details and
customer details and company details. Employee details include id, name, address, shift timings,
category (based on the field of expertise), number of calls attended and salary details.

94
 UML DIAGRAMS

USECASE DIAGRAM:

95
ACTIVITY DIAGRAM:

96
CLASS DIAGRAM:

97
SEQUENCE DIAGRAM

98
COLLABRATION DIAGRAM

COMPONENT DIAGRAM

99
DEPLOYMENT DIAGRAM

CODING :

BPO Organization.java
import java.util.Vector;

public class BPO Organization {

public String Org_name;

public String Address1;

public String Address2;

public String Address3;

public String State;

public Integer Contact_no;

public String Emailid;

public Integer Total_no_of_emp;

public Vector myProject Details;

public Vector myProcess;
public Vector myEmployee Details;

public void addOrg() {

}

public void updateOrg() {

}
100
}

Project Details.java
import java.util.Vector;

public class Project Details {

public String Project_name;

public Integer Project_id;

public String Project_description;

public String Project_duration;

public Date project_st_date;

public Date Project_ship_date;

public Double Total_amount;

public Integer Client_id;

public String Status;

public Vector myBPO Organization;

public Vector myClient;
public Vector myProcess;

public void addProject() {

}

public void delProject() {

}

public void updateProject() {

}

Client.java
import java.util.Vector;

public class Client {

public String Client_name;

public Integer Client_id;

public String Address;

101
 public String State;

public Integer Pincode;

public Integer Contactno;

public String Clientemailid;

public Vector myProject Details;

public Vector myProcess;

public void addClient() {

}

public void delClient() {

}

public void updateClient() {

}

Process.java
import java.util.Vector;

public class Process {

public Integer Project_id;

public Integer Emp_id;

public String Status;

public Vector myClient;

public Vector myProject Details;
public Vector myBPO Organization;
public Vector myEmployee Details;

public void performQC() {

}

public void performConversion() {

}

public void downloadip() {

}

public void shipment() {

}

public void cal_payment() {

}

102
}

Employee Details.java
import java.util.Vector;

public class Employee Details {

public Sg Emp_name;

public Integer Emp_id;

public String EmpAddress;

public Integer Emp_phoneno;

public String Emp_emailid;

public Double Salary;

public String Shift;

public Strring Dept;

public Integer Project_id;

public String design;

public Vector myBPO Organization;

public Vector myProcess;

public void addEmp() {

}

public void delemp() {

}

public void updateEmp() {

}

public void salCal() {

}

CONCLUSION:
Thus the mini project for BPO management system has been successfully executed and codes are generated.

103
EX NO: 15 LIBRARY MANAGEMENT SYSTEM
DATE:

AIM: To implement a software for library management system

REQUIREMENTS:

SYSTEM REQUIREMENTS:

Processor: Pentium Core 2 Duo

RAM: 2 GB
Hard Disk: 40 GB

SOFTWARE REQUIREMENTS:
ArgoUML

PROBLEM ANALYSIS AND PROJECT PLAN:

PROBLEM STATEMENT:
The steps involved in Library Management system are:
• Store student and book details.
• Ensure borrowing and returning books based on availability.
• Ensure access of journal and magazine

104
 UML DIAGRAM

USE CASE DIAGRAM

105
CLASS DIAGRAM

106
ACTIVITY DIAGRAM FOR BOOK ISSUE

107
ACTIVITY DIAGRAM FRO BOOK RETURN

108
STATE CHART DIAGRAM-BOOK

STATE CHART DIAGRAM-LIBRARIAN

109
UML SEQUENCE DIAGRAM

110
SEQUENCE DIAGRAM FOR RETURN BOOK

111
COLLABORATION DIAGRAM FOR ISSUE BOOK

COLLABORATION DIAGRAM FOR RETURN BOOK

112
COMPONENT DIAGRAM

DEPLOYMENT DIAGRAM

113
 OUTPUT:
SOURCE CODE:

Book.java
import java.util.Vector;

public class Book {

public Integer bookId;

public String author;

public String name;

public Integer price;

public Integer rackNo;

public String status;

public Integer edition;

public Integer dateOfPurchase;

public Vector issues;

public Vector requests;

public void displayBooksDetails() {

}

public void updateStatus() {

}

Librarian.java
import java.util.Vector;

public class Librarian {

public String name;

public String password;

public Vector issues;

public Vector creates;
public Vector creates;

public void searchBooks() {

}

114
 public void verifyMember() {
}

public void issueBook() {

}

public void calculateFine() {

}

public void createBill() {

}

public void returnBook() {

}

Transaction.java
import java.util.Vector;

public class Transaction {

public Integer transId;

public Integer memberId;

public Integer bookId;

public Integer dateOfIssue;

public Integer dueDate;

public Vector creates;

public Vector refers;

public void createTransaction() {

}

public void deleteTransaction() {

}

public void retrieveTransaction() {

}

115
Bill.java
import java.util.Vector;

public class Bill {

public Integer billNo;

public Integer date;

public Integer memberId;

public Integer amount;

public Vector refers;

public Vector pays;
public Vector creates;

public void billCreate() {

}

public void billUpdate() {

}

MemberRecord.java
import java.util.Vector;

public class MemberRecord {

public Integer memberId;

public String type;

public Integer dateOfMembership;

public Integer noBookIssue;

public Integer maxBookLimit;

public String name;

public String address;

public Integer phoneNo;

public Vector pays;

public Vector requests;

public void retrieveMember() {

}

116
public void increaseBookIssue() {
}

public void decreseBookIssue() {

}

public void payBill() {

}

Faculty.java
public class Faculty extends MemberRecord {
}

Student.java
public class Student extends MemberRecord {
}

Journals.java
public class Journals extends Book {
}

Magzines.java
public class Magzines extends Book {
}

StudyBooks.java
public class StudyBooks extends Book {
}

RESULT:
Thus uml diagram for library management system as been created and executed successfully

117