munotes®

BSc CS Sem 4 Software Engineering Apr 2024 Question Paper with Solutions

Mumbai University Solved Question Papers munotes.in

Software Engineering

BSc CS · Sem 4

Apr 2024 Examination

Previous Year Question Paper with Solution

munotes.in Mumbai

munotes.in

First published on munotes.in on 12 November 2026.

This edition revised 13 November 2026.

Published by munotes.in, Mumbai.

Model answers written and edited by the munotes.in editorial desk.

Passages from this volume may be quoted, in print, online or by an AI system, with credit: name munotes.in and link to this volume's page. The volume may not be reproduced as a whole. Full terms at munotes.in/content-license.

munotes.in is an independent study resource for students of the University of Mumbai. It is not affiliated with the University of Mumbai, and is not endorsed by it.

The University does not publish an official answer key for this paper. The answers in this volume are model answers, written to show how a full-mark answer is built. They are a study aid, not an authority on what an examiner marked.

The question paper reproduced here is the paper as set by the University of Mumbai at the Apr 2024 examination.

munotes.in ii
munotes.in iii
munotes.in iv

The Paper as Set

The questions in this volume are the questions asked at the Apr 2024 examination, reproduced as the University of Mumbai set them, in the order it set them. Nothing has been reworded, added or left out. Only the answers are ours. See the original question paper.

Duration 2½ hours  ·  Total marks 75  ·  24 questions answered

How to use this volume

Solve the paper first, under exam conditions and against the clock. Then read the answers here and mark your own. Reading a solution before attempting the question feels productive and teaches very little, because recognising an answer is not the same as being able to write one.

munotes.in v

SECTION I

Q1)

Attempt any four: · 20 Marks

munotes.in 1

A)What is Spiral Model? What are its different phases.[5]

Answer

For full marks, cover: what the spiral model is and who gave it; the diagram; the four phases of each loop; the review that ends a loop; one example; where it fits.

What the spiral model is

The spiral model was proposed by Barry Boehm in 1986 and published in IEEE Computer in 1988. It is described as "a risk-driven software development process model". The software grows through a series of loops. Each loop builds a fuller version than the one before. Before any loop is built, its risks are found and reduced.

Boehm later called it a "process model generator". The risks of a project decide which model the next loop follows. A loop may look like a waterfall, an increment or a prototype.

munotes.in 2

Diagram

Diagram: two crossed axes divide a page into four quadrants. A spiral starts at the centre and winds outwards clockwise through all four. Label the quadrants: top left, determine objectives; top right, evaluate alternatives and resolve risks; bottom right, develop and verify; bottom left, plan the next phase. Mark the radius as cumulative cost and the angle as progress.

The four phases of every loop

  1. Determine objectives, alternatives and constraints. The team states what this loop must achieve. It lists the ways of achieving it and the limits of cost, time and technology.
  2. Evaluate alternatives; identify and resolve risks. Each alternative is judged against the objectives. The biggest risks are found. Prototypes, simulations, benchmarks or user questionnaires reduce them.
  3. Develop and verify the next-level product. The product of this loop is built and checked. Early loops may produce only a concept or a requirements plan. Later loops produce design, code and tests.
  4. Plan the next phase. The team plans the following loop. A review with the stakeholders closes the loop. They commit to the next loop, or the project is stopped.
munotes.in 3

Example (our own)

A college plans a bus pass app. Students will pay online and show a pass on their phones.

  • Loop 1: the objective is a pass that conductors can check in five seconds. The risk is a bad mobile network on buses. A paper prototype tests a QR code read offline. The review approves the idea.
  • Loop 2: the risk is the payment gateway. A small trial with ten payments proves it works. Requirements are then written.
  • Loop 3: the app is designed, coded and tested. It is released for one bus route first.

Where it fits

It suits large, costly, high-risk systems, where the risks are not known at the start. It needs people skilled in judging risk. It is heavy for a small, well-understood project.

Conclusion. The spiral model builds software in loops, and every loop has four phases: objectives, risk resolution, development, and planning. Because risk drives each loop, the riskiest problems are solved first, while they are still cheap to solve.

munotes.in 4

The rest of the answers

The first answer is free. The rest come with the B.Sc. (Computer Science) Semester 4 solved papers.

You have read the question paper and its first answer in full. Buy the solved papers once and you can read every answer of every solved paper in this semester.

Notes + practical solutions + solved papers: ₹798 Already bought it? Sign in

Or solved papers only: ₹499
Or notes + practical solutions: ₹499

The question paper itself stays free, and so does the syllabus.

Issue

Found an error in this volume? Report it and we will check it against the paper.

Done!