Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

Introduction to Software Engineering-Enterprise Applicatio Development-Lecture Handout, Exercises of Software Development

This lecture handout was provided by Sir Aabher Dutt at Indian Institute of Space Science and Technology for Enterprise Application Development course. It includes: Introduction, Software, Engineering, Crisis, Development, Process, Hardware, Complexity, Waterfall, Incremental

Typology: Exercises

2011/2012

Uploaded on 07/19/2012

pankti
pankti 🇮🇳

4.1

(8)

50 documents

1 / 5

Related documents


Partial preview of the text

Download Introduction to Software Engineering-Enterprise Applicatio Development-Lecture Handout and more Exercises Software Development in PDF only on Docsity! Table of Contents 1 Background Discussion.......................................................................................................................................6 2 Advancements......................................................................................................................................................6 3 Software Crisis.....................................................................................................................................................6 4 What is Software and Software Engineering.......................................................................................................7 5 Software development process............................................................................................................................7 5.1 General Model..................................................................................................................................................7 6 Overlapping with Other Fields.............................................................................................................................9 7 Conclusion...........................................................................................................................................................9 8 References............................................................................................................................................................9 5 docsity.com 1 Background Discussion Software Engineering is an extensive and large computer field. It came into existence after a great effort of computer scientist and it's supreme need. The term Software Engineering was first used in late 1950's and early 1960's. Before the concept of Software Engineering, punch cards and other handy methods were used to operate a program on computer. It required a great and a lot of precious time. Scientists of IBM and other big companies sit together to have a proper way to solve problems and they emphasize to build a basic skeleton which can easily be reused. Ideas of modularity and re useability were also new at that time. Based on these ideas, there was an emergence of Software Engineering. Initial boast to field was given by NATO SCIENCE COMITTEE by sponsoring two conferences in years 1968 and 1969 respectively. In the early days of computing the primary concern was with building or acquiring the hardware. Software was almost expected to take care of itself. The consensus held that "hardware" is "hard" to change, while "software" is "soft," or easy to change. According, most people in the industry carefully planned hardware development but gave considerably less forethought to the software. If the software didn't work, they believed, it would be easy enough to change it until it did work. 2 Advancements As programs became more complex, the early methods used to make blueprints (flowcharts) were no longer satisfactory to represent this greater complexity. And thus it became difficult for one person who needed a program written to convey to another person, the programmer, just what was wanted, or for programmers to convey to each other what they were doing. In fact, without better methods of representation it became difficult for even one programmer to keep track of what he or she is doing. 3 Software Crisis Unfortunately, until several years ago no good method of representation existed to describe satisfactorily systems as complex as those that are being developed today. The only good representation of what the product will look like was the finished product itself. Developers could not show clients what they were planning. And clients could not see whether what the software was what they wanted until it was finally built. Then it was too expensive to change. This was referred to as Software Crisis. 6 docsity.com
Docsity logo



Copyright © 2024 Ladybird Srl - Via Leonardo da Vinci 16, 10126, Torino, Italy - VAT 10816460017 - All rights reserved