Projects Home







Digital Business Ecosystems

Business Modeling & Integration Task Force
The OMG BMI Domain Task Force is devoted to the development of specifications for business modeling. BMI specifications in progress include Semantics of Business Vocabulary and Business Rules, Production Rule Representation, Organizational Structure Metamodel, Business Process Definition Metamodel, Business Process Runtime Interface, Business Process Modeling Notation, Business Motivation Model, and Business Rule Management Model.

>> Read More

Digital Business Ecosystem
The DBE is an integrated project of the European Commission Framework Prrogramme 6. that invovles over 100 researchers from industry, academia, and local government agencies in five countries. DBE address the technical middleware, natural language modeling, and the sociological aspects of uptake of the technology by prospective users, aiming to establish a self-organizing infrastructure for peer to peer transactions, catering especially to small and medium enterprises (SMEs). An important part of DBE is natural language modeling and registration by non-technical SMEs so they can be discovered by other SMEs and then engage in peer-to-peer transactions. DBE has adopted SBVR for its Business Modeling Language, and Hendryx's Architecture of Business Modeling. Stan Hendryx is a member of the DBE Strategic Advisory Board.

Pierfranco Ferronato,, Chief Architect of DBE described DBE in this way:

"The Digital Business Ecosystem (DBE) project, as a consequence of non irrelevant political and sociological requirements, has to build an Internet-wide open SOA environment where business services can be modeled, published, searched, and consumed (this is really an over simplification of the its capability). The "open" term in the specification has meant for us also to try avoiding single point of failure in the architecture. In SOA the infrastructure relies on UDDI registries that, even in version 3, are pretty static (relation and delegation need to be defined manually and endpoint addresses need to be kept updated: what about mobile devices?). The P2P in the DBE is related to the implementation technology of the service registry (implemented by SUN), which is also able to deliver proxy objects to requestors. Last but not least, the registry entries are kept in sync with the availability of the service endpoints; it's in the nature of a P2P re implementation of Jini.

"This is not to say that the DBE is a P2P based SOA project, rather there is some P2P in the DBE which enables a more resilient architecture. From the business modelling and execution perspective the P2P is completely transparent.

"It might be interesting to notice that in the healthcare industry, when integrating health record (HR) of patients the existence of a centralized (although clustered) registry is a major concern (NICTIZ, NHS, EHRS, IHE). A couple of project are actually moving to P2P based registry for such a SOA projects (IBIS, Italy). The point IMO is that SOA as it is actually, is clumsy when scaling up to inter-enterprise environments with a highly dynamic network of requestors and providers. There is also an interesting aspect related to Scale Free network."


505 South Murphy Ave :: Sunnyvale, California 94086
Ph: 408-773-8089 :: Mobile 408-218-9455