Use Case Driven Modularization as a Basis for Test Driven Modularization

Abstract

Abstract-While in waterfall-like processes changes are expected to happen mostly after the main development has finished, agile approaches have incorporated response to changes into the main development itself, which raises the importance of the ability to respond to changes effectively to a sine qua non. Changes are specified from the perspective of how users actually use systems, i.e., usage scenarios, which does not correspond to a common object-oriented code modularization. In their complete form, usage scenarios can be directly observed in user acceptance tests. Unit tests reveal parts of usage scenarios, too. Logically, tests follow the modularization of the code they are related to. Thus, in common object-oriented code, user acceptance tests, which play a very important role in any kind of software development process and which follow the procedural modularization, would be scattered and, consequently, hard to maintain. In this paper, we propose a new approach capable of achieving test driven modularization, i.e., organizing code according to tests. Besides pure test driven modularization, which can be based on user acceptance tests, unit tests, or both, the approach also enables combining use case and test driven modularization.

User acceptance test for software development in the agricultural domain using natural language processing

“…Moreover, Scenarios describing the behaviour of the application domain constitute an excellent approach since scenarios tell stories that are easily understandable. Other works deriving Uses Cases to Users Acceptance Tests (UAT) (Bystrický & Vranić, 2017;C. Y. Hsieh et al, 2013) or acceptance criteria described in the form of Given-When-Then (Pandit et al, 2016) are also frequently used.…”

AGUTER a platform for automated generation of user acceptance tests from requirements specifications

“…Moreover, scenarios describing the behavior of the domain are a good tool since scenarios tells stories and people are naturally trained in that activity. There are other works to derive UAT from use cases (Hsieh et al , 2013; Bystrický and Vranić, 2017) or acceptance criteria described in the form of Given-When-Then (Pandit et al , 2016). But all require an effort to build these models and agile methodologies which do not use these artifacts (Jeeva Padmini et al , 2016).…”