Antonio Oliveira Filho
ABSTRACT
Impact analysis is the identification of the potential consequences of a change, or estimating what needs to be modified to accomplish a change, including related costs and schedule estimates. In this work, we distinguish between two kinds of concerns related to impact analysis: (1) business-specific concerns, those related to stakeholders interested in checking if other business rules are impacted by the change and also need to be modified; and (2) software-specific concerns, those related to stakeholders interested in the impacted software artifacts that need to be modified. Several traceability techniques have been studied and none of them supported impact analysis that dealt with business-specific concerns with reasonable values of precision and recall for the discovered impacts. Our research work aims to support business-specific concerns during impact analysis, by proposing and evaluating a traceability technique that resorts on a new traceability model defined over business rules, with expected precision and recall values of 100%.
- G. Antoniol et al. Recovering traceability links between code and documentation. IEEE Trans. Softw. Eng., 28(10):970--983, 2002. Google Scholar
Digital Library
- R. S. Arnold. Software Change Impact Analysis. IEEE Computer Society Press, 1996. Google ScholarDigital Library
- J. Cleland-Huang. Just enough requirements traceability. In COMPSAC'06: Proc. 30th Annual Intl Computer Software and Applications Conf., pages 41--42, Washington, DC, USA, 2006. IEEE Comp. Society. Google ScholarDigital Library
- A. Filho Oliveira et al. Em busca de agilidade na analise de impacto: O artefato fir. Latin America Transactions, IEEE, 6(3):275--281, July 2008.Google ScholarCross Ref
- B. R. Group. Business rules group (BRG) - http://www.businessrulesgroup.org.Google Scholar
- B. V. Halle. Business Rules Applied: Building Better Systems Using the Business Rules Approach. John Wiley & Sons, Inc., New York, NY, USA, 2001. Google ScholarDigital Library
- M. Heindl et al. A case study on value-based requirements tracing. In ESEC/FSE-13: Proc. 10th ESEC13th ACM SIGSOFT Intl Symp. on Found. of Software Engineering, pages 60--69, New York, NY, USA, 2005. ACM. Google ScholarDigital Library
- T. Kasse. Practical Insight Into CMMI. Artech House, Boston, USA, 2004. Google ScholarDigital Library
- M. M. Lehman. Laws of software evolution revisited. In EWSPT '96: Proceedings of the 5th European Workshop on Software Process Technology, pages 108--124, London, UK, 1996. Springer-Verlag. Google ScholarDigital Library
- J. Leite and M. C. Leonardi. Business rules as organizational policies. In IWSSD'98: Proc. 9th Intl Workshop on Software Specification and Design, page 68, Washington, DC, USA, 1998. IEEE Computer Society. Google ScholarDigital Library
- U. A. Raja and K. Kamran. Framework for requirements traceability - tlfrt supporting pre-rs & post-rs traceability. Master's thesis, Blekinge Institute of Technology, School of Engineering, 2008.Google Scholar
- S. Rochimah et al. An evaluation of traceability approaches to support software evolution. In ICSEA'07: Proc. Intl Conf. on Software Engineering Advances, page 19, Washington, DC, USA, 2007. IEEE Computer Society. Google ScholarDigital Library
- G. Zemont. Towards Value-Based Requirements Traceability. PhD thesis, Dept. of Computer Science, De Paul University, 2005.Google Scholar
Index Terms
- Change impact analysis from business rules
Recommendations
Discovering business rules from business process models
CompSysTech '11: Proceedings of the 12th International Conference on Computer Systems and TechnologiesDiscovering business rules from business process models are of advantage to ensure the compliance of business processes with business rules. Furthermore it provides the agility of business processes in case of business rules evolution. Current ...
Modeling Business Rules in E-commerce Systems Using Stateful Aspects
ICEE '12: Proceedings of the 2012 3rd International Conference on E-Business and E-Government - Volume 05Business rules are typical crosscutting concerns in ecommerce systems. Many approaches adopt aspect-oriented paradigms to separate business rules from the core functionality. However, many business rules are history-sensitive. Traditional aspects can ...
Linking business rules to object-oriented software using JAsCo
Selected papers from the International Conference on Computer Science,Software Engineering, Information Technology, e-Business, and Applications, 2003Object-oriented software applications that support a particular business or domain consist of substantial core application functionality and business rules. Since business rules tend to evolve frequently, it is important to separate them from the core ...
Comments