Using tagging to identify and organize concerns during pre-requirements analysis

  • Authors:

  • Harold Ossher;David Amid;Ateret Anaby-Tavor;Rachel Bellamy;Matt Callery;Michael Desmond;Jackie De Vries;Amit Fisher;Sophia Krasikov;Ian Simmonds;Cal Swart

  • Affiliations:

  • IBM T.J. Watson and Haifa Research Centers, USA;IBM T.J. Watson and Haifa Research Centers, USA;IBM T.J. Watson and Haifa Research Centers, USA;IBM T.J. Watson and Haifa Research Centers, USA;IBM T.J. Watson and Haifa Research Centers, USA;IBM T.J. Watson and Haifa Research Centers, USA;IBM T.J. Watson and Haifa Research Centers, USA;IBM T.J. Watson and Haifa Research Centers, USA;IBM T.J. Watson and Haifa Research Centers, USA;IBM T.J. Watson and Haifa Research Centers, USA;IBM T.J. Watson and Haifa Research Centers, USA

  • Venue:
  • EA '09 Proceedings of the 2009 ICSE Workshop on Aspect-Oriented Requirements Engineering and Architecture Design
  • Year:
  • 2009

Quantified Score

Hi-index 0.00

Visualization

Abstract

Before requirements analysis takes place in a business context, business analysis is usually performed. Important concerns emerge during this analysis that need to be captured and communicated to requirements engineers. In this paper, we take the position that tagging is a promising approach for identifying and organizing these concerns. The fact that tags can be attached freely to entities, often with multiple tags attached to the same entity and the same tag attached to multiple entities, leads to multi-dimensional structures that are suitable for representing crosscutting concerns and exploring their relationships. The resulting tag structures can be hardened into classifications that capture and communicate important concerns.