CFP last date
20 January 2025
Reseach Article

Aspects Oriented Approach towards the Goal Driven Software Lifecycle

by G. SuryaTeja
International Journal of Computer Applications
Foundation of Computer Science (FCS), NY, USA
Volume 124 - Number 17
Year of Publication: 2015
Authors: G. SuryaTeja
10.5120/ijca2015905581

G. SuryaTeja . Aspects Oriented Approach towards the Goal Driven Software Lifecycle. International Journal of Computer Applications. 124, 17 ( August 2015), 55-57. DOI=10.5120/ijca2015905581

@article{ 10.5120/ijca2015905581,
author = { G. SuryaTeja },
title = { Aspects Oriented Approach towards the Goal Driven Software Lifecycle },
journal = { International Journal of Computer Applications },
issue_date = { August 2015 },
volume = { 124 },
number = { 17 },
month = { August },
year = { 2015 },
issn = { 0975-8887 },
pages = { 55-57 },
numpages = {9},
url = { https://ijcaonline.org/archives/volume124/number17/22201-2015905581/ },
doi = { 10.5120/ijca2015905581 },
publisher = {Foundation of Computer Science (FCS), NY, USA},
address = {New York, USA}
}
%0 Journal Article
%1 2024-02-06T23:14:43.811222+05:30
%A G. SuryaTeja
%T Aspects Oriented Approach towards the Goal Driven Software Lifecycle
%J International Journal of Computer Applications
%@ 0975-8887
%V 124
%N 17
%P 55-57
%D 2015
%I Foundation of Computer Science (FCS), NY, USA
Abstract

Technology and its development need to be improved ion the aspect of the Information Technology which follows some methodology or process. In the current context we usually talking about the XP, Agile and test driven Approach needs to also change in its aspect oriented. Development of the software needs to be smart unique and proportionally domination if we want to explore in the Digitalized information World. If we see the data analysis of the requirement which having many draw flaws leads us to the next level of the journey of life cycle of SDLC. Aspect Oriented requirement needs to be early discussed and should follow a rapid model of changing with each and every version to base cycle which we represented in this paper making to inspiration next level of the classical technology may not be adoptable . IT industry moves on two major task one is deliverable in time which is based on the requirements is the base Pillar.

References
  1. E. Baniassad, P. C. Clements, J. Ara_ujo, A. Moreira, A. Rashid, and B. Tekinerdo_gan, “Discovering early aspects,” IEEE Softw., vol. 23, no. 1, pp. 61–70, Jan.-Feb. 2006.
  2. A. Rashid, A. Moreira, and J. Ara_ujo, “Modularisation and composition of aspectual requirements,” in Proc. 2nd Aspect-Oriented Softw. Develop. Conf., 2003, pp. 11–21.
  3. M. Mortensen, S. Ghosh, and J. M. Bieman, “Aspect-oriented refactoring of legacy applications: An evaluation,” IEEE Trans. Softw. Eng., vol. 38, no. 1, pp. 118–140, Jan./Feb. 2012.
  4. S. Miller, “Aspect-oriented programming takes aim at software complexity,” Comput., vol. 34, no. 4, pp. 18–21, Apr. 2001.
  5. N. Noda and T. Kishi, “On aspect-oriented design-an approach to designing quality attributes,” in Proc. 6th Asia Pac. Softw. Eng. Conf., 1999, pp. 230–237.
  6. M. Shomrat and A. Yehudai, “Obvious or not? regulating architectural decisions using aspect-oriented programming,” in Proc. 1st Int. Conf. Aspect-Oriented Softw. Develop., Apr. 2002, pp. 3–9.
  7. J. Viega and J. Voas, “Can aspect-oriented programming lead to more reliable software?” IEEE Softw., vol. 17, no. 6, pp. 19–21, Nov./Dec. 2000.
  8. A. Rashid, A. Moreira, and B. Tekinerdogan, “Early aspects— Aspect-oriented requirements engineering and architecture design,” IEEE Proc. Softw., vol. 151, no. 4, pp. 153–155, Aug. 2004.
  9. S. M. Sutton Jr. and I. Rouvellou, “Modeling of software concerns in cosmos,” in Proc. 1st Int. Conf. Aspect-Oriented Softw. Develop., 2002, pp. 127–133.
  10. A. Dardenne, A. van Lamsweerde, and S. Fickas, “Goal-directed requirements acquisition,” Sci. Comput. Programm., vol. 20, no. 1–2, pp. 3–50, 1993.
  11. J. Mylopoulos, L. Chung, and B. Nixon, “Representing and using nonfunctional requirements: A process-oriented approach,” IEEE Trans. Softw. Eng., vol. 18, no. 6, pp. 483–497, Jun. 1992.
  12. A. van Lamsweerde, R. Darimont, and E. Leitier, “Managing conflicts in goal-driven requirements engineering,” IEEE Trans. Softw. Eng., vol. 24, no. 11, pp. 908–926, Nov. 1998.
  13. J. Lee and Y. Fanjiang, “Modeling imprecise requirements with xml,” Inform. Softw. Technol., vol. 45, no. 7, pp. 445–460, May 2003. W. Lee, W. Deng, J. Lee, and S. Lee, “Change impact analysis with a goal-driven traceability-based approach,” Int. J. Intell. Syst., vol. 25, pp. 878–908, Aug. 2010.
  14. F. Steimann, “Domain models are aspect free,” in Model Driven Engineering Languages and Systems, New York, NY, USA: Springer-Verlag, 2005, pp. 171–185.
  15. A. Moreira, A. Rashid, and J. Ara_ujo, “Multi-dimensional separation of concerns in requirements engineering,” in Proc. 13th IEEE Int. Conf. Requirements Eng., 2005, pp. 285–296.
  16. Rashid and A. Moreira, “Domain models are not aspect free,” in Proc. 9th Int. Conf. Model Driven Eng. Lang. Syst., Springer, 2006, pp. 155–169.
  17. L. Constantine and L. Lockwood, Software for Use. Reading, MA, USA: Addison-Wesley, 1999.
Index Terms

Computer Science
Information Sciences

Keywords

Early aspects goals goals interaction fuzzy logic use cases goal cluster.