Stefan Tilkov wrote:
  The main problem is in tools (and you cannot do MDA without  
tools). I  learned that majority of tools support OOAD (Object  
oriented analysis and design). Most of them only transforms class  
models into static object structure. That’s useful. It could save  
time during developmnet phase. Etc… but does not help with SOA.
    
I don't understand this statement. First of all, lots of tools  
support generation from other models; e.g. it's easily possible to  
use UML activity diagrams to describe a business process and generate  
e.g. BPEL from it. Secondly, I don't see how generating WSDLs from  
UML class models "does not help with SOA".
  
I tried generating BPEL from activity diagram in IBM Software Architect and from BPM model in Borland Together and creating full model took me longer time than writing BPEL XML "by hand".
Also possibilities to integrate that model with other models to get BPEL itnegrated with other generated artifacts were poor.
May be I should try other tools.

I agree that tools does help with SOA, but on low level of abstraction...


Which is exactly my point - the fault is not in UML, nor OO, but in  
using it wrongly.

  
I agree.
But the way you use UML, nor OO, depends on tools that support it.
Let's give an example of tools that leads developer to use it rigth way? (eg. that solve problems like SOA enablement of legacy applications...).

   Lukas
__._,_.___


SPONSORED LINKS
Computer software program Computer software spy Computer job
Database software Discount computer software


YAHOO! GROUPS LINKS




__,_._,___

Reply via email to