BE Computer Engineering (IOE, TU) Software Engineering (IOE, CT 601 / ENCT 352) Question Paper 2079
This is the official BE Computer Engineering (IOE, TU) Software Engineering (IOE, CT 601 / ENCT 352) question paper for 2079, as set in the regular annual examination. It carries 80 full marks and a time allowance of 180 minutes, across 12 questions. On Kekkei you can attempt this Software Engineering (IOE, CT 601 / ENCT 352) past paper online with a timer, get instant AI feedback and step-by-step solutions, and track the topics where you lose marks — completely free. Whether you are revising for your BE Computer Engineering (IOE, TU) Software Engineering (IOE, CT 601 / ENCT 352) exam or solving previous years' question papers, this 2079 paper is a great way to practise under real exam conditions.
Section A: Long Answer Questions
Attempt all / any as specified.
(a) Compare the Waterfall model and the Spiral model of software development with respect to risk handling, customer involvement, and suitability for large-scale projects. (8)
(b) For a project where requirements are expected to evolve significantly and the customer wants to see working software early and frequently, recommend a suitable process model and justify your choice. (4)
Consider a Library Management System for a university that must support member registration, book issue/return, fine calculation, and online catalogue search.
(a) Identify the major functional and non-functional requirements of this system. (5)
(b) Draw a Context-level (Level-0) Data Flow Diagram and a Level-1 DFD for the book issue and return process. (7)
(a) Explain the layered (n-tier) software architecture style. Discuss its advantages and limitations, and give one application domain where it is appropriate. (7)
(b) Differentiate between black-box testing and white-box testing. For a function that computes the grade of a student from a numeric score (0-100), design black-box test cases using equivalence partitioning and boundary value analysis. (5)
(a) Describe the three modes of the Basic COCOMO model (organic, semi-detached, embedded) and state the conditions under which each is applicable. (4)
(b) A software project is estimated to have 40 KLOC of delivered source code and is classified as an organic project. Using Basic COCOMO (E = a(KLOC)^b person-months, D = c(E)^d months with a=2.4, b=1.05, c=2.5, d=0.38), compute the estimated effort, development time, and average staffing required. (8)
Section B: Short Answer Questions
Attempt all / any as specified.
What is a Software Requirements Specification (SRS) document? List and briefly explain the desirable characteristics of a good SRS as per IEEE 830.
Define Software Configuration Management (SCM). Explain the role of baselines and version control in managing changes to software work products throughout the project life cycle.
Differentiate between verification and validation. Explain the V-model of software testing and how it relates each testing level to a corresponding development phase.
What is software maintenance? Explain the four types of maintenance (corrective, adaptive, perfective, and preventive) with a suitable example of each.
Explain coupling and cohesion as measures of software design quality. Why is a design with low coupling and high cohesion considered desirable? Give examples of one type of coupling and one type of cohesion.
Draw and explain a Gantt chart and a network (PERT/CPM) diagram as project scheduling tools. State one advantage of each in monitoring software project progress.
Explain the Capability Maturity Model Integration (CMMI). Briefly describe its five maturity levels and how they help an organization improve its software process.
Write short notes on any TWO of the following: (a) Use-case diagram (b) Requirement elicitation techniques (c) Feasibility study