Software crisis is a term used in Computer Science in the early’s 60, for the difficulty of writing useful and efficient computer programs at the required time. It was due to using the same workforce, same methods, and the same tools even though rapidly increasing in software demand, complexity, and challenges.
What are the symptoms of a Software crisis?
- Fails to meet user requirements.
- Expensive to handle or manage.
- Difficult to alter, debug, and enhance.
- Often delivered late.
- Use resources non-optimally.
Which factors are the key contributors to the Software crisis?
- Larger problems
- Poor Project management
- Lack of adequate training in Software Engineering
- Increasing skill shortage
- Low Productivity improvements
Now the question comes to mind: If there are so many problems with software projects, why don’t we move to entirely hardware solutions?
The virtue of Software projects is that they are relatively easy to change and faster to develop. It does not consume space, weight, and power. Moreover, It also does not require a huge investment in infrastructure building. So the better approach is to standardized the development process.
Reference
- Fundamentals of Software Engineering Book & NPTEL Video Lectures by Rajib Mall.
CITE THIS AS:
“Need for SDLC: Software Crisis” From NotePub.io – Publish & Share Note! https://notepub.io/notes/software-engineering/software-development-life-cycle/need-for-sdlc-software-crisis/
770 total views, 1 views today
