CFP last date
20 May 2024
Reseach Article

Aspect-Oriented Software Development based Solution for Intervention Concerns Problems: Case Study

by Farhad Soleimanian Gharehchopogh, Esmail Amini, Behnam Zebardast
International Journal of Computer Applications
Foundation of Computer Science (FCS), NY, USA
Volume 63 - Number 4
Year of Publication: 2013
Authors: Farhad Soleimanian Gharehchopogh, Esmail Amini, Behnam Zebardast
10.5120/10453-5157

Farhad Soleimanian Gharehchopogh, Esmail Amini, Behnam Zebardast . Aspect-Oriented Software Development based Solution for Intervention Concerns Problems: Case Study. International Journal of Computer Applications. 63, 4 ( February 2013), 16-25. DOI=10.5120/10453-5157

@article{ 10.5120/10453-5157,
author = { Farhad Soleimanian Gharehchopogh, Esmail Amini, Behnam Zebardast },
title = { Aspect-Oriented Software Development based Solution for Intervention Concerns Problems: Case Study },
journal = { International Journal of Computer Applications },
issue_date = { February 2013 },
volume = { 63 },
number = { 4 },
month = { February },
year = { 2013 },
issn = { 0975-8887 },
pages = { 16-25 },
numpages = {9},
url = { https://ijcaonline.org/archives/volume63/number4/10453-5157/ },
doi = { 10.5120/10453-5157 },
publisher = {Foundation of Computer Science (FCS), NY, USA},
address = {New York, USA}
}
%0 Journal Article
%1 2024-02-06T21:13:16.404718+05:30
%A Farhad Soleimanian Gharehchopogh
%A Esmail Amini
%A Behnam Zebardast
%T Aspect-Oriented Software Development based Solution for Intervention Concerns Problems: Case Study
%J International Journal of Computer Applications
%@ 0975-8887
%V 63
%N 4
%P 16-25
%D 2013
%I Foundation of Computer Science (FCS), NY, USA
Abstract

All existing methods for Developing Software Systems, most insist on a separate system to keep the components together till they have been had the least overlapping. But these methods in the management system those have some parts and are using use case, and involved in the other parts of the systems, are inefficient. With arriving the Aspect-Oriented Programming, programmers were able to Implement the overcome some of these requirements and Implement them in a separate unit, but there are still some of the analysis requirements and design, because of the wrong analysis and design they cannot be implemented as a measure. In this article we want to prominent the phase of analysis and design of this work using the Aspect-Oriented Software, in order to implement them in the Implementation phase as a cup-on.

References
  1. IEEE 2000, "IEEE recommended practice for architectural description of software intensive systems". Available: http://www. win. tue. nl/~johanl/educ/2II45/Lit/software-architecture-std1471-2000. pdf. Last Availabel 02. 08. 2012.
  2. R. S. Pressman, Software Engineering: apractitioner's approach, Fifth edition, McGraw-Hill, page 541, 2001.
  3. S. Brinkkemper,"Method engineering: engineering of information systems development methods and tools", Inf. Software Technol. Vol. 38, N. 4, pp. 275-280, 1996.
  4. B. Morin, O. Barais, R. Ramos,"Towards a Generic Aspect-Oriented Modeling Framework", Author manuscript, published in "Models and Aspects workshop", at ECOOP 2007. Availabel: http://www. irisa. fr/triskell/publis/2007/morin07a. pdf , Last Availabel: 02. 08. 2012
  5. S. Apel, D. Batory,"An Analysis of Eleven AspectJ Programs", Technical Report, Number MIP-0801 Department of Informatics and Mathematics University of Passau, Germany, April 2008.
  6. B. , Nuseibeh, J. Kramer, and A. Finkelstein, "Expressing the relationships between multiple views in requirements specification", Proceedings of 15th International Conference on Software Engineering, Baltimore, USA, pp: 1-10, May 1993.
  7. G. Booch, I. Jacobson, and J. Rumbaugh, Object Oriented Analysis and Design with Applications, 3rd Edition, Addison. Wesley, 2007.
  8. D. L. Parnas, "On the Criteria To Be Used in Decomposing Systems into Modules", Communications of the ACM, Vol. 15, No. 12, pp. 1053-1058, 1972.
  9. K. Gregor, J. Lamping, A. Mendhekar, C. Maeda, C. Lopes, J. Loingtier, and J. Irwin "Aspect-Oriented Programming", Proceedings of the European Conference on Object-Oriented Programming, vol. 1241, pp. 220–242, 1997.
  10. R. E. Filman, D. P. Friedman, Aspect-oriented programming is quantification and Obliviousness, RIACE Technical Report 01. 12, pp. 1-9, May 2001.
  11. P. Jayaraman, J. Whittle, A. Elkhodary, and H. Gomaa. "Model Composition in Product Lines and Feature Interaction Detection Using Critical Pair Analysis", In MoDELS'07: Proceedings of the 10th International Conference on "Model Driven Engineering Languages and Systems", LNCS, pages 151–165, Nashville TN USA, Vanderbilt University,Springer-Verlag, Oct. 2007.
  12. B. Morin, O. Barais, J. M. J. Equel, " Weaving Aspect Configurations for Managing System Variability", Availabel: http://www. irisa. fr/triskell/publis/2008/Morin08a. pdf. Last Availabel: 02. 08. 2012.
  13. R. T. Alexander, J. M. Bieman, and A. A. Andrews,"Towards the Systematic Testing of Aspect- Oriented Programs", Technical Report CS-4-105, ColoradoState University,2004.
  14. A. Rashid, R. Chitchyan, "Aspect-Oriented Requirements Engineering: A Roadmap", Proceeding EA '08 Proceedings of the 13th international workshop on Early Aspects Pages 35-41 ACM New York, NY, USA ,2008.
  15. H. Hosny, A. A. Zakaia, Metrics for Aspect-Orinted Software Design, Technical report The American University in Cairo, 2004.
  16. O. Aldawud, T. Elrad, A. Bader, "Uml profile for aspect-oriented software development", Lucent Technologies Naperville, IL, Illinois Institute of Technology Chicago, IL, 2006.
  17. J. Araujo, A. Moreira, I. Brito, A. Rashid, "Aspect-Oriented Requirements with UML", Universidade Nova Lisboa, Instituto Politecnico de Beja, Lancaster University Lancaster, October 2002.
Index Terms

Computer Science
Information Sciences

Keywords

Intervention Concerns Software Development Aspect-Oriented Software Development Modularization Requirements