Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Systems development life cycle
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== Strengths and weaknesses == Fundamentally, SDLC trades flexibility for control by imposing structure. It is more commonly used for large scale projects with many developers. {| class="wikitable" style="margin:auto;" |+ Strength and Weaknesses of SDLC<ref name="Post, G. 2006"/> |- !style="background:#ffdead;"| Strengths !style="background:#ffdead;"| Weaknesses |- | Control | Increased development time |- | Monitor large projects | Increased development cost |- | Detailed steps | Systems must be defined up front |- | Evaluate costs and completion targets | Rigidity |- | Documentation | Hard to estimate costs, project overruns |- | Well defined user input | User input is sometimes limited |- | Ease of maintenance | Little parallelism |- | Development and design standards | Automation of documentation and standards is limited |- | Tolerates changes in MIS of staffing | Does not tolerate changes in requirements |- | | Projects canned early on the result in little or no value |}
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)