The objective of this document(*)
is to provide some rational, structured access to an analysis of cognitive and agent architectures (for
more information on accessing the document, see the Reader's Guide). Twelve architectures have
been used for this preliminary analysis representing a wide range of
current architectures in artificial
intelligence (AI). The aim of the project is to facilitate both
an understanding of current architectures and provide insight to the
development of future, improved intelligent agent architectures.
This work was based on publications from 1992 and before and has not
been authorized by the researchers responsible for particular
architectures (see DISCLAIMER for additional
information).
Most BREs today are deployed as “decision services”, and are used in “stateless” transactions to make “decisions” as a part of a business process. A CEP application is instead processing multiple event streams and sources over time, which requires a “stateful” rule service optimized for long running. This is an important distinction, as a stateful BRE for long-running processes needs to have failover support - the ability to cache its working memory for application restarting or distribution. And of course long-running processes need to be very particular over issues like memory handling - no memory leaks allowed!
Every organization has 4 other domains in which BPM projects are executed; Corporate Performance Management (CPM), IT architecture Management (ITAM) and Governance Risks and Compliance (GRC), Core Application Framework (CAF/SAP). The Enterprise BPM framework can be also used in all these domains, which results in 5 maturity models including the ERP/SAP maturity model (see figure below).
at the core, enterprise architecture is very simple: it starts with the idea that one should plan technology purchases and development ahead of time and -- here's the important part -- that the business people, not technology people, should determine what is needed (the requirements).
This is EDA! Model your business events right and have their software representations travel in real-time through a global (enterprise wide) data space (call it an ESB), then you are offering your business huge opportunities. Think of connecting your global data space with those controlled by other enterprises: your fantasy is the limit.
Truviso continuously analyzes massive volumes of dynamic information—providing comprehensive visibility and actionable insights for any event, opportunity or trend on-demand. Truviso empowers decision-makers with continuous:
Analysis - always-on, game-changing analytics of streaming data
Visibility - dynamic, web-based dashboards and on-demand applications
Action - extensible, data-driven actions and alerts
Truviso's approach is based on years of pioneering research, leveraging industry standards, so it's fast to implement, flexible to configure, and easy to modify as your needs change over time.
For those unfamiliar with business-driven architecture, I believe the most viable, agile architectures will be comprised of a blend of architecture strategies, including (but not limited to) service-oriented architecture, event-driven architecture, process-based architecture, federated information, enterprise integration and open source adoption.
- leave anything related to transport, communication to other layers- use this revised CEP to express and execute event-relevant logic, the purpose of which is to translate the ambient events into relevant business events- have these business events trigger business processes (however lightweight you want to make them)- have these business processes invoke decision services implemented through decision management to decide what they should be doing at every step- have the business processes invoke action services to execute the actions decided by the decision services- all the while generating business events or ambient events- etc.
The Zachman Framework is a framework for enterprise architecture, which provides a formal and highly structured way of viewing and defining an enterprise.
The Framework in practice is used for organizing enterprise architectural "artifacts" in a way that takes into account both:
who the artifact targets for example, business owner and builder, and
what particular issue for example, data and functionality is being addressed.
These artifacts may include design documents, specifications, and models.[3]
The Framework is in essence a matrix,[4]. It is named after its creator John Zachman, who first developed the concept in the 1980s at IBM. It has been updated several times ever since.[5]
Das Zachman Framework ist ein 1987 von John Zachman konzipierter domänenneutraler Ordnungsrahmen zur Entwicklung von Informationssystemen.
Es bildet dabei einen Leitfaden, der Vorschläge enthält, welche Aspekte aus welchen Perspektiven Berücksichtigung finden sollten, um die IT-Architektur einer Unternehmung erfolgreich aufzustellen. Mit Hilfe dieser Modellierung kann sowohl die Dokumentation- als auch die Planung eines solchen Projekts unterstützt werden, wenn bspw. nachvollzogen werden soll, welche Entscheidungen welche technischen Umsetzungen nach sich gezogen haben.
M. LeMay, R. Nelli, G. Gross, und C. Gunter. HICSS '08: Proceedings of the Proceedings of the 41st Annual Hawaii International Conference on System Sciences, Seite 174. Washington, DC, USA, IEEE Computer Society, (2008)
A. Harter, A. Hopper, P. Steggles, A. Ward, und P. Webster. MobiCom '99: Proceedings of the 5th annual ACM/IEEE international conference on Mobile computing and networking, Seite 59--68. New York, NY, USA, ACM, (1999)
B. Schilit, N. Adams, und R. Want. In Proceedings of the Workshop on Mobile Computing Systems and Applications, Seite 85--90. IEEE Computer Society, (1994)