<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"><channel rdf:about="https://www.bibsonomy.org/user/cschie/systems"><title>BibSonomy bookmarks for /user/cschie/systems</title><link>https://www.bibsonomy.org/user/cschie/systems</link><description>BibSonomy RSS Feed for /user/cschie/systems</description><items><rdf:Seq><rdf:li rdf:resource="http://www.zabbix.com/"/><rdf:li rdf:resource="http://de.wikipedia.org/wiki/Kontextsensitivität_(Informatik)"/><rdf:li rdf:resource="http://www.qualiasystems.co.uk/applications"/><rdf:li rdf:resource="http://en.wikipedia.org/wiki/Context-aware_pervasive_systems"/><rdf:li rdf:resource="http://www.edmblog.com/weblog/2008/10/the-evolution-o.html"/><rdf:li rdf:resource="http://www.thecepblog.com/2009/02/25/reasoning-and-complexity/"/><rdf:li rdf:resource="http://jtonedm.com/2009/03/04/19th-century-decision-management/"/><rdf:li rdf:resource="http://epthinking.blogspot.com/2009/03/international-banking-systems-article.html"/><rdf:li rdf:resource="http://books.google.co.uk/books?id=1OE-Oj4l9mEC"/><rdf:li rdf:resource="http://blog.elementallinks.net/2009/02/health-it-stimulus-check-to-spend-check-out-the-practical-guide-to-soa-in-healthcare.html"/><rdf:li rdf:resource="http://www.ibm.com/developerworks/data/library/techarticle/dm-0809byrne/"/><rdf:li rdf:resource="http://vsr.informatik.tu-chemnitz.de/publications/2008/04"/><rdf:li rdf:resource="http://www.dulcian.com/papers/ODTUG/2004/ODTUG%202004_Muhammad_Testing%20Methodology.htm"/></rdf:Seq></items></channel><item rdf:about="http://www.zabbix.com/"><title>Homepage of ZABBIX :: An Enterprise-Class Open Source Distributed Monitoring Solution</title><description></description><link>http://www.zabbix.com/</link><dc:creator>cschie</dc:creator><dc:date>2009-03-23T15:44:39+01:00</dc:date><dc:subject>systems networks open monitoring source event tool processing </dc:subject><content:encoded>&lt;a itemprop=&#034;url&#034; data-versiondate=&#034;2009-03-23T15:44:39+01:00&#034; href=&#034;http://www.zabbix.com/&#034; rel=&#034;nofollow&#034; class=&#034;description-link&#034;&gt;http://www.zabbix.com/&lt;/a&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/systems"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/networks"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/open"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/monitoring"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/source"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/event"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/tool"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/processing"/></rdf:Bag></taxo:topics></item><item rdf:about="http://de.wikipedia.org/wiki/Kontextsensitivität_(Informatik)"><title>Kontextsensitivität (Informatik) – Wikipedia</title><description>Kontextsensitivität (engl. context awareness, auch Kontextabhängigkeit) bezeichnet das Verhalten von Anwendungsprogrammen, die Informationen über ihren „Kontext“, also ihre Umgebung, benutzen, um ihr Verhalten darauf abzustimmen.
Die Basis, auf der diese Systeme arbeiten, sind Informationen, welche durch unterschiedlichste Quellen oder Sensoren zur Verfügung gestellt werden. Mit Hilfe dieser Informationen werden Schlüsse über den Kontext gezogen. Der ermittelte Kontext wird von der Anwendung verwendet, um ihr Verhalten anzupassen, insbesondere das Verhalten der Benutzungsschnittstelle. Kontext wird z. B. definiert als „... jegliche Information, die genutzt werden kann, um die Situation einer Entität zu charakterisieren.“[1]. Der Gebrauch von Kontextinformationen ist am häufigsten mit dem Zeit- und Ortsaspekt von Personen verbunden. Jedoch können beliebig weitere Aspekte in ein Kontextmodell aufgenommen werden, wenn entsprechende Quellen oder Sensoren dazu existieren. Dieses können beispielsweise Archivdaten oder Vitalwerte von Personen, die Temperatur in einer Umgebung oder auch die Beziehungen zwischen Personen sein.
Das Ziel der Entwicklung kontextsensitiver Anwendungen ist es, eine höhere Nutzwert als mit klassischen Anwendungen zu erreichen.</description><link>http://de.wikipedia.org/wiki/Kontextsensitivität_(Informatik)</link><dc:creator>cschie</dc:creator><dc:date>2009-03-18T13:24:21+01:00</dc:date><dc:subject>applications behavior context-aware sensor systems wiki </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;Kontextsensitivität (engl. context awareness, auch Kontextabhängigkeit) bezeichnet das Verhalten von Anwendungsprogrammen, die Informationen über ihren „Kontext“, also ihre Umgebung, benutzen, um ihr Verhalten darauf abzustimmen.
Die Basis, auf der diese Systeme arbeiten, sind Informationen, welche durch unterschiedlichste Quellen oder Sensoren zur Verfügung gestellt werden. Mit Hilfe dieser Informationen werden Schlüsse über den Kontext gezogen. Der ermittelte Kontext wird von der Anwendung verwendet, um ihr Verhalten anzupassen, insbesondere das Verhalten der Benutzungsschnittstelle. Kontext wird z. B. definiert als „... jegliche Information, die genutzt werden kann, um die Situation einer Entität zu charakterisieren.“[1]. Der Gebrauch von Kontextinformationen ist am häufigsten mit dem Zeit- und Ortsaspekt von Personen verbunden. Jedoch können beliebig weitere Aspekte in ein Kontextmodell aufgenommen werden, wenn entsprechende Quellen oder Sensoren dazu existieren. Dieses können beispielsweise Archivdaten oder Vitalwerte von Personen, die Temperatur in einer Umgebung oder auch die Beziehungen zwischen Personen sein.
Das Ziel der Entwicklung kontextsensitiver Anwendungen ist es, eine höhere Nutzwert als mit klassischen Anwendungen zu erreichen.&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/applications"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/behavior"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/context-aware"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/sensor"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/systems"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/wiki"/></rdf:Bag></taxo:topics></item><item rdf:about="http://www.qualiasystems.co.uk/applications"><title>Applications | Qualia Systems | Incanto</title><description>Incanto can be implemented to solve the following kinds of decision making problems:

Problems where the expert rule set is large or complex. Incanto is especially suited to managing complexity.
Problems where the rules change frequently. Incanto`s testing capabilities mean amended rule sets can be introduced swiftly and with confidence.
Problems where the expert rules set needs to be applied to large volumes of data. 

Where all these conditions apply Incanto is probably the only good answer in the market at present.</description><link>http://www.qualiasystems.co.uk/applications</link><dc:creator>cschie</dc:creator><dc:date>2009-03-14T12:33:41+01:00</dc:date><dc:subject>applications business decision event rules systems tool </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;Incanto can be implemented to solve the following kinds of decision making problems:

Problems where the expert rule set is large or complex. Incanto is especially suited to managing complexity.
Problems where the rules change frequently. Incanto`s testing capabilities mean amended rule sets can be introduced swiftly and with confidence.
Problems where the expert rules set needs to be applied to large volumes of data. 

Where all these conditions apply Incanto is probably the only good answer in the market at present.&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/applications"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/business"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/decision"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/event"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/rules"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/systems"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/tool"/></rdf:Bag></taxo:topics></item><item rdf:about="http://en.wikipedia.org/wiki/Context-aware_pervasive_systems"><title>Context-aware pervasive systems - Wikipedia, the free encyclopedia</title><description>Context-aware computing refers to a general class of mobile systems that can sense their physical environment, i.e., their context of use, and adapt their behavior accordingly. Such systems are a component of a ubiquitous computing or pervasive computing environment. Three important aspects of context are: (1) where you are; (2) who you are with; and (3) what resources are nearby. Although location is a primary capability, location-aware does not necessarily capture things of interest that are mobile or changing. Context-aware in contrast is used more generally to include nearby people, devices, lighting, noise level, network availability, and even the social situation; e.g., whether you are with your family or a friend from school.</description><link>http://en.wikipedia.org/wiki/Context-aware_pervasive_systems</link><dc:creator>cschie</dc:creator><dc:date>2009-03-13T17:03:55+01:00</dc:date><dc:subject>awareness behavior context context-aware pervasive systems wiki </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;Context-aware computing refers to a general class of mobile systems that can sense their physical environment, i.e., their context of use, and adapt their behavior accordingly. Such systems are a component of a ubiquitous computing or pervasive computing environment. Three important aspects of context are: (1) where you are; (2) who you are with; and (3) what resources are nearby. Although location is a primary capability, location-aware does not necessarily capture things of interest that are mobile or changing. Context-aware in contrast is used more generally to include nearby people, devices, lighting, noise level, network availability, and even the social situation; e.g., whether you are with your family or a friend from school.&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/awareness"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/behavior"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/context"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/context-aware"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/pervasive"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/systems"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/wiki"/></rdf:Bag></taxo:topics></item><item rdf:about="http://www.edmblog.com/weblog/2008/10/the-evolution-o.html"><title>The evolution of BRMS (part 1) - Enterprise Decision Management - a Weblog</title><description>For those of you that could not make it, I wanted to give you the gist of what I presented.  This presentation covers the evolution of the business rules technology focusing first on the drivers that forced the market to shift its focus from Business Rules Engines (BRE) to Business Rules Management Systems (BRMS).  In a nutshell, the main ideas are summarized below.  In a few days, the recording will also be posted on our community site for your convenience.</description><link>http://www.edmblog.com/weblog/2008/10/the-evolution-o.html</link><dc:creator>cschie</dc:creator><dc:date>2009-03-13T10:51:46+01:00</dc:date><dc:subject>BRE BRMS business decision engine enterprise evolution management rules systems technology </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;For those of you that could not make it, I wanted to give you the gist of what I presented.  This presentation covers the evolution of the business rules technology focusing first on the drivers that forced the market to shift its focus from Business Rules Engines (BRE) to Business Rules Management Systems (BRMS).  In a nutshell, the main ideas are summarized below.  In a few days, the recording will also be posted on our community site for your convenience.&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/BRE"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/BRMS"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/business"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/decision"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/engine"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/enterprise"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/evolution"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/management"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/rules"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/systems"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/technology"/></rdf:Bag></taxo:topics></item><item rdf:about="http://www.thecepblog.com/2009/02/25/reasoning-and-complexity/"><title>Reasoning and Complexity | Cyberstrategics Complex Event Processing Blog</title><description>Some definitions key on the question of the probability of encountering a given condition of a system once characteristics of the system are specified. Warren Weaver has posited that the complexity of a particular system is the degree of difficulty in predicting the properties of the system if the properties of the system’s parts are given. In Weaver’s view, complexity comes in two forms: disorganized complexity, and organized complexity. [2] Weaver’s paper has influenced contemporary thinking about complexity. [3]</description><link>http://www.thecepblog.com/2009/02/25/reasoning-and-complexity/</link><dc:creator>cschie</dc:creator><dc:date>2009-03-09T16:49:05+01:00</dc:date><dc:subject>complex complexity definition event processing systems </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;Some definitions key on the question of the probability of encountering a given condition of a system once characteristics of the system are specified. Warren Weaver has posited that the complexity of a particular system is the degree of difficulty in predicting the properties of the system if the properties of the system’s parts are given. In Weaver’s view, complexity comes in two forms: disorganized complexity, and organized complexity. [2] Weaver’s paper has influenced contemporary thinking about complexity. [3]&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/complex"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/complexity"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/definition"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/event"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/processing"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/systems"/></rdf:Bag></taxo:topics></item><item rdf:about="http://jtonedm.com/2009/03/04/19th-century-decision-management/"><title>19th Century Decision Management » JT on EDM</title><description>Substitute a standard web services interface for a speaking tube, a business rules management system for his encyclopedic knowledge of policies and regulations, data mining or predictive analytics for his customer knowledge and adaptive control for his experimentation and you have Decision Management. The Answerer but on an industrial scale.</description><link>http://jtonedm.com/2009/03/04/19th-century-decision-management/</link><dc:creator>cschie</dc:creator><dc:date>2009-03-05T13:47:34+01:00</dc:date><dc:subject>EDM adaptive analytics business control decision enterprise management policies predictive regulations rules services systems web </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;Substitute a standard web services interface for a speaking tube, a business rules management system for his encyclopedic knowledge of policies and regulations, data mining or predictive analytics for his customer knowledge and adaptive control for his experimentation and you have Decision Management. The Answerer but on an industrial scale.&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/EDM"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/adaptive"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/analytics"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/business"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/control"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/decision"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/enterprise"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/management"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/policies"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/predictive"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/regulations"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/rules"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/services"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/systems"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/web"/></rdf:Bag></taxo:topics></item><item rdf:about="http://epthinking.blogspot.com/2009/03/international-banking-systems-article.html"><title>Event Processing Thinking: International Banking Systems article on &#034;Event Horizon&#034;</title><description>Various of EP applications are mentioned besides algorithmic trading are:  external surveillance by regulators, risk management, auditing, market depth analysis and more.</description><link>http://epthinking.blogspot.com/2009/03/international-banking-systems-article.html</link><dc:creator>cschie</dc:creator><dc:date>2009-03-03T10:02:49+01:00</dc:date><dc:subject>application article banking event international processing systems thinking </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;Various of EP applications are mentioned besides algorithmic trading are:  external surveillance by regulators, risk management, auditing, market depth analysis and more.&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/application"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/article"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/banking"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/event"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/international"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/processing"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/systems"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/thinking"/></rdf:Bag></taxo:topics></item><item rdf:about="http://books.google.co.uk/books?id=1OE-Oj4l9mEC"><title>Semantics in Business Systems: The ... - Google Buchsuche</title><description>Semantics in Business Systems begins with a description of what semantics are and how they affect business systems. It examines four main aspects of the application of semantics to systems, specifically: How do we infer meaning from unstructured information, how do application systems make meaning as they operate, how do practitioners uncover meaning in business settings, and how do we understand and communicate what we have deduced? This book illustrates how this applies to the future of application system development, especially how it informs and affects Web services and business rule- based approaches, and how semantics will play out with XML and the semantic Web. The book also contains a quick reference guide to related terms and technologies. It is part of Morgan Kaufmann&#039;s series of Savvy Manager&#039;s Guides.</description><link>http://books.google.co.uk/books?id=1OE-Oj4l9mEC</link><dc:creator>cschie</dc:creator><dc:date>2009-02-27T17:20:47+01:00</dc:date><dc:subject>business ontologies rules semantic systems </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;Semantics in Business Systems begins with a description of what semantics are and how they affect business systems. It examines four main aspects of the application of semantics to systems, specifically: How do we infer meaning from unstructured information, how do application systems make meaning as they operate, how do practitioners uncover meaning in business settings, and how do we understand and communicate what we have deduced? This book illustrates how this applies to the future of application system development, especially how it informs and affects Web services and business rule- based approaches, and how semantics will play out with XML and the semantic Web. The book also contains a quick reference guide to related terms and technologies. It is part of Morgan Kaufmann&amp;#039;s series of Savvy Manager&amp;#039;s Guides.&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/business"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/ontologies"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/rules"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/semantic"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/systems"/></rdf:Bag></taxo:topics></item><item rdf:about="http://blog.elementallinks.net/2009/02/health-it-stimulus-check-to-spend-check-out-the-practical-guide-to-soa-in-healthcare.html"><title>Check out the Practical Guide to SOA in Healthcare</title><description></description><link>http://blog.elementallinks.net/2009/02/health-it-stimulus-check-to-spend-check-out-the-practical-guide-to-soa-in-healthcare.html</link><dc:creator>cschie</dc:creator><dc:date>2009-02-19T16:50:04+01:00</dc:date><dc:subject>Michelson abbildung architecture boundary systems </dc:subject><content:encoded>&lt;a itemprop=&#034;url&#034; data-versiondate=&#034;2009-02-19T16:50:04+01:00&#034; href=&#034;http://blog.elementallinks.net/2009/02/health-it-stimulus-check-to-spend-check-out-the-practical-guide-to-soa-in-healthcare.html&#034; rel=&#034;nofollow&#034; class=&#034;description-link&#034;&gt;http://blog.elementallinks.net/2009/02/health-it-stimulus-check-to-spend-check-out-the-practical-guide-to-soa-in-healthcare.html&lt;/a&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/Michelson"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/abbildung"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/architecture"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/boundary"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/systems"/></rdf:Bag></taxo:topics></item><item rdf:about="http://www.ibm.com/developerworks/data/library/techarticle/dm-0809byrne/"><title>IBM Industry Models and ILOG business rules management systems, Part 1: Define business rules using IBM Industry Models</title><description></description><link>http://www.ibm.com/developerworks/data/library/techarticle/dm-0809byrne/</link><dc:creator>cschie</dc:creator><dc:date>2009-02-10T18:38:45+01:00</dc:date><dc:subject>IBM ILOG business management model rules systems </dc:subject><content:encoded>&lt;a itemprop=&#034;url&#034; data-versiondate=&#034;2009-02-10T18:38:45+01:00&#034; href=&#034;http://www.ibm.com/developerworks/data/library/techarticle/dm-0809byrne/&#034; rel=&#034;nofollow&#034; class=&#034;description-link&#034;&gt;http://www.ibm.com/developerworks/data/library/techarticle/dm-0809byrne/&lt;/a&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/IBM"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/ILOG"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/business"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/management"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/model"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/rules"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/systems"/></rdf:Bag></taxo:topics></item><item rdf:about="http://vsr.informatik.tu-chemnitz.de/publications/2008/04"><title>A Descriptive Approach for the Lifecycle Support of Distributed Web-based Systems</title><description></description><link>http://vsr.informatik.tu-chemnitz.de/publications/2008/04</link><dc:creator>cschie</dc:creator><dc:date>2009-02-02T19:55:18+01:00</dc:date><dc:subject>descriptive lifecycle systems </dc:subject><content:encoded>&lt;a itemprop=&#034;url&#034; data-versiondate=&#034;2009-02-02T19:55:18+01:00&#034; href=&#034;http://vsr.informatik.tu-chemnitz.de/publications/2008/04&#034; rel=&#034;nofollow&#034; class=&#034;description-link&#034;&gt;http://vsr.informatik.tu-chemnitz.de/publications/2008/04&lt;/a&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/descriptive"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/lifecycle"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/systems"/></rdf:Bag></taxo:topics></item><item rdf:about="http://www.dulcian.com/papers/ODTUG/2004/ODTUG%202004_Muhammad_Testing%20Methodology.htm"><title>Testing Methodology for Business-Rules Based Systems</title><description>Testing Methodology For Business Rules-Based Systems</description><link>http://www.dulcian.com/papers/ODTUG/2004/ODTUG%202004_Muhammad_Testing%20Methodology.htm</link><dc:creator>cschie</dc:creator><dc:date>2008-12-16T08:40:31+01:00</dc:date><dc:subject>Testing business methodology rules systems </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;Testing Methodology For Business Rules-Based Systems&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/Testing"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/business"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/methodology"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/rules"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/systems"/></rdf:Bag></taxo:topics></item></rdf:RDF>