I don't think the issue is to quantify business process features but to quantify business processes. The central issue is to define what business process is. If this is done incorrectly, we won't go anythere. To do it correctly needs a new theory or a new language. To speak a new language we need to have a new eye to see the same land into a new world. To have a new eye requires a new philosophy and worldview. The challenge is that we often do not know what our old worldview is let alone transformation of it.
Jerry Zhu --- ash galal <[EMAIL PROTECTED]> wrote: > From my background and experience, I found out that > most of business processes tend to be informal and > subjective which is very difficult to quantify. > We need to quantify such features of the business > processes to enable automatic business processes > composition. > But this is very challenging, because we need to > properly formulate the descriptive and subjective > requirements into quantifiable, objective, and > machine-readable formats. In addition, the current > Web > services specifications lack the facility to define > comprehensive relationships among business entities, > business services, and operations. Without such > relationships we will not been able to optimize > business process composition. Which I think it is > out > of SOA architecture. It is business architecture may > be. Any ideas? > I noticed also that this part is almost ignored by > vendors reference architecture or white papers but > only addressed by IBM SOA reference architecture to > some extent. > I think this area needs more researches and I think > it > needs business people, not business analyst, who > have > practical business experience, work hand-on-hand > with > IT architects. > I don't think that any W3C or OASIS specifications > for > WS-* can address such area since OASIS SOA > definition > is a technical one. > Your comments is highly appreciated > > Ashraf Galal > >
