Abstract
Aspect-oriented requirements analysis involves the identification of concerns that behaviorally influence other concerns. Such concerns are described in requirements called emphaspectual requirements: requirements that detail the influence of one concern over another. The current state of the art for aspect-oriented requirements analysis is Theme/Doc, which allows lexical analysis of requirements based on a set of developer-chosen keywords. It provides a graphical depiction of how concerns relate to requirements, and affords identification of potential aspectual requirements. In addition, clusters of requirements and concerns are identified to arrive at a more useful set of concerns than those initially identified.Because of the lexical nature of the Theme/Doc approach, aspectual requirements are missed, or wrongly identified. Additionally, requirements may be wrongly clustered if they contain ambiguous terms.In this work we explored whether the use of a statistical approach for textual analysis, Latent Semantic Analysis (LSA), would improve upon the lexical approach used by Theme/Doc. We found that LSA helps identify useful concern clusters, and helps reduce the number of falsely identified aspectual requirements.
- E. Baniassad and S. Clarke. Theme: An approach for aspect-oriented analysis and design. In ICSE '04: Proceedings of the 26th International Conference on Software Engineering, pages 158--167, Washington, DC, USA, 2004. IEEE Computer Society. Google Scholar
Digital Library
- E. Baniassad, P. Clements, J. Araujo, A. Moreira, A. Rashid, and B. Tekinerdogan. Discovering early aspects. IEEE Software, Jan/Feb 2006. Google Scholar
Digital Library
- M. Berry, X. Drmac, and E. Jessup. Matrices, vector spaces, and information retrieval. SIAM Review, 41(2):335--362. Google Scholar
Digital Library
- M. Berry, S. Dumais, and G. O'Brien. Using linear algebra for intelligent information retrieval. SIAM review, 37(4):573--595, 1995. Google Scholar
Digital Library
- S. Clarke and E. Baniassad. Aspect-Oriented Analysis and Design: The Theme Approach. Addison Wesley, 2005. Google Scholar
Digital Library
- S. C. Deerwester, S. T. Dumais, T. K. Landauer, G. W. Furnas, and R. A. Harshman. Indexing by latent semantic analysis. Journal of the American Society of Information Science, 41(6):391--407, 1990.Google Scholar
Cross Ref
- G. H. Golub and C. F. V. Loan. Matrix Computations. John Hopkins University Press, third edition, 1996.Google Scholar
- J. Grundy. Aspect-oriented requirements engineering for component based software systems. In 4th IEEE International Symposium on Requirements Engineering, pages 84--91. Google Scholar
Digital Library
- T. K. Landauer, P. W. Foltz, and D. Laham. Introduction to latent semantic analysis. Discourse Processes, 25:259--284, 1998.Google Scholar
Cross Ref
- J. Maletic and A. Marcus. Supporting program comprehension using semantic and structural information. In ICSE '01: Proceedings of the 23rd International Conference on Software Engineering, pages 103--112, Washington, DC, USA, 2001. IEEE Computer Society. Google Scholar
Digital Library
- J. Maletic and A. Marcus. Recovering documentation-to-sourcecode traceability links using latent semantic indexing. In ICSE '03: Proceedings of the 25rd International Conference on Software Engineering, 2003. Google Scholar
Digital Library
- A. Rashid, A. Moreira, and J. Araujo. pages 11--20, 2003.Google Scholar
- A. Sampaio, N. Loughran, A. Rashid, and P. Rayson. Mining aspects in requiements. In AOSD'2005 Aspect-Oriented Requirements Engineering and Architecture Design Workshop, Chicago, Illinois, USA, 2005.Google Scholar
- A. Stone and P. Sawyer. Finding tacit knowledge by solving the pre-requirements tracing problem. In Workshop on Requirements Engineering: Foundation for Software Quality, 2005.Google Scholar
- R. Suen and E. Baniassad. Isolating concerns in requirements using latent semantic analysis. In OOPSLA'2005 Workshop on Early Aspects, San Diego, California, USA, October 2005.Google Scholar
Index Terms
Isolating and relating concerns in requirements using latent semantic analysis
Recommendations
Isolating and relating concerns in requirements using latent semantic analysis
OOPSLA '06: Proceedings of the 21st annual ACM SIGPLAN conference on Object-oriented programming systems, languages, and applicationsAspect-oriented requirements analysis involves the identification of concerns that behaviorally influence other concerns. Such concerns are described in requirements called emphaspectual requirements: requirements that detail the influence of one ...
Revealing Crosscutting Concerns in Textual Requirements Documents: An Exploratory Study with Industry Systems
SBES '12: Proceedings of the 2012 26th Brazilian Symposium on Software EngineeringIt is well-known that effective requirements analysis plays a crucial role in the quality of software systems. However, the scattered and tangled nature of certain system's concerns can hinder the proper understanding and treatment of import ...
A Comprehensive Aspect-Oriented Use Case Method for Modeling Complex Business Requirements
ER '08: Proceedings of the ER 2008 Workshops (CMLSA, ECDM, FP-UML, M2AS, RIGiM, SeCoGIS, WISM) on Advances in Conceptual Modeling: Challenges and OpportunitiesThe aspect-oriented approach separates cross-cutting concerns and models them as aspects. In this paper, we present a comprehensive aspect-oriented use case approach for modeling complex business requirements. We identify four categories of aspects: ...







Comments