RN SHETTY TRUST®

RNS INSTITUTE OF TECHNOLOGY

Autonomous Institution Affiliated to VTU, Recognized by GOK, Approved by AICTE
(NAAC ‘A+ Grade’ Accredited, NBA Accredited (UG - CSE, ECE, ISE, EIE and EEE)
Channasandra, Dr. Vishnuvardhan Road, Bengaluru - 560 098
Ph:(080)28611880,28611881 URL: www.rnsit.ac.in

DEPARTMENT OF INFORMATION SCIENCE & ENGINEERING

Question Bank
SUBJECT CODE AND TITLE 21CS61 SOFTWARE ENGINEERING AND PROJECT
MANAGEMENT.
SCHEME 2021 BATCH 2021-25
SEMESTER& SECTION VI “B” Section
FACULTY NAME
Ms Harshitha P

Q.No. Question Mark RBT COs

s *
Module 1
1 Define software engineering and explain the layers of software
6 L2 CO1
engineering?
2 Explain the essence of software engineering practice 6 L2 CO1
3 Which process model leads to software reuse? Justify 6 L2 CO1
4 With a neat diagram explain the layers of software engineering. 6 L2 CO1
5 Explain the unique nature of WebApps. 10 L2 CO1
6 Briefly Explain software process. 6 L2 CO1
7 Explain the following
I. The essence of practice 6 L2 CO1
II. General Principles
8 Explain software myths in detail. 6 L2 CO1
9 Explain Generic Process model in detail. 12 L2 CO1
10 Explain Process Assessment and Improvement in detail. 6 L2 CO1
11 Explain the following with neat diagram
I. The Waterfall model 12 L2 CO1
II. The Incremental model
12 Explain the following with neat diagram
I. The Evolutionary Process model 12 L2 CO1
II. Specialized Process model
Module 2
1 List out the seven distinct tasks of requirements engineering 6 L2 CO2
2 List and explain all the Requirement Engineering Tasks. 12 L2 CO2
3 Explain the following
I. Identifying Stakeholders
II. Recognizing Multiple Viewpoints 12 L2 CO2
III. Working toward Collaboration
IV. Asking the First questions
4 Explain the process of Eliciting requirements of a project 6 L2 CO2
5 State the challenges involved in software requirements of a project 6 L3 CO2
6 What is use case diagram? Draw a use case diagram for an ATM system? 6 L2 CO2

1
7 Explain the following
I. Negotiating Requirements 6 L2 CO2
II. Validating Requirements
8 Explain activity diagrams? Draw an activity diagram for an ATM 6 L2 CO2
system?
9 Explain Requirement analysis in detail. 6 L2 CO2
10 Explain the following
I. Analysis rules of thumb 12 L2 CO2
II. Domain Analysis
11 Explain Requirement Modelling Approaches in detail. 6 L2 CO2
12 Briefly explain Scenario-Based Modelling 12 L2 CO2
13 Explain the following
I. Creating a Preliminary Use Case
II. Refining a Preliminary Use Case 12 L2 CO2
III. Writing a Formal Use Case

14 Explain UML models that supplement the use case. 12 L2 CO2

15 List and Explain Data Modelling Concepts in detail. 12 L2 CO2
16 List and Explain Class Based Modelling in detail. 12 L2 CO2
Module 3
1 What is Agility?List agility principles for those who want to achieve
6 L2 C03
agility.
2 Explain the following
I. Agility And The Cost of Change 6 L2 C03
II. What is an Agile Process?
3 Explain the following
I. The Politics of Agile Development. 6 L2 C03
II. Human Factors.
4 Explain Extreme Programming (XP)in detail. 12 L2 C03
5 Explain the following
I. XP values 12 L2 C03
II. The XP Process
6 Explain the following
I. Industrial XP 12 L2 C03
II. The XP Debate
7 Explain other Agile Process Models in briefly? 12 L2 CO3
8 Explain A Tool set for the Agile Process 6 L2 C03
9 What is agile software development? outline the agile process . 8 L2 CO3
10 What is software Engineering Knowledge. List and Explain the core
12 L2 CO3
principles
11 List and Explain the Principles that guide each framework activity. ` L2 CO3
Module 4
1 List and explain the problems that are encountered in software projects. 8 L2 CO4
2 Why is Software Project Management Important. 6 L2 CO4
3 Explain the following
I. Software Projects Versus Other types of projects 12 L2 CO4
II. Contract Management and Technical Project Management
2
4 Explain the following
I. Activities Covered by Software Project Management. 12 L2 CO4
II. Plans,Methods and Methodologies.
5 Explain the following
I. Changes to the Characteristics of software projects
II. Compulsory versus voluntary users 12 L2 CO4
III. Information systems Versus embedded systems
IV. Software products versus services.
6 Explain the following
I. Stakeholders
12 L2 CO4
II. Setting Objectives
III. Sub-objectives and Goals
7 Explain the following
I. The Business Case 6 L2 CO4
II. Project Success and Failure
8 Define and Explain Management with a neat diagram. 6 L2 CO4
9 Explain Management Control with neat diagram. 6 L2 CO4
10 Explain Software development and Project Management Life Cycles. 6 L2 CO4
11 Explain Project Management Life Cycle in detail. 12 L2 CO4
12 Explain Traditional Versus Modern Management Practices in detail. 12 L2 CO4
13 What is contract management. 6 L2 CO4
14 Explain the objectives of activity planning. 8 L2 CO4
15 With a neat diagram explain project control cycle model. 8 L2 CO4
Module 5
1 What are the problems with software project from manager’s point of
6 L2 CO5
view?
2 Explain the framework of Software Quality in Planning Project with a
6 L2 CO5
neat diagram.
3 Explain the Importance of Software Quality. 6 L2 CO5
4 Explain the following
I. Defining Software Quality 6 L2 CO5
II. Software Quality Models
5 Explain the following
I. Garvins Quality Dimensions
6 L2 CO5
II. McCalls model
III. Boehms mode
6 Explain Product and Process Metrics 6 L2 CO5
7 Explain the following
I. Product Versus Process Quality Management 6 L2 CO5
II. Quality Management Sysems
8 Explain the Techniques to Enhnace Software Quality 6 L2 CO5
9 Explain the following
I. Inspections 6 L2 CO5
II. The General Principles behind the Fagan method
10 Explain Structured programming and clean room software development
6 L2 CO5
in detail.

3
 11 Explain Software quality Circles and Software Reliability. 6 L2 CO5
12 Explain Software Reliability in detail 6 L2 CO5
13 Explain quality plans in detail. 6 L2 CO5
2 What are the benefits of management? 8 L2 CO5
3 What are the characteristics which makes software project s different 8 L2
CO5
from other project?
4 Explain. Why FPA methodology is better than LOC methodology 8 L2 CO5

Course Coordinator Module Coordinator Program Coordinator/ HOD