~3m10:34
Gate Smashers

What is Software Engineering and its Evolution in Hindi with examples

May 8, 2020

Read: ~3m · You save: 8 min

What is Software Engineering and its Evolution (in Hindi, with examples)

Discover what software engineering really means beyond coding, why the 1965-85 software crisis happened, and how the field evolved into today's AI-driven world.

Definition

Software engineering is a systematic, disciplined, and cost-effective technique for software development.

  • Systematic: Development follows a step-by-step approach.
  • Disciplined: Work follows defined rules and proceeds on a regular basis. Work is not performed in bursts followed by long gaps. Each phase is completed within its deadline.
  • Cost-effective: Development stays within budget. Cost is a key parameter. Time is also a key constraint, and work must be completed within the scheduled time.

Software engineering does not concern only the writing of code. It covers the complete development process, from the initial idea to maintenance. The main stages are:

  1. Idea
  2. Requirements
  3. Feasibility study and planning
  4. Design
  5. Implementation
  6. Testing
  7. Product delivery
  8. Maintenance and regular updates

The term "engineering approach" refers to this step-by-step, systematic process that moves from the first stage to the last. It does not refer to work performed by engineers.

Engineering Approach Compared with Build-and-Fix

The source illustrates the difference with a comparison between branded and non-branded vehicles. The example is based on the author's personal experience.

Non-branded (build-and-deliver):

  • Modified jeeps are produced locally.
  • Mechanics remove the engine of an old jeep, install broad tyres, and build a new body.
  • The vehicle is delivered to the market without testing.
  • The vehicle may work for a short distance, such as 2 kilometres or 200 kilometres, but it fails on a long drive.

Branded (engineering approach):

  • Manufacturers such as Mahindra (Thar), Jeep, and Toyota (SUV) follow each step in a defined process.
  • The manufacturer provides maintenance after delivery. For example, a customer can visit the showroom five years after purchase and still receive maintenance services, for which a charge applies.

The same principle applies to software. A structured approach from idea through maintenance and updating defines software engineering.

Evolution of Software Engineering

Origin (1945–1965)

The term "software engineering" originated between 1945 and 1965. Software development began during World War II. NASA, IBM, and other large organizations started development work independently. At that time, no one used the term "engineering." Work consisted of simple software development based on the build-and-fix method, also called the build-and-deliver method. Developers produced a product and released it without completing the full set of steps.

The source states that this method created problems over the long term. Early results could work initially, but they were not effective over time. The term "software engineering" was first named at a series of NATO conferences.

Software Crisis (1965–1985)

The period from 1965 to 1985 is known as the software crisis. The crisis resulted from the absence of a structured approach. Developers still followed the build-and-deliver method, aiming to complete tasks quickly and deliver them to clients.

The main problems were:

  • Low usage: Only about 2% of the software produced during this period was used.
  • Non-delivery: Approximately 45–50% of the software was never delivered and was scrapped.
  • Budget overruns: Projects exceeded their budgets. The source gives an example of a project with a budget of 1 billion that had already consumed 1 billion while remaining incomplete.
  • Time overruns: Projects exceeded their scheduled time.
  • Complexity: Multiple factors increased project complexity.

OS/360 (IBM): IBM's OS/360 operating system is cited as a major failure. The project leader later described it as a multi-million-dollar failure. According to the source, the project began without a prior design. No coherent design was prepared. Developers began coding and implementation directly and released the product to the market.

The source attributes this failure to not following the engineering approach. It notes that following the approach does not guarantee success. It does, however, increase the probability of success, while not following it increases the probability of failure.

The crisis continued after 1985. The following projects are cited:

  • Torus project (UK): Developed over 10–12 years at a cost of a large amount of British pounds. The project was ultimately scrapped.
  • Autonomous system project (US): Development ran for a period recorded in the source as "11:50 years." The budget overran, and the project was scrapped.

Internet Era (After 1990)

After 1990, the Internet era began. Microsoft Windows, a system software also known as an operating system, was released during this period. Web browsers were widely developed.

Mobile Era

The mobile era introduced lightweight software. Earlier software ran on personal computers. Lightweight platforms and lightweight software were developed so that applications could run on mobile devices.

AI and Machine Learning (After 2010)

After 2010, the focus shifted to artificial intelligence, machine learning, and deep learning. These technologies apply the concept of self-learning in software, in which a system attempts to learn on its own, similar to a human.

Open Software

A major change in the evolution of software is the shift from proprietary to free software. Earlier, companies developed software and kept it under their control. Most software is now free, which allows people to study, work on, and learn from it.

Summary of Evolution

PeriodKey Characteristics
1945–1965Origin of the term; build-and-fix development; work begins during World War II
1965–1985Software crisis; about 2% of software used; 45–50% not delivered; budget and time overruns
After 1990Internet era; Microsoft Windows; web browsers
Mobile eraLightweight software and platforms for mobile devices
After 2010AI, machine learning, and deep learning; self-learning software
Current trendShift from proprietary to free software

Definition and Engineering Approach

Software engineering is a systematic, disciplined, cost-effective technique for software development, focused on the full process rather than coding alone.

  • Definition: a systematic, disciplined, cost-effective technique for software development
  • Systematic means step-by-step; disciplined means following rules, regular work, and proper deadlines
  • Cost-effective means working within budget; time is also a key constraint
  • Software engineering is a whole approach, not just how to code
  • Lifecycle steps: idea, requirement, feasibility study, planning, implementation, design, testing, maintenance, product delivery
  • Engineering approach means step-by-step systematic progress from first step to last to achieve the goal

Real-Life Example: Branded vs Non-Branded

The lecture uses branded versus non-branded modified jeeps to illustrate the difference between a complete engineering approach and a build-and-deliver approach.

  • Non-branded modified jeeps: old engine removed, broad tyres installed, good body built, then sold without testing
  • Non-branded method is build and deliver; the vehicle may fail after 2 km or 200 km, and the speaker cites personal experience
  • Branded examples: Mahindra Thar, Jeep company, Toyota SUV
  • Branded companies follow all steps and provide maintenance services even 5 years after purchase, for a charge
  • The point is the approach (idea to maintenance, then regular updates), not the skill or degree of the person

Origin of Software Engineering (1945-65)

Software engineering originated around 1945-65 during World War II, when software development began, initially using build-and-fix methods; the term was named at NATO conferences.

  • Term software engineering originated between 1945-65
  • Development began around World War II, with NASA, IBM and other organizations starting work
  • Build-and-fix (build and deliver) method was used, leading to likely long-term problems
  • The term was first named at famous NATO conferences

Software Crisis (1965-85)

The 1965-85 software crisis saw massive failures, with only about 2% of software used and 45-50% never delivered, due to lack of an engineering approach.

  • Only about 2% of software made at the time was actually used
  • Approximately 45-50% of software was never delivered and was scrapped
  • Common problems: budget overruns (example: 1 billion budget fully spent with software incomplete), time overruns, complexity
  • IBM OS/360 operating system was a failure; its leader called it a multi-million dollar failure because no coherent design was prepared beforehand
  • Torus project: 10-12 years of work and many UK pounds spent, still scrapped
  • US autonomous system project: 11-50 years of work mentioned, budget overrun, scrapped
  • Following the approach does not guarantee success, but increases the probability of success

Evolution After 1990: Internet, Mobile, AI and Free Software

After 1990, the Internet era brought popular system software and web browsers; later phases brought lightweight mobile software and AI/ML.

  • Internet era began after 1990
  • Microsoft Windows, a system software also called an operating system, emerged in this period
  • Web browsers were widely developed during the Internet phase
  • Mobile phase emphasized lightweight software and lightweight platforms
  • After 2010: AI, machine learning, deep learning, and self-learning software
  • Most software is now free, whereas earlier it was proprietary and kept by companies, enabling people to learn and work on it

Exam Relevance

The lecture closes by noting that these evolution topics can appear in exams, college or university tests, and placements.

  • Evolution topics may be asked in college/university exams and placements
  • The speaker thanks viewers at the end