Passport Automation System

WWW.VIDYARTHIPLUS.
COM
EXNO:1
DATE:
PASSPORT AUTOMATION SYSTEM
AIM:
To generate the UML diagram for online passport verification system.
ALGORITHM:
MODULE 1:
 Provide a user interface for getting the user’s login details.

 Verify login id and if correct,provide access to online passport verification
system.
MODULE 2:
 If a new user enters,provide a registration.

 Enter the applicant id and verify the status of the application.
MODULE 3:
 Process the application.

 If the passport is valid,then accept the passport.
USECASE DIAGRAM:
1
WWW.VIDYARTHIPLUS.COM
ACTIVITY DIAGRAM:
Check Status
Admin Panel
2
CLASS DIAGRAM:
CODE GENERATION:
Public class Passportautomatonsystem
Public passportautomatonsystem
3
Public class Applicationstatus
Public string applicantid;
Public Applicationstatus
Public getstatus
Public applicationstatus
Public class Newregistrationsystem
Public string name;
Public string dob;
Public string fname;
Public string foccupation;
Public string address;
4
Public Newregistrationsystem {
Public register{
Public cancel{
SEQUENCE DIAGRAM:
Check Status
Admin panel
5
COLLABORATION DIAGRAM:
Check Status
Admin Panel
6
STATE CHART DIAGRAM:
Enter login Verify Grant

name password permission
Enter
applicant id
Validate Process the

passport
COMPONENT DIAGRAM:
Applicant Passport verification

system
Manager
DEPLOYEMENT DIAGRAM:
passport verification
system
applicant <<TCP/IP>>
RESULT:
The UML diagram for Online passport verification system was generated successfully.
7
EX NO :2
DATE :
BOOK BANK
AIM:
To generate the UML diagram for online passport verification system.
ALGORITHM:
MODULE 1
 Verify login ID and if correct, provide access to the library database.
MODULE 2
 Provide a search mechanism to search for a particular book.
 Input the book name and the author’s name.
MODULE 3
 Get the book details from the database.
 Display the book details on the screen.
MODULE 4
 Allow the user to select the book for checking out.
 Issue the book.
8
USE CASE DIAGRAM:
CLASS DIAGRAM:
Software Entry
Data Entry Querying

Name
Id no.
Book name
Author
DOI
DOR
Card no Issue Return
Querying Querying
Issue() DOI.
Return()
Return ()
paymentl()
Issue()
9
CODE GENERATION:
Public class softwareentry
{
Public softwareentry()
{
}*
Public class dataentry{
Public dataentry{
}
Public string name;
Public string idno;
Public string bookname;
Public string author;
Public string doi;
Public string dor;
Public string cardno;
Public issue(){
}
Public return(){
}
Public class querying{
}
Public class issue querying{
Public string dol;
}
Public payment(){
}
Public issue(){}
Public class return querying{
Public return(){
}
10
SEQUENCE DIAGRAM:
Student bookbank
manager Administrator
Enter Login Details
Verify Authentication
Grant Permission/ Deny
Enter Login Details
Verify Authentication
Grant Permission/Deny
Enter Book name

Search the book
Enter author name
Check the book
Display results
11
manager
Student
9: Enter author name

11: Issue the book
6: Grant Permission/Deny
1: Enter Login Details
4: Enter Login Details3: Grant Permission/ Deny

7: Enter Book name
2: Verify Authentication
5: Verify Authentication
8: Search the book
System Administrator
STATECHART DIAGRAM:
Enter login Verify Grant

name permission
Enter the
book name
Issue the Display the

book book
12
ACTIVITY DIAGRAM:
Enter login
name
Verify
Grant
permission
Enter book
name
Enter author Display the

name book
Check out the

book
COMPONENT DIAGRAM:
13
DEPLOYMENT DIAGRAM:
Client Web Server

Processor
RESULT:
The above modules for the Book Bank System have been designed and verified.
14
EX NO: 3
DATE
EXAM REGISTRATION SYSTEM
AIM:
To generate the UML diagram for Exam registration system.
ALGORITHM:
MODULE 1:
 The system gets the application registration form.

 The system gets the data from the user and checks for validity.
MODULE 2:
 If the form is valid then the system checks for correction of data with respect to
the respective colleges database.
 The form checks for eligibility criteria.
MODULE 3:
 If the form is valid and eligible and there is no reduction in the given data then the
unique registration id, and hall ticket is issued to the applicant.
 If the form entries are invalid then the application form is rejected.
15
USE CASE DIAGRAM:
16
ACTIVITY DIAGRAM:
17
CLASS DIAGRAM:
CODE GENERATION:
public class applicant

{
private number app_id;
private string app_name;
public validation theValidation[];
/**
@roseuid 3F0925F102AF
*/
public applicant(){
}
/** @roseuid 3F092385009C */
18
public void fill_form(){

}
}
public class validation {
private number phone_no;
private string address;
private number age;
private number mark;
public admin theAdmin[];
/**@roseuid 3F09267601C */
public validation() {
}
/**
@roseuid 3F0923F202BF
*/
public void valid_data() {
}
/**
@roseuid 3F09240A032C
*/
public void valid_criteria() {
}
}
public class admin
{
private string mail_id;
private number reg_no;
/**
@roseuid 3F0926830232
*/
public admin() {
}
/**
@roseuid 3F09246900BB
*/
public void issue_hall_ticket()
{
}
}
19
SEQUENCE DIAGRAM:
20
1: login 3: fill form 8: logout

applicant admin
4: validation complete 2: display form 7: issue hall ticket
5: criteria validation complete 6: data criteria complete
21
COMPONENT DIAGRAM:
Applicant Exam Registration

System
Admin
DEPLOYMENT DIAGRAM:
Exam Registration
Applicant System
TCP/IP
RESULT:
The UML diagram for Exam registration system was generated.
22
EX NO: 4
DATE:
STOCK MAINTANENCE
AIM:
To represent the stock management system using UML diagrams.The system
consists of three modules namely product supply, product storage and product order.
ALGORITHM:
MODULE 1:
 The supplier gets the list of products required from the warehouses.
 The products are supplied based on the received list.
MODULE 2:
 The warehouses stores the products sent by the supplier.
 The warehouse manager is responsible for the mangement of the products in the
warehouses.
MODULE 3:
 The supermarket sends a product order to the warehouses.
 If the products are available, then the products are delivered to the supermarket.
23
USECASE DIAGRAM:
Provide Products
Supplier
Store Products
Save Product Details
Initiate Product Order
WareHouse
Manager
Super Market
Specify necessary information
Process order
Check Product Availability
Update Stock Inventory
Generate Invoice
Deliver Products
24
ACTIVITY DIAGRAM:
Store Product
Details
Select
Products
Edible Non-Edible
Process
Order
Check
Availability
Update
Inventory
Generate
Invoice
Deliver
Items
25
CLASS DIAGRAM:
CODE:
//Source file: C:\\Program Files\\Rational\\RUPBuilder\\Supplier.java

public class Supplier
{
private int Name;
private int ID;
public WarehouseManager theWarehouseManager;
/**
* @roseuid 4D6F21FC02FD
*/
public Supplier()
{
}
/**
* @roseuid 4D6F208103D8
*/
public void provideProducts()
26
{
}
}
//Source file: C:\\Program Files\\Rational\\RUPBuilder\\WarehouseManager.java
public class WarehouseManager
{
private int name;
public Supplier theSupplier[];
public SuperMarket theSuperMarket;
/**
* @roseuid 4D6F21FC031C
*/
public WarehouseManager() {
}
/**
* @roseuid 4D6F1FFF0128
*/
public void storeProducts() {
}
/**
* @roseuid 4D6F20240261
*/
public void saveProductDetails() {
}
/**
* @roseuid 4D6F200A004E
*/
public void processOrder() {
}
/**
* @roseuid 4D6F204C02DE
*/
public void Deliver() {
}
}
//Source file: C:\\Program Files\\Rational\\RUPBuilder\\SuperMarket.java
public class SuperMarket
{
private int ID;
private int Name;
27
private int Address;

public WarehouseManager theWarehouseManager;
/**
* @roseuid 4D6F21FC033C
*/
public SuperMarket() {
}
/**
* @roseuid 4D6F20BE0290
*/
public void FurnishDetails()
{
}
/**
* @roseuid 4D6F20C40261
*/
public void initiateproductorder()
{
}
}
28
SEQUENCE DIAGRAM:
Supplier WareHouse Super Market Database

Manager
Provide Products
Save Product Details
Initiate Product Order
Specify Necessary Details
Check Product Availability
Process Order
Update Inventory
Deliver Products
1: Provide Products
Supplier WareHouse
Manager
3: Initiate Product Order

4: Specify Necessary Details 2: Save Product Details
5: Check Product Availability
6: Process Order 7: Update Inventory
8: Deliver Products
Super Database
Market
29
COMPONENT DIAGRAM:
Super
Market
Warehouse
Manager
Supplier
DEPLOYMENT DIAGRAM:
Supplier
Ware house
Manager
Super market
STATECHART DIAGRAM:
Product
Order
Selnonedi()
seledi()
Edible Non-Edible
Items Items
Checkavail()
Checkavail()
Process
Order
Update()
Update
Inventory
RESULT: The stock management system was successfully described using UML
diagrams.
30
EXNO:5
DATE:
ONLINE COURSE RESERVATION SYSTEM
AIM:
To generate the UML diagram for course reservation system.
ALGORITHM:
MODULE 1:
 Student logs in.

 Student selects the course.
MODULE 2:
 It is decided whether the student is eligible to take up the course based on certain
criteria.
MODULE 3:
 Student pays for course he selected.

 The payment details are verified.
USECASE DIAGRAM:
31
ACTIVITY DIAGRAM:
CLASS DIAGRAM:
32
CODE GENERATION:
public class Student
public string name;
public string Registernumber;
Public Student()
Public class Reservation
Public Reservation ()
Public class Payment
public String amount;
Public Payment()
Public class CreditPayment extends Payment
33
Public CreditPayment ()
Public class CashPayment extends Payment
Public CashPayment()
public class Course
public string name
public void Course()
Public class subjects
Public String name;
Public void Subjects()
34
SEQUENCE DIAGRAM:
35
Get
Register no
Get cut off
Compare
cuttoff
Add to available
college list
Enter
course
Register
Student
36
COMPONENT DIAGRAM:
DEPLOYEMENT DIAGRAM:
RESULT:
The UML diagram for Course reservation system was generated successfully.
37
EX NO: 6
DATE:
E-TICKETING
AIM:
To generate the UML diagram for E-ticketing.
ALGORITHM:
MODULE 1:
 The user logs into the website using their id and password.
 If the user is a new user, create an id and password by filling the sign up form.
MODULE 2:
 After logging the system displays the form in which the user is allowed to select
the destination and source place.
 The user can also select the date.
 The system displays available trains.
MODULE 3:
 The user can select the required one and give the number of tickets, class.
 The system check for the availability.
 If it is available then book the ticket by filing the details about individuals such as
name, age, gender etc.
MODULE 4:
 Make the payment either by card or through netbanking.

 After booking the ticket, print the ticket.
38
USE CASE DIAGRAM:
Login
Book Ticket
Customer Admin
Make Payment
Bank
Print Ticket
39
ACTIVITY DIAGRAM:
40
CLASS DIAGRAM:
CODE GENERATION
public class customer
{
private string name;
private sring ID;
private int age;
public Authenticate theAuthenticate;
/**
@roseuid 3F0927D0031C
*/
public customer()
{
41
/**
@roseuid 3F09272A01A5
*/
public customer()
{
/**
@roseuid 3F0924600213
*/
public void bookticket()
{
/**
@roseuid 3F09246D0222
*/
public void makepayment()
{
/**
@roseuid 3F09247700EA
*/
public void printticket()
{
}
}
public class Authenticate
{
private string username;
private string password;
public admin theAdmin;
/**
@roseuid 3F0927E10196
*/
public Authenticate()
{
42
/**
@roseuid 3F0924A9009C
*/
public void validate()
{
}
}
public class Bank
{
private string cardno;
public account theAccount[];
/**
@roseuid 3F0927E8004E
*/
public Bank()
{
/**
@roseuid 3F0924D7031C
*/
public void validateno()
{
/**
@roseuid 3F0924E400CB
*/
public void opname2()
{
}
}
public class account
{
private string cust_id;
private string cust_name;
/**
@roseuid 3F092808036B
*/
public account()
43
/**
@roseuid 3F09251100AB
*/
public void withdraw()
{
}
}
public class ticket
{
private string dest;
private string source;
private string time;
private string date;
private string trainname;
public Authenticate theAuthenticate;
public Bank theBank[];
/**
@roseuid 3F09281000EA
*/
public ticket()
{
/**
@roseuid 3F09259C000F
*/
public void book()
{
/**
@roseuid 3F09259F00BB
*/
public void cancel()
{
}
}
public class admin
{
44
/**
@roseuid 3F092835003E
*/
public admin()
{
/**
@roseuid 3F0928150109
*/
public admin()
{
/**
@roseuid 3F09253C0271
*/
public void maintaindatabase()
{
/**
@roseuid 3F092550007D
*/
public void updatedatabase()
{
}
}
/**
void Admin.getdetails(){
*/
45
SEQUENCE DIAGRAM:
LOGIN:
BOOK TICKET:
46
MAKE PAYMENT:
PRINT TICKET:
47
1: enter id and password

customer e-ticketing
4: invalid
2: authenticate
3: valid
admin
48
COMPONENT DIAGRAM:
Customer E-ticketing
Bank
DEPLOYMENT DIAGRAM:
TCP/IP E- ticketing
Customer
RESULT:
The UML diagram for E-ticketing was generated successfully.
49
EXNO:7
DATE:
SOFTWARE PERSONNEL MANAGEMENT SYSTEM
AIM:-
To represent the software personnel management system using UML Diagrams.
The system consists of modules that manage users such as HR and employee to
manipulate various types of details like Personal, Monetary, Leave, etc.
ALGORITHM:
MODULE 1:
 Provide user interface in order to allow the user to enter login details.
 Authenticate the user based on the login details.
 In case the user is not authorized, ask the user to relogin.
MODULE 2:
 Select the type of detail to be viewed or edited.
 The HR can perform actions like add,delete,view and edit details.
 The Employee can only view details.
MODULE 3:
 The changes made by the HR are updated and stored in the database.
 The user logouts.
50
USECASE DIAGRAM:
Login
Authentication
employee
Select type of details System
Insert details
HR
View datails
Modify details
Delete details
Update db
Logout
51
ACTIVITY DIAGRAM:
Login
Authenticate
Yes
Select type of
detail
Personal Monetary Project Details Dept Details Leave Details

Details Details
Privileges Current Projects Projects

Alloted Completed
Actions
Insert Modify View Delete
Update
Database
Logout
52
CLASS DIAGRAM:
CODING:
//Source file: C:\\Program Files\\Rational\\RUPBuilder\\RecordType.java
public class RecordType

{
public CompanySystem theCompanySystem;
/**
* @roseuid 4D6F0B0F0167
*/
public RecordType()
{
53
/**
* @roseuid 4D6E83EC011E
*/
public void insert()
{
/**
* @roseuid 4D6E83F8003E
*/
public void view()
{
/**
* @roseuid 4D6E83FA03A5
*/
public void modify()
{
/**
* @roseuid 4D6E83FD018D
*/
public void delete()
{
}
}
//Source file: C:\\Program Files\\Rational\\RUPBuilder\\CompanySystem.java
public class CompanySystem

{
private int userid;
private int password;
public RecordType theRecordType;
54
/**
*/
public CompanySystem()
{
/**
* @roseuid 4D6E83C5039D
*/
public void authenticate()
{
/**
* @roseuid 4D6E83CB0172
*/
public void update()
{
}
}
//Source file: C:\\Program Files\\Rational\\RUPBuilder\\HR.java
public class HR
{
private int name;
private int id;
/**
*/
public HR()
{
/**
* @roseuid 4D6E838F00F7
*/
55
public void edit()

{
/**
* @roseuid 4D6E83910104
*/
public void view()
{
/**
* @roseuid 4D6E83970280
*/
public void add()
{
/**
* @roseuid 4D6E83990193
*/
public void delete()
{
}
}
//Source file: C:\\Program Files\\Rational\\RUPBuilder\\Employee.java
public class Employee

{
private int name;
private int id;
private int dept;
/**
*/
public Employee()
{
56
/**
* @roseuid 4D6E835E02C5
*/
public void view()
{
}
}
//Source file: C:\\Program Files\\Rational\\RUPBuilder\\DeptDetails.java
public class DeptDetails extends RecordType

{
private int name;
private int id;
private int managerName;
private int projects;
/**
* @roseuid 4D6F0B0F00FA
*/
public DeptDetails()
{
}
}
//Source file: C:\\Program Files\\Rational\\RUPBuilder\\LeaveDetails.java
public class LeaveDetails extends RecordType

{
private int employeeName;
private int leavesAvailed;
private int leavesGranted;
/**
* @roseuid 4D6F0B0F00EA
*/
public LeaveDetails()
{
57
}
}
//Source file: C:\\Program Files\\Rational\\RUPBuilder\\ProjectDetails.java
public class ProjectDetails extends RecordType

{
private int name;
private int dept;
private int manager;
private int id;
private int noofmembers;
private int status;
/**
* @roseuid 4D6F0B0F00BB
*/
public ProjectDetails()
{
}
}
//Source file: C:\\Program Files\\Rational\\RUPBuilder\\MonetaryDetails.java
public class MonetaryDetails extends RecordType

{
private int salary;
private int benefits;
private int bonus;
/**
* @roseuid 4D6F0B0F00AB
*/
public MonetaryDetails()
{
}
}
//Source file: C:\\Program Files\\Rational\\RUPBuilder\\PersonalDetails.java
public class PersonalDetails extends RecordType

{
58
private int name;

private int address;
private int contact;
private int email;
/**
* @roseuid 4D6F0B0F008C
*/
public PersonalDetails()
{
}
}
SEQUENCE DIAGRAM:
Employee System HR
Login
Login
Authenticate Authenticate
Select record type

Select record type
View Record Perform task
Save Task
Update
Logout Logout
59
COLLABRATION DIAGRAM:
HR
Employee 2: Login
5: Select record type
8: View Record 10: Update 4: Authenticate
12: Logout
1: Login
3: Authenticate 6: Select record type
7: Perform task
System 9: Save Task
11: Logout
STATECHART DIAGRAM:
Login
Select Type of
Detail
Select
Action
Insert View Modify Delete
Update db
Logout
60
COMPONENT DIAGRAM:
HR Employee
System System
LAN LAN
Company
Server
DEPLOYMENT DIAGRAM:
HR Employee
LAN LAN
Server
RESULT:
The above module has been designed and verified
61
EX NO:8
DATE:
CREDIT CARD PROCESSING
AIM:
To represent credit card processing in UML notations. It has been dived

into the following three modules.
ALGORITHM:
MODULE 1:
 Choose items from the shop and fill the cart.

 Get the items to the cashier.
MODULE 2:
 Cashier enters item id , quantity in the system.

 Cashier produces bill which gives the total amount with taxes.
MODULE 3:
 Cashier gets the credit card from the customer.

 Cashier swipe the card to get paid for the bill.
 If validated cashier delivers the goods.
62
USE CASE DIAGRAM:
Place Order
Receive Cart
Get Product Details
Update Details
CASHIER
Compute Total
CUSTOMER
Swipe Card
Enter ID
BANK
Validate Card
Get Items
63
ACTIVITY DIAGRAM:
Place Order
Receive Cart
Cart
Get Product
Details
Update Details
Calculate Total
Swipe Card
Enter ID
VALIDATE
Print Bill Reject Card
Bill
Recieve Bill &

Items
64
CLASS DIAGRAM:
CODE:
//Source file: C:\\Program Files\\Rational\\RUPBuilder\\Cashier.java

public class Cashier
{
private int itemid;
private int item;
private int name;
65
/**
* @roseuid 4D6F24920128
*/
public Cashier()
{
}
/**
* @roseuid 4D6F1DAA0242
*/
public void getItems()
{
}
/**
* @roseuid 4D6F1DB9002E
*/
public void enterItems()
{
}
}
SEQUENCE DIAGRAM:
:Customer :Cashier :System :Bank

GiveItems
EnterDetails
GiveBill
GiveCard
Validate
Getvalid_id
DeliverItems
66
1: GiveItems
4: GiveCard
:Customer :Cashier
3: GiveBill
7: DeliverItems
6: Getvalid_id 2: EnterDetails
5: Validate
:Bank
:System
PlaceOrder Updatedeta
ils
SwipeCard
DeliverItem Validate
s
67
COMPONENT DIAGRAM:
Cashier access Bank
DEPLOYMENT DIAGRAM:
paysTo
Custom Cashier
er
validatesFrom
Bank
Server
RESULT:
The above module has been prepared and verified.
68
EX NO: 9
DATE:
E-BOOK MANAGEMENT SYSTEM
AIM:
To generate the UML diagram for e-book management system.
ALGORITHM:
MODULE 1:
 The user logs in.

 The user’s id and password are verified.
MODULE 2:
 The user selects a book.

 The book price information is checked.
MODULE 3:
 The user requests a book.

 The book is searched in the database and availability status is displayed.
 Then user get sign out
69
USECASE DIAGRAM:
enter
user login
manager
browse
select book
book price information
confirmation
book display
sign out
70
ACTIVITY DIAGRAM:
enter the login id

and password
enter the correct login id

verify
and password
select the
book
enter the enter the

book name author name
check
availability
display
book
71
CLASS DIAGRAM:
CODE GENERATION:
Public class customer{
Public customer(){
Void customer.detail(){
Void customer.customer()
Public class login
Private string username;
72
Private int password;
Public login ()
Void login.execute()
Void login.login()
Public class check
Public check()
Void check.availability()
Public class book
Private string bookname;
Public book()
73
Void book.getbookname()
Void book.search()
Void book.book()
Public class manager
Public manager()
Void manager.displaybook()
Void manager.manager()
74
SEQUENCE DIAGRAM:
customer : e web server : server : a

enter
enter the login and password
verift the password
select the book
check the availability
send request to display the book
display the book
COLABORATION DIAGRAM:
1: enter the login ands password

3: select the book
customer : web server :
w a
6: diosplay the book
2: verify the password

5: send request to display the book
4: check availability
server : e
75
STATECHART DIAGRAM:
enter login id and

book request password
request
created
customer request to authorizer
cancel request
valid yes
request no
deleted enter book
name
invalid customer's wants to enter
password
authorizer replies to customer enter author

name
try again authorizer replies to customer
display
book
COMPONENT DIAGRAM:
custome web
r server
dbms
server
76
DEPLOYMENT DIAGRAM:
customer <<ethernet>> webserver
<<ethernet>>
<<ethernet>>
dbms
server
RESULT:
The UML diagram for e-book management system was generated successfully.
77
EX NO: 10
DATE:
RECRUITMENT SYSTEM
AIM:
To generate the UML diagram for recruitment system.
ALGORITHM:
MODULE 1:
 Invigilator collects the CV from all candidates and distributes the self
assessment form.
 He also conducts the aptitude test for all candidates and evaluates
the paper to short-list the candidates for the next level.
MODULE 2:
 Candidates fill the self assessment form and attend the aptitude test.
 The short-listed candidate hops to next level of interview.
MODULE 3:
 Department manager conducts the technical round for the short-listed candidate
and filter some candidate.
 HR manager conducts the HR round and document verification will be done.
 The final candidate gets the offer letter from the HR manager.
78
USECASE DIAGRAM;
Collects the CV
(from Use Case View)
invigilator
Distribute Self assesment form

candidate
Fill Self Assesment form
DM
(from Use Case View) Conducts Aptitude Test
Conducts Technical Round

HR
HR Interview & Document
Verification
Offer Letter
79
ACTIVITY DIAGRAM:
collect cv
distribute self
assessment form
fill the form
conduct aptitute
test
short listing
pass
conduct technical
round
pass
short list
hr interview and document

fail
verification
fail
elligible
pass
fail
offer letter
80
CLASS DIAGRAM:
CODE GENERATION:
Public class invigilator
Public invigilator ()
Void invigilator.collectscv()
Void invigilator.distributeform()
81
Void invigilator.conductsaptitute()
Public class candidate
Private string name;
Private int regno;
Public candidate ()
Void candidate.fillform()
Void candidate.update()
Public class Hrmanager
Public Hrmanager(){
82
Void Hrmanager .documentverification(){
Void Hrmanager .conductsHrinterview(){
Public class departmentmanager
Private string technicalquestion;
Public departmentmanager(){
Void departmentmanager.conductstechnicalround(){
Public class offerletter
Public offerletter()
Void offerletter.issue()
Void offerletter.offerletter()
83
SEQUENCE DIAGRAM:
invigilator Department HR Manager

: candidate
Manager
submit CV
distribute self assessment form

fill self assessment form
conducts aptitude test
short list
shortlisted candidate enters
conducts technical round
short list
shortlisted candidate enters

conducts HR interview and document verification
short list candidates
issue offer letter
84
5: short list
1: submit CV
3: fill self assessment form
invigilator
: candidate 2: distribute self assessment form
4: conducts aptitude test
7: conducts technical round 9: shortlisted candidate enters
10: conducts HR interview and document verification

6: shortlisted candidate enters 12: issue offer letter
11: short list candidates

8: short list
HR Manager
Department
Manager
get cv from candidate
collects cv distribute self conduct shortlist the

assesment form aptitude test candidate
85
COMPONENT DIAGRAM:
candidate invigilator
HR department
manager manager
DEPLOYMENT DIAGRAM:
candidate <<ethernet>> invigilator
<<TCP/IP>>
<<ethernet>> <<ethernet>>
HR <<ethernet>> Department
Manager Manager
RESULT:
The UML diagram for recruitment system was generated successfully.
86
EX NO: 11
DATE:
FOREIGN TRADING SYSTEM
AIM:
To generate UML diagram for foreign management system.
ALGORITHM:
MODULE 1: (user entry for log-in)
Log-in is required in order to exchange money transfer from the bank and update
portfolio information. The old customer enters the exchange system site by entering
the username and password. If the password or username is invalid ,then an error
message is displayed.
MODULE 2: (selection)
After signing in the customer can select particular country and a detailed description
of the equivalent money information is displayed.The customer can also select the
option compare to see the features of different countries money rate.
MODULE 3: (exchange)
The customer inputs the money rate for which equivalent money of the selected country
is transacted to his/her bank account and this is done by providing the credit card number.
MODULE 4: (delivery)
Once the customer enters the necessary details and when the SUBMIT button is
clicked, the acknowledgement is sent and the money is transacted to the respective
bank.
87
CLASS DIAGRAM:
CODE GENERATION:
Public class BankAdmin{
Private string databaseaccess;
Public void addclient(){
Public void deleteclient(){
Public void updateclient(){
88
Public void isvalid(){
Public void portfoliohange()
Public void systemRecovery()
Public void getInfo()
Public class database
Private String accountRecord;
Private String password;
Public void database()
Public void getRecord()
89
Public void setRecord()
Public class client
Private string name;
Private int clientID;
Private string EmailAddress;
Private string password;
Public void client()
Public void changePassword()
Public void changeAddress()
90
Public void creditCardinfo()
Public class transaction
Private int transactionId;
Private Date transactionDate;
Private string transactionStatus;
Public void transaction()
Public void getTransaction()
Public void getClient()
Public void getTransactiomType()
91
Public void isValidtransaction()
Public void transactionDate()
Public class ExchangeService
Private string info;
Public void ExchangeService()
Public void getRequest(){
Public void sendResponse()
{}
92
USE CASE DIAGRAM:
new user registration
customer bank admin
set preference alerts
login/logout
change account info.
account reactivation
place order
manage client account
terminate account
system recovery
update portfolio
analyst
exchange service
retrieve info.
SEQUENCE DIAGRAM:
database bankadmin transaction

: client : exchangeservice
getclient()
getid()
isvalidtransaction()
add client()
delete()
update()
system recovery
changepassword
change address
credit card info
get request()
send response()
8: changepassword
9: change address
database 10: credit card info
bankadmin
4: add client()
: client 5: delete()
6: update()
11: get request() 7: system recovery
12: send response()

1: getclient()
2: getid()
3: isvalidtransaction()
: exchangeservice
transactio
n
ACTIVITY DIAGRAM:
Check user
login
no
yes
registration if allow user to access

not a user and update their info
check with the

exchange service
calculate the amount equivalent in

requested currency
allow transaction if user

account is valid
report the account

transaction to the admin
STATECHART DIAGRAM:
login to
enter
update any info

if required
check info with calcuate the amount eqivalent

exchange service in the required currency
make the amount

transaction
update info to
the admin
COMPONENT DIAGRAM:
DEPLOYMENT DIAGRAM:
Client Web Server

Processor
RESULT:
The above modules for the foreign trading system have been designed and verified.
EX NO: 12
DATE:
CONFERENCE MANAGEMENT SYSTEM
AIM:
To generate the UML diagrams for Conference Management System.
ALGORITHM:
MODULE 1:
 Participant sends the soft copy of the paper to the given email.
 The paper is analyzed by the coordinator and if the paper is selected then the
participant gets intimated.
MODULE 2:
 Participant comes to venue for presenting the paper.
 He registers for the event at front desk and pays the required amount.
MODULE 3:
 Participant presents the paper.
 The Chief Guest asks queries to the participant.
 Participant answers the queries.

USECASE DIAGRAM:
Send the paper
Send Intimation Mail
Coordinator
Register the Name

Participant
Take the Seats
Chief Guest
Address the gathering
Present the papers
Audience
Ask the queries
Answering the queries
Announce the result

ACTIVITY DIAGRAM:
Send Paper
Selection No Reject
Yes
Send Intimation
Register using Register using

name ID
Valid No
Yes
Present the
paper
Answer queries
wait for result

CLASS DIAGRAM:
CODE GENERATION:
public class Coordinator
private String Name;
private String emailID;
public Participant theParticipant[];
/**
* @roseuid 4D58FE8F0399
*/
public Coordinator()
/**
* @return Void
* @roseuid 4D58F8890251
*/
public Void recieve()
return null;
/**
* @return Void
* @roseuid 4D58F88C03B9
*/
public Void select()
return null;
public class Registration
private long ID;
private String Name;
public Participant theParticipant[];
/**
* @roseuid 4D58FE8F03B9
*/
public Registration()
/**
* @return Void
* @roseuid 4D58F8A1004E
*/
public Void register()
return null;
public class Paper
private string Topic;
private time time;

public Participant theParticipant;
public ChiefGuest theChiefGuest;
/**
* @roseuid 4D58FE8F03D8
*/
public Paper()
/**
* @return Void
* @roseuid 4D58F8B400DA
*/
public Void present()
return null;
public class Result
private String Winner;
private string Runner;
public ChiefGuest theChiefGuest;
/**
* @roseuid 4D58FE90001F
*/
public Result()
{
/**
* @return string
* @roseuid 4D58F8DD004E
*/
public string announce()
return null;
SEQUENCE DIAGRAM:
: Participant Regstrtion Paper : ChiefGuest
register()
Send paper()
select()
present()
questionQueries()
answerQueries()
announce()
Regstrtion : ChiefGuest
4: present() 5: questionQueries()
6: answerQueries() 7: announce()
1: register()
Paper
2: Send paper()
3: select()
: Participant
registers in presents answers view the

the venue the paper the queries result
COMPONENT DIAGRAM:
Partici
pant
Registrati
onDB
PaperDB
DEPLOYMENT DIAGRAM:
Particip Coordin
ant TCP/IP
ator
RESULT:
The UML diagram for Conference Management System were generated successfully.
EX NO: 13
DATE:
BPO MANAGEMENT SYSTEM
AIM:
To represent BPO Management System processing in UML notations. It has been

divided into the following three modules.
ALGORITHM:
MODULE 1:
 Customer submits query to the customer care.
MODULE 2:
 Customer care checks whether the query is hardware or software.

 If the query is software the customer care will respond.
 Otherwise the query will be diverted to hardware technician.
MODULE 3:
 The hardware technician will respond to the query.

 Get the details of the customer.
 Update database and terminate the call.
USE CASE DIAGRAM:
Make a Call
Attend Call
Submit Queries
Get Details of Customer
Customer
Customer Care
Divert to Hardware Technician
Response for Software Queries
Response for Hardware Querries

Hardware
Technician
Update Database
Server
end call
ACTIVITY DIAGRAM:
Make A
Call
Attend
Call
Submit
Queries
No If Submit
Queries
Yes
No Divert to Hardware
verify is Software
Technician
problem
Yes
Response to Response to
Software Queries Hardware Queries
Get Details
Enter Enter
Name number
Update
Database
End Call
CLASS DIAGRAM:
CODE GENERATION FOR CLASS DIAGRAM:
//Source file: C:\\Program Files\\Rational\\RUPBuilder\\HardwareTechnician.java

public class HardwareTechnician
{
private int Hquery;
public CustomerCare theCustomerCare;
public HardwareTechnician()
{
}
public void Get_Hquery()
{
}
public void Response_Query()
{
}
}
public class customer
{
private String name;
private String address;
public login theLogin;

public check theCheck;
public customer()
{
}
public Void detail()
{
return null;
}
}
void Customer.Order()
{
}
void Customer.ViewStocks()
{
}
public class Server
{
private int Query;
private int Name;
private int Number;
private int Response;
public CustomerCare theCustomerCare;
public Server()
{
}
public void Update_Database()
{
}
}
SEQUENCE DIAGRAM:
:Customer :Customer Care :Hardware :Server

Technician
Make a Call
Attend Call
Submit Querries
Get Details
Response for Software Queries Divet to Hardware Technician if

Hardware Querries
Response For hardware Queries
Update Details
1: Make a Call
3: Submit Querries
:Customer :Customer
Care
2: Attend Call
4: Get Details
5: Response for Software Queries
8: Update Details
6: Divet to Hardware Technician if Hardware Querries
7: Response For hardware Queries
:Server :Hardware
Technician
Make call
Submit
Queries
Response
Queries
Response to Response to
Hardware queries Software Queries
Get Details
Update
Database
COMPONENT DIAGRAM:
Customer Customer
Care
Server Hardware
Technician
DEPLOYMENT DIAGRAM:
Customer Calls Customer

Care
Details Divert
Hardware
Server Technician
RESULT:
Thus the BPO management system has been implemented successfully.

EX NO:14
DATE:
LIBRARY MANAGEMENGT SYSTEM
AIM:
To generate the UML diagram for library management system
ALGORITHM:
MODULE 1:
 Verify login ID and if correct, provide access to the library database.
MODULE 2:
 Provide a search mechanism to search for a particular book.
 Input the book name and the author’s name.
MODULE 3:
 Get the book details from the database.
 Display the book details on the screen.
MODULE 4:
 Allow the user to select the book for checking out.
 Issue the book.
SEQUENCE DIAGRAM:
CLASS DIAGRAM:
PROGRAM:
Librarian.java
importjava.util.Vector;
public class librarian {
public string name;
private number idnum;
public database updates;

public Vector 1...*;
public void maintaindetails() {

}
}
Database.java
public class database {
public string bookname;
public string authorname;
public librarian updates;
public void updatedetails() {

}
public void maintainmembership() {

}
}
Cashier.java
public class cashier {

public string studentname;
public number membershipidnum;
public Vector mystudent;

/**
*
* @element-type student
*/
public Vector pays;
public void renewmembership() {
}
public void renewbook() {
}
}Student.java
public class student {
public string name;
public number idnum;

public Vector mycashier;
public Vector 1;
public cashier pays;
public void borrowbook() {
}
public void returnbook() {
}
public void fine() {
}
}
USE CASE DIAGRAM:
ACTIVITY DIAGRAM:
STATECHART DIAGRAM:
COMPONENT DIAGRAM:
DEPLOYMENT DIAGRAM:
RESULT:
The UML diagram for library management system was generated successfully.
EX NO: 15
DATE:
STUDENT INFORMATION SYSTEM
AIM
To draw the UML diagrams for the given student information system.
ALGORITHM:
MODULE 1:
 This module enables the authenticated users to record the marks and thereby their
respective grades in a database.
 This is the most important module as it maintains the details of the marks scored by
the students in the database and it is the first and the foremost step in this system.
MODULE 2:
 This module permits the respective users to view their grades as and when necessary
after their identification through their login name and password.
 This module proves to be the simplest as it does not allow the user to modify or
update any information except viewing them.
MODULE 3:
 This module enables the authenticated users to update the marks of the students after
each and every test in order to update the data to the present existing grades of the
students.
 This module just allows the user to modify or update the grades of the students alone
but not their personal details.
 This module does not allow any user just like that only authenticated users are
allowed to update the necessary data after their identification through their login name
and password
USE CASE DIAGRAM:
CLASS DIAGRAM:
PROGRAM:
Admin.java
public class Admin {
public Integer Adminname;
public Integer Adminid;
/**
*
* @element-type Staff
*/
public Vector myStaff;
public Database myDatabase;
public void manageDB() {

}
public void grantPriveleges() {

}
}
Database.java
public class Database {
public Integer id;
public Integer marks;
public Integer attendance;
public String address;
public Integer contact;
public String email;
public Vector myStudent;

public Vector myStaff;
public Vector myAdmin;
}
Staff.java
public class Staff {
public String Staffname;

public Integer Staffid;
public Integer dob;
/**
*
* @element-type Student
*/
public Vector myStudent;
public Database myDatabase;
public Admin myAdmin;
public void createAccount() {

}
public void fillDetails() {

}
public void updateChanges() {

}
}
Student.java
public class Student {
public String name;
public Integer id;
public Integer dob;
public Staff myStaff;

public Vector 1;
public void suggestChanges() {

}
public void viewDetails() {

}
}
ACTIVITY DIAGRAM:
STATE DIAGRAM:
SEQUENCE DIAGRAM
COMPONENT DIAGRAM:
DEPLOYMENT DIAGRAM:
RESULT:
Thus the UML diagrams for student information system is drawn successfully .
EX NO:16
DATE:
PAYROLL SYSTEM
AIM:
To generate the UML diagram for Payroll system.
ALGORITHM:
MODULE 1:
 Enter the employee details name and eno.

 Obtain HRA,DA,PF.
 Get the basic pay as per designation.
MODULE 2:
 Calculate deductions and allowance percentage.

 Calculate the basic pay.
MODULE 3:
 Calculate the number of days taken leave.

 Calculate the deductions due to leave.
 Calculate the net pay after subtracting the net deductions.
 Provide salary slip.
USE CASE DIAGRAM:
Enter details into database
Obtain basic pay as per

designation
Calculate net deductions employee

employer
calculate deductions due to leave
net salary
SEQUENCE DIAGRAM:
employer database salary employee

calculation
Enter employee details
obtain basic pay
obtain hra,da,ta
obtain leave details
calculate salary
store
retrieve net pay
hand over pay slip

1: Enter employee details

database
employer
7: retrieve net pay
5: calculate salary
6: store
8: hand over pay slip 2: obtain basic pay

3: obtain hra,da,ta
4: obtain leave details
salary
calculation
employee
CLASS DIAGRAM:
ACTIVITY DIAGRAM:
provide employee
details
get basic pay as per

designation
calculate net deductions and

allowance percentage
netpay=basic netpay=basic
pay-deductions pay+ (hra,da,pf)
provide salary
COMPONENT DIAGRAM:
DEPLOYMENT DIAGRAM:
Node 1:Registrar
Update
Node 2:PC
Get employee
details
Get basic
pay
Calculate net basic

deductions pay+allowance
Basic Salary
pay-deductions
RESULT:
The above modules for the Payroll System have been designed and verified.
EXNO:17
DATE:
DOMAIN MODEL
AIM:
To generate the Domain Model for course reservation system.
ALGORITHM:
MODULE 1:
 Student logs in.

 Student selects the course.
MODULE 2:
 It is decided whether the student is eligible to take up the course based on certain
criteria.
MODULE 3:
 Student pays for course he selected.

 The payment details are verified.
CLASS DIAGRAM:
reservation course
Student
+regno:Integer +regno:integer +vacany:integer
+name:String +vacany:integer +coursed:integer
+address:String +check_vacancy() +fee:integer
+phone:String +check_validuser()
+emailID:String
+dateofbirth:Date
+Fathersname:string payment
subject
+fee:integer
+sname:string
+total:integer
+generatebill() +display_contents()
Credit payment Cash payment

CODE GENERATION:
public class Student
public string name;
public string Registernumber;
Public Student()
{ }
Public class Reservation
Public Reservation ()
{ }
Public class Payment
public String amount;
Public Payment()
{ }
Public class CreditPayment extends Payment
Public CreditPayment ()
{ }
Public class CashPayment extends Payment
Public CashPayment()
{ }
public class Course
public string name
public void Course()
{ }
Public class subjects
Public String name;
Public void Subjects()
{ }
DOMAIN MODEL:
Student
Name Reservation Course
RegisterNo RegisterNo CourseId
Dob
EmailId
Phone
Address
Father’s name Payment Subject
Amount Name
Credit payment Cash payment

CONCEPTUAL CLASSES
1. student
Student
+regno:Integer
+name:String
+address:String
+phone:String
+emailID:String
+dateofbirth:Date
+Fathersname:string
2.reservation
reservation
+regno:integer
+vacany:integer
+check_vacancy()
+check_validuser()
3. course
Course
+vacany:integer
+coursed:integer
+fee:integer
4. payment
Payment
+fee:integer
+total:integer
+generatebill()
5. subject
Subject
+sname:string
+display_contents()
RESULT:
The Domain for Course reservation system was generated successfully.

EX NO: 18
DATE:
LOGICAL ARCHITECTURE
AIM
To draw the logical architecture of conference management system.
ALGORITHM:
MODULE 1:
 Provide user interface in order to allow the user to upload their paper and reference
details.
 Authenticate the user based on the registration details.
 In case the user is not authorized, ask the user to re-submit the paper with all
credentials.
MODULE 2:
 The paper management can perform actions like

 Receiving paper submissions (PDF upload, collection of bibliographic metadata)
 Collecting reviewers' topic preferences
 Assigning reviewers to papers
 Collecting reviews
 Sharing reviews among the program committee
 Providing a per-submission discussion forum for the reviewers
 Ranking reviews and setting acceptance threshold
 Reporting reviewers' comments and program committee decision to authors
 Creating a conference website and program
 Registering attendees
 Publishing proceedings
 The user will be receiving the notifications or intimations.
MODULE 3:
 The selected papers are updated and stored in the database for presentation.
 The selected user attends the conference.
LOGICAL ARCHITECTURE:
USER INTERFACE:
DOMAIN LAYER:
TECHNICAL SERVICE LAYAER:
RESULT:
The above logical architecture is constructed successfully.

Passport Automation System

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Passport Automation System

Diunggah oleh

Hak Cipta:

Format Tersedia

WWW.VIDYARTHIPLUS.

PASSPORT AUTOMATION SYSTEM

To generate the UML diagram for online passport verification system.

 Provide a user interface for getting the user’s login details.

 If a new user enters,provide a registration.

 Process the application.

Public class Passportautomatonsystem

Public class Applicationstatus

Public string applicantid;

Public class Newregistrationsystem

Public string name;

Public string dob;

Public string fname;

Public string foccupation;

Public string address;

STATE CHART DIAGRAM:

Enter login Verify Grant

Validate Process the

Applicant Passport verification

USE CASE DIAGRAM:

Data Entry Querying

Enter Login Details

Grant Permission/ Deny

Enter Login Details

Enter Book name

Enter author name

Check the book

9: Enter author name

4: Enter Login Details3: Grant Permission/ Deny

Enter login Verify Grant

Issue the Display the

Enter author Display the

Check out the

Client Web Server

EXAM REGISTRATION SYSTEM

To generate the UML diagram for Exam registration system.

 The system gets the application registration form.

USE CASE DIAGRAM:

public class applicant

public void fill_form(){

STATE CHART DIAGRAM:

1: login 3: fill form 8: logout

4: validation complete 2: display form 7: issue hall ticket

5: criteria validation complete 6: data criteria complete

Applicant Exam Registration

The UML diagram for Exam registration system was generated.

To represent the stock management system using UML diagrams.The system

 The products are supplied based on the received list.

 The warehouses stores the products sent by the supplier.

 The supermarket sends a product order to the warehouses.

Save Product Details

Initiate Product Order

Check Product Availability

Update Stock Inventory

//Source file: C:\\Program Files\\Rational\\RUPBuilder\\Supplier.java

private int Address;

Supplier WareHouse Super Market Database

Save Product Details

Initiate Product Order

Specify Necessary Details

Check Product Availability

3: Initiate Product Order