0% found this document useful (0 votes)

25 views92 pages

EX - NO: 1 Passport Automation System Date: Aim

The Passport Automation System aims to streamline the passport application process using ArgoUML, Java, and MySQL, allowing applicants to submit their details online for verification by authorities. The system minimizes manual work, enhances efficiency, and facilitates communication between applicants, administrators, and police for necessary verifications. It includes various UML diagrams to illustrate system functions, user interactions, and data flow, ultimately ensuring timely passport issuance while maintaining security and accuracy.

Uploaded by

Jerlin John

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOC, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

25 views92 pages

EX - NO: 1 Passport Automation System Date: Aim

Uploaded by

Jerlin John

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOC, PDF, TXT or read online on Scribd

EX.

NO: 1 PASSPORT AUTOMATION SYSTEM DATE:

AIM:
To develop the Passport Automation System using ArgoUML tools, Java and MySQL.

PROBLEM ANALYSIS AND PROJECT PLAN:

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

SOFTWARE REQUIREMENTS SPECIFICATION:

1) INTRODUCTION:
Passport Automation System is an interface between the Applicant and the
Authority responsible for the Issue of Passport. It aims at improving the efficiency in the Issue of
Passport and reduces the complexities involved in it to the maximum possible extent.

1.1) PURPOSE:
If the entire process of 'Issue of Passport' is done in a manual manner then it would
take several months for the passport to reach the applicant. Considering the fact that the number of
applicants for passport is increasing every year, an Automated System becomes essential to meet the
demand. So, this system uses several programming and Database techniques to elucidate the work
involved in this process. As this is a matter of National Security, the system has been carefully
verified and validated in order to satisfy it.

1.2) SCOPE:

• The System provides an online interface to the user where they can fill in their personal details.
• The authority concerned with the issue of passport can use this system to reduce his workload and
process the application in a speedy manner.
• Provide a communication platform between the applicant and the administrator.
• Transfer of data between the Passport Issuing Authority and the Local Police for verification of
applicant's information.

1.3) DEFINITIONS, ACRONYMS AND THE ABBREVIATIONS:

• Administrator - Refers to the super user who is the Central Authority who has been vested with the
privilege manage the entire system. It can be any higher official in the Regional Passport Office of
Ministry of External Affairs.
• Applicant – He is the one who wishes to obtain the Passport.
• PAS - Refers to this Passport Automation System.

1.4) REFERENCES:
It is given in IEEE Software Requirement Specification format.

1.5) TECHNOLOGIES TO BE USED:

 Java 6.0

1.6) TOOLS TO BE USED:

 ArgoUML tool (for developing UML Patterns)

1.7) OVERVIEW:
SRS includes two sections overall description and specific requirements - Overall
description will describe major role of the system components and inter-connections. Specific
requirements will describe roles & functions of the actors.

2) PRODUCT DESCRIPTION:
The PAS acts as an interface between the 'applicant' and the
'administrator'. This system tries to make the interface as simple as possible and at the same time not
risking the security of data stored in. This minimizes the time duration in which the user receives the
passport.

2.1) SYSTEM FUNCTIONS:

• Secure Registration of information by the Applicants.
• Message box for Passport Application Status Display by the Administrator.
• Administrator can generate reports from the information and is the only authorized
Personnel to add the eligible.
• Application information to the Database.

2.2) USER CHARACTERISTICS:

• Applicant - They are the people who desire to obtain the passport and submit the
information to the Database.
• Administrator - He has the certain privileges to add the passport status and to approve the issue
of passport. He may contain a group of persons under him to verify the documents and give
suggestion whether or not to approve the dispatch of passport.
• Police - He is the person who upon receiving intimation from the PAS, perform a personal
verification of the applicant and see if he has any criminal case against him before or at present.
He has been vetoed with the power to decline an application by suggesting it to the
Administrator if he finds any discrepancy with the applicant. He communicates via this PAS.

2.3) CONSTRAINTS:
• The applicants require a computer to submit their information.
• Although the security is given high importance, there is always a chance of intrusion in the
web world which requires constant monitoring.
• The user has to be careful while submitting the information. Much care is required.

2.4) ASSUMPTIONS AND DEPENDENCIES:

• The Applicants and Administrator must have basic knowledge of computers and English
Language.
• The applicants may be required to scan the documents and send.

UML DIAGRAMS:

1. USE CASE DIAGRAM:

DOCUMENTATION OF USE CASE DIAGRAM:

• The actors in use case diagram are Applicant, regional administrator, Database, passport
Administrator, Police.
• The use cases are Login, give details, logout, collect details, verification and issue.
• The actors use the use case is denoted by the arrow.
• The login use case checks the username and password for applicant, regional
administrator, passport administrator and police.
• The submit details use case is used by the applicant for submitting his details
• The check status use case is used by the applicant for checking the status of the application
process.
• The get details, verify and store verification use case is used by passport
administrator, regional administrator, and police.
• The details use case is used for getting the details form the Database for verification. The
verify use case is used for verifying the details by comparing the data in the Database.
• The store verification use case is to update the data in the Database.
• And finally, the issue passport use case is used by the passport administrator for issuing
passport whose application verified successfully by all the actor.

DOCUMENTATION OF CLASS DIAGRAM:

• APPLICANT - The applicant has attribute such as name and password and operations are login,
give details and logout. The applicant login and fill the details that are required for applying the
passport. After applying the person can view the status of the passport verification process.
• THE DATABASE - The Database has attributed such as name and operation is store. The
purpose is to store the data.
 REGIONAL ADMINISTRATOR - The regional administrator has attribute such as name and
operation are get details, verify details and send. The regional administrator gets the details form
Database and verify with their Database
 PASSPORT ADMINISTRATOR - The passport administrator has attributed such as name and
operation are getDetails(), verifyDetails() and issue().
3. SEQUENCE DIAGRAM:
A sequence diagram in Unified Modeling Language (UML) is a kind of
interaction diagram that shows how processes operate with one another and in what order. It is a construct
of a Message Sequence Chart. There are two dimensions.
• Vertical dimension-represent time.
• Horizontal dimension-represent different objects.

DOCUMENTATION OF SEQUENCE DIAGRAM:

• The applicant login the Database and give his details and Database store the details.
• The passport administrator gets the details from the Database and do verification and the forward
to regional administrator.
• The regional administrator gets the details form passport administrator and perform verification
and send report to passport administrator.
• The police get the details form passport administrator and perform verification and send report to
passport administrator.

5. STATE CHART DIAGRAM:

The purpose of state chart diagram is to understand the algorithm
involved in performing a method. It is also called as state diagram. A state is represented as a round box,
which may contain one or more compartments. An initial state is represented as small dot.

DOCUMENTATION OF STATE CHART DIAGRAM:

• The states of the passport automation system are denoted in the state chart diagram
• Login state represent authentication for login the passport automation system.
• Police, regional administrator and passport administrator get necessary details and verification of
the applicant are denoted from the Get detail state and verification state.
6. ACTIVITY DIAGRAM:
Activity diagrams are graphical representations of workflows of stepwise
activities and actions with support for choice, iteration and concurrency. In the Unified Modeling
Language, activity diagrams can be used to describe the business and operational step-by-step workflows
of components in a system. An activity diagram shows the overall flow of control. An activity is shown
as a rounded box containing the name of the operation.

DOCUMENTATION OF ACTIVITY DIAGRAM:

• The activities in the passport automation system are login, submit details, get details, issue
passport and penalty and verification.
• In the login activity applicant give username and password and then login into the passport
automation system after then fill the details that are required for application.

7. COMPONENT DIAGRAM:
The component diagram is represented by figure dependency and it is a graph of
design of figure dependency. 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.
DOCUMENTATION OF COMPONENT DIAGRAM:
The components in the passport automation system
are:
• Passport Automation System
• Applicant
• Passport administrator
• Regional administrator
• Police.

DOCUMENTATION OF DEPLOYMENT DIAGRAM:

The device node is passport automation system
and execution environment nodes are applicant passport administrator, regional administrator, and police.

8. PACKAGE DIAGRAM:
Package diagram in unified modeling language 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 and Technical services layer.
• User interface layer - Software objects representing domain concepts that fulfill application
requirements, such as calculation of a sale total.
• Domain Layer - Layer that contains domain objects to handle application logic work
• Technical services Layer - General purpose object and sub system that provide supporting
technical services, such as interfacing with a Database logging
DOCUMENTATION OF PACKAGE DIAGRAM:
The three layers in the passport automation system are
user interface, domain and technical service layers.
 The user interface layer- represents the user interface components such as web, applicant,
passport administrator, police, and regional administrator.
 The domain layer- has major actions such as give and get details, verification and issues.
 Technical service layer- authenticated user only can access the technical services.

RESULT:
Thus, the project to develop passport automation system was developed using ArgoUML
Software and was executed successfully.
[Link]: 2 BOOK BANK MANAGEMENT SYSTEM DATE:

AIM:
To develop a project of Book bank management system using ArgoUML Software and to
implement the software in Java.

PROBLEM ANALYSIS AND PROJECT DESIGN:

The book bank management system is software
in which a member can register themselves and then he can borrow books from the book bank. It mainly
concentrates on providing books for engineering students. The process of members registering and
purchasing books from the book bank are described sequentially through following steps: First the
member registers himself if he was new to the book bank. Old members will directly select old member
button. They select their corresponding year. After selecting the year they fill the necessary details and
select the book.

SOFTWARE REQUIREMENT SPECIFICATION:

[Link]. CONTENTS
1 INTRODUCTION
2 OBJECTIVE
3 OVERVIEW
4 GLOSSARY
5 PURPOSE
6 SCOPE
7 FUNCTIONALITY
8 USABILITY
9 PERFORMANCE
10 RELIABILITY
11 FUNCTIONAL REQUIREMENTS
12 SOFTWARE REQUIREMENTS
13 HARDWARE REQUIREMENTS

1. INTRODUCTION:
This system would be used by members who are students of any college to check
the availability of the books and borrow the books, and then the Databases are updated. The purpose of
this document is to analyze and elaborate on the high-level needs and features of the book bank
management system. It also tells the usability, reliability defined in use case specification.

2. OBJECTIVE:
The main objective of the system is to design an online book-bank monitoring system to enable a central
monitoring mechanism of the book-bank be faster and less error prone. Apart from this, help the students
acquire the right books for the syllabus at the right time, ensure availability of basic textbooks to students
against limited funds and develop students’ ability to handle property loaned to them.

3. OVERVIEW:
The overview of this project is to design a tool for book bank so that it can be used by any book banks to
lend their books as well as colleges.

4. GLOSSARY:

TERMS DESCRIPTION
MEMBER The one who registers himself and purchase books from the bank.
DATABASE Database is used to store the details of members and books.
ADMINISTRATOR The one who verifies the availability of book and issue them.
USER Member
SOFTWARE REQUIREMENT This software specification documents full set of features and function
SPECIFICATION Book bank management system that is performed in company website.

5. PURPOSE:
The purpose of the book bank management system is to reduce the manual intervention.

6. SCOPE:
The scope of this book bank management system is to act as a tool for book bank
administrator for quick reference, availability of the books.

7. FUNCTIONALITY:
Many members will be waiting to take the book from the book bank at a single day.

8. USABILITY:
User interface makes the book bank management system to be efficient. That is the system will
help the member to register easily and helps them to get their books easily. The system should be user
friendly.

9. PERFORMANCE:
It describes the capability of the system to perform the book bank management process of
the applicant without any error and performing it efficiently.

10. RELIABILITY:
The book bank management system should be able to serve the applicant with correct
information and day-to-day update of information.

11. FUNCTIONAL REQUIREMENTS:

Functional requirements are those refer to the functionality of the system.
That is the services that are provided to the member who borrows book.

12. SOFTWARE REQUIREMENTS:

Front end: ArgoUML and Java.

Back end: MySQL.

13. HARDWARE REQUIREMENTS:

Processor: Intel Core I5

RAM: 256 Mb
Operating system: Fedora v12
Free disk space: 1Gb

UML DIAGRAMS:

1. USE CASE DIAGRAM:

This class diagram has 8 classes:

Member details class- is the class name. Its attributes are name, father name, date of
birth, address, phone number, member id, college, degree, course and semester.
• Administrator- is the class name. Its attributes are name, address, phone, mail id. Its operations
are authentication, verification and issue books.
• Year-is the class name. Its attribute is year selection. Its operations are 1 st year,2nd year, 3rd
year,4th year.
• Issue for 1st year-is the class name. Its attributes are member code, member name, book code,
book name, and quantity. Its operation is issue.
• Issue for 2nd year-is the class name. Its attributes are member code, member name, book code,
book name, and quantity. Its operation is issue.
• Issue for 3rd year-is the class name. Its attributes are member code, member name, book code,
book name, and quantity. Its operation is issue.

DOCUMENTATION OF SEQUENCE DIAGRAM:

The sequence diagram describes the sequence of steps to
show:
• The member registers himself in book bank
• He will select the year
• He selects the books given and the Database will update the status of book.
• Then administrator will log in and verify the status of books.
• If the book is available, he will issue the book.

4. COLLABARATION DIAGRAM:
A collaboration diagram, also called a communication diagram or
interaction diagram. A sophisticated modeling tool can easily convert a collaboration diagram into a
sequence diagram and the vice versa. A collaboration diagram resembles a flowchart that portrays the
roles, functionality and behavior of individual objects as well as the overall operation of the system in real
time.

DOCUMENTATION OF COLLABORATION DIAGRAM:

The collaboration diagram is to show
how the member registers himself and borrow the book from the book bank. Here the sequence is
numbered according to the flow of execution.

DOCUMENTATION OF ACTIVITY DIAGRAM:

This activity diagram flow of stepwise activities
performed in book bank management system.

1. The member registers himself in book bank

2. After that he will select the year.
3. He will select the books.
4. Database will update the status of book.
5. Database will update the details
6. Then the administrator will log in to his account.
7. After authentication he will verify the availability of book.
8. If available he will issue the book.

DOCUMENTATION OF COMPONENT DIAGRAM:

The main component in this component diagram
is online book bank management systems. And member details, issue for first year, issue for second year
issue for third year and issue for fourth year are components comes under the main component.

7. DEPLOYMENT DIAGRAM:
A deployment diagram in the unified modeling language serves to model
the physical deployment of artifacts on deployment targets Dependencies are represented by
communication association. The basic element of a deployment diagram is a node of two types:
 DEVICE NODE – A physical computing resource with processing and memory
service to execute software such as a typical computer or a mobile phone.
 EXECUTION ENVIRONMENT NODE - This is a software computing resource
that runs within an outer node and which itself provides a service to host an execute
other executable software.
DOCUMENTATION OF DEPLOYMENT DIAGRAM:
The processor in this deployment diagram is the
book bank which is the main part and which are the some of the main activities performed in the system.
And issue for first year, issue for second year issue for third year and issue for fourth year are some
activities performed in this system.

DOCUMENTATION OF PACKAGE DIAGRAM:

The three layers in the Book bank management system are
• The User interface layer - consists of the web and member details. This layer describes how
the member goes to book bank and registers himself.
• The Domain layer – shows the activities that are performed in the book bank management
system. The activities are register and book issues.
• The Technical service layer - the member details and verification details are stored in the
Database.

RESULT : Thus, the project to develop book bank management system using ArgoUML Software and to
implement the software in Java was done successfully.
[Link]: 3 EXAM REGISTRATION SYSTEM DATE:

AIM:
To develop a project Exam Registration using ArgoUML Software and to implement the software in
Java.

PROBLEM ANALYSIS AND PROJECT PLANNING:

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

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

SOFTWARE REQUIREMENTS SPECIFICATION:

[Link]. CONTENTS
1 INTRODUCTION
2 OBJECTIVE
3 OVERVIEW
4 GLOSSARY
5 PURPOSE
6 SCOPE
7 FUNCTIONALITY
8 USABILITY
9 PERFORMANCE
10 RELIABILITY
11 FUNCTIONAL REQUIREMENTS
12 HARDWARE REQUIREMENTS

1. INTRODUCTION:
Exam Registration application is an interface between the Student and the Authority
responsible for the Exams. It aims at improving the efficiency in the registration of exams and reduces the
complexities involved in it to the maximum possible extent.

2. OBJECTIVE:
The main objective of Exam Registration System is to make applicants register
themselves and apply for the exam. Exam Registration System provides easy interface to all the users to
apply for the exam easily.

3. OVERVIEW:
The overview of the project is to design an exam registration tool for the registration
process which makes the work easy for the applicant as well as the Authorities of Exam. Authorities of
the exam can keep track of and maintain the Database of the registered applicants for the exams.
4. GLOSSARY:

TERMS DESCRIPTION
Applicant can register himself by filling out the registration form and
APPLICANT OR STUDENT finally paying the payment for attending the exam.
Database is used to maintain and store the details of registered
DATABASE applicants.
SOFTWARE REQUIREMENT This software specification documents full set of features and function
SPECIFICATION for exam registration system that is performed in company website.

5. PURPOSE:
The purpose of exam registration system is to register for the exam in an easier way and
to maintain the registered details in an effective manner.

6. SCOPE:
The scope of this Exam Registration process is to provide an easy interface to the applicants
where they can fill their details and the authorities maintain those details in an easy and effective way.

7. FUNCTIONALITY:
The main functionality of registration system is to make the registration and
Database for it to be maintained in an efficient manner.

8. USABILITY:
User interface makes the Exam Registration system to be efficient. That is the system
will help the applicant to register easily and helps the authorities to maintain details effectively. The
system should be user friendly. It describes the capability of the system to perform the registration
process of the applicant without any error and performing it efficiently.

9. RELIABILITY:
The Exam Registration system should be able to serve the applicant with correct
information and day-to-day update of information.

10. FUNCTIONAL REQUIREMENTS:

Functional requirements are those refer to the functionality of the
system. That is the services that are provided to the applicant who apply for the Exam.

11. EXTERNAL INTERFACE REQUIREMANTS SOFTWARE REQUIREMENTS:

Front end: ArgoUML and Java

Back end: MySQL

12. HARDWARE REQUIREMENTS:

Processor: Intel Core I5

RAM: 256 Mb
Operating system: Fedora v12
Free disk space: 1Gb

UML DIAGRAMS:

1. USE CASE DIAGRAM:

DOCUMENTATION OF USE CASE DIAGRAM:

The actors in this use case diagram are Student, Interface
and Database. The use cases are the activities performed by actors.
 Student Fills out the form in the form filling process.
 The interface checks and validates registered details.
 Then the Database is searched for details and verified.
 Database stores the details and returns acknowledgement.

2. CLASS DIAGRAM:
A class diagram in the unified modeling language (UML) is a type of static
structure diagram that describes the structure of a system by showing the system's classes, their attributes,
and the relationships between the classes. It is represented using a rectangle with three compartments.
Top compartment has the class name, middle compartment the attributes and the bottom compartment
with operations.
DOCUMENTATION OF CLASS DIAGRAM:
This class diagram has three classes - applicant, recruiter
and Database.
• Student–is the class name. Its attributes are name, Address, DOB, Gender, College, Subjects,
Semester, Year, Degree, Branch and Payment. The operations performed in the student’s class are
form filling, search Database and receiving acknowledgement.
• Registrations Interface – is the class name. Its attributes are Login, Password and Database. The
operations performed are form verification, store in Database and send acknowledgement.
• Database – is the class name. The operations performed are storing Search and storing the values.

DOCUMENTATION OF COLLABORATION DIAGRAM:

The collaboration diagram is to show
how the Student registers and the authorities maintain the details of the registered students in the
registration system. Here the sequence is numbered according to the flow of execution.

6. DEPLOYMENT DIAGRAM:
A deployment diagram in the unified modeling language serves to model
the physical deployment of artifacts on deployment targets Dependencies are represented by
communication association. The basic element of a deployment diagram is a node of two types:
 DEVICE NODE – A physical computing resource with processing and memory
service to execute software such as a typical computer or a mobile phone.
 EXECUTION ENVIRONMENT NODE - This is a software computing resource
that runs within an outer node and which itself provides a service to host an execute
other executable software.
DOCUMENTATION OF DEPLOYMENT DIAGRAM:
The processor in this deployment diagram is the
Exam Registration system which is the main part and the devices are the register, verify and search which
are the some of the main activities performed in the system.

7. PACKAGE DIAGRAM:
Package diagram in unified modeling language 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 and Technical services layer.
• User interface layer - Software objects representing domain concepts that fulfill application
requirements, such as calculation of a sale total.
• Domain Layer - Layer that contains domain objects to handle application logic work
• Technical services Layer - General purpose object and sub system that provide
supporting technical services, such as interfacing with a Database logging

DOCUMENTATION OF PACKAGE DIAGRAM:

The three layers in the exam registration system are:
• The User interface layer - consists of the form and login. This layer describes how the
applicant logins to the search and apply for the exam.
• The Domain layer – shows the activities that are performed in the Exam Registration system.
The activities are register and search the Database.
• The Technical service layer – get student details and the selected applicant details are stored
in the Database.
RESULT:
Thus, the project to develop Exam Registration system using ArgoUML Software and to
implement the software in Java is done successfully.
EX. NO: 4 STOCK MAINTENANCE SYSTEM DATE:

AIM:
To develop a project stock maintenance system using ArgoUML Software and to
implement the software in Java.

PROBLEM ANALYSIS AND PROJECT PLANNING:

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

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

SOFTWARE REQUIREMENTS SPECIFICATION:

[Link]. CONTENTS
1 INTRODUCTION
2 OBJECTIVE
3 OVERVIEW
4 GLOSSARY
5 PURPOSE
6 SCOPE
7 FUNCTIONALITY
8 USABILITY
9 PERFORMANCE
10 RELIABILITY
11 FUNCTIONAL REQUIREMENTS

1. INTRODUCTION:
This software specification documents full set of features and function for
online stock maintenance system that is performed in company website. In this we give
specification about the customer orders. It tells the usability, reliability defined in use case
specification.

2. OBJECTIVE:
The main objective of the stock maintenance system is to maintain the stock. It
provides the vendor to maintain the stock in a precise manner.

3. OVERVIEW:
The overview of the project is to design an online tool for the stock maintenance
process which eases the work for the customer as well as the companies. Companies can create
their company forms according to their wish in which the applicant can register.
4. GLOSSARY:

TERMS DESCRIPTION
The customer can have the username and password after login to the system.
After login they directed to fill the customer details. And the customer places
their order. After placing orders, they lead to verify all the details in a single
CUSTOMER form. Then they place the order successfully.
DATABASE Database is used to verify the customer details and orders.
VENDOR Vendor has the login id. After login vendor verify the customer details and orders
and maintain the stocks.
SOFTWARE This software specification documents full set of features and function for stock
REQUIREMENT maintenance system that is performed in application.
SPECIFICATION

5. PURPOSE:
The purpose of stock maintenance system is to maintain the stock in an precise manner.

6. SCOPE:
The scope of this stock maintenance system is to maintain the stock.

7. FUNCTIONALITY:
The main functionality of the stock maintenance system is to maintain the stock.

8. USABILITY:
User interface makes the stock maintenance system to be efficient. That is the system will
help the customer to place the details and orders easily and helps the vendor to maintain the stock
accurate. The system should be user friendly.

9. PERFORMANCE:
It describes the capability of the system to maintain the stock without any loss of stock
and performing it efficiently.

10. RELIABILITY:
The stock maintenance system should be able to maintain the stock with correct updates
from day to day placement of new orders from customer.

11. FUNCTIONAL REQUIREMENTS:

Functional requirements are those refer to the functionality of the
system. That is the services that are provided to the customer who places the orders.

UML DIAGRAMS:

1. USE CASE DIAGRAM:

A use case is a methodology used in system analysis to identify, clarify, and
organize system requirements. The use case is made up of a set of possible sequences of interactions
between systems and users in a particular environment and related to a particular goal. It is represented
using ellipse. Actor is any external entity that makes use of the system being modeled. It is represented
using stick figure.
DOCUMENTATION OF USE CASE DIAGRAM:
The actors in this use case diagram are customer, vendor
and Database. The use cases are the activities performed by actors.
 CUSTOMER: Customer logins to the particular system and fills the customer details and
places the orders.
 DATABASE: All the details and orders given by customer are updated in the Database.
 VENDOR: Vendor logins and verify the customer orders and the stock details.

DOCUMENTATION OF CLASS DIAGRAM:

This class diagram has three classes’ customer, vendor
and Database.
• Customer – is the class name. Its attributes are username, password, name, phone no and
address. The operations performed in the customer class are login and places the orders.
• Vendor – is the class name. Its attributes are views in the Database.
• Database – is the class name. The operations performed are storing customer details, and their
orders.

DOCUMENTATION OF SEQUENCE DIAGRAM:

• The customer login in to the system and fills the customer details.
• Then the customer places the order. It updated to the Database.
• The vendor login to the system and views the customer orders and the stock details.

5. STATE CHART DIAGRAM:

DOCUMENTATION OF STATE CHART DIAGRAM:

This state diagram describes the behavior of the
system.
• First state is login where the customer login to the system.
• The next state is to fill the customer details.
• And the next state is to place the orders.
• Update Database with the orders and details of customer.

6. ACTIVITY DIAGRAM:
Activity diagrams are graphical representations of workflows of stepwise
activities and actions with support for choice, iteration and concurrency. In the Unified Modeling
Language, activity diagrams can be used to describe the business and operational step-by-step workflows
of components in a system. An activity diagram shows the overall flow of control. An activity is shown as
a rounded box containing the name of the operation.

DOCUMENTATION OF ACTIVITY DIAGRAM:

This activity diagram flow of stepwise activities
performed in stock maintenance system.
• First the customer login then fills the details.
• The customer places the order according to their needs.
• After placing the order, the Database is updated.
• Vendor login to the system and verifies the customer orders and stock details.
•

DOCUMENTATION OF COMPONENT DIAGRAM:

The main component in this component diagram
is stock maintenance systems. And customer Database details and update Database then vendor views the
Database are the Components comes under the main component.

8. DEPLOYMENT DIAGRAM:
A deployment diagram in the unified modeling language serves to model
the physical deployment of artifacts on deployment targets Dependencies are represented by
communication association. The basic element of a deployment diagram is a node of two types:
 DEVICE NODE – A physical computing resource with processing and memory
service to execute software such as a typical computer or a mobile phone.
 EXECUTION ENVIRONMENT NODE - This is a software computing resource
that runs within an outer node and which itself provides a service to host an execute
other executable software.

.
DOCUMENTATION OF DEPLOYMENT DIAGRAM:
The processor in this deployment diagram is the
stock maintenance system which is the main part and the devices are the filling customer details and
placing orders then vendor views which are the some of the main activities performed in the system.

9. PACKAGE DIAGRAM:
Package diagram in unified modeling language 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 and Technical services layer.
• User interface layer - Software objects representing domain concepts that fulfill application
requirements, such as calculation of a sale total.
• Domain Layer - Layer that contains domain objects to handle application logic work
• Technical services Layer - General purpose object and sub system that provide supporting
technical services, such as interfacing with a Database logging
DOCUMENTATION OF PACKAGE DIAGRAM:
The three layers in the stock maintenance system are
• The User interface layer - consists of the web and login. This layer describes how the applicant
logins to the website and places the order.
• The Domain layer – shows the activities that are performed by the customer to place the orders.
• The Technical service layer - the vendor logins and verifies the customer orders and stock
details

RESULT:
Thus, the project stock maintenance system using ArgoUML Software and implement the
software in Java is executed successfully.
EX NO: 5 ONLINE COURSE RESERVATION SYSTEM DATE:

AIM:
To develop a mini-project implementing an interactive ONLINE COURSE RESERVATION
system.

PROBLEM ANALYSIS AND PROJECT PLANNING:

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

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

UML DIAGRAMS:

1. USE CASE DIAGRAM:

A use case is a methodology used in system analysis to identify, clarify, and
organize system requirements. The use case is made up of a set of possible sequences of interactions
between systems and users in a particular environment and related to a particular goal. It is represented
using ellipse. Actor is any external entity that makes use of the system being modeled. It is represented
using stick figure.
DOCUMENTATION FOR USE CASE DIAGRAM:
The use case diagram in the course registration system
illustrates the sequence of steps followed in the system related to the actions of the system.
• Login: This use case gives an entry to the student, professor and the register
• Select College and Course: This use case lists out the various courses offered by the institution
• Submit Grades: This use case given the marks scored by the system
• Maintain Professor Information: This use case maintains the information about professor in the
system.
• Maintain Student Information: This use case maintains the information about the professor in
the system
• Close Registration: This use case describes the certification of the student when he/she finishes
the course.

• The various classes involved in the system are registered student record, professor record all
administration grade and close registration
• The student register for the course
• After the course gets over each student will be asked to write a test
• Test mark are analyzed for the issue grade sheet after certification the registration of the student
in closes.

DOCUMENTATION OF SEQUECE DIAGRAM:

• The single use case in the course registration is taken and sequence of operation followed in the
usecase.
• In the registration for the course use case diagram illustration on the process of registering and
select a course.
• The student enters the institution and gets a catalog about the list of course offered by the system
• The student can select a particular use case and registration for the course
• In the record use case submit grade at the end of each course each student will be asked to write a
test. The result will evaluate for the issue of grade sheet and the grade are submitted.

DOCUMENTATION OF DEPLOYMENT DIAGRAM:

The device node is online course reservation and
execution nodes are course details, login and college details.

RESULT:
Thus, the project Online Course Reservation system using ArgoUML Software and implement the
software in Java is executed successfully.
[Link]: 6 E-TICKETING DATE:

AIM:
To develop a mini project for e-Ticketing.

PROBLEM STATEMENT:
This project enables a user to perform the following operations:
• Online Booking of tickets
• Online cancellation of tickets
• Online Enquiry system
• Online ticket status checking

The booking service accepts the source, destination derails along with the train name and date
of service. According to the availability of tickets, the particular passenger is allocated a seat on the
particular train. The tickets would be displayed in a particular passenger is allocated a seat on the
particular train. The ticket would be displayed in a printable format along with a unique seat number to
differentiate between online ticket reservations.
The cancellation services come in very handy in case of emergency cancellation where in a
passenger who has already booked his tickets can follow easy steps to cancel his ticket. The passenger
specifies his seat no and other unique identification parameter like credit card number and the details are
validated. If found legal, the ticket is cancelled and the transaction with the bank is nullified.
The train schedule and enquiry features of this system enable the user to interactively identify
a suitable configuration of train timings and fares. This module gives the user complete train details and
facilities the passenger to choose a train of his choice.

UML DIAGRAMS:

1. USE CASE DIAGRAM:

DOCUMENTATION OF USE CASE DIAGRAM:

The actors in this use case diagram are
applicant, and E-ticketing Database. The use cases are the activities performed by actors. The
actors in this use case diagram are
• Applicant - logins the E-Ticketing and filling the required data fields.
• E-Ticketing Database-verify the login and filling the details and selected applicant
details are stored in it.
The use cases in this use case diagram are
• Login - applicant enter their username and password to enter in to the E-Ticketing form.
• Filling Details –applicants are used to enter the details in the required form.
• Selecting Flight –it is used to selecting the flight for the applicants.
• Book Ticket –it is used to book the ticket through the E-Ticketing database.
• Search –it is used to search the flight details.
• Cancel Ticket- it is used to cancel the ticket through the E-Ticketing Database

DOCUMENTATION OF CLASS DIAGRAM:

This class diagram has two classes applicant, E-
Ticketing Database.
• Applicant - logins the E-Ticketing and filling the required data fields.
• E-Ticketing Database-verify the login and filling the details and selected applicant
details are stored in it.

3. SEQUENCE DIAGRAM:
A sequence diagram in Unified Modeling Language (UML) is a kind of
interaction diagram that shows how processes operate with one another and in what order. It is a construct
of a Message Sequence Chart. There are two dimensions.
• Vertical dimension-represent time.
• Horizontal dimension-represent different objects.
DOCUMENTATION OF SEQUENCE DIAGRAM:
This sequence diagram describes the
sequence of steps to show:
• Applicants are used to login the form. And then it verifies the username and password.
• If the password and username are correct then applicants are used to login the filling
details.
• Applicants are used to selecting the flights and book the tickets.
• Now the E-Ticketing Database verify the filling Details.
• And then the E-Ticketing Database display the ticket information.
• In case of any sudden change of the plan, the applicant can cancel the ticket.

DOCUMENTATION OF COLLABRATION DIAGRAM:

This collaboration diagram is
to show how the applicant login and register in the E-Ticketing system. Here the sequence is
numbered according to the flow of execution. This collaboration diagram is to show the selection
process of the applicant for the ticket booking. The flow of execution of this selection process is
represented using the numbers.

5. ACTIVITY DIAGRAM:
Activity diagrams are graphical representations of workflows of stepwise
activities and actions with support for choice, iteration and concurrency. In the Unified Modeling
Language, activity diagrams can be used to describe the business and operational step-by-step workflows
of components in a system. An activity diagram shows the overall flow of control. An activity is shown as
a rounded box containing the name of the operation.
DOCUMENTATION OF ACTIVITY DIAGRAM:
This activity diagram describes the behavior
of the system.
• First state is login where the applicant login to the E-Ticketing system.
• The next state is filling details the applicant is used to fill the form.
• Then applicant used to select the flight.
• The applicant appears for book ticket and search details from E-Ticketing Database.
6. DEPLOYMENT DIAGRAM:
A deployment diagram in the unified modeling language serves to model
the physical deployment of artifacts on deployment targets Dependencies are represented by
communication association. The basic element of a deployment diagram is a node of two types:
 DEVICE NODE – A physical computing resource with processing and memory
service to execute software such as a typical computer or a mobile phone.
 EXECUTION ENVIRONMENT NODE - This is a software computing resource
that runs within an outer node and which itself provides a service to host an execute
other executable software.

DOCUMENTATION OF DEPLOYMENT DIAGRAM:

The processor in this deployment
diagram is the E-Ticketing system which is the main part and the devices are the login, appear
for the filling details and selecting flights applicant which are the some of the main activities
performed in the system.

RESULT:
Thus, the project to develop E-ticketing system using ArgoUML Software and to implement the
software in Java was done successfully.

[Link]: 7 SOFTWARE PERSONNEL MANAGEMENT SYSTEM DATE:

AIM:
To develop a project software personnel management system using the Rational Rose Software
from the UML diagram and to implement the software in Java.

PROJECT ANALYSIS AND PROJECT PLANNING:

The software personnel management system is used to manage our personnel things such as
maintaining databases in offices etc. this project is easy for the CEO to handle the details. This is
personally used for CEO.

PROBLEM STATEMENT:
The CEO must enter the name and password to login the form and select the
particular employee to view the details about that employee and maintaining the employee details
personally. This process of software personnel management system are described sequentially through
following steps,
 The CEO login to the software personnel management system.
 He/she search for the list of employees.
 Then select the particular employee.
 Then view the details of that employee.
 After displaying the employee details then logout.

UML DIAGRAMS:

1. USE CASE DIAGRAM:

A use case is a methodology used in system analysis to identify, clarify, and
organize system requirements. The use case is made up of a set of possible sequences of interactions
between systems and users in a particular environment and related to a particular goal. It is represented
using ellipse. Actor is any external entity that makes use of the system being modeled. It is represented
using stick figure.
DOCUMENTATION OF USE CASE DIAGRAM:
The use case diagram in the software personnel
management system illustrates the sequence of sequencing and describing an interaction between a CEO
and a system.
• Login - This use case gives as entry to the CEO and the database.
• List of employees - This will create the situation for the CEO to select particular employee from
the available list.
• Employee details -The CEO can able to view the details of the employee using this use case.

DOCUMENTATION OF CLASS DIAGRAM:

The Classes used in this project are
• CEO: The CEO has to login the form by specifying the name and password of him.
• Database: The database checks whether the CEO has given the name and password accordingly
if not the error message will be displayed.
• Available employees: The database is connected to the list of available employees and the CEO
if wants then select the employee from it.

DOCUMENTATION OF SEQUENCE DIAGRAM:

The CEO must enter his name and password to login the
software personnel management system. The verification process is undergone by the database. If the
details are correct, he can enter to the system otherwise error is displayed. After login the details of the
particular employee is viewed by the CEO. Finally, he is logged out from the system.

4. DEPLOYMENT DIAGRAM:
A deployment diagram in the unified modeling language serves to model
the physical deployment of artifacts on deployment targets Dependencies are represented by
communication association. The basic element of a deployment diagram is a node of two types:
 DEVICE NODE – A physical computing resource with processing and memory
service to execute software such as a typical computer or a mobile phone.
 EXECUTION ENVIRONMENT NODE - This is a software computing resource
that runs within an outer node and which itself provides a service to host an execute
other executable software.
DOCUMENTATION OF DEPLOYMENT DIAGRAM:
The processor in this deployment
diagram is the software personnel management system which is the main part and the devices are
the CEO, database and available employee which are the some of the main activities performed
in the system.

RESULT:
Thus, the project to develop Software personnel system using ArgoUML Software and to
implement the software in Java is done successfully.
[Link]: 8 CREDIT CARD PROCESSING DATE:

AIM:
To develop and identify UML diagram for credit card processing and to implement the software
in Java.

PROBLEM ANALYSIS:
The Credit Card Processing System which is use to purchasing an item from any
shop mall, and it is used to maintain the limitation of credit card balance and current transaction process
could be update via credit card machine. This project mainly used for large amount of item can be easy to
buy from anywhere and required transaction process should be maintained them.

PROBLEM STATEMENT:
To credit card processing first involves checking card number for validation.
The credit card has a credit limit. During billing changes, the credit limit without any penalty. If charge
is more then, credit limit over the limit is accessed when balance increases the credit decreases. At the
end of billing, the billing statement is provided. Billing statement includes balance of the beginning of
billing cycle. It provides details about credit card charges and payments and also credits and fee in the
balance from previous billing cycle while payment and credits are subtracted to come up with current
balance. When the payment is made on the credit card the amount is subtracted from balance. The
balance decreases and the credit increases.

UML DIAGRAMS:

1. USE CASE DIAGRAM:

A use case is a methodology used in system analysis to identify, clarify, and
organize system requirements. The use case is made up of a set of possible sequences of interactions
between systems and users in a particular environment and related to a particular goal. It is represented
using ellipse. Actor is any external entity that makes use of the system being modeled. It is represented
using stick figure.
DOCUMENTATION OF USE CASE DIAGRAM:
The actors in this use case diagram are customer, vendor
and card reader. The use cases are the activities performed by actors. The actors in this use case diagram
are Customer, Vendor, Card reader. The use cases in this use case diagram are:
• Purchase item – customer enter the shop to purchase some item by using credit card payment.
• Bill issue – vendor will make a bill for the selected item.
• Swap the card – vendor will swap the card.
• Make transaction– card reader will process the amount transaction.
• Print the statement – after the transaction, balance amount should be printed.
• Signature – customer should put the signature and give it to vendor.
• Deliver the item–vendor issued to deliver a item.

2. CLASS DIAGRAM:
A class diagram in the unified modeling language (UML) is a type of static
structure diagram that describes the structure of a system by showing the system's classes, their attributes,
and the relationships between the classes. It is represented using a rectangle with three compartments.
Top compartment has the class name, middle compartment the attributes and the bottom compartment
with operations.
DOCUMENTATION OF CLASS DIAGRAM:
The Classes used in this project are:
• Customer – is the class name. Its attributes are name, age, signature, and card number. The
operations performed in the customer class are purchase item and swap the credit card.
• Vendor – is the class name. Its attributes are name, address, and phone number. The operations
performed are making bill and then delivered item purchased by the customer.
• Card Reader – is the class name. Its attributes are machine number, software and company. The
operations performed are making the transaction and print balance statement.

DOCUMENTATION OF SEQUENCE DIAGRAM:

The customer wants to purchase some item
from the shop; Vendor makes a bill for the selected item. The Customer gives the credit card to
the vendor to the swap the card. The further transaction is proceeding for if the credit card is
validated. Vendor will issue the required balance statement to the customer. Customer put the
signature in the receipt and returns the one copy of statement to the vendor.

DOCUMENTATION OF ACTIVITY DIAGRAM:

The customer’s activity should contain an purchase item
by using credit card and then his referred to check the current transaction processing its completed or not.
The vendor should issue a bill copy to the customer and its swap the card to make amount transaction by
using card reader. The vendor should give required statement to customer will deliver the item from the
shop.

DOCUMENTATION OF DEPLOYMENT DIAGRAM:

The processor in this deployment diagram is the credit
card processing system which is the main part and the devices are the purchase item, swap the card, make
transaction, verify signature, delivery item which are the some of the main activities performed in the
system.

RESULT:
Thus, the project to develop Credit Card system using ArgoUML Software and to implement the
software in Java is done successfully.
[Link]: 9 E-BOOK MANAGEMENT SYSTEM DATE:

AIM:
The aim of the project is to implement the E-book management [Link] enables case of
purchasing,searching and managing the books online.

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

PROBLEM STATEMENT:
 Product perspective - The ebook system is a package to be used by any random user of internet
who wants to buy or sells his books online to improve the efficiency and frustrations of him
buying or selling the same book office. The system provides books catalog and information to
users and helps them decide on the books to buy from the E-book website. The Website
administrator can keep the books catalog updated all the time so that the users get the updated
information all the time.
 Product Functions - The E-book System provides real time information about the books
available in the E-book and the user information. The Product functions are more or less the same
as described in the product perspective.
1. The member should be provided with the updated information about the books catalog.
2. Provisions for the users to buy the books they want, if all athe other required rules hold good.
3. The member is given a provision to check his account information and change the account
information any time in the given valid period.

UML DIAGRAMS:

1. USE CASE DIAGRAM:

A use case is a methodology used in system analysis to identify, clarify, and
organize system requirements. The use case is made up of a set of possible sequences of interactions
between systems and users in a particular environment and related to a particular goal. It is represented
using ellipse. Actor is any external entity that makes use of the system being modeled. It is represented
using stick figure.
DOCUMENTATION OF USE CASE DIAGRAM:
The actors in this use case diagram are Supplier, Store
Keeper and Database. The use cases are the activities performed by actors.
• The website will give the books available.
• Customer will login and check the list of e-books in the database.
• The database will be updated according to the purchase done and it will be up to date.
• The use cases in the use case diagram are Quotation & Purchase, login, stock, purchase.
• Select books will gives us the status of the purchasing order details
• Login will give us the entry for the customer of this project.
• Database will give us the details about the total e-book available.
• Purchase will give us the details about the details and the history of e-books purchased.

DOCUMENTATION OF CLASS DIAGRAM:

This class diagram has three classes applicant, recruiter
and database.
• Customer – is the class name. Its attributes are name, address and cont no. The operations
performed in the Supplier class are get order, supply goods and get money.
• Books – is the class name. Its attributes are operating system, computer architecture, DBMS,
web technology and OOAD. The operations performed are select and buy.
• Database – is the class name. Its attribute is operation. The operations performed is store.

DOCUMENTATION OF SEQUENCE DIAGRAM:

• The Customer enters the E-book website.
• The list of books available are listed.
• Customer checks the book list.
• Database provides user id and pass.
• Customer selects the book.
• Pay money to the Website.

4. COLLABORATION DIAGRAM:
A collaboration diagram, also called a communication diagram or
interaction diagram. A sophisticated modeling tool can easily convert a collaboration diagram into a
sequence diagram and the vice versa. A collaboration diagram resembles a flowchart that portrays the
roles, functionality and behavior of individual objects as well as the overall operation of the system in real
time.
DOCUMENTATION OF COLLABORATION DIAGRAM:
The first collaboration diagram is to show how
the customer login and getting details of e-books in the e-book management system. Here the sequence is
numbered according to the flow of execution.
5. ACTIVITY DIAGRAM:
Activity diagrams are graphical representations of workflows of stepwise
activities and actions with support for choice, iteration and concurrency. In the Unified Modeling
Language, activity diagrams can be used to describe the business and operational step-by-step workflows
of components in a system. An activity diagram shows the overall flow of control. An activity is shown as
a rounded box containing the name of the operation.

DOCUMENTATION OF ACTIVITY DIAGRAM:

This activity diagram flow of stepwise activities
performed in recruitment system.
• First Customer login then checks books available.
• The book list is verified and is given in an ordered format.
• The needed book is selected.
• Enter your account details and purchase the book.
6. DEPLOYMENT DIAGRAM:
A deployment diagram in the unified modeling language serves to model
the physical deployment of artifacts on deployment targets Dependencies are represented by
communication association. The basic element of a deployment diagram is a node of two types:
 DEVICE NODE – A physical computing resource with processing and memory
service to execute software such as a typical computer or a mobile phone.
 EXECUTION ENVIRONMENT NODE - This is a software computing resource
that runs within an outer node and which itself provides a service to host an execute
other executable software.

DOCUMENTATION OF DEPLOYMENT DIAGRAM:

The processor in this deployment diagram is the
online recruitment system which is the main part and the devices are the select and payment which are the
some of the main activities performed in the system.

RESULT:
Thus, the project to develop E-book system using ArgoUML Software and to implement the
software in Java is done successfully.
[Link]: 10 RECRUITMENT SYSTEM DATE:

AIM:
To develop a project on recruitment system using ArgoUML Software and to implement the
project in Java.

PROBLEM ANALYSIS AND PROJECT PLANNING:

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

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

UML DIAGRAMS:

1. USE CASE DIAGRAM:

A use case is a methodology used in system analysis to identify, clarify, and
organize system requirements. The use case is made up of a set of possible sequences of interactions
between systems and users in a particular environment and related to a particular goal. It is represented
using ellipse. Actor is any external entity that makes use of the system being modeled. It is represented
using stick figure.
DOCUMENTATION OF USE CASE DIAGRAM:
The actors in this use case diagram are applicant,
recruiter and database. The use cases are the activities performed by actors.
The actors in this use case diagram are Student, HR, Admin.
The use cases in this use case diagram are
 Login – student enter their username and password to enter in to the recruitment system
 View – student can view the list of students who got recruited.
 Edit– HR can refine the students in each round.
 Validate – student appears for the test.
 New fields – based on the outcome of test talented student is selected.
 Specify requirements – hr select the students based on their capability.

2. CLASS DIAGRAM:
A class diagram in the unified modeling language (UML) is a type of static
structure diagram that describes the structure of a system by showing the system's classes, their attributes,
and the relationships between the classes. It is represented using a rectangle with three compartments.
Top compartment has the class name, middle compartment the attributes and the bottom compartment
with operations.
DOCUMENTATION OF CLASS DIAGRAM:
This class diagram has three classes student, HR and Admin.
 student – is the class name. Its attributes are username, password, name, phone no and address.
The operations performed in the applicant class are login, register and giving applicant details.
 HR– is the class name. Its attributes are name, designation, phone no, marks in apps and marks in
technical. The operations performed are selecting applicants based on apps and technical.
 Admin – is the class name. The operations performed are storing applicant details, verifying
login and storing selected applicant details.

3. COLLABORATION DIAGRAM:
A collaboration diagram, also called a communication diagram or interaction diagram. A
sophisticated modeling tool can easily convert a collaboration diagram into a sequence diagram and the
vice versa. A collaboration diagram resembles a flowchart that portrays the roles, functionality and
behavior of individual objects as well as the overall operation of the system in real time.

DOCUMENTATION OF COLLABORATION DIAGRAM:

This collaboration diagram is to show how the student login and register in the
recruitment system. Here the sequence is numbered according to the flow of execution. This collaboration
diagram is to show the selection process of the applicant for the job. The flow of execution of this
selection process is represented using the numbers.

4. ACTIVITY DIAGRAM:
Activity diagrams are graphical representations of workflows of stepwise activities and
actions with support for choice, iteration and concurrency. In the Unified Modeling Language, activity
diagrams can be used to describe the business and operational step-by-step workflows of components in a
system. An activity diagram shows the overall flow of control. An activity is shown as a rounded box
containing the name of the operation.
DOCUMENTATION OF ACTIVITY DIAGRAM:
This activity diagram flow of stepwise activities performed in recruitment
system.
 First the student login then registers.
 The student details are verified and interview details are send to student by hr.
 Students appear for test.
 HR select talented student.
 Update the selected student details in the database.

5. DEPLOYMENT DIAGRAM:
A deployment diagram in the unified modeling language serves to model the physical
deployment of artifacts on deployment targets Dependencies are represented by communication
association. The basic element of a deployment diagram is a node of two types:
 DEVICE NODE – A physical computing resource with processing and memory
service to execute software such as a typical computer or a mobile phone.
 EXECUTION ENVIRONMENT NODE - This is a software computing resource
that runs within an outer node and which itself provides a service to host an execute
other executable software.
DOCUMENTATION OF DEPLOYMENT DIAGRAM:
The processor in this deployment diagram is the
online recruitment system which is the main part and the devices are the register, appear for test and
select talented applicant which are the some of the main activities performed in the system.

RESULT:
Thus, the project to develop recruitment system using ArgoUML Software and to implement the software
in Java was done successfully.

[Link]: 11 FOREIGN TRADING SYSTEM DATE:

AIM:
To design a project Foreign Trading System using ArgoUML Software and to implement the
software in Java.

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

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

UML DIAGRAMS:

1. USE CASE DIAGRAM:

DOCUMENTATION OF USE CASE DIAGRAM:

The actors in this use case diagram are customer,
administrator and database. The use cases are the activities that are represented in the ellipse.
 Trader logins the foreign trading system and perform the sourcing to select the
required commodities and places the order.
 The administrator checks for ordered commodities, after the commodities are ready trader pays
the amount.
 The administrator provides the items along with the bill.
 The database stores the all the details and updates it whenever there is a change in any part of the
trading process.

2. CLASS DIAGRAM:
A class diagram in the unified modeling language (UML) is a type of static
structure diagram that describes the structure of a system by showing the system's classes, their attributes,
and the relationships between the classes. It is represented using a rectangle with three compartments.
Top compartment has the class name, middle compartment the attributes and the bottom compartment
with operations.
DOCUMENTATION OF CLASS DIAGRAM:
A class diagram in the unified modeling language
(UML) is a type of static structure diagram that describes the structure of a system by showing the
system's classes, their attributes, and the relationships between the classes. It is represented using a
rectangle with three compartments. Top compartment has the class name, middle compartment the
attributes and the bottom compartment with operations.

DOCUMENTATION OF SEQUENCE DIAGRAM:

A sequence diagram in Unified Modeling Language
(UML) is a kind of interaction diagram that shows how processes operate with one another and in what
order. It is a construct of a Message Sequence Chart. There are two dimensions.
 Vertical dimension-represent time.
 Horizontal dimension-represent different objects.

DOCUMENTATION OF COLLABORATION DIAGRAM:

A collaboration diagram, also called a
communication diagram or interaction diagram. A sophisticated modeling tool can easily convert a
collaboration diagram into a sequence diagram and the vice versa. A collaboration diagram resembles a
flowchart that portrays the roles, functionality and behavior of individual objects as well as the overall
operation of the system in real time.

DOCUMENTATION OF DEPLOYMENT DIAGRAM:

The processor in this deployment diagram is the
stock maintenance system which is the main part and the devices are the filling customer details and
placing orders then vendor views which are the some of the main activities performed in the system.

RESULT:
Thus, the project to develop Foreign Trading system using ArgoUML Software and to implement
the software in Java was done successfully.

[Link]: 12 CONFERENCE MANAGEMENT SYSTEM DATE:

AIM:
To develop a project on Conference management system using ArgoUMLSoftware and to
implement the project in Java.

PROBLEM ANALYSIS AND PROJECT PLANNING:

The Conference Management System is an
online website in which candidate can submit the paper and register themselves and then attend the
conference. The paper will be reviewed. The details of the conference, date and time will be made
available to them through the website. After getting the confirmation details the candidate should submit
the revised and camera-ready paper. Then the registration process will be done.

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

UML DIAGRAMS:

1. USE CASE DIAGRAM:

DOCUMENTATION OF USE CASE DIAGRAM:

The actors in this use case diagram are candidate,
reviewer and database. The use cases are the activities performed by actors. The actors in this use case
diagram are Candidate, Reviewer, Databases. The use cases in this use case diagram are:
 Login - Candidate enter their username and password to login to the conference system.
 Paper submission – Candidate submits the paper.
 Review the paper– The paper is been reviewed by the reviewer and the paper is selected.
 Paper confirmation details – The reviewer can send the confirmation details to the candidate.
 Revised and camera-ready paper – After the paper is selected and the camera ready paper
should be submitted to the reviewer by candidate.
 Registration – After submitting the revised paper the candidate wants to register.

2. CLASS DIAGRAM:
A class diagram in the unified modeling language (UML) is a type of static
structure diagram that describes the structure of a system by showing the system's classes, their attributes,
and the relationships between the classes. It is represented using a rectangle with three compartments.
Top compartment has the class name, middle compartment the attributes and the bottom compartment
with operations.
DOCUMENTATION OF CLASS DIAGRAM:
This class diagram has three classes candidate, reviewer
and database.
 Candidate – Its attributes are name, college name, department, paper title. The operations
performed in the candidate class are login, submit the paper, submit revised and camera-ready
paper and registration.
 Reviewer – Its attributes are name, department, reviewer ID The operations performed are review
the paper and send the paper confirmation details.
 Database –The operations performed are storing candidate details and verifying login

DOCUMENTATION OF SEQUENCE DIAGRAM:

This sequence diagram describes the sequence of steps
to show
 The candidate login in to the conference system and register for job.
 The verification done in the database.
 The candidate should submit the paper.
 The reviewer reviews the paper and sends acknowledgement to the candidate.
 The candidate submits revised and camera-ready paper.
 This candidate will register their details.
4. DEPLOYMENT DIAGRAM:
A deployment diagram in the unified modeling language serves to model
the physical deployment of artifacts on deployment targets Dependencies are represented by
communication association. The basic element of a deployment diagram is a node of two types:
 DEVICE NODE – A physical computing resource with processing and memory
service to execute software such as a typical computer or a mobile phone.
 EXECUTION ENVIRONMENT NODE - This is a software computing resource
that runs within an outer node and which itself provides a service to host an execute
other executable software.

DOCUMENTATION OF DEPLOYMENT DIAGRAM:

The processor in this deployment diagram is the
conference management system which is the main part and the devices are the candidate, appear for do
conference, reviewer will review the paper, database will store all details which are the some of the main
activities performed in the system.

RESULT:
Thus, the mini project for Conference Management System has been developed and executed
successfully.
[Link]: 13 BPO MANAGEMENT SYSTEM Date:

AIM:
To develop a project Business Process Outsourcing(BPO) management system Using ArgoUML
software and to implement the software in Java.

PROBLEM ANALYSIS AND PROJECT PLANNING:

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

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

UML DIAGRAMS:

1. USE CASE DIAGRAM:

DOCUMENTATION OF USE CASE DIAGRAM:

The actors in this use case diagram are Process agent, Customer and Database. The use
cases are the activities performed by actors.
 PROCESS AGENT: The ultimate Goal of the process agent is to make sale. The operation
performed by him/her is he/she will first call the customer then pitches there are product for sale.
If the customer is interested the agents mark it has a sale else disconnects the call and moves to
another customer.
 DATABASE: The database is neither a computer nor a memory where all the customers’ details
will be stored. It consists of the customer name, customer address, and customer phone number.
Further details of the customer can also be added in the future by the agent.
 CUSTOMER: Customer plays a vital role in the BPO industry. Agent calls the customer from
the database. Once the call gets connected and the customer is happy with the product which is
pitched by the agent then he/she will show interest for buying the product else he/she will reject
the product and disconnect the call.

2. CLASS DIAGRAM:
A class diagram in the unified modeling language (UML) is a type of static
structure diagram that describes the structure of a system by showing the system's classes, their attributes,
and the relationships between the classes. It is represented using a rectangle with three compartments.
Top compartment has the class name, middle compartment the attributes and the bottom compartment
with operations.
DOCUMENTATION OF CLASS DIAGRAM:
This class diagram has three classes process agent, customer and
database.
 Agent – is the class name. Its attributes are username, password, name, phone no and address.
The operations performed by the agent class are login, giving details to customer and selling the
product.
 Customer – is the class name. Its attributes are name, phone no, address. The operations
performed are attending the call, asks about the product.
 Database – is the class name. The operations performed are storing customer details, verifying
login and updating the customer details.

DOCUMENTATION OF SEQUENCE DIAGRAM:

 Agent fetches the data from the database
 database provides the details of the customer to agent and agent dials to the customer.
 Customer responds to the agent and agent pitches his/her product.
 If necessary, customer buys else discards.
 Agent updates the call history and proceeds with another call.

DOCUMENTATION OF DEPLOYMENT DIAGRAM:

The processor in this deployment diagram is the
BPO management system which is the main part and the devices are the agent, customer and to sell the
product to the customer are the main activities performed in the system.

RESULT:
Thus, a mini project for BPO Management System using java and netbeans is created and
executed.
EX NO:14 LIBRARY MANAGEMENT SYSTEM DATE:

AIM:
To develop a project of Library management system using ArgoUML Software and to implement
the software in Java.

PROBLEM ANALYSIS AND PROJECT DESIGN:

The library management system is software in which a
member can register themselves and then he can borrow books from the library. It mainly concentrates on
providing books for engineering students. The process of members registering and purchasing books from
the library are described sequentially through following steps: First the member registers himself if he
was new to the library. Old members will directly select old member button. They select their
corresponding year. After selecting the year, they fill the necessary details and select the book.

SOFTWARE REQUIREMENT SPECIFICATION:

[Link]. CONTENTS
1 INTRODUCTION
2 OBJECTIVE
3 OVERVIEW
4 GLOSSARY
5 PURPOSE
6 SCOPE
7 FUNCTIONALITY
8 USABILITY

1. INTRODUCTION:
This system would be used by members who are students of any college to check the
availability of the books and borrow the books, and then the Databases are updated. The purpose of this
document is to analyze and elaborate on the high-level needs and features of the library management
system. It also tells the usability, reliability defined in use case specification.

2. OBJECTIVE:
The main objective of the system is to design an online book-bank monitoring system to
enable a central monitoring mechanism of the book-bank be faster and less error prone. Apart from this,
help the students acquire the right books for the syllabus at the right time, ensure availability of basic
textbooks to students against limited funds and develop students’ ability to handle property loaned to
them.

3. OVERVIEW:
The overview of this project is to design a tool for library so that it can be used by any
library to lend their books as well as colleges.

4. GLOSSARY:

TERMS DESCRIPTION
MEMBER The one who registers himself and purchase books from the bank.
DATABASE Database is used to store the details of members and books.
ADMINISTRATOR The one who verifies the availability of book and issue them.
USER Member
SOFTWARE REQUIREMENT This software specification documents full set of features and function
SPECIFICATION Library management system that is performed in company website.

5. PURPOSE:
The purpose of the library management system is to reduce the manual intervention.

6. SCOPE:
The scope of this library management system is to act as a tool for library administrator for quick
reference, availability of the books.

7. FUNCTIONALITY:
Many members will be waiting to take the book from the library at a single day.

8. USABILITY:
User interface makes the library management system to be efficient. That is the system
will help the member to register easily and helps them to get their books easily. The system should be
user friendly.

UML DIAGRAMS:

[Link] CASE DIAGRAM:

DOCUMENTATION OF CLASS DIAGRAM:

This class diagram has 8 classes:
 Member details class - Its attributes are name, father name, date of birth, address,
phone number, member id, college, degree, course and semester.
 Administrator – Its attributes are name, address, phone, id
 Year – Its attribute is select year.
 Issue for 1st year – Its attributes are member name, member id, book code, book
name.
 Issue for 2nd year – Its attributes are member name, member id, book code, book
name.
 Issue for 3rd year – Its attributes are member name, member id, book code, book
name.
 Issue for 4th year – Its attributes are member name, member id, book code, book
name.
 Database – Its attribute is name.

DOCUMENTATION OF SEQUENCE DIAGRAM:

The sequence diagram describes the sequence of steps to
show
• The member registers himself in book bank
• He will select the year
• He selects the books given and the Database will update the status of book.
• Then administrator will log in and verify the status of books.
• If the book is available, he will issue the book.

DOCUMENTATION OF ACTIVITY DIAGRAM:

This activity diagram flow of stepwise activities
performed in library management system.
• The member registers himself in library
• After that he will select the year.
• He will select the books.
• Database will update the status of book.

6. COMPONENT DIAGRAM:
The component diagram is represented by figure dependency and it is a graph of
design of figure dependency. 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.
DOCUMENTATION OF COMPONENT DIAGRAM:
The main component in this component diagram
is online library management systems. And member details, issue for first year, issue for second year
issue for third year and issue for fourth year are components comes under the main component.

7. PACKAGE DIAGRAM:
Package diagram in unified modeling language 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 and Technical services layer.
• User interface layer - Software objects representing domain concepts that fulfill application
requirements, such as calculation of a sale total.
• Domain Layer - Layer that contains domain objects to handle application logic work
• Technical services Layer - General purpose object and sub system that provide supporting
technical services, such as interfacing with a Database logging

DOCUMENTATION OF PACKAGE DIAGRAM:

The three layers in the package diagram of Library
management system are:
• The User interface layer - consists of the web and member details. This layer
describes how the member goes to library and registers himself.
• The Domain layer – shows the activities that are performed in the library
management system. The activities are register and book issues.
• The Technical service layer - the member details and verification details are
stored in the Database.

RESULT:
Thus, the project to develop library management system using ArgoUML Software and to
implement the software in Java was done successfully.

[Link]: 15 STUDENT INFORMATION SYSTEM DATE:

AIM:
The aim of the project is to implement the Student Information [Link] enables ease of
purchasing, searching and managing the student details online.

PROBLEM ANALYSIS:
Student Information system gives an idea about how details about the student are
maintained in the particular websites. The student personal details, results and attendance are maintained
here. Further some additional details of the current books that is available in the store are also given.
Student information system in this project is done in an authorized way. The password and user id have
been set here.

PROBLEM STATEMENT:
• Student details can be added.
• Student details can be updated if needed details.
• They can access their attendance details
• They can verify or check their personnel as well as result details.

UML DIAGRAMS:

1. USE CASE DIAGRAM:

3. SEQUENCE DIAGRAM:
A sequence diagram in Unified Modeling Language (UML) is a kind of
interaction diagram that shows how processes operate with one another and in what order. It is a construct
of a Message Sequence Chart. There are two dimensions.
• Vertical dimension-represent time.
• Horizontal dimension-represent different objects.
4. DEPLOYMENT DIAGRAM:
A deployment diagram in the unified modeling language serves
to model the physical deployment of artifacts on deployment targets Dependencies are represented by
communication association. The basic element of a deployment diagram is a node of two types:
 DEVICE NODE – A physical computing resource with processing and memory
service to execute software such as a typical computer or a mobile phone.
 EXECUTION ENVIRONMENT NODE - This is a software computing resource
that runs within an outer node and which itself provides a service to host an execute
other executable software.

RESULT:
Thus, the project to develop Student Information System system using ArgoUML Software and
to implement the software in Java is done successfully.
EX. NO: 16 (ADDITIONAL) ATM SYSTEM DATE:

AIM:
To implement the ATM System.

ALGORITHM:

1. ALGORITHM FOR USE CASE DIAGRAM:

Step1: Identify the Actors and Use cases.

In the system, the actors and use cases are:
• Actors: User, System and Database.
• Use cases: Login, Deposit, withdrawal, updation, balance enquiry
Step2: Build the relationship between actors and Use cases.

Use case diagram for the ATM System

2. ALGORITHM FOR SEQUENCE DIAGRAM:

Step1: Identify the objects. In this System, the objects are: User, System and Database.
Step2: Identify the sequence of events.
Step3: Login to the system to check the validity.
Step4: Select the option in the system.
Step5: For the user to deposit or withdraw the amount, they should enter the option in the
System.
Step6: The System will do the corresponding processing with proper Updation in the Database.
Step7: Finally, the balance is displayed to the user.

Sequence diagram for ATM System

3. ALGORITHM FOR CLASS DIAGRAM:

Step1: Create class diagram for each identified object under sequence diagram. Identified objects are:
• User
• System
• Database
Step2: Class diagram for each object is divided into three parts.
• Top portion represents the Class name.
• Middle portion represents the Attributes.
• Bottom portion represents the methods.

Class diagram for ATM system

PROCEDURE TO WRITE THE SOFTWARE FOR THE ATM SYSTEM USING RATIONAL
ROSE SOFTWARE TOOL:

1. Click start->Rational Software->Rational Rose Enterprise Edition.

2. In the Create New model window select VB6 Standard Framework->A screen appears;
select the untitled project from the browser window and save it.
3. Right Click the use case view->New->Use case diagram->Sequence diagram->class diagram
(name and save the files)
4. Click use case diagram->using the tool box build the use case diagram.
5. Click sequence diagram->using the tool box build the sequence diagram.
6. Click class diagram->using the tool box build the class diagram.
7. Right click Component view->component diagram->Open specification->select the Stereotype
as DLL->Select the language as Visual Basic->Switch from General tab to Realize tab->Select
the classes you created in class diagram->right click->Assign->Ok.
8. Right click component view->update code from model->the tool window for converting
diagrams to code appears->next->Finish->the skeleton code in VB is generated
automatically for the class diagram.

CODINGS:

1. PINPROCESS CODING:

Dim DB As Database
Dim RS As Recordset
Dim A As Integer
Private Sub Command1_Click()
A = Val([Link])
[Link]
While (True)
If Val(A) = Val(RS(3)) Then
[Link]
GoTo AA
Else
[Link]
End If
If [Link] = True Then
MsgBox "YOUR PIN NUMBER IS WRONG"
GoTo AA
End If
Wend
AA:
End Sub

Private Sub Form_Load()

Set DB = OpenDatabase("E:\atm\[Link]")
Set RS = [Link]("CUSDET")
End Sub

2. DISPLAY CODING:

Dim DB As Database
Dim RS As Recordset
Private Sub Command1_Click()
[Link]
While (True)
If Val([Link]) = Val(RS(3)) Then
[Link]
GoTo AA
Else
[Link]
End If
Wend
AA:
End Sub

Private Sub Command2_Click()

[Link]
End Sub

Private Sub Command3_Click()

[Link]
End Sub

Private Sub Command4_Click()

[Link]
End Sub

Private Sub Command6_Click()

[Link]
End Sub
Private Sub Form_Load()
Set DB = OpenDatabase("E:\atm\[Link]")
Set RS = [Link]("CUSDET")
[Link]
While (True)
If Val([Link]) = Val(RS(3)) Then
[Link] = RS(2)
GoTo AA
Else
[Link]
End If
Wend
AA:
End Sub

3. BALANCE ENQUIRY CODING:

Dim DB As Database
Dim RS As Recordset
Private Sub Command1_Click()
Unload Me
[Link]
[Link] = ""
[Link]
End Sub

Private Sub Command3_Click()

[Link]
End Sub

Private Sub Form_Load()

Set DB = OpenDatabase("E:\atm\[Link]")
Set RS = [Link]("CUSDET")
[Link]
While (True)
If Val([Link]) = Val(RS(3)) Then
[Link] = RS(4)
[Link] = RS(5)
GoTo AA
Else
[Link]
End If
Wend
AA:
End Sub

4. WITHDRAW CODING:

Dim DB As Database
Dim RS As Recordset
Dim B As Double

Private Sub Command1_Click()

B=0
B = Val([Link])
[Link]
While (True)
If Val([Link]) = Val(RS(3)) Then
If (Val(B) > Val(RS(4))) Then
MsgBox "YOUR BALANCE IS LOW"
[Link] = ""
[Link]
GoTo BB
Else
MsgBox "TAKE YOUR CASH "
[Link] = ""
B = Val(RS(4)) - Val(B)
[Link]
RS(4) = Val(B)
RS(5) = Val(RS(4))
[Link]
GoTo AA
End If
Else
[Link]
End If
Wend
AA:
BB:
[Link]
[Link] = ""
[Link]
End Sub

Private Sub Command2_Click()

[Link] = ""
[Link]
End Sub

Private Sub Form_Load()

Set DB = OpenDatabase("E:\atm\[Link]")
Set RS = [Link]("CUSDET")
[Link] = ""
End Sub

5. MOBILE NUMBER CHANGE CODING:

Dim DB As Database
Dim RS As Recordset
Dim B As Double
Private Sub Command1_Click()
B=0
B = Val([Link])
[Link]
While (True)
If Val([Link]) = Val(RS(3)) Then
If (Val(B) > Val(RS(4))) Then
MsgBox "YOUR BALANCE IS LOW"
[Link] = ""
[Link]
GoTo BB
Else
MsgBox "TAKE YOUR CASH "
[Link] = ""
B = Val(RS(4)) - Val(B)
[Link]
RS(4) = Val(B)
RS(5) = Val(RS(4))
[Link]
GoTo AA
End If
Else
[Link]
End If
Wend
AA:
BB:
[Link]
[Link] = ""
[Link]
End Sub
Private Sub Command2_Click()
[Link]
End Sub

Private Sub Form_Load()

Set DB = OpenDatabase("E:\atm\[Link]")
Set RS = [Link]("CUSDET")
[Link] = ""
End Sub

6. PIN NUMBER CHANGE CODING:

Dim DB As Database
Dim RS As Recordset
Private Sub Command1_Click()
[Link]
While (True)
If Val([Link]) = Val(RS(3)) Then
MsgBox "PIN ALREADY EXIST"
[Link] = ""
GoTo BB

Else
[Link]
End If
If [Link] = False Then
GoTo CC
End If
Wend
CC:
[Link]
While (True)
If Val([Link]) = Val(RS(3)) Then
[Link]
RS(3) = Val([Link])
[Link] = Val([Link])
[Link]
MsgBox "YOUR PIN NO WILL BE CHANGE"
[Link] = ""
GoTo AA
Else
[Link]
End If
Wend
AA:
[Link]
[Link] = ""
Unload Me
BB:
End Sub

Private Sub Command2_Click()

[Link] = ""
[Link]
End Sub

Private Sub Form_Activate()

[Link]
While (True)
If Val([Link]) = Val(RS(3)) Then
[Link] = RS(3)
GoTo AA
Else
[Link]
End If
Wend
AA:
End Sub

Private Sub Form_Load()

Set DB = OpenDatabase("E:\atm\[Link]")
Set RS = [Link]("CUSDET")
End Sub

OUTPUT:

1. PIN NUMBER PROCESS FORM:

2. MENU FORM:

3. BALANCE ENQUIRY FORM:

4. WITHDRAW FORM:
5. PIN NUMBER CHANGE FORM:

6. MOBILE NUMBER CHAGE FORM:

7. CHECK YOUR BALANCE FORM:

8. CHECK YOUR PIN NUMBER:

RESULT:
Thus, the above program has been successfully completed.

Passport Automation System Project Guide
No ratings yet
Passport Automation System Project Guide
114 pages
Ex 1-3
No ratings yet
Ex 1-3
28 pages
Passport Automation System Overview
No ratings yet
Passport Automation System Overview
271 pages
Passport Automation System Overview
No ratings yet
Passport Automation System Overview
196 pages
Se r18 Lab Manual
100% (2)
Se r18 Lab Manual
145 pages
Cycle1 Lab Record
No ratings yet
Cycle1 Lab Record
41 pages
Passport Automation System Overview
0% (1)
Passport Automation System Overview
42 pages
Book Bank System UML Diagrams
No ratings yet
Book Bank System UML Diagrams
49 pages
Ooad Lab Manual
No ratings yet
Ooad Lab Manual
224 pages
Passport Automation System Project Guide
No ratings yet
Passport Automation System Project Guide
323 pages
Passport Automation System Overview
No ratings yet
Passport Automation System Overview
150 pages
Passport Automation System Project Report
No ratings yet
Passport Automation System Project Report
178 pages
Software Engineering Lab Manual r20 Batch
No ratings yet
Software Engineering Lab Manual r20 Batch
237 pages
Passport Automation System Lab Manual
No ratings yet
Passport Automation System Lab Manual
350 pages
1 Passport Automation System PDF
0% (1)
1 Passport Automation System PDF
22 pages
Passport Automation System Overview
No ratings yet
Passport Automation System Overview
59 pages
Arunai Engineering College: Department of Computer Science & Engineering
No ratings yet
Arunai Engineering College: Department of Computer Science & Engineering
132 pages
1 Passport Automation System Srs Use Case Diagram Uml Diagrams Class Diagrams
No ratings yet
1 Passport Automation System Srs Use Case Diagram Uml Diagrams Class Diagrams
37 pages
Ccs356 Oose Manual
No ratings yet
Ccs356 Oose Manual
157 pages
Passport Automation System SRS Document
No ratings yet
Passport Automation System SRS Document
132 pages
OOAD Lab Manual for Passport System
No ratings yet
OOAD Lab Manual for Passport System
221 pages
Passport Automation System Overview
No ratings yet
Passport Automation System Overview
37 pages
Ccs356 Oose Lab Manual-1
No ratings yet
Ccs356 Oose Lab Manual-1
168 pages
Passport Automation System
0% (1)
Passport Automation System
16 pages
Passport Automation System Overview
No ratings yet
Passport Automation System Overview
269 pages
Passport System UML Analysis
No ratings yet
Passport System UML Analysis
25 pages
CSE Case Tools Lab Manual
No ratings yet
CSE Case Tools Lab Manual
225 pages
Passport Automation System F
No ratings yet
Passport Automation System F
22 pages
Passport Automation System Overview
No ratings yet
Passport Automation System Overview
16 pages
Passport Automation System Guide
No ratings yet
Passport Automation System Guide
17 pages
Passportautomationsystem
No ratings yet
Passportautomationsystem
23 pages
Passport Automation System SRS Document
No ratings yet
Passport Automation System SRS Document
170 pages
Passport Automation System
No ratings yet
Passport Automation System
13 pages
Se Manual r22
No ratings yet
Se Manual r22
104 pages
Oo Lab
No ratings yet
Oo Lab
327 pages
Passport Automation System
33% (6)
Passport Automation System
14 pages
Passport Automation System Overview
No ratings yet
Passport Automation System Overview
138 pages
Passport Service System
No ratings yet
Passport Service System
23 pages
SRS for Passport & Library Systems
No ratings yet
SRS for Passport & Library Systems
9 pages
OOAD Lab Manual for CS2357 Course
No ratings yet
OOAD Lab Manual for CS2357 Course
240 pages
Passport Automation System - F
No ratings yet
Passport Automation System - F
16 pages
Software Engineering Lab Syllabus CSE
No ratings yet
Software Engineering Lab Syllabus CSE
180 pages
Passport Automation System
No ratings yet
Passport Automation System
18 pages
Object Oriented Design Lab Record
No ratings yet
Object Oriented Design Lab Record
225 pages
Cs8582-Object Oriented Analysisand Design Laboratory-46023968-Cs8582 - Ooad Lab (1) - Removed
No ratings yet
Cs8582-Object Oriented Analysisand Design Laboratory-46023968-Cs8582 - Ooad Lab (1) - Removed
10 pages
Case Tools Laboratory Lab Manual
No ratings yet
Case Tools Laboratory Lab Manual
281 pages
Passport Automation System Srs PDF
67% (3)
Passport Automation System Srs PDF
5 pages
R-2021 Ooad Lab Manual
No ratings yet
R-2021 Ooad Lab Manual
126 pages
Oose Ex2
No ratings yet
Oose Ex2
2 pages
Ooad Lab Manual
No ratings yet
Ooad Lab Manual
20 pages
OOSE Ex7
No ratings yet
OOSE Ex7
10 pages
Passport Automation System UML Diagrams
No ratings yet
Passport Automation System UML Diagrams
131 pages
Oose Record
No ratings yet
Oose Record
131 pages
Passport Automation System Case Study
No ratings yet
Passport Automation System Case Study
97 pages
Passport Management System VB Projects
67% (6)
Passport Management System VB Projects
7 pages
Millennials' Ethics and Cultural Identity
No ratings yet
Millennials' Ethics and Cultural Identity
4 pages
The Burgess Urban Land Use Model
0% (1)
The Burgess Urban Land Use Model
5 pages
LSGS Full Test Paper for PSC Exam
No ratings yet
LSGS Full Test Paper for PSC Exam
79 pages
Chapter 1 and 2
No ratings yet
Chapter 1 and 2
47 pages
2024 Banking Tech Conference Awards
No ratings yet
2024 Banking Tech Conference Awards
46 pages
Atlas II AS7-D-H Clan Assault Mech
No ratings yet
Atlas II AS7-D-H Clan Assault Mech
2 pages
Faculty Development in AI & Education
No ratings yet
Faculty Development in AI & Education
8 pages
Denmark - Keso
No ratings yet
Denmark - Keso
2 pages
VTR MtA Hybrid 4-Page Interactive
No ratings yet
VTR MtA Hybrid 4-Page Interactive
4 pages
CSR&SG g1p4.1 MQP June2024
No ratings yet
CSR&SG g1p4.1 MQP June2024
10 pages
BoonJon Composting Toilet Manual
No ratings yet
BoonJon Composting Toilet Manual
13 pages
Living and Non-Living Things Quiz
No ratings yet
Living and Non-Living Things Quiz
9 pages
CV Kenny EN 2014
No ratings yet
CV Kenny EN 2014
2 pages
Division Unified Test in Practical Research 1 4th Quarter
No ratings yet
Division Unified Test in Practical Research 1 4th Quarter
6 pages
Technical Specifications 24000btuhr Wall Mount Gree ACs
100% (1)
Technical Specifications 24000btuhr Wall Mount Gree ACs
7 pages
Pronunciation Guide for Andrijasevic
No ratings yet
Pronunciation Guide for Andrijasevic
125 pages
FHA FULL Condo Questionnaire 12-09
No ratings yet
FHA FULL Condo Questionnaire 12-09
2 pages
HW-8 Phase 2
No ratings yet
HW-8 Phase 2
6 pages
Guitar Department Exam Levels1-8 Proficiency BERKLEE
83% (6)
Guitar Department Exam Levels1-8 Proficiency BERKLEE
12 pages
Chemical Safety for Industry
No ratings yet
Chemical Safety for Industry
7 pages
Business Accounting Revision Questions
No ratings yet
Business Accounting Revision Questions
5 pages
Australian Gothic Fiction Insights
No ratings yet
Australian Gothic Fiction Insights
2 pages
Simplification and Value Finding Exercises
No ratings yet
Simplification and Value Finding Exercises
4 pages
Configure and Deploy Intune MDM
67% (3)
Configure and Deploy Intune MDM
92 pages
Error Word Identification
No ratings yet
Error Word Identification
6 pages
Understanding Business Stakeholders
No ratings yet
Understanding Business Stakeholders
22 pages
Rooms Management Housekeeping - Opera PMS User Guide Version 4 PDF
100% (1)
Rooms Management Housekeeping - Opera PMS User Guide Version 4 PDF
36 pages
Internet Scavenger Hunt Guide
No ratings yet
Internet Scavenger Hunt Guide
2 pages
Spe-207419-Ms EPOXY RESIN SCP ELIMINATION
No ratings yet
Spe-207419-Ms EPOXY RESIN SCP ELIMINATION
12 pages
LECTURE 1 - Fundamental Tools of Space Planning, Design and Analysis
No ratings yet
LECTURE 1 - Fundamental Tools of Space Planning, Design and Analysis
23 pages

EX - NO: 1 Passport Automation System Date: Aim

Uploaded by

EX - NO: 1 Passport Automation System Date: Aim

Uploaded by

EX.

NO: 1 PASSPORT AUTOMATION SYSTEM DATE:

PROBLEM ANALYSIS AND PROJECT PLAN:

SOFTWARE REQUIREMENTS SPECIFICATION:

[Link]. SOFTWARE REQUIREMENTS SPECIFICATION

1.3) DEFINITIONS, ACRONYMS AND THE ABBREVIATIONS:

1.5) TECHNOLOGIES TO BE USED:

1.6) TOOLS TO BE USED:

2.1) SYSTEM FUNCTIONS:

2.2) USER CHARACTERISTICS:

2.4) ASSUMPTIONS AND DEPENDENCIES:

1. USE CASE DIAGRAM:

DOCUMENTATION OF USE CASE DIAGRAM:

DOCUMENTATION OF CLASS DIAGRAM:

DOCUMENTATION OF SEQUENCE DIAGRAM:

5. STATE CHART DIAGRAM:

DOCUMENTATION OF STATE CHART DIAGRAM:

DOCUMENTATION OF ACTIVITY DIAGRAM:

DOCUMENTATION OF DEPLOYMENT DIAGRAM:

PROBLEM ANALYSIS AND PROJECT DESIGN:

SOFTWARE REQUIREMENT SPECIFICATION:

11. FUNCTIONAL REQUIREMENTS:

12. SOFTWARE REQUIREMENTS:

Front end: ArgoUML and Java.

13. HARDWARE REQUIREMENTS:

Processor: Intel Core I5

1. USE CASE DIAGRAM:

This class diagram has 8 classes:

DOCUMENTATION OF SEQUENCE DIAGRAM:

DOCUMENTATION OF COLLABORATION DIAGRAM:

DOCUMENTATION OF ACTIVITY DIAGRAM:

1. The member registers himself in book bank

DOCUMENTATION OF COMPONENT DIAGRAM:

DOCUMENTATION OF PACKAGE DIAGRAM:

PROBLEM ANALYSIS AND PROJECT PLANNING:

SOFTWARE REQUIREMENTS SPECIFICATION:

10. FUNCTIONAL REQUIREMENTS:

11. EXTERNAL INTERFACE REQUIREMANTS SOFTWARE REQUIREMENTS:

Front end: ArgoUML and Java

12. HARDWARE REQUIREMENTS:

Processor: Intel Core I5

1. USE CASE DIAGRAM:

DOCUMENTATION OF USE CASE DIAGRAM:

DOCUMENTATION OF COLLABORATION DIAGRAM:

DOCUMENTATION OF PACKAGE DIAGRAM:

PROBLEM ANALYSIS AND PROJECT PLANNING:

SOFTWARE REQUIREMENTS SPECIFICATION:

11. FUNCTIONAL REQUIREMENTS:

1. USE CASE DIAGRAM:

DOCUMENTATION OF CLASS DIAGRAM:

DOCUMENTATION OF SEQUENCE DIAGRAM:

5. STATE CHART DIAGRAM:

DOCUMENTATION OF STATE CHART DIAGRAM:

DOCUMENTATION OF ACTIVITY DIAGRAM:

DOCUMENTATION OF COMPONENT DIAGRAM:

PROBLEM ANALYSIS AND PROJECT PLANNING:

1. USE CASE DIAGRAM:

DOCUMENTATION OF SEQUECE DIAGRAM:

DOCUMENTATION OF DEPLOYMENT DIAGRAM:

1. USE CASE DIAGRAM:

DOCUMENTATION OF USE CASE DIAGRAM:

DOCUMENTATION OF CLASS DIAGRAM:

DOCUMENTATION OF COLLABRATION DIAGRAM:

DOCUMENTATION OF DEPLOYMENT DIAGRAM:

[Link]: 7 SOFTWARE PERSONNEL MANAGEMENT SYSTEM DATE:

PROJECT ANALYSIS AND PROJECT PLANNING:

1. USE CASE DIAGRAM:

DOCUMENTATION OF CLASS DIAGRAM:

DOCUMENTATION OF SEQUENCE DIAGRAM:

1. USE CASE DIAGRAM:

DOCUMENTATION OF SEQUENCE DIAGRAM:

DOCUMENTATION OF ACTIVITY DIAGRAM:

DOCUMENTATION OF DEPLOYMENT DIAGRAM:

1. USE CASE DIAGRAM:

DOCUMENTATION OF CLASS DIAGRAM:

DOCUMENTATION OF SEQUENCE DIAGRAM: