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

Change Requests Artifacts to Assess Impact on Structural Design of SDLC Phases

by Rudra Kumar Madapudi, A. Ananda Rao, Gopichand Merugu
journal cover thumbnail

International Journal of Computer Applications
Foundation of Computer Science (FCS), NY, USA
Volume 54 - Number 18
Year of Publication: 2012
Authors: Rudra Kumar Madapudi, A. Ananda Rao, Gopichand Merugu
10.5120/8682-2508

Rudra Kumar Madapudi, A. Ananda Rao, Gopichand Merugu . Change Requests Artifacts to Assess Impact on Structural Design of SDLC Phases. International Journal of Computer Applications. 54, 18 ( September 2012), 21-26. DOI=10.5120/8682-2508

@article{ 10.5120/8682-2508,
author = { Rudra Kumar Madapudi, A. Ananda Rao, Gopichand Merugu },
title = { Change Requests Artifacts to Assess Impact on Structural Design of SDLC Phases },
journal = { International Journal of Computer Applications },
issue_date = { September 2012 },
volume = { 54 },
number = { 18 },
month = { September },
year = { 2012 },
issn = { 0975-8887 },
pages = { 21-26 },
numpages = {9},
url = { https://ijcaonline.org/archives/volume54/number18/8682-2508/ },
doi = { 10.5120/8682-2508 },
publisher = {Foundation of Computer Science (FCS), NY, USA},
address = {New York, USA}
}
%0 Journal Article
%1 2024-02-06T20:56:02.337315+05:30
%A Rudra Kumar Madapudi
%A A. Ananda Rao
%A Gopichand Merugu
%T Change Requests Artifacts to Assess Impact on Structural Design of SDLC Phases
%J International Journal of Computer Applications
%@ 0975-8887
%V 54
%N 18
%P 21-26
%D 2012
%I Foundation of Computer Science (FCS), NY, USA
Abstract

Current escalating demands on software, software developers to be obliged to generate software that can be altered, which escape from the risk of mortifying the software structural-design of the "SDLC phases". Degraded software structural-design is problematic because it makes the system more prone to defects and change requests turn to be costlier. The impacts of change requests to software can be hard to determine. One way to determine these consequences is to artifact the causes and effects caused by change request. A software change artifact allows to assess the effects of a change using different criteria such as causes to apply the change to be requested, change request type and the software module influenced by that changes. Once these artifacts identified then these artifacts can be used to scale the potential impact of the change. Another benefit of defining artifacts of the change-requests are that it allows engineers to develop a common approach to deal with changes that have similar in defined artifacts, rather than addressing each change individually. This paper introduces a mechanism that defines artifacts of the change-request to assist developers in measuring the impact of a software change on the structural-design of the SDLC-phases.

References
  1. M. M. Lehman and L. Belady, Software Evolution - Processes of Software Change, Academic Press, London, 1985
  2. L. Arthur, Software Evolution: The Software Maintenance Challenge, John Wiley & Sons, Toronto, Canada, 1988.
  3. C. Jones, "Software Change Management," Computer, vol. 29, no. 2, 1996, pp. 80-82.
  4. B. Boehm, Software Engineering Economics, Prentice-Hall, Englewood Cliffs, NJ, 1981.
  5. G. Stark, A. Skillicorn, and R. Ameele, "An Examination of the Effects of Requirements Changes on Software Releases " Crosstalk: The Journal of Defense Software Engineering, vol. 11, no. 12, 1998, pp. 11-16.
  6. G. Kotonya and I. Sommerville, Requirements Engineering: Processes and Techniques, John Wiley & Sons, Chichester, West Sussex, England, 1998.
  7. J. Siddiqi, "Requirement Engineering: The Emerging Wisdom," IEEE Software, vol. 13, no. 2, 1996, pp. 15.
  8. N. Nurmuliani, D. Zowghi, and S. P. Williams. "Using Card Sorting Technique to Classify Requirements Change," in Proceedings of the 12th IEEE International Requirements Engineering Conference, 2004, pp. 240-248.
  9. B. Lientz and B. Swanson, Software Maintenance Management Addison-Wesley, 1980
  10. I. Sommerville, Software Engineering. 7th ed: Addison-Wesley, 2004
  11. P. Mohagheghi and R. Conradi. "An Empirical Study of Software Change: Origin, Acceptance Rate, and Functionality Vs. Quality Attributes," in Proceedings of the 2004 International Symposium on Empirical Software Engineering (ISESE '04), 2004, pp. 7- 16.
  12. J. Nedstam, E. A. Karlsson, and M. Host. "The Architectural Change Process," in Proceedings of the 2004 International Symposium on Empirical Software Engineering (ISESE '04), 2004, pp. 27-36.
  13. D. Kung, J. Gao, P. Hsia, F. Wen, Y. Toyoshima, and C. Chen. "Change Impact Identification in Object Oriented Software Maintenance," in Proceedings of the International Conference on Software Maintenance, Victoria, BC, 1994, pp. 202-211.
  14. Gall, H. , Hajek, K. , and Jazayeri, M. , "Detection of rational coupling based on product release history," IEEE Int'l Conf. on Softw. Maint. ICSM, pp. 190-198, 1998.
  15. Cataldo, M. , Mockus, A. , Roberts, J. A. , and Herbsleb, J. D. , "Software dependencies, work dependencies, and their impact on failures," IEEE Trans. Softw. Eng. 36, 2, pp. 864-878, 2009.
  16. Zimmermann, T. , and Nagappan, N. , "Predicting defects using network analysis on dependency graphs," Int'l Conf. on Softw. Eng. ICSE, pp. 531-540, 2008.
  17. Kobayashi, K. ; Matsuo, A. ; Inoue, K. ; Hayase, Y. ; Kamimura, M. ; Yoshino, T. ; , "ImpactScale: Quantifying change impact to predict faults in large software systems," Software Maintenance (ICSM), 2011 27th IEEE International Conference on , vol. , no. , pp. 43-52, 25-30 Sept. 2011; doi: 10. 1109/ICSM. 2011. 6080771
  18. Bohner, S. A. , and Arnold, R. S. (Eds. ), "Software change impact analysis," Bohner, S. A. and Arnold, R. S. , "An introduction to software change impact analysis," IEEE Computer Society Press, pp. 1-26, 1996.
  19. Grove,D. , and Chambers,C. , "A framework for call graph construction algorithms," ACM Trans. Program. Lang. Syst. 23, 6, pp. 685-746, 2001.
  20. Law, J. , and Rothermel, G. , "Whole program path-based dynamic impact analysis," Int'l Conf. on Softw. Eng. ICSE, pp. 308-318, 2003.
  21. Ren, X. , Shah, F. , Tip, F. , Ryder, B. G. , and Chesley, O. , "Chianti: a tool for change impact analysis of Java programs," Conf. on Object-Oriented Prog. , Syst. , Lang. , and App. OOPSLA, pp. 432-448, 2004.
  22. J. Bosch, Design and Use of Software Architectures: Addison Wesley, 2000
  23. V. Basili and D. Weiss. "Evaluation of a Software Requirements Document by Analysis of Change Data," in Proceedings of the 5th international conference on Software engineering, San Diego, CA, IEEE Press, 1981, pp. 314-323.
  24. L. C. Briand and V. R. Basili. "A Classification Procedure for the Effective Management of Changes During the Maintenance Process," in Proceeding of the Conference on Software Maintenance, Orlando, FL, 1992, pp. 328-336.
  25. N. H. Madhavji. "The Prism Model of Changes," in Proceedings of the 13th International Conference on Software Engineering Austin, TX, 1991, pp. 166-177.
  26. A. Mockus and L. G. Votta. "Identifying Reasons for Software Changes Using Historic Databases," in Proceedings of the International Conference on Software Maintenance, San Jose, CA, 2000, pp. 120-130.
Index Terms

Computer Science
Information Sciences

Keywords

Artifact change request SDLC software engineering risk prediction

Powered by PhDFocusTM