Abstract

Use cases (UC) have traditionally been applied by software development teams as a technical and administrative tool. From each of these perspectives, it is necessary to have a set of attributes to manage, because the information taken for the development of a software product contains information from both the system and the organization. If all this information is intended to be captured through the uc, probably what results is a significant increase in the complexity of its specification, which creates some level of confusion when using them. In this paper we propose the separation of business and technical elements, when drafting uc, using the ATx. We are introducing the ATx in modeling with uc to reduce its complexity and mainly to increase their effectiveness and usefulness in what has to do with the human computer interaction.

Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call