- 25 Downloads
Any software or product goes through a development life cycle. Once the product is launched it undergoes rigorous maintenance as long as it is alive and does not become obsolete. Developers are constrained to minimize the cost and risks associated with bugs (or errors) that may be detected during the development or maintenance lifecycles [1, 2]. These errors can range from simple logistics to complex non-compliance issues.
- 1.Yu E, Modelling strategic relationships for process reengineering. PhD thesis, University of Toronto, Toronto, CanadaGoogle Scholar
- 2.Hinge K, Ghose A, Koliadis G (2009) Process SEER: a tool for semantic effect annotation of business process models. In: Proceedings of the 13th IEEE international conference on Enterprise Distributed Object Computing (EDOC), pp 54–63. https://doi.org/10.1109/EDOC.2009.24
- 4.Horkoff J et al (2016) Goal-oriented requirements engineering: a systematic literature map. In: Proceedings of the IEEE 24th international requirements engineering conference (RE), Beijing, China, pp 106–115. https://doi.org/10.1109/RE.2016.41
- 5.Deb N, Chaki N (2014) Verification of i\(^*\) models for existential compliance rules in remote healthcare systems. Appl Innov Mob Comput 60–66. https://doi.org/10.1109/AIMOC.2014.6785520
- 7.Fuxman AD (2001) Formal analysis of early requirements specifications. MS thesis, Department of Computer Science, University of Toronto, CanadaGoogle Scholar