(An Autonomous Institution, Affiliated to Anna University, Chennai)

QUESTION BANK FORMAT

(Questions Should Not Repeat)

NAME OF THE DEPARTMENT COMPUTER SCIENCE AND ENGINEERING

YEAR / SEMESTER II/IV

REGULATION R2022(Rev)
SUBJECT CODE CS3405
SUBJECT NAME SOFTWARE ENGINEERING
FACULTY NAME DR.G.SENTHIL KUMAR Contact 89396 18019
MRS.GOMATHI
Number
94425 51195
MRS.R.POORNIMA LAKSHMI 88709 64537
MRS.S.SHOPIKA 9487150398
MRS.J.SINDHUJA
95006 85394

UNIT-I: SOFTWARE PROCESS

Introduction to Software Engineering - Software Process - Perspective Models: Waterfall, Iterative &
Incremental, V- and Spiral models - Specialized Process Models: Agile models, Component-Based
Development (CBD), Rapid Application Development (RAD), and Formal Methods.
PART-A (2-Marks)

S.NO QUESTIONS CO RBT LEVEL

1 Define Software Engineering. 1 K1

2 What is a software process? 1 K1

3 List the characteristics of a good software process. 1 K2

4 Differentiate between software and a program. 1 K2

5 State the main goal of the Waterfall model. 1 K1

6 Mention any two advantages of the Iterative model. 1 K2

7 What is the role of risk management in the Spiral model? 1 K2

8 Define Rapid Application Development (RAD). 1 K1

9 List any two features of Agile models. 1 K2

10 Differentiate between Agile and Waterfall models. 1 K2

11 What is Component-Based Development (CBD)? 1 K1

12 Explain the term "formal methods" in software engineering. 1 K2

13 Identify the phases of the V-model. 1 K2

14 List the major phases of the software lifecycle. 1 K2

15 State the purpose of requirement analysis. 1 K1

16 What is the significance of user involvement in Agile models? 1 K2

17 Define "incremental development" in the context of software processes. 1 K1

18 Name two software development methodologies classified as specialized

1 K2
models.
19 State any two limitations of the Waterfall model. 1 K1

20 Mention one use case for the Spiral model. 1 K1

RBT
PART-B (13- Marks Or 16-Marks or 8-Marks) CO Marks
Level
1 Apply the Waterfall model to develop a library management system. 1 K3 13

2 Explain the Iterative and Incremental model with an example. 1 K3 13

3 Compare the V-model and Spiral model with their respective use cases. 1 K4 13

4 Analyze the effectiveness of Agile methodologies in modern software 1 13

K4
development.
5 Differentiate between RAD and Component-Based Development. 1 K4 13

6 Discuss the challenges faced in implementing the Spiral model in large 1 13

K4
projects.
7 Illustrate the phases of the V-model using a real-world application 1 13
K3
scenario.
8 Describe the principles of Agile development and how they impact 1 13
K3
project outcomes.
9 Apply the RAD model to design a small e-commerce website. 1 K3 13

10 Analyze the risk-driven approach in the Spiral model. 1 K4 13

11 Explain the role of formal methods in safety-critical software systems. 1 K3 13

12 Compare incremental and iterative development approaches. 1 K4 13

13 Discuss how Component-Based Development improves software 1 13

K4
reusability.
14 Analyze the impact of user feedback in Agile software development. 1 K4 13

15 Apply the V-model to validate and verify a banking application. 1 K3 13

16 Illustrate how the Spiral model integrates risk analysis into the software 1 13
K3
process.
17 Evaluate the advantages and disadvantages of RAD for large-scale 1 13
K4
software projects.
18 Describe the key features of Agile models and compare them with 1 13
K4
traditional approaches.
19 Analyze the trade-offs between using the Waterfall and Iterative models. 1 K4 13

20 Apply formal methods to ensure correctness in mission-critical systems. 1 K3 13

RBT
PART-C (15-Marks) CO Marks
Level
1 Evaluate the suitability of different process models for a large-scale ERP 1 K5 15
system.
2 Create a detailed workflow diagram of the Spiral model, highlighting its 1 K6 15
key activities.
3 Evaluate the effectiveness of RAD in accelerating software development 1 K5 15
timelines.
4 Design a custom Agile framework for a start-up company with limited 1 K6 15
resources.
5 Propose a hybrid model combining features of Agile and the V-model, 1 K6 15
and justify its use.

UNIT-II: REQUIREMENTS ANALYSIS AND SPECIFICATION

Requirement Analysis and Specification - Requirements Gathering and Analysis - Functional and
NonFunctional Requirements - Software Requirement Specification (SRS) - Formal System Specification:
Finite State Machines, Petri Nets - Modern Requirement Modelling Techniques - Introduction to UML:
Use Case Model, Class Diagrams - Agile Requirements Techniques: User Stories, Epics, Acceptance
Criteria.
PART-A (2-Marks)

S.NO QUESTIONS CO RBT LEVEL

1 Define Requirement Analysis. 2 K1

2 What is a functional requirement? 2 K1

3 List any two examples of non-functional requirements. 2 K2

4 State the purpose of a Software Requirement Specification (SRS). 2 K1

5 What are the characteristics of a good SRS? 2 K2

6 Differentiate between functional and non-functional requirements. 2 K2

7 Define Finite State Machine (FSM). 2 K1

8 What is a Petri Net? 2 K1

9 Mention two uses of UML in requirement modeling. 2 K2

10 Define the term "user story" in Agile techniques. 2 K1

11 What is the role of epics in Agile requirements? 2 K2

12 Explain acceptance criteria in Agile methodology. 2 K2

13 What is the purpose of a use case model in UML? 2 K1

14 State any two components of a class diagram in UML. 2 K2

15 Define requirements elicitation. 2 K1

16 List two modern requirement modeling techniques. 2 K2

17 What is formal system specification? 2 K1

18 Identify the significance of Petri Nets in system modeling. 2 K2

19 Define the concept of "epics" in Agile methodology. 2 K1

20 State the difference between user stories and epics. 2 K2

RBT
PART-B (13- Marks Or 16-Marks or 8-Marks) CO Marks
Level
1 Apply requirement analysis techniques to identify functional and non-
2 K3 13
functional requirements for an online banking system.
2 Analyze the steps involved in requirements gathering and specify their 2 13
K4
significance.
3 Discuss the structure and components of an SRS document. 2 K3 13
4 Compare Finite State Machines and Petri Nets as formal system 2 13
K2
specification tools.
5 Explain the role of UML diagrams in modern requirement modeling. 2 K3 13

6 Analyze the effectiveness of user stories in Agile requirements 2 13

K3
gathering.
7 Apply the use case model to capture requirements for a library 2 13
K3
management system.
8 Describe the process of creating class diagrams in UML and their 2 13
K3
application in software projects.
9 Evaluate the role of acceptance criteria in ensuring the quality of Agile 2 13
K3
projects.
10 Analyze the challenges in eliciting requirements from diverse 2 13
K3
stakeholders.
11 Apply Petri Nets to model a simple traffic light control system. 2 K3 13

12 Compare the advantages and limitations of formal specification 2 13

K2
techniques like FSM and Petri Nets.
13 Illustrate the role of epics in organizing user stories for a mobile 2 13
K3
application project.
14 Explain the need for combining modern modeling techniques with 2 13
K2
traditional methods in requirements analysis.
15 Apply Finite State Machines to represent the states and transitions of an 2 13
K3
elevator system.
16 Analyze the importance of traceability in maintaining requirement 2 13
K3
specifications.
17 Discuss the impact of incomplete requirements on software project 2 13
K2
success.
18 Apply Agile requirements techniques to define requirements for a social 2 13
K3
media application.
19 Evaluate the effectiveness of SRS documents in large-scale software 2 13
K3
development.
20 Analyze the significance of modern requirement modeling techniques in 2 13
K3
addressing complex systems.
RBT
PART-C (15-Marks) CO Marks
Level
1 Evaluate the advantages and disadvantages of formal system 2 K3 15
specification techniques in safety-critical systems.
2 Create a complete use case model for an online shopping application, 2 K3 15
including actors and use cases.
3 Propose a detailed class diagram for a university course registration 2 K3 15
system.
4 Design a workflow using Petri Nets for a hospital patient management 2 K3 15
system.
5 Evaluate the role of Agile requirements techniques in rapidly evolving 2 K3 15
software environments.
 UNIT-III: SOFTWARE DESIGN
Software Design Process and Concepts - Design Principles: Coupling, Cohesion, Functional
Independence - Design Patterns: Model-View-Controller, Publish-Subscribe, Adapter, Command,
Strategy, Observer, Proxy, Fagade - Architectural Styles: Layered, Client-Server, Tiered, Pipe and Filter
- User Interface Design - Modern Design Practices: Microservices Architecture, RESTful Services.
PART-A (2-Marks)

S.NO QUESTIONS CO RBT LEVEL

1 Define software design principles. 3 K2

2 What is the importance of cohesion in software design? 3 K1
3 Differentiate between coupling and cohesion. 3 K1
4 What is functional independence? 3 K2
5 Name any two design patterns and their applications. 3 K2
6 Define the Model-View-Controller (MVC) design pattern. 3 K1
7 What is the purpose of the Publish-Subscribe pattern? 3 K2
8 Mention the advantages of using the Adapter pattern. 3 K1
9 What is a Proxy design pattern? 3 K1
10 Define the Command pattern with an example. 3 K2
11 What is the role of architectural styles in software design? 3 K2
12 Define the Layered architectural style. 3 K1
13 Differentiate between Client-Server and Tiered architectural styles. 3 K1
14 What is the Pipe and Filter architectural style? 3 K2
15 Define User Interface (UI) design. 3 K2
16 What are RESTful services? 3 K2
17 Define Microservices Architecture. 3 K2
18 What are the key principles of user interface design? 3 K1
19 Mention two advantages of using modern design practices like RESTful 3 K1
services.
20 Define the Fagade design pattern. 3 K2
 RBT
PART-B (13- Marks Or 16-Marks or 8-Marks) CO Marks
Level
1 Explain the importance of coupling and cohesion in software design with 3 K2 13
examples.
2 Discuss functional independence and how it is achieved in software 3 13
K3
design.
3 Explain the working of the Model-View-Controller (MVC) design 3 13
K3
pattern with an example.
4 Illustrate the Adapter design pattern with a real-world scenario. 3 K3 13

5 Describe the Command pattern and its advantages in designing flexible 3 13

K2
systems.
6 Explain the Publish-Subscribe design pattern with a suitable example. 3 K2 13

7 Apply the Proxy pattern to a system with remote access functionality. 3 K3 13

8 Compare Layered and Tiered architectural styles with real-world 3 13

K2
examples.
9 Explain the Client-Server architectural style and its use in distributed 3 13
K2
systems.
10 Illustrate the working of the Pipe and Filter architectural style with an 3 13
K3
example.
11 Discuss the principles of user interface design and their impact on 3 13
K2
software usability.
12 Describe the Microservices Architecture and its advantages over 3 13
K2
monolithic architectures.
13 Apply RESTful services in designing a scalable web application. 3 K3 13

14 Analyze the importance of modern design practices in developing 3 13

K2
distributed systems.
15 Illustrate the Fagade design pattern and explain its applications in 3 13
K3
simplifying interfaces.
16 Discuss the role of design patterns in improving software maintainability 3 13
K2
and reusability.
17 Apply the Observer design pattern to implement a notification system. 3 K3 13

18 Explain the Strategy design pattern with its real-world usage. 3 K2 13

19 Analyze the differences between architectural styles and design patterns. 3 K2 13

20 Discuss the use of User Stories and RESTful services in modern system 3 13
K3
design.
RBT
PART-C (15-Marks) CO Marks
Level
1 Design a scalable e-commerce system using Microservices Architecture 3 K3 15
and RESTful services.
2 Apply the Model-View-Controller (MVC) design pattern to develop a 3 15
K3
social media platform.
3 Illustrate the Pipe and Filter architectural style by designing a data 3 15
K3
processing pipeline.
4 Design a user-friendly interface for a healthcare application, applying UI 3 15
K3
design principles.
5 Implement a notification system using the Observer design pattern. 3 K3 15

UNIT-IV: SOFTWARE TESTING AND MAINTENANCE

Testing Techniques: Unit Testing, Black Box Testing, White Box Testing, Integration and System Testing,
Regression Testing - Debugging and Program Analysis - Advanced Testing Techniques: Symbolic
Execution, Model Checking - Release Management: Continuous Integration, Continuous Deployment,
DevOps Practices.
PART-A (2-Marks)

S.NO QUESTIONS CO RBT LEVEL

1 Define unit testing and state its purpose. 4 K2

2 What is black-box testing? 4 K1
3 Differentiate between black-box and white-box testing. 4 K1
4 Define white-box testing and give an example. 4 K2
5 What is integration testing? 4 K2
6 Mention the advantages of system testing. 4 K1
7 Define regression testing and explain its significance. 4 K2
8 What is debugging? 4 K1
9 List any two techniques used in program analysis. 4 K1
10 Define symbolic execution in testing. 4 K2
11 What is model checking in advanced testing? 4 K2
12 Explain the purpose of continuous integration in release management. 4 K2
13 What is continuous deployment? 4 K2
14 Define DevOps practices in release management. 4 K2
15 Differentiate between continuous integration and continuous 4 K1
deployment.
16 Mention any two challenges in debugging. 4 K1
17 Define system testing and its importance. 4 K2
18 What is the role of test cases in black-box testing? 4 K1
19 State the purpose of program analysis. 4 K1
20 What is the main goal of regression testing? 4 K2
RBT
PART-B (13- Marks Or 16-Marks or 8-Marks) CO Marks
Level
1 Explain the process of unit testing with a suitable example. 4 K2 13
2 Describe the different types of black-box testing techniques. 4 K2 13

3 Apply white-box testing to design test cases for a sample program. 4 K3 13

4 Discuss the challenges faced during integration testing and how they can 4 13
K2
be resolved.
5 Explain system testing with examples of real-world applications. 4 K2 13

6 Illustrate the process of regression testing with an example. 4 K3 13

7 Write about debugging techniques and their significance in program 4 13

K2
development.
8 Apply symbolic execution to analyze the behavior of a program with 4 13
K3
multiple input paths.
9 Explain model checking as an advanced testing technique and its 4 13
K2
applications.
10 Discuss the benefits and challenges of implementing continuous 4 13
K2
integration in software projects.
11 Explain continuous deployment with an example of its use in modern 4 13
K2
software systems.
12 Discuss the key principles of DevOps practices in release management. 4 K2 13

13 Apply debugging techniques to identify and fix a logical error in a 4 13

K3
program.
14 Explain the differences between black-box, white-box, and grey-box 4 13
K2
testing with examples.
15 Describe the role of automated testing in continuous integration and 4 13
K2
continuous deployment.
16 Illustrate the process of program analysis with suitable techniques and 4 13
K3
examples.
17 Discuss the role of regression testing in maintaining software quality 4 13
K2
after updates.
18 Apply model checking to verify the properties of a finite state system. 4 K3 13

19 Describe the challenges and advantages of using symbolic execution in 4 13

K2
software testing.
20 Explain the process and benefits of combining DevOps with continuous 4 13
K2
deployment.
RBT
PART-C (15-Marks) CO Marks
Level
1 Design and implement test cases for a sample application using black- 4 K3 15
box and white-box testing.
2 Apply symbolic execution to create a decision tree for a program with 4 K3 15
multiple paths.
3 Develop a testing strategy that incorporates regression testing and 4 K3 15
advanced techniques.
4 Design a pipeline for continuous integration and continuous deployment 4 K3 15
using DevOps principles.
5 Apply model checking to verify the correctness of a system described 4 K3 15
using finite state machines.

UNIT-V: PROJECT MANGAEMENT

Software Project Management Fundamentals - Software Configuration Management - Project Scheduling and Agile
Project Management - DevOps: Motivation, Cloud as a Platform, Operations - Deployment Pipeline: Architecture,
Building, Testing, Deployment - Tools for DevOps: Jenkins, Docker, Kubernetes.

PART-A (2-Marks)

S.NO QUESTIONS CO RBT LEVEL

1 Define software project management. 5 K2

2 What is software configuration management (SCM)? 5 K1

3 Mention any two goals of project scheduling. 5 K1

4 What is Agile Project Management? 5 K2

5 Define DevOps and its significance in software development. 5 K2

6 What is the role of cloud computing in DevOps? 5 K2

7 List two benefits of using a deployment pipeline. 5 K1

8 What are the main stages in a deployment pipeline? 5 K1

9 Define Jenkins and its role in DevOps practices. 5 K2

10 What is Docker, and how is it used in software deployment? 5 K2

11 What are Kubernetes clusters? 5 K2

12 Define project scheduling in the context of software project 5 K2

management.
13 What is the significance of SCM in software projects? 5 K2

14 Mention any two tools commonly used in DevOps. 5 K1

15 What is the role of automated testing in the deployment pipeline? 5 K2

16 Differentiate between Jenkins and Docker. 5 K1

17 What is the purpose of Kubernetes in container orchestration? 5 K2

18 Define the term "continuous integration" in software development. 5 K2

19 List any two challenges in implementing DevOps. 5 K1

20 What is the purpose of operations in DevOps practices? 5 K2

RBT
PART-B (13- Marks Or 16-Marks or 8-Marks) CO Marks
Level
1 Explain the fundamentals of software project management and its
5 K2 13
importance.
2 Describe the steps involved in software configuration management 5 13
K2
(SCM).
3 Apply Agile Project Management principles to a software development 5 13
K3
scenario.
4 Explain the significance of project scheduling in meeting project 5 13
K2
deadlines.
5 Discuss the key motivations for adopting DevOps in modern software 5 13
K2
projects.
6 Describe how cloud computing acts as a platform for implementing 5 13
K2
DevOps.
7 Apply the concept of a deployment pipeline in automating software 5 13
K3
delivery.
8 Explain the architecture of a deployment pipeline and its stages. 5 K2 13

9 Illustrate the use of Jenkins in automating continuous integration tasks. 5 K3 13

10 Describe the working of Docker in managing application containers. 5 K2 13

11 Apply Kubernetes in managing containerized applications in a 5 13
K3
distributed environment.
12 Discuss the advantages and limitations of using Agile Project 5 13
K2
Management in large teams.
13 Apply SCM techniques to manage changes in a large software project. 5 K3 13

14 Explain the role of automated testing in enhancing the reliability of the 5 13

K2
deployment pipeline.
15 Describe the integration of Jenkins, Docker, and Kubernetes in a 5 13
K2
DevOps workflow.
16 Explain the role of continuous integration and continuous deployment in 5 13
K2
DevOps.
17 Illustrate the architecture of Kubernetes and its role in container 5 13
K3
orchestration.
18 Apply project scheduling techniques to a software project with tight 5 13
K3
deadlines.
19 Discuss the role of DevOps in bridging the gap between development 5 13
K2
and operations teams.
20 Describe the challenges in implementing DevOps and ways to overcome 5 13
K2
them.
RBT
PART-C (15-Marks) CO Marks
Level
1 Design and implement a deployment pipeline for an e-commerce
5 K3 15
application using DevOps tools.
2 Apply Agile Project Management to plan, execute, and monitor a 5 15
K3
software project.
3 Illustrate the integration of Jenkins, Docker, and Kubernetes in 5 15
K3
automating application delivery.
4 Design a project schedule for a large software development project using 5 15
K3
modern scheduling tools.
5 Apply SCM and DevOps principles to manage version control, build 5 15
K3
automation, and deployment.