CS301 HIGHLIGHTED HANDOUTS GET PDF FILES FROM THE BELOW LINK.
In this lecture, we will discuss the “software crisis” in detail with the reason behind this crisis. It will be followed by a discussion on the classic model with reference to the waterfall model and V model, what are the drawbacks of this model, and then the need for an Agile process model.
CS301 HIGHLIGHTED HANDOUTS
MUST JOIN MY TELEGRAM GROUP FOR ALL ASSIGNMENTS, GDB, MIDTERM PAST PAPERS, AND FINAL TERM PAST PAPERSFROM THE BELOW LINK:
History of software crisis:
The software crisis was a term used in the early days of computing science. The term was used to describe the impact of rapid increases in computer power and the complexity of the problems which could be tackled.
In essence, it refers to the difficulty of writing correct, understandable, and verifiable computer programs. The term “software crisis” was coined by F. L. Bauer at the first NATO Software Engineering Conference in 1968 at Garmisch, Germany Software CHAOS Report Standish Group Study.
In 1986, Alfred Spector, president of Transarc Corporation, co-authored a paper comparing bridge building to software development. The premise: Bridges are normally built on time, on budget, and do not fall down. On the other hand, the software never comes in on time or on budget.
CS301 HIGHLIGHTED HANDOUTS-DATA STRUCTURE:
In addition, it always breaks down. (Nevertheless, bridge building did not always have such a stellar record. Many bridge-building projects overshot their estimates, time frames, and some even fell down.).
One of the biggest reasons bridges come in on time, on budget, and do not fall down is because of the extreme detail of the design. The design is frozen and the contractor has little flexibility in changing the specifications.
However, in today’s fast-moving business environment, a frozen design does not accommodate changes in business practices. Therefore a more flexible model must be used. This could be and has been used as a rationale for development failure.
CS301 HIGHLIGHTED HANDOUTS PDF-DATA STRUCTURE:
But there is another difference between software failures and bridge failures, besides 3,000 years of experience. When a bridge falls down, it is investigated and a report is written on the cause of the failure.
This is not so in the computer industry where failures are covered up, ignored, and/or rationalized. As a result, we keep making the same mistakes over and over again.
CS301 HIGHLIGHTED HANDOUTS PDF DOWNLOAD-DATA STRUCTURE: