PERI INSTITUTE OF TECHNOLOGY

MANNIVAKKAM, CHENNAI – 600 048

AFFILIATED TO ANNA UNIVERSITY, CHENNAI

DEPARTMENT OF COMPUTER SCIENCE AND

ENGINEERING

CCS356–OBJECT ORIENRED SOFTWARE ENGINEERING

LABORATORY

NAME :

REG NO :

YEAR :

SEMESTER :

BRANCH :
 PERI INSTITUTE OF TECHNOLOGY
MANNIVAKKAM, CHENNAI – 600 048

AFFILIATED TO ANNA UNIVERSITY, CHENNAI

BONAFIDE
CERTIFICATE

This is a certified Bonafide Record Work of Mr./Ms.

Register No. submitted for the Anna University Practical
Examination held on in CCS356 –OBJECT ORIENTED
SOFTWARE ENGINEERING LABORATORY during the year 2023-2024.

Signature of the Lab In-charge Head of the Department

Internal Examiner External Examiner

Date
 PERI INSTITUTE OF TECHNOLOGY

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

VISION AND MISSION OF THE INSTITUTION

VISION
• To be an internationally recognized seat of higher learning in Engineering, Technology &
Science in future.
• It also visualizes being a research incubator for academicians, industrialists and researchers
from across the country/world.

MISSION
• It strives to provide quality technical education at affordable cost.
• Providing state-of-the-art infrastructure facilities to achieve excellence in teaching
learning, Research & Development.
• Aligning with leading industries to create competent engineers through internships and
placement focused training.
• Create an environment which is conducive to learn skills which will solve pressing issues
along with foundation in moral values and ethics.

VISION AND MISSION OF THE DEPARTMENT

VISION

The vision of the department is to prepare industry-ready competent professionals with moral
values by imparting scientific knowledge and skill-based education.
MISSION
• To provide exposure of latest tools and technologies in the broad area of computing.
• To promote research-based projects / activities in the emerging areas of technology.
• To enhance Industry Institute Interaction program to get acquainted with corporate
culture and to develop entrepreneurship skills
• To induce ethical values and spirit of social commitment.
 PROGRAM EDUCATIONAL OBJECTIVES (PEOs)

PEO1: To enable graduates to pursue higher education and research, or a successful career in
industries associated with Computer Science and Engineering, or as entrepreneurs.
PEO2: To ensure that graduates will have the ability and attitude to adapt to emerging
technological changes.
PEO3: To exhibit professional attitude, teamwork and practice code of ethics in the area of
specialization.

PROGRAM OUTCOMES (POs)

1. Engineering knowledge: Apply the knowledge of Mathematics, Science, Engineering

fundamentals, and an engineering specialization to the solution of complex engineering problems.
2. Problem analysis: Identify, formulate, review research literature, and analyze complex
engineering problems reaching substantiated conclusions using first principles of Mathematics,
Natural Sciences, and Engineering Sciences.
3. Design/development of solutions: Design solutions for complex engineering problems and
design system components or processes that meet the specified needs with appropriate
consideration for the public health and safety, and the cultural, societal, and environmental
considerations.
4. Conduct investigations of complex problems: Use research-based knowledge and research
methods including design of experiments, analysis and interpretation of data, and synthesis of the
information to provide valid conclusions.
5. Modern tool usage: Create, select, and apply appropriate techniques, resources, andmodern
engineering and IT tools including prediction and modeling to complex engineering activities
with an understanding of the limitations.
6. The engineer and society: Apply reasoning informed by the contextual knowledge to assess
societal, health, safety, legal and cultural issues and the consequent responsibilities relevant to
 the professional engineering practice.

7. Environment and sustainability: Understand the impact of the professional engineering

solutions in societal and environmental contexts, and demonstrate the knowledge of, and need for
sustainable development.
8. Ethics: Apply ethical principles and commit to professional ethics and responsibilities and norms
of the engineering practice.
9. Individual and team work: Function effectively as an individual, and as a member or leader in
diverse teams, and in multidisciplinary settings.
10. Communication: Communicate effectively on complex engineering activities with the
engineering community and with society at large, such as, being able to comprehend and write
effective reports and design documentation, make effective presentations, and give and receive
clear instructions.
11. Project management and finance: Demonstrate knowledge and understanding of the
engineering and management principles and apply these to one’s own work, as a member and
leader in a team, to manage projects and in multidisciplinary environments.
12. Life-long learning: Recognize the need for, and have the preparation and ability to engage
independent and life-long learning in the broadest context of technological change.

PROGRAMME SPECIFIC OUTCOMES (PSOs)

1. To analyze, design and develop computing solutions by applying foundational concepts

of Computer Science and Engineering.
2. To apply software engineering principles and practices for developing quality software for
scientific and business applications
3. To adapt to emerging Information and Communication Technologies (ICT) to innovate ideas
and solutions to existing/novel problems.
 TABLE OF CONTENT

S.NO. DATE EXPERIMENT TITLE PAGE NO MARKS SIGN.

1 Passport automation system

2 Book bank

3 Exam Registration

4 Stock maintenance system

5 Online course reservation system

6 Airline/Railway reservation system

7 Software personnel management system

8 Credit card processing

9 E-book management system

10 Recruitment system

11 Foreign trading system

12 Conference Management System

13 BPO Management System

14 Library management system

15 Student information system

16 ATM Management System

EX. NO: 1
DATE:

PASSPORT AUTOMATION SYSTEM

AIM:

To develop mini project on Passport Automation System using Argo UML.

HARDWARE REQUIREMENTS:

Intel Pentium Processor 3

SOFTWARE REQUIREMENTS:
Argo UML

PROBLEM STATEMENT:
This system is mainly designed to have ease issue of passport and renewal without direct
intervention of human.

USE CASE DIAGRAM:

This diagram will contain the actors, use cases which are given below
Actors:Applicant, passportofficer, postofficer
Use cases: Fill form, Validation, Appointment, Verification, Enquiry and Passport issue.

ACTIVITY DIAGRAM:
This diagram will have the activities, start point, end point, and decision boxes. It
describes the flow of activities of the system under design.

CLASS DIAGRAM:
This diagram consists of the following classes, attributes, and their operations namely
Passport officer, Applicant and Central system.

SEQUENCE DIAGRAM:
This Diagram consists of the objects, messages, and Return messages.
Objects: Applicant, Passport officer and Centralized computer

COLLABORATION DIAGRAM
This diagram contains the objects and actors. It also shows the interaction between the
object via messages using a single link.
PACKAGE DIAGRAM

A package diagram is represented as a folder shown as a large rectangle with a top attached to its
upper left corner. A package may contain both sub ordinate package and ordinary model elements.
All uml models and diagrams are organized into package. A package diagram in unified modeling
language that depicts the dependencies between the packages that make up a model. A Package
Diagram (PD) shows a grouping of elements in the OO model, and is a Cradleextension to UML.
PDs can be used to show groups of classes in Class Diagrams (CDs), groups of components or
processes in Component Diagrams (CPDs), or groups of processors in Deployment Diagrams
(DPDs).
There are three types of layer. They are

o User interface layer

o Domain layer

o Technical services layer

COMPONENT DIAGRAM

The component diagram's main purpose is to show the structural relationships between the
components of a system. It is represented by boxed figure. Dependencies are represented by
communication association

DEPLOYMENT DIAGRAM

A deployment diagram in the unified modeling language serves to model the physical deployment
of artifacts on deployment targets. Deployment diagrams show "the allocation of artifacts to nodes
according to the Deployments defined between them. It is represented by 3- dimentional box.
Dependencies are represented by communication association.
USE CASE DIAGRAM:

SEQUENCE DIAGRAM
ACTIVITY DIAGRAM:

COLLABORATION DIAGRAM:
STATE CHART DIAGRAM:

CLASS DIAGRAM:
PACKAGE DIAGRAM

COMPONENT DIAGRAM
DEPLOYMENT DIAGRAM

MERITS:

• Provides Convenience
• Easy usage

DEMERITS:

• May cause calculation errors

• Result publishing problem

CODE:
APPLICANT
public class applicant {

public Integer name;

public Integer address;

public Integer appno;

public passport officer mypassport officer;

public void apply() {

}

public void applicant() {

}

CENTRAL SYSTEM
public class central system {
public Integer name;

public Integer proofs;

public void rejects() {

}

public void issue() {

}

public void control system() {

}

}
PASSPORT OFFICER
public class passport officer {

public Integer name;

public string address;

public Integer newAttr;

public central system mycentral system;

public void verify() {

}

public void provide() {

}

public void passport officer() {

}

RESULT:
Thus the mini project for Passport Automation System was developed using Argo UML and
executed successfully.
EX. NO: 2
DATE:

BOOK BANK

AIM:
To develop mini project on Book Bank using Argo UML.

HARDWARE REQUIREMENTS:
Intel Pentium Processor 3

SOFTWARE REQUIREMENTS:
Argo UML

PROBLEM STATEMENT:
It is mainly designed for supporting to computerize the book bank system to have easy
access to books among students.

USE CASE DIAGRAM:

This diagram will contain the actors, use cases which are given below
Actors: Student, Issuer.
Use cases: login, student registration, issue of books and payment.

ACTIVITY DIAGRAM:
This diagram will have the activities, start point, end point, and decision boxes. It
describes the flow of activities of the system under design.

CLASS DIAGRAM:
This diagram consists of the following classes, attributes, and their operations namely,
Student, Central Database and Incharge/Issuer.

SEQUENCE DIAGRAM:

This diagram consists of the objects, messages, and Return messages

Objects: Student, Issuer/Incharge, Centralized computer.

COLLABORATION DIAGRAM

This diagram contains the objects and actors. It also shows the interaction between the
object via messages using a single link
PACKAGE DIAGRAM

A package diagram is represented as a folder shown as a large rectangle with a top attached to its
upper left corner. A package may contain both sub ordinate package and ordinary model elements.
All uml models and diagrams are organized into package. A package diagram in unified modeling
language that depicts the dependencies between the packages that make up a model. A Package
Diagram (PD) shows a grouping of elements in the OO model, and is a Cradleextension to UML.
PDs can be used to show groups of classes in Class Diagrams (CDs), groups of components or
processes in Component Diagrams (CPDs), or groups of processors in Deployment Diagrams
(DPDs).
There are three types of layer. They are

o User interface layer

o Domain layer

o Technical services layer

COMPONENT DIAGRAM

The component diagram's main purpose is to show the structural relationships between the
components of a system. It is represented by boxed figure. Dependencies are represented by
communication association.

DEPLOYMENT DIAGRAM

A deployment diagram in the unified modeling language serves to model the physical deployment
of artifacts on deployment targets. Deployment diagrams show "the allocation of artifacts to nodes
according to the Deployments defined between them. It is represented by 3- dimentional box.
Dependencies are represented by communication association.
USE CASE DIAGRAM:

STATE CHART DIAGRAM:

SEQUENCE DIAGRAM:

COLLABORATION DIAGRAM:
ACTIVITY DIAGRAM:

PACKAGE DIAGRAM
CLASS DIAGRAM:

DEPLOYMENT DIAGRAM
 COMPONENT DIAGRAM

MERITS:
Provides Convenience
Easy usage
User Friendliness

DEMERITS:
Need Computer Knowledge

CODE:
BOOK
import java.util.Vector;

public class book{

public Integer accno;

private string author;

public string title;

public string edition;

public Integer price;

public Integer purchase price;

public Integer reference;

public Integer newAttr;

public RETURN myRETURN;

public Vector 1;

public void viewbookdetails() {

}

public void addbookinfo() {

}

public void deletebookinfo() {

}

public void modifybookinfo() {

}

}
ISSUE
import java.util.Vector;

public class ISSUE {

public Integer issueid;

public Integer issuedate;

public Integer accno;

public string title;

public Integer enrollno;

public string name;

public string dept;

public string batch;

public STUDENT mySTUDENT;

public Vector 1;

public void bookissue() {

}

public void modifyissueinfo() {

}

RETURN
import java.util.Vector;
public class RETURN {

public Integer returnid;

public Integer returndate;

public Integer accno;

public string title;

public Integer enrollno;

public string name;

public string dept;

private Integer string;

public Vector myBOOK;

public Vector 1;

public void bookreturn() {

}

public void modifyreturninfo() {

}

STUDENT
import java.util.Vector;

public class STUDENT {

public string name;

public Integer dob;

public string address;

public string state;

public Integer pincode;

public string deptname;

public Integer batchid;

public Vector myISSUE;

public Vector myRETURN;
 public void addinfo() {
}

public void deleteinfo() {

}

public void modifyinfo() {

}

RESULT:
Thus the mini project for Book Bank developed using Argo UML and executed
successfully.
EX. NO: 3
DATE:
EXAM REGISTRATION

AIM:
To develop mini project on Exam Registration using Argo UML.

HARDWARE REQUIREMENTS:
Intel Pentium Processor 3

SOFTWARE REQUIREMENTS:
Argo UML

PROBLEM STATEMENT:
This system is designed to allow quick access to student information, registration for
examination, payment details, no-due details and finally issue of hall ticket.

USE CASE DIAGRAM:

This diagram will contain the actors, use cases which are given below
Actors: Student, Officer, Central System.
Use cases: Student details, verification, issue of hall ticket.

ACTIVITY DIAGRAM:
This diagram will have the activities, start point, end point, and decision boxes. It
describes the flow of activities of the system under design.

CLASS DIAGRAM:
This diagram consists of the following classes, attributes, and their operations namely
Applicant, Manager, and Database.

SEQUENCE DIAGRAM:
This diagram consists of the objects, messages, and return messages
Objects: Student, Officer, Central System.

COLLABORATION DIAGRAM
This diagram contains the objects and actors. It also shows the interaction between the
object via messages using a single link

COMPONENT DIAGRAM

The component diagram's main purpose is to show the structural relationships between the
components of a system. It is represented by boxed figure. Dependencies are represented by
communication association
DEPLOYMENT DIAGRAM

A deployment diagram in the unified modeling language serves to model the physical deployment
of artifacts on deployment targets. Deployment diagrams show "the allocation of artifacts to nodes
according to the Deployments defined between them. It is represented by 3- dimentional box.
Dependencies are represented by communication association.

PACKAGE DIAGRAM

A package diagram in unified modeling language that depicts the dependencies between the
packages that make up a model. A Package Diagram (PD) shows a grouping of elements in the
OO model, and is a Cradle extension to UML. PDs can be used to show groups of classes in
Class Diagrams (CDs), groups of components or processes in Component Diagrams (CPDs), or
groups of processors in Deployment Diagrams (DPDs).

There are three types of layer. They are

o User interface layer

o Domain layer

o Technical services layer

USECASEDIAGRAM:
SEQUENCE DIAGRAM:

COLLABORATIONDIAGARM:
ACTIVITY DIAGRAM:

STATE DIAGRAM:
CLASS DIAGARM:

COMPONENT DIAGRAM:
PACKETDIAGRAM:

DEPLOYMENT DIAGRAM:

MERITS:
Provides Convenience
Easy usage
User Friendliness

DEMERITS:
Need Computer Knowledge
 CODE:

DATABASE
public class database {

public Integer applicantno;

public string coursedetails;

public void string() {

}

public void store() {

}

public void database() {

}

INCHARGE
public class incharge extends database {

private string coursedetails;

public Integer applicantno;

public void manager() {

}

public void issuehallticket() {

}

STUDENT
public class student extends incharge {

public Integer regnum;

public char name;

public Integer dob;

public Integer mobilenum;

public void student() {

}
 public void payment() {
}

public void course() {

}

RESULT:
Thus the mini project for Exam Registration System was developed using Argo UML and
executed successfully.
EX. NO: 4
DATE:
STOCK MAINTENANCE SYSTEM.

AIM:
To develop mini project on Stock Maintenance System using Argo UML.

HARDWARE REQUIREMENTS:
Intel Pentium Processor 3

SOFTWARE REQUIREMENTS:
Argo UML

PROBLEM STATEMENT:
The main objective of the project is to monitor the stocks of an enterprise. It includes
checking of stock list, details of a product, placing new order, enquiry about the product,payment
and updation of clearance.

USE CASE DIAGRAM:

This diagram will contain the actors, use cases which are given below
Actors: customer, inventory System, central computer.
Use cases: place order, check order details, enquiry

ACTIVITY DIAGRAM:
This diagram will have the activities, start point, end point, and decision boxes. Itdescribes
the flow of activities of the system under design.

CLASS DIAGRAM:
This diagram consists of the following classes, attributes, and their operations namely
Customer, Central computer and inventory machine system.

SEQUENCE DIAGRAM:
This Diagram consists of the objects, messages, and Return messages
Objects: customer, inventory system, Centralized computer

COLLABORATION DIAGRAM
This diagram contains the objects and actors. It also shows the interaction between the
object via messages using a single link

COMPONENT DIAGRAM

The component diagram's main purpose is to show the structural relationships between the
components of a system. It is represented by boxed figure. Dependencies are represented by
communication association
DEPLOYMENT DIAGRAM

A deployment diagram in the unified modeling language serves to model the physical deployment
of artifacts on deployment targets. Deployment diagrams show "the allocation of artifacts to nodes
according to the Deployments defined between them. It is represented by 3- dimentional box.
Dependencies are represented by communication association.

PACKAGE DIAGRAM

A package diagram in unified modeling language that depicts the dependencies between the
packages that make up a model. A Package Diagram (PD) shows a grouping of elements in the
OO model, and is a Cradle extension to UML. PDs can be used to show groups of classes in
Class Diagrams (CDs), groups of components or processes in Component Diagrams (CPDs), or
groups of processors in Deployment Diagrams (DPDs).

There are three types of layer. They are

o User interface layer

o Domain layer

o Technical services layer

USECASEDIAGRAM:
SEQUENCE DIAGRAM:

COLLABORATIONDIAGARM:
ACTIVITY DIAGRAM:

STATE DIAGRAM:
CLASS DIAGARM:

COMPONENT DIAGRAM:
PACKETDIAGRAM:

DEPLOYMENT DIAGRAM:
 MERITS:
Provides Convenience
Easy usage
User Friendliness

DEMERITS:
Need Computer Knowledge

CODE:
CENTRAL SYSTEM
public class centralsystem {

public string availability;

public Integer stock;

public void check() {

}

public void clear() {

}

public void centralsyatem() {

}

}
DEALER
import java.util.Vector;

public class dealer {

public string name;

public Integer phonenum;

public float payment;

public Vector 11;

public void sumbit() {

}

public void pay() {

}

public void dealer() {

}
}
SUPERVISOR

import java.util.Vector;

public class supervisor {

public string productinfo;

public Integer stock;

public Vector 1;

public void update() {

}

public void supervisor() {

}

RESULT:
Thus the mini project for Stock Maintenance System was developed using Argo UML
and executed successfully.
EX. NO: 5
DATE:

ONLINE COURSE RESERVATION SYSTEM

AIM:
To develop mini project on Online Course Reservation System using Argo UML.

HARDWARE REQUIREMENTS:
Intel Pentium Processor 3

SOFTWARE REQUIREMENTS:
Argo UML

PROBLEM STATEMENT:
This project is designed for supporting to computerize the course reservation. In this, the
reservation, cancellation of the tickets is done. For the reservation/cancellation we must fill the
form and it will be given to the operator and they will check the reservation/cancellation and
confirms the place or amount return.

USECASE DIAGRAM:
This diagram will contain the actors, use cases which are given below
Actors: Students, Course Reservation System
Use case: Status, Reservation, Cancellation and Central Computer.

ACTIVITY DIAGRAM:
This diagram will have the activities, start point, end point, and decision boxes. Itdescribes
the flow of activities of the system under design.

CLASS DIAGRAM:
This diagram consists of the following classes, attributes, and their operations namely
Central Computer, Student and Course Management system.

SEQUENCE DIAGRAM:
This diagram consists of the objects and actors from the use case diagram
Objects: Student, Course reservation system and central computer.

COLLABORATION DIAGRAM:
This diagram contains the objects and actors. It also shows the interaction between the
object via messages using a single link.

PACKAGE DIAGRAM:
A kind of structural diagram ,shows arrangement and organization of model elements
In middle to large scale project.
USECASE DIAGRAM:

STATE DIAGRAM:
SEQUENCE DIAGRAM:

PACKAGE DIAGRAM:
DEPLOYMENT DIAGRAM:

COMPONENT DIAGRAM:

COLLABORATION DIAGRAM:
ACTIVITY DIAGRAM:

CLASS DIAGRAM:
MERITS:
Provides Convenience
Easy usage
User Friendliness

DEMERITS:
Need Computer Knowledge

CODING:
CMS

public class CMS {

public Integer studentinfo;

public Integer staffinfo;

public course manager mycourse manager;

public void verify() {

}

public void seatfees() {

}

}
COURSE MANAGER

public class course manager {

public Integer name;

public Integer id;

public void confirmed() {

}

public void update() {

}

public void reject() {

}

}
STUDENT

public class student {

public Integer name;

public Integer address;

public CMS 0..*;

public void sumbit() {

}

public void payment() {

}

RESULT:
Thus the mini project for Online Course Reservation System was developed using Argo
UML and executed successfully.
EX. NO: 6
DATE:

AIRLINE/RAILWAY RESERVATION SYSTEM

AIM:

To develop mini project on E-ticketing using Argo UML.

HARDWARE REQUIREMENTS:

Intel Pentium Processor 3

SOFTWARE REQUIREMENTS:

Argo UML

PROBLEM STATEMENT:

This project is designed for supporting to computerize the railway reservation. In this, the
reservation, cancellation of the tickets is done. For the reservation/cancellation we must fill the
form and it will be given to the operator and they will check the reservation/cancellation and
confirms the place or amount return.

USECASE DIAGRAM:

This diagram will contain the actors, use cases which are given below
Actors: Passengers, Railway Reservation System.
Use case: Status, Reservation, Cancellation and Central Computer.

ACTIVITY DIAGRAM:

This diagram will have the activities, start point, end point, and decision boxes. Itdescribes
the flow of activities of the system under design.

CLASS DIAGRAM:
This diagram consists of the following classes, attributes, and their operations namely
Central computer, passenger, railway management system.

SEQUENCE DIAGRAM:

This diagram consists of the objects and actors from the usecase diagram
Objects: Passenger, railway reservation system and central computer

COLLABORATION DIAGRAM:

This diagram contains the objects and actors. It also shows the interaction between the
object via messages using a single link

PACKAGE DIAGRAM:
A kind of structural diagram shows arrangement and organization of model elements
In middle to large scale project.

USECASE DIAGRAM:
ACTIVITY DIAGRAM:

STATE CHART:
COLLABORATION DIAGRAM:

SEQUENCE DIAGRAM:
COMPONENT DIAGRAM:

DEPLOYMENT DIAGRAM:
PACKAGE DIAGRAM:

CLASS DIAGRAM:
 MERITS:
Provides Convenience
Easy usage
User Friendliness

DEMERITS:
Need Computer Knowledge

CODE:
CMS
import java.util.Vector;

public class CMS {

public Integer db_no;

public Integer traino;

/**
*
* @element-type TRAVELLER
*/
public Vector myTRAVELLER;
public INCHARGE myINCHARGE;

public void checkpayment() {

}

}
INCHARGE
public class INCHARGE {

public Integer id;

public Integer cost;

public CMS myCMS;

public void checkpayment() {

}

public void issuseticket() {

}

}
 TRAVELLER
public class TRAVELLER {

public string name;

public Integer age;

public CMS myCMS;

public void checkavailability() {

}

RESULT:
Thus the mini project for Software Personnel Management System was developed using
Argo UML and executed successfully.
EX. NO: 7
DATE:
SOFTWARE PERSONNEL MANAGEMENT SYSTEM

AIM:
To develop mini project on Software Personnel Management System using Argo
UML.

HARDWARE REQUIREMENTS:
Intel Pentium Processor 3

SOFTWARE REQUIREMENTS:
Argo UML

PROBLEM STATEMENT:

This project is mainly designed to maintain details about the employee working in
software or any company. It includes entire database of the person involved in an
organization.

USE CASE DIAGRAM:

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

Actors: Employee, HR

Use cases: login, employee details, designation, period of service, experience etc.

ACTIVITY DIAGRAM:

This diagram will have the activities, start point, end point, and decision boxes. It
describes the flow of activities of the system under design.

CLASS DIAGRAM:

This diagram consists of the following classes, attributes, and their operations
namely,

Employee, HR, Central management system.

SEQUENCE DIAGRAM:

This Diagram consists of the objects, messages, and Return messages

Objects: Employee, HR, Central management system.

COLLABORATION DIAGRAM

This diagram contains the objects and actors. It also shows the interaction between
the object via messages using a single link

COMPONENT DIAGRAM
The component diagram's main purpose is to show the structural relationships between the
components of a system. It is represented by boxed figure. Dependencies are represented by
communication association

DEPLOYMENT DIAGRAM
A deployment diagram in the unified modeling language serves to model the physical
deployment of artifacts on deployment targets. Deployment diagrams show "the allocation of
artifacts to nodes according to the Deployments defined between them. It is represented by 3-
dimentional box. Dependencies are represented by communication association.

PACKAGE DIAGRAM
A package diagram in unified modeling language that depicts the dependencies between the
packages that make up a model. A Package Diagram (PD) shows a grouping of elements in the
OO model, and is a Cradle extension to UML. PDs can be used to show groups of classesin
Class Diagrams (CDs), groups of components or processes in Component Diagrams(CPDs),
or groups of processors in Deployment Diagrams (DPDs).
There are three types of layer. They are

User interface layer

Domain layer

Technical services layer

USECASE DIAGRAM:

SEQUENCE DIAGRAM:
COLLABORATION DIAGRAM:

STATE CHART DIAGRAM:

PACKAGE DIAGRAM:

DEPLOYMENT DIAGRAM:
ACTIVITY DIAGRAM:
COMPONENT DIAGRAM:

CLASS DIAGRAM:
 MERITS:
Provides Convenience
Easy usage

DEMERITS:
May cause calculation errors
Result publishing problem
CODE:
CMS
public class CMS {

public string empdetails;

public Integer salary;

public HR myHR;

public void update() {

}

}
EMPLOYEE
public class employee {

public string name;

public Integer id;

private Integer string;

public HR myHR;

public void sumbit() {

}

}
HR
public class HR {

public string name;

private string details;

public employee myemployee;

public CMS myCMS;

public void update() {

}
}

RESULT:
Thus the mini project for Software personnal management System was developed using
Argo UML and executed successfully.
EX. NO: 8
DATE:
CREDIT CARD PROCESSING

AIM:
To develop mini project on Credit Card Processing System using Argo UML.

HARDWARE REQUIREMENTS:
Intel Pentium Processor 3

SOFTWARE REQUIREMENTS:
Argo UML

PROBLEM STATEMENT:
This project is designed to ease the use of credit card which consists of issue of card to
customer, perform online purchase of item by customer and amount settled using the card.

USE CASE DIAGRAM:

This diagram will contain the actors, use cases which are given below
Actors: Cardholder, Incharge, Manager.

Use cases: Apply for new card, issue of card, purchase of item, verification of credit limit and
settlement of amount via card.

ACTIVITY DIAGRAM:
This diagram will have the activities, start point, end point, and decision boxes. It
describes the flow of activities of the system under design.

CLASS DIAGRAM:
This diagram consists of the following classes, attributes, and their operations
Applicant, Banker, Cashier, Central Management System.

SEQUENCE DIAGRAM:
This diagram consists of the objects, messages, and Return messages.
Objects: Applicant, Banker, Cashier, Central management system.

COLLABORATION DIAGRAM
This diagram contains the objects and actors. It also shows the interaction between
the object via messages using a single link

COMPONENT DIAGRAM
The component diagram's main purpose is to show the structural relationships between the
components of a system. It is represented by boxed figure. Dependencies are represented by
communication association
DEPLOYMENT DIAGRAM
A deployment diagram in the unified modeling language serves to model the physical
deployment of artifacts on deployment targets. Deployment diagrams show "the allocation of
artifacts to nodes according to the Deployments defined between them. It is represented by 3-
dimentional box. Dependencies are represented by communication association.

PACKAGE DIAGRAM
A package diagram in unified modeling language that depicts the dependencies between the
packages that make up a model. A Package Diagram (PD) shows a grouping of elements in the
OO model, and is a Cradle extension to UML. PDs can be used to show groups of classesin
Class Diagrams (CDs), groups of components or processes in Component Diagrams(CPDs),
or groups of processors in Deployment Diagrams (DPDs).
There are three types of layer. They are

User interface layer

Domain layer

Technical services layer

CLASS DIAGRAM:
PACKAGE DIAGRAM:

STATE CHART DIAGRAM:

SEQUENCE DIAGRAM:

COMPONENT DIAGRAM:
USECASE DIAGRAM
ACTIVITY DIAGRAM:
COLLABORATION DIAGRAM:
 DEPLOYMENT DIAGRAM:

MERITS:
provides convenience
easy usage

DEMERITS:
may cause calculation errors
result publishing problem

CODE:
APPLICANT
import java.util.Vector;

public class applicant {

public char name;

public char details;

public Vector mycashier;

public Vector mybanker;

public void sumbit() {

}

public void pay() {

}

}
 BANKER
import java.util.Vector;

public class banker {

public char details;

public int cardno;

public Vector myapplicant;

public void verify() {

}

public void issue() {

}

}
CASHIER
import java.util.Vector;

public class cashier {

public char purdet;

public int bill;

public Vector myapplicant;

public Vector mydatabase;

public void issue() {

}

public void delivery() {

}

}
DATABASE
import java.util.Vector;

public class database {

public char name;

public char details;

public Vector mycashier;

public void store() {

}
 public void update() {
}

RESULT:
Thus the mini project for credit card processing System was developed using Argo UML
and executed successfully.
EX.NO:9
DATE:
E-BOOK MANAGEMENT SYSTEM

AIM:
To develop mini project on E-book management System using Argo UML.

HARDWARE REQUIREMENTS:
Intel Pentium Processor 3

SOFTWARE REQUIREMENTS:
Argo UML

PROBLEM STATEMENT:
The problem with the existing manual system is that it cannot process more than one person
or member at a time. It is a very tedious and time consuming process. Maintenance of large number
of records and information is difficult.Multiple users can login at a time and is timeefficient.
Database can be easily managed by the system.

USE CASE DIAGRAM:

This diagram will contain the actors, use cases which are given below
Actors: User, Library Management System, central computer
Use cases: Login, Return, issue, place order

ACTIVITY DIAGRAM:
This diagram will have the activities, start point, end point, and decision boxes. Itdescribes
the flow of activities of the system under design.

CLASS DIAGRAM:
This diagram consists of the following classes, attributes, and their operations namely
User, Library management system, Central computer.

SEQUENCE DIAGRAM:
This diagram consists of the objects, messages, and Return messages
Objects: User, library management system, Centralized computer

COLLABORATION DIAGRAM
his diagram contains the objects and actors. It also shows the interaction between the
object via messages using a single link

COMPONENT DIAGRAM
The component diagram's main purpose is to show the structural relationships between
thecomponents of a system. It is represented by boxed figure. Dependencies are represented
by communication association
 DEPLOYMENT DIAGRAM
A deployment diagram in the unified modeling language serves to model the physical
deployment of artifacts on deployment targets. Deployment diagrams show "the allocation of
artifacts to nodes according to the Deployments defined between them. It is represented by 3-
dimentional box. Dependencies are represented by communication association.

PACKAGE DIAGRAM
A package diagram in unified modeling language that depicts the dependencies between
the packages that make up a model. A Package Diagram (PD) shows a grouping of elements
in the OO model, and is a Cradle extension to UML. PDs can be used to show groups of
classes in Class Diagrams (CDs), groups of components or processes in Component
Diagrams (CPDs), or groups of processors in Deployment Diagrams (DPDs).
There are three types of layer. They are

User interface layer

Domain layer

Technical services layer

USE CASE DIAGRAM:

CLASS DIAGRAM:

SEQUENCE DIAGRAM:
STATE MACHINE DIAGRAM:

COLLABORATION DIAGRAM:
PACKAGE DIAGRAM:

COMPONENT DIAGRAM:
ACTIVITY DIAGRAM:
DEPLOYMENT DIAGRAM:

MERITS:
Provides Convenience
Easy usage
User Friendliness

DEMERITS:
Need Computer Knowledge
CODE:
DATABASE
public class Database {

public Euser username;

public Integer no;

public Ebook manager myEbook manager;

public void store() {

}

public void update() {

}

}
EBOOK MANAGER
public class Ebook manager {

public string name;

public string email;

 public Euser myEuser;
public Database myDatabase;

public void update() {

}

public void list() {

}

}
EUSER
public class Euser {

public string name;

public Integer id.no;

public string email;

public Ebook manager myEbook manager;

public void login() {

}

public void download() {

}

public void payment() {

}

RESULT:
Thus the mini project for E-book Management System was developed using Argo UML
and executed successfully.
EX. NO: 10
DATE:
RECRUITMENT SYSTEM

AIM:
To develop mini project on Recruitment System using Argo UML.

HARDWARE REQUIREMENTS:
Intel Pentium Processor 3

SOFTWARE REQUIREMENTS:
Argo UML

PROBLEM STATEMENT:
This project is mainly designed to ease the selection process for recruiting person in a
company. Selection is done by conducting series of various rounds.

USE CASE DIAGRAM:

This diagram will contain the actors, use cases which are given below
Actors: Candidate, Employer
Use cases: Registration, selection, Appointment

ACTIVITY DIAGRAM:
This diagram will have the activities, start point, end point, and decision boxes. It
describes the flow of activities of the system under design.

CLASS DIAGRAM:
This diagram consists of the following classes, attributes, and their operations namely
candidate, employer and recruitment management system.

SEQUENCE DIAGRAM:
This diagram consists of the objects, messages, and Return messages
Objects: User, E-Book management system, Centralized computer

COLLABORATION DIAGRAM
This diagram contains the objects and actors. It also shows the interaction between the
object via messages using a single link
COMPONENT DIAGRAM
The component diagram's main purpose is to show the structural relationships between
thecomponents of a system. It is represented by boxed figure. Dependencies are represented
by communication association

DEPLOYMENT DIAGRAM
A deployment diagram in the unified modeling language serves to model the physical
deployment of artifacts on deployment targets. Deployment diagrams show "the allocation of
artifacts to nodes according to the Deployments defined between them. It is represented by 3-
dimentional box. Dependencies are represented by communication association.
 PACKAGE DIAGRAM
A package diagram in unified modeling language that depicts the dependencies between
the packages that make up a model. A Package Diagram (PD) shows a grouping of elements
in the OO model, and is a Cradle extension to UML. PDs can be used to show groups of
classes in Class Diagrams (CDs), groups of components or processes in Component
Diagrams (CPDs), or groups of processors in Deployment Diagrams (DPDs).
There are three types of layer. They are

User interface layer

Domain layer

Technical services layer

USECASE DIAGRAM:
CLASS DIAGRAM:

COLLABORATION DIAGRAM:
ACTIVITY DIAGRAM:
STATE CHART DIAGRAM:

SEQUENCE DIAGRAM:
COMPONENT DIAGRAM:

DEPLOYMENT DIAGRAM:
 PACKAGE DIAGRAM:

MERITS:
Provides Convenienc
Easy usage
User Friendliness

DEMERITS:
Need Computer Knowledge

CODE:
CANDIDATE

public class candidate {

public string name;

public string details;

public Integer ph.no;

public HR myHR;

public void login() {

}

public void sumbit() {

}

DATABASE

public class Database {

public string name;

public Integer no;

public HR myHR;

public void check() {

}

public void store() {

}

HR

public class HR {

public string name;

public Integer id.no;

public Integer ph.no;

public candidate mycandidate;

public Database myDatabase;

public void verify() {

}
public void result() {
}

public void report() {

}
}
RESULT:
Thus the mini project for Recruitment System was developed using Argo UML
and executed successful
 EX. NO: 11
DATE:
FOREIGN TRADING SYSTEM

AIM:
To develop mini project on Foreign Trading System using Argo UML.

HARDWARE REQUIREMENTS:
Intel Pentium Processor 3

SOFTWARE REQUIREMENTS:
Argo UML

PROBLEM STATEMENT:
This project is mainly designed to have access to trading system and to know about the in
and out of trading done in the state.

USE CASE DIAGRAM:

This diagram will contain the actors, use cases which are given below
Actors: User, Internet
Use cases: Display, option, central computer

ACTIVITY DIAGRAM:
This diagram will have the activities, start point, end point, and decision boxes. It
describes the flow of activities of the system under design.

CLASS DIAGRAM:
This diagram consists of the following classes, attributes, and their operations namely
user, central computer.

SEQUENCE DIAGRAM:
This diagram consists of the objects, messages, and Return messages
Objects: User, centralized trading system.

COLLABORATION DIAGRAM
This diagram contains the objects and actors. It also shows the interaction between the
object via messages using a single link

COMPONENT DIAGRAM
The component diagram's main purpose is to show the structural relationships between
thecomponents of a system. It is represented by boxed figure. Dependencies are represented
by communication association
DEPLOY MENT DIAGRAM
A deployment diagram in the unified modeling language serves to model the physical
deployment of artifacts on deployment targets. Deployment diagrams show "the allocation of
artifacts to nodes according to the Deployments defined between them. It is represented by 3-
dimentional box. Dependencies are represented by communication association.

PACKAGE DIAGRAM
A package diagram in unified modeling language that depicts the dependencies between
the packages that make up a model. A Package Diagram (PD) shows a grouping of elements
in the OO model, and is a Cradle extension to UML. PDs can be used to show groups of
classes in Class Diagrams (CDs), groups of components or processes in Component
Diagrams (CPDs), or groups of processors in Deployment Diagrams (DPDs).
There are three types of layer. They are

User interface layer

Domain layer

Technical services layer

USECASE DIAGRAM:
CLASS DIAGRAM:

SEQUENCE DIAGRAM:
STATECHART DIAGRAM:

COLLABORATION DIAGRAM:
ACTIVITY DIAGRAM:
COMPONENT DIAGRAM:

DEPLOYEMENT DIAGRAM
 PACKAGE DIAGRAM:

MERITS:
Provides Convenience
Easy usage
User Friendliness

DEMERITS:
Need Computer Knowledge

CODE:

CUSTOMER
import java.util.Vector;

public class customer {

public char name;

public int id;

public char addr;

public Vector mysupplier;

public void order() {

}

public void payment() {

}

}
 SUPPLIER
import java.util.Vector;

public class supplier {

public char name;

public Int id;

public char product;

public Vector mycustomer;

public Vector 1;

public void payment() {

}

public void delivery() {

}

}
TRADING MANAGEMENT SYSTEM
import java.util.Vector;

public class trading management system {

public char product;

public Int quantity;

public float price;

public Vector 1;

public void verify() {

}

public void shipping() {

}

RESULT:
Thus the mini project for Foreign Trading System was developed using Argo UML and
executed successfully.
 EX. NO: 12
DATE:

CONFERENCE MANAGEMENT SYSTEM

AIM:
To develop mini project on Conference Management System using Argo UML.

HARDWARE REQUIREMENTS:
Intel Pentium Processor 3

SOFTWARE REQUIREMENTS:
Argo UML

PROBLEM STATEMENT:
This project is mainly designed to ease the conduct of conference in an institution.
Here all activities are carried out without direct interaction

USE CASE DIAGRAM:

This diagram will contain the actors, use cases which are given below
Actors: User, Coordinator
Use cases: Registration, Submission of papers, Confirmation and conduct of event.

ACTIVITY DIAGRAM:
This diagram will have the activities, start point, end point, and decision boxes. It
describes the flow of activities of the system under design.

CLASS DIAGRAM:
This diagram consists of the following classes, attributes, and their operations
User, central management system, conference coordinator

SEQUENCE DIAGRAM:
This diagram consists of the objects, messages, and Return messages
Objects: User, Conference coordinator, Centralized computer

COLLABORATION DIAGRAM
This diagram contains the objects and actors. It also shows the interaction between the
object via messages using a single link
COMPONENT DIAGRAM
The component diagram's main purpose is to show the structural relationships between
thecomponents of a system. It is represented by boxed figure. Dependencies are represented
by communication association

DEPLOY MENT DIAGRAM

A deployment diagram in the unified modeling language serves to model the physical
deployment of artifacts on deployment targets. Deployment diagrams show "the allocation of
artifacts to nodes according to the Deployments defined between them. It is represented by 3-
dimentional box. Dependencies are represented by communication association.
 PACKAGE DIAGRAM

A package diagram in unified modeling language that depicts the dependencies between
the packages that make up a model. A Package Diagram (PD) shows a grouping of elements
in the OO model, and is a Cradle extension to UML. PDs can be used to show groups of
classes in Class Diagrams (CDs), groups of components or processes in Component
Diagrams (CPDs), or groups of processors in Deployment Diagrams (DPDs).
There are three types of layer. They are

User interface layer

Domain layer

Technical services layer

USECASE DIAGRAM:
STATECHART DIAGRAM:

CLASS DIAGRAM:
SEQUENCE DIAGRAM:

COLLABORATION DIAGRAM:
ACTIVITY DIAGRAM:
COMPONENT DIAGRAM:

DEPLOYEMENT DIAGRAM:
PACKAGE DIAGRAM:

MERITS:
Provides Convenience
Easy usage
User Friendliness

DEMERITS:
Need Computer Knowledge

CODE:

CENTRAL SYSTEM

import java.util.Vector;

public class central system {

public char topic;

public Int count;

public Integer newAttr;

public Vector 1 1;

public void prize() {

}

}
 MEMBER
import java.util.Vector;

public class member {

public char name;

public Int id;

public char dept;

public Vector 1 1;

public void register() {

}

public void present_paper() {

}

}
ORGANIZER

import java.util.Vector;

public class organizer {

public char name;

public Int id;

public char dept;

public Vector 1 1;
public Vector 1 1;

public void selection() {

}

public void allcate_seats() {

}

RESULT:
Thus the mini project for Conference Management System was developed using Argo
UML and executed successfully.
EX. NO: 13
DATE:

BPO MANAGEMENT SYSTEM

AIM:
To develop mini project on BPO Management System using Argo UML.

HARDWARE REQUIREMENTS:
Intel Pentium Processor 3

SOFTWARE REQUIREMENTS:
Argo UML

PROBLEM STATEMENT:
This project is mainly designed to access information about products and provide services
to clients by answering their queries.

USE CASE DIAGRAM:

This diagram will contain the actors, use cases which are given below
Actors: User, Service provider
Use cases: Client, Query, Central computer

ACTIVITY DIAGRAM:
This diagram will have the activities, start point, end point, and decision boxes. It
describes the flow of activities of the system under design.

CLASS DIAGRAM:
This diagram consists of the following classes, attributes, and their operations namely
Client, Service-provider and Centralized computer.

SEQUENCE DIAGRAM:
This Diagram consists of the objects, messages, and Return messages
Objects: Client, Service-provider, Centralized computer.

COLLABORATION DIAGRAM
This diagram contains the objects and actors. It also shows the interaction between the
object via messages using a single link
COMPONENT DIAGRAM
The component diagram's main purpose is to show the structural relationships between
thecomponents of a system. It is represented by boxed figure. Dependencies are represented
by communication association

DEPLOY MENT DIAGRAM

A deployment diagram in the unified modeling language serves to model the physical
deployment of artifacts on deployment targets. Deployment diagrams show "the allocation of
artifacts to nodes according to the Deployments defined between them. It is represented by 3-
dimentional box. Dependencies are represented by communication association.
 PACKAGE DIAGRAM
A package diagram in unified modeling language that depicts the dependencies between
the packages that make up a model. A Package Diagram (PD) shows a grouping of elements
in the OO model, and is a Cradle extension to UML. PDs can be used to show groups of
classes in Class Diagrams (CDs), groups of components or processes in Component
Diagrams (CPDs), or groups of processors in Deployment Diagrams (DPDs).
There are three types of layer. They are

User interface layer

Domain layer

Technical services layer

USECASE DIAGRAM:
CLASS DIAGRAM:

STATE CHART DIAGRAM:

ACTIVITYDIAGRAM:
SEQUENCEDIAGRAM:
COLLABORATION DIAGRAM:
COMPONENT DIAGRAM:

DEPLOYEMENT DIAGRAM:
 PACKAGE DIAGRAM:

MERITS:
Provides Convenience
Easy usage
User Friendliness

DEMERITS:
Need Computer Knowledge

CODE:
AGENT
import java.util.Vector;

public class agent {

public char name;

public Int id;

public Int phno;

public Vector mycustomer;

public Vector mydatabase;

public void make_calls() {

}

public void make_sale() {

}

}
 CUSTOMER

import java.util.Vector;

public class customer {

public char name;

public char address;

public Int phno;

public Vector myagent;

public void attend_call() {

}

public void asks_query() {

}

DATABASE
import java.util.Vector;

public class database {

public char name;

public Vector myagent;

public void get_details() {

}

public void update() {

}

RESULT:
Thus the mini project for BPO Management System was developed using Argo UML and
executed successfully.
EX. NO: 14
DATE:
LIBRARY MANAGEMENT SYSTEM

AIM:
To develop mini project on Library Management System using Argo UML.

HARDWARE REQUIREMENTS:
Intel Pentium Processor 3

SOFTWARE REQUIREMENTS:
Argo UML

PROBLEM STATEMENT:
This project is mainly designed for the providing online access to library/Digital Library. It
also provide easy management of books, journals and magazines.

USE CASE DIAGRAM:

This diagram will contain the actors, use cases which are given below
Actors: Library Patron, Librarian

Use cases: Login, Renew, Search,Add book, Delete book etc.

ACTIVITY DIAGRAM:
This diagram will have the activities, start point, end point, and decision boxes. It
describes the flow of activities of the system under design.

CLASS DIAGRAM:
This diagram consists of the following classes, attributes, and their operations namely
Customer, Service provider and Centralized database.

SEQUENCE DIAGRAM:
This Diagram consists of the objects, messages, and Return messages

COLLABORATION DIAGRAM
This diagram contains the objects and actors. It also shows the interaction between the
object via messages using a single link
COMPONENT DIAGRAM
The component diagram's main purpose is to show the structural relationships between
thecomponents of a system. It is represented by boxed figure. Dependencies are represented
by communication association

DEPLOY MENT DIAGRAM

A deployment diagram in the unified modeling language serves to model the physical
deployment of artifacts on deployment targets. Deployment diagrams show "the allocation of
artifacts to nodes according to the Deployments defined between them. It is represented by 3-
dimentional box. Dependencies are represented by communication association.
 PACKAGE DIAGRAM
A package diagram in unified modeling language that depicts the dependencies between
the packages that make up a model. A Package Diagram (PD) shows a grouping of elements
in the OO model, and is a Cradle extension to UML. PDs can be used to show groups of
classes in Class Diagrams (CDs), groups of components or processes in Component
Diagrams (CPDs), or groups of processors in Deployment Diagrams (DPDs).
There are three types of layer. They are

User interface layer

Domain layer

Technical services layer

USECASE DIAGRAM:

STATE CHART DIAGRAM:

CLASS DIAGRAM:

COMPONENTDIAGRAM
ACTIVITYDIAGRAM:
SEQUENCEDIAGRAM:

PACKAGE DIAGRAM:
COLLABORATION DIAGRAM:

DEPLOYMENT DIAGRAM:
 MERITS:
Provides Convenience
Easy usage
User Friendliness

DEMERITS:
Need Computer Knowledge

CODE:

DATABASE

public class database {

private string book details;

public student mystudent;

public void check() {

}

public void update() {

}

LIBRARIAN
import java.util.Vector;

public class librarian {

public string bookname;

public string author;

/**
*
* @element-type student
*/
public Vector mystudent;

public void verify() {

}

public void issue() {

}

}
 STUDENT

public class student {

public Int id;

private string book name;

public string author;

public librarian mylibrarian;

public database mydatabase;

public void request() {

}

public void select() {

}

RESULT:
Thus the mini project for Library Management System was developed using Argo UML
and executed successfully.
EX. NO: 15
DATE:
STUDENT INFORMATION SYSTEM

AIM:
To develop mini project on Student Information System using Argo UML.

HARDWARE REQUIREMENTS:
Intel Pentium Processor 3

SOFTWARE REQUIREMENTS:
Argo UML

PROBLEM STATEMENT:
A Student Information System is a software application for educational establishments to
manage student data. Student information system (SIS) provides capabilities for entering student
test and other assessment scores, building student schedules, tracing student attendance and
managing many other student related data needs in a school, college or university.

USE CASE DIAGRAM:

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

Use cases: Registration, update, enter marks, attendance etc.

ACTIVITY DIAGRAM:
This diagram will have the activities, start point, end point, and decision boxes. Itdescribes
the flow of activities of the system under design.

CLASS DIAGRAM:
This diagram consists of the following classes, attributes, and their operations namely
Customer, Service provider and Centralized database.

SEQUENCE DIAGRAM:
This Diagram consists of the objects, messages, and Return messages
Objects:

COLLABORATION DIAGRAM
This diagram contains the objects and actors. It also shows the interaction between the
object via messages using a single link
COMPONENT DIAGRAM
The component diagram's main purpose is to show the structural relationships between
thecomponents of a system. It is represented by boxed figure. Dependencies are represented
by communication association
DEPLOY MENT DIAGRAM
A deployment diagram in the unified modeling language serves to model the physical
deployment of artifacts on deployment targets. Deployment diagrams show "the allocation of
artifacts to nodes according to the Deployments defined between them. It is represented by 3-
dimentional box. Dependencies are represented by communication association.

PACKAGE DIAGRAM
A package diagram in unified modeling language that depicts the dependencies between
the packages that make up a model. A Package Diagram (PD) shows a grouping of elements
in the OO model, and is a Cradle extension to UML. PDs can be used to show groups of
classes in Class Diagrams (CDs), groups of components or processes in Component
Diagrams (CPDs), or groups of processors in Deployment Diagrams (DPDs).
There are three types of layer. They are

User interface layer

Domain layer

Technical services layer

USECASE DIAGRAM:
CLASS DIAGRAM:

STATECHART DIAGRAM:
ACTIVITY DIAGRAM:
COMPONENT DIAGRAM:

COLLABORATION DIAGRAM:
SEQUENCE DIAGRAM:

DEPLOYEMENT DIAGRAM:
 PACKAGE DIAGRAM:

MERITS:
Provides Convenience
Easy usage
User Friendliness

DEMERITS:
Need Computer Knowledge

CODE:

DATABASE
public class database {

public string name;

public Integer id;

public staff mystaff;

public void update() {

}

public void delete() {

}

}
 STAFF
import java.util.Vector;

public class staff {

public string name;

public string dept;

/**
*
* @element-type student
*/
public Vector mystudent;
public database mydatabase;

public void calculate() {

}

public void average() {

}

public void result() {

}

STUDENT
public class student {

public string name;

public Integer regno;

public string dept;

public staff mystaff;

public void getresult() {

}

public void getsubject() {

}

RESULT:
Thus the mini project for Student Information System was developed using Argo UML
and executed successfully.
EX. NO: 16
DATE:
ATM MANAGEMENT SYSTEM

AIM:
To develop mini project on ATM system using Argo UML.

HARDWARE REQUIREMENTS:
Intel Pentium Processor 3

SOFTWARE REQUIREMENTS:
Argo UML

PROBLEM STATEMENT:
This project is mainly designed designed for the supporting the computerized access to the ATM
network system in order to provide the cash transaction like withdrawal of amount, deposition and
transferring the amount. ATM process takes care of money transferring & deposition. The processing takes
updating of amount, view amount etc are done.

USE CASE DIAGRAM:

This diagram will contain the actors, use cases which are given below
Actors: Card Holder, ATM Management System

Use cases: Login, withdraw, deposit, balance enquiry and central computer

ACTIVITY DIAGRAM:
This diagram will have the activities, start point, end point, and decision boxes. It
describes the flow of activities of the system under design.

CLASS DIAGRAM:
This diagram consists of the following classes, attributes, and their operations namely
Customer, Service provider and Centralized database.

SEQUENCE DIAGRAM:
This Diagram consists of the objects, messages, and Return messages
Objects: Bank Customer, ATM machine, Centralized computer.

COLLABORATION DIAGRAM
This diagram contains the objects and actors. It also shows the interaction between the
object via messages using a single link
COMPONENT DIAGRAM
The component diagram's main purpose is to show the structural relationships between
thecomponents of a system. It is represented by boxed figure. Dependencies are represented
by communication association
DEPLOY MENT DIAGRAM
A deployment diagram in the unified modeling language serves to model the physical
deployment of artifacts on deployment targets. Deployment diagrams show "the allocation of
artifacts to nodes according to the Deployments defined between them. It is represented by 3-
dimentional box. Dependencies are represented by communication association.

PACKAGE DIAGRAM
A package diagram in unified modeling language that depicts the dependencies between
the packages that make up a model. A Package Diagram (PD) shows a grouping of elements
in the OO model, and is a Cradle extension to UML. PDs can be used to show groups of
classes in Class Diagrams (CDs), groups of components or processes in Component
Diagrams (CPDs), or groups of processors in Deployment Diagrams (DPDs).
There are three types of layer. They are

User interface layer

Domain layer

Technical services layer

USECASE DIAGRAM:
CLASS DIAGRAM:

STATECHART DIAGRAM:
ACTIVITY DIAGRAM:

COLLABORATION DIAGRAM:
SEQUENCE DIAGRAM:

COMPONENT DIAGRAM:
PACKAGE DIAGRAM:

DEPLOYEMENT DIAGRAM:
MERITS:
Provides Convenience
Easy usage
User Friendliness

DEMERITS:
Need Computer Knowledge

CODE:

ATM MACHINE
public class ATM machine {

public string name;

public Integer accno;

public Integer pinno;

public user myuser;

public Database myDatabase;

public void select() {

}

DATABASE

public class Database {

public string name;

public string addr;

public Integer accno;

public Integer pinno;

public ATM machine myATM machine;

public void validity() {

}

public void verify() {

}

}
 USER
public class user {

public string name;

public Integer accno;

public Integer pinno;

public ATM machine myATM machine;

public void swipe() {

}

public void withdraw() {

}

RESULT:
Thus the mini project for ATM management system was developed using Argo UML
and executed successfully.