CFP last date
22 April 2024
Call for Paper
May Edition
IJCA solicits high quality original research papers for the upcoming May edition of the journal. The last date of research paper submission is 22 April 2024

Submit your paper
Know more
The week's pick
Responsive image
Enhancing Privacy Preservation: Multi-Attribute Protection with P-Sensitive K-Anonymity

Twinkle Patel Kiran Amin
Random Articles
Reseach Article

Towards an Integrated AORE Process Model for Handling Crosscutting Concerns

by Narender Singh, Nasib Singh Gill
journal cover thumbnail

International Journal of Computer Applications
Foundation of Computer Science (FCS), NY, USA
Volume 37 - Number 3
Year of Publication: 2012
Authors: Narender Singh, Nasib Singh Gill
10.5120/4587-6525

Narender Singh, Nasib Singh Gill . Towards an Integrated AORE Process Model for Handling Crosscutting Concerns. International Journal of Computer Applications. 37, 3 ( January 2012), 18-24. DOI=10.5120/4587-6525

@article{ 10.5120/4587-6525,
author = { Narender Singh, Nasib Singh Gill },
title = { Towards an Integrated AORE Process Model for Handling Crosscutting Concerns },
journal = { International Journal of Computer Applications },
issue_date = { January 2012 },
volume = { 37 },
number = { 3 },
month = { January },
year = { 2012 },
issn = { 0975-8887 },
pages = { 18-24 },
numpages = {9},
url = { https://ijcaonline.org/archives/volume37/number3/4587-6525/ },
doi = { 10.5120/4587-6525 },
publisher = {Foundation of Computer Science (FCS), NY, USA},
address = {New York, USA}
}
%0 Journal Article
%1 2024-02-06T20:23:20.418511+05:30
%A Narender Singh
%A Nasib Singh Gill
%T Towards an Integrated AORE Process Model for Handling Crosscutting Concerns
%J International Journal of Computer Applications
%@ 0975-8887
%V 37
%N 3
%P 18-24
%D 2012
%I Foundation of Computer Science (FCS), NY, USA
Abstract

The two fundamental principles in software engineering to deal software complexity are separation of concerns and modularity. A lot of techniques exist in literature adopting these fundamental principles and some success in this direction has been achieved. Despite this improvement, still complete separation of concerns is not achieved and is far from adequate. Aspect-Oriented Software Development is another step towards achieving improved modularity and aims to advanced separation of concerns. It handles crosscutting concerns in an efficient manner by encapsulation them in separate modules called aspects and further uses composition mechanism to integrate them with core concerns. Handling crosscutting concerns in the early stages of software development is beneficial rather than handling them in later stages of software development because it not only makes the design simpler, but also helps to reduce the cost and defects that occur in the later stages of development. Aspect-Oriented Requirements Engineering (AORE) focuses on identifying, analyzing, specifying, verifying, and managing the crosscutting concerns at the early stages of software development. In last few years, many researchers contributed their significant efforts in this area but, still it is not sufficient. In this paper, we have proposed such an approach that incorporates aspect-oriented concepts and which includes concern management as a key separate activity that is not clearly mentioned earlier in literature. Also, traceability is an essential activity to accommodate changes in requirements but it is very difficult to implement. Organizing large numbers of requirements into meaningful and more manageable groups and negotiating specification with clients can make traceability easier to implement and maintain. The proposed approach supports identification, management, specification, and composition of all concerns.

References
  1. Pressman, R. Software Engineering: A Practitioner ’.s Approach, 3‘d edition, McGraw Hill, 1992.
  2. P. Naur and B. Randell, “Software Engineering: Report of the Working Conference on Software Engineering”, Garmisch, Germany, October 1968. NATO Science Committee, 1969.
  3. Parnas, D.L. “On the criteria to be used in decomposing systems into modules”, Communications of the ACM, 15(12):1053–1058
  4. .
  5. Dijkstra, E.W. “A Discipline of Programming”, Prentice Hall PTR, Upper Saddle River, NJ, USA
  6. .
  7. Baldwin, C.Y. and Clark, K.B. “Design Rules: The Power of Modularity Volume 1”, MIT Press, Cambridge, MA, USA
  8. .
  9. S. M. Sutton Jr and I. Rouvellou, “Modeling of Software Concerns in Cosmos”, In Proceeding of the Ist International Conference on Aspect-Oriented Software Development, pg. 127-133, ACM Press, 2002.
  10. D. L. Parnas, “A Technique for Software Module Specification with Examples”, Communications of the ACM (CACM), 15(5):330–336, 1972.
  11. Elrad T., Filman R., and Bader A. (eds.), "Theme Section on Aspect-Oriented Programming", CACM, 44(10), 2001.
  12. Rashid, A., Moreira, A., Araújo, J., “Modularization and Composition of Aspectual Requirements”, In 2nd Aspect-Oriented Software Development Conference (AOSD'03), Boston, USA, ACM Press. 11-20, 2003.
  13. Baniassad, E., Clements, P., Araújo, J., Moreira, A., Rashid, A., Tekinerdogan, B., "Discovering Early Aspects", IEEE Software Special Issue on Aspect-Oriented Programming. 23(1): 61-70, 2006.
  14. Clarke S. and Walker R. J., "Composition Patterns: An Approach to Designing Reusable Aspects", ICSE, 2001.
  15. Suzuki J. and Yamamoto Y., "Extending UML with Aspects: Aspect Support in the Design Phase", ECOOP Workshop on AOP, 1999.
  16. J. Grundy, "Aspect-Oriented Requirements Engineering for Component-based Software Systems", IEEE International Symposium on Requirements Engineering, IEEE CS, pp. 84-91, 1999.
  17. Rashid, A., Sawyer, P., Moreira, A., and Araújo, J. "Early Aspects: a Model for Aspect-Oriented Requirements Engineering", Proc. of Int. Conference on Requirements Engineering (RE'02), 2002.
  18. E. Baniassad, S. Clarke, "Theme: An Approach for Aspect-Oriented Analysis and Design", In Proceedings of the 26th Int. Conf. on Software Engineering (ICSE04), 2004.
  19. Araújo, J. Whittle, and D-K. Kim, “Modeling And Composing Scenario-Based Requirements With Aspects” In Proc. of the 12th IEEE International Requirements Engineering Conference (RE 04), 2004.
  20. Jacobson, I.,” Aspect-Oriented Software Development with Use Cases”, 978-0-321-26888-4, Addison-Wesley, 2004.
  21. A. Moreira, J. Araújo, A. Rashid, “A Concern-Oriented Requirements Engineering Model”, Proc. Conference on Advanced Information Systems Engineering, Portugal, LNCS 3520, pp. 293 – 308, Springer-Verlag Berlin Heidelberg 2005.
  22. Isabel Sofia Brito and Ana Moreira, “Towards an Integrated Approach for Aspectual Requirements”, 14th IEEE International Requirements Engineering Conference (RE'06), IEEE 2006.
  23. Zhang Jingjun, Li Furong, and Zhang Yang, “Aspect-Oriented Requirements Modeling”, Proceeding of the 31st IEEE Software Engineering Workshop SEW-31 (SEW’07), Baltimore, MD, USA, 2007.
  24. Moreira, A., Araújo, J., Brito, I., “Crosscutting Quality Attributes for Requirements Engineering”, In 14th Software Engineering and Knowledge Engineering Conference (SEKE'02), Ischia, Italy, ACM Press. 167 – 174, 2002.
  25. Jing Zhang, Yan Liu, Michael Jiang, and John Strassner, “An Aspect-Oriented Approach to Handling Crosscutting Concerns in Activity Modeling”, Proceedings of the International MultiConference of Engineers and Computer Scientists 2008 Vol I, IMECS 2008, Hong Kong, 19-21 March, 2008.
  26. Busyairah Syd Ali and Zarinah Mohd. Kasirun,”Developing Tool for Crosscutting Concern Identification using NLP”, IEEE 2008.
  27. G. Mussbacher, “Aspect-Oriented User Requirements Notation: Aspects in Goal and Scenario Models”, MoDELS 2007 Workshops, LNCS 5002, pp. 305–316, 2008, Springer-Verlag Berlin Heidelberg 2008.
  28. S. Iqbal, and G. Allen, “Representing Aspects in Design", presented at 2009 Third IEEE International Symposium on Theoretical Aspects of Software Engineering, Tianjin, China , 2009.
  29. S. Hamza and D. Darwish, “On the Discovery of Crosscutting concerns in Software Requirements”, Proc. Of Sixth International Conference on Information Technology: New Generations, 2009.
  30. Xiaojuan Zheng, Xiaomei Liu, and shulin Liu, “Use case And Non-functional Scenario Template-Based Approach to Identify Aspects”, Second International Conference on Computer Engineering and Applications, 2010.
  31. I. Jacobson, Object-Oriented Software Engineering - a Use Case Driven Approach: Addison-Wesley, 1992.
  32. A. Lamsweerde, "Goal-Oriented Requirements Engineering: A Guided Tour", 5th Int'l Symp. on RE, 2001, IEEE CS Press, pp. 249-261.
  33. A. Finkelstein and I. Sommerville, "The Viewpoints FAQ", BCS/IEE Software Engineering Journal, 11(1), 1996.
  34. The Standish Group. Chaos Report. Technical report, Standish Group International, 1995, http://www.it-cortex.com/Stat_Failure_Rate.htm#The%20Chaos%20Report%20(1995).
  35. The Standish Group, “CHAOS Summary 2009”, Technical report, Standish Group International, Boston, Massachusetts, April 23, 2009, http://www1.standishgroup.com/newsroom/chaos_2009.php
  36. L. Rosenhainer, “The DISCERN Method: Dealing Separately With Crosscutting Concerns”, In Early Aspects, OOPSLA 2005, 2005.
Index Terms

Computer Science
Information Sciences

Keywords

Separation of concerns crosscutting concerns aspect-oriented software development aspect-oriented requirements engineering

Powered by PhDFocusTM