ARUNACHALA COLLEGE OF

ENGINEERING FOR WOMEN

MANAVILAI, VELLICHANTHAI
KANYAKUMARI DISTRICT

LABORATORY RECORD 2023-2024

This to certify that this is the bonafide record of work done by

Ms…………………………………….Register Number …………………………….
of sixth semester, Department of Computer Science and Engineering of this college
in the Object Oriented Software Engineering (CCS356) during 2023-2024 in partial
fulfillment of the requirement of the B.E. degree course of the Anna University,
Chennai.

Staff-in-charge Head of the department

This record is submitted for the University practical Examination held on………………

INTERNAL EXAMINER EXTERNAL EXAMINER

 INDEX

SI PAGE
DATE EXPERIMENT NAME SIGNATURE
NO NO
 PASSPORT AUTOMATION SYSTEM
EX.NO:1
DATE:

AIM
To develop the Passport Automation System using Argo UML tools.

PROBLEM STATEMENT

Passport Automation System (PAS) is used in the effective dispatch of passport to

all of the applicants. 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.

USE CASE DIAGRAM

CLASSDIAGRAM
SEQUENCE DIAGRAM
COLLABORATION DIAGRAM

STATE CHART DIAGRAM

 ACTIVITY DIAGRAM

COMPONENT DIAGRAM
 PACKAGE DIAGRAM

DEPLOYMENT DIAGRAM

OUTPUT:

APPLICANT.CPP:
#include "Applicant.h"
Applicant::login()
{
}
Applicant::submitdetails()
{
}
Applicant::checkdetails()
{
}

DATABASE.CPP:
#include "database.h"
database::store()
{
}

PASSPORTADMNISTRATOR.H:
#ifndef PASSPORTADMINISTRATOR_H_HEADER_INCLUDED_AEF591BD
#define PASSPORTADMINISTRATOR_H_HEADER_INCLUDED_AEF591BD
class PassportAdministrator
{
public:
Getdetails();
Verify();
Store();
IssuePassport();
private:
Name;
};
#endif

POLICE.CPP:
#include "Police.h
Police::GetDetail()
{
}
Police::Verify()
{
}
Police::Store()
{
}

REGIONAL.CPP:
#include "RegionalAction.h"
RegionalAction::GetDetail()
{
}
RegionalAction::Verify()
{
}
RegionalAction::Store()
{
}
RESULT:
Thus the project to develop passport automation system was developed using Argo UML was
done successfully
EX. NO: 2 BOOK BANK MANAGEMENT SYSTEM
DATE:

AIM
To develop a project of Book bank management system using Argo UML

PROBLEM STATEMENT

The book bank management system is a software in which a member can register
themselves and then he can borrow books from the book bank. The process of members
registering and purchasing books from the book bank are described sequentially through
following steps:
• First the member registers himself if he was new to the book bank.
• Old members will directly select old member button..
• They select their corresponding year.
• After selecting the year they fill the necessary details and select the book and he will be
directed towards administrator
• The administrator will verify the status and issue the book

USE CASE DIAGRAM

 CLASS DIAGRAM

SEQUENCE DIAGRAM
COLLABRATION DIAGRAM

STATE CHART DIAGRAM

 ACTIVITY DIAGRAM

COMPONENT DIAGRAM
 PACKAGE DIAGRAM

DEPLOYMENT DIAGRAM
OUTPUT:

BOOKBANK.CPP:

#include "Bookbank.h"
Bookbank::checking()
{
}
Bookbank::issueing()
{
}
Bookbank::share()
{
}

STUDENT.CPP:

#include "Student.h"
Student::register()
{
}
Student::submitbookinformation()
{
}
Student::collectbook()
{
}
Student::register()
{
}

RESULT
Thus the project to develop book bank management system using Argo UML was done
successfully.
EX. NO: 3 EXAM REGISTRATION SYSTEM
DATE:

AIM
To develop a project Exam Registration using Argo UML.

PROBLEM ANALYSIS

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
• The students access exam registration application.
• They fill out the form with correct and eligible details.
• They complete the payment process.
• The authorities verify or check the details.
• After all verification the exam registration database is finalized.

USE CASE DIAGRAM

 CLASS DIAGRAM

SEQUENCE DIAGRAM
COLLABRATION DIAGRAM

STATE CHART DIAGRAM

ACTIVITY DIAGRAM
COMPONENT DIAGRAM

DEPLOYMENT DIAGRAM
 PACKAGE DIAGRAM
UI

Swing Text

ExamReg ExamReg
System Console

Domain

Student ExamController

Register ViewFeeDetail Confirmation Display Fee

Authentication

Logout
Login

Technical Services

Persistence Log4J
SOAP

DBFacade
OUTPUT:

REGWEBSITE.CPP:

#include "Reg website.h"

Reg website::verification()
{
}
Reg website::processing()
{
}
Reg website::registrating()
{
} STUDENT1.CPP:

#include "Student1.h"
Student::form filling()
{
}
Student::registration()
{
}

UNIVERSITY.CPP:

#include "University Database.h"

University Database::storing registration()
{
}

RESULT
Thus the project to develop Exam Registration system using Argo UML was done
successfully.
EX. NO: 4 STOCK MAINTENANCE SYSTEM
DATE:

AIM
To develop a project stock maintenance system using Argo UML

PROBLEM ANALYSIS

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.

PROBLEM STATEMENT

The process of stock maintenance system is that the customer login to the particular site
to place the order for the customer product. The stock maintenance system are described
sequentially through steps
• The customer login to the particular site.
• They fill the customer details.
• They place the orders for their product.
• The vendor login and views the customer details and orders.

USE CASE DIAGRAM

 CLASS DIAGRAM

SEQUENCE DIAGRAM
COLLABRATION DIAGRAM

STATE CHART DIAGRAM

ACTIVITY DIAGRAM
 PACKAGE DIAGRAM

UI

Swing Text

StMain System StMaint

Console

Domain

Customer Order

Register Invoice Stock

Shipment
Product

Technical Services

Persistence SOAP Log4J

DBFacade
 COMPONENT DIAGRAM

OUTPUT:

AGENT.CPP:
#include "agent.h"
agent::request()
{
}
agent::purchase()
{
}
agent::bill()
{
}
CASH.CPP:
#include "cash.h"
cash::amt()
{
}

ITEM.CPP:
#include "item.h"
item::expiry date()
{
}
item::Quantity()
{
}
item::price()
{
}

ORDER.CPP:
#include "order.h"
order::purchase()
 {
}
order::discount(void 0)
{
}
order::product count()
{
}

SYSTEM.CPP:
#include "system.h"
system::associativity()
{
}
system::expiry date()
{
}

TOTAL PROFIT.CPP:
#include "toatl profit.h"
toatl profit::amt()
{
}

RESULT
Thus the project to develop Stock Maintenance system using Argo UML was done
successfully.
EX. NO: 5 ONLINE COURSE RESERVATION SYSTEM
DATE:

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

PROBLEM ANALYSIS

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

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

USE CASE DIAGRAM

 CLASS DIAGRAM

SEQUENCE DIAGRAMS
COLLABRATION DIAGRAMS
STATE CHART DIAGRAM

COMPONENT DIAGRAM
ACTIVITY DIAGRAM

PACKAGE DIAGRAM

Deployment diagram
 OUTPUT:

IT.CPP:

#include “CSE/IT.h”
CSE/IT :: Terminate()
{
}

COLLAGE.CPP:

#include "College.h"
Collage::admision()
{
}

EEE.CPP:
#include “EEE.h”
MBA.CPP:
#include "MBA.h"

MECHANICAL.CPP:
#include "Mechanical.h"
Mechanical::production()
{
}
STUDENT.CPP:

#include "Student.h"
Student::study()
{
}

RESULT
Thus the project to develop online course reservation system was developed using Argo UML
was done successfully.
EX. NO: 6 AIRLINE/RAILWAY RESERVATION SYSTEM
DATE:

AIM
To develop the Airline/Railway reservation system using Argo UML.

PROBLEM ANALYSIS

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

PROBLEM STATEMENT

The Airline/Railway reservation system is the initial requirement to develop the project
about the mechanism of the E-ticketing system what the process do at all.
• The requirement are analyzed and refined which enables the end users to efficiently use the E-
ticketing system.

• First the applicant wants to login to the database after that the person wants to fill their details.
• Then the database will seach for ticket or else the person will cancelled the ticket if he/she no
need.

SOFTWARE REQUIREMENT SPECIFICATION

INTRODUCTION
The Airline/Railway reservation system supports online ticket booking. It has various
options like reservation, cancellation and to view details about available seats.

SCOPE
The main scope for this project is that the applicant should reserve for the flight/railway
ticket.
It provides a communication platform between the passenger and the administrator. Also the
Passenger will come to know their status of application

FUNCTIONALITY
The database should be act as an main role of the Airline/Railway reservation system it
can be booking the ticket in easy way.

USER CHARACTERISTICS

• Applicant - They are the people who desire to book the ticket and submit the information
to the database.

CONSTRAINTS
• The applicants require a computer to submit their information.
• The user has to be careful while submitting the information. Much care is required.

USE CASE DIAGRAM

 CLASS DIAGRAM

SEQUENCE DIAGRAM
COLLABRATION DIAGRAM

STATE CHART DIAGRAM

COMPONENT DIAGRAM
 ACTIVITY DIAGRAM

OUTPUT:
APPLICANT.CPP:

#include "Applicant.h"
Applicant::filling details()
{
}
Applicant::selecting flight()
{
}
Applicant::book ticket()
{
}
Applicant::cancel ticket()
{}
ETICKETING DATABASE.CPP:

#include "Eticketing database.h"

Eticketing database::ticket booking()
{
}

Eticketing database::hotel booking()

{
}
Eticketing database::verifing ticket()
{
}

RESULT
Thus the project to develop Airline/Railway reservation system using Argo
UML was done successfully.
EX. NO: 7 SOFTWARE PERSONNEL MANAGEMENT SYSTEM
DATE:

AIM
To develop a project Software personnel management system using the Argo UML.

PROJECT ANALYSIS

The Software personnel 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.

SOFTWARE REQUIREMENT SPECIFICATION

INTRODUCTION
The Software Personnel Management system is an interface between Employee and the
administrator responsible for generation of payment slip. It aims at improving the efficiency in
the generation of Pay slip and reduces the complexities involved in it to the maximum possible
extent.

PURPOSE
If the entire process of Software personnel management is done in a manual manner then it
would more time for pay slip generation process. Considering the fact that the number of
employee 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

• Software system allows Administrator to manage its employee in a better way.

• When needed, it will take just a few second to find out the background of an employee
and his/her contribution to the organization, it will also facilitate keeping all the records
of employee.
 • So all the information about an employee will be available in a few seconds, it will also
make it very easy to generate statistical data or custom data, line finding a certain set of
employee.

USER CHARACTERISTICS
• Employee - These are the person who desires to view the salary details.
• Administrator - Administrator has the certain privileges to generate pay slip for the
employee.
• Database manager - DB manager stores all the data related to Employee and
Administrator.

CONSTRAINTS
The administrator requires a system to monitor information of the employee.

ASSUMPTIONS AND DEPENDENCIES

The employee and Administrator must have basic knowledge of computers and English
Language.

UML DIAGRAMS

1. Usecase Diagram
2. Class Diagram
3. Sequence Diagram
4. Collaboration Diagram
5. State Chart Diagram
6. Component Diagram

USE CASE DIAGRAM

 CLASS DIAGRAM

SEQUENCE DIAGRAMS

46
COLLABRATION DIAGRAMS

47
STATE CHART DIAGRAM

COMPONENT DIAGRAM

48
ACTIVITY DIAGRAM

PACKAGE DIAGRAM

49
OUTPUT:

CEO.CPP:

#include "CEO.h"
CEO::view()
{
}
CEO::update()
{
}
CEO::login()
{
}

DATABASE.CPP:

#include "database.h"
database::storedata()
{
}
database::update()
{
}
database::insert()
{
}
database::enquiry()
{
}
database::delete()
{
}
database::verify()
{
}
database::display()
{
}

EMPLOYEE.CPP:

#include "employee.h"

RESULT
Thus the project is to develop a Software personnel management system using the Argo
UML was done successfully.
50
EX. NO: 8 CREDIT CARD PROCESSING SYSTEM
DATE:

AIM
To develop credit card processing system using the Argo UML.

PROBLEM ANALYSIS

The Credit Card Processing System which is used 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

SOFTWARE REQUIREMENT SPECIFICATION

INTRODUCTION
A credit card is a small plastic card issued to users as a system of payment. It allows its
holder to buy goods and services. When a purchase is made, the merchant swipes the card.
Credit card accounts entered during booking are validated to assure that the account is active and
in good standing

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

SCOPE

• Automatically connects to your financial network for credit card authorizations and
settlements
• Compliant with Visa and MasterCard Electronic Commerce Indicator (ECI) regulations

51
FUNCTIONALITY

Many members of the process lives to checking for the occurrence and transaction we all
have to carry over sometimes user interface to make the transaction to be efficient.

USER CHARACTERISTICS

• Customer – He buys the product using his credit card.

• Vendor – Accepts credit card and gives bill to the customer.

ASSUMPTION AND DEPENDENCIES

The Vendor and Customer must have basic knowledge of computers and English
Language. The vendor may be required to deliver the item purchased by the customer.

USE CASE DIAGRAM

52
 CLASS DIAGRAM

SEQUENCE DIAGRAM

53
COLLABRATION DIAGRAM

STATE CHART DIAGRAM

54
 COMPONENT DIAGRAM

PACKAGE DIAGRAM

UI

Swing

CCP system

Domain

User Merchant

Purchase Account Info Request Receipt

AutherizationSerivic
e

Reply

65
 DEPLOYMENT DIAGRAM

ACTIVITY DIAGRAM

OUTPUT:

66
CARD READER.CPP:

#include "card reader.h"

card reader::make transistion()
{
}
card reader::print receipt()
{
}

CUSTOMER.cpp:

#include "customer.h"
customer::purchase
item()
{
}
customer::swap()
{
}

VENDOR.CPP:

#include
"vendor.h"
vendor::make
bill()
{
}
vendor::delivery item()
{

}
vendor::submit()
{
}

RESULT
Thus the project to develop credit card processing system using Argo UML was
donesuccessfully.

67
EX. NO: 9 EBOOK MANAGEMENT SYSTEM
DATE:

AIM
To develop a project E-Book Management system using Argo UML

PROBLEM ANALYSIS

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 e-book purchase process can
be improved. E-book management in this project gives the idea about how e-books are
maintained in a particular concern. The book details which includes the number of books
available, no of pages and price. E-book management system the E-book management in this
project is understood by going through the modules that is being involved.

SOFTWARE REQUIREMENT SPECIFICATION

INTRODUCTION

E-book management gives an idea about how e-books are maintained in the particular
concern. The e-books that are to be purchased, the e-books that are to be sold are maintained
here. Further some additional details of the current e-book list that is available in the website are
also given. E-book management in this project is done in an authorized way.

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

SCOPE

The scope of this e-book management is to maintain the book details after the purchase
and list of reaming books available in the same book type.

USER CHARACTERISTICS
• User - One who wishes to obtain the Books or Magazines.
• Administrator - One who manages and maintain Books or Magazines.

68
CONSTRAINTS
The User requires a computer to submit their information.

ASSUMPTIONS AND DEPENDENCIES

The user and e-book manager must have basic knowledge of computers and English Language.

USE CASE DIAGRAM

CLASS DIAGRAM

69
 SEQUENCE DIAGRAM

COLLABRATION DIAGRAM

STATE CHART DIAGRAM

70
 ACTIVITY DIAGRAM

COMPONENT DIAGRAM

PACKAGE DIAGRAM

71
 UI

Swing

E-Book system

Domain

Client bill Order

Credit History Process Balance

Technical Services

Persistence Log4J
SOAP

DBFacade

DEPLOYMENT DIAGRAM

OUTPUT:

BOOKS.CPP:

#include "books.h"
books::select()
{
}
books::buy()
{
72
}

CUSTOMER.CPP:

#include "customer.h"
customer::login()
{
}
customer::payment()
{
}

DATABASE.CPP:

#include "database.h"
database::store()
{
}

RESULT
Thus the project to develop E-book Management System using Argo UML was done
successfully.

73
 EX. NO: 10 RECRUITMENT SYSTEM
DATE:

AIM
To develop a project an recruitment system using Argo UML.

PROBLEM ANALYSIS

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

SOFTWARE REQUIREMENT SPECIFICATION

INTRODUCTION

This software specification documents full set of features and function for online
recruitment system that is performed in company website. In this we give specification about the
system requirements that are apart from the functionality of the system to perform the
recruitment of the jobseekers. It tells the usability, reliability defined in use case specification.

PURPOSE

If the entire process of Recruitment is done in a manual manner then it would

takes several days for the recruitment. Considering the fact that the number of applicants for
recruitment is increasing every year, an Automated System becomes essential to meet the
demand. So this system uses several programming and database techniques to elucidate the work
involved in this process.
USE CASE DIAGRAM

74
SCOPE

The scope of this recruitment process is to select the best applicant from the list of
applicant registered based on their performance in the recruitment process.

USER CHARACTERISTICS

• Applicant – These are the persons who desire to apply for the job.
• Organization - These are the person with certain privileges to announce recruitment
depending upon the organization need. He/ She may contain a group of persons
under him/her to publish advertisement and give suggestion whether or not to approve
the recruitment.
• HR - He/ She is the person who upon receiving intimation from the RS, perform a
personal verification of the applicants and see if he/she has eligibility for the
advertised job through a process of Test and Interview.

CONSTRAINTS

The Applicants require a computer to submit their information.

ASSUMPTIONS AND DEPENDENCIES

The Applicants and HR must have basic knowledge of computers and English Language.

75
 CLASS DIAGRAM

SEQUENCE DIAGRAM FOR REGISTER &

STATUS,ADMIN

76
COLLABRATION DIAGRAM FOR REGISTER &
STATUS,ADMIN

77
78
STATE CHART DIAGRAM

COMPONENT DIAGRAM

79
ACTIVITY DIAGRAM

80
 PACKAGE DIAGRAM

UI

Swing Text

Recruitment Recruitment
system Form

Domain

Candidate Admin panel

Submit Cancel send delete

Status

Get status

Technical Services

Persistence Log4J
SOAP
DBFacade

81
 DEPLOYMENT DIAGRAM

OUTPUT:

Applicant.cpp:

#include "Applicant1.h"
Applicant1::Register()
{
}
Applicant1::Login()
{
}
Applicant1::Applicant Details()
{
}
Database1.cpp:
#include "Database11.h"
Database1::APs_details()

{
Database1::tech_details()
{
}
Database1::selected_applicant_details()
{
}

Recruiter.cp
p:
#include "Recruiter1.h"
Recruiter1::APS_test()
{
}
Recruiter1::APS1_test()
{
}
Recruiter1::Tech_Round()
{
}
82
Recruiter1::Tech1_Round()
{
}

RESULT
Thus the project to develop online recruitment system using Argo UML was done
successfully.

83
EX. NO: 11 FOREIGN TRADING SYSTEM
DATE:

AIM
To design a project Foreign Trading System using Argo UML.

PROJECT ANALYSIS

The initial requirements to develop the project about the mechanism of the Foreign
Trading System is bought from the trader. The requirements are analyzed and refined which
enables the analyst (administrator) to efficiently use the Foreign Trading System. The complete
project analysis is developed after the whole project analysis explaining about the scope and the
project statement is prepared.

PROBLEM STATEMENT

The steps involved in Foreign Trading System are:

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

SOFTWARE REQUIREMENT SPECIFICATION

INTRODUCTION

International trade is exchange of capital, goods, and services across international borders
or territories. In most countries, it represents a significant share of gross domestic product
(GDP). While international trade has been present throughout much of history (see Silk Road,
Amber Road), its economic, social, and political importance has been on the rise in recent
centuries. Industrialization, advanced transportation, globalization, multinational corporations,
and outsourcing are all having a major impact on the international trade system. Increasing
international trade is crucial to the continuance of globalization. Without international trade,
nations would be limited to the goods and services produced within their own borders.

SCOPE
The are a lot of advantages in Forex Trading as compared to many other financial trading,
like futures or stock trading. The Forex market is open 24 hour a day. Being the market available

84
24 hours a day, this gives the trader to choose which time they would like to trade. It requires
only minimum beginning capital to start the Forex trade. Forex Trading has outstanding liquidity
as it never closes.
USER CHARACTERISTICS

• Trader - They are the people who desire to trade on international market.

CONSTRAINTS

• The trader requires a computer to submit their information.

• The trader has to be careful while providing the information.

ASSUMPTIONS AND DEPENDENCIES

• The trader must have basic knowledge of computers and English Language.

USE CASE DIAGRAM

85
 CLASS DIAGRAM

SEQUENCE DIAGRAM

86
COLLABRATION DIAGRAM

STATE CHART DIAGRAM

87
COMPONENT DIAGRAM

PACKAGE DIAGRAM

DEPLOYMENT DIAGRAM

88
OUTPUT:

Account.cpp:

#include "Account.h"
Account::Account no()
{}
Account::account pay()
{}
Administrator1.cpp:

#include "Administrator1.h"
Administrator1::Bill1()
{}
Administrator1::Bill2()
{}
Administrator1::Trace order()
{}
Administrator1::pay bill1()
{}
Administrator1::pay bill2()
{}
Item.cpp:

#include "Item.h"
Item::Get perfume()
{}
Item::Get dolls()
{}
Traders.cpp:
#include "Traders.h"
Traders::Login()
{}
Traders::Sourcing()
{ }
Traders::place order()
{}
Traders::pay()
{}
Traders::logout()
{}

RESULT
Thus the project to develop foreign trading system using Argo UML was done
successfully.

89
EX. NO: 12 CONFERENCE MANAGEMENT SYSTEM
DATE:

AIM
To develop a project on Conference management system using Argo UML

PROBLEM ANALYSIS

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.

PROBLEM STATEMENT

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

SOFTWARE REQUIREMENT SPECIFICATION

INTRODUCTION

This software specification document consist full set of features and function for online
conference management system. In this we give specification about the system requirements that
are apart from the functionality of the system to perform the candidate paper valuation. It tells
the usability, reliability defined in use case specification.

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

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

90
USER CHARACTERISTICS

Candidate - Logins the conference system and submits the paper then do the registration process.
Reviewer – Review the paper, select best candidate and send acknowledgement to them.

CONSTRAINTS

The user has to be careful while submitting the information. Much care is
required.

ASSUMPTIONS AND DEPENDENCIES

The candidate and reviewer must have basic knowledge of computers and English
Language.
USE CASE DIAGRAM

91
 CLASS DIAGRAM

SEQUENCE DIAGRAMS

92
COLLABRATION DIAGRAMS

93
STATE CHART DIAGRAM

COMPONENT DIAGRAM

94
 ACTIVITY DIAGRAM

DEPLOYMENT DIAGRAM

OUTPUT:

Candidates.cpp
#include "candidates.h"
candidates::login()
{
}
candidates::submit the paper()
{
}
candidates::revise,camera ready paper & submission()
{
}
candidates::registration()
{
}
95
Database.cpp
#include "database 1.h"
database 1::code verification()
{
}
database 1::reviewer accessibility()
{
}

Reviewer.cpp
#include "reviewer1.h"
reviewer1::paperreview()
{
}
reviewer1::sending paper confirmation details()
{
}

RESULT
Thus the project to develop conference management system using Argo UML was
done successfully.

96
EX. NO: 13 BUSINESS PROCESS OUTSOURCING MANAGEMENT SYSTEMS
DATE:

AIM
To develop a project Business Process Outsourcing(BPO) management system using
Argo UML.

PROBLEM ANALYSIS

Generally outsourcing can be defined as an organization entering into a contract with

another organization to operate and managed one or more of its business processes. There are
many problems faced by the BPO one among them is meeting their targets and leaving the
concern very often and switch to another company. In this project we deal with the inbound
system of the BPO. In inbound system the agent calls the customer from his database to sell his
product.

PROBLEM STATEMENT

In this BPO inbound system, the process undergoing is that the agent tries to sell his
product so that the agent gets the details of the customer from the database and pitches about his
product and makes the sales successful. The communication is done through the telephone.
Telephone is the major component used for this customer satisfaction service. The steps are as
follows:
• The agent login to the website and enters the username and password .It checks for
authorization.
• If the username and password is correct, it allows the agent to get the details of the customer
from the database.
• Now the agent makes the call to the customer and pitches about the product.
• If the customer is satisfied, agent sells the product else disconnects the call.
• Agent proceeds with another call.

SOFTWARE REQUIREMENT SPECIFICATION

INTRODUCTION

BPO is typically categorized into back office outsourcing-which includes internal

business functions such as human resources or finance and accounting, and front office
outsourcing-which includes customer related services such as contact center services. BPO that
is contracted outside a company’s country is called offshore outsourcing. BPO that is contracted
to a company’s neighboring country is called near shore outsourcing. Given the proximity of
BPO to the information technology industry, it is categorized as an information technology
enabled service or ITES. Knowledge process outsourcing (KPO) and legal process outsourcing
(LPO) are some of the sub-segments of business process outsourcing industry. In the following
SRS the front office outsourcing is explained in detail.

PURPOSE
• Seamless process that is fully integrated ensuring better quality of service to customers.

97
 • Cost reductions by automation of upload processes from clients; automatic routing of
documents to operators using OCR.
• Documents as well as the status of process is accessible quickly and from anywhere to
BPO management as well as customers.
• Enriched experience for users as they can search for documents and process them online.

SCOPE

The main scope is to develop a good BPO management system. BPO is a way in which it
helps to increase company’s flexibility. As part of BPO, documents need to be managed between
the outsourcing company and the offshore company. Multiple clients need to be managed by the
BPO company.

USER CHARACTERISTICS

• BPO Organization - They are the people who desire to obtain the outsourcing job from
various clients and submit the information to the database.
• Client - He has the certain privileges to outsource their jobs and to approve the issue of
document. He may contain a group of persons under him to verify the documents
and give suggestion whether or not to approve the dispatch of job.

CONSTRAINTS

• The Client requires a computer to submit their information.

ASSUMPTIONS AND DEPENDENCIES

• The BPO Organization and Client must have basic knowledge of computers and English
Language.

UML DIAGRAMS

1. Usecase Diagram
2. Class Diagram
3. Sequence Diagram
4. Collaboration Diagram
5. State Chart Diagram
6. Component Diagram

98
USE CASE DIAGRAM

99
SEQUENCE DIAGRAM

100
COLLABRATION DIAGRAM

COMPONENT DIAGRAM

101
STATE CHART DIAGRAM

DEPLOYMENT DIAGRAM

102
PACKAGE DIAGRAM:

UI

Swing Text

BPOS Recruitment
Form

Domain

BPOS Admin

QC Data Entry Download OCR

Client

Upload Feedback

Technical Services

Persistence Log4J
SOAP

DBFacade

103
 CLASS DIAGRAM

OUTPUT:
CUSTOMER.CPP:

#include "customer.h"
customer::attend call()
{
}
customer::asks query()
{
}

DATABASE.CPP:

#include "database.h"
database::get details()
{
}
database::upadate detail()
{
}
104
PROCESSAGENT.CPP:

#include "process agent.h"

process agent::make call()
{
}
process agent::pitches about product make sales()
{
}
process agent::end the call()
{
}

RESULT
Thus the project to develop BPO management system using Argo UML and was done
successfully.

105
EX. NO: 14 LIBRARY MANAGEMENT SYSTEM
DATE:

AIM
To develop a project on Library Management system using Argo UML.

PROBLEM STATEMENT

Library Management System is software used to manages the catalog of a library. This helps to
keep the records of whole transactions of the books available in the library.

USE CASE DIAGRAM

login

<<actor>>
projection of

user

issue book

return book

maintain database DBA

106
 CLASS DIAGRAM

STATE CHART DIAGRAM

login enter requesting display book

details for book details

logout return book issue book search

book

107
SEQUENCE DIAGRA

DEPLOYMENT DIAGRAM

108
COLLABRATION DIAGRAM

COMPONENT DIAGRAM

109
ACTIVITY DIAGRAM

110
 PACKAGE DIAGRAM

RESULT
Thus the project to develop Library management system using Argo UML and was done
successfully.

111
EX.NO: 15 STUDENT INFORMATION SYSTEM
DATE:

AIM
To develop a project on Student Information system using Argo UML.

PROBLEM STATEMENT

The student must register by entering the name and password to login the form. The admin select
the particular student to view the details about that student and maintaining the student
details. This process of student information system is described sequentially through following
steps.
• The student registers the system.
• The admin logins to the student information system.
• He/she search for the list of students.
• Then select the particular student.
• Then view the details of that student.
• After displaying the student details then logout.

COMPONENT DIAGRAM

112
USE CASE DIAGRAM

113
CLASS DIAGRAM

114
SEQUENCE DIAGRAM

115
COLLABRATION DIAGRAM

STATE CHART DIAGRAM

116
RESULT
Thus the project to develop Student information system using Argo UML and was done
successfully.

117
 EXPERIMENTS (BEYOND THE SYLLABUS)
EX. NO: 1 ATM SYSTEM

AIM
To draw the UML diagrams for ATM system using Argo UML.

UML DIAGRAMS

USECASE DIAGRAM

118
CLASS DIAGRAM

119
SEQUENCE DIAGRAM

120
COLLABORATION DIAGRAM

121
STATE CHART DIAGRAM

122
COMPONENT DIAGRAM

123
 DEPLOYMENT DIAGRAM

RESULT
Thus the UML diagrams for ATM system using Argo UML was done successfully.

124
EX. NO: 2 RETAIL STORE SYSTEM

AIM
To draw the UML diagrams for Retail Store system using Argo UML.

UML DIAGRAMS

USECASE DIAGRAM

125
CLASS DIAGRAM

126
 SEQUENCE DIAGRAM

STATE CHART DIAGRAM

127
COLLABORATION DIAGRAM

128
ACTIVITY DIAGRAM

129
 COMPONENT DIAGRAM

DEPLOYMENT DIAGRAM

RESULT
Thus the UML diagrams for Retail Store system using Argo UML was done successfully.

130
EX. NO: 3 TOUR MANAGEMENT SYSTEM

AIM
To draw the UML diagrams for Tour Management system using Argo UML.

UML DIAGRAMS

USECASE DIAGRAM

131
CLASS DIAGRAM

132
SEQUENCE DIAGRAM

133
ACTIVITY DIAGRAM

134
COLLABORATION DIAGRAM

135
STATE CHART DIAGRAM

136
COMPONENT DIAGRAM

137
 DEPLOYMENT DIAGRAM

RESULT
Thus the UML diagrams for Tour Management system using Argo UML was done
successfully.

138
EX. NO: 4 VENDING MACHINE SYSTEM

AIM
To draw the UML diagrams for Vending Machine system using Argo UML.

UML DIAGRAMS

USECASE DIAGRAM

139
CLASS DIAGRAM

140
SEQUENCE DIAGRAM

141
ACTIVITY DIAGRAM

142
STATE CHART DIAGRAM

143
COLLABORATION DIAGRAM

144
COMPONENT DIAGRAM

145
 DEPLOYMENT DIAGRAM

RESULT
Thus the UML diagrams for Vending Machine system using Argo UML was done
successfully.

146
EX. NO: 5 AIRPORT CHECK-INAND BOARDING SYSTEM

AIM
To draw the UML diagrams for Airport Check-in and Boarding system using Argo UML.

UML DIAGRAMS

USECASE DIAGRAM

147
CLASS DIAGRAM

148
SEQUENCE DIAGRAM

149
COLLABORATION DIAGRAM

150
STATE CHART DIAGRAM

COMPONENT DIAGRAM

DEPLOYMENT DIAGRAM

151
RESULT
Thus the UML diagrams for Airport Check-in and Boarding system using Argo UML was
done successfully.

152
 VIVA QUESTIONS

1. What is Object-Oriented Analysis?

During object-oriented analysis there is an emphasis on finding and describing the objects
or concepts in the problem domain. For example, in the case of the flight information
system, some of the concepts include Plane, Flight, and Pilot.

2. What is Object-Oriented Design?

During object-oriented design (or simply, object design) there is an emphasis on defining
software objects and how they collaborate to fulfill the requirements. The combination of
these two concepts shortly known as object oriented analysis and design.

3. What is Object-Oriented Analysis and Design?

During object-oriented analysis there is an emphasis on finding and describing the objects
or concepts in the problem domain. For example, in the case of the flight information
system, some of the concepts include Plane, Flight, and Pilot.

During object-oriented design (or simply, object design) there is an emphasis on defining
software objects and how they collaborate to fulfill the requirements. The combination of
these two concepts shortly known as object oriented analysis and design.

4. What is Analysis and Design?

Analysis emphasizes an investigation of the problem and requirements, rather than a

solution. Design emphasizes a conceptual solution (in software and hardware) that fulfills
the requirements, rather than its implementation. For example, a description of a database
schema and software objects.

5. Define Design Class Diagrams

A static view of the class definitions is usefully shown with a design class diagram. This
illustrates the attributes and methods of the classes.

6. What is the UML?

The Unified Modeling Language is a visual language for specifying, constructing and
documenting the artifacts of systems.

7. What are the three ways and perspectives to Apply UML?

Ways - UML as sketch, UML as blueprint, UML as programming language

Perspectives-Conceptual perspective, Specification (software) perspective, Implementation

153
 (Software) perspective.

8. What is Inception?

Inception is the initial short step to establish a common vision and basic scope for the
Project. It will include analysis of perhaps 10% of the use cases, analysis of the critical
non-Functional requirement, creation of a business case, and preparation of the
development Environment so that programming can start in the elaboration phase.
Inception in one Sentence: Envision the product scope, vision, and business case.

9. What Artifacts May Start in Inception?

Some sample artifacts are Vision and Business Case, Use-Case Model, Supplementary
Specification, Glossary, Risk List & Risk Management Plan, Prototypes and proof-of-
concepts etc.

10. Define Requirements and mention its types.

Requirements are capabilities and conditions to which the system and more broadly, the
project must conform.

1. Functional

2. Reliability

3. Performance

4. Supportability

11. What are Actors?

An actor is something with behavior, such as a person (identified by role), computer system, or
organization; for example, a cashier.

12. What is a scenario?

A scenario is a specific sequence of actions and interactions between actors and the system; it is
also called a use case instance. It is one particular story of using a system, or one path through
the use case; for example, the scenario of successfully purchasing items with cash, or the
scenario of failing to purchase items because of a credit payment denial.

13. Define Use case.

A use case is a collection of related success and failure scenarios that describe an actor using a
system to support a goal. Use cases are text documents, not diagrams, and use-case modeling is
primarily an act of writing text, not drawing diagrams.

14. What are Three Kinds of Actors?

154
Primary actor, Supporting actor, offstage actor.

15. What Tests Can Help Find Useful Use Cases?

1. The Boss Test

2. The EBP Test

3. The Size Test

16. What are UseCase Diagrams?

A use case diagram is an excellent picture of the system context; it makes a good context
diagram that is, showing the boundary of a system, what lies outside of it, and how it gets used.
It serves as a communication tool that summarizes the behavior of a system and its actors.

17. What are Activity Diagrams?

A diagram which is useful to visualize workflows and business processes. These can be a useful
alternative or adjunct to writing the use case text, especially for business use cases that describe
complex workflows involving many parties and concurrent actions.

18. List the relationships used in use cases?

1.Include

2.Extend

3.Generalize

19. List out the steps for finding use cases.

• Identifify the actor
• Name the use cases
• Describe the usecse by using terminologies.

20. What is an object?

An object is a combination of data and logic; the representation of some real-world entity.

21. What is the main advantage of object-oriented development?

• High level of abstraction

• Seamless transition among different phases of software development

155
• Encouragement of good programming techniques.

• Promotion of reusability.

22. What is Object Oriented System development methodology?

Object oriented system development methodology is a way to develop software by building

self-contained modules or objects that can be easily replaced, modified and reused.

23. Distinguish between method and message in object.

Method Message

i) Methods are similar to functions, procedures or subroutines in more traditional

programming languages. Message essentially are non-specific function calls.

ii) Method is the implementation. Message is the instruction.

iii) In an object oriented system, a method is invoked by sending an object a message. An object
understands a message when it can match the message to a method that has the same name as
the message.

24. What is Elaboration?

Elaboration is the initial series of iterations during which the team does serious investigation,
implements (programs and tests) the core architecture, clarifies most requirements, and tackles
the high-risk issues. In the UP, "risk" includes business value. Therefore, early work may
include implementing scenarios that are deemed important, but are not especially technically
risky.

25. What is a Domain Model?

A domain model is a visual representation of conceptual classes or real-situation objects in

a domain. The term "Domain Model" means a representation of real-situation conceptual
classes, not of software objects. The term does not mean a set of diagrams describing
software classes, the domain layer of a software architecture, or software objects with
responsibilities.
26. How the domain model is illustrated?

Applying UML notation, a domain model is illustrated with a set of class diagrams in
which no operations (method signatures) are defined. It provides a conceptual perspective.
It may show: domain objects or conceptual classes, associations between conceptual
classes, attributes of conceptual classes.

156