BPO Management System
BPO Management System
AIM:
PROBLEM STATEMENT:
With the reduction in communication costs and improved bandwidths and associated
infrastructure, BPO as a segment is witnessing a massive growth. One of the key challenges that
BPO companies that provide data entry/data validation services is an efficient and effective way
of getting the source documents from different customers and accurately route the same to
different operators for processing.
1.0 INTRODUCTION
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. Originally, this was associated with manufacturing firms, such as Coca Cola
that outsourced large segments of its supply chain.[1] In the contemporary context, it is primarily
used to refer to the outsourcing of business processing services to an outside firm, replacing in-
house services with labor from an outside firm.
BPO is typically categorized into back office outsourcing - which includes internal business
functions such as human resources or finance and accounting, and front office outsourcing -
which includes customer-related services such as contact center services.
BPO that is contracted outside a company's country is called offshore outsourcing. BPO that is
contracted to a company's neighboring (or nearby) country is called nearshore outsourcing.
1.1 PURPOSE
Seamless process that is fully integrated ensuring better quality of service to customers.
Documents as well as the status of process is accessible quickly and from anywhere to BPO
management as well as customers.
Enriched experience for users as they can search for documents and process them online.
1.2 SCOPE
As part of BPO, documents need to be managed between the outsourcing company and the
offshore company.
Security of the documents has to be ensured so that there is no unauthorized access of the
documents to other organizations.
Appropriate process flow of the documents has to be present in the system to check the status
of the documents at any point of time.
J2EE Java 2 Enterprise Edition is a programming platform java platform for developing and
running distributed java applications.
1.4 REFERENCES
HTML
JSP
Javascript
Java
AIM:
To draw the usecase diagram for BPO management system under the analysis model.
PROCEDURE:
Step 6: Select usecase diagram then in screen editor drag and trag. Usecase and actor
From pallet and draw the usecase model.
DESCRIPTION:
4. Quality Check
5. Shipment 6. Payment
ACTORS:
1. BPO Organization
2. Client
ACTORS DOCUMENTATION:
1. BPO Organization:
Searching the client
2. Client:
Clients can scan documents from multiple locations and an automatic uploader module that can
be scheduled automatically uploads the documents.
USE-CASE NAME: Search for client/job BPO organization searches the outsourcing job.
USE-CASE NAME: Negotiate the project Once job has been found then negotiate with the
client for doing that project.
USE-CASE NAME: Upload input data After finalizing the negotiation client uploads the input
to the BPO organization through
FTP USE-CASE NAME: Perform required conversion BPO organization starts the required
conversion process.
This usecase is used to ensure that the quality of the product. Randomly audits the outcome of
the project to ensure the quality. This process is continued until we achieve the required quality.
USE-CASE NAME: Shipment After QC, upload the output to the client.
USE-CASE NAME: Payment Get the payment for the project from client
RESULT:
Thus the usecase diagram for bpo management system is implemented and executed
successfully.
EX NO:
AIM:
To draw the sequence diagram for BPO management system under the analysis model.
PROCEDURE:
Step 6: Select sequence diagram then in screen editor drag and trag. sequence and actor
An object is shows as an box and the top of dash vertical line. This
vertical line is called object life line. The life line represents objects life during interaction this
was give by Jackupson. Each message is represent by an arrow between the lifeline of
Two objec. The order of message is occurred from top to bottom of a page. Message cotain
This interactive behaviour is represented in UML by two diagrams known as Sequence diagram
and Collaboration diagram. Sequence diagram emphasizes on time sequence of messages and
collaboration diagram emphasizes on the structural organization of the objects that send and
receive messages.
The purposes of interaction diagrams are to visualize the interactive behaviour of the
system. Now visualizing interaction is a difficult task. So the solution is to use different types of
models to capture the different aspects of the interaction, that is why sequence and collaboration
diagrams are used to capture dynamic nature but from a different angle.
Thus the sequence diagram for BPO management system is implemented executed and
verified successfully.
EX NO:
DATE: CLASS DIAGRAM FOR BPO
AIM:
To draw the class diagram for BPO management system under the analysis model.
PROCEDURE:
Step 6: Select class diagram then in screen editor drag and trag. class and actor
The UML class diagram is to illustrate class interfaces and their actions. They are used for static
object modeling, we have already introduced and used their UML diagram while domain
modeling
A UML class diagram is refered to as object modeling is the main static analysis diagram.
Notations:
The class diagram is a static diagram. It represents the static view of an application. Class
diagram is not only used for visualizing, describing and documenting different aspects of a
system but also for constructing executable code of the software application. The class diagram
describes the attributes and operations of a class and also the constraints imposed on the system.
The class diagram is widely used in the modeling of object oriented systems because they are the
only UML diagrams which can be mapped directly with object oriented languages.
The class diagram shows a collection of classes, interfaces, associations, collaborations and
constraints. It is also known as a structural diagram.The purpose of the class diagram can be
summarized as:
Thus the class diagram for BPO managemet system is implemented and executed
Successfully.
EX NO:
AIM:
To draw the activity diagram for BPO management system under the analysis model.
PROCEDURE:
Step 6: Select avtivity diagram then in screen editor drag and trag. ativity and actor
An activit diagram is veriatio or special case or a state mechine, in which the states
are activities representing a performance of opration and the transition or triggered by the
completion of operation. Activity diagram is similar to state chart diagram where the tocken
represented as an operation. An activity shows as a round box containing name of operation.
The concurrent control is indicated by multiple arrows, leaving a synchronization bar represented
by short or thick bar with incoming and outgoing arrows.
Activity diagram is another important diagram in UML to describe dynamic aspects of the
system. This diagram is basically a flow chart to represent the flow form one activity to another
activity. The activity can be described as an operation of the system. So the control flow is
drawn from one operation to another. This flow can be sequential, branched or concurrent.
Activity diagrams deals with all type of flow control by using different elements like fork, join
etc.
The basic purposes of activity diagrams are similar to other four diagrams. It
captures the dynamic behaviour of the system. Other four diagrams are used to show the message
flow from one object to another but activity diagram is used to show message flow from one
activity to another. Activity is a particular operation of the system. Activity diagrams are not
only used for visualizing dynamic nature of a system but they are also used to construct the
executable system by using forward and reverse engineering techniques. The only missing thing
in activity diagram is the message part.
It does not show any message flow from one activity to another. Activity diagram is
some time considered as the flow chart. Although the diagrams looks like a flow chart but it is
not. It shows different flow like parallel, branched, concurrent and single. So the purposes can
be described as:
Thus the activity diagram for BPO management system are implemented and executed
successfully.
EX NO:
AIM:
To draw the activity diagram for BPO management system under the analysis model.
PROCEDURE:
Step 6: Select collaboration diagram then in screen editor drag and trag. ativity and actor.
DESCRIPTION:
Thus the collaboration diagram for BPO management system is implemented and
executed successfully.
EX NO:
To draw the activity diagram for BPO management system under the analysis model.
PROCEDURE:
Step 6: Select collaboration diagram then in screen editor drag and trag. ativity and actor.
DESCRIPTION:
State diagram describes all the possible states that particular objects can get into
and how the object state changes as the result of events that reach the object. It describes the
behavior of the system. At start point on initial transition call as get fast item leads to the
checking state. Checking state has an activity, associated with check item.
The name of the diagram itself clarifies the purpose of the diagram and other
details. It describes different states of a component in a system. The states are specific to a
component/object of a system.
A Statechart diagram describes a state machine. Now to clarify it state machine can be
defined as a machine which defines different states of an object and these states are controlled by
external or internal events.Statechart diagram is one of the five UML diagrams used to model
dynamic nature of a system. They define different states of an object during its lifetime. And
these states are changed by events. So Statechart diagrams are useful to model reactive systems.
Reactive systems can be defined as a system that responds to external or internal events.
State chart diagram describes the flow of control from one state to another state. States
are defined as a condition in which an object exists and it changes when some event is triggered.
So the most important purpose of Statechart diagram is to model life time of an object from
creation to termination. State chart diagrams are also used for forward and reverse engineering of
a system. But the main purpose is to model reactive system.
RESULT:
Thus the state diagrame for BPO management system are implemented executed
successfully.
EX NO:
AIM:
To draw the package diagram for BPO management system under the analysis model.
PROCEDURE:
Step 6: Select package diagram then in screen editor drag and trag. ativity and actor.
DESCRIPTION:
Packages are applied to any model element, not only classes. Package diagram
shows the packages of classes and the independent among them. A dependencies they exists
may be two element. Changes to the definition ofone element may course change to the other.
Dependency exist for many reasons like, a pase scale design must minimize the dependencies .
So that the effect of changes are reduced.
A package import is "a relationship between an importing namespace and a package, indicating
that the importing namespace adds the names of the members of the package to its own
namespace." By default, an unlabeled dependency between two packages is interpreted as a
package import relationship. In this relationship elements within the target package will be
imported in source package.
A package merge is "a directed relationship between two packages that indicates
that the contents of the two packages are to be combined. It is very similar to Generalization in
the sense that the source element conceptually adds the characteristics of the target element to its
own characteristics resulting in an element that combines the characteristics of both". Packages
containing use cases i.e In this relationship if an element exists within source element's
definition and target also then the source element's definition's will be expanded to include target
element's definitions.
Package diagrams can use packages containing use cases to illustrate the functionality of
a software system. Package diagrams can use packages that represent the different layers of a
software system to illustrate the layered architecture of a software system. The dependencies
between these packages can be adorned with labels stereotypes to indicate the communication
mechanism between the layers.
RESULT:
Thus the pakage diagram for BPO management system are implemented and executed
successfully.