Towards an activity taxonomy (ATx) from separation of concerns in use case modeling
Article Sidebar
The total or partial reproduction of the contents of the journal for educational, research, or academic purposes is authorized as long as the source is cited. For reproduction for other purposes, express authorization from the Sello Editorial Universidad de Medellín is required.
Main Article Content
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.
Article Details
References
[2] Nunes, D. N. J., Object Modeling for User-Centered Development and User Interface Design: The Wisdom Approach. 2001, Universidade da Madeira: Funchal.
[3] Lozano, M.D., Entorno metodológico orientado a objetos para la especificación y desarrollo de interfaces de usuario. 2001, Universidad Politecnica de Valencia.
[4] Giraldo, W. J., Marco de desarrollo de sistemas software interactivos basado en la integración de procesos y notaciones, Escuela Superior de Informática de Ciudad Real. 2010, Universidad de Castilla-La Mancha: Ciudad Real. p. 370.
[5] Ng, P.-W., 'Effective Business Modeling with UML: Describing Business Use Case and Realizations'. The Rational Edge, 2002.
[6] Gottesdiener, E., 'Top Ten Ways Project Teams Misuse Use Cases -- and How to Correct Them', Rational Edge. 2002, Rational Software.
[7] Constantine, L. L. and L. A. D. Lockwood, 'Structure and style in use cases for user interface design', in Object modeling and user interface design: designing interactive systems. 2001, Addison-Wesley. pp 245-279.
[8] Cockburn, A., Writing Effective Use Cases. Addison-Wesley. 2000.
[9] Villegas, M. L., C. A. Collazos, W.J. Giraldo and J.M. González. 'Activity Theory as a Framework for Activity Taxonomy in HCI'. IEEE Latin America Transactions, Vol. 14, No. 2. 2016.
[10] Paternò, F. 'Towards a UML for Interactive Systems'. in 8th International Conference on Engineering for Human-Computer Interaction. 2001. Springer.
[11] Langlands, M. and C. Edwards, 'Business vs. System Use Cases'. Disponible en: http://www.agileea.com/Whitepapers/All3%20Business%20vs%20System%20Use%20Cases%20v1%209.pdf. 2009.
[12] Kramer, J. and O. Hazzan, 'The Role of Abstraction in Software Engineering', 28th International Conference on Software Engineering (ICSE) 2006, ACM: Shanghai, China.
[13] Zachman, J. A., 'The Zachman Framework for Enterprise Arquitecture - The Enterprise Ontology'. Disponible en: www.zachman.com. 2007-2011.
[14] Liskov, B. and S. Zilles, 'Specification techniques for data abstractions', Proceedings of the international conference on Reliable software. 1975, ACM.
[15] Giraldo, W. J., M. L. Villegas, and C.A. Collazos. Incorporación de HCI: Validación de la Usabilidad en Casos de Uso mediante la Taxonomía de la Actividad. in Computing Colombian Conference (10CCC), 2015 9th. 2015.
[16] Iqbal, R., A. James, and R. Gatward, 'Designing with ethnography: An integrative approach to CSCW design'. Advanced Engineering Informatics, 2005. 19(2): pp 81-92.
[17] Molina, A. I. 'CIAM: A methodology for the development of groupware user interfaces'. Journal of Universal Computer Science(JUCS), 2008. 14(9).
[18] Ambler, S.W. 'System Use Cases: An Agile Introduction'. Disponible en:http://agilemodeling.com/artifacts/systemUseCase.htm. 2013-2014.
[19] Paternò, F.: ‘ConcurTaskTrees: An Engineered Notation for Task Models’. Lawrence Erlbaum Associates, 2004. pp. 483-501.
[20] Constantine, L. L., 'Essential modeling: use cases for user interfaces'. Interactions ACM, 1995. 2(2): pp 34-46.