Developing .NET Web Services with XML

Functional Application Design

Coming up with a good application design is critically important for the success of any software application. The first step is to move top-down from goals to design by starting to define (in still very general terms) the functionality exposed by the Jokes service, and then developing a back-end schema that supports that functionality from a data perspective. In a second step, we then create in more detail an object model suitable to implement the services the Jokes application is supposed to provide. At this juncture, it is also appropriate to make decisions about security, state management, and error handling.

Defining Public Methods

Let s start the application design process by writing down the specific methods we think our Jokes Web Service should offer, and the categories that reflect their function:

The application needs methods dealing with user administration:

  • addUser Lets a user register to our service.

  • addModerator Lets a moderator add an existing user to become a moderator.

  • checkUser Verifies that a user has previously registered with the service. Refer to the State Management section to see why this is a useful method for the service to expose.

Then, the application needs methods dealing with delivering and managing jokes:

  • addJoke Lets a registered user add a joke.

  • getJokes Delivers some randomly selected jokes, say up to 10 per request, to our registered users.

  • addRating Lets our users add a rating to a joke, say on a scale of 1 to 5.

  • getUnmoderated Registered moderators can call...

UNLIMITED FREE
ACCESS
TO THE WORLD'S BEST IDEAS

SUBMIT
Already a GlobalSpec user? Log in.

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

Customize Your GlobalSpec Experience

Category: Virtual Reality Software
Finish!
Privacy Policy

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.