(SEM VI) THEORY EXAMINATION 2022-23 SOFTWARE ENGINEERING

SOFTWARE ENGINEERING (KCS-601)

B.Tech Semester VI – Theory Examination (2022–23) 

SOFTWARE-ENGINEERING-KCS-601

Software Engineering is a systematic and disciplined approach to the development, operation, maintenance, and evolution of software systems. As software has become an integral part of almost every domain such as banking, healthcare, education, defense, and communication, the need for reliable, maintainable, and cost-effective software has increased significantly. This subject focuses on understanding software processes, models, design principles, testing strategies, quality assurance, project management, and maintenance techniques. The given question paper is designed to test both conceptual clarity and analytical understanding of software development practices. To score well, answers must be written in clear, descriptive, and logically connected paragraphs, using correct software engineering terminology.

SECTION A – BASIC SOFTWARE ENGINEERING CONCEPTS

Section A evaluates the student’s understanding of fundamental definitions and distinctions that form the foundation of software engineering.

When defining generic software, students should explain that it refers to software products developed for a broad market and not for a single customer, such as word processors or operating systems. This must be contrasted implicitly with customized software.

The concept of software components should be explained as reusable, independent units of software that perform specific functions and can be assembled into larger systems, emphasizing modularity and reuse.

Questions related to non-functional requirements must explain how such requirements define system quality attributes like performance, reliability, security, and usability rather than system functionality.

Software prototyping should be explained as a technique used to build an early version of the system to understand requirements better and reduce ambiguity between developers and users.

Horizontal and vertical partitioning should be explained in the context of system decomposition and modular design, focusing on separation of concerns and layered architecture.

The definition of software architecture must explain it as the high-level structure of a system that defines components, their relationships, and interaction patterns.

Differences between verification and validation, alpha and beta testing, and explanation of CASE tools must focus on purpose, stage of use, and benefits in software development.

Finally, adaptive maintenance should be explained as a type of maintenance carried out to adapt software to changes in environment such as operating system upgrades or hardware changes.

SECTION B – SOFTWARE PROCESS MODELS, DESIGN & TESTING

Section B focuses on process understanding, problem analysis, design representation, testing techniques, and configuration management. Answers here should be written with clarity and proper flow.

The explanation of iterative waterfall and spiral models must describe how software development progresses through phases such as requirement analysis, design, implementation, testing, and maintenance. The spiral model must be explained as a risk-driven model that combines iterative development with systematic risk analysis.

Problems faced in software engineering should be explained by discussing issues like changing requirements, cost overruns, poor quality, schedule delays, and lack of user involvement, highlighting why software projects often fail.

The structure chart must be explained as a design tool that represents system modules and their hierarchical relationships. Its types should be explained by focusing on data flow and control flow between modules.

Boundary value analysis should be explained as a black-box testing technique that focuses on testing values at the boundaries of input domains, emphasizing its effectiveness in detecting errors.

Software Configuration Management (SCM) should be explained as a discipline that controls and manages changes in software artifacts throughout the software lifecycle. Version control and project risks should be discussed to show how SCM helps in managing complexity and ensuring consistency.

SECTION C – SOFTWARE QUALITY, DESIGN & PROCESS IMPROVEMENT

Section C evaluates deep conceptual understanding, quality management, and advanced software engineering practices. Answers must be written in a detailed, exam-ready manner.

Software characteristics must be explained by highlighting that software is intangible, does not wear out, and is developed rather than manufactured. The software crisis should be explained as the result of increasing software complexity, poor project management, and lack of disciplined processes.

McCall’s quality factors must be explained in relation to software quality attributes such as correctness, reliability, efficiency, maintainability, and portability, along with the quality triangle concept.

The SEI-CMM model should be explained as a framework for process improvement that defines maturity levels of software organizations. The phrase state of fire-fighting must be explained as a chaotic development environment where problems are handled reactively rather than proactively.

The requirement engineering process must be explained by describing stages such as feasibility study, requirement elicitation, analysis, specification, validation, and management, along with their interrelationship.

The software design framework and design principles should be explained with emphasis on abstraction, modularity, information hiding, and functional independence.

SOFTWARE TESTING, METRICS & RE-ENGINEERING

Questions on control flow graphs and cyclomatic complexity require explanation of how program logic is represented and how complexity is calculated using different methods to determine the number of independent paths.

Structural testing techniques should be explained by discussing statement coverage, branch coverage, and path coverage with suitable examples.

The software re-engineering model must be explained as a process of analyzing and transforming legacy systems to improve maintainability and performance.

Finally, Function Point, COCOMO, and the distinction between defect, fault, and failure must be explained clearly, as these are core topics related to software estimation and quality assurance.

HOW TO WRITE SOFTWARE ENGINEERING ANSWERS IN THE EXAM

In Software Engineering, never write answers in short bullet points. Always begin with a clear definition, then explain the concept in depth with purpose, process, and significance. Use standard terminology such as lifecycle models, quality factors, configuration management, testing strategies, and process maturity. Diagrams, when mentioned, must be supported with descriptive explanation. Examiners focus on clarity of thought, conceptual understanding, and logical presentation.