This paper presents a tool to provide an enaction\ud capability for use case descriptions. Use cases have\ud wide industry acceptance and are well suited for\ud constructing initial approximations of the intended\ud behaviour. However, use case descriptions are still\ud relatively immature with respect to precise syntax\ud and semantics. Hence, despite promising work on\ud providing writing guidelines, rigorous validation of\ud use case descriptions requires further support.\ud One approach to supporting validation is to use\ud enaction. Indeed, enactable models have been used\ud extensively within process modelling to clarify\ud understanding of descriptions.\ud Given the importance of requirements validation,\ud such automated support promises significant benefits.\ud However, the need to produce formal descriptions, to\ud drive enaction, is often seen as a barrier to the takeup\ud of such technologies. That is, developers have\ud traditionally been reluctant to increase the\ud proportion of effort devoted to requirements\ud activities. Our approach involves the development of\ud a lightweight state-machine, which obviates any need\ud to create intermediate formal descriptions, thereby\ud maintaining the simple nature of the use case\ud description.\ud Hence, this 'lightweight' approach, which provides\ud an enaction capability ‘for minimal effort’, increases\ud the likelihood of industrial take-up
To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.