• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Soa Architecture Design

 
Ranch Hand
Posts: 38
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello Guy's
Where i work, we use Spring / CXF to create webservice.

How we procede for the analyse is :
1) Design in Enterprise Architect
2) Document it textual in a wiki
3) Code.

But we talking about services here.
I am not agree with enter the code in a wiki because its a lot of loosing time.

We had to view the service tree with all fuctions very quickly when we developed a facade service or an front-end application.

With the wiki approch , we had to navigate in pages for each services and I think this is not a good thing.

Do you have some suggestion to how doing the UML / Diagram of class / and view all services in a simple way for programmers / analyst and project manager otherwise of writing all this in a wiki.

if so , please help me with that.

Thanks a lot,
Chris.
 
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
You may want to consider using this notation instead.
[ April 18, 2008: Message edited by: Peer Reynders ]
 
christian leclerc
Ranch Hand
Posts: 38
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
interesting
 
Ranch Hand
Posts: 2187
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Creating textual descriptions of the functionality/behavior of web services is very important. Moreover, having this information easily accessible is just as important. So, storing this information is a good practice.

The textual descriptions can be augmented by visual UML Use-case diagrams. These diagrams can help programmers identify existing services and their relationships.

Based on your description, I don't think you are creating these type of visual diagrams. Now, dependeing upon the number of services your organization has, you still might have to navigate thru pages of diagrams. But, this should be easier than navigating thru textual information.

The diagrams should be stored in the project wiki or other document repository of the SOA.
[ April 18, 2008: Message edited by: James Clark ]
 
Jimmy Clark
Ranch Hand
Posts: 2187
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Another important element of an SOA is a service registry. The registry is where you can login and take inventory of what services are available, etc. If an organization has to manage hundreds, maybe even thousands of web services, a functioning service registry is a critical element.

When organizations are just starting out, they might overlook the importance of a service registry. It would be best to implement one as soon as possible.

See for more service registry
[ April 18, 2008: Message edited by: James Clark ]
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic