"We know gravity keeps us on earth."
André Born
We examine current trends in information technology with close attention:
- Business Rules Approach (BRA)
- Executable UML® (xUML®)
- Knowledge Management (KM)
- Aspect Oriented Analysis/Design/Programming (AOA/AOD/AOP)
Definition
A business rules approach is a methodology by which all business-relevant connections which are represented in an information system are implemented in one single place, i.e. they are specified in a non-technical form and completely separated from business data and user interfaces.
Benefits
A declarative business rules approach and its use..
- ...can be better understood by non-technical persons because common program languages or charts are written in a colloquial language.
- ...can adjust more rapidly to changes and/or new business requests than conventional program languages and databases.
Difficulties
- There is still an uncontrolled growth of incompatible concepts and products resulting from the innovative character of this approach.
- There is yet little experience on how projects can be approached systematically by using BRA and on how such an approach can be combined with conventional IT-systems in a meaningful way.
KnowGravity
KnowGravity is a member of the international Business Rules Group and contributes therewith to the consolidation and standardization of these concepts. KnowGravity supports the awareness of the Business Rules Approach in Europe with the European Business Rules Conference and in different customer projects. You find further information here.
KnowPapers
 |
KnowFuture - BRA | General introduction to the subject of Business Rules |
|
KnowFuture - PuB | Business Rules in the case study "Products and orders" |
Business-Rules Conference
KnowGravity organises, together with Model Systems and LibRT the
More details, watch out www.eurobizrules.com
Definition
The extension of UML® with a precise action language and the renouncement of semantically weak UML® elements make a direct executable UML® model possible without the error-prone detour of programming. The term xUML® stands for eXecutable UML®.
Benefits
xUML® models are directly executable, therefore ...
- ...tests can be made already in the specification phase
- ...logical errors can be located and repaired on the high level of the UML®
- ...modelling persons don't have to concentrate on the technical requirements and won't lose time with implementation details.
The automatic generation of code, along with immediate testability, the xUML® models optimally support the MDA approach. Additionally, a xUML® model can be formally verified, whereby with safety sensitive applications in particular it can be shown that the logical model is correct.
Difficulties
- Most of today's xUML® tools only support a small subset of the UML® notation and makes so the way to elegant solutions complicated.
- "Programming" in model level is still unusual today.
KnowGravity
KnowGravity is developing a xUML® simulator based on the CASSANDRA platform with the aim of supporting the complete UML® notation. We offer a favourable xUML® starter kit for interested companies (as part of a customer project) which includes the development of a xUML® model.
Definition
KM is a concept, in which an enterprise consequently gathers, organizes, analyzes and shares its knowledge. It also involves information on who has what knowledge, and which knowledge is needed.
Benefits
As one of the most precious business resources knowledge...
- ...can be made explicit through knowledge management.
- ...can be located within the enterprise.
- ...can be transferred by know-how carriers and know-how consumer
Difficulties
In our opinion the main difficulties are:
- Before one can benefit, a sufficient large community must gain the knowledge during a substantial period (even if this takes place partly automatically).
- Social/humane opposition might often obstruct the free passing on of personal knowledge.
KnowGravity
KnowGravity promotes and supports the sharing of knowledge within the organisation and between its customers.
Aspect Oriented Analysis/Design/Programming (AOA/AOD/AOP)
Definition
With the specification and implementation of an information system only a specific aspect of a business object is used unlike previously when a business object was used as a basic modulation unit. Such a view can be technically justified (e.g. the aspect "customer" of the object "person") or have a technical background (e.g. the aspect "tracing" for all objects).
Benefits
- Larger IT projects can be systematically subdivided into subprojects by early identification of aspects.
- The modelling of Aspects results in very clean and narrow interfaces between business and technical components, which can also be realised in different technologies.
- By means of technical aspects, infrastructure services can be realized at one single place and many other objects (or aspects) can be added in a standardised way.
Difficulties
- Only few tools support the AOA/AOD/AOP approach at the moment.
- The criteria for the systematic formation of technical aspects still have to be developed.
KnowGravity
KnowGravity employees already use the aspects concept since 1994 in customer's projects (from AOA to AOP) and also teach this topic in training courses for many years. Besides, CASSANDRA actively supports modelling aspects.
KnowPapers
|
What is an Object | Motivation for aspects and scope of objects |