Business Rules in Software Development

Sammanfattning: Business rules represent policies, procedures and constraints regarding how an enterprise conducts its business. BR(s) often focus on access control issues and may consist of business calculation and are evidently important for organizations. Their value has also been recognized within the information system (IS) domain, mostly because of their ability to make applications flexible and amendable to change. Problematic issues includes: the quality of software engineering projects often suffers due to the large gap between the way stakeholders present their requirements and system analysts capture and express those requirements and information systems often fail because their requirements are poorly defined. This thesis is devoted to the study of business rules in software development life cycle. Software development life cycle contains different phases but this study concentrates on how system analysts work with business rules in the requirement specification phase and which approach they are using either BR-oriented or non BR-oriented? This study is based on the information collected by using interviews with system analysts. Various articles and books on business rules are also used. To validate our empirical findings we have compared them with our theoretical baseline. As a result we have found that most of the system analysts work with both BR-oriented and non BR-oriented approaches but BR-oriented approach makes the information system successful as well as flexible.