Hi again, 2009/12/16 Michael Poulin <[email protected]>
> 3) “Flexibility is not a function of service functionality”, please, > comment more, I have not got your point here > > In technical terms (SOA is about technology remember), ability to replace a task in a IT defined process is not a dependent on what the task does, but on the interfaces of the task. For example, if I have a BPEL process and want to exchange a task, effort required is based on whether the interfaces are equivalent or have to be changed. As an often used analogy, we know that fashion changes every season/year but it's very difficult to predict the fashion 5 years into the future. However, if the methods on how to receive it and on how to sell it remains the same, it's possible to use the same methods. > 4) “Domain specific semantic dictionary” vs. UML. It is well-known > (sorry for this note) that the Domain specific semantic is limited in the > scope by the Domain. You cross the domain – your information looses sense. > Since you so confident in Domain specific over the UML, I start thinking > about cultural specifics of countries where people frequently change the > domain and where they stay with the domain for long time. Am I right? > I'm only using the semantic dictionary to model messages. I'm still using UML for functional analysis to identify services and interfaces. > > 5)”Designing by semantic model of messages after services are identified > services by functional/nonfunctional requirements can enable processes to > become more flexible” - I have not understood this > > Check answer to question 3. > 6) “ Services related to change by specification usually impact > processes more than changes by design or by deviation” - IMO, a functional > change in the service used as the process' action provider is immaterial > whilst new functionality provides the same RWE and accessible via the same > interface and the old one. That is, the change stays transparent to the > consumer of the service (the process in this case). If the service changes > in the way that it cannot meet the process' needs, the process cannot > perform and simply throws such service away. If the service changes affect > only interaction interface with the process, process is affected, but how do > you distinguish between the “changes by design” and the “changes by > specification” when new design is done due to the change in the > specification? Or I miss something big here? > > I'm not talking about functionality in the presentation. Functional analysis is done when identifying services and interfaces. Thanks for your comments. :-) Cheers, H.Ozawa
