INTRODUCTION

In this paper we utilize Human-Provided Services (HPS) enabling flexible interactions in service oriented systems. We discuss the discovery and interactions in mixed service oriented systems comprising HPS and software-based services (SBS). Experts offer their skills and capabilities as HPS that can be requested on demand. In this work we present the following key contributions: (i) Estimation of user reputation based on a context-sensitive algorithm. Our approach, called ExpertHITS, is based on the concept of hubs and authorities in Web-based environments. (ii) An approach for community reputation (the hub-expertise of users) influenced by trust relations. Dynamic link weights are based on trust and user rating influenced by the query context. ExpertHITS is calculated online, thus fully personalized based on the expertrequesters preferences (i.e., the demanded set of skills). (iii) Implementation and evaluation of our approach demonstrating scalability and effectiveness of our proposed algorithm.

Applying this idea in our scenario, a member of the Expert Web may receive an RFS and delegate work to some other peer in the network (characterizing hubs in the network). Receivers of the delegated work, however, expect RFSs fitting their skills and expertise (i.e., being an authority in the given domain). Careless delegations of work will overload these peers resulting in degraded processing time due to missing expertise. Within the ExpertWeb, authorities give feedback using rating mechanism (e.g., a number on the scale from 1 to 5) to indicate their satisfaction whether a particular hub distributes work according to their skills and interest. Thus, a good hub is characterized by a neighborhood of peers that are satisfied with received RFSs. On the other hand, delegation of work is strongly influenced by trust, for example, whether the initial receiver of the RFS (hub within the Expert Web) expects that the peer will process work in a reliable and timely manner. RFS receivers need to be trusted by influential hubs that are highly rated in order to be recognized as authoritative peers in the Expert Web. Notice, hub and authority scores are available for each member in the network. Thus, a member may act as a hub and authority by processing or delegating tasks.

LITERATURE SURVEY

Literature survey is the most important step in software development process. Before developing the tool it is necessary to determine the time factor, economy n company strength. Once these things r satisfied, ten next steps is to determine which operating system and language can be used for developing the tool. Once the programmers start building the tool the programmers need lot of external support. This support can be obtained from senior programmers, from book or from websites. Before building the system the above consideration r taken into account for developing the proposed system.

We have to analysis the Service Computing:

WEB SERVICES:
Web Services can convert your application into a Web-application, which can publish its function or message to the rest of the world. The basic Web Services platform is XML + HTTP. A web service is a method of communication between two electronic devices. It a "solution logic" that can be exposed over world-wide web. The W3C defines a "web service" as "a software system designed to support interoperable machine-to-machine interaction over a network. It has an interface described in a machine-processable format (specifically Web Services Description Language WSDL). Other systems interact with the web service in a manner prescribed by its description using SOAP messages, typically conveyed using HTTP with an XML serialization in conjunction with other Web-related standards." 2

REMOTE PROCEDURE CALLS

RPC web services present a distributed function (or method) call interface that is familiar to many developers. Typically, the basic unit of RPC web services is the WSDL operation. The first web services tools were focused on RPC, and as a result this style is widely deployed and supported. However, it is sometimes criticized for not being loosely coupled, because it was often implemented by mapping services directly to language-specific functions or method calls. Many vendors felt this approach to be a dead end, and pushed for RPC to be disallowed in the WS-I Basic Profile. Other approaches with nearly the same functionality as RPC are Object Management Group's (OMG) Common Object Request Broker Architecture (CORBA), Microsoft's Distributed Component Object Model (DCOM) or Sun Microsystems's Java/Remote Method Invocation (RMI).

APPLIED COMPUTING:
Although when considered from a purely technological point of view ServiceOriented Programming (SOP) is not an enormous novelty, when it comes to paradigmatic considerations SOP is quickly changing our vision of the Web. Originally, the Web was mainly seen as a means of presenting the information to a wide spectrum of people, but SOP is now triggering a radical shift to a vision of the Web as a computational fabric where loosely coupled services interact publishing their interfaces inside dedicated repositories, where they can be searched by other services, retrieved and invoked, always abstracting from the actual implementation. In the context of this modern paradigm we have to cope with an old challenge, like in the early days of Object-Oriented Programming when, until key features like encapsulation, inheritance, and

polymorphism, and proper design methodologies were defined, consistency in the programming model definition was not achieved. The complex scenario of Service Oriented Programming engineering needs and to be clarified the on many aspects, point both of from the view.

from

foundational

From the engineering point of view, there are open issues at many levels. Among others, at the system design level, both traditional approaches based on UML and approaches taking inspiration from business process modeling, e.g. BPMN, are used. At the composition level, although WS-BPEL is a de-facto industrial standard, other approaches are appearing, and both the orchestration and choreography views have their supporters. At the description and discovery level there are two separate communities pushing respectively the semantic approach (ontologies, ...) and the syntactic one (WSBPEL, ...). In particular, the role of discovery engines and protocols is not clear. In this respect we still lack adopted standards: UDDI looked to be a good candidate, but it is no longer pushed by the main corporations, and its wide adoption seems difficult. Furthermore, a new different implementation platform, the so-called REST services, is emerging and competing with classic Web Services. Finally, features like Quality of 4

Service,

security,

sustainability

and

dependability

need

to

be

taken

seriously into account, and this investigation should lead to standard proposals.

EXISTING SYSTEM
The process model may be composed of single tasks assigned to responsible persons, describing the steps needed to produce a software module. After finishing a common requirements analysis, an engineer evaluates the re-usability of existing work, while a software architect designs the framework. Existing approaches in personalized expertise mining algorithm typically perform offline interaction analysis.

PROPOSED SYSTEM
Here we propose the Expert Web consisting of connected experts that provide help and support in a service oriented manner. Examples are crowd-sourcing applications in enterprise environments or open Internet based platforms. These online platforms distribute problem solving tasks among a group of humans. The members of the Expert Web are either humans, such as company employees offering help as online support services or can in some cases be provided as software-based services. Applied to enterprise scenarios, such a network of experts, spanning various organizational units, can be consulted for efficient discovery of available support. The expert seekers, for example the software engineers or architect in our use case, send requests for support, abbreviated as RFSs. Experts may also delegate RFSs to other experts in the network, for example when they are overloaded or not able to provide satisfying responses. Following this way, not only users of the expert network establish trust in experts, but also trust relations between experts emerge.

In our future work, we will study network effects of two-sided markets in mixed serviceoriented systems. Also, we plan to make the system available for public use.

ADVANTAGES:
1. 2. 3.

Solve emergent problems in distributed collaboration environments Trust relations Expert-HITS is calculated online

CONCLUSION:

Web services are one of the key elements of the so-called programmable Web. They are extremely versatile software elements that really have the potential to open up a new era in software: the age of interoperability. Web services can be effectively used to participate in and set up business-to-business (B2B) transactions. They are great at exposing software functionality to customers and integrating heterogeneous platforms.

SYSTEM ANALYSIS

SYSTEM REQUIREMENTS:
HARDWARE REQUIREMENTS: System Hard Disk : Pentium IV 2.4 GHz. : 40 GB.

Floppy Drive : 1.44 Mb. Monitor Mouse Ram : 15 VGA Colour. : Sony. : 512 Mb.

SOFTWARE REQUIREMENTS: Operating system Coding Language : Windows XP. : ASP.Net with C# : SQL Server 2005.

Data Base

SYSTEM DESIGN
DATA FLOW DIAGRAM / USE CASE DIAGRAM / FLOW DIAGRAM
The DFD is also called as bubble chart. It is a simple graphical formalism that can be used to represent a system in terms of the input data to the system, various processing carried out on these data, and the output data is generated by the system.

ACTIVITY DIAGRAM

LOGIN

User check

Expert Create Account no exists ? yes Private check Public View User & Delegate Query Request

no exists ? yes Create Account Guest

Compose Request

View Experts List and Rating

View Query Answers PROCESS REJECTED

View Request & Response Quries

No Permission to View Quries DELEGATE

View Request & Response Quries Generate Rating Points and Ranking Query Act Public or Private

FLOWCHART DIAGRAM
Login

User
Check

Expert

Create Account Exists yes Private Query Request To Expert Check Public View Request & Response Quries No Permission to View Query PROCESS View Experts Rating Points DELEGATE REJECT View Query as Public yes View User & Delegate Query Request no Create Account no Exists

Query Act Private or Public

Generate Rating Points and Ranking

End

10

SEQUENCE DIAGRAM

Database User Create Account Create Account Expert Guest

Query Request View Query Request Process,Delegate,Reject View Process,Delegate,Reject Quries Expert Ranking and Rating Points View Expert Rating View Query Response Query Act Public or Private

View QueryAnswers

public / private

query act as Public

11

USE CASE DIAGRAM

Create Account

Login

Query Request

User

view query answer (public act) Expert

View Experts List

Guest

Generate Rating and Ranking

View Query Responses

Act Public or Private query use

12

CLASS DIAGRAM

User Accout ID Name LoginID Password ConPassword EMail LoginType

RFS Query QID Category Title Description UserName ExpertName DelegateExpert Answer QueryStatus AddRequest() View WebServices()

Loginidgenration() CreateAccount()

Expert Account ID Name LoginID Password ConPassword EMail LoginType Rating Ranking Loginidgenration() CreateAccount()

13

IMPLIMENTATION AND RESULTS

SAMPLE SCREENS

USER DISCOVERY

14

15

16

17

18

19

GUEST

20

21

22

23

EXPERT DISCOVERY

24

25

26

27

28

29

30

31

32

33

34

35

36

TESTING AND VALIDATION

The purpose of testing is to discover errors. Testing is the process of trying to discover every conceivable fault or weakness in a work product. It provides a way to check the functionality of components, sub assemblies, assemblies and/or a finished product It is the process of exercising software with the intent of ensuring that the Software system meets its requirements and user expectations and does not fail in an unacceptable manner. There are various types of test. Each test type addresses a specific testing requirement.

TYPES OF TESTS

UNIT TESTING Unit testing involves the design of test cases that validate that the internal program logic is functioning properly, and that program inputs produce valid outputs. All decision branches and internal code flow should be validated. It is the testing of individual software units of the application .it is done after the completion of an individual unit before integration. This is a structural testing, that relies on knowledge of its construction and is invasive. Unit tests perform basic tests at component level and test a specific business process, application, and/or system configuration. Unit tests ensure that each unique path of a business process performs accurately to the documented specifications and contains clearly defined inputs and expected results.

37

INTEGRATION TESTING

Integration tests are designed to test integrated software components to determine if they actually run as one program. Testing is event driven and is more concerned with the basic outcome of screens or fields. Integration tests demonstrate that although the components were individually satisfaction, as shown by successfully unit testing, the combination of components is correct and consistent. Integration testing is specifically aimed at arise from the combination of components. exposing the problems that

FUNCTIONAL TEST

Functional tests provide systematic demonstrations that functions tested are available as specified by the business and technical requirements, system documentation, and user manuals. Functional testing is centered on the following items:

Valid Input Invalid Input Functions Output

: identified classes of valid input must be accepted. : identified classes of invalid input must be rejected. : identified functions must be exercised. : identified classes of application outputs must be exercised.

Systems/Procedures : interfacing systems or procedures must be invoked.

Organization and preparation of functional tests is focused on requirements, key functions, or special test cases. In addition, systematic coverage pertaining to identify Business process flows; data fields, predefined processes, and successive processes must be considered for testing. 38

Before functional testing is complete, additional tests are identified and the effective value of current tests is determined.

SYSTEM TEST
System testing ensures that the entire integrated software system meets requirements. It tests a configuration to ensure known and predictable results. An example of system testing is the configuration oriented system integration test. System testing is based on process descriptions and flows, emphasizing pre-driven process links and integration points.

WHITE BOX TESTING

White Box Testing is a testing in which in which the software tester has knowledge of the inner workings, structure and language of the software, or at least its purpose. It is purpose. It is used to test areas that cannot be reached from a black box level.

BLACK BOX TESTING

Black Box Testing is testing the software without any knowledge of the inner workings, structure or language of the module being tested. Black box tests, as most other kinds of tests, must be written from a definitive source document, such as specification or requirements document, such as specification or requirements document. It is a testing in which the software under test is treated, as a black box .you cannot see into it. The test provides inputs and responds to outputs without considering how the software works.

39

6.1 UNIT TESTING:

Unit testing is usually conducted as part of a combined code and unit test phase of the software lifecycle, although it is not uncommon for coding and unit testing to be conducted as two distinct phases.

TEST STRATEGY AND APPROACH Field testing will be performed manually and functional tests will be written in detail. TEST OBJECTIVES All field entries must work properly. Pages must be activated from the identified link. The entry screen, messages and responses must not be delayed.

FEATURES TO BE TESTED Verify that the entries are of the correct format No duplicate entries should be allowed All links should take the user to the correct page.

40

6.2 INTEGRATION TESTING

Software integration testing is the incremental integration testing of two or more integrated software components on a single platform to produce failures caused by interface defects. The task of the integration test is to check that components or software applications, e.g. components in a software system or one step up software applications at the company level interact without error.

TEST RESULTS: All the test cases mentioned above passed successfully. No defects encountered.

6.3 ACCEPTANCE TESTING

User Acceptance Testing is a critical phase of any project and requires significant participation by the end user. It also ensures that the system meets the functional requirements.

TEST RESULTS: All the test cases mentioned above passed successfully. No defects encountered. 41

42