SOFTWARE ENGINEERING – COMPLETE QUESTION BANK

UNIT 1 – SOFTWARE PROCESS & PROCESS MODELS

A. 2-MARK QUESTIONS (K1–K3)

1. Define Software Engineering. (K1)

2. List the characteristics of software. (K1)
3. Compare software with hardware. (K2)
4. Define Software Process. (K1)
5. What is Software Process Framework? (K1)
6. List the umbrella activities. (K1)
7. Define feasibility study and its types. (K2)
8. Write any two principles of Software Engineering. (K2)
9. What is a prescriptive process model? (K1)
10. Differentiate Waterfall and Spiral model. (K3)
11. What is a Unified Process? (K1)
12. Define Incremental Process Model. (K1)
13. What is an Evolutionary model? (K1)
14. Define Agile Process. (K1)
15. State the principles of Agile. (K2)
16. What is XP? (K1)
17. List any four agile models. (K1)
18. Define PSP and TSP. (K1)
19. What is the Make/Buy Decision? (K2)
20. What is the W5HH principle? (K2)
21. Define software scope. (K1)
22. List the activities in requirement engineering. (K2)
23. What is the risk in the software process? (K2)
24. Define spiral model risk analysis. (K3)
25. Define win-win negotiation in RE. (K2)
 B. 8-MARK QUESTIONS (K3–K5)

26. Explain the layered technology of software engineering with a neat diagram. (K3)
27. Explain prescriptive process models with suitable diagrams. (K4)
28. Compare the Waterfall, Incremental, and Evolutionary models. (K4)
29. Explain the Spiral model and its framework activities. (K4)
30. Describe Agile Manifesto and principles of Agile. (K4)
31. Explain Extreme Programming (XP) practices. (K4)
32. Compare Agile and Prescriptive models. (K4)
33. Explain Unified Process Model with phases. (K4)
34. Discuss the principles and objectives of Team Software Process (TSP). (K5)
35. Describe Personal Software Process (PSP) and its time management steps. (K5)
36. Explain feasibility analysis and types of feasibility. (K3)
37. Illustrate the Concept of Prototyping Model with an example. (K4)
38. Discuss Component-Based Development Model. (K4)
39. Explain the Make or Buy Decision Process in software engineering. (K5)
40. Explain the advantages and limitations of Evolutionary Process Models. (K4)
 C. 16-MARK QUESTIONS (K4–K6)

41. Explain in detail the Waterfall model with a neat diagram and discuss its advantages and
limitations. (K5)
42. With a neat sketch, explain the Spiral Model and discuss risk analysis phases. (K5)
43. Explain Unified Process Model in detail with all workflows. (K4)
44. Describe any two Prescriptive Process Models with diagrams and compare them. (K6)
45. Explain Agile Process model in detail and discuss XP, Scrum, Crystal, FDD. (K6)
46. Explain Evolutionary Model and compare Prototyping with Spiral model. (K5)
47. Explain in detail PSP and TSP with objectives, phases, and outcomes. (K6)
48. “Process models should be chosen based on project characteristics.” Justify with
examples. (K6)
49. Evaluate the suitability of Incremental Model and Spiral Model for developing a banking
application. (K6)
50. Develop a complete feasibility study report for an online shopping software (Technical,
Operational, Economic). (K6)
51. Create a comparative analysis of all SE process models focusing on adaptability, risk,
and customer involvement. (K6)
52. Explain the importance of Software Process Framework & umbrella activities with
examples. (K5)
53. Construct a detailed process table for developing a word processor using your chosen
model. (K6)
54. Analyze the suitability of Agile for real-time embedded systems—justify with reasons.
(K6)
55. Demonstrate the phases of Requirement Engineering + Process Framework in a full
case example (e.g., ATM). (K6)
56. Explain the challenges in selecting the correct process model. Provide a structured
selection approach. (K5)
57. Perform a complete W5HH analysis for an educational ERP project. (K6)
58. Compare in detail: Waterfall vs UP vs Agile vs Spiral (all dimensions). (K6)
59. Explain all 4 process framework activities of UP and develop a use-case driven workflow
diagram. (K6)
60. Explain the concept of software process maturity (CMMI levels) and relate it to PSP/TSP.
(K5)
 UNIT 2 — REQUIREMENTS ENGINEERING & ANALYSIS MODELING

A. 2-MARK QUESTIONS (40 Questions — K1–K3)

1. Define Requirements Engineering. (K1)

2. What is the need for Requirement Analysis? (K1)
3. List any four Requirement Engineering activities. (K1)
4. Define Functional Requirement with example. (K1)
5. Define Non-Functional Requirements. (K1)
6. List the components of a Software Requirements Specification. (K1)
7. What is a feasibility study? (K2)
8. Define the term “Software Scope”. (K1)
9. Mention any two requirement elicitation techniques. (K1)
10. What is win-win negotiation? (K2)
11. Define Use Case. (K1)
12. What is requirement validation? (K1)
13. What is requirement management? (K2)
14. Define product and process requirements. (K1)
15. What is SRS? (K1)
16. State the characteristics of a good SRS. (K2)
17. What is an analysis model? (K1)
18. Define DFD. (K1)
19. What is a context diagram? (K2)
20. Define activity diagram. (K1)
21. Define class-based modeling. (K1)
22. What is an entity in ER modeling? (K1)
23. List any two elements of UML diagrams used in analysis. (K1)
24. What is scenario-based modeling? (K1)
25. What is CRC modeling? (K1)
26. What is a data dictionary? (K2)
27. Define requirement inconsistency. (K1)
28. What is requirement ambiguity? (K2)
29. Define traceability. (K2)
30. What is prototyping in requirements? (K1)
31. Define stakeholder. (K1)
32. What is Risk in requirement engineering? (K2)
33. Define validation vs verification in RE perspective. (K2)
34. What is the interface requirement? (K1)
35. What is refinement? (K2)
36. Define use-case narrative. (K1)
37. Define system requirements. (K1)
38. What are user stories? (K2)
39. Define data model. (K1)
40. What is domain analysis? (K2)
 B. 8-MARK QUESTIONS (30 Questions — K3–K5)

41. Explain the Requirement Engineering Process with a neat diagram. (K3)
42. Describe in detail the activities in Requirements Elicitation. (K4)
43. Discuss the challenges in requirement elicitation and how to manage them. (K4)
44. Explain functional and non-functional requirements with examples. (K3)
45. Write short notes on:
a) Requirement validation
b) Requirement negotiation (K3)
46. Explain any four requirement elicitation techniques. (K4)
47. Write the characteristics of a good SRS and its components. (K3)
48. Explain the steps in writing an effective use case. (K4)
49. Explain use case diagram for an ATM Withdrawal System. (K4)
50. Explain activity diagram and sequence diagram with a simple example. (K4)
51. Illustrate Class-based modeling with suitable UML diagrams. (K4)
52. Explain scenario-based modeling in detail. (K4)
53. Discuss different types of analysis models. (K4)
54. Compare Context-level DFD and Level-1 DFD with examples. (K3)
55. Explain Requirement Management and change control process. (K4)
56. Explain domain analysis and its process. (K3)
57. Discuss feasibility study and its types. (K3)
58. Explain SRS template with examples. (K3)
59. Explain CRC modeling with an example case. (K4)
60. Elaborate data modeling and entity-relationship diagrams. (K4)
61. Explain the purpose of the prototype model in requirement analysis. (K4)
62. Describe the structure of the analysis model using UML diagrams. (K4)
63. Explain object-oriented analysis in detail. (K4)
64. Illustrate the types of UML diagrams used in requirements analysis. (K4)
65. Explain the steps for requirement validation and verification. (K4)
66. Describe elaboration in the Unified Process Model. (K4)
67. Explain interface and performance requirements with examples. (K3)
68. Describe user stories and story mapping in agile RE. (K4)
69. Explain traceability matrix with template and example. (K4)
70. Explain requirement prioritization methods like MoSCoW, Kano. (K5)
 C. 16-MARK QUESTIONS (30 Questions — K4–K6)

71. Describe in detail the Requirements Engineering Process Model with neat diagrams.
(K5)
72. “Requirement Elicitation is the most difficult task in SE.” Justify with challenges and
solutions. (K6)
73. Develop a complete SRS Document for an Online Railway Ticket Booking System. (K6)
74. Explain in detail the FIVE stages of Requirement Engineering with an end-to-end
example. (K5)
75. Construct use case, activity diagram, and sequence diagram for ATM Withdrawal
System. (K6)
76. Illustrate a detailed Class Model + CRC cards for a Library Management System. (K6)
77. Prepare Context DFD (Level-0) and Level-1 DFD for an Online Examination System.
(K6)
78. Develop a complete Requirement Specification for a Hospital Management System. (K6)
79. Explain all UML diagrams involved in Analysis Modeling with a mini project example.
(K6)
80. Analyze requirement ambiguity issues and propose solutions with case examples. (K6)
81. Explain requirement evolution, change control, and change management process. (K5)
82. Evaluate functional vs non-functional requirements using a full case study. (K6)
83. Explain Object-Oriented Analysis (OOA) in detail with diagrams. (K6)
84. For a Safe Home Security System:Use case diagram ,Activity Diagram,Class
Diagram,Sequence Diagram (K6)
85. Explain Scenario-based, Class-based, and Behavioral models with a multi-view example.
(K6)
86. Construct a requirement specification and DFD for Online Food Ordering System. (K6)
87. Explain the need for SRS, its components, and prepare a sample SRS for a Banking
App. (K5)
88. Analyze and redesign poor requirements from a sample project (you can request for a
sample). (K6)
89. Prepare a detailed traceability matrix for an Airline Reservation System. (K6)
90. Develop a detailed requirement model for E-Learning Management System. (K6)
91. “Good requirements lead to successful software.” Analyze and justify with examples.(K6)
92. Compare structured analysis and object-oriented analysis with diagrams. (K5)
93. Construct all analysis diagrams (use case, DFD, class, sequence) for an Inventory
System. (K6)
94. Evaluate the role of negotiation and validation in RE with real-world examples. (K5)
95. Create a full-case domain model for an Online Banking System. (K6)
96. Explain the UP (Unified Process) Analysis workflow for a real-time system. (K5)
97. Create a complete RE + Analysis package for Bus Ticket Booking System. (K6)
98. Describe the impact of poor requirements on project failure with case studies. (K6)
99. Explain requirement prioritization strategies and apply them for a social media
application. (K6)
100. Develop a detailed conceptual model for a Real-time Ticketing System with UML. (K6)
 UNIT 3 – DESIGN ENGINEERING & ARCHITECTURAL DESIGN

A. 2-MARK QUESTIONS (K1–K3)

(40 Questions)

1. What is Software Design? (K1)

2. Define architectural design. (K1)
3. What is data design? (K1)
4. Define interface design. (K1)
5. List the elements of the design model. (K1)
6. What is modularity? (K1)
7. Define abstraction. (K2)
8. Define cohesion. (K1)
9. Define coupling. (K1)
10. List the types of cohesion. (K1)
11. List the types of coupling. (K1)
12. What is component-level design? (K2)
13. Define architecture pattern. (K1)
14. What is layered architecture? (K2)
15. What is data-centered architecture? (K2)
16. What is pipe-and-filter architecture? (K1)
17. Define the term "Design Class". (K1)
18. What are quality attributes of design? (K2)
19. List any two architectural styles. (K1)
20. What is transform mapping? (K1)
21. What is transaction mapping? (K2)
22. Define interface specification. (K1)
23. What is a component diagram? (K1)
24. What is a deployment diagram? (K1)
25. Define design constraints. (K2)
26. What is refactoring? (K2)
27. What is the role of design concepts? (K2)
28. Define the term “architecture view”. (K1)
29. What is functional independence? (K2)
30. What is the difference between class and object? (K2)
31. What is user interface design? (K1)
32. What is information hiding? (K2)
33. Define Template class. (K1)
34. What is inheritance? (K1)
35. Define polymorphism. (K1)
36. What is a sequence diagram? (K1)
37. What is a collaboration diagram? (K1)
38. What is architectural mapping? (K2)
39. Define design heuristics. (K2)
40. What is software architecture? (K1)
 B. 8-MARK QUESTIONS (K3–K5)

(30 Questions)

41. Explain the elements of the design model in detail. (K4)

42. Discuss the major design concepts—abstraction, refinement, modularity. (K4)
43. Explain cohesion and coupling with examples. (K4)
44. Explain data design and its components. (K3)
45. Illustrate interface design principles with examples. (K4)
46. Explain component-level design and its tasks. (K4)
47. Explain different architectural styles with examples. (K4)
48. Explain data-centered and layered architecture with neat diagrams. (K4)
49. Write short notes on:
a) Client-server architecture
b) Object-oriented architecture (K3)
50. Explain the steps involved in transform mapping with examples. (K4)
51. Explain the steps involved in transaction mapping. (K4)
52. Describe the importance of design quality guidelines. (K3)
53. Explain interface specification with examples. (K3)
54. Illustrate with examples:
a) Sequence diagram
b) Activity diagram (K4)
55. Discuss the principles suggested by Davis for good software design. (K4)
56. Explain component diagram and deployment diagram with examples. (K4)
57. Discuss software architecture vs software design differences. (K4)
58. Describe object-oriented design concepts with examples. (K4)
59. Write about design class characteristics and responsibilities. (K4)
60. Explain system design vs detailed design. (K3)
61. Describe architectural mapping using data flow diagrams. (K4)
62. Explain the importance of modularity and information hiding. (K4)
63. Explain the art of debugging in design & coding. (K4)
64. Explain user interface design principles. (K4)
65. Discuss cohesion–coupling-based modular system design. (K5)
66. Explain the role of patterns in software architectures. (K4)
67. Compare the types of architectural styles. (K4)
68. Explain the concept of functional independence in software design. (K5)
69. Explain the system structure, data structure, and control structure choices. (K4)
70. Describe the mapping of design models to code-level structures. (K4)
 C. 16-MARK QUESTIONS (K4–K6)
71. Explain in detail ALL the elements of the Software Design Model with diagrams. (K6)
72. Elaborate on Abstraction, Modularity, Encapsulation, and Information Hiding with case
study. (K6)
73. Prepare a full architectural design for a Library Management System using layered,
data-centered, and OO architecture. (K6)
74. Illustrate in detail various architectural styles with neat sketches and examples. (K6)
75. Explain transform mapping in detail with a complete example and diagram. (K6)
76. Prepare a detailed architectural mapping for "Online Food Ordering System" using DFD
+ mapping rules. (K6)
77. Compare all architectural patterns: Layered, Client-server,Data-centered,Pipe-filter,OO
architecture With examples. (K6)
78. Explain and illustrate component-level design steps for an ATM or Banking System. (K5)
79. Draw and explain: Class Diagram, Sequence Diagram,Activity Diagram, Component
Diagram For a “Safe Home Security System”. (K6)
80. Explain in detail design principles recommended by Davis and Grady. (K5)
81. Prepare the object-oriented design (OOD) for an e-commerce application. (K6)
82. Develop a complete design (data + architecture + interface + component) for an Online
Examination System. (K6)
83. Explain in detail user interface design principles and develop UI mockups for an ATM.
(K6)
84. “Design quality is measured through design metrics.” Evaluate design metrics with case
analysis. (K6)
85. Explain the difference between architectural design & detailed design with an industrial
example. (K5)
86. Build a detailed design class model using CRC cards for an Inventory System. (K6)
87. Explain object-oriented architectural design in detail with UML diagrams. (K6)
88. Discuss design problems that arise in large-scale software projects and propose
solutions. (K6)
89. Explain and analyze the importance of functional independence and refactoring. (K6)
90. Develop an end-to-end system architecture for an online flight reservation system. (K6)
91. Prepare component + deployment diagrams for a Hospital Management System. (K6)
92. Write a detailed design specification for a Banking Management System. (K6)
93. Explain how architectural decisions affect software performance, security, and
maintainability. (K6)
94. Analyze poor design practices in software engineering and propose improvements. (K5)
95. Explain the taxonomy of architectural styles with neat sketches. (K6)
96. Demonstrate the importance of modularity through a complete module decomposition
example. (K6)
97. Develop UI, architecture, and component design for a social media application. (K6)
98. Demonstrate the mapping from analysis model → design model → architecture →
components using a real case. (K6)
99. “Architectural design is the blueprint of the software.” Analyze the statement with
examples. (K6)
100. Create a complete object-oriented design solution (all UML diagrams) for “Online Movie
Ticket Booking System.” (K6)
 UNIT 4 – TESTING & QUALITY ASSURANCE

A. 2-MARK QUESTIONS (40 Questions – K1 to K3)

1. Define Software Testing. (K1)

2. What is verification? (K1)
3. What is validation? (K1)
4. Differentiate verification and validation. (K2)
5. Define unit testing. (K1)
6. Define integration testing. (K1)
7. What is system testing? (K1)
8. What is acceptance testing? (K1)
9. Define black-box testing. (K1)
10. Define white-box testing. (K1)
11. What is boundary value analysis? (K2)
12. What is equivalence partitioning? (K2)
13. Define cyclomatic complexity. (K1)
14. What are stubs in testing? (K2)
15. What are drivers in testing? (K2)
16. Define regression testing. (K1)
17. What is alpha testing? (K1)
18. What is beta testing? (K1)
19. Define defects. (K1)
20. What is debugging? (K2)
21. What is a test case? (K1)
22. Define test scenario. (K2)
23. Define load testing. (K1)
24. Define stress testing. (K1)
25. What is usability testing? (K2)
26. What is OO testing? (K1)
27. What is mutation testing? (K1)
28. List any two web testing methods. (K1)
29. Define code coverage. (K2)
30. List the components of the test plan. (K1)
31. Define test metrics. (K2)
32. What is quality assurance (QA)? (K2)
33. Define software quality. (K1)
34. What are software quality attributes? (K1)
35. Define static testing. (K1)
36. Define dynamic testing. (K1)
37. What is the test strategy? (K2)
38. What is path testing? (K2)
39. What is clean-room software engineering? (K3)
40. Define the test environment. (K2)
 B. 8-MARK QUESTIONS (30 Questions – K3 to K5)

41. Explain Verification vs Validation with examples. (K4)

42. Explain unit testing and integration testing. (K3)
43. Explain the system testing and acceptance testing process. (K4)
44. Compare black-box and white-box testing with examples. (K4)
45. Explain equivalence partitioning and boundary value analysis with examples. (K3)
46. Explain cyclomatic complexity and derive its formula. (K4)
47. Explain basis path testing with neat flow graph examples. (K4)
48. Discuss stub and driver usage in testing. (K3)
49. Explain regression testing process and when it is applied. (K4)
50. Explain alpha and beta testing. (K3)
51. Discuss different types of System Testing. (K4)
52. Explain different debugging strategies. (K4)
53. Explain testing strategies for Object-Oriented Systems. (K4)
54. Explain the steps involved in web application testing. (K3)
55. Discuss load testing, stress testing, and performance testing. (K4)
56. Explain types of software quality attributes. (K4)
57. Explain the components of a test plan with examples. (K4)
58. Explain the activities of validation testing. (K4)
59. Explain integration testing strategies (Top-down, Bottom-up). (K4)
60. Discuss different types of acceptance testing with examples. (K4)
61. Explain the importance of user interface testing. (K4)
62. Explain clean-room software engineering. (K4)
63. Explain various testing strategies used in real-time systems. (K5)
64. Describe the metrics used in testing and quality assurance. (K4)
65. Explain the role of testing in software quality assurance. (K4)
66. Discuss the importance of test case documentation. (K4)
67. Explain validation testing and highlight its difficulties. (K4)
68. Explain mutation testing. (K4)
69. Explain driver–stub-based incremental testing. (K4)
70. Explain security testing for web applications. (K5)
 C. 16-MARK QUESTIONS (30 Questions – K4 to K6)
71. Explain in detail the various software testing strategies with neat diagrams. (K6)
72. Explain the unit testing → integration testing → system testing → acceptance testing
phases of the testing pyramid. (K6)
73. Compare black-box testing and white-box testing with detailed examples and diagrams.
(K6)
74. Explain in detail the process of path testing and derive cyclomatic complexity for a given
flow graph. (K5)
75. Develop complete test cases, test data, and expected outputs for an ATM Withdrawal
System. (K6)
76. Discuss in detail boundary value analysis and equivalence partitioning with 4 real-time
examples. (K5)
77. Design a complete testing strategy for a web-based e-commerce application. (K6)
78. Explain regression testing, re-testing, and continuous testing in DevOps environments.
(K6)
79. Evaluate the importance of debugging and explain its process with types of debugging
strategies. (K6)
80. Explain object-oriented testing strategies using class testing, integration testing, and
scenario-based testing. (K5)
81. “Validation Testing ensures complete correctness.” Justify with real-world difficulties and
examples. (K6)
82. Explain white-box testing methods with detailed examples :Statement Coverage, Branch
Coverage, Condition Coverage (K6)
83. Develop a complete system-level test plan for an Online Examination System. (K6)
84. Create 10 test cases for the login module and validate equivalence classes. (K5)
85. Discuss the testing concepts for WebApps with architecture-based testing. (K6)
86. Explain the differences and relationship between software Quality Assurance & Testing.
(K6)
87. Explain the ISO 9126/25010 quality model in detail with examples. (K5)
88. Develop a stress + performance + load testing model for a mobile app. (K6)
89. Describe with diagrams the Top-down and Bottom-up integration testing strategies. (K6)
90. Explain Acceptance Testing (Alpha / Beta / User Acceptance) in detail with examples.
(K6)
91. Analyze challenges in testing large software systems and propose solutions. (K6)
92. Develop OO testing strategy for a Library Management System. (K6)
93. Explain security testing in detail—XSS, SQLi, session hijacking, CSRF attacks. (K6)
94. Discuss the role of Quality Assurance in the Software Project Management life cycle.
(K6)
95. Prepare a complete testing document (plan + scenarios + cases + expected results) for
an Airline Booking System. (K6)
96. Conduct a complete V-Model explanation linking testing levels to SDLC stages. (K5)
97. “Test automation improves test effectiveness.” Evaluate using Selenium/JMeter
examples. (K6)
98. Prepare full design of test cases for an Online Shopping Cart System. (K6)
99. Compare all black-box testing techniques with full examples for each. (K5)
100. Create a full white-box testing design for a given pseudocode with flow graph, paths,
and test data. (K6)
 UNIT 5 – SOFTWARE PROJECT MANAGEMENT, METRICS & ESTIMATION
A. 2-MARK QUESTIONS (40 Questions – K1 to K3)

1. Define Software Project Management. (K1)

2. What is a software metric? (K1)
3. Define process metric. (K1)
4. Define product metric. (K1)
5. What is the project metric? (K1)
6. List any two software estimation techniques. (K1)
7. What is the size measure? (K1)
8. What is COCOMO? (K1)
9. Define function point. (K1)
10. What is empirical estimation? (K1)
11. What is earned value analysis (EVA)? (K2)
12. Define project scheduling. (K1)
13. What is the risk? (K1)
14. Define risk management. (K1)
15. What is project planning? (K1)
16. List the decomposition techniques. (K1)
17. What is the work breakdown structure (WBS)? (K2)
18. Define task network. (K1)
19. What is the critical path? (K2)
20. What is resource allocation? (K2)
21. List the project scheduling principles. (K1)
22. Define software quality. (K1)
23. What is cost estimation? (K1)
24. What is project effort? (K1)
25. Define productivity. (K2)
26. What is staffing level? (K2)
27. Define Putnam’s software equation. (K2)
28. What is LOC? (K1)
29. What is FP analysis? (K2)
30. Define risk exposure. (K2)
31. Define schedule variance (SV). (K1)
32. Define cost variance (CV). (K2)
33. Define milestones. (K1)
34. What is the task set? (K1)
35. List the types of risks. (K2)
36. Define estimation by analogy. (K2)
37. What is a project plan? (K1)
38. What are people–product–process triangles? (K2)
39. What is Earned Value (EV)? (K2)
40. What is re-estimation? (K2)
 B. 8-MARK QUESTIONS (30 Questions – K3 to K5)

41. Explain process metrics and product metrics with examples. (K4)
42. Explain project metrics and why they are required. (K4)
43. Discuss empirical estimation models. (K3)
44. Explain decomposition techniques in estimation. (K3)
45. Explain function point analysis with an example. (K4)
46. Compare LOC and FP-based estimation. (K4)
47. Explain the COCOMO basic model. (K4)
48. Explain the detailed COCOMO model and its components. (K4)
49. Explain Putnam’s Software Equation with an example. (K4)
50. Explain project scheduling principles. (K4)
51. Explain risk management activities. (K4)
52. Discuss the types of risks and risk mitigation strategies. (K5)
53. Explain earned value analysis (EVA) with examples. (K4)
54. Explain software quality and quality metrics. (K4)
55. Describe project planning activities. (K3)
56. Explain task network and scheduling process. (K4)
57. Discuss people-product-process model in project management. (K4)
58. Explain estimation by decomposition with example. (K4)
59. Explain cost and effort estimation in software project management. (K4)
60. Explain staffing level estimation using Rayleigh curve. (K4)
61. Discuss specialized estimation techniques. (K4)
62. Explain make/buy decision-making with examples. (K4)
63. Explain the steps for establishing a goal-driven metrics program. (K4)
64. Explain the process and project domain metrics. (K4)
65. Explain risk exposure and methods to compute it. (K5)
66. Discuss error tracking and defect removal metrics. (K4)
67. Explain the types of project schedules and their significance. (K4)
68. Explain earned value parameters: EV, PV, AC, SV, CV. (K4)
69. Discuss software project tracking methods. (K4)
70. Explain the importance of reviews and audits in quality assurance. (K4)
 C. 16-MARK QUESTIONS (30 Questions – K4 to K6)

71. Explain process, product, and project metrics with proper case study examples. (K6)
72. Develop a complete software estimation using function point analysis for a Library
Management System. (K6)
73. Explain in detail all COCOMO models—Basic, Intermediate, Detailed—with example
calculations. (K6)
74. Prepare full cost and effort estimation for an ATM application using COCOMO II. (K6)
75. Explain project planning activities with detailed WBS creation for a real-time system. (K6)
76. Explain risk identification, risk projection, risk mitigation, and monitoring in detail. (K6)
77. Evaluate different estimation techniques: Empirical, Heuristic, Decomposition, and
Specialized techniques. (K6)
78. Prepare a Rayleigh curve staffing profile for a large-scale project and interpret it. (K5)
79. Develop a full Earned Value Analysis table for a 12-week software project and interpret
SV, CV, CPI, SPI. (K6)
80. Explain the challenges in project scheduling and propose solutions using critical-path
analysis. (K6)
81. Develop effort estimation using decomposition approach for an Online Shopping System.
(K6)
82. “Metrics improve software quality and productivity.” Justify with examples and data. (K6)
83. Evaluate people – product – process – project issues in SPM with real examples. (K6)
84. Compare problem-based estimation and process-based estimation with full examples.
(K6)
85. Prepare a detailed project plan for an E-Learning Management System. (K6)
86. Explain quality models (McCall, Boehm, ISO 25010) and compare them in detail. (K6)
87. Analyse project risk categories and propose mitigation plans for each. (K6)
88. Construct a detailed project estimation report (cost + schedule + risk + quality metrics)
for a Banking System. (K6)
89. Explain Earned Value Analysis and illustrate with three real-life project scenarios. (K6)
90. Develop an estimation using Use Case Points (UCP) for a web application. (K6)
91. Explain staffing and team structure models (Hierarchical, Democratic, Chief
Programmer). (K5)
92. Create a complete scheduling plan using task network + Gantt chart explanation. (K6)
93. Evaluate the role of metrics in project and process improvement. (K6)
94. Discuss estimation issues and challenges in large-scale software projects. (K6)
95. Prepare a detailed make/buy decision report for an ERP system in a company. (K6)
96. Create a complete risk management plan for Online Railway Ticket Booking System.
(K6)
97. Explain Putnam’s SLIM model fully with step-by-step mathematical explanation. (K6)
98. Compare all estimation techniques (COCOMO, FP, LOC, UCP, SLIM). (K6)
99. Prepare a full-scale effort and cost estimation model for a social media application. (K6)
100. Create a comprehensive SPM document containing estimation, metrics, EVA, risk plan,
and scheduling. (K6)