The text of this article is not in this database — only its details are. Read it on the old site: System Development Life Cycle: Part 1
2 Comments
Join the conversation! Your thoughts help the community grow.
Sign in to leave a comment.
The text of this article is not in this database — only its details are. Read it on the old site: System Development Life Cycle: Part 1
Join the conversation! Your thoughts help the community grow.
Sign in to leave a comment.
Jaque JarowskiPosted Mar 1, 2021, 9:25 AM
Thank you for sharing such knowledge about the software development lifecycle model, i.e. from collecting and analyzing requirements, designing, implementing or coding, testing, deploying, maintaining, that really helps you understand the software development lifecycle model.
Sam HobbsPosted Apr 28, 2011, 2:57 PM
Thank you for this; I think it is a good beginning for understanding SDLC. I think one thing that would help is to emphasize the "cycle" part of Software Development Life Cycle. SDLC is designed to be reiterative in two ways; a design phase is supposed to be initiated when any changes are made (requested or discovered) to the design. In other words, when changes are discovered, coding is supposed to stop until an appropriate redesign is completed. Also, in the real world, systems undergo extensive changes. Businesses change the way they do business. Management changes and do things differently. The laws change in ways that affect software. The SDLC can be highly effective for many years after a system has been developed. I think all this is fundamental and critical to the SDLC and it helps to emphasize these.