Updated Casetools Record PDF

TABLE OF CONTENTS
S.NO DATE NAME OF THE EXPERIMENT PG.NO MARK SIGNATURE
1 Study Of UML Diagrams
2 Passport Automation System
3 Book Bank System
Exam Registration
4
5 Stock Maintenance System
6 Online Course Registration System
E-Ticketing
7
Software Personnel Management

8
System
Credit Card Processing System

9
E-Book Management System

10
Recruitment System
11
Foreign Trading System

12
Conference Management System

13
14 BPO Management System
15 Library Management System
16 Students Information System

EXPERIMENT NO:
DATE STUDY OF UML DIAGRAMS
AIM
DESCRIPTION
The Unified Modelling Language is a standard visual modelling language intended to

be used for modelling business and similar processes, analysis, design, and implementation of
software-based systems.UML is a common language for business analysts, software
architects and developers used to describe, specify, design, and document existing or new
business processes, structure and behaviour of artifacts of softwaresystems.
1. Use casediagrams
2. Classdiagrams
3. Objectdiagrams
4. Sequencediagrams
5. Collaborationdiagrams
6. State chartdiagrams
7. Activitydiagrams
8. Componentdiagrams
9. Deploymentdiagrams
The UML is applicable to object-oriented problem solving. Anyone interested in
learning UML must be familiar with the underlying tenet of object-oriented problem solving-
- it all begins with the construction of a model. A model is an abstraction of the underlying
problem. The domain is the actual world from which the problemcomes.
Models consist of objects that interact by sending each other message. Think of an
object as "alive." Objects have things they know (attributes) and things they can do
(behaviours or operations). The values of an object's attributes determine its state. Classes are
the "blueprints" for objects. A class wraps attributes (data) and behaviours (methods or
functions) into a single distinct entity. Objects are instances ofclasses.
AN INTRODUCTION TO UMLDIAGRAM
The Unified Modelling Language is a language for specifying, constructing,

visualizing, and documenting the artifacts of a software-intensive system. Analogous to the
use of architectural blueprints in the construction industry, UML provides a common
language for describing software models, and it can be used in conjunction with a wide range
of software lifecycles and developmentprocesses.
1. USE CASEDIAGRAM
Use Case diagrams identify the functionality provided by the system (use cases), the users
who interact with the system (actors), and the association between the users and the
functionality. Use Cases are used in the Analysis phase of software development to articulate
the high-level requirements of the system. The primary goals of Use Case diagramsinclude:
 Providing a high-level view of what the systemdoes

 Identifying the users ("actors") of thesystem
 Determining areas needing human-computerinterfaces.
Actor
An Actor, as mentioned, is a user of the system, and is depicted using a stick figure. The role
of the user is written beneath theicon.
UseCase
A Use Case is functionality provided by the system, typically described as verb + object (e.g.
Register Car, DeleteUser).
Association
Associations are used to link Actors with Use Cases, and indicate that an Actor participates in
the Use Case in some form. Associations are depicted by a line connecting the Actor and the
UseCase.
Use case diagrams are helpful in threeareas.
•Determining features (requirements). New use cases often generate new requirements as the
system is analyzed and the design takesshape.
•Communicating with clients. Their notational simplicity makes use case diagrams a good
way for developers to communicate withclients.
•Generating test cases. The collection of scenarios for a use case may suggest a suite of test
cases for thosescenarios.
2. SEQUENCEDIAGRAM
Sequence diagrams document the interactions between classes to achieve a result,

such as a use case. Because UML is designed for object-oriented programming, these
communications between classes are known as messages. The Sequence diagram lists objects
horizontally, and time vertically, and models these messages overtime.
Life Box
Objects are instances of classes, and are arranged horizontally. The pictorial representation
for an Object is a class (a rectangle) with the name prefixed by the object name (optional) and
asemi-colon.
Object
Lifeline
The Lifeline identifies the existence of the object over time. The notation for a Lifeline is a
vertical dotted line extending from anobject.
Activation
Activations, modelled as rectangular boxes on the lifeline, indicate when the object is
performing anaction.
Message
Messages, modelled as horizontal arrows between Activations, indicate the communications

betweenobjects.
3. ACTIVITYDIAGRAM
Activity diagrams are used to document workflows in a system, from the business
level down to the operational level. When looking at an Activity diagram, you'll notice
elements from State diagrams. In fact, the Activity diagram is a variation of the state diagram
where the "states" represent operations, and the transitions represent the activities thathappen
when the operation is complete. The general purpose of Activity diagrams is to focus on
flows driven by internal processing vs. externalevents.
ActivityStates
Activity states mark an action by an object. The notations for these states are rounded
rectangles, the same notation as found in State chartdiagrams.
State
Transition
When an Activity State is completed, processing moves to another Activity State. Transitions
are used to mark this movement. Transitions are modelled usingarrows.
Transition
InitialState
The Initial State marks the entry point and the initial Activity State. The notation for the
Initial State is the same as in State chart diagrams, a solid circle. There can only be one Initial
State onadiagram.
FinalState
Final States mark the end of the modelled workflow. There can be multiple Final States on a
diagram, and these states are modelled using a solid circle surrounded by anothercircle.
SynchronizationBar
Activities often can be done in parallel. To split processing ("fork"), or to resume processing
when multiple activities have been completed ("join"), Synchronization Bars are used. These
are modelled as solid rectangles, with multiple transitions going in and/orout.
4. COMPONENTDIAGRAM
Component diagrams fall under the category of an implementation diagram, a kind of

diagram that models the implementation and deployment of the system. A Component
Diagram, in particular, is used to describe the dependencies between various software
components such as the dependency between executable files and source files. This
information is similar to that within make files, which describe source code dependencies and
can be used to properly compile anapplication.
Component
A component represents a software entity in asystem.

Examples include source code files, programs, documents, and resource files. A component is
represented using a rectangular box, with two rectangles protruding from the left side, as seen
in the image to theright.
Dependency
A Dependency is used to model the relationship between two components. The notation for a
dependency relationship is a dotted arrow, pointing from a component to the component it
dependson.
5. CLASSDIAGRAM
A Class diagram gives an overview of a system by showing its classes and the relationships
among them. Class diagrams are static -- they display what interacts but not what happens
when they do interact.UML class notation is a rectangle divided into three parts: class name,
attributes, and operations. Names of abstract classes, such as Payment, are in italics.
Relationships between classes are the connectinglinks.
The top part contains the name of theclass.
The middle part contains the attributes of theclass.
The bottom part contains the methods/function the class canexecute.
6. PACKAGES AND OBJECTDIAGRAMS
Package in the Unified Modelling Language is used "to group elements, and to provide a
namespace for the grouped elements”. A package may contain other packages, thus providing
for a hierarchical organization ofpackages.
Package
Packages appear as rectangles with small tabs at the top. The package name is on the tab or
inside therectangle.
7. COLLABORATION DIAGRAMS
Collaboration diagrams are also interaction diagrams. They convey the same information as
sequence diagrams, but they focus on object roles instead of the times that messages are sent.
In a sequence diagram, object roles are the vertices and messages are the connectinglinks.
8. STATE CHART DIAGRAMS
A state diagram is a type of diagram used in computer science and related fields to
describe the behaviour of systems. State diagrams require that the system described is
composed of a finite number of states; sometimes, this is indeed the case, while at other times
this is a reasonable abstraction. Many forms of state diagrams exist, which differ slightly and
have differentsemantics.
States are rounded rectangles. Transitions are arrows from one state to another. Events or
conditions that trigger transitions are written beside the arrows. The initial state (black circle)
is a dummy to start the action. Final states are also dummy states that terminate theaction.
9. DEPLOYMENT DIAGRAMS
A deployment diagram the Unified Modelling Language models the physical

deployment of artefacts on nodes. To describe a web site, for example, a deployment diagram
would show what hardware components ("nodes") exist (e.g., a web server, an application
server, and a database server), what software components ("artifacts") run on each node (e.g.,
web application, database), and how the different pieces are connected (e.g. JDBC, REST,
RMI).
Logical Architecture and UML PackageDiagrams
OOS has threelayers
 UILayer
 Domain and applicationlayer
 Technical ServiceLayer
RESULT:
EXPERIMENT NO:
DATE PASSPORT AUTOMATION SYSTEM
AIM
PROBLEMSTATEMENT
1. Passport Automation System is used in the effective dispatch of passport to all of the
applicants. This system adopts a comprehensive approach to minimize the manual
work and schedule resources, time in a cogentmanner.
2. The core of the system is to get the online registration form (with details such as
name, address etc.,) filled by the applicant whose testament is verified for its
genuineness by the Passport Automation System with respect to the already existing
information in thedatabase.
3. This forms the first and foremost step in the processing of passport application. After
the first round of verification done by the system, the information is in turn forwarded
to the regional administrator's (Ministry of External Affairs)office.
4. The application is then processed manually based on the report given by the system,
and any forfeiting identified can make the applicant liable to penalty as per thelaw.
5. The system forwards the necessary details to the police for its separate verification
whose report is then presented to the administrator. After all the necessary criteria
have been met, the original information is added to the database and the passport is
sent to theapplicant.
SOFTWARE REQUIREMENTSSPECIFICATION
SNO SOFTWARE REQUIREMENTS

SPECIFICATION
1.0 Introduction
1.1 Purpose
1.2 Scope
1.3 Definition, Acronyms and Abbreviations
1.4 Reference
1.5 Technology to be used
1.6 Tools to be used
1.7 Overview
2.0 Overall description
2.1 Productive description
2.2 Software interface
2.3 Hardware interface
2.4 Systemfunction
2.5 User Characteristic
2.6 Constraints
2.7 Assumption andDependences
1.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 possibleextent.
1.2 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 satisfyit.
1.3 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'sinformation.
1.4 DEFINITIONS, ACRONYMS AND THEABBREVIATIONS
1. Administrator - Refers to the super user who is the Central Authority who has been
vested with the privilege to manage the entire system. It can be any higher official in
the Regional Passport Office of Ministry of ExternalAffairs.
2. Applicant - One who wishes to obtain thePassport.
3. PAS - Refers to this Passport AutomationSystem.
1.5 REFERENCES IEEE Software Requirement Specificationformat.
1.6 TECHNOLOGIES TO BE USED • Microsoft Visual Basic6.0
1.7 TOOLS TO BE USED • StarUML tool (for developing UMLPatterns)
1.8 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 theactors.
2.1 OVERALLDESCRIPTION
2.2 PRODUCTPERSPECTIVE
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.3 SOFTWAREINTERFACE
1. Front End Client - The applicant and Administrator online interface is built using
Microsoft Visual Basic6.0.
2. Back End – MS Accessdatabase
2.4 HARDWAREINTERFACE
The server is directly connected to the client systems. The client systems have access tothe
database in theserver.
2.5 SYSTEMFUNCTIONS
1. Secure Registration of information by theApplicants.

2. Message box for Passport Application Status Display by theAdministrator.
3. Administrator can generate reports from the information and is the only authorized
personnel to add the eligible application information to thedatabase.
2.6 USERCHARACTERISTICS
1. Applicant - They are the people who desire to obtain the passport and submit the
information to thedatabase.
2. 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 ofpassport.
3. 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 thisPAS.
2.7 CONSTRAINTS
1. The applicants require a computer to submit theirinformation.

2. Although the security is given high importance, there is always a chance of intrusion
in the web world which requires constantmonitoring.
3. The user has to be careful while submitting the information. Much care isrequired.
2.8 ASSUMPTIONS ANDDEPENDENCIES
1. The Applicants and Administrator must have basic knowledge of computers and
EnglishLanguage.
2. The applicants may be required to scan the documents andsend.
UMLDIAGRAMS
S.NO UMLDIAGRAMS
1 Use Casediagram
2 Classdiagram
3 Interactiondiagram
4 Sequencediagram
5 Collaborationdiagram
6 State Chartdiagram
7 Activitydiagram
8 Componentdiagram
9 Deploymentdiagram
10 Packagediagram
GANTTCHART:
USECASEDIAGRAM:
DOCUMENTATION OF USECASEDIAGRAM
a. The actors in use case diagram are Applicant, regional administrator, database,
passport Administrator,Police.
b. The use cases are Login, givedetails, logout, collectdetails, verification,issue.
c. The actors use the use case are denoted by thearrow.
d. The login use case checks the username and password for applicant, regional
administrator, passport administrator andpolice.
e. The submit details use case is used by the applicant for submitting hisdetails.
f. The check status use case is used by the applicant for checking the status of
the applicationprocess.
g. The get details, verify and store verification use case is used by passport
administrator, regional administrator, andpolice.
h. The details use case is used for getting the details form the database for
verification.
2. The verify use case is used for verifying the details by comparing the data in the
database.
a. The store verification use case is to update the data in thedatabase.
b. And finally the issue passport use case is used by the passport administrator
for issuing passport who’s application verified successfully by all the actor.
CLASSDIAGRAM
A class is drawn as rectangle box with three compartments or components separated

by horizontal lines. The top compartment holds the class name and middle compartment
holds the attribute and bottom compartment holds list ofoperations.
DOCUMENTATION OF CLASSDIAGRAM
a. APPLICANT-The applicant has attribute such as name and password and

operations are login, givedetails 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 verificationprocess.
b. THE DATABASE-The database has attributed such as name and operation is
store. The purpose is to store thedata.
c. REGIONAL ADMINISTRATOR- The regional administrator has attribute
such as name and operation are get details, verify details and send. The
regional administrator get the details form database and verify with their
database.
d. PASSPORT ADMINISTRATOR-The passport administrator has attributed
such as name and operation are get details, verify details and issue. The
passport administrator get the details form database and verify with their
database , update the verification and issue thepassport.
e. THE POLICE-The police has attribute such as name and operation are get
details, verify details and send. The police get the details form database and
verify with their database , update the verification in thedatabase
SEQUENCEDIAGRAM
A sequence diagram shows an interaction arranged in timesequence,

It shows object participating in interaction by their lifeline by the message they exchange
arranged in time sequence. Vertical dimension represent time and horizontal dimension
representobject.
DOCUMENTATION OF SEQUENCEDIAGRAM.
a. The applicant login the database and give his details and database store the
details.
b. The passport administrator get the details from the database and do
verification and the forward to regionaladministrator.
c. The regional administrator get details form passport administrator and perform
verification and send report to passportadministrator.
d. The police get the details form passport administrator and perform verification
and send report to passportadministrator
COLLABORATIONDIAGRAM
A collaboration diagram is similar to sequence diagram but the message in number format. In
a collaboration diagram sequence diagram is indicated by the numbering the message. 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 realtime.
STATE CHARTDIAGRAM
The state chart diagram contains the states in the rectangle boxes and starts in indicated by
the dot and finish is indicated by dot encircled. The purpose of state chart diagram is to
understand the algorithm in the performingmethod.
CreateLogin
event OnCreated / Login

do/ Tryagain/end
GiveDetails
event Oncorrect entry/ Can modify before submit

event Onwrong Entry/ Check All the fieldsproperly
GetDetails
Verification
event onview/ Viewdetails
event Onnot found/ Check yourrecords eventonview/
PayPenalty IssuePassport
event ontime/renewal event onuptodate/issue

event Undefined/ paypenalty event onexpires/ paypenalty
DOCUMENTATION OF STATE CHARTDIAGRAM

a. The states of the passport automation system are denoted in the state chart
diagram
b. Login state represent authentication for login the passport automationsystem.
c. In this state, it checks whether the applicant has provided all the details that is
required.
d. Police, regional administrator and passport administrator get necessary details
and verification of the applicant are denoted from the Get detail state and
verificationstate
ACTIVITYDIAGRAM
An activity diagram is a variation or special case of a state machine in which the states or
activity representing the performance of operation and transitions are triggered by the
completion of operation. The purpose is to provide view of close and what is going on inside
a use case or among several classes. An activity is shown as rounded box containing the
name ofoperation.
Login
Submit
details
Givedetails
Getdetails
Penalityas
perlaw
Issue
Passport
DOCUMENTATION OF ACTIVITYDIAGRAM
a. The activities in the passport automation system are login, submit details, get
details, issue passport and penalty andverification.
b. 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.
c. After the verification procedure completed successfully the passport is issued
to theapplicant.
COMPONENTDIAGRAM
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 systems. It is represented by boxed figure.
Dependencies are represented by communicationassosiation.
DOCUMENTATION OF COMPONENTDIAGRAM
a. The components in the passport automation system are passport automation

system, applicant, passport administrator, regional administrator, andpolice.
b. Applicant ,passport administrator, regional administrator and police are

dependent on passport automation system are shown by the dottedarrow
DEPLOYMENTDIAGRAM
It is a graph of nodes connected by communication association. It is represented by a three
dimensional box. A deployment diagram in the unified modeling language serves to model
the physical deployment of artifacts on deployment targets. Deployment diagrams show "the
allocation of artifacts to nodes according to the Deployments defined between them. It is
represented by 3-dimentional box. Dependencies are represented by communication
association. The basic element of a deployment diagram is a node of twotypes
DEVICENODE–
A physical computing resource with processing and memory service to executesoftware,
such as a typical computer or a mobilephone.
EXECUTION ENVIRONMENTNODE
This is a software computing resource that runs within an outer node and which itself
provides a service to host an execute other executable softwareelement.
DOCUMENTATION OF DEPLOYMENTDIAGRAM
The device node is passport automation system and execution environment node are applicant
passport administrator, regional administrator, andpolice.
PACKAGEDIAGRAM
A package diagram is represented as a folder shown as a large rectangle with a top

attached to its upper left corner. A package may contain both sub ordinate package and
ordinary model elements. All uml models and diagrams are organized into package. A
package diagram in unified modeling language that depicts the dependencies between the
packages that make up a model. A Package Diagram (PD) shows a grouping of elements in
the OO model, and is a 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. Theyare
o User interfacelayer
o Domainlayer
o Technical serviceslayer
DOCUMENTATION OF PACKAGEDIAGRAM
The three layer in the passport automation system are user interface layer, domain layer,
technical servicelayer
a. The user interface layer- represents the user interface components such as
web, applicant, passport administrator, police, and regionaladministrator.
b. The domain layer- has major actions such as give and get details, verification
andissues.
c. Technical service layer- authenticated user only can access the technical
services.
JAVACODING
Applicant.java
public classApplicant
{
private int Name;
private int FatherName;
private intDateOfBirth;
private int PermanantAddress;
private int TemporaryAddress;
private intEmailID;
private int PhoneNumber;
private intPanNo;
private int ApplicationNo;
private int Username;
private int Password;
publicApplicant()
{
}}
Database.java
public classDatabase
{
private int Name;
publicDatabase()
{
}
public voidStore()
{
}}
PassportAdminisrator.java
public classPassportAdminisrator
{
private intName;
publicPassportAdminisrator()
{
}
public voidlogin()
{
}
public voidmodify()
{
}
public voidupdate()
{
}
public voidIssuePassport()
{
}
public voidStore()
{
}}
Police.java
public classPolice
{
publicPolice()
{
}
public voidLogin()
{
}
public voidverify()
{
}
public voidupdate()
{
}
public voidStore()
{
}
}
RegionalAdministrator.java
public classRegionalAdministrator
{
private intPassword;
publicRegionalAdministrator()
{
}
public voidLogin()
{
}
public voidverify()
{
}
public voidupdate()
{
}
public voidStore()
{
}}
RESULT:
EXPERIMENT NO:
DATE BOOK BANK SYSTEM
AIM
PROBLEMSTATEMENT
Book bank system is where the books can be collected every semester and must be returned at
theendofsemester.Thesystemmusthaveoptionfornewmemberstoenrollformembershipbypaying deposit.
A provision for getting six or seven books per semester. Membership can be renewed by using the
register number. The deposit must be refunded on termination of membership. A database must be
maintained to guide the issuer to track the details of students. Search option must be provided so that
the member can search for the availability of a particularbook.
SOFTWARE REQUIREMENTSPECIFICATION
S.NO SOFTWARE REQUIREMENTSPECIFICATION
1 Introduction
1.1 Purpose
1.2 Productscope
1.3 Document conventions
1.4 References
2 Overall Description
2.1 Product Perspective
2.2 Product Functions
2.4 External Interface
3 Hardware Interface
3.1 Software Interface
3.2 System Features
4 RequestingBooks
4.1 Stimulus/response Sequence
4.1.1 FunctionalRequirements
4.1.2 Other non-functional requirements
4.1.3 PerformanceRequirements
4.1.4 Safety Requirements
4.1.5 SecurityRequirements
1. INTRODUCTION
The book bank is a set up that lends books for all its members which they can return at the end
ofeachsemester.Ithasahugecollectionofbooksandhastokeeptrackofallitsmembers’detailssuch as
requests, dues and penalties and thebooks.
1.1 PURPOSE
The purpose of this document is to present a detailed description of the Book Bank System. It
will explain the purpose and features of the system, the interfaces of the system, what the system will
do, the constraints under which it must operate and how the system will react to externalstimuli.
1.2 SCOPE
The book bank holds an online interface with its members for maintaining all kinds of
transaction details. Each member is provided with a unique user id at the time of registering as a
member.
1.3 DOCUMENTCONVENTIONS
· Director: The ultimate authority in the staff hierarchy of the bookbank
· Member: Any person who registers with the bookbank
· HTML-Hyper Text Markup Language used to create webpage.
1.4 REFERENCES
www.reachbookbank.comw
ww.bookworldlibrary.com
2. OVERALLDESCRIPTION
This project is a self-contained one for enabling a book bank organization to be connected with
its students, through this system, the students can check for availability of books, makes requests,etc.
2.2 PRODUCTFUNCTIONS
This system functions with a database at the back end, for keeping track of its member’s dues
andpayments,andalsoitsavailableresources.Everystudentwhoisamemberneedsonlyawebbrowser to
connect to thissystem.
2.3 TOOLS TO BEUSED

Visual basic and MicrosoftAccess
3. EXTERNALINTERFACES
3.1 HARDWAREINTERFACES
Thesystemshouldhavegoodhardwaresupport.Theprocessorshouldhavehighspeedandmust be of
highefficiency.
The system uses ODBC drive to connect and control thedatabase.
4. SYSTEMFEATURES
4.1 REQUESTINGBOOKS
4.1.1 SYSTEM DESCRIPTION &PRIORITY
Allows a student, who becomes a member to login using a unique id issued at the time of
registeringasamember,andafterloggingin,themembercanbrowsethroughavailablebooksandmake
requestsaccordingly.Thebookswillbeissuedprovidedthereisnodue,regardingreturningofprevious books.
4.1.2 STIMULUS/RESPONSESEQUENCE
Wheneverthestudentwishestogetbooks,he/shechecksfortheavailabilitybyloggingin.When the
request is made, the director of the book bank decides on granting the request of book(s) after
checking the member details for due in returning previousbooks.
4.1.3 FUNCTIONALREQUIREMENTS
Themembershouldbeauthenticatedbymeansofuniqueloginidandpassword.Theavailability of
books requested must be prompted to the user through e-mail or smsnotifications.
5. OTHER NON-FUNCTIONALREQUIREMENTS
5.1 PERFORMANCEREQUIREMENTS
The web interface should be able to support multiple users trying to log insimultaneously.
5.2 SAFETYREQUIREMENTS
The student details should be made available in the database and must be updated every time a
book is issued or returned or some kind of payment takes place to preventerrors.
5.3 SECURITYREQUIREMENTS
The member can only access certain details from the database. He/she should not be able to
modify the database nor has any of its information corrupted. Only the DBA must be bestowedwith
the privileges of handling any kind ofmodifications.
USECASEDIAGRAM
S.NO UMLDIAGRAMS
1 Use Casediagram
2 Classdiagram
4 Sequencediagram
7 Activitydiagram
8 Componentdiagram
9 Deploymentdiagram
10 Packagediagram
GANTTCHART:
Task Dec Jan Feb March April

w w w w w w w w w w w w w w w w w w w w
1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4
Requirementa
nalysis
Design
Coding
Testing
Maintanence
USECASEDIAGRAM
login
existing user signup

admin
user
provide userid
new user <<Actor>>
database
updates the bookdetails
borrowsbook
returnsbook
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 ofinteractions
between systems and users in a particular environment and related to a particular goal. It is
represented usingellipse.
Actor is any external entity that makes use of the system beingmodeled.
DOCUMENTATION OF USE CASEDIAGRAM

The actors in this use case diagram are member and database. The use cases are theactivities
performed byactors.
• The member will register himself in the bookbank.
• After registration he will select the year to which hebelongs
• After selecting he will selectbooks
• Database will verify the status ofbook
CLASSDIAGRAM
The class diagram is the main building block of object oriented modelling. It is used both for
general conceptual modelling of the systematics of the application, and for detailed modelling
translating the models into programming code. Class diagrams can also be used for
datamodeling. The classes in a class diagram represent both the main objects, interactions in the
application and the classes to be programmed. In the diagram, classes are represented with boxes
which contain threeparts:
 The top part contains the name of the class. It is printed in bold and centered, and thefirst
letter iscapitalized.
 The middle part contains the attributes of the class. They are left-aligned and the first letteris
lowercase.
 The bottom part contains the methods the class can execute. They are also left-aligned and
the first letter islowercase.
This class diagram has 8classes:
• Member details class- is the class name. Its attributes are name, father name, date ofbirth,
address, phone number, member id, college, degree, course and semester. Its operations are
registration, authentication, and yearselection.
• Administrator- is the class name. Its attributes are name, address, phone, mail id.Its
operations are authentication, verification and issuebooks.
• Year-is the class name. Its attribute is year selection. Its operations are 1st year,2nd year,3rd
year,4thyear.
• Issue for 1st year-is the class name. Its attributes are member code, member name, bookcode,
book name, and quantity. Its operation isissue
Issue for 2nd year-is the class name. Its attributes are member code, member name, bookcode,
• Issue for 3rd year-is the class name. Its attributes are member code, member name, bookcode,
SEQUENCEDIAGRAM
A Sequence diagram is an interaction diagram that shows how processes operate
with one another and what is their order. It is a construct of a Message Sequence Chart. A
sequence diagram shows object interactions arranged in time sequence. It depicts the objectsand
classes involved in the scenario and the sequence of messages exchanged between the objects
needed
user admin database

request forbook
check foravailability
respond with status of the book
issues the book if it is available
receives thebook
returns the book on or before the duedate
updates the bookdb
DOCUMENTATION OF SEQUENCEDIAGRAM
The sequence diagram describes the sequence of steps toshow
• The member registers himself in bookbank
• He will select theyear
• He select the books given and the database will update the status ofbook.
• Then administrator will log in and verify the status ofbooks.
• If the book is available he will issue thebook.
Acollaborationdiagramissimilartosequencediagrambutthemessageinnumberformat. In a
collaboration diagram sequence diagram is indicated by the numbering the message. 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
realtime.
5: receives thebook
1: request forbook
6: returns the book on or before the due date
user admin
4: issues the book if it isavailable
3: respond with status of thebook

2: check for availability
7: updates the bookdb
database
DOCUMENTATION OF COLLABORATIONDIAGRAM
Thecollaborationdiagramistoshowhowthememberregistershimselfandborrowthebookfrom the
book bank. Here the sequence is numbered according to the flow ofexecution.
STATE CHARTDIAGRAM
Thestatechartdiagramcontainsthestatesintherectangleboxesandstartsinindicatedbythedot and
finish is indicated by dot encircled. The purpose of state chart diagram is to understand the
algorithm in the performingmethod.

This state diagram describes the behavior of thesystem.
• In the first state the member registers himself in bookbank
• After that he will select the year in nextstate.
• In the next state he will select thebooks.
• In the next state database will update the status of book.
• In the next state administrator will login.
ACTIVITYDIAGRAM
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 are intended to model both computational and organisational processes (i.e.
workflows). Activity diagrams show the overall flow of control. Activity diagrams are
constructed from a limited number of shapes, connected with arrows.The most importantshape
types:
This activity diagram flow of stepwise activities performed in book bank managementsystem.
• After that he will select theyear.
• He will select thebooks.
• Database will update the status ofbook.
• Database will update thedetails
• Then the administrator will log in to hisaccount.
After authentication he will verify the availability ofbook.
• If available he will issue thebook.
COMPONENTDIAGRAM
book banksystem
administrator user database
A component is something required to execute a stereotype function. Examples of stereotypes in

components include executables, documents, database tables, files, and library files.Components
are wired together component with the provided interface of anothercomponent.
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 maincomponent
DEPLOYMENTDIAGRAM
<<<<client>>>>
:intel:(os=xp/7/vista)
keyboar loginer
d
JDBC:ODBCconnection
mouse
database

dimensionalbox.Adeploymentdiagramintheunifiedmodelinglanguageservestomodelthe
physical deployment of artifacts on deployment targets. Deployment diagrams show "the
represented by 3-dimentional box. Dependencies are represented by communication association.
The basic element of a deployment diagram is a node of twotypes
DEVICENODE–
A physical computing resource with processing and memory service to execute software, suchas
a typical computer or a mobilephone.
This is a software computing resource that runs within an outer node and which itself providesa
service to host and execute other executable softwareelement.
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 forsecond
year issue for third year and issue for fourth year are some activities performed in thissystem.
PACKAGEDIAGRAM
A package diagram in unified modeling language that depicts the dependencies between the
packages that make up a model. A Package Diagram (PD) shows a grouping of elements in the
OO model, and is a Cradle extension to UML. PDs can be used to show groups of classes in
Class Diagrams (CDs), groups of components or processes in Component Diagrams (CPDs),or
groups of processors in Deployment Diagrams(DPDs).
• User interfacelayer
• Domainlayer
• Technical serviceslayer
The three layers in the online recruitment systemare
• The User interface layer - consists of the web and member details. This layer describeshow
the member goes to book bank and registershimself..
• The Domain layer – shows the activities that are performed in the book bankmanagement
system. The activities are register and bookissues..
• The Technical service layer - the member details and verification details are stored inthe
database.
DOMAIN
UI
getthedetails issue
web user
admin verify
technical
login
database
JAVACODING
Database.java
public classbookDatabase
private char bookName;
private char authorName;
private intedition;
publicbookDatabase()
public voidtransaction()
{
}
public voidupdationOfBookDetails()
user.java
public classuser
private char firstName;
private char lastName;
private char address;
private int phoneNumber;
private int loginId;
private int password;
public admintheAdmin;
public bookDatabasetheBookDatabase;
publicuser()
public voidreturnsBook()
public voidborrowsBook()
{ }}
admin.java
public classadmin
private int phoneNumber;
private int loginId;
private intpassword;
public bookDatabasetheBookDatabase;
publicadmin()
public voidprovideLoginId()
RESULT
EXPERIMENT NO:
DATE EXAM REGISTRATION
AIM
PROBLEMSTATEMENT
1. Exam Registration System is used in the effective registration of exams to all of the
applicants. This system adopts a comprehensive approach to minimize the manual
work and schedule resources, time in a coherentmanner.
2. The core of the system is to get the online registration form (with details such as
name, address etc.,) filled by the applicant whose details are later verified by the
Administrator.
3. Then the applicant needs to pay the examination fees by the interface provided in the
Exam Registration system. After the end of the due date for submitting the form, the
information is in turn forwarded to the administrator'sview.
4. The applications are then processed based on the information given by the applicant,
and any forfeiting identified can make the applicant liable to penalty as per thelaw.
5. The administrator after successful confirmation, initiates the process to generate the
hall tickets for the applicants. After successful generation of hall tickets, the system
delivers the hall ticket to the applicants. The applicants can download the hall tickets
finally in theend.

SPECIFICATION
1.0 Introduction
1.1 Purpose
1.2 Scope
1.4 Reference
1.7 Overview
2.4 Systemfunction
2.6 Constraints
1.1 INTRODUCTION
Exam Registration System is an interface between the Applicant and the Administrator
responsible for the registration of examinations. It aims at improving the efficiency in the
exam registration process and reduces the complexities involved in it to the maximum
possibleextent.
1.2 PURPOSE
If the entire process of ‘exam registration’ is done in a manual manner then it would take
several months for the application forms to reach the admin. Considering the fact that the
number of applicants who register for exams 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
Examination Process, the system has been carefully verified and validated in order to satisfy
it.
1.3 SCOPE
The System provides an online interface to the user where they can fill in their personal
details. The authority conducting the particular exam can use this system to reduce their
workload and process the application in a speedy manner. It provides a communication
platform between the applicant and the administrator also it provides a way for transfer of
data between the Bank and the Administrator for verification of applicant's transaction
details.
1. Administrator - Refers to the super user who is the Examiner who has been vested
with the privilege to manage the entire system. It can be any higher official in the
Particular domainoffice.
2. Applicant - One who wishes to apply for anexam.
3. ERS - Refers to this Exam RegistrationSystem.
1.8 OVERVIEW
SRS includes two sections overall description and specific requirements - Overall description
will describe major role of the system components and inter-connections. Specific
The ERS acts as an interface between the 'applicant' and the'administrator'.
the security of data stored in. This minimizes the time duration in which the applicant
receives the hallticket.
The server is directly connected to the client systems. The client systems have secured access
to the database in theserver.
2.5 SYSTEMFUNCTIONS

2. Highly Secured Online Transaction interface that connects thebank.
3. Message box for Exam Registration Status Display for theApplicant.
4. Administrator can generate reports from the information and is the only authorized
1. Applicant - They are the people who desire to apply for the examination and submit
the information to thedatabase.
2. Administrator - He has the privileges to add new exam status and to generate the hall
ticket. He may contain a group of persons under him to verify the documents and give
suggestion whether or not to conduct theexamination.
2.7 CONSTRAINTS

2. Although the security is given high importance, there is always a chance of intrusion
in the web world which requires constantmonitoring.
1. The Applicants and Administrator must have basic knowledge of computers and
EnglishLanguage.
2. The applicants may be required to scan the documents andsend.
UMLDIAGRAMS
S.NO UMLDIAGRAMS
1 Use Casediagram
2 Classdiagram
4 Sequencediagram
7 Activitydiagram
8 Componentdiagram
9 Deploymentdiagram
10 Packagediagram
GANTTCHART:
14-Dec 15-Jan 15-Feb 15-Mar
Taskname w3 w4 w1 w2 w3 w4 w1 w2 w3 w4 w1 w2 w3 w4
ProblemStatement
SRSDocument
Specification
Analysis
Design
Development
Testing
Maintenance
USE CASE DIAGRAM:
login:
applicationdetails
verify the applicationform
moneytransaction
applicant
admin
verify thetransaction
bank
hall ticket process
DOCUMENTATION OF USE CASEDIAGRAM:
 The actors in use case diagram are admin, applicant andbank.

 The use cases are login, application details, verifying the application form, money
transaction, verifying transaction and finally hall ticketprocess.
 The actor use the use case are denoted byarrow
 The login use case checks the username and password for admin andapplicant
 The application details use case is used by admin for issuing the form and applicant
for filling theform
 Verify the application form use case is used by admin to verify the form given by
applicant
 The money transaction use case is used to perform the transaction of money paid by
applicant
 Verify transaction use case is used by admin to verify the process of transaction
performed inbank
 Hall ticket process use case is used by admin to issue the hall ticket and by applicant
to get the hallticket
CLASSDIAGRAM:
A class is drawn as rectangle box with three compartments or components separated by

horizontal lines. The top compartment holds the class name and middle compartment holds
the attribute and bottom compartment holds list ofoperations.
APPLICANT-The applicant has attribute such as name and email.id and operations are
login, give details and logout. The applicant login and fill the details that are required for
applying the exam registration system .After applying the person can view the status of the
online exam verificationprocess.
ADMINISTRATOR- The administrator has attribute such as name and operation are get
details, verify details, fee payment and send. The regional administrator get the details form
database and verify with their database. update the verification and issue the hallticket.
BANK-The bank has perform the transaction process from the user to admin. Attribute of
bank such as bank name branch name and the operation are transactionprocess
SEQUENCEDIAGRAM:

representobject.
server bank admin

applicant:
NewClass
login
success login
view examdetails
fill the applicationform
submit applicationform view and verify applicantdetails
payex amfees
successful transaction
verifytransaction
get hallticket process hallticket
download
DOCUMENTATION OF SEQUENCEDIAGRAM:
a. The applicant and admin login the server and give his details and server store the
details.
b. The admin get the details from the server and do the verification and report to the
client.
c. The client give the details of exam fee to the server and the bank get the details from
the server and perform transaction and admin verifyit.
d. The admin give the detail of the hallticket and the applicant download from the
server.
COLLABORATIONDIAGRAM:
A collaboration diagram is similar to sequence diagram but the message in number

format. In a collaboration diagram sequence diagram is indicated by the numbering the
message. 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 realtime
4: view exam details

5:filltheapplicationform
1:login
6:submitapplicationform
11: get hallticket
server
2:success
applicant: 13:download
NewClass
3:login
7:viewandverifyapplicantdet...
12:processhallticket
9:successful 8tr:apnasyacetxioanm fees
bank admin
10:verifytransaction
STATE CHARTDIAGRAM:
The state chart diagram contains the states in the rectangle boxes and starts in indicated by
the dot and finish is indicated by dot encircled. The purpose of state chart diagram is to
understand the algorithm in the performingmethod.
/enter website addressor openapplication
homepage login
entry/ fill loginform

registration
entry/ fill the appilcationform

onSubmit
submit
verify theform
appilication form
event check/ registration is vaild ornot
eventonvaild/ display homepage
verifiedsucessfully

a. The states of the exam registration system are denoted in the state chart
diagram
b. Login state represent authentication for login the exam registrationsystem.
required.
d. admin get necessary details and verification are noted from the application
form.
ACTIVITYDIAGRAM:
An activity diagram is a variation or special case of a state machine in which the states or
activity representing the performance of operation and transitions are triggered by the
completion of operation. The purpose is to provide view of close and what is going on inside
a use case or among several classes. An activity is shown as rounded box containing the
name ofoperation.
a. The activities in the online exam registration are login, submit details, get details,
issue hall ticket and penalty andverification.
b. In the login activity applicant give username and password and then login into the
exam registration system after then fill the details that are required foradmin.
c. After the verification procedure completed successfully the hall ticket is issued to the
applicant.
COMPONENTDIAGRAM:
The component diagram is represented by figure dependency and it is a graph of design of

relationships between the components of a systems. It is represented by boxed figure.
Dependencies are represented by communicationassociation.
admin verify the

applicant detail
& issue hall
ticket
aplplicant bank
money
login homepage
transaction
Fill the
between the
application&sub
admin&applicant
mittotheadmin
a. The components in the online exam registration are online exam registration,
applicant, administrator,bank.
b. Applicant, administrator, and bank are dependent on online exam registration

are shown by the dottedarrow
DEPLOYMENTDIAGRAM:

DEVICENODE
A physical computing resource with processing and memory service to execute software,
Keyboard
inputdevices
<<applicant>>
:intel(os=windows7/8/8.1)
Loginneer
Mouse
bank
Secure moneyTransaction
WebServer Database
DatabaseStores
Jdbc:Odbcconnection theapplicants
data
Web server handles

the dynamicaccess
of WebPages
The device node is online exam registration and execution environment node are applicant ,
administrator, andbank
PACKAGEDIAGRAM:
the OO model, and is a Cradle extension to UML. PDs can be used to show groups ofclasses
o Server
o Bank
web browser,applicant,admin.
b. Server- has major actions such as give and get details, verification andissues.
c. Bank-authenticated user only can access thebank.
JAVACODING
applicant.java
public classapplicant
{
private int First name;
private int middle name;
private int last name;
private intDOB;
private int Gender;
private int age;
private intAddress;
private int Father’s name;
private int Email id;
private int Contact no;
private int Qualification;
private int Marital status;
publiclogin()
{
}
public detail of the applicant()
{
}
public submit theform()
{
}
public feepayment()
{
}
public Gethallticket()
{
}
}
bank.java
public classbank
{
private int bank name;
private int branch name;
public Transactionprocess()
{
}
}
admin.java
public classadmin
{
private int id;
private int name;
private int Emailid;
private int contact no;
publiclogin()
{
}
public verify theform()
{
}
public check thetransaction()
{
}
public issue hallticket()
{
}
RESULT:
EXPERIMENT NO:
DATE STOCK MAINTENANCE SYSTEM
AIM:
PROBLEM STATEMENT:
1. Inventorysystemis a realtimeapplicationused inthe merchant’sday to daysystem.

Thisis a databaseto store thetransactionthattakesplacesbetween theManufacturer,
Dealerand theShop Keeper thatincludesstock inward andstock outward with
referenceto the dealer.Here we assume our self as theDealer
2. TheStock is thedatabaseusedin our Systemwhichrecords alltransactionsthat
takesplacebetweenthe Manufacturerand theDealerand theRetailer.
3. Theworking process of the stockmaintenancesystemis describedsequentiallyas:
Thewholesalerlogin tothe dealersite
Once thecustomerfilltheirdetails,theyenquire for thestock availability
Thenthe orderis placed
Themoney canbe paidthrough onlinetransactionifincaserequired
Thedealerloginand makeorder to themanufacturer
SOFTWAREREQUIREMENTS SPECIFICATION

SPECIFICATION
1.0 Introduction
1.1 Purpose
1.2 Scope
1.3 Definition,Acronyms andAbbreviations
1.4 Reference
1.5 Technologyto be used
1.6 Toolsto be used
1.7 Overview
2.0 Overalldescription
2.1 Productivedescription
2.3 Hardwareinterface
2.4 Systemfunction
2.6 Constraints
2.7 Assumptionand Dependences
1.0 INTRODUCTION:
Thissoftwarespecificationdocumentsfullsetof features andfunction for onlinestock
maintenancesystemthatis performedin companywebsite.In thiswe givespecification
aboutthe customerorders. Ittells theusability,reliabilitydefinedin use case specification
1.1 PURPOSE:
Thissoftwarespecificationdocumentsfullsetof features andfunction for onlinestock

maintenancesystemthatis performedin companywebsite.In thiswe givespecification
aboutthe customerorders. Ittells theusability,reliabilitydefinedin use case specification
1.2 SCOPE:
Thescope of this stockmaintenancesystemis to maintainthestock
1.3 DEFINITIONS,ACRONYMSANDTHEABBREVIATIONS:
 Dealer:Heistheuserwhomaintainsthewebsiteandhastheprivilegetomanagethe
entiresystem.Thedealerhas thedetailsof both wholesalerand manufacturer
Wholesaler: The wholesaleris theone who makes orders
Manufacturer:Themanufacturerproduces the itemsinthe wholesaler’sorder
SMS:Stock MaintenanceSystem
1.4 REFERENCESIEEESoftwareRequirementSpecificationformat.
1.5TECHNOLOGIESTOBE USED• MicrosoftVisualBasic6.0
1.6TOOLSTOBE USED• StarUMLtool(for developingUMLPatterns)
1.7 OVERVIEW
SRSincludestwo sectionsoveralldescriptionandspecificrequirements-Overalldescription
willdescribemajorrole ofthesystemcomponentsandinter-connections.Specific
requirementswilldescriberoles &functions of theactors.
2.1 PRODUCTPERSPECTIVE:
TheSMS actsas aninterfacebetweenthe‘wholesaler’,'dealer'and ‘producer’.
Thissystemtries tomakethe interfaceas simpleas possibleand atthe sametimenotrisking
thesecurityof datastored in.This minimizesthetimedurationin which thewholesaler
receivesthestock orders. User interfacemakesthe stockmaintenancesystemto beefficient.
Thatis thesystemwillhelp thecustomerto placethedetailsand orders easilyand helps the
vendorto maintainthe stockaccurate.The systemshouldbe user friendly.
2.2 SOFTWAREINTERFACE:
1. FrontEnd Client-TheapplicantandAdministratoronlineinterfaceis builtusing

MicrosoftVisualBasic6.0.
2. Back End– MSAccess database
2.3 HARDWARE INTERFACE:
Theserver is directlyconnectedto theclientsystems.Theclientsystemshave accessto the

databaseinthe server.
2.4 SYSTEMFUNCTIONS:
1. SecureRegistrationof informationby the wholesaler.

2. Message box for Order Status Displayby the Dealer.
2.5 USER CHARACTERISTICS:
 TheManufactureris the producerof theitems anditcontainsthenecessary informationof

the itemsuchas price peritem,Date of manufacture,bestbeforeuse, Numberof
ItemavailableandtheirCompanyAddress.
TheDealeris the secondarysourceof an Itemand he purchasesItemfromthe
manufacturerby requestingthe requiredItemwith itscorresponding CompanyName
andthe Number of Itemsrequired.The Dealeris only responsiblefor distributionof
theItemto theRetailersin theTown or City.
 TheShopKeeperorRetaileristheonewhoisprimesourceforsellingitemsinthe market.
2.6 CONSTRAINTS:
1. Thewholesalerand manufacturerrequire acomputerto submittheirinformation.

2. Althoughthe securityis givenhigh importance,thereis always a chanceof intrusion
inthe web world which requiresconstantmonitoring.
3. Theuser has to be carefulwhilesubmittingtheinformation.Much careis required.
2.7ASSUMPTIONSAND DEPENDENCIES:
Thewholesaler,dealerandmanufacturermusthavebasicknowledgeofcomputers
andEnglish Language.
.
UMLDIAGRAMS:
S.NO UMLDIAGRAMS
1 Use Case diagram
2 Class diagram
4 Sequencediagram
6 StateChartdiagram
7 Activitydiagram
8 Componentdiagram
9 Deploymentdiagram
10 Packagediagram
GANTTCHART:
USECASEDIAGRAM:
Use casediagramat itssimplestis a representationof a user's interactionwith thesystem

thatshows the relationshipbetweenthe user and thedifferentusecaseswhichtheuseris
involved.Ause case diagramcan identifythedifferenttypes of users of a systemand the
differentusecases.The boundary,whichdefinesthe systemof interestin relationtothe
worldaround it.
Theactors, usuallyindividualsinvolvedwith thesystemdefinedaccordingtotheir
roles.
 Theuse cases, which thespecificroles areplayed by theactors withinand aroundthe
system.
Therelationshipsbetweenand amongthe actorsand theuse cases.
DOCUMENTATION OFUSECASE DIAGRAM
Theactors inthis use case diagramare producer,dealerand wholesaler

Theuse cases are login,register,companyname,placingorder and numberof items
Theassociationdefines theassociation betweenuse cases and actor
Theloginuse caseis used to makeloginby the dealer,producerand wholesaler
Theregisterusecase is used to sign up for new producerand wholesaler
Theplacingorder use casedenotes theplacingof order fromwholesalertoproducer
Thetotalnumberof itemsplacedis denotedby the no of itemsuse case
CLASSDIAGRAM:
Aclassisdrawnasrectangleboxwiththreecompartmentsorcomponentsseparated
byhorizontallines.Thetopcompartmentholdstheclassnameandmiddlecompartment holds
theattributeand bottomcompartmentholds listof operations.
DOCUMENTATION OFCLASS DIAGRAM
 WHOLESALER:Thewholesalerhas thefollowingattributesname,wholesalerid,
address, contactinfo, mailid.Thewholesalerlogin using thewholesalerid and make
orderalong with thepayment.Once theorder is placedhecan checkthe statusof the
orderand receivesthe order.
 DEALER:Thedealerhas the dealername,dealerid,address, contactnumber as the
attributes.The dealermakesa loginto collectwholesalerinformationcheckthe client
list,initiatethepackingorders of thewholesaler,getpaymentfrom theclient.
 MANUFACTURER:Theattributesof themanufacturerarename,manufacturerid,
companyname,price,contactnumber.The manufacturermakesa loginand updates
theinformation,receivestheorder fromthe customerthrough dealerandreceives
paymentfromdealer.
SEQUENCEDIAGRAM:
Asequencediagramshows an interactionarrangedintimesequence,
Itshowsobjectparticipatingininteractionby theirlifelineby themessagetheyexchange
arrangedintimesequence. Verticaldimensionrepresenttimeandhorizontaldimension
representobject.
DOCUMENTATION OFSEQUENCE DIAGRAM
Thesequencediagramdescribes thesequence of steps toshow

Thecustomerlogin into thesystemand fillsthe customerdetails.
Thenthe customerplacestheorder. Itupdated tothe database.
Thevendor loginto thesystemand views thecustomerorders andthe Stockdetails.
Acollaborationdiagramissimilartosequencediagrambutthemessageinnumberformat.In
acollaborationdiagramsequencediagramisindicatedbythenumberingthemessage. A
sophisticatedmodelingtoolcan easilyconverta collaborationdiagramintoa sequence
diagramandtheviceversa. Acollaborationdiagramresemblesaflowchartthatportraysthe
roles,functionalityandbehaviorofindividualobjectsaswellastheoveralloperationofthe
systemin realtime.
1:makeorder 7:receivepackingorderandretrievestock
wholesalerdealermanufactu
rer
8:deliverthestock
9:payforservice
3:checkclientintheexistingandcreatenewrecord
5:initiatepackingorder
4:verifyproductno.andstockon hold
wholesaler 2:collectwholesalerinformation
database 6:updateinformation
manufacturer
dealer database
database
STATECHARTDIAGRAM:
Thestatechartdiagramcontainsthe statesin therectangleboxes and startsin indicatedby

thedotand finishis indicatedby dotencircled.Thepurpose of statechartdiagramis to
understandthe algorithmin theperformingmethod.
DOCUMENTATION OFSTATE CHARTDIAGRAM
a. Thestatesofthestockmaintenancesystemaredenotedinthestatechart diagram
b. Make orderstaterepresentverificationfor ordering thestock.
c. Inthisstate,itcheckswhetherthewholesalerhasprovidedallthedetailsthat is
required.
d. Aftergettingthenecessarydetailsfromthedealerdatabasethemanufacturer
informstock person for packingwhich aredenotedfrompay for servicestate
ACTIVITYDIAGRAM:
An activitydiagramisa variationor specialcase ofa statemachinein which thestatesor

activityrepresenting the performanceof operation and transitionsare triggeredby the
completionofoperation.Thepurposeistoprovideviewofcloseandwhatisgoingoninside ause
caseor among severalclasses.An activityis shown as roundedbox containingthename of
operation.
DOCUMENTATION OFACTIVITYDIAGRAM
 Theactivitiesinthestockmaintenancesystemarelogin,verification,makeorder,
verifyproduct, orderto shipping, informaccountant,pay for service.
Intheloginactivitythecustomerloginusingtheusernameandpassword,itgets
verifiedinthe database
 Iftheloginisvalidthecustomercanmakeorderorelseifthecustomerisnew,new records
willbe created
Once theorder is placeditgets verifiedby thedealer
Themanufacturermakes theorder to shippingupon the verificationof payment
COMPONENTDIAGRAM:
Thecomponentdiagramisrepresentedbyfiguredependencyanditisa
graphofdesignoffiguredependency.Thecomponentdiagram'smainpurposeistoshowthe
structuralrelationshipsbetweenthecomponentsofasystems.Itisrepresentedbyboxed
figure.Dependenciesare representedby communicationassociation.
DOCUMENTATION OFCOMPONENTDIAGRAM
a. The components in the stock maintenance system are

wholesaler,dealer,manufacturer,login/register,placingorder,database
b. Placingorderdependsuponwholesaleranddealersimilarlydatabasedepends on
loginand placingorderwhichare shown by the dottedarrow
DEPLOYMENTDIAGRAM:
Itisa graphofnodesconnectedbycommunicationassociation.It isrepresentedbya three

dimensionalbox.Adeploymentdiagramintheunifiedmodelinglanguageservestomodel
thephysicaldeploymentof artifactson deploymenttargets.Deploymentdiagramsshow "the
allocationof artifactstonodesaccordingtotheDeploymentsdefinedbetweenthem.Itis
representedby 3-dimentionalbox. Dependenciesarerepresentedbycommunication
association.Thebasic elementof a deploymentdiagramis a node of two types
DEVICE NODE–
Aphysicalcomputingresourcewith theprocessing and memoryserviceto executesoftware, such
as a typicalcomputeror a mobilephone
Thisis a software computingresourcethatruns withinan outernode and whichitself

providesa servicefor the host to executeother executablesoftware element.
DOCUMENTATION OFDEPLOYMENTDIAGRAM
Thedevicenodeisstockmaintenancesystemandexecutionenvironmentnodesaredatabase andthe
person who login.
PACKAGEDIAGRAM:
Apackagediagramis representedas afolder shown as alargerectanglewith atop

attachedto itsupper leftcorner.Apackagemaycontainboth sub ordinatepackageand
ordinarymodelelements.Allumlmodels and diagramsareorganizedinto package.A
packagediagraminunifiedmodelinglanguagethatdepictsthe dependenciesbetween the
packagesthatmakeup a model.APackageDiagram(PD) shows a groupingof elementsin
theOO model,and is aCradle extensiontoUML. PDs canbe used to show groups of classes
inClass Diagrams (CDs), groups of componentsor processes in ComponentDiagrams (CPDs),
or groups of processors in DeploymentDiagrams(DPDs).
Therearethree typesof layer.They are
o Domainlayer
o Technicalservices layer
DOCUMENTATION OFPACKAGE DIAGRAM
Thethreelayers inthe onlinerecruitmentsystemare

 The Userinterfacelayer- consists of theweb and login.Thislayerdescribeshow the
applicantlogins tothe websiteand placesthe order.
 The Domainlayer– shows theactivitiesthatare performedby thecustomerto
placethe orders.
TheTechnicalservicelayer-the vendorlogins and verifiesthecustomer orders
and stock details
JAVACODING:
Manufacturer.java
publicclass manufacturer
{
privateintname;
privateintmanufacturerid;
privateintcompanyName;
privateintitemPrice;
privateintcontactno;
publicdealertheDealer;
publicmanufacturer()
{
}
publicvoidlogin()
{
}
publicvoidaddinfo()
{
}
publicvoidreceivingPlacingOrder()
{
}
publicvoidgetpayment()
{
}
}
Dealer.java
publicclass dealer
{
privateintdealername;
privateintdealerid;
privateintaddress;
publicwholesalertheWholesaler;
publicmanufacturertheManufacturer;
publicdealer()
{
}
publicvoidlogin()
{
}
publicvoidcollectwholesalerinfo()
{
}
publicvoidinitiatePackingoreder()
{
}
publicvoidupdatebill()
{
}
publicvoidcheckClientList()
{
}
publicvoidgetPayment()
{
}
}
Wholesaler.java
publicclass wholesaler
{
privateintname;
privateintwholesalerid;
privateintaddress;
privateintitemPrice;
privateintmailid;
publicdealertheDealer;
publicwholesaler()
{
}
publicvoidlogin()
{
}
publicvoidplaceorder()
{
}
publicvoidpayment()
{
}
publicvoidreceivestock()
{
}
RESULT:
EXPERIMENT NO:
DATE ONLINE COURSE RESERVATION SYSTEM
AIM
PROBLEMSTATEMENT
Online course registration system is a web based registration software that helps you to register
courses online. This system is being developed for student’s above age 18.Initially, the students
are asked to enter their age. Once it is verified, the system provides the students to register
forcourses.
The students can learn on their own schedule and even continue their working in mean time.
This system has many options. The students should select the available courses and various
subjects under that respectivecourses.
After giving these details the system displays the date, time and its related information. The
students needs to register by giving their personal details and mention the mode of payment for
thecourse.
Once the registration is done successfully, the acknowledgement message will be sent to their
respective e-mail id’s. The students is given an user id and password using which he can login
and use the onlinesystem.
A database is maintained for the course catalogue, list of the students and their details, progress
etc. The Administrator maintains the database and ensures the efficient making of the
designedsystem
SOFTWARE REQUIREMENTS SPECIFICATION:
SNO SOFTWARE REQUIREMENTSSPECIFICATION
1.0 Introduction
1.1 Purpose
1.2 Scope
1.3 Definition, Acronyms andAbbreviations
1.4 Reference
1.5 Technology to beused
1.6 Tools to beused
1.7 Overview
2.2 Softwareinterface
2.4 Systemfunction
2.5 UserCharacteristic
2.6 Constraints
INTRODUCTION
Online Course Registration System is an interface between the Student and the System responsible
for the registration of seats.. It aims at improving the efficiency in the Registration of course
and reduces the complexities involved in it to the maximum possible extent.
PURPOSE
If the entire process of 'Registration of Course' is done in a manual manner then it would take a lot
of time for the student to register for the course. Considering the fact that the number of
students for registering courses is increasing every year, an Automated Online 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 satisfyit.
SCOPE
The System provides an online interface to the student where they can fill in their personal details.
The authority concerned with the registration of course can use this system to reduce his
workload and process the application in a speedy manner. Provides a communication platform
between the Student and the System for Transfer of data between the System and the Student
for verification of student'sinformation.
DEFINITIONS, ACRONYMS AND THEABBREVIATIONS
System- Refers to the super user who is the Central Authority who has been vested with the
privilege to manage the entire system. It can be any higher official in the Online Course
RegistrationSystem.
Student - One who wishes to register for thecourse?
Database- Refers to this database of Online RegistrationSystem.
REFERENCES IEEE Software Requirement Specificationformat.
TECHNOLOGIES TO BE USED • Microsoft Visual Basic6.0
TOOLS TO BE USED • Star UML tool (for developing UMLPatterns)
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 theactors.
OVERALLDESCRIPTION
PRODUCTPERSPECTIVE
The Course Registration System acts as an interface between the 'student' and the 'system'.
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 student takes to
register for thecourse.
SOFTWAREINTERFACE
Front End Client - The Student and System online interface is built using StarUML
Back End – MS Accessdatabase
HARDWAREINTERFACE
The server is directly connected to the client systems. The client systems have access to the
SYSTEMFUNCTIONS
Secure Registration of course by theStudents.

Message box for Student’s Registration Status Display by theSystem.
System can generate reports from the information and is the only authorized personnel to add
the eligible course information to thedatabase.
USERCHARACTERISTICS
Student - They are the people who desire to register and submit the information to the database.
System-It acts as the interface between student and database. It receives information from the
students and store the information indatabase.
Database – It has all the information about the students who have been registered for online
coursereservation.
CONSTRAINTS
The student require a computer to submit theirinformation.

Although the security is given high importance, there is always a chance of intrusion in the web
world which requires constantmonitoring.
The students has to be careful while submitting the information. Much care is required.
ASSUMPTIONS ANDDEPENDENCIES
The Applicants and Administrator must have basic knowledge of computers and
EnglishLanguage.
The applicants may be required to scan the documents andsend.
UMLDIAGRAMS
S.NO UMLDIAGRAMS
Use Casediagram
Classdiagram
Interactiondiagram
Sequencediagram
State Chartdiagram
Activitydiagram
Componentdiagram
Deploymentdiagram
Packagediagram
GANTTCHART:
USECASEDIAGRAM
The actors in use case diagram areUser,Administrator,registration.

The use cases are Login , Enter age, courses and payment ,choose course, course information, mode
of payment, PG, UG, maintain information, verify user information, update user information,
validate user information, verify age, invalid password,help.
The actors use the use case are denoted by thearrow.
The login use case is used by students for courseregistration.
The verify age use case checks whether the student age is above18.
The course and payment use case is used by the student for selecting their courses and mode
ofpayment.
The Maintain database use case is used by the student for maintaining the information of thestudent.
CLASSDIAGRAM:
A class is drawn as rectangle box with three compartments or components separated by horizontal
lines. The top compartment holds the class name and middle compartment holds the attribute
and bottom compartment holds list ofoperations.
USER-The student has attribute such as name and age and operation are choose course, view
andlogin.
ADMINISTRATOR-The database has attribute such as no. of students, course and operation
are verify info, update info, validate info and bin. The system get the information from the
students and maintained for futureuse.
REGISTRATION- The system has attribute which is system password and operation are
verify age andhelp.
SEQUENCEDIAGRAM:
A sequence diagram shows an interaction arranged in timesequence.

It shows object participating in interaction by their lifeline by the message they exchange arranged in
time sequence. Vertical dimension represent time and horizontal dimension representobject.
The student login the database and give his details and database store the details.
The student registration system get the details from the database and do verification and the
forward to thestudent.
The student get details from the system and perform verification and send report tostudent.
STATE CHARTDIAGRAM:
The state chart diagram contains the states in the rectangle boxes and starts in indicated by the dot
and finish is indicated by dot encircled. The purpose of state chart diagram is to understand the
The states of the online course reservation system are denoted in the state chartdiagram
Login state represent authentication for login the online course reservation system.
In this state, it checks whether the student has provided all the details that is required.
Payment, course details and maintaining information of the student are required
ACTIVITYDIAGRAM:
An activity diagram is a variation or special case of a state machine in which the states or activity
representing the performance of operation and transitions are triggered by the completion of
operation. The purpose is to provide view of close and what is going on inside a use case or
among several classes. An activity is shown as rounded box.
The activities in the online course reservation system are login, enter age, course details, mode of
payment, maintain database andlogout.
In the login activity student give username and password and then login into the online course
reservation system after then fill the details that are required forstudent.
In the enter age activity student give age and enter into the online course reservation system if the
age is greater than 18 after then fill the details that are required forstudent.
After the verification procedure completed successfully and some details was processed, then the
registration for the course was donesuccessfully.
COMPONENTDIAGRAM:
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 systems. It is represented by boxed figure. Dependencies are
represented by communicationassociation.
The components in the online course reservation system are student, system, anddatabase.
Student depend on system, system depend on database and student depend on database on online
course reservation are shown by the dottedarrow
DEPLOYMENTDIAGRAM:
It is a graph of nodes connected by communication association. It is represented by a three dimensional

box. A deployment diagram in the unified modeling language serves to model the physical
deployment of artifacts on deployment targets. Deployment diagrams show "the allocation of
artifacts to nodes according to the Deployments defined between them. It is represented by 3-
dimentional box. Dependencies are represented by communication association. The basic element
of a deployment diagram is a node of twotypes
DEVICENODE
A physical computing resource with processing and memory service to execute software, such as a
typical computer or a mobilephone.
This is a software computing resource that runs within an outer node and which itself provides a
service to host an execute other executable softwareelement.
The execution environment node are student, system, anddatabase.
PACKAGEDIAGRAM:
A package diagram is represented as a folder shown as a large rectangle with a top attached to its
upper left corner. A package may contain both sub ordinate package and ordinary model
elements. All uml models and diagrams are organized into package. A package diagram in
unified modeling language that depicts the dependencies between the packages that make up a
model. A Package Diagram (PD) shows a grouping of elements in the OO model, and is a
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).
User interfacelayer
Domainlayer
Technical serviceslayer
The three layer in the passport automation system are user interface layer, domain layer, technical
servicelayer
The user interface layer- represents the user interface components such as system,student.
The domain layer- has major actions such as course and paymentdetails.
Technical service layer- authenticated user only can access the technical services.
JAVACODING
Administrator.java
import java.util.Vector; public class administrator{
public Integer name; public Integeremail;
public Integer qualification; public Integerlist;
publicVector myregistration;
public void prof.info(){

}
public void course_info(){

}
public void student_info(){

}
Registration.java
import java.util.Vector; public class registration{
public Integer duration; public Integer paynow; private Integerafter;
publicVector myadministrator;
public void courseoverview(){

}
public void course_schedule(){

}
public void billing_system(){

}
}
User.java
public class user { public Integer name; public IntegerBadge;
public Integercomp.course;
public Integer accomplishment; public void profile(){
}
public void search(){

}
RESULT:
EXPERIMENT NO:
DATE ONLINE TICKET RESERVATION SYSTEM (E-TICKETING)
AIM
PROBLEMSTATEMENT
1. An E-Ticket (Electronic ticket) is a paperless electronic document used for ticketing

passengers, particularly in the commercial airline, railwayindustries.
2. An E-Ticket offers many advantages for both travelers and airline including security,
flexibility and cost convenience. At the same time, it also provides the standard
assurance of the traditional paper ticket, scaling choice, travel time options and other
flexibilities.
3. Passengers typically print out copies of their E-Ticket including confirmation E-mail
and other document. All those documents can be replaced by pulling them out of the
computer again and only a person with proper identification can actually use an E-
Ticket.
4. E-Ticket passengers can receive everything from gate assignments to cancellation or

delay through E-mail, text messages sent to their home or business computers or to
their cellphones.
5. Finally, using E-Ticket is a more environmental friendly approach. The main purpose
of the online bus ticket system is to provide another way for transnational customers
to buy theirtickets.

SPECIFICATION
1.0 Introduction
1.1 Purpose
1.2 Scope
1.4 Reference
1.6 Tools to beused
1.7 Overview
2.4 Systemfunction
2.6 Constraints
1.1 INTRODUCTION
E-Ticketing is an environmentally friendly approach to ease the customer inbooking

their tickets conveniently rather than their traditional way of getting thetickets.
1.2 PURPOSE
An Electronic ticket system is a more efficient method of ticket entry, processing and
marketing for companies in the railways, flight and other transport industry. These tickets can
be ordered over the internet and printed. Electronic tickets are also available in smart phones
and shown as SMS or MMS. Due to these facilities we go forE-Ticketing.
1.3 SCOPE
E-Ticketing avail future scope too as of implementing via mobile apps,mobile

version, home delivery, call center support,etc.
1.4 DEFINITIONS,ACRONYMSANDTHEABBREVIATIONS
1. Ad-On – Extra buses at extracost

2. Dep –Departure
3. ETA – Estimated time ofarrival
4. ETD – Estimated time ofdeparture
5. FOP – Form ofpayment
6. N/A – Notavailable
7. HTML – It is the standard set of formatting codes which are inserted into a text file
that is published on the world wideweb
8. HTTP – Hyper Text Transfer Protocol, graphics and text over theinternet
1.5 REFERENCES: IEEE Software Requirement Specificationformat.
1.6 TECHNOLOGIES TO BE USED: Microsoft Visual Basic6.0
1.7 TOOLS TO BE USED: StarUML tool (for developing UMLPatterns)
1.8 OVERVIEW
SRS includes two sections overall description and specific requirements - Overall
description will describe major role of the system components and inter-connections. Specific
E-Ticketing makes it simple for the customers to make reservation without waiting
according to their needs in a place whether they stay rather than moving over to the ticket
counters.
1. Front End Client –The customer and E-Ticketing online interface is built usingJSP
and HTML web server – Glassfish ApplicationServer.
2. Back End – Oracledatabase.
The server is directly connected to the client system. The client system has accessto
the database in thesystem.
2.5 FUNCTIONS
The purpose of E-Ticketing system is to book the ticket viaonline.
2.6 USABILITY
The User Interface makes E-Ticketing to be simple and efficient. I.e. The system will
help the customer to place their details and book ticketseasily.
2.7 PERFORMANCE
It describes the capability of the system to maintain the details without any dataloss.
2.8 RELIABILITY
The E-Ticketing system should be able to maintain the details with the correctroute
updates.
1. The passengers and admin should have basic knowledge of computer and English
language.
2. The passenger is required to have a hardcopy of theticket.
UMLDIAGRAMS
S.NO UMLDIAGRAMS
1 Use Casediagram
2 Classdiagram
4 Sequencediagram
7 Activitydiagram
8 Componentdiagram
9 Deploymentdiagram
10 Packagediagram
GANTTCHART:
USECASEDIAGRAM:
a. Theactorsinusecasediagramarecustomers,T.admin,bankandadmin.
b. The use cases are the activities performed by theactors.
c. The actors using the use case are denoted by thearrow.
d. The use cases present here are login, check availability, book ticket, cancel
ticket, get registered, admin login, journey details, refund, payment gateway,
update details, maintain details, customerdetails.
Customer:
The passenger is used to book and cancel the tickets. The passenger makes useof
bank to make his/hertransaction.
T.admin:
The train admin has all the informations/details of all the train .The trainadmin
displays he list of trains to the customer as per the request given by thecustomer.
Bank:
The bank is used for collecting payment on booking tickets and refundingon
cancelling thetickets.
Admin:
The admin actor is used to validate the username & password details of the customer.
CLASSDIAGRAM

a. CUSTOMER- customer is the class name. Its attributes are name, email id,
phone no. The operations performed by the passenger are login, booking,
cancellation, checkavailability.
b. ADMIN- Admin is the class name. Its attributes are username, password. The
operations performed by administrator are updation and validation.
c. BANK-Bank is the class name. Its attributes are bank name, account no, pin
no,etc.., The operations performed by banking are payment andrefund.
d. T.ADMIN-T. admin is the class name. Its attributes are train details. The
operations performed by T. admin are updating and maintaining the details
oftrain.
SEQUENCEDIAGRAM

representobject.
Sequence diagram illustrate instructions in a kind of fence format in which newobject

is added to the object. From the customer, the login moves on to the server. On checking the
availability, the server provides its response to the customer. Likewise the booking operation,
cancellation operation, payment, refund, updating the details and maintaining those in the
database taken place in a particular sequence as each event occurs. The disadvantage of
sequence diagram is that it is forced to extend to the right when adding new objects which
consumes a mix of horizontalspace.

operation of the system in realtime.
STATE CHARTDIAGRAM
The state chart diagram contains the states in the rectangle boxes and starts in
indicated by the dot and finish is indicated by dot encircled. The purpose of state chart
diagram is to understand the algorithm in the performingmethod.
a. The states of the E-ticketing system are denoted in the state chartdiagram
b. The details of the train selected state represents the process of checking the
availability of the seats,time of the train,the stations it passesthrough.
c. In book the tickets state, it checks whether the customer has provided all the
details about the source anddestination
ACTIVITYDIAGRAM
An activity diagram is a variation or special case of a state machine in which the

states or activity representing the performance of operation and transitions are triggered by
the completion of operation. The purpose is to provide view of close and what is going on
inside a use case or among several classes. An activity is shown as rounded box containing
the name ofoperation.
a. The activities in the e-ticketing system are login, check availability, booking
ticket, payment, cancellation and updatedetails
b. In the login activity, passenger give username and password and then login
into the e-ticketing system after then fill the details that are required for
bookingtickets.
c. After the payment procedure completed successfully, the ticket isprinted.
COMPONENTDIAGRAM
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 systems. It is represented by boxed
figure. Dependencies are represented by communicationassociation.
a. The components in the e-ticketing system are customer, T.admin, bank,admin.
b. customer,T.admin,admin and bank that are dependent on e-ticketing system

are shown by the dottedarrow
DEPLOYMENTDIAGRAM

dimensional box. A deployment diagram in the unified modeling language serves to model the
association. The basic element of a deployment diagram is a node of two types
DEVICENODE–
A physical computing resource with processing and memory service toexecute

software, such as a typical computer or a mobilephone.
This is a software computing resource that runs within an outer node and it
providesa service to host and executes other executable softwareelement.
The device node is e-ticketing system and execution environment node are passenger,
system, ticket anddatabase.
PACKAGEDIAGRAM

o Domainlayer
The three layer in the e-ticketing system are user interface layer, domain layer,
web,passenger,visitor,bank,andticketadministrator.
b. The domain layer- has major actions such as give and get details,
authentication and printtickets
c. Technical service layer- authenticated user only can access the technical
services.
JAVACODING
ADMIN.JAVA
public classadmin
{
public Integer username;
public Integer password;
public voidgetlogindetails()
{
}
public voidchecklogindetails()
{
}
}
BANK.JAVA
public classbank
{
public Integer bank name;
public Integer username;
public Integer card type;
public Integer accnumber;
public Integeramt;
public Integer balance amt;
public Integer expire date ofcard;
public Integer pinnumber;
public voidgetuserdetails()
{
}
public voidcalc_balance()
{
}
public voiddisplay_balance()
{
}
public voidgetcard_details()
{
}
public voidvalidate_carddetails()
{
}
}
CUSTOMER.JAVA
public classcustomer
{
public Integerusername;
public Integer password;
public Integer age;
public Integer gender;
public Integername;
public voidgivelogindetails()
{
}
public voidgivecustomerdetails()
{
}}
TADMIN.JAVA
public classTadmin
{
public Integer trainnam;
public Integer trainnumber;
public Integerseatavailability;
public Integertime;
public Integer date;
public IntegernewAttr;
public Integersations;
public Integer noofpassengers;
public Integernoofcompartments;
public voiddisplaytraindetailos()
{
}
public voidgetcustomerdetails()
{
}
public voiddisplayticket()
{
}
}
RESULT:
EXPERIMENT NO:
DATE SOFTWARE PERSONNEL MANAGEMENT SYSTEM
AIM
PROBLEMSTATEMENT
1. Software Personnel Management System is a robust system capable of putting

detailed data for senior faculty and investigations and their supporting staff attheir
fingerprints.
2. Personal information of employee are stored in the database by anadministrator
3. An employee or Human Resource manager logs into the system by undergoing
authentication and authorization mechanisms to view the personal informationof
theemployees
4. Employee after viewing his personal details, logs out; Human Resourcemanager
can view many employee’s details and logsout

1.0 Introduction
1.1 Purpose
1.2 Scope
1.4 Reference
1.6 Tools to beused
1.7 Overview
2.4 Systemfunction
2.5 UserCharacteristics
1.1 INTRODUCTION
Software Personnel Management system is an interface between the Human Resource

manager, an employee and the database which stores the personal information of the
employees. It aims at giving detailed data for senior faculty about their supporting staff at
their fingerprints.
1.2 PURPOSE
Instead of taking a record notebook and analyzing an employee’s personal details

since the time he joined the organization, the Human Resource manager could simply logs
into the Personnel Management system and views the detail of an employee whom hewants.
1.3 SCOPE
The System provides an online interface to the employee where they can view their
personal details and their performance in that organization. The Human Resource Manager
who is concerned with the system could reduce his workload and easily manipulate personal
information of employees. It also provides a communication platform between the Human
Resource manager and the employees of theorganization.
1.4 DEFINITIONS,ACRONYMSANDTHEABBREVIATIONS
1. HR-Human Resource manager, refers to the higher official who needs to know
about every employee in hisorganization
2. Administrator - Refers to the super user who is the Central Authority who has been
vested with the privilege to manage (updating) the entiresystem.
3. Employee- workers of theorganization
4. PMS- Personnel ManagementSystem
1.5 REFERENCES
IEEE Software Requirement Specificationformat.
1.6 TECHNOLOGIES TO BEUSED
• Microsoft Visual Basic6.0
1.7 TOOLS TO BEUSED
 StarUML (for developing UMLPatterns)
1.8 OVERVIEW
SRS includes two sections overall description and specific requirements - Overall
description will describe major role of the system components and inter-connections. Specific
The PMS acts as an interface between the HR, employee and thedatabase.
This system tries to make the interface as simple as possible and at the same time notrisking
the security of data stored in. This system helps the HR to manipulate the personal
information of the employees in an easyway.
1. Front End Client - The applicant andAdministrator online interface is built using
The server is directly connected to the client-HR and employee systems. Theclient
systems have access to the database in theserver.
2.5 SYSTEMFUNCTIONS

2. MessageboxforPassportApplicationStatusDisplaybytheAdministrator.
3. Administrator can generate reports from the information and is the onlyauthorized
1. HR- He is the person who views all the details, takes actions and investigations over
hisstaff.
2. Employee- They are the workers of the organization who would like to know about
their personal details and their performance in theirjob.
1. The HR and employee should belong to that organization for which the PMS is
developed.
2. The employee can view only his personal detail whereas HR can view details of all
theemployees.
UMLDIAGRAMS
S.NO UMLDIAGRAMS
1 Use Casediagram
2 Classdiagram
4 Sequencediagram
7 Activitydiagram
8 Componentdiagram
9 Deploymentdiagram
10 Packagediagram
GANTTCHART:
USECASEDIAGRAM:
1. The actors in use case diagram are HR,Employees- team lead, project lead,
softwareengineer
a. The use cases are Login, recruit, training, performance, increment,salary.
b. The actors who uses the use case are denoted by thearrow.
c. The login use case checks the username and password for the administrator,
HR and theemployees.
d. The recruit use case is used by the HR to view the recruitment details of the
employees
e. The training use case is used by both HR and employee to view the training
process undergone by the employee during their trainingperiod
f. The performance use case is used by HR and employee to view an employee’s
performance since he wasappointed.
g. The appraisal is done by HR and information regarding the employee can be
discussed with the employee throughonline
h. The increment use case is used by the HR to do increment the salary based on
the performance of theemployee
i. The salary use case is used by HR to update the incremented salary detail into
the employee’sprofile
CLASSDIAGRAM

a. Human Resource- the Human Resource Manager ha attributes such as

curriculum vitae, recruitment, salary and operations are login, recruit,
performance monitor, increment. He recruits an employee, monitors his
performance, increments hissalary.
b. Employee- The employee has attribute such as authentication, bank details,
regularity and operations are login, register, training, performance, and salary.
An employee logins into the PMS and registers if he is newly appointed,views
his training details, performance, salary, and other personaldetails.
c. Human Resource Personnel- Human Resource Personnel has
operations such as complaints, motivate. He guides his teammembers.
d. Appraisal- This class is used to store attributes such as performance and
attendance. It also performs operations such as Pay Calculation and provides
Increment, ifany.
e. Employee Details- This class is used to store attributes such as name,
phone number, salary, email ID and Employee ID. It also has an operation
Attendance.
SEQUENCEDIAGRAM

representsobject.
a. The HR adds employees to the database and an employee can login to view
the updated details of his trainingdetails
b. The HR updates the training details into the database The HR monitors the
performance details and updates it in the database from which the employee
knows his personaldetails.
c. The HR performs salary increments based on the performance of employee
and updates the salary details into thedatabase.
d. Employee views his details and logs out of thesystem.

operation of the system in realtime.
STATE CHARTDIAGRAM
The state chart diagram contains the states in the

rectangle boxes and starts in indicated by the dot and finish is indicated by dot encircled.The
purpose of state chart diagram is to understand the algorithm in the performingmethod.
a. The states of the PMS are denoted in the state chartdiagram

b. Login state represent authentication for login thePMS.
required.
d. Based on whether it is the HR or the Employee, the interface and functions
change.
e. If there are any changes made by the user, then it is updated in thedatabase.
ACTIVITYDIAGRAM
An activity diagram is a variation or special case of a state machine in which the

states or activity representing the performance of operation and transitions are triggered by
the completion of operation. The purpose is to provide view of close and what is going on
inside a use case or among several classes. An activity is shown as rounded box containing
the name ofoperation.
a. The activities in the PMS are login, update details, view details, orlogout.
b. HR logs in, he starts by entering the employee id, searches the employees
name in the employee list, views personal details including performance,
contributions to the organization, and update salary details, then either returns
to the home page to view some other employee or logsout.
c. An employee logs in, views his personal details and other details such as
recruitment, salary, training, project details and logsout.
COMPONENTDIAGRAM
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 communicationassociation.
a. Some of the components in the PMS are salary, salary increment, salary
updatedcomponents.
b. Salary updation component is dependent on salary increment component
which in turn depends on the salarycomponent.
DEPLOYMENTDIAGRAM
It is a graph of nodes connected by communication association. It is represented by a
three dimensional box. A deployment diagram in the unified modeling language serves to
model the physical deployment of artifacts on deployment targets. Deployment diagrams
show "the allocation of artifacts to nodes according to the Deployments defined between
them. It is represented by 3-dimentional box. Dependencies are represented by
communication association. The basic element of a deployment diagram is a node of two
types
HR recruits employee for a company employee recruited by HR goes under training

before actually working. Training period is given to the employee with the training details.
The salary details for the employee areprovided.
PACKAGEDIAGRAM

package diagram in unified modeling language depicts the dependencies between the
JAVACODING
HR.java
public class HR {
public String Name;
public StringEmailID;
public IntegerEmpID;
public Integer PhoneNumber;
public IntegerSalary;
public VectorSearch_Details;
public Vector Search_Details;

public Vector myAppraisal;
public Vector myAppraisal;
public void Recruit(){
public void Train(){
public void Search_Details(){
public void Appraisal(){
public void Fire_Employee(){
HR_Personnel.java
public class HR Personnel extends HR{
public void Complaints(){

}
public void Motivate(){

}
Employee.java
import java.util.Vector;
public class Employee{
public String Name;
public String EmailID;
public IntegerPhoneNumber;
public Integer Salary;
public IntegerAttendance;
public Vector myEmployee_Details;
public Vector myEmployee_Details;
public void Show_Details(){
public void Performance(){
Employee_Details.java
public class Employee_Details{
public StringName;
public StringEmailID;
public Integer PhoneNumber;
public IntegerSalary;
public void Attendance(){
Appraisal.java
import java.util.Vector;
public class Appraisal {
public Integer Performance;
public IntegerAttendance;
public Vector myHR;
public VectormyEmployee_Details;
public void Pay_Calculator(){

}
public void Increment(){

}
RESULT:
EXPERIMENT NO:
DATE CREDIT CARD PROCESSING SYSTEM
AIM
PROBLEMSTATEMENT
A. Credit card is used by customers for the transactions and processing money between
customers. When the customer uses credit card, the administrator enquires about the pin
number and the authenticationdetails.
B. Ifallthedetailsgivenbythecustomerarevalidthenthetransactionofmoneytakesplace.
When it is used for processing money for institutions transactions and retranslations takes
place between the customer and the agent for sponsoring finance and manage customer
account.
C. The credit card is one of the most devise products among all the financial tools available.
The most of the people pay all their expenses using creditcard.

1.0 Introduction
1.1 Purpose
1.2 Scope
1.4 Reference
1.6 Tools to beused
1.7 Overview
2.4 Systemfunction
2.6 Constraints
1.0INTRODUCTION
Credit card processing System is an interface between the Customer and the Bank is responsible
for the Issue of Credit card. It aims at improving the efficiency of online application and reduces
the complexities involved in it to the maximum possibleextent.
1.1PURPOSE
Thecreditcardismorenecessarynowadays.soifweneedtogetacreditcardwecannotgotobank stand in
a queue and fill the form and doing so many procedures .this online registration is very useful
for the customers. They can apply for their credit card in their home itself. After the verification
done a mail or a message will be received we need to get credit card from bank. Nowadays
everybody have their own creditcard.
1.2 SCOPE
 Thesystemprovidesanonlineinterfacetotheuserwheretheycanfillintheirpersonaldetailsand submit.
 The manager than verifies his bank account .if the customer has enough bankaccount.
 Themanageraftercertaindayshewillissuethecreditcardtocustomerthatwillhappenmanually.
 The mode of purchase becomes easier with credit card and shopping simpler as it can be done
through online or evenphone.
CCP- Credit Card Processor is an organization that manages that process oftransferring
authorized and captured credit card funds between different financialaccounts
Chargeback (CHGB) – is a procedure used by the bank who issues the card where it returnsthe
disputed amount of money to the customer through the merchants transactionprocessor
ISP-Internet ServiceProvider.
1.6 TOOLS TO BE USED • Star UML tool (for developing UMLPatterns)

1.7 OVERVIEW
SRSincludestwosectionsoveralldescriptionandspecificrequirements-Overalldescriptionwill
describe major role of the system components and inter-connections. Specific requirements will
describe roles & functions of theactors.
Credit Card processing system acts as an interface between the 'Customer' and the ‘Bank’. 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 Credit
Card.
2 SOFTWAREINTERFACE
1. Front End Client - The applicant and Administrator online interface is built using Microsoft
Visual Basic6.0.
2 HARDWAREINTERFACE
The server is directly connected to the client systems. The client systems have access tothe
2.4 CONSTRAINTS
1. The customer requires a computer to submit theirinformation.

2. Although the security is given high importance, there is always a chance of intrusion in the web
world which requires constantmonitoring.
2.5ASSUMPTIONS ANDDEPENDENCIES
The vendor and customer must have basic knowledge of computers and English language .the
vendor may be required to deliver the item purchased by thecustomer.
UMLDIAGRAMS
S.NO UMLDIAGRAMS
1 Use Casediagram
2 Classdiagram
4 Sequencediagram
7 Activitydiagram
8 Componentdiagram
9 Deploymentdiagram
10 Packagediagram
GANTTCHART:
MONTH 1 MONTH 2 MONTH3

Weeks 2 4 6 8 10 12 14
REQUIREMENT AND 4
SRS WEEKS
4
ANALYSIS ANDDESIGN WEEKS
MODULE1 2WEEKS
4
MODULE2 WEEKS
MODULE3 4WEEKS
TESTING 2WEEKS
MAINTANCE 4WEEKS
USE CASEDIAGRAM:
Use cases define interactions between external actors and the system to attain particulargoals.
There are three basic elements that make up a usecase:
 Actors: Actors are the type of users that interact with thesystem.
 System: Use cases capture functional requirements that specify the intended behavior of the
system.
 Goals: Use cases are typically initiated by a user to fulfill goals describing the activities and
variants involved in attaining thegoal.
Use cases are modeled using unified modeling language and are represented by ovals containing
the names of the use case. Actors are represented using lines with the name of the actor written
below the line. To represent an actor's participation in a system, a line is drawn between the actor
and the use case. Boxes around the use case represent the systemboundary.
1. The actors used in credit card processing are bank, manager, andcustomer.
2. And the actors are connected with use cases bylinks
3. The use cases are represented by ovalshape.
4. In use case diagram generalization is alsoused.
CLASSDIAGRAM
horizontal lines. The top compartment holds the class name and middle compartment holds the
attribute and bottom compartment holds list ofoperations.
APPLICANT-The applicant has attribute such as name and password and operations are login,
register and swipe. The applicant login and fill the details that are required for applying the credit
card.
ACCOUNT-The Account has attributed such as account number and operation is deposit,
withdraw, andsavings.
CREDIT CARD- the Credit card has attributed such as card number, validfrom, valid to and
operation iswithdrawn.
MANAGER-The Manager has attributed such as manager id, password, branch name and
operation are verify details, issue card. The manager gets the details form database and verifies
with their database, update the verification and issue thecard.
SEQUENCEDIAGRAM:
Itshowsobjectparticipatingininteractionbytheirlifelinebythemessagetheyexchangearranged in time
sequence. Vertical dimension represent time and horizontal dimensionrepresent
A. The applicant login the database and give his details and database store thedetails.
B. The manager gets the details from the database and doesverification.
C. Using the credit card we can do transactions like withdrawcash.
A collaboration diagram is similar to sequence diagram but the message in number format. In a
collaboration diagram sequence diagram is indicated by the numbering the message. A
sophisticated modeling tool can easily convert a collaboration diagram into a sequencediagram
functionality and behavior of individual objects as well as the overall operation of thesystem.
STATE CHARTDIAGRAM
Thestatechartdiagramcontainsthestatesintherectangleboxesandstartsinindicatedbythedot and
finish is indicated by dot encircled. The purpose of state chart diagram is to understand the

A. The states of the credit card processing system are denoted in the state chartdiagram
B. Login state represent authentication for login the credit card processingsystem.
C. In this state, it checks whether the applicant has provided all the details that isrequired.
ACTIVITYDIAGRAM
operation.Thepurposeistoprovideviewofcloseandwhatisgoingoninsideausecaseoramong several
classes. An activity is shown as rounded box containing the name ofoperation.
A. The activities in the passport automation system are login, submit details, and get details, issue
card andverification.
B. In the login activity applicant give username and password and then login into the credit card
processing system after then fill the details that are required forapplication.
C. After the verification procedure completed successfully the credit card is issued to theapplicant.
COMPONENTDIAGRAM
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
The components in the credit card processing system are customer, register, verify,login.
DEPLOYMENTDIAGRAM
DEVICENODE–
Aphysicalcomputingresourcewithprocessingandmemoryservicetoexecutesoftware,suchasa typical
computer or a mobilephone.
The device node is credit card processing system and execution environment node are customer,
database,admin.
PACKAGEDIAGRAM
Apackagediagramisrepresentedasafoldershownasalargerectanglewithatopattached to its
upper left corner. A package may contain both sub ordinate package and ordinary model
elements.Allumlmodelsanddiagramsareorganizedintopackage.Apackagediagraminunified
modeling language that depicts the dependencies between the packages that make up a model. A
Package Diagram (PD) shows a grouping of elements in the OO model, and is aCradle
extensiontoUML.PDscanbeusedtoshowgroupsofclassesinClassDiagrams(CDs),groupsof
componentsorprocessesinComponentDiagrams(CPDs),orgroupsofprocessorsinDeployment
Diagrams(DPDs).
 User interfacelayer
 Domainlayer
 Technical serviceslayer
The three layers in the passport automation system are user interface layer, domain layer,and
 The user interface layer- represents the user interface components such as web, customer, and
bankmanager.
 The domain layer- has major actions such as give details, verification, andissue.
 Technical service layer- authenticated user only can access the technicalservices.
JAVACODING
CUSTOMER.JAVA:
Public classCustomer
{
Private amountloaned;
Loaned amount()
{
}
Public Remaining loan ()
{
}
Public Due date()
{
Repay()
{
}}
BANKDATABASE.JAVA
Public classBankdatabase
{
Public customer details()
{
Creditloan();
}
Public employee details()
{
Warn();
}
Public void authorizationdetails()
{
Blockcard();
}
Public void swipe()
{
}}
EMPLOYEE.JAVA:
Public classEmployee
{
Public credit card()
{
Creditloan();
}
Public void customer details()
{
}
Public salary()
{
Warn();
Collect();
}}
RESULT:
:
EXPERIMENT NO:
DATE E-BOOK MANAGEMENT SYSTEM
AIM:
PROBLEMSTATEMENT:
1. E-book Management System gives an idea about how books are maintained in the
particular websites. The books that are to be purchased, the books that are to be sold
are maintainedhere.
2. 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 authorizedway.
The password and user id has been set here.
3. The website has to be maintained properly since the whole e-book purchase process
can be improved. E-book management in this project gives the idea about how e-books
are maintained in a particularconcern.
4. The book details which includes the number of books available, no of pages and price.
E-book management in this project is understood by going through the modules that is
beinginvolved.

SPECIFICATION
1.0 Introduction
1.1 Purpose
1.2 Scope
1.4 Reference
1.7 Overview
2.4 Systemfunction
2.6 Constraints
:
1.1 INTRODUCTION
Ebook management gives an idea about how ebooks are maintained in the particular concern.
The ebooks that are to be purchased, the ebooks that are to be sold are maintained here. Further
some additional details of the current ebook list that is available in the website are alsogiven.
Ebook management in this project is done in an authorizedway
1.2 PURPOSE
The main objective of this project is to overcome the work load and time consumption which
makes the maintenance of the ebook in an organization as a tedious process. This project
provides complete information about the details of the ebook to the customers. This project
identifies the amount of book available. Separate modules have been created for purchasing,
viewing book details, and deliverydetails.
1.3 SCOPE
The scope of this ebook management is to maintain the book details after the purchase and
list of reaming books available in the same booktype.
1.4 DEFINITION, ACRONYMS ANDABBREVIATION

 CUSTOMER- Customer will purchase the books from theWebsite.
 DATABASE - Database is used to store the books and details ofbooks.
 ADMIN - Handles all the support features and the technical works in the
application
 BANK - Handles thepayment
1.6 TECHNOLOGIES TO BE USED Microsoft Visual Basic6.0
1.7 TOOLS TO BE USED starUML tool . (for developing UMLPatterns)
1.8 OVERVIEW
The overview of the project is to Storing of information about the ebooks and updating the
ebook list for each organization which is using this system, keeps track of all the information
about the ebooks purchased that are made by the customers, having registration feature of adding
up new customers to the organization are provided in thissystem.
2.2 PRODUCT PERSPECTIVE

the security of data stored in. This minimizes the time duration in which the user can easily
download the books
database in the server.
2.5 SYSTEMFUNCTIONS
 Secure Registration of information by theUsers.
 Administrator can update the details of thebooks.
 User - They are the people who desire to download the books and submit the information
to the database.
 Administrator - He has the certain privileges to upload and update books into the ebook
management system.He can also view the details of the users stored in thedatabase.
2.7 CONSTRAINTS

2. Although the security is given high importance, there is always a chance of intrusion in
the web world which requires constantmonitoring.
The user must have the basic knowledge of computer and English language. The user must
correctly login the database.
UMLDIAGRAMS
S.NO UMLDIAGRAMS
1 Use Casediagram
2 Classdiagram
4 Sequencediagram
7 Activitydiagram
8 Componentdiagram
9 Deploymentdiagram
10 Packagediagram
GANTTCHART:
17‐Dec‐14 27‐Dec‐14 6‐Jan‐15 16‐Jan‐15 26‐Jan‐15 5‐Feb‐15 15‐Feb‐1525‐Feb‐15
requirements
analysisand
design
module1
start
module2 date
module3
testing
maintainanac
e
USE CASEDIAGRAM:
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
usingellipse.
Actor is any external entity that makes use of the system being modeled. It is represented using
stickfigure.
REG NO:
The actors in this use case diagram are User, Admin,Bank and Database. The use cases
are the activities performed byactors.
 The website will give the booksavailable.
 Admin will update the books and has the overallcontrol.
 Customer will login and check the list of ebooks in thedatabase.
 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 orderdetails
 Login will gives us the entry for the customer of thisproject.
 Database will gives us the details about the total ebookavailable.
CLASSDIAGRAM:
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 have the class name, middle compartment the attributes and the bottom
compartment withoperations.
Thisclassdiagramhasfiveclassesusers,banks,administrator,database1anddatabase2.
 Users - is the class name. Its attributes are username and userid. The operations
performed in this class are login,register,search,download.
 Administrator -is the class name. Its attribute is adminid. The operations performed are
update, upload and login.
 Database - is the class name.The operation performed is store, verify andvalidate.
 Bank – is the class name.Its attributes are acc_no,bal.The operation performed ispayment.
SEQUENCEDIAGRAM:
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 twodimensions.
1. Vertical dimension-representtime.
2.Horizontal dimension-represent differentobjects.
 The sequence diagram describes the sequence of steps toshow

 The user register to thesystem.
 The homepage of the system will bedisplayed.
 The user login to the system and search thebooks.
 The available list of books will bedisplayed.
 The user will select and download the book they need and the payment will bedone.
 Admin has the control to update thebooks.
A collaboration diagram, also called a communication diagram or interaction diagram,. A

realtime.
1:register
5: userlogin
9: downloadbooks
2:verify
6: searchbooks
:user database
3: displayhomepage
8: displaybooks
10:payment
4: adminlogin
7:update/upload
bank
:admin
This collaboration diagram is to show how the user login and getting details of ebooks in
the ebook management system. Here the sequence is numbered according to the flow of
execution.
STATE CHARTDIAGRAM:
The purpose of state chart diagram is to understand the algorithm involved inperforming
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. A final state
isrepresented as circle surrounding a smalldot.
This state diagram describes the payment of thesystem.

 First state is entering card details where the user enters their card details to the ebook
managementsystem.
 The next state is making payment where amount will be debited in case of valid event
otherwise,error message will bedisplayed.
ACTIVITYDIAGRAM:

activity diagrams can be used to describe the business and operational step-by-step workflowsof
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 theoperation.
This activity diagram flow of stepwise activities performed insystem.

• First Customer login into the system then checks booksavailable.
• The book lists are verified and is given in a orderedformat.
• The needed book isselected.
• Enter your account details and purchase thebook.
COMPONENTDIAGRAM:
Thecomponentdiagramisrepresentedbyfiguredependencyanditisagraphofdesignof
relationships between the components of a system. It is represented by boxed figure.
Dependencies are represented by communicationassociation.
 The components in the passport automation system are ebook management systemis
user, database andadmin.
 User and Admin are dependent on database are shown by the dottedarrow.
DEPLOYMENTDIAGRAM
A deployment diagram in the unified modeling language serves to model the physical
artifacts to nodes according to the Deployments defined between them. It is represented by3-
dimensional box. Dependencies are represented by communicationassociation.
The processor in this deployment diagram is the online recruitment system which is themain
part and the devices are the select and payment which are the some of the main activities
performed in thesystem.
PACKAGEDIAGRAM
A package diagram in unified modelinglanguage depicts the dependencies betweenthe
OO model, and is a Cradle extension toUML.
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).
 User interface layer: consists of the form and login. This layer describes howthe
customer. Logins and books maintained inwebsite.
 Domain layer: shows the activities that are performed in the ebook managementsystem.
The activities are books are purchased from thewebsite.
 Technical services layer: the update the account details and buy the book bypayment
through theaccount.
JAVAPROGRAM
STUDENTS ANDSTAFF.JAVA
importjava.util.Vector;
public class studentand staff

{
public Integerid;
publicString name;
publicString dept;
public Integerregno;
publicVector mydatabase;
public voidlogin()
{
}
public voidsearch()
{
}
public voiddownload()
{
}
public void logout(){

}
}
ADMIN.JAVA
public classadmin
{
public Integer id; public
Stringname;
publicVector mydatabase;
publicVector mypublisher;
public voidlogin()
{
}
public voidnewbook()
{
}
public voidbuy()
{
}
public voidupdate()
{
}
public void logout(){
}
}
DATABASE.JAVA
public classdatabase
{
public Integer id; public
Stringname;
publicVector
mystudentandstaff;public
Vector myadmin;
public voiddetails()
{
}
public voiddownloadbook()
{
}
public voidupdatebook()
{
}
public voidpayment()
{
}
}
PUBLISHER.JAVA
public classpublisher
{
public Integer publisherid; public
Stringname;
publicVector myadmin;
public voidpublishnewbook()
{
}
public voidsellbook()
{
}
public voidpayment()
{
}
}
RESULT:
:
EXPERIMENT NO:
DATE ONLINE RECRUITMENT SYSTEM
AIM
PROBLEM ANALYSIS AND PROJECTPLANNING

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 thejob.
PROBLEMSTATEMENT
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 followingsteps,
• The applicant login to the online recruitmentsystem.

• They register to the company for thejob.
• They appear forexamination.
• Based on the outcome of the exam, the best applicant isselected.
• The recruiter informs the applicant about theirselection.
SNO SPECIFICATION
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
recruitment system that is performed in company website. In this we give specification.the
system requirements that are apart from the functionality of the system to perform the
recruitment of the jobseekers. It tells the usability, reliability defined in use case
specification.
2. OBJECTIVE
The main objective of Online Recruitment System is to make applicants register
themselves online and apply for job and attend the exam. Online Recruitment System
provides online help to the users all over theworld.
3. OVERVIEW
The overview of the project is to design an online tool for the recruitment process
which ease the work for the applicant as well as the companies. Companies can create their
company forms according to their wish in which the applicant canregister.
4. GLOSSARY
TERMS DESCRIPTION
CANDIDATES Applicant can register
himself.Afterregistration,he will be directed to
his homepage. Here he can update his profile,
change password and see the examination details
andall.
ADMIN Admin verify applicant detailsandconduct

examination, approve or disapprove applicant
attending examination and provides results about
the selectedapplicant.
DATABASE Database is used to verify login andstorethe

details of selectedapplicants.
USER Applicant and thereader
SOFTWARE REQUIREMENT This software specification documents full set of

SPECIFICATION features and function for onlinerecruitment
system that is performed in companywebsite.
The main functionality of recruitment system is to recruit the applicant for the job in their
company.
8. USABILITY
User interface makes the Recruitment system to be efficient. That is the system will
help the applicant to register easily and helps the companies to recruit the applicant
effectively. The system should be userfriendly.
9. PERFORMANCE
It describes the capability of the system to perform the recruitment process of the
applicant without any error and performing itefficiently.
10. RELIABILITY
The online recruitment system should be able to serve the applicant with correct
information and day-to-day update ofinformation.
11. FUNCTIONALREQUIREMENTS
Functional requirements are those refer to the functionality of the system. That is
the services that are provided to the applicant who apply for thejob.
UMLDIAGRAMS
The following UML diagrams describe the process involved in the online recruitmentsystem
• Use casediagram
• Classdiagram
• Sequencediagram
• Collaborationdiagram
• State chartdiagram
• Activitydiagram
• Componentdiagram
• Deploymentdiagram
• Packagediagram
GANTTCHART:
USE CASEDIAGRAM
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
modelled. It is represented using stickfigure.
The actors in this use case diagram are applicant, recruiter and database. The use cases are
the activities performed byactors.
The actors in this use case diagramare

• Candidates - logins the recruitment system and register for the job and attend the test
conducted at somevenue.
• Admin - send the interview details, select talented applicant and send appointment letter to
them.
Databases - verify the login and register details and selected applicant details are stored in it.
The use cases in this use case diagramare
• Login - applicant enter their username and password to enter in to the recruitmentsystem
• Register – applicant register in to the recruitment system forjob.
• Evaluation window– it evaluates the candidatesdetails.
CLASSDIAGRAM
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 have the class name, middle compartment the
attributes and the bottom compartment withoperations.
This class diagram has three classes applicant, recruiter anddatabase.
• Candidate – 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
applicantdetails.
• Admin – 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.
• Database – is the class name. The operations performed are storing applicant details,
verifying login and storing selected applicantdetails.
SEQUENCEDIAGRAM
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 twodimensions.
1. Vertical dimension-representtime.
2. Horizontal dimension-represent differentobjects.

REGISTER
This sequence diagram describes the sequence of steps toshow
• The applicant login in to the recruitment system and register forjob.
• The verification done in the database andrecruiter
• The interview details are send to the applicant byrecruiter.
SELECTINGCANDIDATES
This sequence diagram shows steps toshow
• The applicant attend aptitude test and they are short listed based onevaluation
• The applicant appear for technicalround
• The talented applicant isselected.

• This detail is stored in thedatabase.
COLLABRATIONDIAGRAM
A collaboration diagram, also called a communication diagram or interaction

diagram,. A sophisticated modeling tool can easily convert a collaboration diagram into a
operation of the system in realtime
DOCUMENTATION OF COLLABRATION DIAGRAM
REGISTER
This collaboration diagram is to show how the applicant login and register in the recruitment
system. Here the sequence is numbered according to the flow ofexecution.
SELECTINGCANDIDATES
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 thenumbers.
STATE CHARTDIAGRAM
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. A
final state is represented as circle surrounding a smalldot.
• First state is login where the applicant login to the recruitmentsystem.
• The next state is register where the applicant registers forjob.
• Then verify the applicant details and sent interviewdetails.
• The applicant appears fortest.
• Update database with details of selectedapplicant.
ACTIVITYDIAGRAM
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 theoperation.
This activity diagram flow of stepwise activities performed in recruitmentsystem.
• First the applicant login thenregisters.
• The applicant details are verified and interview details are sending to applicant byrecruiter.
• Applicants appear fortest.
• Recruiter select talentedapplicant.
COMPONENTDIAGRAM
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
The main component in this component diagram is online recruitment systems. And register,
attend test and select talented applicants are the components comes under the main
component.
DEPLOYMENTDIAGRAM
dimensional box. Dependencies are represented by communicationassociation.
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 thesystem.
PACKAGEDIAGRAM
A package diagram in unified modeling language that depicts the dependencies

between the packages that make up a model. A Package Diagram (PD) shows a grouping of
elements in the OO model, and is a Cradle extension to UML. PDs can be used to show
groups of classes in Class Diagrams (CDs), groups of components or processes in
Component Diagrams (CPDs), or groups of processors in Deployment Diagrams(DPDs).
• User interface layer - software objects representing domain concepts that fulfill application
requirements, such as calculation a saletotal.
• Domain layer – layer that contains domain objects to handle application logicwork.
• Technical services layer – general purpose objects and subsystems that provide supporting
technical services, such as interfacing with a database or errorlogging.
• The User interface layer - consists of the web and login. This layer describes how
the applicant logins to the website and apply for thejob.
• The Domain layer – shows the activities that are performed in the online
recruitment system. The activities are register, attend test and select talentedapplicant.
• The Technical service layer - the applicant details, verification details and the selected
applicant details are stored in thedatabase.
CODEGENERATION:
JobSeeker:
importjava.util.Vector;
public class Job_Seekers{
public StringLoginID;
public StringPassword;
public IntegerMarks;
public void Upload_Resume(){

}
public void Company_List(){
}
public void Online_Test(){
}
public void Results(){
}
}
Admin:
public class Admin{
public StringLogin;
public StringPassword;
public IntegerDatabaseKey;
public void Manage_SIte(){

}
}
}
HR:
public class HR { private
StringLoginID;
public Character Designations;
public IntegerExperience;
public void Company_Profile(){

}
public void Details_of_Vacancies(){

}

}
RESULT:
EXPERIMENT NO:
DATE FOREIGN TRADING SYSTEM
AIM:
PROJECT ANALYSIS AND PROJECTPLANNING
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.
PROBLEMSTATEMENT
The steps involved in Foreign Trading Systemare:

• The Forex system begins its process by getting the username and password from thetrader.
• Aftertheauthorizationpermittedbytheadministrator,thetraderisallowedtoperformthesourcing to
know about the commoditydetails.
• After the required commodities are chosen, the trader places theorder.
• Theadministratorchecksfortheavailabilityfortherequiredcommoditiesandupdatesitinthe
database.
• Afterthecommoditiesarereadyforthetrade,thetraderpaystheamounttotheadministrator.
• Theadministratorinturnprovidesthebillbyreceivingtheamountandupdatesitinthedatabase.
• The trader logouts after the confirmation message has beenreceived.
SOFTWARE REQUIREMENTSPECIFICATION:

SPECIFICATION
1 Introduction
2 Objective
3 Overview
4 Glossary
5 Purpose
6 Scope
7 Functionality
8 Usability
9 Performance
10 Reliability
1. INTRODUCTION:
International trade is exchange of capital, goods, and services across international borders or
territories. In most countries, it represents a significant share of gross domestic product (GDP). While
international trade has been present throughout much of history (see Silk Road, Amber Road), it’s
economic, social, and political importance has been on the rise in recent centuries. Industrialization,
advanced transportation, globalization, multinational corporations, and outsourcing are all having a
major impact on the international trade system. Increasing international trade is crucial to the
continuance of globalization. Without international trade, nations would be limited to the goods and
services produced within their ownborders.
2. OBJECTIVE:
The main objective of Foreign Trading System is to make the traders to do trading process easily
through online as the forex is open 24 hours aday.
3. OVERVIEW:
Theoverviewoftheprojectistodesignanonlinetoolfortheforeigntradingprocessanditoversees the
implementation, administration and operations covered in foreigntrade.
4. GLOSSARY:
TERM DESCRIPTION
TRADER Person who trades for thecommodities
ADMINISTRATOR One who coordinates the entire tradingprocess
DATABASE All the transaction details are shortedhere.
READER Person who is viewing thewebsite
USER The traders and the viewers
aretheusersSOFTWARE REQUIREMENT This software specification
documents fullsetofSPECIFICATION Features and function for foreign
tradingsystem
5. PURPOSE
The primary purpose of the Forex is to assist international trade and investment, by allowing
businesses to convert one currency to another currency. That is, In a typical foreign exchange
transaction, a trader purchases a quantity of one currency by paying the quantity of another
currency.
6. SCOPE
There are a lot of advantages in Forex Trading as compared to many other financial trading, like
futures or stock trading. The Forex market is open 24 hour a day. Being the market available
24 hours a day, this gives the trader to choose which time they would like to trade. It requires only
minimum beginning capital to start the Forex trade. Forex Trading has outstanding liquidity
as it nevercloses.
7. FUNCTIONALITY
Transfer purchasing power between countries. Obtain credit for international trade
transactions. Minimize exposure to the risks of exchange ratechanges.
8. USABILITY
The interface to make the trader access the system will beefficient.
9. PERFORMANCE:
The capability that the system performs on the whole will be efficient and reliable without any
erroroccurrence.
10. RELIABILITY
Thesystemshouldbeabletomaintainitsfunctionthroughoutthetransactionsinthefuture.
UMLDIAGRAMS:
S.NO UMLDIAGRAMS
1 Use Casediagram
2 Classdiagram
4 Sequencediagram
7 Activitydiagram
8 Componentdiagram
9 Deploymentdiagram
10 Packagediagram
GANTTCHART:
1. USECASEDIAGRAM:
DOCUMENTATIONOFUSECASEDIAGRAM:
 The actors in this use case diagram are customer, administrator,supplier,custom office and
database. The use cases are the activities that are represented in theellipse
 Customer logins the foreign trading system and perform the sourcing to select the
required commodities and places theorder.
 The Supplier checks for ordered commodities, after the commodities are ready Customer
pays theamount.
 The administrator provides the items along with thebill.
2. CLASSDIAGRAM:
Aclassisdrawnasrectangleboxwiththreecompartmentsorcomponentsseparatedbyhorizontal lines. The
top compartment holds the class name and middle compartment holds the attribute and bottom
compartment holds list ofoperations.
DOCUMENTATION OF CLASSDIAGRAM:
Customer: The customer class consist of attributes customer name, idaddress,mobile no,order of
product and operations as login ,display product details,view product details,view amount detailsand
productfeedback.
Admin: It consist of attributes admin name,address,mobile number,admin id,email id and operations
as admin login,verify document,verify product details,verify payment details and verify delivery
details.
Supplier:Itconsistofattributesname,address,mobilenumber,emailid,productsupply,amountand
Available product,specify amount,money transfer and supplierlogin.
SEQUENCEDIAGRAM:
A sequence diagram shows an interaction arranged in time sequence. It shows object participating in
interaction by their lifeline by the message they exchange arranged in time sequence. Vertical
dimension represent time and horizontal dimension representobject.
 The customer login the database and give his details and database store thedetails.
 Theadministratorgetthedetailsfromthedatabaseanddoverificationandtheforwardto
supplier.
 The supplier get details from the customer and perform verification and send report tothe
customer.
 The money exchanger used to validate the money and provide the cashpayment.
A collaboration diagram is similar to sequence diagram but the message in number format. In a
collaboration diagram sequence diagram is indicated by the numbering the message. A collaboration
diagram, also called a communication diagram or interaction diagram, A sophisticated modeling tool
caneasilyconvertacollaborationdiagramintoasequencediagramandtheviceversa.Acollaboration diagram
resembles a flowchart that portrays the roles, functionality and behavior of individual objects as well
as the overall operation of the system in realtime.
S
TATE CHARTDIAGRAM
Thestatechartdiagramcontainsthestatesintherectangleboxesandstartsinindicatedbythedotand finish is
indicated by dot encircled. The purpose of state chart diagram is to understand the algorithm in the
performingmethod.
DOCUMENTATION OF STATE CHARTDIAGRAM:
 The states of the foreign trading system are denoted in the state chartdiagram.
 This state chart diagram represents the process ofexport.
 Product details state represent the details of theproduct.
 Payment state represent the details of the mode ofpayment.
ACTIVITYDIAGRAM:
operation.Thepurposeistoprovideviewofcloseandwhatisgoingoninsideausecaseoramong
severalclasses.Anactivityisshownasroundedboxcontainingthenameofoperation.
DOCUMENTATION OF ACTIVITYDIAGRAM:
 The customer is used to create an account and fill theform.

 Theadministratorisusedtoverifytheaccountanddisplaymessagetothecustomer.
 Customer is used to make trade by checking the availability in the administrator, If the
availability is there, place theorder.
COMPONENTDIAGRAM:
dependency.Thecomponentdiagram'smainpurposeistoshowthestructuralrelationshipsbetween the
components of a system. It is represented by boxed figure. Dependencies are represented by
communicationassociation.
DOCUMENTATION OF COMPONENTDIAGRAM:
The main component in the component diagram is foreign trading system. The trader who come to do
the trading process and administrator who manages all the other processes is the subcomponents.
DEPLOYMENTDIAGRAM:

physical deployment of artifacts on deployment targets. Deployment diagrams show "the allocation of
dimentional box. Dependencies are represented by communication association. The basic element of a
deployment diagram is a node of twotypes
DEVICENODE:
Aphysicalcomputingresourcewithprocessingandmemoryservicetoexecutesoftware,suchasa typical
computer or a mobilephone.
EXECUTION ENVIRONMENTNODE:
DOCUMENTATION OF DEPLOYMENTDIAGRAM:
The device node is foreign trading system and execution environment node aresupplier,admin.
PACKAGE DIAGRAM:
A package diagram is represented as a folder shown as a large rectangle with a top attached to its
upper left corner. A package may contain both sub ordinate package and ordinary model elements. All
UML models and diagrams are organized into package. A package diagram in unified modeling
language that depicts the dependencies between the packages that make up a model. A Package
Diagram (PD) shows a grouping of elements in the OO model, and is a 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).
 User interfacelayer
 Domainlayer
 Technical serviceslayer
userinterface
domain
web login
payment
database
DOCUMENTATION OF PACKAGEDIAGRAM:
 Thethreelayerinthepassportautomationsystemareuserinterfacelayer,domainlayer,
technical servicelayer.
 Theuserinterfacelayer-representstheuserinterfacecomponentssuchasweb,applicant,
passportadministrator,police,andregionaladministrator.
 Thedomainlayer-hasmajoractionssuchasgiveandgetdetails,verificationandissues.
 Technical service layer- authenticated user only can access the technicalservices.
JAVACODING:
Customer.java
{
private intcustomerName;
private int customerId;
private intcustomerNo;
public salesDepartment theSalesDepartment;
public individualCustomertheIndividualCustomer;
public corporateCustomer theCorporateCustomer;
public managertheManager;
publiccustomer()
{
}
public voidregister()
{
}
public voidlogin()
{
}
}
Individualcustomer.java
public classindividualCustomer
{
private int customerName;
private int customerNo;
publicindividualCustomer()
{
}
{
}
}
Corporatecustomer.java
public classcorporateCustomer
{
private int customerName;
publiccorporateCustomer()
{
}
{
}
}
Salesdepartment.java
public classsalesDepartment
{
private int salesNo;
private int salesItem;
publicsalesDepartment()
{
}
public voidorder()
{
}
public voidbill()
{
}
}
Manager.java
public classmanager
{
private intmonitor;
publicmanager()
{
public voidhandle()
{
}
public voidverify()
{
}
}
RESULT:
EXPERIMENT NO:
DATE CONFERENCE MANAGEMENT SYSTEM
AIM:
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.
SOFTWARE REQUI REMENT SPECIFICATION:
S.NO SPECIFICATION
1 INTRODUCTION
2 OBJECTIVE
3 OVERVIEW
4 GLOSSARY
5 PURPOSE
6 SCOPE
7 FUNCTIONALITY
8 USABILITY
9 PERFORMANCE
10 RELIABILITY
11 FUNCTIONAL REQUIREMENTS
INTRODUCTION:
This software specification document consist full set of features

and function for online conference management system. In this we give specification about
the system requirements that are apart from the functionality of the system to perform the
candidate paper valuation. It tells the usability, reliability defined in use case specification.
OBJ ECTIVE:
The main objective of Conference Management System is to

accomplish paper submission online, update the presentation details and confirm registration.
Conference management system provides online help to the users all over the world.
OVERVIEW:
The overview of the project is to design a process which ease the work
for the candidate as well as the reviewer. Candidate can easily submit the paper and go for
registration.
GLOSSARY:
TERMS DESCRIPTION
The candidate can login and submit the paper to the
CANDIDATE reviewer. After getting paper then registration
process will be carried out.
Reviewer will review the paper and sending
REVIEWER
acknowledgement to the candidates.
Database is used to verify login and store details of
DATABASE
selected candidates.
SOFTWARE This software specification documents full set of
REQUIREMENTS features and function for conference management
SPECIFICATION system.
PURPOSE:
The purpose of the conference management system is that the system can
easily review the process. The main process in this document is the submission of paper by
the candidate, reviewing process by the reviewer and sending of acknowledgement to the
candidates whose paper is selected.
SCOPE:
The scope of this conference management process is to select the best candidate
from the list of candidates based on their performance in the process.
FUNCTIONALITY:
The main functionality of conference system is to select the candidate for the
presentation in conference.
USABILITY:
The user interface to make the process should be effective that is the system will
help the candidates to register easily. The system should be user friendly.
PERFORMANCE:
It describes the capability of the system to perform the

conference process of the candidate without any error and performing it
efficiently.
RELIABILITY:
The conference system should be able to serve the applicant with correct
information and day-to-day update of information.
FUNCTIONAL REQUI REMENTS:
Functional requirements are those that refer to the functionality of the

System that is the services that are provided to the candidate who register for the
conference.
UML DIAGRAMS:
The following UML diagrams describe the process involved in the conference management
system.
•Use case diagram
•Class diagram
•Sequence diagram
•Collaboration diagram
•State chart diagram
•Activity diagram
•Component diagram
•Deployment diagram
•Package diagram
USE CASE DIAGRAM
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 candidate, reviewer and database. The use
cases are the activities performed by actors.
Candidate - Logins the conference system and submits the paper then do the
registration process.
Reviewer –Review the paper, select best candidate and send acknowledgement to
them.
Databases - verify the login and register details and selected candidate details are
stored in it.
Login - Candidate enter their username and password to login to the conference
system.
Paper sub mission–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.
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 have 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.
SEQUENCE DIAGRAM
A sequence diagram in Unified Modelling Language (UML) is a kind of interaction diagram

Message Sequence Chart. There are two dimensions.
1. Vertical dimension-represent time.
2. Horizontal dimension-represent different objects.
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 submits the paper.
 The reviewer reviews the paper and sends acknowledgement to thecandidates.
 The candidate submits revised and camera ready paper.
 This candidate will register their details.
COLLABRATION DIAGRAM
A collaboration diagram, also called a communication diagram or interaction diagram. A

sophisticated modelling tool can easily convert a collaboration diagram into a sequence
roles, functionality and behaviour of individual objects as well as the overall operation of the
system in real time.
DOCUMENTATION OF COLLABRATION DIAGRAM
This collaboration diagram is to show how the applicant login in the conference system.
Here the sequence is numbered according to the flow of execution . It is also to show the
submitting paper process of the candidate for the conference . The flow of execution of this
selection process is represented using the numbers.
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. A final state is
represented as circle surrounding a small dot
DOCUMENTATION OF STATE CHART DIAGRAM
This state diagram describes the behavior of the system.

•First state is login where the candidate login to the conference system.
•The next state is submitting the paper.
•Then review the paper if it is selected the process will continue..
•The candidate should submit revised and camera ready paper.
•Then registration process will be carried out.
ACTIVITY DIAGRAM

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 an 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 candidate login to the database.
•Then the candidate should submit the paper.
•If it is selected the acknowledgement will send to the candidate.
•After submitting revised paper the registration process will be done.
COMPONENT DIAGRAM
The component diagram's main purpose is to show the structural relationships between the
components of a system. It is represented by boxed figure. Dependencies are represented by
communication association.
DOCUMENTATION OF COMPONENT DIAGRAM
The main component in this component diagram is conference management system. And
submit the paper, review the paper and registration.
DEPLOYMENT DIAGRAM
dimensional box. Dependencies are represented by communication association
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
reviews paper, database will store all details which are the some of the main activities
performed in the system.
PACK AGE DIAGRAM
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 inter face layer - software objects representing domain concepts that fulfil
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 objects and subsystems that provide
supporting technical services, such as interfacing with a database or error logging.
DOCUMENTATION OF PACK AGE DIAGRAM
The three layers in the online recruitment system are

•The User inter face layer - consists of the web and login. This layer describes how
the candidate login.
•The Domain layer –shows the activities that are performed in the conference
management system. The activities are paper submission, review paper, registration.
•The Technical service layer - the verification details and the selected candidate details
will stored into the database.
SOURCE CODE
CANDIDATE
public class candidate
{
private int name;
private int paper title;
public reviewer the reviewer;
public candidate()
{
}
public void opname()
{
}
public void submit _ paper()
{
}
public void registration()
{
}}
REVIEWER
public class reviewer

{
private int name;
private int reviewer id;
public candidate the candidate;
public database the database;
public reviewer()
{
}
public void paper review()
{
}
public void confirmation details()
{
}
}
DATABASE
public class database

{
private int username;
private int password;
public candidate the candidate;
public database()
{
}
public void reviewer Accessibility()
{
}
public void code_ Verification()
{
}
}
RESULT:
EXPERIMENT NO:
BUSINESS PROCESS OUTSOURCING
DATE MANAGEMENT SYSTEM
AIM
PROBLEMSTATEMENT
1. Generally outsourcing can be defined as an organization entering into a contract with

another organization to operate and managed one or more of its businessprocesses.
2. 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 salessuccessful.
3. The agent login to the website and enters the username and password .It checks for
authorization.
4. If the username and password is correct, it allows the agent to get the details of the
customer from thedatabase.
5. Now the agent makes the call to the customer and pitches about theproduct.
6. If the customer is satisfied, agent sells the product else disconnects thecall.
7. Agent proceeds with thecall.

SPECIFICATION
1.0 Introduction
1.1 Purpose
1.2 Scope
1.4 Reference
1.7 Overview
2.4 Systemfunction
2.6 Constraints
1.1 INTRODUCTION
BPO is typically categorized into back office outsourcing-which includes internal business
functions such as human resources or finance and accounting, and front office outsourcing-
which includes customer related services such as contact center services. BPO that is
contracted outside a company’s country is called offshore outsourcing.BPO that is contracted
to a company’s neighboring country is called nearshore outsourcing.Given the proximityof
BPO to the information technology industry,it is categorized as an information technology
enabled service or ITES.Knowledge process outsourcing(KPO) and legal process
outsourcing(LPO) are some of the sub-segments of business process outsourcing industry.In
the following SRS the front office outsourcing is explained indetail.
1.2 PURPOSE
The purpose of this system is to provide information about the customer need from inside and
outside world.With the reduction in communication costs and improved bandwidths and
associated infrastructure,BPO as a segment is witnessingmassivegrowth. One of the key
challenges that BPO companies is that to provide data entry/data validation services is an
efficient and effective way of getting the source documents from different customers and
accurately route the same of different operators forprocessing.
1.3 SCOPE
Developing a good BPO management system.BPO is a way in which it helps to increase

company’s flexibility.As part of BPO,documents need to be managed between the
outsourcing company and the offshore company.Multiple clients need to be managed by the
BPO company.
1. Process agent-Finds the login and searches for thedatabase.

2. Database-It is used to give the phone number and customerdetails.
3. Customer-They respond to he agentscall.
1.8 OVERVIEW
This system deals with the front office outsourcing,it is designed to understandable to the
customers.it lists the set of all constrains and functions performed by the customer.The main
function of the this system is the customersatisfaction
TERM DESCRIPTION
Customer Person who is seekinginformation.

Agent People who receives thequery.
Database Collection of all information monitored by the
BPOsystem.
Reader Anyone visiting the site to read about BPO
managementsystem.
2.2 PRODUCT PERSPECTIVE
Business Process Outsourcing (BPO) provides a flexible, strategic way to do business. At its
most basic, it’s simply hiring another company to handle certain aspects and processes of
your business. Today, organizations outsource human resources administration, call center
services, accounting, and diverse insurance and technologyprocesses.
database in the server.
2.5SYSTEMFUNCTIONS
The BPO system is embedded in a larger system involving several management systems.we
describe this environment as communication system between customer and agent through
voicechat.
1. The user interface to make the bpo management to beefficient
2. It is the capability about which it can perform function for many user efficiently at the
same time without any erroroccurance
2.7 CONSTRAINTS
Functional requirements are those refer to the functionality of the system.i.e. what services it
will provide to the user. Non functional (supplementary) requirements pertain to other
information needed to produce the system correctly and detailedseparately.
1.Process agent and customer must have basic knowledge of computers and English
Language.
2.The database may be required to scan the documents andsend.
UMLDIAGRAMS
S.NO UMLDIAGRAMS
1 Use Case diagram
2 Class diagram
3 Interaction diagram
4 Sequence diagram
5 Collaboration diagram
7 Activity diagram
8 Componentdiagram
9 Deploymentdiagram
10 Package diagram
GANTTCHART:
USECASEDIAGRAM: 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
toaparticulargoal.Itisrepresentedusingellipse.
The actors in this use case diagram are Process agent,Customer and Database. The usecases
are the activities performed byactors.
USECASE
Use case is a collection of failure and related success scenarios that describe the actor using a
system to support agoal.
ACTOR
The Actor is a user playing a role with respect to the system. A single actor may perform
many use cases. Similarly a user case can have many users performing theoperation.
PROCESSAGENT
The ultimate Goal of the process agent is to make sale. The operation performed by him/her
ishe/shewillfirstcallthecustomerthenpitchesthereproductforsale.Ifthecustomeris
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 theagent.
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 thecall.
login <<extend>>
available
browsecatalog
<<extend>>
customer notavailable
selectitems
call customercare
<<extend>>
receivecall
<<extend>>
search library
dealer
response
returncall
<<include>>
pay bycredit
payment payonline
<<include>>
pay bydebit
CLASSDIAGRAM

horizontal lines. The top compartment holds the class name and middle compartment holds
the attribute and bottom compartment holds list of operations. 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 have
the class name,middle comparment the attributes and the bottom compartment with
operations.
This class diagram has three classes process agent, customer anddatabase.
• Agent – is the class name. Its attributes are username, password, name, phoneno and
address. The operations performed by the agent class are login, giving details to customer and
selling theproduct.
• Customer – is the class name. Its attributes are name, phoneno, address . The operations
performed are attending the call,asks about theproduct.
• Database – is the class name. The operations performed are storing customer details,
verifying login and updating the customerdetails.
SEQUENCEDIAGRAM
A sequence diagram in Unified Modeling Language (UML) is a kind of interaction diagram
1.Veritcal dimension-representtime.
2.Horizontal dimension-represent differentobjects
The single use case in the BPO management system is taken and sequence of operations
followed in theusecase.
The BPO has the following sequence of process:
1.Agent fetches the data from thedatabase
2.database provides the details of the customer to agent and agent dials to the customer.
3.Customer responds to the agent and agent pitches his/herproduct.
4.If necessary customer buys else discards.
5.Agent updates the call history
6.proceeds with the anothercall.
A collaboration diagram, also called a communication diagram or interaction diagram,. A
roles, functionality and behavior of individual objects as well as the overall operation of the
system in realtime.
8: returndetails
system dealer
7:search
5: call customercare
6: receivecalls
1:login 10:order
2:password 11: 12:update
3: browsecatalog
4: selectitems
9: returncall
13:bill
database
customer
DOCUMENTATION OF COLLABRATIONDIAGRAM
This diagram is similar to sequence diagram.But the difference is the various operations
involved in the particular use case will be numbered.In this diagram,the sequence of stepis
• Fetches the customer details from thedatabase.
• Database provides the customerdetails.
• Agent dials thecustomer.
• Customer responds to the agentcall.
The agent pitches about his/her product to the customer.
If necessary customer buys else disconnects the call
The agent updates the callhistory.
The agent proceeds with the anothercall.
STATE CHARTDIAGRAM
It is also called as State diagram .The purpose of state diagram is to understand the algorithm
in problemstatement.
A state is represented as a rounded box, Which may contain one or more compartments.
Compartments are alloptional.
Types ofcompartment:
*Name compartment- holds name of thestate
*Internal transition- holds internal actions or activities.
State chart is shown as the small dot . Final state is shown as circle surrounding a smalldot.

The various states are login,fetches data from database, calls the customer, pitches the
product, sales the product, proceeds with anothercall.
The state chart diagram describes the behavior of thesystem.
1. The main purpose of the system is to sale the product to thecustomer.
2. After login, the agent gets details of customer fromdatabase.
3. the agent calls thecustomer.
4. The agent pitches about theproduct.
5. If customer interested , the agent buys the product elsediscards.
6. Agent proceeds with the anothercall.
ACTIVITYDIAGRAM
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 an rounded box containing the name of theoperation.
Activity Diagram is shows the flow of the activity which is carried out in the BPO
management. It is more or less equal to the flow chart which we use in our programming
languages. It consists of states such as login , fetches the data, calls the customer, pitches the
product, makes the sale andetc……
Initial node: The filled in circle is the starting point of the diagram. An initial node isn’t
required although it does make it significantly easier to read thediagram.
• Activity final node. The filled circle with a border is the ending point. An activity diagram
can have zero or more activity finalnodes.
• Activity. The rounded rectangles represent activities that occur. An activity may be
physical, such as Inspect Forms, or electronic, such as display the BPOdetails.
• Flow/edge. The arrows on the diagram. Although there is a subtle difference between flows
and edges I have never seen a practical purpose for the difference although I have no doubt
one exists. I’ll use the termflow.
COMPONENTDIAGRAM
The component diagram's main purpose is to show the structural relationships between the
components of a systems. It is represented by boxed figure. Dependencies are represented by
communication assosiation.
The main component in this component diagram is BPO management systems. And the agent
calls customer, pitches about his product and makes the sale are the main component comes
under the componentdiagram.
DEPLOYMENTDIAGRAM
DEVICENODE–
A physical computing resource with processing and memory service to execute software,
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 thesystem.
PACKAGEDIAGRAM
A package diagram is represented as a folder shown as a large rectangle with a top attached
to its upper left corner. A package may contain both sub ordinate package and ordinary model
elements. All uml models and diagrams are organized into package. A package diagram in
unified modeling language that depicts the dependencies between the packages that make up
a model. A Package Diagram (PD) shows a grouping of elements in the OO model, and is a
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).
o Domainlayer
The three layers in the BPO management systemsare
• The User interface layer - consists of the web and login. This layer decribes how
The agent logs on to the website and gets the customerdetails.
The Domain layer – shows the activities that are performed in the BPO rmanagement
system.The agent makes the call and he pitches about the product to customer and makes
sale.Finally agent aborts the call and proceeds with anothercall.
• The Technical service layer –the customer details are shown in the database.If the
customer buys product it makes the saleentry.
JAVACODING:
Customer.java
{
private int name;
private intitems;
public database theDatabase;
publiccustomer()
{
}
public voidorder()
{
}
public voiditems()
{
}
}
dealer.java
public classdealer
{
private intname;
private int productdetails;
private intavailablity;
public database theDatabase;
public customer theCustomer;
publicdealer()
{
}
public voidsubmitdetails()
{
}
public voidcheckstatus()
{
}
public voidorder()
{
}
}
database.java
public classdatabase
{
private int noofitems;
private int bill;
public database()
{
}
public voidbill()
{
}
public voidupdate()
{
}
}
register.java
public classregister
{
private int username;
private intpassword;
public customer theCustomer;
publicregister()
{
}
public void login()

{
}
public void verify()
{
}
public voidupdate()
{
}
}
RESULT
EXPERIMENT NO:
DATE LIBRARY MANAGEMENT SYSTEM
AIM
PROBLEMSTATEMENT
Book bank system is where the books can be collected every semester and must be returned at
the end of semester. The system must have option for new members to enroll for membership by
paying deposit. A provision for getting six or seven books per semester. Membership can be renewed
by using the register number. The deposit must be refunded on termination of membership. A database
must be maintained to guide the issuer to track the details of students. Search option must be provided
so that the member can search for the availability of a particularbook.
S.NO SOFTWARE REQUIREMENTSPECIFICATION
1 Introduction
1.1 Purpose
1.2 Productscope
1.3 Document conventions
1.4 References
2 Overall Description
2.1 Product Perspective
2.2 Product Functions
2.4 External Interface
3 Hardware Interface
3.1 Software Interface
3.2 System Features
4 RequestingBooks
4.1 Stimulus/response Sequence
4.1.1 FunctionalRequirements
4.1.2 Other non-functional requirements
4.1.3 PerformanceRequirements
4.1.4 Safety Requirements
4.1.5 SecurityRequirements
1. INTRODUCTION
The book bank is a set up that lends books for all its members which they can return at the end
of each semester. It has a huge collection of books and has to keep track of all its members’ details
such as requests, dues and penalties and thebooks.
1.1 PURPOSE
The purpose of this document is to present a detailed description of the Book Bank System. It
will explain the purpose and features of the system, the interfaces of the system, what the system will
do, the constraints under which it must operate and how the system will react to externalstimuli.
1.2 SCOPE
The book bank holds an online interface with its members for maintaining all kinds of
transaction details. Each member is provided with a unique user id at the time of registering as a
member.
1.3 DOCUMENTCONVENTIONS
· Director: The ultimate authority in the staff hierarchy of the bookbank
· Member: Any person who registers with the bookbank
· HTML-Hyper Text Markup Language used to create webpage.
1.4 REFERENCES
www.reachbookbank.comw
ww.bookworldlibrary.com
2. OVERALLDESCRIPTION
This project is a self-contained one for enabling a book bank organization to be connected with
its students, through this system, the students can check for availability of books, makes requests,etc.
2.2 PRODUCTFUNCTIONS
This system functions with a database at the back end, for keeping track of its member’s dues
and payments, and also its available resources. Every student who is a member needs only a web
browser to connect to thissystem.
2.3 TOOLS TO BEUSED

Visual basic and MicrosoftAccess
3. EXTERNALINTERFACES
3.1 HARDWAREINTERFACES
The system should have good hardware support. The processor should have high speed and
must be of highefficiency.
The system uses ODBC drive to connect and control thedatabase.
4. SYSTEMFEATURES
4.1 REQUESTINGBOOKS
4.1.1 SYSTEM DESCRIPTION &PRIORITY
Allows a student, who becomes a member to login using a unique id issued at the time of
registering as a member, and after logging in, the member can browse through available books and
make requests accordingly. The books will be issued provided there is no due, regarding returning of
previousbooks.
4.1.2 STIMULUS/RESPONSESEQUENCE
Whenever the student wishes to get books, he/she checks for the availability by logging in.
When the request is made, the director of the book bank decides on granting the request of book(s)
after checking the member details for due in returning previousbooks.
4.1.3 FUNCTIONALREQUIREMENTS
The member should be authenticated by means of unique login id and password. The
availability of books requested must be prompted to the user through e-mail or smsnotifications.
5. OTHER NON-FUNCTIONALREQUIREMENTS
5.1 PERFORMANCEREQUIREMENTS
The web interface should be able to support multiple users trying to log insimultaneously.
5.2 SAFETYREQUIREMENTS
The student details should be made available in the database and must be updated every time a
book is issued or returned or some kind of payment takes place to preventerrors.
5.3 SECURITYREQUIREMENTS
The member can only access certain details from the database. He/she should not be able to
modify the database nor has any of its information corrupted. Only the DBA must be bestowedwith
the privileges of handling any kind ofmodifications.
USECASEDIAGRAM
S.NO UMLDIAGRAMS
1 Use Casediagram
2 Classdiagram
4 Sequencediagram
7 Activitydiagram
8 Componentdiagram
9 Deploymentdiagram
10 Packagediagram
GANTTCHART:
Task Dec Jan Feb March April

w w w w w w w w w w w w w w w w w w w w
1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4
Requirementa
nalysis
Design
Coding
Testing
Maintanence
USECASEDIAGRAM
usingellipse.
Actor is any external entity that makes use of the system beingmodeled.

The actors in this use case diagram are member and database. The use cases are theactivities
performed byactors.
• The member will register himself in the bookbank.
• After registration he will select the year to which hebelongs
• After selecting he will selectbooks
• Database will verify the status ofbook
CLASSDIAGRAM
The class diagram is the main building block of object oriented modelling. Itis used both for
general conceptual modelling of the systematics of the application, and for detailed modelling
translating the models into programming code. Class diagrams can also be used for
datamodeling.The classes in a class diagram represent both the main objects, interactions in the
application and the classes to be programmed. In the diagram, classes are represented with boxes
which contain threeparts:
 The top part contains the name of the class. It is printed in bold and centered, and thefirst
letter iscapitalized.
 The middle part contains the attributes of the class. They are left-aligned and the first letteris
lowercase.
 The bottom part contains the methods the class can execute. They are also left-aligned and
the first letter islowercase.
This class diagram has 8classes:
• Member details class- is the class name. Its attributes are name, father name, date ofbirth,
address, phone number, member id, college, degree, course and semester. Its operations are
registration, authentication, and yearselection.
• Administrator- is the class name. Its attributes are name, address, phone, mail id.Its
operations are authentication, verification and issuebooks.
• Year-is the class name. Its attribute is year selection. Its operations are 1st year,2nd year,3rd
year,4thyear.
• Issue for 1st year-is the class name. Its attributes are member code, member name, bookcode,
Issue for 2nd year-is the class name. Its attributes are member code, member name, bookcode,
• Issue for 3rd year-is the class name. Its attributes are member code, member name, bookcode,
SEQUENCEDIAGRAM
A Sequence diagram is an interaction diagram that shows how processes operate
with one another and what is their order. It is a construct of a Message Sequence Chart. A
sequence diagram shows object interactions arranged in time sequence. It depicts the objectsand
classes involved in the scenario and the sequence of messages exchanged between the objects
needed
The sequence diagram describes the sequence of steps toshow
• He will select theyear
• He select the books given and the database will update the status ofbook.
• Then administrator will log in and verify the status ofbooks.
• If the book is available he will issue thebook.

format. In a collaboration diagram sequence diagram is indicated by the numbering the message.
A collaboration diagram, also called a communication diagram or interaction diagram, A
realtime.
5: receives thebook
1: request forbook
6: returns the book on or before the due date
user admin
4: issues the book if it isavailable
3: respond with status of thebook

2: check for availability
7: updates the bookdb
database
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 ofexecution.
STATE CHARTDIAGRAM
The state chart diagram contains the states in the rectangle boxes and starts in indicated by the
dot and finish is indicated by dot encircled. The purpose of state chart diagram is to understand
the algorithm in the performingmethod.

• In the first state the member registers himself in bookbank
• After that he will select the year in nextstate.
• In the next state he will select thebooks.
• In the next state database will update the status of book.
• In the next state administrator will login.
ACTIVITYDIAGRAM
activity diagrams are intended to model both computational and organisational processes (i.e.
workflows). Activity diagrams show the overall flow of control. Activity diagrams are
constructed from a limited number of shapes, connected with arrows.The most importantshape
types:
This activity diagram flow of stepwise activities performed in book bank managementsystem.
• After that he will select theyear.
• He will select thebooks.
• Database will update the status ofbook.
• Database will update thedetails
• Then the administrator will log in to hisaccount.
• After authentication he will verify the availability ofbook.
• If available he will issue thebook.
COMPONENTDIAGRAM
A component is something required to execute a stereotype function. Examples of stereotypes in

components include executables, documents, database tables, files, and library files.Components
are wired together component with the provided interface of anothercomponent.
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 forfourth
year are components comes under the maincomponent
DEPLOYMENTDIAGRAM
DEVICENODE–
A physical computing resource with processing and memory service to execute software, suchas
a typical computer or a mobilephone.
service to host and execute other executable softwareelement.
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 forsecond
year issue for third year and issue for fourth year are some activities performed in thissystem.
PACKAGEDIAGRAM
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).
• User interfacelayer
• Domainlayer
• Technical serviceslayer
• The User interface layer - consists of the web and member details. This layer describeshow
the member goes to book bank and registershimself..
• The Domain layer – shows the activities that are performed in the book bankmanagement
system. The activities are register and bookissues..
• The Technical service layer - the member details and verification details are stored inthe
database.
JAVACODING
Database.java
public classbookDatabase
private charbookName;
private charauthorName;
privateint edition;
publicbookDatabase()
public voidtransaction()
public voidupdationOfBookDetails()
user.java
public classuser
privateintphoneNumber;
privateintloginId;
privateint password;
public admintheAdmin;
publicbookDatabasetheBookDatabase;
publicuser()
{
public voidreturnsBook()
public voidborrowsBook()
{ }}
admin.java
public classadmin
privateintphoneNumber;
privateintloginId;
privateintpassword;
publicbookDatabasetheBookDatabase;
publicadmin()
public voidprovideLoginId()
{
}
RESULT
EXPERIMENT NO:
DATE STUDENT INFORMATION SYSTEM
AIM:
PROBLEMANALYSIS AND PROJECT PLANNING:
A Student information system (SIS) is a software application for educational

establishments to manage student data. Student information systems provide capabilities
for entering student test and other assessment scores, building student schedules, tracking
student attendance, and managing many other student-related data needs in a school,
college oruniversity.
PROBLEMSTATEMENT:
The student must register by entering the name and password to login the form.
The admin select the particular student to view the details about that student and
maintaining the student details. This process of student information system are described
sequentially through followingsteps,
 The student registers thesystem
 The admin login to the student informationsystem.
 He/she search for the list ofstudents.
 Then select the particularstudent.
 Then view the details of thatstudent.
 After displaying the student details thenlogout.

UMLDIAGRAMS:
The following UML diagrams describe the process involved in the online recruitment
system
S.NO UMLDIAGRAMS
1 Use Casediagram
2 Classdiagram
4 Sequencediagram
7 Activitydiagram
8 Componentdiagram
9 Deploymentdiagram
10 Packagediagram
GANTTCHART:
USE CASEDIAGRAM:
systemrequirements.Theusecaseismadeupofasetofpossiblesequencesofinteractions
betweensystemsandusersinaparticularenvironmentandrelatedtoaparticulargoal.Itis
represented using ellipse. Actor is any external entity that makes use of the system being
modelled. Its represented using stickfigure
The actors in this use case diagram are Admin, Student, Database. The use cases are
the activities performed byactors.
a. Admin register login, and store the student records details indatabase.
b. Student Register from the Student Loginprocess.
c. Then the database is searched for details andverified.
d. Database stores the details and returnsacknowledgement
CLASSDIAGRAM:
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 s represented using a rectangle
with three compartments. Top compartment have the class name, middle compartment the
attributes and the bottom compartment withoperations.
ThisclassdiagramhasthreeclassesLogin,Studentdetailsand Updatedetailsindatabase.
a. Students – is the class name. Its attributes are name, Address, DOB, Gender,
College, Subjects, Semester, Year, Degree, Branch. The operations Performed in the
students class, Store database andUpdate.
b. Administration–istheclassname.ItsattributesareLogin,Passwordanddatabase. The
operations performed are Student Details store in database and send acknowledgement.
c. Database – is the class name. The operations performed are storing Search and
storing thevalues.
SEQUENCEDIAGRAM:
AsequencediagraminUnifiedModelingLanguage(UML)isakindofinteractiondiagram that
shows how processes operate with one another and in what order. It is a construct of a
1. Veritcal dimension-representtime.
2. Horizontal dimension-represent differentobjects.
ForValidity:
Admin/Student Validation Database
1:Requestforvalidity()
2:Checkforvalidity()
3:Validate()
4:Successfulvalidate()
ForAdministrator:
ForStudent:
The sequence diagram describes the sequence of steps to show
a.The Admin login and registering forAdd Student Details.
b. The verification done by the interface and sendingacknowledgement for

registration.
c. Searching the database with login and displaying it formaintenance.
COLLABRATIONDIAGRAM:
Acollaborationdiagram,alsocalledacommunicationdiagramorinteractiondiagram,. A
diagram and the vice. 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 realtime
ForValidity:
Database
3:Validate()
2:Checkforvalidity()
Validation
1:Requestforvalidity()
4:Successfulvalidate()
Admin/Student
ForAdministrator:
Database
3 : Validuser()
6 :Add()
10 :Update()
7 :Successful() 2 : Check forvalidity()

11 :Successful()
Login
ReqAddStudent
ReqUpdateStudent
1 : Enter Credentials forlogin()
8 : Successfullyadded()
4 : Successfull ogin()
12 : SuccessfullyUpdated()
9 : Entercredentials for update studentrecord()
5:Enterdetailsforaddingastudent()
Admin
ForStudent:
Database
3 :Valid()
6 :Request() 2:CheckforValidity()
7:SetDetails1(0):Request()
11:SetDetails() Login
ReqViewProfile
8:Getthedetails() ReqViewDetails
4 : Validlogin()
1:Entercredentialsforlogin()
Object1
5:Requestforviewprofile()
9:RequestforviewDetails()
12:GettheDetails()
Student
DOCUMENTATION OF COLLABRATIONDIAGRAM
The collaboration diagram is to show how the Student registers and the authorities
maintains the details of the registered students in the Information system. Here the
sequence is numbered according to the flow ofexecution.
STATE CHARTDIAGRAM:
DOCUMENTATION OF THE STATE CHARTDIAGRAM:
The various states are the login, lists of student, selects a student, display the information
about the student,logout.
The state chart diagram describes the behaviour of the system. The main purpose of the
system
is to maintain a student details. For that the admin Login to the student information
system.
He/she selects a particular student from the list of available student. The admin has to
view the details of the particular student by clicking the respective button. The admin
views the Details then finally he is logout from thesystem.
ACTIVITYDIAGRAM:
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 an rounded box containing the name of the operation.
DOCUMENTATION OFACTIVITY DIAGRAM
This activity diagram flow of stepwise activities performed in recruitmentsystem.
a. The student details are Add and stored indatabase.
b. Select the course from the given Course bystudent.
c. Search Profile and Result with login and if data present in the database.
d. The searched data is displayed if available and then LogOut.
COMPONENTDIAGRAM:
Thecomponentdiagram'smainpurposeistoshowthestructuralrelationshipsbetweenthe
components of a system. It is represented by boxed figure. Dependencies are represented
by communicationassociation.
The main component in this component diagram is Student Information system. And
register, User and Manage, Request details are the components comes under the main
component.
DEPLOYMENTDIAGRAM:
deployment of artifacts on deployment targets. Deployment Diagrams show "the
association.
The processor in this deployment diagram is the Student Information System which is the
mainpartandtheStudentaretheAdmin,verifyandsearchwhicharethesomeofthemain activities
performed in thesystem.
PACKAGEDIAGRAM:

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).
o Domainlayer
a. The user interface layer- represents the user interface components such as system,
student.
b. The domain layer- has major actions such as course and paymentdetails.
c. Technical service layer- authenticated user only can access the technicalservices.
JavaCoding:
import java.awt.*;
import java.awt.event.*;
import javax.swing.*;
importjava.sql.*;
public class jdbcframe1 extends JFrame implementsActionListener
{
public JLabel l1,l2,l3,l4,l5;
public JTextFieldt1,t2,t3,t4,t5;
public JButtonb1;
Containerc;
publicjdbcframe1()
{
setSize(180,400);
setTitle("STUDENTDETAILS");
setVisible(true);
setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
c=getContentPane();
c.setLayout(new FlowLayout());
l1=new JLabel("Regno");
c.add(l1);
t1=newJTextField(10);
c.add(t1);
l2=new JLabel("Name");
c.add(l2);
c.add(t2);
l3=new JLabel("Dept");
c.add(l3);
c.add(t3);
l4=new JLabel("Course");
c.add(l4);
c.add(t4);
l5=new JLabel("Contact");
c.add(l5);
c.add(t5);
b1=new JButton("SAVE");
c.add(b1);
b1.addActionListener(this);
}
public void actionPerformed(ActionEventae)
{
if(ae.getSource()==b1)
{
try
{
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connectioncon=DriverManager.getConnection("jdbc:odbc:student");
Statementst=con.createStatement();
PreparedStatementps,ps1;
ps1=con.prepaeStatement("select * from student whereregno="+t1.getText());
ps=con.prepareStatement("insertinto
student(regno,name,dept,course,contact)values(?,?,?,?,?)");
ps.setString(1,t1.getText());
ps.executeUpdate();
JOptionPane.showMessageDialog(null,"RECORDSAVED");
}
catch(SQLExceptionsq)
{
System.out.println(sq);
System.out.println("\nHai this place is erroroccur");
}
catch(Exceptione)
{
System.out.println(e);
}
}
}
public static void main(Stringargs[])
{
jdbcframe1 f=newjdbcframe1();
}
}
RESUL:

Updated Casetools Record PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Updated Casetools Record PDF

Încărcat de

Drepturi de autor:

Formate disponibile

TABLE OF CONTENTS

S.NO DATE NAME OF THE EXPERIMENT PG.NO MARK SIGNATURE

1 Study Of UML Diagrams

2 Passport Automation System

3 Book Bank System

5 Stock Maintenance System

6 Online Course Registration System

Software Personnel Management

Credit Card Processing System

E-Book Management System

Foreign Trading System

Conference Management System

14 BPO Management System

15 Library Management System

16 Students Information System

DATE STUDY OF UML DIAGRAMS

The Unified Modelling Language is a standard visual modelling language intended to

The Unified Modelling Language is a language for specifying, constructing,

 Providing a high-level view of what the systemdoes

Use case diagrams are helpful in threeareas.

Sequence diagrams document the interactions between classes to achieve a result,

Messages, modelled as horizontal arrows between Activations, indicate the communications

Component diagrams fall under the category of an implementation diagram, a kind of

A component represents a software entity in asystem.

The top part contains the name of theclass.

The middle part contains the attributes of theclass.

The bottom part contains the methods/function the class canexecute.

6. PACKAGES AND OBJECTDIAGRAMS

8. STATE CHART DIAGRAMS

A deployment diagram the Unified Modelling Language models the physical

Logical Architecture and UML PackageDiagrams

OOS has threelayers

DATE PASSPORT AUTOMATION SYSTEM

SNO SOFTWARE REQUIREMENTS

1.4 DEFINITIONS, ACRONYMS AND THEABBREVIATIONS

1.5 REFERENCES IEEE Software Requirement Specificationformat.

1.6 TECHNOLOGIES TO BE USED • Microsoft Visual Basic6.0

1.7 TOOLS TO BE USED • StarUML tool (for developing UMLPatterns)

1. Secure Registration of information by theApplicants.

1. The applicants require a computer to submit theirinformation.

2.8 ASSUMPTIONS ANDDEPENDENCIES

A class is drawn as rectangle box with three compartments or components separated

a. APPLICANT-The applicant has attribute such as name and password and

A sequence diagram shows an interaction arranged in timesequence,

event OnCreated / Login

event Oncorrect entry/ Can modify before submit

event ontime/renewal event onuptodate/issue

DOCUMENTATION OF STATE CHARTDIAGRAM

a. The components in the passport automation system are passport automation

b. Applicant ,passport administrator, regional administrator and police are

A package diagram is represented as a folder shown as a large rectangle with a top

DATE BOOK BANK SYSTEM

2.3 TOOLS TO BEUSED

Task Dec Jan Feb March April

existing user signup

updates the bookdetails

DOCUMENTATION OF USE CASEDIAGRAM

user admin database

respond with status of the book

issues the book if it is available

returns the book on or before the duedate

updates the bookdb

4: issues the book if it isavailable