I was wondering if other Aces recognize the same challenges as I do, concerning SOA. As technology is developing so fast, I see that methodology is lagging behind. Things I'm looking for are:

• (Business) Service Design & Discovery
• Service Versioning
• the use of servicedomains
  
• Scoping of services (in relation to the domains)
  
• How-To document a service
• Getting a grip on depencies

For example:
From a business perspective, we define domains. The domain consists of all the data and relationship that's owned by a specific business user (usually a department or head of). We also define the (large grained business) services in the domain. However, domains do have relationships. As you get down to building the domains & services you will need to address the relationships. Here's the catch: as the relationship cannot be constrained by the database (as we used to do) because of the architectural rule that a service maintains its own data, you will have to build in awareness of the relationship into services. This means that the services are aware of each other, which is contradictory to service independency. So in fact, I have two basic rules that conflict. How to solve?

I don't expect answers here, but I do hope we can have a session during OOW talking about this kind of stuff. But there will be a lot of other questions around, i think.

Let me know if you're going to attend! Oh, btw, it is called ACE Unconference, but everybody is welcome to attend!