Just to follow up on   Why OO Sucks   thread from LtU DG.

Isaac asks "Could you write the top 5 things that OO brings to problem analysis and to solution design?"

My list is not orthogonal but here it goes anyways: OOAD helps us focus on

• emphasis on use cases
• roles of stakeholers
• identities of "domain objects" (or rather just things that matter to the problem - TTMTTP ;-)
• responsibilities of the domain objects/TTMTTP (and their implementations - components, classes, objects, modules, etc in PL whether they are OOPL or not).
• relations between the TTMTTPs and also interactions between TTMTTPs and stakeholders

In the begening and in the end, identy and act identification are at the core of (OO) AD.

5:19:41 PM  #  

BPMI.org Publishes BPML 1.0 and Business Process Modeling Notation (BPMN) Working Draft. The Business Process Management Initiative (BPMI.org) has announced the final draft for the Business Process Modeling Language (BPML 1.0) and the first public working draft for the Business Process Modeling Notation (BPMN). This business process modeling language and graphical notation can be used by business analysts for the modeling of executable and manageable business processes. Mappings from BPMN to BPML and BPEL4WS are documented. [The XML Cover Pages]

Okay, I had a small part in introducing my old company to BPMI a few years ago. BPMI took two years to write an XML "application" that is BPML spec. But there is no APIs or SDKs available from any of its large number of members. IBM already has java for BPEL4WS shipping. Weblogic is hedging its bets by supporting both. My guess is BPEL will win just because of early adopters of Java coders because comparing BPEL and BPML side-by-side yields few enlightments.

11:13:40 AM  #