The acquisition and sharing of domain knowledge contained in software with a compliant sik architecture
Vasile Avram · International Journal of Engineering · 2015
The benefits and needs for extensive management towards the organizations require, among other things, to change architectures for a better adaptation to the era. The change argued in this paper refers to adding a component in the form of one or many companion repositories expressed as Resource Description Framework (RDF), to systematically acquire, structure, formalize, store and maintain domain described as business rules, for all business rules that are incorporated in the product itself. For every adopting this architecture, the companion repositories acts as vectors to manage, communicate, transfer and share what is called software inherited knowledge (SIK), like a genetic repository. SIK architectures refer mainly to that incorporates internally, mixed with its logic, the served domain business rules. It refers also partly to that uses externalized business rules but keeps also business rules internally incorporated and does not refer at all to business rules management systems that define and manipulate externally all business rules. As it is defined, SIK allows applications to inherit domains rules from other applications and direct (or little adapted) usage of those business rules, from the Business Rules Management System (BRMS) the company may have. The inheritance of business rules, by using SIK architecture, is different from the inheritance induced by the internal classes and objects, in object-oriented applications. One aim of this paper is to define and explain the SIK concept, together with all related concepts, from both theoretical and practical perspectives. Another aim of this paper is to exemplify how can be designed or adapted to be compliant with SIK architecture. The last aim is to outline and emphasize the major benefits, for all users and environments where the application is used, when adopting SIK architecture for applications or when buying applications complying with that architecture. Keywords management, Business rules, Software inherited (SIK), Software architecture.