DMI College of Engineering

(Affiliated to Anna University, Chennai-600 025)

Palanchur, Chennai-602 123.

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

CS8582 OBJECT ORIENTED ANALYSIS AND DESIGN LABORATORY

V SEMESTER/ III YEAR

NOV/DEC-2021

LIST OF EXPERIMENTS
1
S.NO. TITLE

1. INTRODUCTION

2. PASSPORT AUTOMATION SYSTEM

3. BOOK BANK

4. EXAM REGISTRATION SYSTEM

5. STOCK MAINTENANCE SYSTEM

6. ONLINE COURSE RESERVATION SYSTEM

7. E-TICKETING

8. SOFTWARE PERSONNEL MANAGEMENT SYSTEM

9. CREDIT CARD PROCESSING SYSTEM

10. E-BOOK MANAGEMENT SYSTEM

11. RECRUITMENT SYSTEM

12. FOREIGN TRADING SYSTEM

13. CONFERENCE MANAGEMENT SYSTEM

14. BPO MANAGEMENT SYSTEM

INRODUCTION
What is OOAD?
2
Objects have been used as the information basis for the conceptual design of interactive systems
for at least a decade. Given recent advances in the development of object-oriented modeling
languages and methodologies, it is now timely to re-evaluate the role of object modeling during
the process of user interface design.

OO MODELING AND USER INTERFACE DESIGN

User interface design techniques which incorporate object-oriented modeling techniques, e.g. to
depict the domain, core objects, and interactive capabilities of an application have significant
advantages, including the following:
1.Object models act as a reference to the current state of a system design, and serve as a means
of communication between user interface designers and system analysts and designers.
2. Object models act as a focus for the user interface design process, providing a framework in
which to view user tasks and the interactive capabilities of a putative system.
3. Object models of interactive systems enable the specification of tasks and/or user actions.
These specifications, which may be either formal or informal, are written in terms of state
changes in an object model of an interactive system.
4. The rigorous approach offered by the combination of object modeling and user interface
design form a solid foundation for subsequent implementation efforts.

Looking to the future, it is likely that object oriented modeling will become a standard part of the
system life cycle. Consequently, it is of fundamental importance that the user interface design
community provides methodologies that work in conjunction with object-oriented system
analysis and design methodologies.

GOALS:
The goals of the workshop are to bring together user interface design practitioners and
methodologies in order to:
1. Survey current practice and theory in object-oriented user interface design.
2. Formulate an integrated approach to object modeling within user interface deign life cycle.

ISSUES:
Dominant issues which the workshop will address in position papers and in small group
discussions are:

 The role of object-oriented modeling techniques within user interface design

methodologies.
 A general framework for the integration of object-oriented and user interface design
methods.
 Relating user interface design artifacts to object models.
 Notations for object-oriented user interface design.
 Description of user’s interaction through use cases.

3
  The effects of interaction style on the structure of object models.
 Abstract object-oriented architectures and patterns for interactive system specification.
 Appropriate levels of formality during the design process.
 Systematic techniques for the revelation of domain objects and states at the user interface.
 Tools support for object-oriented user interface design.

OBJECT INTEROPERABILITY

Interoperability can be defined as the ability of two or more entities to communicate and
cooperate despite differences in the implementation language, the execution environment or the
model abstraction. Basically, three main levels of interoperability between objects can be
distinguished: the syntactic level (names and signatures of operation), the protocol level(partial
ordering between exchanged messages and blocking conditions), and the semantic level(“meaning”
of operations).

Syntactic interoperability is currently well defined and understood at the interface level.
The basic problem is that the study of interoperability at the other two levels currently presents
serious challenges, from both the theoretical and practical points of view. This workshop focuses
mainly on object interoperability at the protocol and semantic levels.

Interoperability is one of the key aspects related to the construction of large object-
oriented systems, and it can be defined as the ability of two or more entities to communicate and
cooperate despite differences in the implementation language, the execution environment or the
model abstraction. Basically three main levels of interoperability between objects can be
distinguished: the syntactic level (names and signatures of operation), the protocol level(partial
ordering between exchanged messages and blocking conditions), and the semantic
level(“meaning” of operations).

Syntactic interoperability is currently well defined and understood at the interface level,
where now open system architects and vendors are trying to establish interpretational standards
(COBRA,JavaBeans,COM..).

However, it is also recognized by all the software developers that this sort of
interoperability is not sufficient for ensuring the correct development of object oriented
applications, should they be object-oriented or component-based applications.

But on the other hand, the study and the usage of the latter two levels currently present
serious challenges, from both the theoretical and practical point of view. There have been some
partial advances in those levels, but we are still far from reaching any satisfactory solution.

4
 Object interoperability can embrace aspects besides and beyond components. Although
often confused, components and objects can be really seen as orthogonal concepts, each one
having its own specific and distinguishing features. In general, component interoperability can be
seen as a particular case of the object interoperability problem.

Another interesting issue and closely related to object interoperability is replace ability,
i.e. the polymorphic substitutability of objects in clients, or how to guarantee that the behavior of
subclass instances is consistent with that of super class instances. Interoperability and replace
ability are the two flip sides of the object compatibility coin.

This workshop aims to promote research concerned with all the aspects of
interoperability and the replace ability and between object, in particular at the protocol and
semantic levels. Topics of interest include, but are not limited to:

 Enabling models, technologies and architectures for object interoperability.

 Interface and protocol matching.
 Mediated architectures and automated construction of mediators.
 Resource discovery based on the semantic matching.
 Extension to object interfaces and IDLs to deal with protocol or semantic interoperability.
 Formal aspects of interoperability.
 Object replacement and correct sub classing.
 Using coordination to achieve interoperability.

The workshop tries to provide a venue where researchers and practitioners on these topics can
meet, disseminate and exchange ideas and problems, identify some of the key issues related to
object interoperability, and explore together possible solutions. To enable lively and productive
discussions, attendance will be limited to 20 participants and submission of a position statement
is required. All submissions will be formally reviewed.

INTEROPERABILITY—DEFINITIONS AND SCOPE

Interoperability is a broad problem domain. It is typically investigated within a specific

scope, such as within particular community (e.g., libraries, commercial entities, scientific
communities), within a particular classification of information (e.g., electronic records, technical
reports, software), or within a particular information technology area (e.g., relational databases,
digital imaging, data visualization).

OBJECTIVES

The objectives this is to introduce an approach to software design where the design is structured
as interacting objects. When you have read this chapter you will: understand how a software

5
design may be represented as a set of interacting objects that manage their own state and
operations,

 Know the most important activities in a general object-oriented design process.

 Understand different models that may be used to document an object oriented design.
 Have been introduced these models in the Unified Modeling Language (UML).

UML

UML is used to specify, visualize, modify, construct and document the artifacts of an
object-oriented software-intensive system under development.

USE-CASE DIAGRAMS (OVERVIEW)

Use-case diagrams graphically depict system behavior (use cases). These diagrams
present a high level view of the system is used as viewed from an outsider’s (actors) perspective.
A use-case diagram may depict all or some of the use cases of a system.

A use case system diagram can contain:

 Actors (“things” outside the system)

 Use cases (system boundaries identifying what the system should do)
 Interactions or relationships between actors and use cases in the system including the
associations, dependencies and generalizations.

Use-case diagrams can be used during analysis to capture the system requirements and to
understand how the system should work. During the design phase, you can use use-case
diagrams to specify the behavior of the system as implemented. You can display and modify the
properties and relationships of a use case through the use-case specification.

6
 membership enrollment

<<include>> <<include>>

fill form pay amount

Manager

log in

student

search books
update details

issue books

database

Return books

update status

pay fine

cancel membership

ACTIVITY DIAGRAM (OVERVIEW)

7
 Activity diagram provide a way to model the workflow of a business process. You can
also use activity diagrams to model code-specific information such as a class operation. Activity
diagrams are familiar to a flowchart because you can model a workflow from activity to activity.
An activity diagram is basically a special case of a state machine in which most of the states area
activities and most of the transitions are implicitly triggered by completion of the actions in he
source activities and most of the transitions are implicitly triggered by completion of the actions
in the source activities. The main difference between activity diagrams and state charts is activity
diagrams are centric, while state charts are state centric. An activity diagram is typically used for
modeling the sequence of activities in a process, whereas a state chart is better suited to model
the discrete stages of an object’s lifetime.

Activity diagram can model many different types of workflows. For example, a company
could use activity diagram to model the flow for approval of orders or to model the paper trial of
invoices. An accounting firm could use activity diagrams to model any number of financial
transactions. A software company could use activity diagram to model a software development
process.

State machine diagram samples

 Modeling tan operation with an activity diagram sample

 Robot transmission state chart diagram sample
 Using swim lanes on an activity diagram sample

Understanding workflows

Each activity represents the performance of a group of actions in a workflow. Once the
activity is complete, the flow of control moves to the next activity or state through a transition. If
an outgoing transition is not clearly triggered by an event, then it is triggered by the completion
of the contained actions inside the activity. A unique activity diagram feature swim lane that
defines who or what is responsible for carrying out the activity or state. It is also possible to
place objects on activity diagrams. The workflow stops when a transition reaches an end state.

You can attach activity diagrams to most model elements in the use case or logical views.
Activity diagrams cannot reside within the component view.

Activity Diagram Tools

You can use the following tools on the activity diagram toolbox to model activity diagrams:

8
 Activities
 Decisions
 End state
 Object
 Object flow
 Start state
 States
 Swim lanes
 Synchronizations

book bank
management system

authenticat book get books status

register search
ion

enter enter the enter

enter memberID and enter
details search criteria member ID
password bookID

details display enter

display membership
valid valid results duration
status

<<No>>
<<No>> invalid reg
authenticat
<<Yes>> ion failed membershi
p active
obtain
<<Yes>>
memberId
<<No>> calculate fine
enter into
the panel
successful
<<Yes>>
registration
obtain the
book
authentication <<No>>
successful

9
CLASS DIAGRAM (OVERVIEW)

The class diagram class allows you to add, retrieve and delete classes and categories to
and from a class diagram. The class diagram class has a set of properties and methods that apply
specifically to class diagrams. In addition, it inherits all diagram class properties and methods.

The following table describes the Diagram class properties.

Property Description

Element Inherits all element class properties

Documentation specifies the documentation belonging to the diagram
ExternalDocuments specifies the collection of external documents belonging to the diagram
Items collection of items belonging to the diagram
ItemViews collection of item views belonging to the diagram
Visible determines diagram visibility
ZoomFactor specifies the zoom factor of the diagram

The following describes the diagram class methods.

Method Description

RoseObject Method inherits all RoseObject class method

Element Methods inherits all Element class methods

Activate makes a diagram the currently active diagram in the application

AddExternalDocument adds an external document object to a diagram

AddNoteView adds a note to a diagram

AddRelation view adds a relation view object to a diagram

AutosizeAll automatically resizes the item views

CenterDiagramToView centers a diagram over one of its RoseItem View

DeleteExternalDocument deletes an external document object from a diagram

Exists determines whether a specified diagram object exists

10
GetNote Views retrieves the note views belonging to a diagram

GetParentContext returns the model element that contains the diagram

GetSelectedItems retrieves the currently selected items from a diagram

Invalidate redraws a diagram

IsACtive Indiactes whether the diagram is currently active

Layout Draws a diagram

Render Creates a window metafile and renders the diagram to file

manager
name : String
branch : String

processdata()
issuemembershipID()
updatestatus()

status update
status : String
enrollment last renewed : Date
return books books holding : Integer
name : String book search books
bookID : Integer next renewal : Date
age : Integer title : String bookID : Integer
memberID : Integer
address : String author : String memberID : Integer
date : Date update()
colege : String publication : String duration : Integer
yearofstudy : Integer ISBN : Integer
return()
contactno : Integer get()
payfine()
search() checkstatus()
update()
register()

SEQUENCE DIAGRAMS (OVERVIEW)

A sequence diagram is a graphical view of a scenario that shows object interaction in a

time-based sequence what happens first, what happens next. Sequence diagrams establish the
roles of objects and help provide essential information to determine class responsibilities and
interfaces. This type of diagram is best used during early analysis phases in design because they
are simple and easy to comprehend.

Sequence diagrams are closely related to collaboration diagrams and both are alternate
representation of an interaction. There are two main differences between sequence and
collaboration diagrams: sequence diagrams shows time-based object interaction while
collaboration diagrams show how objects associate with each other.

A sequence diagram has tow dimensions: typically, vertical placement represent time and
horizontal replacement represent different objects.

11
The following tools located on the sequence diagram toolbox enable you to model sequence
diagrams:

 Object
 Message Icons
 Focus of control
 Message to self
 Note
student manager database

fill form

verify details

payment

issue memberID and password

update

COLLABORATION DIAGRAMS (OVERVIEW)

Collaboration diagrams and sequence diagrams are alternate representations of an

interaction. A collaboration diagram is an interaction diagram that shows the order of messages
that implement an operation or a transaction. A sequence diagram shows object interaction in a
time-based sequence.

Collaboration diagrams shows objects, their links, and their messages. They can also
contain simple class instances and class utility instances. Each collaboration diagram provides a
view of the interactions or structural relationships that occur between objects and object-like
entities in the current model.

The collaboration diagram command creates a collaboration diagram from information

contained in the sequence diagram. The create sequence diagram command creates a sequence
diagram from information contained in the interaction’s collaboration diagram. The Goto
sequence diagram and Goto collaboration diagram commands traverse between an interactions’
two representations.

12
 An object specification enables you to display and modify properties and relationship of
an object. The information in a specification is presented textually. Some of this information can
also be displayed inside the icons representing objects in collaboration diagrams.

Use collaboration diagrams to: Analysis indicate the semantics of the primary and
secondary interaction design show the semantics of mechanisms in the logical design of the
system use collaboration diagram as the primary vehicle to describe interactions that express
your decisions about the behavior of the system.

COMPONENT DIAGRAM

A component diagram shows the allocation of classes and objects to components in the
physical design of a system. A component diagram may represent all or part of the component
architecture of a system.

The dependency relationship indicates that one entity in a component diagram uses the
service or facilities of another. Dependencies in the component diagram represent compilation
dependencies. The dependency relationship may also be used to show calling dependencies
among components, using dependency arrows from the components to interface on another
components.

Draw a dependency relationship between two classes, or between a class and an interface,
to show that the client class depends on the supplier class/interface to provide certain services,
such as:

 The client class accesses a value (constant or variable) defined in the supplier
class/interface.
 Operations of the client class invoke operations of the supplier class/interface.
 Operations of the client class have signatures whose return class or arguments are
instances of the supplier class/interface.

13
DEPLOYMENT DIAGRAMS (OVERVIEW)

A deployment diagram shows processors, devices and connections. Each model contains
a single deployment diagram which shows the connections between its processors and devices
and the allocation of its process to processors.

Processor specifications, device specifications and connection specifications enable you

to display and modify the respective properties. The information in a specification is presented
textually; some of this information can also be displayed inside the icons. You can change
properties or relationships by editing the specifications. It gets automatically updated.

The deployment diagram collection class allows you to crate and manipulate deployment
diagram collections. For example, you can

 Add a deployment diagram to a deployment diagram collection

 Iterate through a deployment diagram collection in order to access a particular
deployment diagram.
 Delete a deployment diagram from a deployment diagram collection.
 Check the lists of properties and methods for complete information.

MANAGER

STUDENT

PRINTER

DATABASE

BARCODE READER

14
 PASSPORT AUTOMATION SYSTEM

PROBLEM STATEMENT

Passport Automation System is used in the effective dispatch of passport to all of the
applicants. This system adopts a comprehensive approach to minimize the manual work and
schedule resources, time in a cogent manner. The core of the system is to get the online
registration form (with details such as name, address etc.,) filled by the applicant whose
testament is verified for its genuineness by the Passport Automation System with respect to the
already existing information in the database. This forms the first and foremost step in the
processing of passport application. After the first round of verification done by the system, the
information is in turn forwarded to the regional administrator's (Ministry of External Affairs)
office. The application is then processed manually based on the report given by the system, and
any forfeiting identified can make the applicant liable to penalty as per the law. The system also
provides the applicant the list of available dates for appointment to 'document verification' in the
administrator's office, from which they can select one. The system forwards the necessary details
to the police for its separate verification whose report is then presented to the administrator. The
administrator will be provided with an option to display the current status of application to the
applicant, which they can view in their online interface. After all the necessary criteria has been
met, the original information is added to the database and the passport is sent to the applicant. 

SOFTWARE REQUIREMENT SPECIFICATION

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

INTRODUCTION

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

The System provides an online interface to the user where they can fill in their personal
details and submit the necessary documents (may be by scanning).
The authority concerned with the issue of passport can use this system to reduce his
workload and process the application in a speedy manner.
Provide a communication platform between the applicant and the administrator.
Transfer of data between the Passport Issuing Authority and the Local Police for
verification of applicant's information.
Users/Applicants will come to know their status of application and the date in which they
must subject themselves for manual document verification.

OVERALL DESCRIPTION

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

16
FUNCTIONAL REQUIREMENT:
DESCRIPTION:

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

INTERFACE REQUIREMENT

LOGIN PAGE:

17
USER PAGE:

USER SIGN UP FORM:

18
STATUS PAGE:

FRESH PASSPORT:

19
RENEW PASSPORT:

20
UML DIAGRAMS

USE CASE DIAGRAM

CLASS DIAGRAM

ACTIVITY DIAGRAM
21
New Registration

22
Check Status

Admin Panel

23
STATECHART DIAGRAM

SEQUENCE DIAGRAM

24
COLLABORATION DIAGRAM

New Registration

25
Check Status

Admin Panel

COMPONENT DIAGRAM:
26
 applicant.obj applicant.cpp applicant\.exe

admin.obj admin.cpp admin.exe

polics.obj polics.cpp polics.exe

DB.obj DB.cpp DB.exe

DEPLOYMENT DIAGRAM:

PC databas
e server

<<TCP/IP>>
<<TCP/IP>>

applicati
...

CONCLUSION:

The Passport Automation System makes the process easier and less burden for the
applicant. This project helps us to apply for passport and renewal process was designed and
UML diagram were drawn and implemented.

27
 BOOK BANK

PROBLEM STATEMENT
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 particular book.

SOFTWARE REQUIREMENTS SPECIFICATION

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 the books.
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 external
stimuli.   
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.
OVERVIEW
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 previous books.

28
OVERALL DESCRIPTION
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,. 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 this system.
FUNCTIONAL REQUIREMENTS
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 notifications. 

NON-FUNCTIONAL REQUIREMENTS

PERFORMANCE REQUIREMENTS: The web interface should be able to support multiple

users trying to log in simultaneously.
SAFETY REQUIREMENTS: 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
prevent errors.
SECURITY REQUIREMENTS: 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 bestowed with the privileges of handling any kind of modifications.
USE CASE DIAGRAM
The UML use case diagram is used to illustrate the names of use cases and actors, and the
relationships between them providing an excellent picture of the system context. The online book
bank management system consists of three actors namely student, manager and database. The
student fills the form and pays the initial amount to become a member of the book bank. The
details of the student are entered into the database by the manager and the student is provided
with a login ID and password. The student logs in the appropriate website to search the required
the books. The list of books available in the database will be searched and the details will be
displayed to the user. The Manager issues the book and the status of the student is updated in the
database. The student returns the book to the Manager who checks the status and then updates

29
the database. The student pays fine to the manager in case of loss of books. The student can also
cancel the membership and the manager updates his/her status in the database.

30
31
 CLASS DIAGRAM
Class diagrams are used to illustrate classes, interfaces and their associations. The classes
used in this project include Manager, Enrollment, book_search, books, return_books and
status_update. Each class includes attributes and operations. The visibility of the attributes can
be made private or public accordingly. The solid arrows or links between the classes indicate the
dependencies of the classes on each other.

manager
name : String
branch : String

processdata()
issuemembershipID()
updatestatus()

status update
status : String
enrollment last renewed : Date
return books books holding : Integer
name : String book search books
bookID : Integer next renewal : Date
age : Integer title : String bookID : Integer
memberID : Integer
address : String author : String memberID : Integer
date : Date update()
colege : String publication : String duration : Integer
yearofstudy : Integer ISBN : Integer
return()
contactno : Integer get()
payfine()
search() checkstatus()
update()
register()

32
INTERACTION DIAGRAMS

MEMBERSHIP ENROLLMENT
The student fills the form and submits to the manager. The form contains the details of
the student (Name, College, Year of study, Address, Contact number). The manager verifies the
details of the student. The student pays the initial amount to the manager who provides the user
ID and password and updates the details of the student in the database.

SEQUENCE DIAGRAM:

student manager database

fill form

verify details

payment

issue memberID and password

update

COLLABORATION DIAGRAM:
1: fill form
3: payment
student manager

4: issue memberID and password

2: verify details
5: update

database

33
SEARCH BOOKS
The student logs in using the unique user ID and password issued to him/her to search the
books in the database. The student enters the book name, author of the book and the publication
details. The ISBN can also be used to search for the books. The database displays a list of
available books in the book bank and the student can make the appropriate choice.
SEQUENCE DIAGRAM:

student database

enter book title

enter book author

enter publication details

display the available books

COLLABORATION DIAGRAM:

1: enter book title

2: enter book author
3: enter publication details
student database

4: display the available books

ISSUE BOOKS

34
 The student enters the required book ID in the database. The corresponding book details
will be displayed to the manager. The books will then be issued to the student. He/She must
collect the books from the book bank center. The database will be updated by the manager that
contains details such as the number of books issued and return date.
SEQUENCE DIAGRAM:

student manager database

enter bookID

display book details

check member status

issue books

update status

COLLABORATION DIAGRAM:

student manager

4: issue books

2: display book details

1: enter bookID
3: check member status
5: update status

database

RETURN BOOKS

35
 The student returns the books to the manager. The manager checks the status of the
student and collects fine in case of loss of any books. The database is then updated.
SEQUENCE DIAGRAM:

student manager database

return books

check status

pay fine in case of due

update

COLLABORATION DIAGRAM:

1: return books
3: pay fine in case of due
student manager

2: check status
4: update

database

ACTIVITY DIAGRAM

36
The activity diagram shows the sequential and parallel activities in the book bank system. The
activities include enrollment of membership, authentication process that involves the student
entering his user ID and password, search books from the database, getting the requested books
and updating of status.

book bank
management system

authenticat book get books status

register search
ion

enter enter the enter

enter memberID and enter
details search criteria member ID
password bookID

details display enter

display membership
valid valid results duration
status

<<No>>
<<No>> invalid reg
authenticat
<<Yes>> ion failed membershi
p active
obtain
<<Yes>>
memberId
<<No>> calculate fine
enter into
the panel
successful
<<Yes>>
registration
obtain the
book
authentication <<No>>
successful

STATE DIAGRAMS

37
MEMBERSHIP ENROLLMENT
The student enters the details. If the details are valid then user ID and password are
issued and the registration will be successful. If invalid, the student has to re-enter the details.

enter valid get successful

details member id registration

invalid

re enter
details

SEARCH BOOKS
The student enters the book details after logging into the appropriate website. The
database displays the list of available books from which the student selects the required books.
If the book is not found a message will be displayed to the student.

enter book found display book

search criteria suggestions

not found

display book
not found

GET BOOKS

38
 The books are received by the student from the manager. In case of loss of any book the
student has to pay fine and may prompt for renewal if necessary. Thedatabase will be updated by
the manager.

enter book enter active status obtain

id member id books

inactive status

display fine and

prompt for renewal

COMPONENT DIAGRAM
The components used in the book bank management system include student,
manager and the database. These components represent a modular part of the system that
encapsulates its contents and its manifestation can be replaced within its environment.

39
DEPLOYMENT DIAGRAM

The deployment diagram shows the deployment of software elements to the

physical architecture and communication between physical elements. The nodes are Manager,
Student, Printer, Database and Barcode readers. These nodes are associated by use of links.

MANAGER

STUDENT

PRINTER

DATABASE

BARCODE READER

CONCLUSION:

The book bank provides various detail about the book was designed and UML diagrams
were drawn and code has been created.

EXAM REGISTRATION SYSTEM

40
PROBLEM STATEMENT

The exam registration system provides the facility for students to register online for
entrance examination. The student uses the web server to fill in the application form and submit
it to the administrator. After the verification of details provided by the student, the administrator
provides the fees details and the payment is done by DD. The hall ticket containing the student
details and register number is issued. The student takes a copy of hall ticket from the web.

SOFTWARE REQUIREMENTS SPECIFICATION:

1. INTRODUCTION:

Student can register in online for writing their entrance examination.

2. SCOPE:

The student instead of going to register them self for entrance exam registration,
he /she can stay where ever they are and register themselves for the entrance exam in
online by downloading the application form from the college website and submit it to the
college administrator. It saves much time of the student and more convenience is present.

3. OVERVIEW:

In this SRS document an overall description and specification requirement for

exam registration is given.

FUNCTIONAL REQUIREMENTS:

The student first browses into the college website and downloads the application and fills
the details and submits the application. The administrator validates the form and if the student is
admitted for writing the entrance exam the details of fees payment is updated in the status of that
student’s application number. Then the student checks the status of fees payment, pays the fees
by DD and administrator provides the hall ticket with student details and register number.

INTERFACE REQUIREMENT:

41
 GUI 1: The application form which the student downloads from the college website is
first interface.

GUI2: The check status for admission and fees payment is the second interface where
the student can check whether the student is admitted or not, and if he is admitted to write
the entrance exam, he checks the fees details sent by the administrator and pays the fees
by DD by entering the DD number in the status form and send it to the administrator.

GUI 3: The administrator on receiving the fees payment, he provides the hall ticket with
the student details and register number to the student.

GUI 4: The student takes the copy of the hall ticket using the printer as the device.

UML DIAGRAMS

USE CASE DIAGRAM:

The above diagram explains about the exam registration done in online. The students first
enters into application and fills the necessary details and submit it, then the admin will verify the
details and if the student is admitted he sends the admission details with fees payment details.
The student checks for the admission status and once he receives the fees payment request he
pays the fees by DD. Then on return the admin will send the hall ticket with students details and
register number.

42
 enter your application

fill all your details

submit all details

student admin

send admission details with fees

details

check status for fees payment

pay the fees by DD

issue hall ticket with student

details and reg no

43
CLASS DIAGRAM:

The student, admin and hall ticket are given as class names. The appropriate attributes
and the operations are given which are related to the exam registration.

administrator
stud name : String
name : String address : String
address : String ph no : Integer
ph no : Integer DOB : Date
DOB : Date degree completed : String
degree completed : String percentage : Integer
percentage : Integer religion : String
religion : String community : String
community : String
verify()
fill app() admit student()
submit form() provide fees details()
provide hall ticket()

hall ticket
reg no : Integer
name : String
DOB : Date
date of exam : Date
location : String

issue()
print()

44
SEQUENCE DIAGRAM:

The event that takes place between the students, admin and providing hall ticket to the
student is given here.

stud administrator hall ticket

get the application

fill the application

submit the application

verify the details

reject application

send the admission confirmation

check staus for fees payment

pay fees by DD

print the details in hall ticket

provide hall ticket

send the hall ticket

collect hall ticket

COLLABORATION DIAGRAM:
45
 When the sequence diagram is run using the f5 key the collaboration diagram is
produced. The events that are given in the sequence diagram is given in the numerical order in
which they are taking place sequentially.

1: get the application

5: reject application
2: fill the application
3: submit the application
7: check staus for fees payment
8: pay fees by DD
12: collect hall ticket
stud administra
tor
4: verify the details
6: send the admission confirmation
10: provide hall ticket

11: send the hall ticket 9: print the details in hall ticket

hall ticket

46
ACTIVITY DIAGRAM:

The activities done between the student and the admin are explained in this activity
diagram.

verify stud
enter into details
application

admit stud for

fill the
entrance exam
details

submit the
details

check
status

provide hall
ticket

pay fees
by DD

collect hall
ticket

STATE CHART DIAGRAM:

47
 The activities done between the student and the admin are given in this state chart
diagram. It has two states valid and invalid. If the application is accepted by the admin after
validation of student details then it moves next process for payment of fees to collect the hall
ticket. If it is invalid it returns back to the application to fill in the left out details.

invalid

enter the submit the verify the

details details details

valid

pay the
fees

issue hall
ticket

COMPONENT DIAGRAM:

The student, admin and hall ticket are used as the components here. The student sends the
details to the administrator; the administrator verifies the student details and provides the hall

48
ticket to the student with their details and register number. The student takes the hall ticket using.

stud administr
ator

hall
ticket

DEPLOYMENT DIAGRAM:

The elements used here are the student, admin, hall ticket and the database of the student.
The student submits the details to the admin; the admin verifies the details and provides the hall
ticket after fees payment done by the student. The student’s details are kept in database for
verification purpose in future. The student takes the hall ticket by using a printer.

stud administ
rator

hall
ticket databas
e

printer

49
CONCLUSION:

A web-based application was designed, developed, and implemented as a web

portal that enables different parties working with Associate-Degree General Examination to
benefit from.

STOCK MAINTENANCE SYSTEM

PROBLEM STATEMENT

INVENTORY SYSTEM is a real time application used in the merchant’s day to day system.
This is a database to store the transaction that takes places between the Manufacturer, Dealer and the Shop
Keeper that includes stock inward and stock outward with reference to the dealer.

SOFTWARE REQUIREMENTS SPECIFICATION

INTRODUCTION:

The purpose of Stock Maintenance System is for managing the Stock or product Information in
the Database and Updating when required, This SMS is used for retrieving, billing and taking the monthly
sales details.

This Scope of Stock Maintenance System is to overcome the work load and time consumption
which make Transaction Report.

The Overview of Stock Maintenance System Project contains Billing with printout formatting,
Stock Purchasing, Sales Report, Purchase Report and Bill Transaction Details to be done in this Project.

OVERALL DESCRIPTION:
50
 The Stock Management System (SMS) assumes control over the bookkeeping and accounting
needed to operate a Warehouse for a company specializing in retail sales of food and groceries. All day-
to-day operations of the warehouse, as well as conducted weekly accounting of the products stored in the
warehouse and disbursed to participating supermarkets, will be performed by the software.

A considerable amount of accounting needed to operate a typical warehouse calls for a reliable
and fast software tool to help the warehouse management handle flows of information regarding incoming
and outgoing quantities of products and a stock inventory.

The problem of storage of the accounting documents such as invoices and orders would be solved.
Tedious arithmetic involved in the corresponding bookkeeping will be automated.

A cost of maintenance of a specially trained accounting professional in the warehouse would be

saved by replacing this position with a software tool and a less costly data entry specialist.

FUNCTIONAL REQUIREMENTS:

1. Login: Login is achieved by the stock manager.

2. Analysis of Goods: Finding the expired goods, Finding the older ones and selling with offer prices
3.Preparing the List: List of goods or items which are needed are prepared by the stock manager.
4. Getting the Quotations: Stock manager gets the quotation from the company manager.
5. Choosing the best one: Stock manager chooses the best quotations.
6. Purchasing the goods: Stock manager purchase the good from the company manager.
7. Delivery & Payment: Delivery of goods by the required company and payment settled by the stock
manager.
8. Update: It is performed by the stock manager in the database.

NON- FUNCTIONAL REQUIREMENTS:

Nonfunctional requirements define the needs in terms if performance, logical database

51
requirements, design constraints, standard compliance, reliability, availability, security, maintainability
and portability.

1. Performance Requirements:
Performance requirements define acceptable response times for system functionality.
The load time for user interface screens will take no longer than two seconds.
The login information shall be verified within five seconds. Queries shall results within five seconds.
2. Design Constraints:
The software shall be a standard system running in a windows environment. The system shall be
developed using rational enterprise suite.

3. Reliability:
Specify the factors required to establish the required reliability of the software system at time of delivery.
4. Availability:
The system should have an availability of 99.99%.
5. Portability:
The system should be extremely via the usb drive.
The system shall be easy to migrate or backed up via another use drive.
6. Maintainability:
The system shall utilize interchangeable plug-in. The system shall be easily updateable for fixes and
patches. The system shall be easy to upgrade.

MODULE DESCRIPTION:

Login: The login is used for security of the Seller. The Seller logs in with the user name and the
password.
Analysis: The stock manager analyses the stocks. He identifies the old stocks and the expired goods and
also the list of items needed.
Old stock clearance: The stock manager clears the old stock goods by selling it at an offer price.
Order List Preparation: The stock manager prepares the list of items to be bought. Then he calls the
52
company for quotations.
Quotation: The stock manager calls the company for quotations. After receiving the quotations from the
company, the stock manager chooses the quotation.
Purchase: The stock manager purchases the needed goods from the corresponding company in which the
quotations are selected.
Payment: The stock manager pays the bills along with the tax and the goods are delivered by the
company manager.

UML DIAGRAMS

UML USECASE DIAGRAM:

UML provides use case diagram notation to illustrate the names of use case and author relationship
between Seller and the Database.

Primary Actor: Seller

Secondary Actor: Database

Precondition: The seller must capable of selecting atleast one product for billing

53
 Search products

View product specification

Seller Add new products DataBase

Edit products

do billing

UML CLASS DIAGRAM:

The UML class diagram is to illustrate class interfaces as their actions. They are used for static
object modeling, in this class diagram Product, Customer and Billing classes are used.

product customer billing

PID : Integer Cname : String Cash : Int
Pname : Integer Caddress : String Card : Int
PType : Integer Cphone : Int Bank name : String
CmailId : String Branch : String
updating()
adding() selecting products() Purchasing()
comparing products()
... checking_balance()

54
UML STATE CHART DIAGRAM:

An UML state machine represents the interaction events and states of an object and behavior of an
object in reaction to an event. It consists of mainly three states login state, selection state and payment
state.

Login

Selection
of product

payment

UML ACTIVITY DIAGRAM:

An UML activity diagram shows sequential and parallel activates in a process, work flows, data
flows and compiler algorithm. All the states of stock maintenance system are shown in detail.

55
 Enter login
details

Select category of
your choice

select the get sale get customer

products information information

payment payment
through cash through card

acknowledge
via bill

UML SEQUENCE DIAGRAM:

Sequence diagrams illustrate a kind of format in which each object interacts via message. This
Sequence diagram consists of Seller, Database and Payment, shows the flow of execution carried out in
stock maintenance system.

56
 Seller Database Payment

login

acknowledge

Add products

select products

update product information

get customer information

paid through card or cash

acknowledge via bill

store information in database

UML COLLABRATION DIAGRAM:

COLLABRATION diagram illustrate that object interact on a graph or network format in which
object can be placed where the diagram. In collaboration diagram the object can be placed in anywhere on
the diagram.

57
 1: login
3: Add products
4: select products
Seller 5: update product information
6: get customer information

Database
2: acknowledge
7: paid through card or cash
9: store information in database
8: acknowledge via bill

Payment

UML COMPONENT DIAGRAM:

Components are slightly fuzzy concept in this UML, because both class and Components can be
used to model the something.

user
interface

Seller updates or processes

Stock Inventory
System(DB)

UML DEPLOYEMENT DIAGRAM:

Deployment diagram shows the assignment of concrete software artifact to Computational nodes.
It shows the deployment of software elements to the physical elements. Deployment diagram are useful to
communicate or deployment architecture.

58
 Client Processor Web server

IMPLEMENTATION:

           After competition of the diagrams for stock management system from use case to deployment we
have to generate code. So select the main class from the use case diagram and then click the tools in the
menu bar. In that select the language in which you e want to generate code. If you select the java/j2ee,
then sub option will open in that select generate code option. Then the system will automatically generate
code from that particular class. Then repeat the process for each diagram.

SOURCE CODE:

STOCKMANAGER.JAVA

//Source file: C:\\Users\\Surya\\Desktop\\product.java

Product.java

public class product

private Integer PID;

private Integer Pname;

private Integer PType;

public customer theCustomer;

/**

@roseuid 4F5F7F0B0064

*/

public product()

59
 }

/**

@roseuid 4F5E19EE0132

*/

public void updating()

/**

@roseuid 4F5E19F60337

*/

public void adding()

//Source file: C:\\Users\\Surya\\Desktop\\billing.java

Billing.java

import java.awt.TexturePaintContext;

public class billing

private TexturePaintContext.Int Cash;

private TexturePaintContext.Int Card;

private String BankName;

private String Branch;

/**

@roseuid 4F5F7F180011

60
 */

public billing()

/**

@roseuid 4F5E1A8E011C

*/

public void Purchasing()

/**

@roseuid 4F5E1A940067

*/

public void checking_balance()

//Source file: C:\\Users\\Surya\\Desktop\\customer.java

Customer.java

import java.awt.TexturePaintContext;

public class customer

private String Cname;

private String Caddress;

private TexturePaintContext.Int Cphone;

61
 private String CmailId;

public billing theBilling;

/**

@roseuid 4F5F7F190260

*/
public customer()

/**

@roseuid 4F5E1A36010D

*/

public void selectingProducts()

/**

@roseuid 4F5E1A400273

*/

public void comparingProducts()

}}

CONCLUSION:

Thus the project for stock management system has been successfully executed and Codes are
generated.

62
 ONLINE COURSE RESERVATION SYSTEM

PROBLEM STATEMENT:

Course registration system is used for the students to register their online course before
joining their college. It also makes registration easier. In the system the student has to enquire
about the online courses, college and about the fee details to the administrator intern will provide
the details that are required by the student. The system also provides the facility for cancelling
the online courses that are registered already without the details.

 The system is build to be used by students and manage by an administration.

 The students who want to join the course will have to register the course and attend
counseling to select the course.
 The student have to login to the system before any processing can be done.
 The student can see the course available to him and register to course he wants.
 The registrar can maintain the course details and view all the students who have
registered to any course

SOFTWARE REQUIREMENT SPECIFICATION

INTRODUCTION

PURPOSE

Online Course Registration System is registration software that helps to accept course or
event registration online. Online Course Registration System is ideal for adult schools,
educational camps, sports camps, corporate training programs, and online training programs.

Online course registration software includes features such as security, email based user accounts,
automatic scheduling, late fee collection, registration deadline, and multi-course deadline. Also,
Online Course Registration System can be fully customized according to your specifications.

SCOPE

The main scope of the Online Course is to perform modification, cancellation, registration
of the online course that is selected by the student.

63
 The following subsections describe the scope of the Course Registration System in terms
of its audience and organization.

Audience:

The intended users are the people responsible for implementing the Course Registration
System.

Organization:

This document describes the Course Registration System requirements in terms of

system requirements, analysis and design diagram.

The course registration system automate the system, rechecking the inclusion of all required
material and automatically ranking, each student application based on the number of criteria. The
criteria include the ranking of the college, their grade said university and their certificate. It
enables things to be simplified and considerably quickly accessed. The data used by the system is
stored in a database that will be the centre of all information held about students and the base for
the remainder of the process after the initial registration has been made.

OVERVIEW

The process of Online Course Reservation System is a multiphase process where several
individual students enroll themselves into a course. Each student has a unique username and
password which can be used to login. After logging, the student can enter their details in the
registration form with their course details and submit it .The registrar checks the student
eligibility for course and processes the form and notifies the status of the student. The eligible
students are given schedule for the course by the registrar.

The Online Course Reservation System replaces the traditional, manual course
reservation system by which lot of paper work can be reduced. The students will be able to view
the available courses select the courses. This is the primary feature of the system. Another
feature is that the system should submit the form to the registrar. The eligibility of the students
for the desired course is verified by the system and then the reservation for the course is done.
The system also provides the facility of cancelling the reservation.

64
FUNCTIONAL REQUIREMENTS

The user shall be able to search either all of the initial set of databases or select a subset
from it. The user shall be able to get knowledge about the course details without referring any
written documents. The software is responsible to automate the admission procedure. The system
has to process the fee settings and fee collections, printout of the fee receipt should be generated
by the system. It should have provision to set the curriculum for each course. The user will
register with the system by providing personal information such as email address, ages, school
etc.., and the information will be stored in the database. The student will be able to see their own
profile page.eg :) The personalized profile page with course registered details, college name and
schedule information when they login the system. When the students press the download link the
student will be able to download all the relevant course materials. Upon the request from the
administrator the system must produce monthly on yearly academic results such as financial,
staffing result and other enrollments. If there is any amendments that needs to be made, the
registrar will do the necessary updates to system.

ENQUIRY MODULE

Description:

It includes activity of listing online course available ,the fee structure for the corresponding
online courses, result analysis of the online courses.

INPUT: Enquire about the online course

PROCESS: Enquiry request are being proceed

OUTPUT: List the details of the enquired online course

ADMISSION MODULE

Description:

It includes getting the application form by students from admin, filling in the application forms
and submission to admin.

INPUT: Get the application from the admin

PROCESS: Filling the application and submitting

65
OUTPUT: Admin prepares the details of fees payment.

MODIFICATION

Description:

It includes the change of onlinecourse, modification of the information provided in application

form etc..

INPUT: Specify the change

PROCESS: Modification are being processed

OUTPUT: Application is modified

CANCELLATION

Description:

It includes the change of dropping out from the college because of personal reason.

INPUT: Request for dropping out

PROCESS: Necessary steps to be taken by the admin

OUTPUT: Certifies return to the student

UML DIAGRAMS:

USE CASE DIAGRAM

Use case Student reserves for the desired course

Primary actor Student

Goal in context To monitor all the functionalities required

to establish the session

Preconditions Online course reservation system has to

be programmed to display he available
courses and reserve the eligible
candidates

trigger On completion of every activity a beep

has to be generated by the system

scenario 1.student selects for reservation

66
 2.student views the available courses and
select the desired one
3.student fill up the form
4.student submits the form
5.student receives the eligibility message
and proceeds for payment.
6.student confirm the reservation

exception 1.The list of courses is unavailable

2.the selected course is not available
3.student is not eligible for the desired
course

priority Essential and must be implemented in

course admission system at university

Secondary actor registrar

Open issues 1.how many courses can be adopted by

the student at a time?
2.what should be the eligibility criteria?
3.How much time must be given to the
student for the cancellation of the seat?

The student performs the following function as

 Register the course

 Submit their personal details
 Select the courses
 Update their details
The registrar performs the following function as

 Receive the information

 Checking the details
 Compute the amount based on marks

67
  Preparing the course catalogue
 Issuing allotment order

register the course

student

prepare course catalogue

registrat

receive student information

store student information

course catalogue
monitoring information

closing registration

preparing allotment orders

issue of allotment order

CLASS DIAGRAM

Classes are composed of three things: a name, attributes, and operation.

68
 A Class has three sections:
 The upper part holds the name of the class.
 The middle part contains the attribute of the class
 The bottom part gives the methods or operation the class can take or undertake.
Class diagram also refers object modeling. It provides the behavior and method of
particular object. The classes involved are student, rank list, registrar, allotment
order, course catalogue.

student course catalogue

name course name
address id
qualification student name
phone no student id
gender student dob
course to apply markdetails
sub_mark1 allotment order allotment order
sub_mark2 id no
total college name issue()
cut off course maintain()
branch name prepare()
apply course() 1
Pay amount() prepare()
issue() 1
registrar
rank list name
stud id qualification
total marks experience
cut off id no
rank
issue()
prepare marklist() register()
schedule
monitor()
date
time
rank
from reg to reg

display time()

ACTIVITY DIAGRAM

Identifying the activities and transitions for managing course information:

69
 The Registrar is responsible for managing course information in the online course
reservation system. As part of managing the course information, the registrar carries out the
following activities:

 Check if course exists

 Check whether the student is eligible or not
 If the student is eligible ,then submit the details
 Applying the course catalogue
 Issuing the allotment order
An activity diagram is a variation or special case of a state machine in which the states are
activities representation the performance of the operation and the updating are triggered the
operation. The steps involved are view college details, refer courses offered, submit
application form, pay the fees, candidate is registered.

s tudent login

browse the cours e catalog

and apply for the course

getting the student mark details

and calculate the cutoff

prepare the
mark list
no
check whether the
student is eligible
yes

reject the alloting order

student for student

clos ing
registration

STATE CHART DIAGRAM

70
 preparing of collecting the preparation of issue of call
catalog student details rank and cutoff letter

issue of allotment print the allotment prepare the student choosing

order order allotment order the course

receiving the
allotment order

INTERACTION DIAGRAM

SEQUENCE DIAGRAM

Sequence diagrams captures most of the information from the system .The steps
involved are apply the course registration, providing the mark, select courses, give
application, shows fees structure, pay fees.

71
student prepare the coursr catalog allotmentorder
ranklist

request to apply for course

accept therequest

prepare the list of students

calculate the cutofffor students

prepare the ranklist

sending ranklist

sending call letterfor counselling

select course

check availability

register course

prepare the allotment order

print and issue the allotment order

72
COLLABORATION DIAGRAM

4: calculate the cutofffor students

5: prepare the ranklist
9: check availability

1: request to apply for course

8: select course
student prepare the
ranklist

2: accept therequest
7: sending call letterfor counselling
10: register course
12: print and issue the allotment order

6: sending ranklist
11: prepare the allotment order
3: prepare the list of students

coursr
catalog

allotmentor der

COMPONENT DIAGRAM

course.e student allotment allotment

xe mark.java order.exe order.java

73
DEPLOYMENT DIAGRAM

<<device>>
applicationserver

JB container observer
auth <<JDBC>>
wind
or
web server o...
<<RMI>> e-ma
stude ... il
auth
web...
revie main frame
... w
cours
feed

b... ...

CONCLUSION:

Thus the project for online course registration system was designed by checking
eligibility criteria of the student, providing them with necessary details such as schedule details,
providing course catalogue, allotting the course catalogue and UML diagrams has been drawn.

74
 E-TICKETING

PROBLEM STATEMENT
The main purpose of this project is to reserve the tickets and cancel the reserved tickets.
E-ticketing for railway department has to be developed should contain following features.

1. The system should provide information about arrival and departure trains along with
information about the station through which it parses.
2. Search about train parsing through station can be optional either by means of train ’s
number, train name or specify source and destination station.
3. While displaying information about train, it has to provide following information
a. Station through which train parses along with arrival and departure time
b. Available of seat in different classes along with waiting list RAC information
4. While reserving ticket online the system obtain following information from the user
a. passenger name, age, sex, address number for ticket reservation
b. credit card no, bank name
c. class through passenger is going to travel ie.first or second class or ac
5. Based on availability of ticket has to be issued, the ticket issued should contain
following information- PNR number, train number, date, number of adults and children, ticket
number, age.
6. Before issuing ticket the amount from customer account has to be transferred to
railway account
7. Cancelation of booked ticket should be available
Introduction:

Purpose:
The purpose of this document is to reserve the train ticket via online. The E-Ticketing
provides an easy solution for the passengers to reserve & cancel the reserved tickets without
going to railway station.

Scope:
To develop an application for online railway ticket reservation system using front end as
Visual basic and backend as MS-Access from UML diagrams using rational

75
Functional Requirement:

Ticket reservation system is the best way for checking the availability of tickets and for
the reservation. The reservation for different trains to different destination and different timing
can be done accordingly.

UML diagram

Use Case diagram:

The use case diagram describes about the actors involved in a particular system and
their use case that are being designed for defining the process that take place in the overall
functioning of the system In this online reservation system the actor and use case are described
in the diagram as shown

Use-case Diagram:

76
CLASS DIAGRAM:

The class diagram also referred to as the object modeling. It is the main static
analysis diagram. The main thing of object modeling is to graphically show what each object will
do in the problem domain. The problem domain the relationship and the structure among the
class in the given diagram are the participants and website and attribute of those classes are listed
below each individually.

Class Diagram:

77
ACTIVITY DIAGRAM

The states are activities representing the performance of operations and the action are
transferred and triggered by the completion of the operation it is used to module the entire
business problem. These activities are described as shown in the diagram.

Activity Diagram:

78
INTERACTION DIAGRAM:

SEQUENCE DIAGRAM

Object is shown as a box at the top of the dashed vertical line. This vertical line is called
objects lifeline. The lifeline represents objects life during interaction. Each message is represent
by an arrow between the lifeline of 2 objects message contain message name arguments and
some control information

Sequence Diagram:

79
COLLABORATION DIAGRAMS

It represents the collaboration which is a set of object related to achieve

A desire outcome in collaboration the sequence is indicated by numbering the messages several
numbering scheme are available

Collaboration Diagram:

STATE DIAGRAM
80
 It shows the sequence of steps that an object goes through during its lifetime in response
to outside stimuli and message. The purpose is to understand the relationship existing between
statuses.

State Diagram:

COMPONENT DIAGRAM

81
 It describes the physical components in a design, these high level physical components
that may or may not be equivalent to many smaller component that is used in creation of your
application.

The components include the online reservation system are

 User screen
 TEST PLAN
 Graphical user interface
 Database

Component Diagram:

DEPLOYMENT DIAGRAM

82
 It is a graph of nodes connected by communication associations. Nodes may contain
component of online reservation system in deployment diagram are

 Ticket reservation
 Printer
 Passenger 1
 Passenger 2
Deployment Diagram:

CONCLUSION:

Thus the E-ticketing project for reserving and cancelling the reserved tickets was
designed and the UML diagrams were drawn and code has been created.

83
 SOFTWARE PERSONNEL MANAGEMENT SYSTEM

Problem Statement:

The current system does not provide a very good maintenance feature for a company ’s
employee records. Lack of filtering results in the redundancy of data and also slows down the
database. As a result, the queries from various employees are queued due to the less handling
capacity of the server and the database. This not only makes the employees to feel uncomfortable
but also reduces the chances of them visiting the system again and keeping track of their personal
records. Since the existing system’s database maintaining technique is older, many internal
server errors and table failures occur frequently – resulting in an inefficient overall system.

Proposed System:

The proposed system has unique features which keep the database and the server intact.
There is no problem of redundant data in the proposed system as data is cross-checked and
refined thoroughly to keep the database clean using various algorithms that act on the database
directly, instead of communicating through the server from a remote host. The server’s request
handling limit is also increased to a higher level, so that it can handle multiple requests at the
same time without decreasing the throughput. As the proposed system operates at much higher
rate than the existing system, it promises to be very effective and at the same it uses very less
resources due to the development in technology.

84
 UML DIAGRAMS

USECASE DIAGRAM:

Requirements Distribution
Client
Company

Required Software
Perfect Software Project manager

DataBase
Team Members
Verifying
Updating
Validation

Recording
Accessing
Modules
Software
Sub Modules Testing

Team Leader
TestingTeam

The Use Case diagram shows us how the database, server, various modules and the various
aspects of a software team interact to share the information in a distributed way. It also shows the
various processes the data undergo before reaching the intended destination machine or person.

CLASS DIAGRAM:
85
 Client <<Class Module>>
clientID : integer ProjectProposal Validation
clientName : text +client Req fro project clientID : integer forwards Validate for cost clientID : integer
design : integer clientInfo : text clientInfo : text
emailID : text oldID : integer
Validate the Project
propose() update()

Verified

Sends for development

Testing development
ProjectID : integer memberID : integer
teamID : integer Project submission projectID : integer -Process
member : integer status : text
completeprocess
test() report()
dbstore() test()

The Class diagram represents the various classes that can be identified in a system. In the above,
Client, Project Proposal, Validation, Testing, Development are the various classes that are
identified from the proposed system. It also represents the various attributes and the functions of
a particular class and also specifies the flow of data from one class to another class.

ACTIVITY DIAGRAM:

86
 GET THE PROJECT
FROM CLIENT

SPLIT INTO
MODULES

NO
IF ABLE TO
ALLOCATE

YES
ALLOCATE
THE TEAM

DIVIDE THE SUB

MODULES

NO
IF ABLE TO
FINISH

YES

START THE DEVELOPING

PROCESS

The Activity diagram shows the various activities performed by the parts of the system. The
diagram starts by getting the project from a client and then proceeds to the team allocation to
complete the project. It also shows how the development phase starts and ends.

SEQUENCE DIAGRAM:

87
 Client Company Project Manager Team Leader Testing Team Team members DataBase

Specification

Estimation of cost

Full Details
Updated
Acceptance

order to do project
Acceptance

Split into modules

Updated

Allocating

Processing
Updated

Spilt into sub modules

Updated

Assigning

Acceptance
updated

Product for Testing

Testing Updation

Comptele Sub modules

Complete modules

Complete Project

Reporting

Delivery

The Sequence (Interaction) diagram shows the various interactions between the various aspects
of the system. It shows the flow requests from a source to the destination. It shows how and
where the request is processed and what kind of results that are produced.
88
COLLABORATION DIAGRAM:

1: Specification
3: Full Details 6: order to do project
Client Compan Project
y Manager
2: Estimation of cost 11: Processing 7: Acceptance
13: Spilt into sub modules 5: Acceptance 22: Complete Project 23: Reporting
24: Delivery

10: Allocating
15: Assigning
Team Team
Leader members
16: Acceptance
4: Updated 21: Complete modules
9: Updated
20: Comptele Sub modules
12: Updated
14: Updated
18: Product for Testing
17: updated
Testing
Team
DataBas
e 19: Testing Updation

The Collaboration diagram is just a detailed and a natural view of the Sequence (Interaction)
diagram. All the aspects of the system are represented as components and the request-response
system is numbered in order to clearly classify them system and its features.

STATECHART DIAGRAM:

89
 Start

SoftwareOr
dering
Event
take ORDER

get
speifications

develop Test NILL ERROR Deliver End

Product Product Product

If any ERROR
Transition
Debug

The State Chart diagram shows the various states of a system. It explains the various states
and the phases of a Software development processes and it mainly focuses on how the projected
is started and how it is delivered to the client.

PACKAGE DIAGRAM:

90
 BOUNDARIES

ENTITY DATABASE
SPECIFICATION

SOFTWARE ORDER
PRODUCT

CUSTOMER

CONTROL
PROJECT TEAM TEAM MEMBER
MANAGER LEADER

The package diagram is nothing but a collection of all the packages in a system or the collection
of all the classes in the system. In the above package diagram, the flow of control from one
package to another package is shown clearly. It also shows the classes and packages inside a
specific main package and also the relationship under which they are clubbed together.

COMPONENT DIAGRAM

91
DEPLOYMENT DIAGRAM:

PROJECT DATABASE
PRINTER

CLIENT
WORKSTATION3

APPLICATION
SERVER

CLIENT
WORKSTATION2

CLIENT
WORKSTATION1

92
USER INTERFACE LAYER:

Login Form:

MDIForm:

93
CONCLUSION:
Thus the software personnel management system to maintain the detail of employee was
designed and the UML diagrams were drawn.

94
 CREDIT CARD PROCESSING SYSTEM

PROBLEM STATEMENT

Credit Card Payment Processing is nothing but the processing of the credit card payment
involving verification of card and the consequent acceptance or rejection of the purchase made
through that card. A credit card issues is a bank or credit union who offers credit card, the card
holders is responsible for sending payment to merchants for purchase made with credit cards
from that bank.

Credit card issues need to help of payment processing network like visa and
MasterCard. The processes involved are the following:

 The user needs to wait in bank premises to debit money from his/her account.
 It consumes more time to complete his/her process.
 The user can retrieve amount only from that particular bank where he/she is holding
his/her account.

SOFTWARE REQUIREMENTS SPECIFICATION

SCOPE:

The system is used to retrieve amount from the user account. In credit card user can
pay money in easy manner since it is not a time consuming process. The user can pay amount in
any place such as shopping, booking tickets online and so on.

FUNCTIONAL REQUIREMENT:

 Processing banks or merchant banks are financial institutions, members of a visa and
master card contract with merchants to accept credit payments for their product server.
o Card holder is an authorized user of a credit or debit card.
o Card issuers are financial institutions that are member of visa and master card
contract .

95
 o Payment processor is an organization that has contracted with an acquiring bank
to provide merchants with card payment processing of the acquirer.
o A service provider can be any third party provides a services used in the card
payment
o Merchant is a business or profit organization that has contracted with an acquiring
bank .

PROJECT DESCRIPTION:

Card Holder:

Card holder is an authorized user of a credit or debit card.

Card Issues:

Card issuers are financial institutions that are member of visa and master card
contract with card holders.

Acquiring Bank:

Processing banks or merchant banks are financial institutions, members of a visa

and master card contract with merchants to accept credit payments for their product server.

Payment Processor:

Payment processor is an organization that has contracted with an acquiring bank to

provide merchants with card payment processing of the acquirer.

Merchant:

Merchant is a business or profit organization that has contracted with an acquiring

bank or a merchant processor to accept card payment.

Service Provider:

A service provider can be any third party provides a services used in the card
payment transaction process, pos terminals, payment gateways, web hasting, SSL
certificates, shopping cards etc.

Transaction Processing Stage:

The processing of the card payments may vary depending on particular procedure
employed by the issues, acquires or merchant but they all involve the following stages:

96
 Authorization:

Authorization is the process by which the card issues approves or declines a card
transaction.

Authentication:

Authentication is the process of establishing the validity of the credit or debit card
account information provided by customer.

Clearing:

Clearing is the process through which a card issues exchanges transaction information
with processing bank. Clearing and settlement occur simultaneously.

Settlement:

Settlement is the process through which card issuing bank exchange funds with
processing bank to cleared transaction.

UML DIAGRAMS:

USE CASE DIAGRAM:

Actor Customer: Customer is an actor who purchases the product.

Shopper: Shopper views and updates the customary goods.

Customer Services: It’s the service for the customer and checks the status with product
information.

Acquirer: A licensed member of master card that screens and accepts merchants into its credit.

View Order Items: Customer views the item is shop.

Search Details: Customer searches item which they needed.

Pay by Credit: Customer pays the bill by credit.

97
 cus tomer authetication

pay by credit
s hopping

cus tomer

view update shopping card

update s umm ary

viewcustomering item

cus tomer s ervice

check order details

product information

<<include>>

placeorder calculate total

credit card rejects

proces s trans action

financial s ettlement

acquirer

is s ue the order
is s uer

CLASS DIAGRAM:
98
 Customer
customer-name : string
bill_up : text
address : text discount
mail_id : string
good rating : boolean
credit_rating : string

add()
modify()
remove()

Items
item_id : int
Descriptor : string
price : double

add()
remove() credit card
credit no : int
valid_from : int
valid_to : int

verify_details()
add()
modify()
delete()

shopping card
product : double
quantity : double
price : double

add()
modify()
delete()

ACTIVITY DIAGRAM:

99
 The states are activities representing the performance of operations and the
actions are transferred and triggered by the completion of the operations. It is used to model the
entire business.

customer purchase
the product

customer strips
the card

POS device captures

card information

POS device transmit the Is card valid

information to acquiring bank
yes

merchant bank transmit through consorting Invalid

(visa,master card) to issuer bank credit card

Issuer bank approves

declines the transaction

POS device prints approval

declined information

merchant presents
the receipt

customer leaves with

the goods and receipt

STATE CHART DIAGRAM:

100
 customer POS device captures
card strip card information

POs device transmission card information

to acquiring bank(merchant bank)

merchant banks transmits data through card

consorting(visa,master card) to issuer bank

POS device prints approval Issuer bank approves/declines

declined information the transaction

INTERACTION DIAGRAM:

SEQUENCE DIAGRAM:

customer pos system require bank issue bank

credit card
capture the card information

trasmits to the requiring bank

transmit data through card
approval the transition
sends the approval infprmation

sends the approval transaction to pos device

prints the approval

COLLABORATION DIAGRAM:

101
 2: capture the card information

1: credit card
customer pos
system
8: prints the approval

7: sends the approval transaction to pos device

3: trasmits to the requiring bank

5: approval the transition

6: sends the approval infprmation

issue bank
require
bank
4: transmit data through card

COMPONENT DIAGRAM:
POS device Issuer Bank Service

Card consortion(visa,master card)Service

Accessing Bank Services

DEPLOYMENT DIAGRAM:

102
 <<TCP/IP>>

POS Server
device

<<TCP/IP>>

Server
DBMS

<<IPX>>
PC

<<TCP/IP>>

Gate
way

USER INTERFACE-LOGIN FORM

CUSTOMER DETAILS ENTRY

103
SUPPLIER DETAILS DISPLAY

PRODUCT
DETAILS ENTRY

104
SALES DETAILS ENTRY

CONCLUSION:

Thus the credit card processing system for the payment of amount and verification was
designed and the UML diagrams were drawn and code has been created.

105
 FOREIGN TRADING SYSTEM

PROBLEM STATEMENT:

Foreign trading system is used in the effective dispatch of currency trading to all applicants.
This system adopts a comprehensive approach to minimize the manual work and schedule Resources. The
system also forwards necessary details to the trading authorities for its formal Verification. The foreign
trading system effectively adopts an online currency transaction of documents and data of the trading
partners with the relevant country and the clients.

SOFTWARE REQUIREMENTS SPECIFICATION

INTRODUCTION:

Foreign trading system is an interface between the trader and the authority responsible for the
issue of currency trading. It aims at improving the efficiency of the issue of the trading system.

PURPOSE:

If the entire process of trading system is done manually or the transaction involves a issue of
Non-online trading. Then it would take several databases and servers to interact and maintain a long
process time. To meet these demands an online currency foreign trading system was designed.

SCOPE:

 The system provides an online interface to the user where they can perform secured trading
interface.
 The authority concerned with the issue of trading can use this System to reduce work load.
 Provides a easy access across other web servers
 Transfer of data between the country authority and verification persons.
 The trader will know the effect and status of online application.

TRADER: They are people who desire to trade the currency and marketing verifier.

TRANSACTOR: This person has certain privileges to add on the status of marketing.

CONSTRAINTS:

 The trading persons require a computer to submit their information.

106
  The web world requires constant monitoring for security.
 The trading has to be in secured software field to transact the currency.

UML DIAGRAMS:

Use Case Diagram

Registration with Forex System

Bank Database Forex Rates Database

Login Details

Buy Client Database

Client Forex
Administrator

Sell

Check Balance

The use diagram in foreign trading system includes two actors called Client and forex admin.
Our use case consists of elements that lie inside the system and are responsible for the
functionality and behavior of the system. Our system involves use cases such as Registration with
the forex system, filling the login details, buy and sell to check balance. The client database, bank
database and forex rates database contains the details for an effective currency transaction.

The client database informs about the client details who are involved in the system.

The bank database contains the account information and balances of the required client in the
system.

The forex database contains the rates of the currency to be transacted to the other end of the
client.

107
Class Diagram:

ForexSystem
UserID : Integer Balance
Login
Username : String Balance : Integer
Username : String
Username : String
Password : String
Buy()
Sell() CheckBalance()
Authenticate()
Balance() Username()
Exit()

Buy Sell
Currency : Integer Currency : Integer
UserID : Integer UserId : Integer
Balance : Integer Profit : Integer

CheckBalance() CheckBalance()
UpdateBalance() GetProfit()
CheckFinance() UpdateBalance()
Exit() CheckFinance()

The use case “registration of the forex system ” is mapped to classes called client and forex
administrator. Similarly, the other use cases are mapped to classes, the action performed by each class
will get mapped to behaviors of the class attributes. Multiplicity denotes the number of objects from one
class that relate to a single object in an associated class, and is represented using multiplicity indicators.
The login class requires the username and password of the client to access the forex system and
authenticates the client details to the server running the forex system. The brief description of the client is
defined in the forex class. The buy and sell methods denote the effective transaction between the two
traders and also checks the balance in the account. Once the transaction is complete the balance class
gives the balance details in the client account and username detects the user address of the current client.

108
Activity Diagram:

Regis ter with

Forex System

Login Details

Buy
Sell

Currency
Transcation

Check Criteria Display Insufficient

Finance

Complete
Transcation

The forex system registers the login details of the client in accordance with the client
account details and the registers the current transaction.

The login details processes either buy or sell condition for currency transaction. There in checks
the criteria ,if the sufficient finance is not available the process terminates, else the process
completes its transaction with sufficient finance.

109
Sequence diagram :

MAIN PROCESS SEQUENCE DIAGRAM:

client transaction forex admin

system
registration

update database

authenticate user

buy/sell

send request

respond

display response

request balance

invoke balance

display balance

110
 BUY/SELL SEQUENCE DIAGRAM:

client transaction Forex Admin Database

system

Buy/sell
Send request

verify database

respond

Display response

Collaboration diagram:

Main Process Collaboration:

111
 1: Registration
4: Buy/Sell
8: Request balance
Client Transaction
System
7: Display Response

3: Authenticate user
6: Respond

10: Display balance 2: Update Database

5: Send request
9: invoke balance

Forex
Admin

Buy/Sell Collaboration:

1: Buy/sell
transaction
client system

5: Display response

2: Send request

3: verify database
Forex Database
Admin
4: respond

State Chart Diagram:

112
 Register with
Forex System

Login
Details

Buy/Sell

Check
Balance

It represents the sequence of states .It includes states with registration with the login details, the
buy/sell states and the states to check details of the balance.

Component Diagram:
Contains all
informati...

Bank
Database Contains
informati...

Client Transacation Forex Forex Rates

System Admin Database

Client
Database

Component Diagram describes the physical component .The various component are client,
transaction system, forex admin and the databases .The databases include the bank database, forex
database and the client database.

Deployment Diagram:
113
 Client
Data...

Client Transca Forex

ti... Admin

Forex
Rat...

Bank
Data...

It is a graph of nodes connected by communication association such as client, transaction system,

the forex admin and the databases

CONCLUSION:

The effective dispatch of currency trading to all applicants using foreign trading system was
designed using UML diagram and the code has been created.

BPO MANAGEMENT SYSTEM

PROBLEM STATEMENT:
The objective is to develop software for BPO management system. Business process outsourcing
(BPO) is a subset of outsourcing that involves the contracting of the operations and
responsibilities of specific business functions (or processes) to a third-party service provider.
BPO management system is used to effectively manage the business activities of a BPO
organization. This system adopts a comprehensive approach to minimize the manual work and
schedule resources, time in a cogent manner. It is designed for hiring any company, that is , it
is generalized system for business process management. The core of the system is to maintain
employee details and customer details and company details.
Employee details include id, name, address, shift timings, category (based on the field of
expertise), number of calls attended and salary details.

HARDWARE REQUIREMENTS:
Processor: Intel Pentium IV-2.0 GHZ (Minimum)
Hard Disk: 40 GB
RAM: 512 MB
DVD RAM: 1 nos.

114
SOFTWARE REQUIREMENTS:
OS: Windows XP/Vista/7
Front End tool: Rational Rose Enterprise Suite
Back End tool: MS Access

 
 
 

USE CASE DIAGRAM:

115
 Browse catalog

Searching for profile of company

Details of company Server

Client
Give details of company

Calls the BPO

Salesperson
Enquires about the product

Owner Select product to purchase

Provides order and quotation for

selected product

Shipping information

Returns the requested product

Pays and update the transaction

Report the fault in product

Corrected fault product

Provides the product

Update the product details

ACTIVITY DIAGRAM:

116
 Browse catalog of
company profile

Call BPO

Enquiry about
product

Select the particular Not satisfied Purcahsed

product denied
Satisfied

Provide order
and quotation

Processing the
product

Deliver product

Fault

Report that
Not fault product

Update
transactions
Corrects the
Product

Update
Products details

CLASS DIAGRAM:

117
 Client1
Name : String
Adress : String
Phone : Longint
request
retrieve Mobile : Longint

Clientid()
Browse()
Select()
Order()
product

company details
Salesperson1
Bankaccount system Name : String
Server1 Address : String
Account-no : String
Gender : String
Branchname : String Connect_type : String Phone : Longint
Account : Longint Connect_topo : String Mobile : Longint
Last deposit : Date issue No-of-System : Int
Acc_Speed : String Product_requirements()
Amount()
Process_product()
Issue() Transaction() Process_delivery()
Update_product()

Owner1
Name : String
Address : String
Mobile : Longint
details
Phone_no : Longint

Productdetails()
Companydetails()

SEQUENCE DIAGRAM:

118
 Client Salesperson Owner Server

Searching Company profile

Returns details

Company details
Give product details
Enquiry about product
Product details

Selects the particular product

Provides order and qoutation
Accepts quotation

Process for product

Returns requested product

Update transaction
Updated

Returns fault product

Correct the product

Provides product

update product details

Updated successfully

COLLABORATION DIAGRAM:

119
 10: Process for product
15: Correct the product
5: Enquiry about product
7: Selects the particular product
8: Provides order and qoutation
Client 14: Returns fault product

Salespers
6: Product details on
9: Accepts quotation
11: Returns requested product
16: Provides product

1: Searching Company profile

4: Give product details 12: Update transaction
17: update product details

2: Returns details
3: Company details 13: Updated
18: Updated successful y

Owner

Server

STATE CHART DIAGRAM:

120
 Search company Calls BPO Enquiry about
details products

Process Provides order Select the

the product and quotation particular product

Provides Update
the product transaction

Correcting fault Reporting product

product to be fault

Return back Update product

the product details

COMPONENT DIAGRAM:

121
 Client.obj Client.cpp Client.exe

Server.exe
Server.obj Server.cpp

Salesperson.cpp
Salesperson.obj Salesperson.exe

Owner.cpp Owner.exe
Owner.obj

DEPLOYMENT DIAGRAM:

122
 <<TCP/IP>>
PC Applicat
i...

<<TCP/IP>>

Databas
e server

Conclusion:

Huge reduction in printing, dispatch costs. Seamless process that is fully integrated
ensuring better quality of service to customers. Cost reductions by automation of upload
processes from clients; automatic routing of documents to operators using OCR. Documents as
well as the status of process is accessible quickly and from anywhere to BPO management as
well as customers. Security of documents as they are stored in digital form. Enriched experience
for users as they can search for documents and process them online.

E-BOOK MANAGEMENT 

PROBLEM STATEMENT:

123
  The aim is to develop and maintain E-book in the website.All the process
involved in e-book are computerized there are many website offers the e-
book.And the website could receive the copyright from the author and they should
pay certain amount to get copyrights.
 When the website receives the copyright he becomes as vendor.And the purpose
of vendor is to place certain amount for the book and attain profit.

 And the customer searches the author and book name and if the customer finds
the book in certain website .Then the customer checks whether the author details
and specifications of book then customer can download the book.

 The customer has to verify if the download charges cost or free .If cost then
customer uses his credit card  and download the book.On the vendor side he
checks the card number and asks certain confidentiality questions to transfer the
money and the customer need to specify the email id,username are to be
submitted.

 The vendor checks the card number and amount verifies the user name and thus
the money is transferred successfully to the vendor.And the customer can
download the book. 

SOFTWARE REQUIREMENT SPECIFICATION:

INTRODUCTION:

 The e-book management  system is to automate all the books in the

website. Generally it includes order processing and account
management.It provides the facility to the customers to purchase (i.e
download) the books without going shop.

PURPOSE:

 Every area of human interactions was invaded by various software

systems, such as real time ,business ,simulation,web bared etc..It also
includes management of e- book.
 This project focuses on the efficient and controls on the transactions of
books in website.It provides many benefits than doing the same thing in
manually.
 communication with suppliers customers abd other related organizations
will be more successfull. The main purpose is to provide easy shopping
facility and easy selling facility.

SCOPE:
124
  The name of the SRS is the management system of e-book. The software
provides both the customer and publisher is PIN number which is unique.

                            This provides the following facilities to the online customers:

 Facility easy shopping online any where.

 Provides information about the books.
 Can reserve or order if the particular book is not available.
 Customers are provided with upto date information on the book available.
 Provides backup facility.

                           The e-book management will not provide the following facilities to the

customers:

 The books downloading cannot be changeable when once confirmed.

 If the pin number is invalid, deny the request of customer.
 The e-book management system provides following facilities to the
publisher:
 Provides complete information about customers.
 Can avail the facility of e-mail correspondence.
 Provides on-spot payment through customer credit card PIN number.
 The main scope of this system is to provide easy assistance to both the
customers as well as the publishers with proper information.

DEFINITIONS, ACRONYMS AND ABBREVIATIONS:

IEEE-The institute of electrical and electronic engineering, Inc.

CUSTOMER- The person who downloads the book.

PUBLISHER- The person/dealer/company who sell book on website.

PIN NUMBER- The unique id given to either customer and publisher who   acess data in site.

AUTHOR - One who sells copyright of book.

REFERENCES:
125
  Online e-book shopping websites.
 This SRS is based on IEEE recommended practice for software
requirements specification.

OVERVIEW:

 It provides the complete overview of specifications requirements

documentation for the product-E-book management system.
 The entire SRS is documented in view of both the customers and the
publishers and the transaction of books between them.

OVERALL DESCRIPTION:

 In this module we define the overall description of the software e-book

management in the website.

PRODUCT PERSPECTIVE:

 It provides good and easy graphical user interface to both new, naïve  as
well as experienced users.

PRODUCT FUNCTIONS:

 The e-book management systems generally performs the following operations:

o Publisher buys copyright and makes the book available in website.

o User searches for the required book in website.

o Publishers verifies book details and asks for download payment.

o Customer pays through credit card.

o Publisher record sales.

USER CHARACTERISTIC:

o Should be familiar with internet.

o Should know English.

o Should be able to use and do according to the graphical user interface.

o The user[customer] should be well trained and should be the relevant

documentation PIN number.
o The customer should be able to follow simple instructions given by system.

126
GENERAL CONSTRAINTS:

o The  browser should support java.

o The browser should be able atleast netscape navigator v4.0 or internet explorer.

o Data encoding scheme:ASCII character.

o Total available memory for programming logic, tables etc as specified in this
document should not be exceeded.

ASSUMPTIONS AND DEPENDENCIES:

o The product assumes that the user don’t opt for the same product number
simultaneauosly.
o It should be accesible in real time.

SPECIFIC REQUIREMENTS:

EXTERNAL INTERFACE REQUIREMENTS:

User interface:

                The system users are:

o Publishers
o Customers

PUBLISHERS:

 The publisher log on to the website with administrator name and

password. Administrator(i.e password) can do any transactions as well as
editing and all details inside it such as adding, deleting, edting a new user
they are the one who do transactions with customers.

CUSTOMERS:

 They have to enter username and password and click on ’login ’ button.if the
customers makes any mistake he will be asked to do the process continuously
until he enters correct one.
 when the customer wants to do any download he has to click main menu. The
transaction will occur between user and publisher.

127
HARDWARRE INTERFACE:

o Publishers PC
o Customers PC

o RAM should be or greater than 120 mb.

o The processor speed should be greater than 400mhz.

SOFTWARE INTERFACE:

                      The system requires the following software and for other requirements:

o HTML,JDK and html editor web interfaces.

o Server(windows 2000,apache etc..).

COMMUNICATION INTERFACES:

o Local intranet and internet protocols.

o Supports all HTTPS,SMTPS and POP3 services.

FUNCTIONAL REQUIREMENTS:

 Basically there are modules which are source of input, processing of inptut,to
give the relevant output.

Source of input are:

                      Customers and  publishers.

The processing is:

Customers:

o Searches the book.

o Request to download.

Publishers:

o Manage the transactions.

Output:

o It is based on the transactions between the user and publisher.

128
Performance requirements:

o Good working PC with all the requirements as stated in the hardware interfaces.
o The response time for menu changes will not be more than 3 seconds.

Design constraints:

o The browser should support java.

o Java programming environment has been used for secure and protection from viruses and
other threats like hacking of passwords by hacker.

                   
 
 
 

         

129
USECASE DIAGRAM:

introduction of author

index of book
server

detail of notes

sels the copy right of book

author

buys the copy right and make it

available in website

customer
search author name

verify the book

check memory

publisher

download

sumit credit card number

colect the amount

download successfully

130
            
 USECASE DIAGRAM:

 Introduction of author:

The author name and the description of the author are needed to be specified in
this section.

 Index of book:

The index of the book specifies the content in the book and page number is
specified.

Detailed notes:

Then the detail notes of the book can be viewed.

Sells the copyright of the book:

  The author sells the copyright to the publisher. To publish on the website.

Buys the copyright makes available in net:

           Then the vendor buys the copyright from the and pays certain amount to author
and publish on his site.

Search author name:

The customer searches the author name according to his/her requirement.

Verify the book:

IF THE CUSTOMER FINDS THE REQUIRED BOOK THEN VERIFIES THE BOOK.
CHECK THE MEMORY :
  THEN CUSTOMER CHECKS THE SIZE OF BOOK IF NEEDED TO DOWNLOAD .

Download:

                       Then the customer can download the required book.

Submit the credit card:

If the download is cost then pays the amount using credit card.
131
Collect amount:

                       Then the vendor collects the amount from the customer.

Downloads successfully:

                        Then customer downloads the book successfully.  

 
 
 

132
ACTIVITYDIAGRAM: 

author sells publisher buys upload in web

server process
detail

fill info form request to customer get

document detail

credit card
payment
check the form

customer fills

payment successfully
received downloaded

133
ACTIVITY DIAGRAM: 

Author sells:

       The author sells his authority for the book and the vendor pays certain money
and buys the amount.

Upload the book:

   Then the publisher buys the book and uploads in his website.

Customer gets details:

       The customer searches for the book in server and gets detail.

Request to download:

       Then customer finds the required book and downloads the book.

Fill information in form: 

 Then if download is cost then he fills the form.

Credit card payment:

       If this is credit payment then check the form.

Payment is provided:

      Then the payment for the book is paid by card.

Successfully provided:

      Then he downloads the book successfully.  

 

134
CLASS DIAGRAM:

servers
book id:integer provibes
book name:string
author name:string

get book id()

issue get book name()
get author name()

provides

publishers authors
name:string name:string
email:string email:string

get name() get name()

get id() get id()

checker

customers
name:string book
email id:string name:string
credit card :int book id:int

get name() get book name()

get id() get book id()
get credit card ()

135
CLASSDIAGRAM: 

Server:

          The server is used to store the details of the author ,book,author name.And all
the book size and all necessary requirements are stored in server.

Author:

          The author name and email and version of the book under his class are specified
other details of author are stored in these class and the details are stored in the server
class

Publisher:

          The publisher buys the copyright from author and publishes on his site and he
needed to specify user name and emailed and pays some amount.

Book:

          The book details are maintained if the customer searches the book based on the
search server results the book. here the book name and book id are specified.

Customer:

           The details of the customer like name ,emaild,credit card number are specified.  
 
 
 
 
 
 

136
SEQUENCEDIAGRAM:

author publisher server customer

sell the authority of book

return ok
request to upload book

successfully uploaded
enquire about book

return requstede one

request to download

enquire about credit card

pay amount

successfully downloaded

137
SEQUENCE DIAGRAM: 
   Author: 
     The name of author and the detail of book are specified in server. And
sells copyright to vendor.
Publisher:
       The vendor buys the book for certain amount and publish in website.
Server:
           The server stores all the detail of the book and the author details are specified.
Customer:
   The customer details are stored in this section and customer searches the book
details.
Sells the authority of book:
   The authority of the book is sold by the author to vendor.
Return ok:
     The publisher pays certain amount for the book and buys from author.
Request to upload the book:
       Then the book is uploaded in the website.
Enquires about author:
       The customer can search for the author and searches the book.
Returns the required book:
       Then required book is selected from the list of books.
Enquires about credit card:
          The credit card of the customer is checked by the vendor.
Pays the amount:
   The cost of the book is transacted from user ’s account to vendor.
Successfully download the book: 
  Then the customer can download the book successfully.  
 
 

138
COLLABORATION DIAGRAM:

1: sell the authority of book

author publisher

2: return ok

4: successfully uploaded
8: enquire about credit card
10: successfully downloaded
7: request to download
3: request to upload book 9: pay amount

5: enquire about book

server
customer

6: return requstede one

139
COLLOBORATION DIAGRAM:
  author:

The author sells his authority to the publisher.

Publisher:

The publisher uploads in the website.

Server database:

The server gives the details about the book,publisher,author.

Customer:

The customer searches about the book amd download it.

 
 
 
 

140
STATE CHART DIAGRAM:

<<request form>>

another publisher request to

customer accept upload

<<send>>

server update
& upload

customer enquire server requested book is

about bookdetail provides obtained

publishers
detail

<<checks>>
customer pays publisher receive
through card checker payment

<<download>>

customer downloads
successfully

141
STATECHART DIAGRAM: 

Author sells authority:

       The author sells his authority to vendor with some price.

Publisher accepts:

       The publisher accepts authority and buys the book.

Request to upload the book:

       The publisher uploads the book in his website.

Customer enquiries for the book:

       The customer searches for the book and finds the book.

Server provides:

The server provides an index of book then customer can pick his choice.

Publisher details: 
The publisher provides the detail for all the book downloads.

Customer pays through card: 

 The download is cost then he pays through card.

Publisher checks:

   The publisher checks the detail provided by customer is true.

Receives payment:

       Then publisher receives the payment.

Downloads successfully:

Then customer downloads the book successfully.  

 

142
LOGICAL ARCHITECTURE LAYER
UI

Web Text
Login Frame Book Details

Domain

Service Load DB

Publisher uploads in Customer searches

Web for book details

Payments
Grant Access
Credits <<Interfaces>> Customer download
Payment Credit book
Authorization

Technical Services

Persistence Server
DB Facade DB Server SOAP

143
TECHNICAL SERVICES

Technical Services

Persistence Server
DB Server
DB Facade SOAP

DOMAIN LAYER:
Domain

Service Load DB

Publisher uploads in Customer searches

Web for book details

Payments
Grant Access
Credits <<Interfaces>> Customer download
Payment Credit book
Authorization

144
USER INTERFACE LAYER

UI

Web
Text

Login Frame Book Details

145
Component Diagram:

146
server.cpp server.obj server.exe

publisher.cpp publisher.obj publisher.exe

customer.cpp cutomer.obj customer.exe

author.cpp author.obj author.exe

card.cpp card.obj card.exe

database.cpp database.obj database.exe

147
COMPONENT DIAGRAM:

Server:

The server gives about the details about author, book.

Author:

The author sells his authority to the publisher

Server database:

The server gives the details about the book, publisher, and author.
Customer:

The customer searches about the book and download it.

Card:

The customer downloads using his/her credit card

148
DEPLOYMENT DIAGRAM:

pc <<TCP/IP>>

database
server

<<TCP/IP>>

<<TCP/IP>>
application
server

149
DEPLOYMENT DIAGRAM: 

Pc:

      The pc contains the detail about the book .The customer apply the required form
for book to download.

Application server:

     This is a deployment that shows a mapping process. The application server
requests the available number of books in server. And these is used associate with the
details of the book.

Data server:

     The data server contains the detail of book and the amount of the book and how
many copies are available are specified in these server.  

Conclusion:

Thus the E-BOOK management system using the use case diagram, class diagram,
sequence diagram, collaboration diagram, state chart diagram, component diagram, deployment
diagram are implemented successfully.

150
 RECRUITMENT SYSTEM
PROBLEM STATEMENT:
1. Recruitment system was developed in companies for interviewing
the employee.

2. The system could contain the following features.

3. The system should provide information about queries, database etc.

4. The system explains about the employees attending interview and HR aking

query to the employee.

5. The following process takes place when recruiting the employee.

6. Employee gives details to the interviewer.

7. Then the employee wait for the result.

8. Finally employee quit from process.

9. The details about the employee will be updated in database.

SOFTWARE REQUIREMENT SPECIFICATION

INTRODUCTION :

Viewing available jobs, or applying for the job at the agency is currently done
manually where in the job seekers has to go to the agency and check the available jobs at the
agency. Job seekers check the list of jobs available and apply the job if the job is not available
otherwise it is of waste for the job seeker to come to the agency to come to check for the job if the
job seeker doesn’t get the job. Then the agency will show available jobs for the job seeker for his
qualifications and the then updates the jobs database.

PURPOSE:

The purpose of Software Requirements Specification (SRS) document is to

describe the external behavior of the Online Recruitment System. Requirements Specification
defines and describes the operations, interfaces, performance, and quality assurance requirements
of the Online Recruitment System. The document also describes the nonfunctional requirements

151
such as the user interfaces. It also describes the design constraints that are to be considered when
the system is to be designed, and other factors necessary to provide a complete and comprehensive
description of the requirements for the software. The Software Requirements Specification (SRS)
captures the complete software requirements for the system, or a portion of the system.
Requirements described in this document are derived from the Vision Document prepared for the
Online Recruitment System.

SCOPE:

The Software Requirements Specification captures all the requirements in a single

document. The Online Recruitment System that is to be developed provides the members with jobs
information, online applying for jobs and many other facilities. The Online Recruitment System is
supposed to have the following features.

OVERVIEW:
The SRS will provide a detailed description of the Online Recruitment System. This
document will provide the outline of the requirements, overview of the characteristics and
constraints of the system.

OVERALL DESCRIPTION:

1. PRODUCT PERSPECTIVE:

The Online Recruitment System is a package to be used by agencies to improve the

efficiency of business. The Online Job Portal System to be developed benefits greatly the members.
The system provides jobs catalog and information to members and helps them decide on the jobs to
apply. The Admin can keep the jobs catalog updated all the time so that the members (Job seekers
and the agencies) get the updated information all the time.

PRODUCT FEATURES:

Jobseekers Features :

 Advanced job search functions

 Register for a jobseekers account
 Build your profile
152
 Build online CV
 Build multiple cover letters
 Upload Word CV
 Paste your Word CV
 Enable/Disable your CV's
 Receive jobs via email
 Enable/Disable email alerts
 Save jobs in your Jobs Inbox
 Apply to job vacancies instantly
 View previous applications
 Upload personal photo
 Easy to use interface
 Retrieve login information via email.

Agencies Features :

 Advanced CV search functions

 View detailed bills.

 Purchase advertising credits via credit card.
 Enable/Disable CV database access.
 Advertise job vacancies instantly.
 Edit/Delete job vacancies.
 Upload company logo.
 Purchase jobseeker contact details.
 Save jobseeker CV's in CV Inbox.
 Hide contact details on job postings.
 Specify application rules for each job posting.
 Receive application alerts via email.
 View/Delete applicant CV's.
 View applicant cover letters.

153
Administration Features :

 Multiple administration accounts

 Live statistics
 Create resources
 Create multiple job categories with subcategories
 Create countries with regions and cities
 Specify working hours, contracts and experience levels
 View/Edit/Delete jobseekers
 Email individual jobseekers
 View/Edit/Delete employers
 Email individual employers
 Upgrade/Downgrade agency accounts
 Upload company logos
 View jobs for each agency
 Add/Edit jobs for each specific agency
 Advanced mailing system

 Advanced content management system

 Add unlimited pages of content

PRODUCT FUNCTIONS:

The Online Recruitment System provides online real time information about the jobs available in
the agencies and the user information. The Product functions are more or less the same as
described in the product perspective. The functions of the system include the system providing
different type of services based on the type of users [Member/Admin].

 The member should be provided with the updated

information about the jobs catalog.

 Provisions for the members to apply the job they want, if all

the other required rules hold good.

154
 The member is given a provision to check his account information and change the account
information any time in the given valid period.

 The members are provided with the jobs available roster and

allowed to apply job, which they want.

 The admin can get the information about the members who

have advertised jobs.

 The admin can get the information about the members who

have applied jobs.

 The admin is provided with interfaces to add/delete the jobs

available in the job catalog.

 The job seeker when complete the applying, the due to be paid by the agency must be calculated
and the information about the agency and the due amount is sent to the billing system.

 The system uses the University information security

requirements to provide the login facility to the users.

1.Operating Environment :

There should be proper commitment of Hardware and communication

gears should be equally coupe with each other, it may help to prevent
many inconveniences during the Browsing. Those requirements have
been Explained later headings. (Please refer to Performance
Requirements on Heading 5.1).

 Web Browsers [Java Script enabled]

 Google Chrome

 Internet explorer

 Mozilla Firefox

 Operating Systems and versions.

 All the Windows OS versions

155
.

USER CHARACTERISTICS:
The users of the system are members and the admin who maintain the system. The
members are assumed to have basic knowledge of the computers and Internet browsing. The admin
of the system to have more knowledge of the internals of the system and is able to rectify the small
problems that may arise due to disk crashes, power failures and other catastrophes to maintain the
system. The proper user interface, user’s manual, online help and the guide to install and maintain
the system must be sufficient to educate the users on how to use the system without any problems.

CONSTRAINTS:
The information of all the users must be stored in a database that is

accessible by the Online Job Portal System.

 The Online Job Portal System is connected to the computer and is

running all 24 hours a day.

 The users access the Online Job Portal System from any computer

that has Internet browsing capabilities and an Internet connection.

 The billing system is connected to the Online Job Portal System

and the database used by the billing system must be compatible

with the interface of the Online Library System.

 The users must have their correct usernames and passwords to

enter into the Online Job Portal System.

ASSUMPTIONS AND DEPENDENCIES:

 The users have sufficient knowledge of computers.

 The Computer should have Internet connection and Internet server

capabilities.

 The users know the English language, as the user interface will be

156
provided in English

 The product can access the member’s database.

SYSTEM FEATURES:

Jobseeker :
 Advanced job search functions.

 Register for a jobseekers account.

 Build your profile.

 Build online CV.

 Build multiple cover letters.

 Upload Word CV.

 Paste your Word CV.

 Enable/Disable your CV's.

 Receive jobs via email.

 Enable/Disable email alerts.

 Save jobs in your Jobs Inbox.

 Apply to job vacancies instantly.

 View previous applications.

 Upload personal photo.

 Easy to use interface.

 Retrieve login information via email.

 Forward job vacancy to a friend.

Agency :

157
 Advanced CV search functions.
 Purchase advertising credits via credit card or invoice.
 Enable/Disable CV database access.
 Advertise job vacancies instantly.
 Edit/Delete job vacancies.
 Upload company logo.
 Do payment for jobseeker contact details.
 Save jobseeker CV's in CV Inbox.
 Hide contact details on job postings.
 Company logo displayed by job postings.
 Specify application rules for each job posting.
 Receive application alerts via email.
 View/Delete applicant CV's.

 View applicant cover letters.

Administration :

 Multiple administration accounts

 Live statistics
 Accept payments.
 View/Edit agencies account balance.
 Send account balance report via email to agencies.
 Create resources
 Create multiple job categories with subcategories
 Create countries with regions and cities
 Specify working hours, contracts and experience levels
 View/Edit/Delete jobseekers
 Email individual jobseekers
 View/Edit/Delete agencies
 Email individual agencies
 Upgrade/Downgrade agency accounts
 Upload company logos
158
 View jobs for each agency
 Add/Edit jobs for each specific agency
 Advanced mailing system.
 Advanced content management system
 Add unlimited pages of content
 Customize the job board to meet your exact requirements

Specific Requirements
This section describes in detail all the functional requirements.

Functionality
Logon Capabilities

The system shall provide the users with logon capabilities.

Mobile Devices

The Online Job Portal System is also supported on mobile devices such as cell phones.

Alerts

The system can alert the in case of any problems.

The languages that shall be used for coding Online Job Portal System are Java Servlets, Java Server
Pages (JSP), and HTML. For working on the coding phase of the Online Library System, the Internet
Information Services (IIS) Server needs to be installed.

Development Tools :

We will make use of the available Java Development Tool kits for working with Java Beans and
Java Server Pages. Also we will make use of the online references available for developing programs
in HTML.

Class Libraries

We will make use of the existing Java libraries available for JSP and Servlets. Also we need to
develop some new libraries for the web- based application. Also we will develop new programs
using scripting languages.

On-line User Documentation and Help System Requirements

159
 Online help is provided for each of the feature available with the Online Job Portal System.
All the applications provide an on-line help system to assist the user. The nature of these systems is
unique to application development as they combine aspects of programming (hyperlinks, etc) with
aspects of technical writing (organization, presentation). Online help is provided for each and every
feature provided by the system.

The User Manual describes the use of the system to Admin. It describes the use of the
system on mobile systems. The user manual should be available as a hard copy and also as online
help.

An installation document will be provided that includes the installation instructions and
configuration guidelines, which is important to a full solution offering. Also, a Read Me file is
typically included as a standard component. The Read Me includes a “What ’s New With This
Release” section, and a discussion of compatibility issues with earlier releases. Most users also
appreciate documentation defining any known bugs and workarounds in the Read Me file.

Since the installation of Online Job Portal System is a complex process, our experts will do
it. So an installation Guide will not be provided to the user.

Purchased Components

The System Administrator will need to purchase the license for IIS Server. Mostly it is
available with Windows Environment. So the system need not purchase any licensing products.

Interfaces :

User Interfaces
The entire user Interfaces will provide with Final Project

Documentation in Later.

Hardware Interfaces
Hardware interfaces and all the functional Interfaces been describe

in Performance Requirements.

Software Interfaces
160
A firewall will be used with the server to prevent unauthorized access

to the system.

 Database Design

My SQL and My SQL Control center

 Graphic Designing

Adobe Photoshop CS3, Dreamweaver CS3

 Advanced Tools

Net Beans 6.1 and J.D.K 6.0

Communications Interfaces :
 The Online Job Portal System will be connected to the World Wide Web.

 The HTTP protocol will be used to facilitate communication between the client and server.

Other functional Requirements.

Performance Requirements
Server Side

The web application will be hosted on one of the windows server.

The ideal specifications for the server machines.

• Intel Core 2 Duo Extreme – 2 GHz

• 8GB of RAM

• Running Windows Server

• A commercial Web Application Server

161
• At least five 3rd party machines for clustering.The minimal specifications for the server machine.

• Intel Core 2 Duo – 1.86 GHz

• 2GB of RAM

• Running Windows XP

• Apache Tomcat Server

Client Side

The system is a web based application clients are requiring using modern web browser such
as Mozilla Firefox 1.5, Internet Explorer 6 and Enable cookies.

•The ideal requirement for a client PC logging into the

system.

•Intel Pentium IV or equivalent processor – 2.0 GHz or

above

Safety Requirements

Highly recommend Kaspersky 2010 internet security to been

Installed in users Pc to prevent the harm that may occurs by Unwanted
malicious software’s, phishing URLs and all the types of Virus attacks
during using this application..

INDEX:
Not applicable.

USE CASE DIAGRAM:

162
 Gives details file

Introduce Byself DB

Query
Employee Detail
Query update

Reply

Interview

Query.

Reply.

HRD
Experience

Company

Update DB

Wait for Result

Quiting

163
USE CASE DIAGRAM:

FULL DETAILS:
Employee can give full details to the interviewer.

SELF INTRODUCTION:
Employee give self introduction to HRD in interview.

QUERY:
HR asks the queries during the interview from employee.

REPLY:
Employee replies for the queries to HRD.

EXPERIENCE:
Database has been updated from an employee.

COMPANY:
He has to give self introduction about his old company.

UPDATE DATABASE:
Database is updated for an employee.
164
ACTIVITY DIAGRAM:

165
 given datails

self introduce

query

reply

update
database

waiting to see quiting

result

employee

166
ACTIVITY DIAGRAM:

FULL DETAILS:
The employee can give full details to the HRD during the interview process.

SELF INTRODUCTION:
Employee gives self introduction to the HRD in the interview.

QUERY:
HR ask the queries during the interview from employee.

REPLY:
Employee replies for the queries to the HRD.

COMPANY:
He has to give self introduction about himself.

UPDATE DATABASE:
Database has been updated for each employee of the organization.

WAIT FOR REPLY:

Employee has to wait for result until they give a call from an organization.

167
QUIT:
After getting his offer letter the employee has to proceed on it, if not he has to try for some
other organization.

CLASS DIAGRAM:

168
 Emplloyee
Name : string
Age : int
Addr : string
Gender : char

Reply()
Fill form()
Register()

Interviewer Db
Name : char System_no : int
Ph_no : int Emp_details : string
...
Mail_id : string
Experience : char... Update()
store()
Interviewer() collect INFO()
opinon()
Queries()
Evaluate()

HRD.
Nmae : string
ph_no : int
id : string
address : string
...

select()
opinion()
suggest()

169
CLASS DIAGRAM:

EMPLOYEE:
Employee is a person has to be prepared for the interview. He can fill the application form
and register

INTERVIEWER:
Interview is taken by the HRD for employee job.

HRD:
HRD is a person who is taking the interview. He can select an employee and suggest his job.

DATABASE:
Database have been updated for an employee.

170
SEQUENCE DIAGRAM:

171
Employee Interviewer HRD DB

Gives details files

Self introduction

Query

Process continues details

Reply

Query

Details

Reply

Wait for result

Quit

172
SEQUENCE DIAGRAM:

EMPLOYEE:
Employee gives the full details about him for the interview.

GIVES FULL DETAILS:

Employee can gives full details to the HRD during interview.

SELF INTRODUCTION:
Employee gives the self introduction to HRD during the interview.

QUERY:
HRD ask the queries in the interview.

PROCESS CONTINUES:
This process continues for all the candidate during HR interview.

REPLY:
Employee replies for the queries.

WAITING FOR RESULT:

Employee has to wait for the result until they give a call from an organization.

173
QUIT:
After getting his offer letter the employee has to proceed on it,if not he has to try for some
other organization.

COLLABORATION DIAGRAM:

174
 4: Process continues details

1: Gives details files

Employ Intervie
ee wer
2: Self introduction

8: Reply
10: Quit
5: Reply
6: Query
9: Wait for result 3: Query

DB
HRD
7: Details

175
COLLABORATION DIAGRAM:-

GIVE DETAILS FILES:-

Employee can give the full details to the HRD.

SELF INTRODUCTION:-
Employee gives the self introduction to the HRD in interview.

QUERY:
HR ask the queries during the interview from employee.

REPLY:
He replies for the queries to the HRD.

EXPERIENCE:
Employee have any other experiences in any organization.

COMPANY:
He has to tell self introduction about his company.

176
UPDATE DATABASE:
Database has been updated for each employee of an organization.

WAIT FOR RESULT:

Employee has to wait for result until they give up a call from an organization.

177
STATE CHART DIAGRAM:

Gives Self Query

details information

Waiting Updation Reply

for result of DB

Quiting

178
STATE CHART DIAGRAM:

DETAILS:
Employee has to give full details to the HRD during the interview.

SELF INTRODUCTION:
Employee gives self introduction to the HRD in interview.

QUERIES:
Query will be asked during the interview by the HRD.

REPLY:
Employee replies for the queries during the interview.

179
UPDATE DB:
Database have been updated for each employee.

WAITING FOR RESULT:

Employee has to wait for the result.

180
LOGICAL LAYER ARDHITECTURE:

181
TECHNICAL SERVICES:

182
DOMAIN LAYER:
183
184
USER INTERFACE LAYER:

185
186
COMPONENT DIAGRAM:

187
COMPONENT DIAGRAM:

EMPLOYEE:
Employee is a person has to be well prepared for the interview.he can enter the application
form and register it.

INTERVIEWER:
Interview is taken by the HRD for the employee’s job.

HRD:
HRD is a person who is taking the interview and giving job to the employee.

DATABASE:
Database has been updated for an employee in particular organization.

188
189
DEPLOYMENT DIAGRAM:

190
DEPLOYMENT DIAGRAM:

PC:
PC is the personel computer .It contains the details about the employee. he employee end of
from to the HRD during interview.It follows the details and he has to provide the full details about
his resume.

APPLICATION SERVER:
It is a deployment that shows the mapping of process. The application server requires the
employee details and be updated to the particular organization. It uses the protocol TCP/IPfor
updating the details of an employee.

DATA SERVER:
Data server contains the details about an employee during HR interview. The particular
details can been updated for the interview process.

191
Conclusion:

Thus the recruitment system for use case diagram, class diagram, sequence diagram,
collaboration diagram,statechart diagram, component diagram,deployment diagram are
implemented successfully.

192