Question Bank

QUESTION BANKOVERVIEWOBJECTIVE: 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 comparisons1. 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 demeritsi. 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 termsi. Milestone and deliverableii. Requirements Definition and Specification31. 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 control41. 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 terms1. Ethnography2. Data dictionary3. COTS4. Stake holder52. 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 DESIGNOBJECTIVE: The objective of this topic is to understand the• The software design process• Design principles• Function oriented design• User interface design59. 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 VALIDATIONOBJECTIVE: 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 programmingb) Cleanroom software development146. 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 SYSTEMSOBJECTIVE: 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 MANAGEMENTOBJECTIVE: 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 toolsb) Software quality assurancec) SEI CMM165. Explain in detaila) Software metrics c) SEI-CMM Model e) Process analysis and measurement.b) Quality Metrics d) CASE

SOFTWARE EVOLUTIONOBJECTIVE: 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 restructuring166. 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.

Class

Chapter Title/

Reference Literature

Topics to be coveredText

Chapter Topic

Page No.

Block Dig Cumulative

1

Chapter #: 1

Chapter #: 2

Software Engineering –An Introduction

1.1 27-38 512

2 Professional and Ethical responsibility

1.2 38-41 ___3

=153

Socio-Technical system:Emergent System

2.1 44-49 26

4 System Engineering 2.2 49-58 6 9

5 Organizations, people & Computer System 2.3 58-62 2

4

6 Legacy system 2.4 62-64 22

=217* Revision 368* Class Test

9

Chapter #: 3

Chapter #: 4

Critical System: A simple safety-critical system 3.1 67-71

4

10 System Dependability 3.2 71-74 3

11 Availability And Reliability3.3 75-79

5=12

12* Revision

13Software Process:

4.1 87-95 8Models

14 Process iteration 4.2 95-98 3

15 Process Activities4.3

98-106

7

16 The Rational Unified Process 4.4

106-109

3

17 Computer Aided Software Engineering 4.5

109-113

4=25

18* Revision 4719* Class Test

Class Chapter Title/

Topics to be covered Text Chapter

Topic

Page No.

Block Dig

Cumulative


20

Chapter #: 6

Chapter #: 7

Requirements: Functional & Non Functional Requirements

6.1141-150

4 10

21User Requirement 6.2

151-153

___ 3

22 System Requirements 6.3153-158

4 5

23 Interface Specification 6.4159-160

1 2

24 The SRS 6.5160-163

2 3=23

25 Requirement Engineering Process: Feasibility Studies

7.1166-170

25

26 Requirement Elicitation &analysis 7.2

170-182

612

27Requirements Validation 7.3

182-184

___2

28Requirements management 7.4

185-190

35


31

Chapter #: 11

Chapter #: 14

Software Design: Architectural Design Decision

11.1265-271

17

32 System organization 11.2271-276

3 5

33 Modular Decomposition 11.3276-279

23

34 Control Style 11.4280-284

45

=2035 Object Orient Design 14.1

337-344

48

36 Object & Object Classes14.2

344-352

68

37 An Object Oriented Design Process

352-359

48

38 Design Evolution 14.3359-360

__ 1=25




Topic

Page No.

Block Dig

Cumulative


41

Chapter #: 17

Chapter #: 21

Development: Rapid Software Development

17415-419

35

42 Agile MethodExtreme Programming

17.1

17.2

420-429

410

43 Rapid Application Development 17.3

429-433

34

=1944 Software Evolution:

Program Evolution Dynamics

21.1512-516

25

45 Software Maintenance 21.2516-522

36

46 Evolution Process 21.3522-528

76

47 Legacy System Evolution 21.4528-533

35


50Chapter #:

25

Chapter #: 26

Management: Managing People Selecting Staff 25.1

616-620

1 5

51 Motivating People 25.2620-623

14

52 Managing People 25.3623-631

18

53 The People Capability Maturity Model 25.4

631-633

12

=1954 Software Cost

Estimation: Software Productivity

26.1636-644

39

55 Estimation Techniques 26.2644-646

12

56 Algorithmic Cost ModellingProject Duration & Staffing

26.3647-660

914

5726.4

661-662

__2



Reference


Topic

Page No.

Block Dig

Cumulative

Literature1

Chapter #: 8

Chapter #: 5

System Models: Context Model 8.1

193-197

25

2Behavior Models 8.2

197-201

34

3 Data Models, Object models

8.3, 8.4

201-211

912

4 Structured Methods 8.5211-214

13

=245 Project Management:

Management Activities 5.1116-120

15

6 Project Planning 5.2120-123

23

7 Project Scheduling 5.3 123-128

5 5

8 Risk Management 5.4 128-135

6 7=20


11

Chapter #: 3

Chapter #: 4

Verification & Validation: Planning 22.1

539-545

3 7

12 Software Inspection 22.2545-551

3 6

13Automated Static Analysis 22.3

551-554

2 3

14 Verification & Formal Method

22.4 554-559

1 5=21

15Software Testing: System Testing 23.1

561-571

5 11

16 Component Testing 23.2572-575

2 4

17 Test Case Testing 23.3575-585

9 10

18 Test Automation 23.4585-587

1 2=27


LiteraturePublication specificationBook type Code Title and AuthorEdition Publication YearText Book T1 Software Engineering by Ian Sommerville 6th Pearson Education 2001Reference Book R1 Software Engineering: A Practitioner's Approach by Roger Pressman 4th TMHReference Book R2An Integrated Approach to Software Engineering by PankajJaloteNarosa PublicationsReference Book R3

Object oriented and classical software engineering by StefanR SchachTMH 2002

Documents

Question Bank