QUESTION BANK

OVERVIEW
OBJECTIVE: The objective of this topic is to understand the
• The Software engineering Definition
• The Software Engineering Process and Product
• Various Process Models- Case study and comparisons
1. Define software product and software engineering (IEEE Def).
2. Mention properties of software.
3. “Software is not merely a collection of programs- Is programming systems product”.
Elucidate.
4. What are the main phases in software development?
5. Explain the requirements analysis phase of software development.
6. Explain the design phase of software development.
7. Explain the coding phase of software development
8. Explain the testing phase of software development.
9. Explain the software development model definition.
10. Compare the software development models.
11. Explain waterfall model.
12. Explain prototyping model.
13. Explain iterative enhancement model.
14. Explain the spiral model.
15. Which process model can be used for A simple data processing system. An outline
reservation system.
16. Mention the drawbacks of each of the software development models.
17. Explain the role of metrics.
18. Comment on the error distribution in the different phases.
19. Comment on the distribution of effort in the life span of software development.
20. What are major phases in the entire life cycle of the software? Which of them consume
maximum effort?
21. Is it reasonable to assume that if software is easy to test, it will be easy to maintain. Suppose
that putting in extra effort is design and coding you increase the cost of these phases by 15% but
you reduce the cost of maintenance by 5%. Will you decide to put in the extra effort and why?
22. Describe the major phases in software development. Discuss the error distribution and cost of
correcting the errors during development.
23. Explain the spiral model. Discuss the features of a software project for which the spiral model
could be a preferred model. Justify your answer.
24. Describe the role of management on software development
25. What is software engineering? Describe the following process model with their relative merits
and demerits
i. Waterfall model.
ii. Evolutionary development.
26. What are the objectives of software engineering?
27. What software engineering? How is it different from traditional engineering approach?
28. Explain four significant attributes that every software product should posses.
29. What is the need for validating the requirements? Explain any requirement validation
techniques.
30. Differentiate between the following terms
i. Milestone and deliverable
ii. Requirements Definition and Specification
31. Distinguish between a software product and a software process.
32. Explain different process models along with their relative merits and demerits.
33. Give a brief description of software prototyping and briefly discuss the various prototyping
techniques.
34. What are software engineering methods? What are its components?
35. What are the key challenges facing software engineering?
36. “Software engineers have responsibilities to the engineering profession and society.
They should not simple be concerned with the technical issues”. Justify the statement.

REQUIREMENT ENGINEERING
OBJECTIVE: The objective of this topic is to understand the
• Basic requirement analysis process
• Various system models
• Requirement definition and specification
• Software requirement and specification document
• Software prototyping
• Various prototyping techniques

37. What is SRS?

38. Explain the DFD?
39. What is structured analysis?
40. Write a SRS for the following: a) Student registration system b) Diet management control
41. Describe the basic goals and desirable characteristics of an SRS. Discuss the important
system properties that an SRS should specify.
42. Develop a zero level and first level DFD for payroll system with suitable specification.
43. Explain DFD and their role in problem analysis.
44. Develop a DFD for a computerized evaluation scheme. Assume marks of all students are
stored in a file.
45. What are the different aspects that should be specified in an SRS?
46. Develop a zero level and first level DFD for banking system with suitable specifications.
47. How can u specify ‘user friendliness’ of the software in the quantitative terms?
48. With an example describe the role of SRS dataflow diagrams in structured system analysis.
49. Write an example; illustrate the use of prototyping as a method for problem analysis.
Discuss its advantages and disadvantages.
50. Describe the structure of SRS and discuss the technologies for verifying the requirements.
51. Explain the following terms
1. Ethnography
2. Data dictionary
3. COTS
4. Stake holder
52. How to organize so that it can be easily manageable?
53. What is software prototyping? Explain throwaway and evolutionary prototyping techniques.
54. Draw a DFD for the following applications
A salary system which computes employee salary per week and deductions. Input in to the
system is a worksheet containing empid, name, number of hours worked, etc. System maintains
table holding tax rates and pay rate for various employee classes. The output is the cheque to the
employee.
55. What are the differences between requirements definition and requirements specification?
56. Discuss the requirements change management process.
57. Suggest who will be stakeholders in a university management system. Explain why it is
almost inevitable that the requirements of the different stakeholders will conflict in some ways.
58. Who should be involved in a requirements review? Draw a process model showing how a
requirements review might be organized.

SOFTWARE DESIGN
OBJECTIVE: The objective of this topic is to understand the
• The software design process
• Design principles
• Function oriented design
• User interface design
59. How are changes in software specifications monitored at various stages of software
development?
60. Why is design a two level process? Why should the system design be furnished before
starting the detail design, rather than starting the detailed design right after the requirements?
61. How are cohesion and coupling related? Give an example of where cohesion increases and
coupling decreases.
62. What is the fundamental difference between the approaches of structured design and object
oriented design?
63. Differentiate between top down approach and bottom approach.
64. Develop a structured design for interactive user interface queries for basic income tax
information with suitable assumptions.
65. What is the difference between functional abstraction and data abstraction?
66. If a module has logical cohesion what kind of coupling is this module likely to have with
others?
67. What are major methods of verifying design? If the design is expressed in a normal language,
can an automated tool help in verification and in what manner?
68. What is object oriented design? Explain with a real world problem.
69. Give design specification and design document for a library system.
70. What needs are to be specified during detail design? What are the described characteristics
of a language to express detailed design?
71. What is the relation between cohesion metric and cyclomatic complexity?
72. What are the methods of verifying a detailed design? Which of these in your opinion is likely
to be most effective in revealing design errors?
73. Describe briefly methods of code verification. Which of these is best suited for “catching” the
maximum number of errors and which of these is the most cost effective?
74. What are the major concepts that help is making program more readable?
75. “object-oriented design tends to be programming language independent” why? What is the
fundamental reference of this design approach compare to structural design?
76. Define the object-oriented design methodology and contrast it with structure design
methodology.
77. Explain the module level concepts of coupling and cohesion; and the relation between them.
78. What is cyclomatic number? With an example, describe how this metric is calculated?
Compare the metric with cohesion metric.
79. Explain the different methods of verifying a detailed design and discuss their effectiveness in
revealing design errors.
80. Write short notes on structure charts and PDL.
81. Discuss coupling and cohesion.
82. Discuss structure and cohesion.
83. Discuss object oriented approach to software design.
84. What is Halstead’s measure? Explain.
85. Write short notes on PDL.
86. What is the difference between functional abstraction and data abstraction? Explain with
suitable example.
87. How are cohesion and coupling related? Give example where cohesion increases and
coupling decreases.
88. What is the fundamental difference between the approaches of structures chart, extend the
notion for structured charts to represent the structure of programs where modules communicate
using global variable?
89. What is the fundamental difference between the approaches of structures design and object
oriented design?
90. Give the design specification and design document for student information system.
91. What are the different methods of verifying a detailed design? Which of them will reveal
design error more effectively?
92. Describe the basic design principles of problem partitioning and abstraction.
93. What is structure chart and how are different types of modules represented in a structure
chart? Illustrate with suitable example.
94. Explain the use of design reviews in verifying a design.
95. With suitable examples illustrate the use of process design language for specifying the
detailed design.
96. Explain with suitable examples and illustrate the use of process design language for
specifying the detailed design.
97. Explain a technique for computing the cohesion metric of a module.
98. Explain the use of critical design reviews for verifying a detailed design.
99. Briefly outline the process of modular design of a system.
100. Define and Explain the measure effective modularity of software systems.
101. Discuss the important methods for producing quantitative specifications for modular
interfaces with suitable example.
102. Describe the object oriented design methodology and discuss its comparative advantages
and disadvantages.
103. Describe the salient features of process design language and discuss its importance in
software engineering.
104. Explain the most commonly used size metrics and complexity metrics for code.
1. What is cyclomatic number? Discuss its significance with suitable example.
106. Why is it important to use different notations to describe design?
107. Differentiate between function oriented designs and object oriented design strategies.
108. Explain why maximizing cohesion and minimizing coupling leads to more maintainable
systems. What other design attributes influence system more maintainable.
109. What are the principles to be followed while designing user interface.
110. Write a bubble sort procedure in PDL and its flow-graph. Also calculate Mclabe’s Cyclomatic
complexity?
111. Describe system architecture modeling with the help of a neat diagram.
112. Explain the different software design strategies with proper illustrations.
113. Write a brief note on data flow design principle.
114. Describe user interface design principles.
115. What are the difference between coupling and cohesion?
116. Write a short note on data dictionary.
117. Explain why it may be necessary to design the system architecture before the specifications
are written.
118. Giving reasons for your answer, suggest an appropriate structural model for the following:
An automated ticket issuing system used by passengers at a railway station.
A computer controlled video conferencing system which allows video, audio and computer data to
be visible to several participants at the same time.
119. Suggest situations where it is unwise or impossible to provide a consistent user interface.

VERIFICATION AND VALIDATION

OBJECTIVE: The objective of this topic is to understand the
• Software reliability
• Software reuse
• Software testing
• Clean room software testing

120. Explain bottom up and top down testing.

121. Define error, fault and failure; bring out the difference between each with a suitable example.
122. What is functional testing and how it differs from structural testing? Explain any two methods
for selecting test cases for functional testing.
123. Explain the complete testing process with help of suitable diagrams.
124. Write short notes on test oracles, instrumentation for structural testing.
125. Discuss the various levels of testing.
126. Compare functional testing with structural testing.
127. Write short notes on verification and validation.
128. Why does software fails after passes acceptance testing?
129. Discuss different levels of testing and set goals of these different levels.
130. Explain error, fault and failure. What is the difference between a failure and a fault?
Explain bottom up and top down testing.
131. Describe the levels of testing and goals at each level.
132. Discuss different coverage criteria for structural testing.
133. What is a test plan and what does a typical test plan contains?
134. Write short notes on psychology of testing and mutation testing.
135. Explain the following: a) Verification b) Validation.
136. Discuss the important objectives of testing software system.
137. Discuss the problems with exhaustive testing.
138. Explain the following with ex. a) Basic path testing b) Control structure testing.
139. Short notes on bottom up testing, criteria for completion of testing and debugging.
140. Write short notes on a) Fault tolerance b) Defensive programming c) Software re- usability.
141. What is software reliability? Explain reliability metrics.
142. Explain briefly the various software reliability metrics.
143. Briefly bring out the difference between verification and validation.
144. Explain the stages of testing process.
145. Describe briefly the following:
a) Defensive programming
b) Cleanroom software development
146. Explain the advantages and disadvantages of reusing software components.
147. How do you distinguish between a program inspection and other types of quality reviews?
148. What are static program analyzers? What are the stages involved in static analyses?
149. Discuss the levels of testing involved in object oriented system.

CRITICAL SYSTEMS
OBJECTIVE: The objective of this topic is to understand the
• Dimensions of dependability
• Importance of dependability to critical systems
• Critical system specification

150. What are the most important dimensions of system dependability?

151. What are the factors you need to consider when specifying the overall system reliability?
152. Explain why there is a close relationship between system availability and system security?
153. Suggest six reasons why dependability is important in critical systems.
154. Discuss the stages involved in security specification process.

SOFTWARE MANAGEMENT
OBJECTIVE: The objective of this topic is to understand the
• Project Planning
• Project Scheduling
• Managing people
• Cost Estimation

155. Explain the importance of project staffing.

156. What are the characteristics of clean room software development?
157. What is SEI process maturity model?
158. “Members of a well –led, cohesive group are loyal to the group”. Justify
159. Explain in detail the various management activities.
160. Explain in detail software cost estimation.
161. Explain cost estimation techniques.
162. What is COCOMO model? Describe its approach to estimate person months.
163. Briefly explain how algorithmic cost can be used for estimating software cost.
164. Write short note on:
a) CASE tools
b) Software quality assurance
c) SEI CMM
165. Explain in detail
a) Software metrics c) SEI-CMM Model e) Process analysis and measurement.
b) Quality Metrics d) CASE

SOFTWARE EVOLUTION
OBJECTIVE: The objective of this topic is to understand the
• How legacy systems are critical to the operation of many businesses
• Legacy system structures
• Re-engineering as an option for software system evolution
• Activities such as reverse engineering and program restructuring
166. Why is source level translation necessary in some cases?
167. List the principle factors that affect re-engineering costs.
168. Differentiate between reverse engineering and re-engineering.
 Chapter
Text Block
Class Title/ Page Cumulative
Reference
Topics to be covered Chapter Dig
Topic No.
Literature
1 Software Engineering –An 12
1.1 27-38 5
Introduction
2 Professional and Ethical 3
1.2 38-41 ___
responsibility =15
3 6
Socio-Technical system:
2.1 44-49 2
Emergent System
Chapter #: 1
4 9
System Engineering 2.2 49-58 6
Chapter #: 2
5 Organizations, people & 4
2.3 58-62 2
Computer System
6 2
Legacy system 2.4 62-64 2
=21
7*
Revision 36
8*
Class Test

9 Critical System: A simple 4

3.1 67-71
safety-critical system
10 System Dependability 3
3.2 71-74
11 Availability And Reliability 5
3.3 75-79
=12
12* Revision
13 Software Process:
4.1 87-95 8
14 Chapter #: 3 Models

15 Chapter #: 4 Process iteration 3

4.2 95-98
16 Process Activities 98- 7
4.3
106
17 The Rational Unified 106- 3
4.4
Process 109
18*
Computer Aided Software 109- 4
4.5
Engineering 113 =25
19*
Revision 47
Class Test
 Chapter
Text Block
Class Title/ Page Cumulative
Reference
Topics to be covered Chapter Dig
Topic No.
Literature
20 Requirements: Functional & 141- 4 10
6.1
Non Functional Requirements 150
21 151- ___ 3
User Requirement 6.2
153
22 153- 4 5
System Requirements 6.3
158
23 159- 1 2
Interface Specification 6.4
160
24 Chapter #: 6 160- 2 3
The SRS 6.5
163 =23
25 Chapter #: 7 Requirement 5
166-
Engineering Process: 7.1 2
26 170
Feasibility Studies
27 Requirement Elicitation 170- 12
7.2 6
&analysis 182
28 182- 2
Requirements Validation 7.3 ___
184
29* 185- 5
Requirements management 7.4 3
190 =24
30*
Revision 47
Class Test
31 Software Design: 7
265-
Architectural Design 11.1 1
32 271
Decision
271-
33 System organization 11.2 3 5
276
276- 3
34 Modular Decomposition 11.3 2
279
280- 5
35 Chapter #: Control Style 11.4 4
284 =20
11 337- 8
36 Object Orient Design 14.1 4
344
Chapter #: 344- 8
37 Object & Object Classes 6
14 352
14.2
38 An Object Oriented Design 352- 8
4
Process 359
39* 359- __ 1
Design Evolution 14.3
360 =25
40*
Revision 45
Class Test
 Chapter
Text Block
Class Title/ Page Cumulative
Reference
Topics to be covered Chapter Dig
Topic No.
Literature
41 Development: Rapid 415- 5
17 3
Software Development 419
42 17.1 10
Agile Method 420-
4
Extreme Programming 429
43 17.2
Rapid Application 429- 4
Chapter #: 17.3 3
44 Development 433 =19
17
Software Evolution: 5
45 512-
Chapter #: Program Evolution 21.1 2
516
21 Dynamics
46
516- 6
Software Maintenance 21.2 3
522
47
522- 6
Evolution Process 21.3 7
48* 528
528- 5
49* Legacy System Evolution 21.4 3
533 =22
Revision 41
Class Test
50 Management: Managing 616-
25.1 1 5
Chapter #: People Selecting Staff 620
51 25 620- 4
Motivating People 25.2 1
623
52 Chapter #: 623- 8
26 Managing People 25.3 1
631
53 The People Capability 631- 2
25.4 1
Maturity Model 633 =19
54
Software Cost 9
636-
55 Estimation: Software 26.1 3
644
Productivity
56 644- 2
Estimation Techniques 26.2 1
646
57 647- 14
Algorithmic Cost Modelling 26.3 9
660
58* Project Duration &
661- 2
Staffing 26.4 __
662 =27
59*
Revision 46
Class Test
 Chapter
Text Block
Class Title/ Page Cumulative
Reference
Topics to be covered Chapter Dig
Topic No.
Literature
1 System Models: Context 193- 5
8.1 2
Model 197
2 197- 4
Behavior Models 8.2 3
201
3 12
Data Models, Object 8.3, 201-
9
models 8.4 211
4 211- 3
Structured Methods 8.5 1
Chapter #: 8 214 =24
5 Project Management: 116- 5
5.1 1
6 Chapter #: 5 Management Activities 120
120- 3
Project Planning 5.2 2
7 123
5.3 123- 5 5
Project Scheduling
8 128
5.4 128- 6 7
Risk Management
9* 135 =20

10*
Revision 44
Class Test
11 Verification & 539- 3 7
22.1
Validation: Planning 545
12 545- 3 6
Software Inspection 22.2
551
13 551- 2 3
Automated Static Analysis 22.3
554
14 Verification & Formal 22.4 554- 1 5
Method 559 =21
Chapter #: 3 Software Testing: 561-
15 23.1 5 11
System Testing 571
16 Chapter #: 4 572- 2 4
Component Testing 23.2
575
17
575- 9 10
Test Case Testing 23.3
18 585
585- 1 2
Test Automation 23.4
19* 587 =27
Revision
20*
48
Class Test
Literature
Publication specification
Book type Code Title and Author
Edition Publication Year
Text Book T1 Software Engineering by Ian Sommerville 6th Pearson
Education 2001
Reference Book R1 Software Engineering: A Practitioner's Approach by
Roger Pressman 4th TMH
Reference Book R2
An Integrated Approach to Software Engineering by Pankaj
Jalote
Narosa Publications
Reference Book R3
Object oriented and classical software engineering by Stefan
R Schach
TMH 2002