munotes®

BSc CS Sem 4 Software Engineering Mar 2026 Question Paper with Solutions

Mumbai University Solved Question Papers munotes.in

Software Engineering

BSc CS · Sem 4

Mar 2026 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 Mar 2026 examination.

munotes.in ii
munotes.in iii

The Paper as Set

The questions in this volume are the questions asked at the Mar 2026 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 1 hours  ·  Total marks 30  ·  12 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 iv

SECTION I

Q I)

Attempt any two · 10 Marks

munotes.in 1

1.Define software engineering principles. Explain how engineering practices differ from coding.[5]

Answer

For full marks, cover: the definition of a principle; Hooker's seven principles, a line each; what engineering practice is, in Polya's four steps; a table of differences of at least six rows; one example; a one-line conclusion.

Software engineering principles

A software engineering principle is a basic rule of good practice that guides every activity of development. It holds whatever process model, method or tool the team uses. A principle answers why. A method answers how, and a tool answers with what.

David Hooker's seven principles (1996) are the best-known set:

  1. The Reason It All Exists. In Hooker's words, "A software system exists for one reason: to provide value to its users". Every decision is judged by that.
  2. KISS (Keep It Simple, Stupid!). Keep the design as simple as possible, without dropping needed features. Simple does not mean quick and dirty.
munotes.in 2
  1. Maintain the Vision. One clear vision keeps the system from becoming a patchwork of designs that do not fit.
  2. What You Produce, Others Will Consume. Specify, design and code knowing that someone else must understand and maintain it.
  3. Be Open to the Future. A system that lasts must adapt, so never design yourself into a corner.
  4. Plan Ahead for Reuse. Reuse saves time and effort, but only when it is planned.
  5. Think! Clear, complete thought before action gives better results. Hooker says the other six depend on it.

What engineering practice is

Software engineering practice is the set of concepts, principles, methods and tools that a software engineer applies daily. Its essence is George Polya's four steps of problem solving, from How to Solve It (1945):

Polya's stepSoftware activity
Understand the problemCommunication and analysis
Plan a solutionPlanning and design
Carry out the planCode generation
Examine the resultTesting and review

How engineering practice differs from coding

munotes.in 3
PointCodingEngineering practice
ScopeOne program, one taskThe whole system and its whole life
Starting pointA task that seems clearThe problem, understood with the customer and written down
DocumentsThe code, perhaps with commentsRequirements, design, test plan, user documents
ReviewsThe author checks own workRequirements, design and code reviewed by others
TestingA few likely inputsPlanned tests from the requirements, awkward cases included
EstimationNoneSize, effort, cost and time estimated and tracked
ChangeEdit the code when askedChanges assessed, approved, recorded and retested
munotes.in 4
PointCodingEngineering practice
TeamOne personMany people with roles, working to one design
AccountabilityDoes it run?Does it meet the need, on time and within budget?

Example

ShelfWise is a library management system for a college library. Its fine is Rs 2 for each day late, never more than Rs 100 for one copy. A developer told only the first half codes the fine as days late × 2. That code charges minus Rs 6 for a copy returned three days early. It charges Rs 102 for 51 days late, above the cap. Practice would have understood the rule first and tested those cases, giving Rs 0 and Rs 100.

Conclusion. Coding is one activity inside engineering practice. Principles guide the practice, and the practice turns them into software that meets its users' need and can be trusted and changed.

munotes.in 5

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!