Adaptive provisioning of human expertise in Service Oriented Systems ppt

INTRODUCTION

Web-based collaborations have become essential in

today’s business environments.

Knowledge-intensive environments clearly demand

for provisioning of human expertise along with sharing

of computing resources or business data through

software-based services.

Human-Provided Services (HPS) Framework enables

human participation in a SOA environment.

The mix of software services and humans interacting

on the Web is called a Mixed Service-oriented System.

The foundational pillars of such mixed systems utilized

are as follows:

•Human-Provided Services. We discuss the HPS concept

letting people participate in pure service-oriented

environments.

•Flexible Interaction Models. Interaction monitoring

and mining is applied to determine the behavior of

services and user relations.

•Adaptive Service Infrastructure. We discuss the need

for run-time adaptation. In particular, we do not only

adapt service behavior,but also provided service

features at run-time.

SYSTEM ANALYSIS

EXISTING SYSTEM:

While most existing work focuses on the discovery

and composition of software based services, we

highlight concepts for a people-centric Web.

LIMITATIONS OF EXISTING SYSTEM:

To address these challenges, we introduce an adaptive

approach allowing humans to provide their expertise

through services using SOA standards, such as SOAP.

PROPOSED SYSTEM:We propose a framework that is based on interaction

monitoring techniques enabling adaptations in SOA-

based socio-technical systems.

ADVANTAGES OF PROPOSED SYSTEM:

These systems are characterized by both technical and

human/social aspects that are tightly bound and

interconnected.

The technical aspects are very similar to traditional

SOAs, including facilities to deploy, register and

discover services, as well as to support flexible

interactions.

FUNCTIONAL REQUIREMENTS:

Functional requirements specify which output file

should be produced from the given file.

They describe the relationship between the input

and output of the system.

For each functional requirement a detailed

description of all data inputs and their source and the

range of valid inputs must be specified.

NON FUNCTIONAL REQUIREMENTS:

Describe user-visible aspects of the system that

are not directly related with the functional behavior

of the system.

Non-Functional requirements include quantitative

constraints, such as response time (i.e. how fast the

system reacts to user commands.) or accuracy (how

precise are the systems numerical answers).

HARDWARE AND SOFTWARE

REQUIREMENTS

HARDWARE REQUIREMENTS:

System : Pentium IV 2.4 GHz.

Hard Disk : 40 GB.

Floppy Drive : 1.44 Mb.

Monitor : : 15 VGA Colour.

Mouse : Logitech.

Ram : 512 Mb.

SOFTWARE REQUIREMENTS:

Operating system : Windows XP.

Coding Language : ASP.Net with C#

Data Base : SQL Server 2005

System DesignSYSTEM ARCHITECTURE:

UML DIAGRAMS:USE CASE DIAGRAM:

User

Admin

Manager

Create Account

Login

Search

Accept/Reject Images

Maintain Webservices

Upload Images

View & DownloadResults

Store Result

IDFromToITypeINameExtensionPathStatus

Imgidgenration()ViewImg()

Download Items

DIDFromDTypeDNameExtensionPathView

Downloadidgenration()ViewDetails()

Login Account

IDNameLoginIDPasswordDateMobileEMailLoginType

Loginidgenration()CreateAccount()

Host Service

IDUrlUrlNameDBNameStatus

Receivedidgenration()View WebServices()

CLASS DIAGRAM:

SEQUENCE DIAGRAM:

User Admin ManagerDatabase

Create Account

Create Account

Create Account

Search

Responce To User

View/Download Details

Record Not Found

Accept/Reject Images

Request MatchesRequest Not

Matches

Upload Images

Allow/Block WebServices

DFD DIAGRAM:Login

CheckManagerUser

Exists Exists Exists

yes

yes

Create Accountno

Create Account Admin

yes

no no

Search

Exists

Exists

Not Exists

View & DownloadResults(Multiple DB)

Record Not Found

Accept/RejectImages

View ManagerResponses

Upload Images

End

Control WebServices

IMPLEMENTATION

Implementation is the stage of the project when the

theoretical design is turned out into a working system.

It is the most critical stage in achieving a successful

new system and in giving the user, confidence that the

new system will work and be effective.

MODULES

User

Manager

Admin

FUTURE ENHANCEMENTS

In the future, we aim at providing more fine-grained

monitoring and adaptation strategies.

CONCLUSION

Web services can be effectively used to participate in

and set up business-to-business (B2B) transactions.

We outlined concepts that let people offer their

expertise in a service-oriented manner and covered the

deployment, discovery and selection of Human-

Provided Services.

For any Queries Contact: 9704562440