Let’s start by recapping decisions services. Decision services are services, generally stateless ones, that answer business questions for other services. Decision Services typically have no side effects so they can be called whenever they are needed without the caller worrying that something will change in the system. This means that database updates, event generation or other actions taken as a result of the decision are taken by the caller not by the Decision Service. This is not 100% true but works as a general rule. To work, Decision Services need to contain all the logic and algorithms necessary to make the decision correctly.
Continuing some posts on next generation warranty systems in the build up to speaking at the Warranty Chain management conference I thought I would contrast how current generation warranty systems handle critical decisions with how next generation systems do so.
As IBM absorbs ILOG it will be important that it continue to invest is this multi-platform approach. Not only are there some nice features in the .Net product (that I for one would like to see available to the Java product) but decision management with business rules is, for most companies, a multi-platform problem. The value of using business rules to decision management comes in part from making sure the same rules are used everywhere they are supposed to be used. While deploying business rules in Decision Services on SOA makes this easier, the best solution is to allow the rules to be packaged up and deployed as Java components, Web Services, .Net assemblies or COBOL code so that they can run natively on all the platforms that run the business.
ebruary second the Open Group released a new version of its framework TOGAF 9. TOGAF started out as a Technical Infrastructure Framework, started by the US Department of Defense in 1995 with TOGAF 1, and has grown out to a full framework for enterprise architecture in TOGAF version 9.
So why do you need a framework like TOGAF 9. From its origin IT was introduced to speedup business process so companies could make more money faster. Somewhere along the way IT became a technology driven, self sustaining machine where we all needed more gadgets without contributing to the added business value. Enterprise architecture is one of the ways to get the primary goal of IT back within normal costs and in control for a organization.
Open source is ready for EDW. Because open source is designed to be modular, an enterprise can start with one piece - say ETL or reporting - and can add on as needed. For comparable power and features an open source solution in this arena can cost 10 to 20 times less than a proprietary product. Whether large or small, companies today are being asked to do more with less. With open source, you can have an EDW without compromise.
Ein großer Teil der Forschung in der Wirtschaftsinformatik ist darauf gerichtet, innovative Artefakte und korrespondierende Handlungssysteme zu entwerfen und zu erproben. Ein solcher konstruktionsorientierter Forschungsansatz bietet spezifische Chancen, die allerdings nur dann überzeugend genutzt werden können, wenn er methodisch überzeugend fundiert wird.
Kontextadaption ist ein Begriff aus der Softwaretechnik, der verwendet wird, um technische Systeme zu bezeichnen, die ihre Struktur, Funktionalität oder Verhalten zur Laufzeit ändern können, um sich an unterschiedliche Umgebungsgegebenheiten zu richten.
J. Schiefer, S. Rozsnyai, C. Rauscher, and G. Saurer. DEBS '07: Proceedings of the 2007 inaugural international conference on Distributed event-based systems, page 198--205. New York, NY, USA, ACM, (2007)