Main Menu
Home
News
Contact Us
Search
Newsletter
Company
Services
Research
Workshops
BMO
Repositories
EAS
Browsers
Web Services
Shop
Best Practices


Key Differentiators PDF Print E-mail
Knowledge-Driven Enterprise Engineering is totally different from traditional software engineering. But what are the key differentiators? We have distilled the following 10 factors that stakeholders believe give them tremendous value:
  1. Knowledge-Driven Enterprise Engineering relies on the composition paradigm. Composition describes the process of assembling and orchestrating a digital enterprise organism. In a more detailed view, composition is the orchestrated assembly of data, processes and services.

  2. The entire enterprise is regarded as a coherent universe, meaning that there are no isolated data, process and application islands. There is only one model type with well-defined syntax and semantics.

  3. The activities of business architect, process designer and application designer are combined in one role: the role of the business analyst. Business analysts fulfill composition roles.

  4. Composition is a collaboration-driven effort that involves non-technical business subject matter experts and business analysts. In contrast, traditional application development still is an IT expert-driven effort.

  5. Knowledge-Driven Enterprise Engineering combines three principles: meta data-driven, model-driven and component-based. All of these principles materialize in an Integrated Composition and Execution Environment (ICEE), which supports the entire engineering process.

  6. Knowledge-Driven Enterprise Engineering relies on a semantically rich ontology-based knowledge asset repository. Semantic integration is not an afterthought but is enforced from the start.

  7. Knowledge-Driven Enterprise Engineering produces dynamic and executable models. Changes to the model immediately impact the execution without requiring intermediate recompiles and coding. Knowledge-Driven Enterprise Engineering implements the 'model > validate > execute' paradigm, which forms a distinct contrast to the traditional 'model > code > debug > test > install > execute' paradigm.

  8. With Knowledge-Driven Enterprise Engineering, business process models are always explicit, rather than implicit (i.e. coded processes). Also, Knowledge-Driven Enterprise Engineering supports both deterministic and non-deterministic processes (case management). Processes are built for rapid modification and extension, and there is no entry barrier for processes built for short-lived situational needs. The result is higher process flexibility and operational transparency at the organizational level.

  9. Knowledge-Driven Enterprise Engineering is a highly iterative process, supporting iterative data and process refinement as well as iterative application evolution. Iterative and incremental engineering with short iterations provides more frequent feedback from stakeholders and users.

  10. Knowledge-Driven Enterprise Engineering is a very lean engineering process that produces consistent, predictable results. It forms a stark contrast to the traditional software engineering process that is considered complex and typically requires 20+ role types with expert IT knowledge in various specialist domains.

 
< Prev   Next >
   Home