Promotor Prof. dr. ir. J.M. Versendaal, Open Universiteit Co-promotoren Dr. ir. R.G. Slot MBA, Hogeschool Utrecht Dr. ing. M.M. Zoet, Zuyd Hogeschool Uit de Nederlandse samenvatting: "Het is voor organisaties van belang om besluitvorming en zogenaamde 'bedrijfslogica' goed in te richten. Organisaties in het algemeen, en zeker ook overheidsinstellingen, maken meer en meer gebruik van (semi-)geautomatiseerde besluitvormingsprocessen bij het leveren van hun producten en diensten. Organisaties krijgen grip op de nale-ving van wet- en regelgeving door de besluitvormingsprocessen goed te beheren. Een adequate vertaling van wet- en regelgeving naar producten en diensten is hierbij no-dig. Business Rules Management (BRM) maakt een en ander mogelijk. Het meeste onderzoek dat wordt uitgevoerd naar BRM kan worden geclassificeerd als technisch (vanuit een informatietechnologieperspectief). Echter, onderzoek naar de implementatie van BRM in de organisatie (vanuit een informatiesysteemperspectief), inclusief het beschouwen van allerlei organisatorische aspecten, ontbreekt groten-deels. Bovendien houdt het bestaande onderzoek naar BRM niet altijd voldoende re-kening met de praktische toepassing van onderzoeksresultaten; met andere woorden: kan een organisatie de voorgestelde theorie of het opgeleverde resultaat daadwerke-lijk gebruiken?"
Author supplied: "Abstract—Software architecture compliance checking (SACC) is an approach to monitor the consistency between the intended and the implemented architecture. In case of static SACC, the focus is mainly on the detection of dependencies that violate architectural relation rules. Interpretation of reported violations may be cumbersome, since the violations need to be connected to architectural resolutions and targeted qualities such as maintainability and portability. This paper describes an SACC case study which shows that inclusion of different types of rules in the SACC process enhances reasoning on architecture violations, especially if a rule type is related to specific architectural pattern. The SACC is performed with HUSACCT, an SACC-tool that provides rich sets of module and rule types in support of patterns such as layers, facade, and gateway. The case system is a governmental system developed in C#, which follows the .NET common application architecture. Even though the system appeared to be well-structured, the SACC revealed that 10 of the 17 architectural rules were violated."
From the publishers' website: The goal of this research is to define a method for configuring a collaborative business rules management solution from a value proposition perspective. In an earlier published study (Business rules management solutions: added value by means of business interoperability. In: van Sinderen M, Oude Luttighuis P, Folmer E, Bosms S (eds), International IFIP working conference on enterprise interoperability, vol 144. Springer, Twente, pp 145---157, 2013) we took a business rules perspective on interorganisational collaboration optimization, when we addressed the question what the relation was between types of business interoperability and an organisation's business rules management solution. Different types of collaboration were defined and subsequently combined with eleven identified types of service systems; these service systems together make up the business rules management solution. In this paper we re-address and -present our earlier work, yet based on the findings, we extend it with the construction of a method for determining the configuration of collaborative business rules management solutions. This method is tested by applying it to a case study at an alliance of airlines. Presented results provide a grounded basis from which empirical and practical research on business rules management solutions can be further explored.
LINK
