Call for Paper - November 2022 Edition
IJCA solicits original research papers for the November 2022 Edition. Last date of manuscript submission is October 20, 2022. Read More

Awareness Regarding Importance of SDLC among IT Professionals and Students: A Survey

Print
PDF
International Journal of Computer Applications
Foundation of Computer Science (FCS), NY, USA
Year of Publication: 2019
Authors:
Syeda Nazia Ashraf
10.5120/ijca2019919026

Syeda Nazia Ashraf. Awareness Regarding Importance of SDLC among IT Professionals and Students: A Survey. International Journal of Computer Applications 178(18):38-46, June 2019. BibTeX

@article{10.5120/ijca2019919026,
	author = {Syeda Nazia Ashraf},
	title = {Awareness Regarding Importance of SDLC among IT Professionals and Students: A Survey},
	journal = {International Journal of Computer Applications},
	issue_date = {June 2019},
	volume = {178},
	number = {18},
	month = {Jun},
	year = {2019},
	issn = {0975-8887},
	pages = {38-46},
	numpages = {9},
	url = {http://www.ijcaonline.org/archives/volume178/number18/30638-2019919026},
	doi = {10.5120/ijca2019919026},
	publisher = {Foundation of Computer Science (FCS), NY, USA},
	address = {New York, USA}
}

Abstract

This paper aims to create awareness regarding importance and need of Software Development Life Cycle (SDLC) among IT

Professionals and Students in executing projects. The SDLC itself is the solution for the success of projects but there is always a room for improvement and its awareness will highlight the areas of SDLC in detail and its need and importance. In this paper, we focus on strengths and weaknesses of SDLC. What are the impacts for selecting right SDLC process models? What are the Risk Factors involved in SDLC Phases? In this regard, some survey results also included to emphasis the importance of SDLC in IT based projects. Survey indicate that, in every organization SDLC implemented by different professionals of every field as well as students in their respective area of projects.

References

  1. S. Balaji and M. S. Murugaiyan, "Waterfall vs. V-Model vs. Agile: A comparative study on SDLC," International Journal of Information Technology and Business Management, vol. 2, pp. 26-30, 2012.
  2. P. Jirava and D. Series, "System development life cycle," Scientific Papers of the University of Pardubice Series D. Pardubice: Univerzita Pardubice, pp. 118-125, 2004.
  3. M. Tanveer, "Agile for large scale projects—A hybrid approach," in 2015 National Software Engineering Conference (NSEC), 2015, pp. 14-18.
  4. A. S. Shaffi and M. Al-Obaidy, "Analysis and comparative study of traditional and web information systems development methodology (WISDM) towards Web development applications," International Journal of Emerging Technology and Advanced Engineering, vol. 3, pp. 277-282, 2013.
  5. M. Sharma, "A Survey of project scenario impact in SDLC models selection process," International Journal of Scientific & Engineering Research, vol. 2, pp. 1-4, 2011.
  6. H. Hijazi, S. Alqrainy, H. Muaidi, and T. Khdour, "Risk factors in software development phases," European Scientific Journal, ESJ, vol. 10, 2014.
  7. APENDIX A
  8. Table Survey Questions
  9. Strongly Agree
  10. Agree
  11. Neutral
  12. Disagree
  13. Strongly Disagree
  14. Not Applicable
  15. 
  16. The project could have been completed faster, but that would have meant a lower quality product
  17. 14
  18. 18
  19. 15
  20. 13
  21. 2
  22. 3
  23. 
  24. Corrective hours resolving runtime problems are/were minimal
  25. 9
  26. 27
  27. 21
  28. 5
  29. 0
  30. 3
  31. 
  32. Project costs were within budget estimates
  33. 13
  34. 28
  35. 11
  36. 4
  37. 1
  38. 7
  39. 
  40. The duration of the project was/is within schedule
  41. 18
  42. 33
  43. 7
  44. 4
  45. 1
  46. 2
  47. 
  48. Capabilities of the finished product fitted well with customer or user needs
  49. 9
  50. 39
  51. 7
  52. 3
  53. 1
  54. 5
  55. 
  56. The quality of the development team's work was acceptable
  57. 9
  58. 47
  59. 6
  60. 1
  61. 0
  62. 2
  63. 
  64. End-users found the finished product was easy to use
  65. 10
  66. 43
  67. 8
  68. 1
  69. 1
  70. 2
  71. 
  72. The ability and previous experience of the software development team was/is
  73. adequate
  74. 2
  75. 33
  76. 1
  77. 1
  78. 10
  79. 8
  80. 
  81. Project goals were/are achieved earlier than predicted
  82. 6
  83. 26
  84. 14
  85. 13
  86. 2
  87. 5
  88. 
  89. The team size was/is adequate for the project
  90. 7
  91. 41
  92. 8
  93. 5
  94. 2
  95. 2
  96. 
  97. Selecting an appropriate SDLC model is a complex and a challenging task, which requires not only broad theoretical knowledge, but also consultation with experienced expert managers.
  98. 11
  99. 38
  100. 0
  101. 0
  102. 0
  103. 6
  104. 
  105. System Development Life Cycles play a very important role on the success of the projects
  106. 17
  107. 36
  108. 0
  109. 0
  110. 1
  111. 0
  112. 
  113. Right selection of SDLC methodology can help successful completion of project on time and within budget
  114. 19
  115. 39
  116. 3
  117. 3
  118. 0
  119. 0
  120. 
  121. In SDLC, there is a possibility of combining two or more project management methodologies for the best outcome.
  122. 9
  123. 36
  124. 11
  125. 2
  126. 1
  127. 4
  128. 
  129. SDLC also heavily emphasizes on the use of documentation and has strict guidelines on it.
  130. 6
  131. 43
  132. 8
  133. 0
  134. 2
  135. 1
  136. 
  137. Waterfall (traditional)model is not capable of addressing the challenges in the modern software development domain.
  138. 6
  139. 27
  140. 13
  141. 0
  142. 2
  143. 1
  144. 
  145. Development of criteria for model selection is that one should consider employing a Decision Support Systems (DSS), expert systems(ES) or knowledge-based systems perceived as the first step towards building a system.
  146. 2
  147. 40
  148. 0
  149. 2
  150. 3
  151. 5
  152. 
  153. When it comes to selecting an appropriate Project
  154. Management Methodology, there are a few dozens of factors you should consider. Each project management methodology carries its own strengths and weaknesses.
  155. 8
  156. 41
  157. 0
  158. 2
  159. 2
  160. 3
  161. 
  162. There is no good or bad methodology and what you should follow is the most suitable one for your project management requirements.
  163. 11
  164. 37
  165. 8
  166. 0
  167. 1
  168. 1
  169. 
  170. The particular life cycle model can significantly affect various concerns associated with a software product. If the process is weak, the end product certainly will suffer.
  171. 8
  172. 24
  173. 0
  174. 3
  175. 9
  176. 0
  177. 
  178. 

Keywords

SDLC, RAD, Risk Factor, RD, AD