(SEM IV) THEORY EXAMINATION 2017-18 SOFTWARE ENGINEERING

The B.Tech Software Engineering (RCS402) question paper from the 2017–18 VI Semester Theory Examination is a comprehensive 70-mark exam structured to test students on the principles, methodologies, models, and tools used in modern software development. The paper is divided into three well-balanced sections: foundational concepts, descriptive answers, and analytical problem-based questions. It covers requirements engineering, SDLC, software design principles, testing methodologies, risk management, software metrics, and quality assurance. 

SECTION A – Short Answer Questions (14 Marks)

This section contains 7 questions, each worth 2 marks, aimed at testing students’ basic theoretical understanding of software engineering fundamentals. Topics include:

Requirement elicitation methods (interviews, questionnaires, prototyping, observation, etc.)

Verification vs. Validation in software development

Software crisis and its causes

Comparison of ISO 9000 vs SEI-CMM (Capability Maturity Model)

Top-down vs Bottom-up approaches

Difference between Software Re-engineering and Reverse Engineering

Black-box testing definition and purpose

These are direct, concept-based questions to ensure clarity of basic SE terminology.

SECTION B – Descriptive Questions (Any 3 × 7 = 21 Marks)

Section B includes medium-length, explanatory questions that evaluate students’ understanding of core software engineering processes, methodologies, and design paradigms.

Key topics include:

1. Modularity in Software Design

Explaining cohesion, coupling, decomposition, modular design principles with examples.

2. SDLC (Software Development Life Cycle)

Discussing various phases such as:

Requirements analysis            Design

Coding                                    Testing

Deployment                            Maintenance

3. OOP Concepts (Object, Message, Polymorphism, Abstraction, Class)

Definitions and importance of object-oriented thinking.

4. Function-Oriented vs Object-Oriented Design

Architectural differences, design flow, advantages, constraints.

5. Short Notes on:

White Box Testing

COCOMO Cost Estimation Model

E-R Diagram

These questions require structured, example-backed answers.

SECTION C – Advanced Analysis & Design Questions (7 Marks Each)

Section C includes scenario-based and analytical questions that test higher-level understanding and application of software engineering principles.

Q3 – DFD or Software Metrics

Students choose one:

Level-1 DFD of a Library Management System (processes, data stores, flows, external entities)
OR

Halstead Software Metrics including token count, operators, operands, and difficulty metrics

Q4 – Testing, SQA & Risk

Option (a) asks for short notes on:

Software Testing

Software Quality Assurance (SQA)

Cyclomatic Complexity

Or (b) Risk Management, differences between project and technical risks.

Q5 – DFD Rules / Coupling & Cohesion

Explain DFD rules, good practices, balancing, naming conventions, with examples
OR

Discuss coupling & cohesion, their roles in software design, and describe the ideal/best types (e.g., functional cohesion, data coupling)

Q6 – Risk Reduction / Software Maintenance

Explain risk management strategies and criteria for selecting the best risk reduction technique
OR

Define Software Maintenance and explain the structure of CASE tools

Q7 – Functional Independence / Software Reviews

Students explain:

Functional independence, why it is essential for good software design
OR

Short notes on:

Walkthroughs

Inspection techniques in software reviews