BE Computer Engineering (Pokhara University) Software Engineering (PU, CMP 348) Question Paper 2079

Software process models prescribe how the activities of software development are organized.

(a) Explain the Waterfall model and the Incremental (iterative) model with neat diagrams. (8)

(b) A client requires a large, safety-critical air-traffic monitoring system whose requirements are unstable and where each phase carries significant technical risk. Which process model would you recommend and why? Justify your answer with reference to the Spiral model and its four quadrants. (7)

Consider the development of an online library management system for a university.

(a) Describe the requirement engineering process, clearly distinguishing between functional and non-functional requirements. List at least three of each for the given system. (7)

(b) Draw a use-case diagram for the system covering the actors Student, Librarian, and Administrator, and write a structured use-case description (including main and alternate flows) for the Issue Book use case. (8)

Software architecture defines the high-level structure of a system.

(a) Explain the layered (n-tier) architectural style and the client–server architectural style, stating the advantages and disadvantages of each. (8)

(b) For a web-based e-commerce application, propose a suitable architecture using a labelled block diagram, identify the major components, and explain how the Model-View-Controller (MVC) pattern improves maintainability. (7)

A software project is estimated to have 33.3 KLOC of delivered source code and is classified as an organic project.

(a) Using the Basic COCOMO model with coefficients for the organic mode (a = 2.4, b = 1.05, c = 2.5, d = 0.38), compute the effort (person-months), development time (months), and the average staffing required. Show all steps. (8)

(b) Explain the difference between size-oriented and function-oriented (Function Point) estimation, and discuss two limitations of the COCOMO model. (7)

(a) Differentiate between black-box testing and white-box testing. (4)

(b) For the code segment below, draw the control flow graph, compute the cyclomatic complexity, and list the independent paths.

if (a > b) {
    x = a - b;
} else {
    x = b - a;
}
while (x > 0) {
    x = x - 1;
}

(4)

(a) Define Software Configuration Management (SCM) and explain the term baseline. (3)

(b) Describe the change control process used to manage modifications to configuration items, mentioning the role of the Change Control Board (CCB). (4)

(a) Distinguish between software quality assurance (SQA) and software quality control (SQC). (3)

(b) Explain the five maturity levels of the Capability Maturity Model Integration (CMMI) with a one-line description of each. (4)

(a) What is meant by coupling and cohesion in software design? Why is low coupling and high cohesion desirable? (4)

(b) With an example, explain any two types of cohesion. (3)

(a) What is a Software Requirements Specification (SRS) document? List four characteristics of a good SRS. (4)

(b) Explain any three requirements elicitation techniques. (3)

(a) What is risk management in software projects? Explain the steps of the risk management process. (4)

(b) Differentiate between a Gantt chart and a PERT chart as project scheduling tools. (3)

Explain the different levels of testing — unit testing, integration testing, system testing, and acceptance testing — and state the purpose of each. Briefly describe the difference between top-down and bottom-up integration testing.

(a) State the four core values of the Agile Manifesto. (3)

(b) Explain the Scrum framework, describing the roles, artifacts, and the purpose of a sprint. (4)