Unit 1 of 4 · MBA Sem 4

Unit 1: Software development process

Managing Software Projects notes · PTU syllabus (MBA 943-18)

3 min read6 topics10 exam questions
On this page
  1. Unit summary
  2. Evolving role of software
  3. The software crisis and software myths
  4. Software engineering: a layered technology
  5. Software process models
  6. Agile development
  7. Choosing an appropriate methodology
  8. Key terms
  9. Quick revision
  10. Important questions

Unit summary

Software runs modern business, yet software projects are notorious for overruns. This unit covers the evolving role of software, the software crisis and myths, software engineering as a layered technology, process models — waterfall, prototyping, RAD, evolutionary, agile and component-based development — and choosing an appropriate methodology.

After this unit you can

  • Explain the evolving role of software and the software crisis
  • Identify software myths and explain the layered technology of software engineering
  • Compare software process models
  • Choose an appropriate development methodology

PTU syllabus topics

  • Evolving role of software
  • software crisis and myths
  • layered technology
  • process models — waterfall
  • prototyping
  • RAD
  • evolutionary
  • agile
  • component-based development
  • choosing an appropriate methodology
1

Topic 1

Evolving role of software

  • Software is both a product (delivering computing capability) and a vehicle for delivering products (operating systems, networks, tools).
  • Eras: batch systems → real-time and multi-user → distributed and embedded → object-oriented, internet and mobile → cloud, AI and SaaS.
  • Categories: system software, application software, engineering and scientific, embedded, product-line, web and mobile apps, AI software.
  • Characteristics: software is developed, not manufactured; it does not wear out but deteriorates through changes; most is custom-built or assembled from components.
2

Topic 2

The software crisis and software myths

  • Software crisis: projects late, over budget, unreliable, hard to maintain, not meeting requirements.
ClassificationSoftware myths (Pressman)
Myths
  • Management myths

    "We have standards, so we are fine"; "If behind schedule, add more programmers"

  • Customer myths

    "A general statement of objectives is enough to start"; "Changes are easy because software is flexible"

  • Practitioner myths

    "Once the program works, the job is done"; "The only deliverable is working code"

  • Brooks's law: adding people to a late software project makes it later.
3

Topic 3

Software engineering: a layered technology

Pressman describes software engineering as four layers. A quality focus is the base; on it rest the process, the methods and the tools.

HierarchyLayers of software engineering
  1. Tools

    Automated support — CASE, IDEs, version control

  2. Methods

    Technical how-tos — analysis, design, coding, testing

  3. Process

    Framework of activities, KPAs, milestones

  4. Quality focus

    Foundation — commitment to quality

Example

In one project: the commitment to defect-free delivery is the quality focus. Agile sprints are the process. Use-case modelling and unit testing are methods. Git, Jira and an IDE are tools.

4

Topic 4

Software process models

A process model sets the order of development activities. The right one depends on how clear the requirements are and how much risk the project carries.

GraphWaterfall model: each phase flows into the next
RequirementsDesignImplementationTestingDeployment andmaintenance

Simple and well documented but rigid: changes are costly and the customer sees working software late

ComparisonProcess models
How it works
Best suited when

Waterfall (linear sequential)

Requirements → design → coding → testing → maintenance, in sequence

Requirements are clear and stable

Prototyping

Build a quick model to clarify requirements, refine with users

Requirements are unclear

RAD (rapid application development)

Component reuse and parallel teams for very short cycles (60–90 days)

Modular systems, time pressure

Evolutionary — incremental

Deliver in increments, each adding features

Early partial delivery needed

Evolutionary — spiral (Boehm)

Iterative cycles with explicit risk analysis

Large, high-risk projects

Component-based development

Assemble systems from reusable components

Mature component libraries exist

ProcessWaterfall model
  1. 1

    Requirements analysis

  2. 2

    System design

  3. 3

    Implementation (coding)

  4. 4

    Testing

  5. 5

    Deployment

  6. 6

    Maintenance

Example

Choosing a model: a payroll system with fixed, well-known requirements suits waterfall. A mobile app whose features will change with user feedback suits agile. A large, risky defence system suits the spiral model, with risk analysis in each loop.

5

Topic 5

Agile development

  • Agile Manifesto (2001): individuals and interactions over processes and tools; working software over documentation; customer collaboration over contract negotiation; responding to change over following a plan.
CycleScrum framework
Scrum framework
1Product backlog
2Sprint planning
3Sprint (1–4 weeks)
4Sprint review
5Sprint retrospective
  1. 1. Product backlog:
  2. 2. Sprint planning:
  3. 3. Sprint (1–4 weeks): Daily stand-up
  4. 4. Sprint review: Demo to stakeholders
  5. 5. Sprint retrospective: Improve the process
  • Roles: product owner, scrum master, development team. Other methods: Kanban, Extreme Programming (pair programming, test-driven development), Lean, SAFe for scale; DevOps integrates development and operations through continuous integration and delivery.
6

Topic 6

Choosing an appropriate methodology

  • Factors: clarity and stability of requirements, project size and complexity, risk, customer availability, team skills and distribution, regulatory and documentation needs, time-to-market.
ComparisonPlan-driven vs agile
Plan-driven (waterfall)
Agile

Requirements

Fixed upfront

Evolving

Documentation

Heavy

Light, just enough

Customer involvement

At start and end

Continuous

Delivery

Single release

Frequent increments

Suits

Regulated, fixed-scope contracts

Fast-changing markets, product development

Key terms

Software crisis
Chronic problems of late, costly, unreliable software
Brooks's law
Adding people to a late project makes it later
Prototyping
Building a quick model to clarify requirements
Spiral model
Iterative model with explicit risk analysis
Scrum
Agile framework using time-boxed sprints

Quick revision

  • Role and characteristics of software; categories.
  • Software crisis; management, customer, practitioner myths.
  • Layers: quality, process, methods, tools.
  • Waterfall, prototyping, RAD, incremental, spiral, component-based; agile and Scrum; DevOps.
  • Choosing a method; plan-driven vs agile.

Important exam questions

Practice questions written to the PTU exam pattern for this unit's syllabus: short answers (Section A style) and long answers (Sections B and C style).

Short-answer questions

  1. Q1.Why does software not wear out?
  2. Q2.State two management myths about software.
  3. Q3.What is Brooks's law?
  4. Q4.Name the layers of software engineering.
  5. Q5.When is prototyping preferred?
  6. Q6.State the four values of the Agile Manifesto.

Long-answer questions

  1. Q1.Explain the evolving role of software and the software crisis.
  2. Q2.Discuss software myths and software engineering as a layered technology.
  3. Q3.Compare waterfall, prototyping, RAD and spiral models.
  4. Q4.Explain agile development and the factors in choosing a methodology.

Stuck on this unit?

Message SBS on WhatsApp for help with Managing Software Projects, or to ask about studying MBA at Synetic.

Planning your MBA in Ludhiana? See the MBA at SBS →

WhatsApp us