Abstract

Over the last few years, several research efforts have been devoted for handling crosscutting concerns at the early phases of software development especially at requirements level. These efforts are meaningless unless all the crosscutting concerns are properly identified. Many approaches only consider non-functional concerns as crosscutting concerns. However, crosscutting concerns may also be functional. In this paper, we are proposing an integrated approach that supports complete separation of concerns i. e. handles both functional and non-functional concerns as crosscutting. Our work will surely contribute some positive in this direction

References

• Dijkstra, E. W. , 1976, A Discipline of Programming, Prentice Hall, Englewood Cliffs, New Jersey, USA.
• S. M. Sutton Jr and I. Rouvellou. , 2002, Modeling of Software Concerns in Cosmos. In Proceedings of the 1st International Conference on Aspect-Oriented Software Development, ACM, pages 127–133.
• Finkelstein, A. , Sommerville, I. 1996, The Viewpoints FAQ, Software Engineering Journal: Special Issue on Viewpoints for Software Engineering, IEE/BCS. 11(1): 2-4.
• Jacobson, I et al. , 1992, Object-Oriented Software Engineering - a Use Case Driven Approach, 978-0201544350, Addison-Wesley.
• Chung, L. et al. , 2000, Non-Functional Requirements in Software Engineering, 0-7923-8666-3, Kluwer Academic Publishers.
• Mark. E. et al. , 2008, Do Crosscutting Concerns Cause Defects?", IEEE Transactions On Software Engineering, Vol. 34, No. 4, July/August.
• I. Brito, A. Moreira, 2003, "Advanced Separation of Concerns for Requirements Engineering", VIII Jornadas de Ingenieria del Software y Bases de Datos (JISBD'03), pp. 47-56, Alicante, Spain. November 12-14.
• G. Kiczales et al. , 1997, Aspect-oriented programming, in: Proceedings of the 11th European Conferenceon Object-Oriented Programming (ECOOP'97), Springer, pp. 220–242.
• Laddad Ramnivas, 2002, I want my AOP! Part 1: Separate software concerns with aspect-oriented programming. Java World Fueling Innovations. URL: http://www. javaworld. com/javaworld/jw-01-2002/jw-0118-aspect. html.
• Rashid, A. , Moreira, A. , Araújo, J. , 2003, Modularization and Composition of Aspectual Requirements, In 2nd Aspect-Oriented Software Development Conference (AOSD'03), Boston, USA, ACM Press. 11-20.
• Baniassad et al. , 2006, Discovering Early Aspects, IEEE Software Special Issue on Aspect-Oriented Programming. 23(1): pp. 61-70.
• AspectJ Project (2007). http://www. eclipse. org/aspectj/.
• AspectC Project (2007). http://www. cs. ubc. ca/labs/spl/projects/aspectc. html.
• Spinczyk, O. , Lohmann, D. , Urban, M. (2005). "AspectC++: an AOP Extension for C++. " Software Developer's Journal 1: 68-76.
• JBoss Project (2007). http://labs. jboss. com/jbossaop/.
• JAsCo Project (2007). http://ssel. vub. ac. be/jasco/.
• HyperJ (2007). http://www. alphaworks. ibm. com/tech/hyperj.
• Clarke S. and Walker R. J. , 2001, Composition Patterns: An Approach to Designing Reusable Aspects, ICSE.
• Suzuki J. and Yamamoto Y. , 1999, Extending UML with Aspects: Aspect Support in the Design Phase, ECOOP Workshop on AOP.
• Y. Yu et al. 2004, From Goals to Aspects: Discovering Aspects from Requirements Goal Models, Proc. RE 2004, IEEE CS, pp. 38-47.
• E. Baniassad, S. Clarke, 2004, Theme: An Approach for Aspect-Oriented Analysis and Design, ICSE 2004, IEEE CS, pp. 158-167.
• A. Moreira et al. , 2005, Multi-Dimensional Separation of Concerns in Requirements Engineering" RE 2005, pp. 285-296.
• Moreira, A. , Araújo, J. , Brito, I, 2002, Crosscutting Quality Attributes for Requirements Engineering. In 14th Software Engineering and Knowledge Engineering Conference (SEKE'02), Ischia, Italy, ACM Press. 167 - 174.
• Rashid, A. , Moreira A. , 2006, Domain Models are NOT Aspect Free. In 9th Model Driven Engineering Languages and Systems Conference (MoDELS/UML'06). Genova, Italy, Lecture Notes in Computer Science 4199. Springer. 155-169.
• J. Grundy, 1999, Aspect-Oriented Requirements Engineering for Component-based Software Systems, IEEE International Symposium on Requirements Engineering, IEEE CS, pp. 84-91.
• Rashid, A. et al. , 2002, Early Aspects: a Model for Aspect-Oriented Requirements Engineering, Proc. of Int. Conference on Requirements Engineering (RE'02).
• E. Baniassad, S. Clarke, 2004, Theme: An Approach for Aspect-Oriented Analysis and Design, In Proceedings of the 26th Int. Conf. on Software Engineering (ICSE04).
• Jacobson, I. , 2004, Aspect-Oriented Software Development with Use Cases, 978-0-321-26888-4, Addison-Wesley.
• Zhang Jingjun et al. , 2007, Aspect-Oriented Requirements Modeling, Proceeding of the 31st IEEE Software Engineering Workshop SEW-31 (SEW'07), Baltimore, MD, USA.
• S. Hamza and D. Darwish, 2009, On the Discovery of Candidate Aspects in Software Requirements, Proc. Of Sixth International Conference on Information Technology: New Generations.
• Xiaojuan et al. , 2010, Use case And Non-functional Scenario Template-Based Approach to Identify Aspects, Second International Conference on Computer Engineering and Applications.
• I. Brito, 2004, Aspect-Oriented Requirements Engineering, UML'04 DocSym, Doctoral Symposium 7th International Conference on the Unified Modeling Language, Lisbon, Portugal.
• A. Amirat et al. , 2006, An Aspect-Oriented Approach in Early Requirements Engineering, IEEE, pp. 1055-1058.
• Bernd Bruegge et al. , 1994, Design Considerations for an Accident Management System, In Proceedings of the Second International Conference on Cooperative Information Systems, Toronto Press, May 1994.
• M. Bookser and B. Bruegge. 1993, Information, Technology and Police Management: The FRIEND system," Proceedings of the 1993 Society of Police Futurists International Symposium, Baltimore, Maryland, May 1993.
• B. Bruegge and A. Dutoit, 2007, Object-Oriented Software Engineering Using UML, Patterns, and JavaTM, 2nd Edition, Pearson Education.