Study Glance
📊
B.Tech CSE SE (Bloom's Taxonomy Aligned)

Software Engineering Important Questions

Unit-wise important 2-mark, 5-mark and 10-mark questions structured across all levels of Bloom's Taxonomy for semester examination preparation.

No questions found Try searching for another topic, unit or question.
Unit I

Introduction to Software Engineering & Process Models

Evolving Role, Software Myths, Process Framework, CMMI & SDLC Process Models

2-Mark Questions

10
  1. Define software engineering.
  2. State the evolving role of software in modern computing.
  3. List common software myths and misconceptions.
  4. Identify the core elements of a generic process framework.
  5. Explain software engineering as a layered technology.
  6. Summarize the primary objectives of CMMI.
  7. Describe the sequential phases of the Waterfall model.
  8. Distinguish between prescriptive process models and agile process models.
  9. Illustrate the iterative nature of the Spiral model.
  10. Demonstrate how incremental process models deliver functional subsets.

5-Mark Questions

8
  1. Explain the changing nature of software and its impact on modern engineering practices.
  2. Examine common software myths and contrast them with realistic industrial truths.
  3. Explain the Capability Maturity Model Integration (CMMI) levels and process maturity.
  4. Compare the Waterfall model with the Spiral model in terms of risk handling.
  5. Analyze the operational workflow of concurrent process models.
  6. Demonstrate how component-based development promotes software reusability.
  7. Explain the core principles and Manifesto of Agile development.
  8. Illustrate how prototyping models assist in ambiguous requirements gathering.

10-Mark Questions

3
  1. Evaluate the suitability of various software process models (Waterfall, Spiral, Agile, and Incremental) for different project domains.
  2. Formulate a comprehensive process improvement strategy for an IT organization using CMMI maturity frameworks.
  3. Design an end-to-end software development life cycle (SDLC) plan combining agile practices with rigorous engineering documentation.
Unit II

Software Requirements & Requirements Engineering

Functional & Non-Functional Requirements, SRS Document & Requirements Process

2-Mark Questions

10
  1. Define functional requirements.
  2. State non-functional requirements with examples.
  3. List user requirements versus system requirements.
  4. Identify the primary purpose of an interface specification.
  5. Explain the role of stakeholders in requirements elicitation.
  6. Summarize the contents of a Software Requirements Specification (SRS) document.
  7. Distinguish between verification and validation in requirements engineering.
  8. Describe the main objective of a feasibility study.
  9. Demonstrate requirement traceability using a simple matrix.
  10. Apply elicitation techniques to uncover hidden customer needs.

5-Mark Questions

8
  1. Explain the key differences between functional and non-functional requirements in real-time systems.
  2. Analyze the challenges encountered during requirements elicitation and negotiation.
  3. Examine the structure and IEEE standards for drafting an SRS document.
  4. Explain the role of feasibility studies (technical, economic, operational) in project initiation.
  5. Demonstrate how requirements validation techniques detect ambiguities and omissions.
  6. Analyze the requirements management and change control process in software projects.
  7. Explain domain requirements and evaluate their influence on system architecture.
  8. Illustrate how use cases help bridge user requirements and system behavior.

10-Mark Questions

3
  1. Evaluate the impact of poorly engineered requirements on project failure and budget overruns.
  2. Design a complete and IEEE-compliant Software Requirements Specification (SRS) document for a complex software application.
  3. Formulate a rigorous requirements traceability and change management framework for a large-scale enterprise system.
Unit III

Design Engineering & UML Modeling

Design Concepts, Architecture, Flowcharts vs UML & UML Structural/Behavioral Diagrams

2-Mark Questions

10
  1. Define software design engineering.
  2. State the key attributes of high design quality.
  3. List core design concepts such as abstraction and modularity.
  4. Identify the elements of the software design model.
  5. Explain information hiding in modular programming.
  6. Summarize the concept of software architecture.
  7. Distinguish between flowcharts and UML diagrams.
  8. Describe the purpose of a use case diagram.
  9. Demonstrate class relationships (association vs aggregation).
  10. Apply sequence diagrams to illustrate object interactions.

5-Mark Questions

8
  1. Explain fundamental design concepts including coupling, cohesion, and modularity.
  2. Analyze common architectural styles and patterns (e.g., client-server, layered architecture).
  3. Compare flowcharts with UML diagrams in representing system logic and workflows.
  4. Explain the conceptual model of UML (things, relationships, and diagrams).
  5. Demonstrate how to construct a robust class diagram with attributes, operations, and multiplicities.
  6. Examine the behavioral modeling aspects using activity diagrams and state machine diagrams.
  7. Explain data design principles at the architectural level.
  8. Illustrate component and deployment diagrams for distributed applications.

10-Mark Questions

3
  1. Evaluate different architectural styles for a high-concurrency cloud-based distributed system, justifying your choice.
  2. Design a comprehensive UML modeling suite (use case, class, sequence, and activity diagrams) for a real-world enterprise system.
  3. Formulate an architectural refactoring plan to improve system maintainability, reducing coupling and maximizing cohesion.
Unit IV

Testing Strategies & Process/Product Metrics

Strategic Testing, Black-Box/White-Box Testing, Validation/System Testing, Debugging & Metrics

2-Mark Questions

10
  1. Define software testing.
  2. State the strategic approach to software testing (V-Model).
  3. List testing levels for conventional software.
  4. Identify black-box testing versus white-box testing.
  5. Explain the primary objective of debugging.
  6. Summarize software measurement and metric classification.
  7. Distinguish between validation testing and acceptance testing.
  8. Describe cyclomatic complexity.
  9. Demonstrate boundary value analysis with an example.
  10. Apply basis path testing principles to compute independent paths.

5-Mark Questions

8
  1. Explain test strategies for conventional software, covering unit and integration testing.
  2. Analyze black-box testing techniques such as equivalence partitioning and boundary value analysis.
  3. Examine white-box testing methods, logic coverage, and path testing.
  4. Explain system testing categories including recovery, security, stress, and performance testing.
  5. Demonstrate how cyclomatic complexity is calculated and used in code quality evaluation.
  6. Analyze the art of debugging, debugging tactics, and fault isolation techniques.
  7. Explain product metrics and quality metrics in software engineering.
  8. Compare top-down integration testing with bottom-up integration testing approaches.

10-Mark Questions

3
  1. Evaluate the effectiveness of black-box versus white-box testing methodologies in uncovering critical software defects.
  2. Design a comprehensive software testing and verification plan for a mission-critical financial transaction system.
  3. Formulate a quality metrics framework to measure, track, and improve code maintainability and test coverage across development teams.
Unit V

Risk Management & Quality Management

Reactive vs Proactive Risks, RMMM, SQA, Formal Reviews, Reliability & ISO 9000

2-Mark Questions

10
  1. Define software risk management.
  2. State the difference between reactive and proactive risk strategies.
  3. List categories of software risks (project, technical, business).
  4. Identify the purpose of risk projection.
  5. Explain software quality assurance (SQA).
  6. Summarize the objectives of Formal Technical Reviews (FTR).
  7. Distinguish between software reliability and software availability.
  8. Describe ISO 9000 quality standards.
  9. Demonstrate risk mitigation using an RMMM plan.
  10. Apply statistical SQA principles to track defect rates.

5-Mark Questions

8
  1. Explain proactive risk management strategies and risk identification techniques.
  2. Analyze risk projection by estimating risk probability and potential impact.
  3. Examine the components of an RMMM (Risk Mitigation, Monitoring, and Management) plan.
  4. Explain Software Quality Assurance (SQA) activities, goals, and framework.
  5. Demonstrate how Formal Technical Reviews (FTR) improve software quality before testing.
  6. Analyze statistical software quality assurance and error tracking methodologies.
  7. Explain the cost of quality (prevention, appraisal, and failure costs).
  8. Compare ISO 9000 quality standards with CMMI process frameworks.

10-Mark Questions

3
  1. Evaluate the long-term return on investment (ROI) of implementing proactive risk management and SQA programs.
  2. Design an end-to-end risk management and quality assurance framework for a high-risk aerospace or medical software project.
  3. Formulate a complete quality management plan incorporating ISO 9000 standards, formal reviews, and reliability models.
💡

Exam Preparation Tip

These questions are designed across all levels of Bloom's Taxonomy (Remember, Understand, Apply, Analyze, Evaluate, Create). Begin with 2-mark foundational definitions, move to 5-mark conceptual analysis and application, and master 10-mark evaluation and design problems.