You may use UML etc. style notations - web services are a new technology, as such improvise your designs etc. as long as they make sense. Use Case Diagram Example.
This is the use case diagram that was made for the Aspect Oriented UDDI. Your one should be made in Microsoft Visio, NOT in Microsoft Word.
WebService Requester
Search for Provider’s with the specific aspects, methods or components Receive notification of new registered provider Register to store search history in AOUDDI
Register with AOWSDL Register a WSDL
WebService Provider
View the search results and errors messages Use a WUI to test the system AOUDDI Tester
AOUDDI Admin
Clear entire Database Delete single webservice entry
Quickly enter default test values.
Object Oriented Analysis (OOA) This is a sample object oriented analysis from the AOUDDI, basically the OOA is a top level design of how your system will be structured, this should contain all the classes you are going to create in your system. Again do NOT make it in MS Word. Webservice Requester (.aspx)
AOUDDISystem Webservice Provider (.asmx)
AOUDDI (.cs)
AOWSDL Decoder (.cs)
AOUDDI Search (.cs)
AOUDD UpdateAcceptor (.cs)
AOUDDI LocalDataManager (.cs)
AOUDDI SearchHistory (.cs)
AOUDD WSRegister (.cs)
AOUDDI DBManager (.cs)
DataBase
Object Oriented Design (OOD) This is a VERY SCALED DOWN version of the Object Oriented Design from the AOUDDI. From the OOD you should be able to generate skeleton code straight away. The OOD should contain ALL the classes/objects in your system, and ALL their public method names, parameters and return types. After this step the implementation tasks should be a lot easier to be divided amount the group. Below is only an example, for this part of your project, the yellow boxes should be just a class.