Abstract

In order to remain useful, it is important for software to evolve according to the changes in its business environment. Business rules, which can be used to represent both user requirements and conditions to which the system should conform, are considered as the most volatile part in today's software applications. Their changes bring high impact on both the business processes and the software itself. In this paper, we present an approach that considers business rules as an integral part of a software system and its evolution. The approach transcends the areas of requirements specification and software design. We develop the Business Rule Model to capture and specify business rules, and the Link Model to relate business rules to the metamodel level of software design elements. The aim is to improve requirements traceability in software design, as well as minimizing the efforts of software changes due to the changes of business rules. The approach is demonstrated using examples from an industrial application.

Author Keywords: Software evolution; Business rules; Software architecture/design; User requirements

Article Outline

1. Introduction

2. Problem background

3. Business rules and evolvable software

3.1. Business rules modelling

3.2. Evolvable software architecture

4. Overview of the MBRM approach

5. The MBRM mapping metamodel

5.1. The business rule model

5.2. The software design metamodel

5.3. The link model

6. The case study

6.1. The business rules

6.2. The preliminary software design

6.3. Business rule mapping

7. Conclusions and future developments

Acknowledgements

References

Vitae