lOMoARcPSD|21699291

QB CSE 605 SE - i ama student of bachelor of technology

(cse) and uploaded the document of software
bachelors in technology (Amity University)

Studocu is not sponsored or endorsed by any college or university

Downloaded by Vivek Parashar (vivekparashar.19@gmail.com)
 lOMoARcPSD|21699291

AMITY UNIVERSITY MADHYA

PRADESH,GWALIOR

QUESTION BANK
OF
SOFTWARE ENGINEERING
CSE-605

PREPARED BY
Dr. ARVIND KUMAR UPADHYAY
Professor
Department of Computer Science & Engineering
Amity School of Engineering & Technology
AMITY UNIVERSITY MADHYA PRADESH,GWALIOR
June 2022

Downloaded by Vivek Parashar (vivekparashar.19@gmail.com)

 lOMoARcPSD|21699291

AMITY SCHOOL OF ENGINEERING & TECHNOLOGY (ASET)

META DATA : QUESTION PAPER

Course BTech.

Batch 2021-2022

Semester 6th Sem

Course Subject Software Engineering

Course Code CSE-605

Course Credits 03

Syllabus Attached

Question bank Attached

Name of the Faculty

Dr. Arvind Kumar Upadhyay, Prof.(CSE)
Member, Designation

Name of Assisting/
Re-checking Faculty -
Member

Name of the HoD Dr. Venkatadri M. Marriboyina

Downloaded by Vivek Parashar (vivekparashar.19@gmail.com)

 lOMoARcPSD|21699291

SOFTWARE ENGINEERING

Course Code: CSE 605 Credit Units: 03

Course Objective:

The basic objective of Software Engineering is to develop methods and

procedures for software development that can scale up for large systems and
that can be used to consistently produce high-quality software at low cost and
with a small cycle time. Software Engineering is the systematic approach to the
development, operation, maintenance, and retirement of software.
The course provides a thorough introduction to the fundamentals principles of
software engineering. The organization broadly be based on the classical
analysis-design-implementation framework.

Course Contents:

Module I: Introduction
Software life cycle models: Waterfall, Prototype, Evolutionary and Spiral
models, Overview of Quality Standards like ISO 9001, SEI-CMM

Module II: Software Metrics and Project Planning

Size Metrics like LOC, Token Count, Function Count, Design Metrics, Data
Structure Metrics, Information Flow Metrics. Cost estimation, static, Single and
multivariate models, COCOMO model, Putnam Resource Allocation Model,
Risk management.

Module III: Software Requirement Analysis, design and coding

Problem Analysis, Software Requirement and Specifications, Behavioural and
non-behavioural requirements, Software Prototyping Cohesion & Coupling,
Classification of Cohesiveness & Coupling, Function Oriented Design, Object
Oriented Design, User Interface Design Top-down and bottom-up Structured
programming, Information hiding,

Module IV: Software Reliability, Testing and Maintenance

Failure and Faults, Reliability Models: Basic Model, Logarithmic Poisson
Model, Software process, Functional testing: Boundary value analysis,
Equivalence class testing, Decision table testing, Cause effect graphing,
Structural testing: path testing, Data flow and mutation testing, unit testing,

Downloaded by Vivek Parashar (vivekparashar.19@gmail.com)

 lOMoARcPSD|21699291

integration and system testing, Debugging, Testing Tools, & Standards.

Management of maintenance, Maintenance Process, Maintenance Models,
Reverse Engineering, Software RE-engineering

Module V: UML
Introduction to UML,Use Case Diagrams, Class Diagram: State Diagram in
UML Activity Diagram in UML Sequence Diagram in UML Collaboration
Diagram in UML

Examination Scheme:

Components A CT S/V/Q HA EE
Weightage (%) 5 10 8 7 70
CT: Class Test, HA: Home Assignment, S/V/Q: Seminar/Viva/Quiz, EE: End
Semester Examination; Att: Attendance

Text & References:

Text:

 K. K. Aggarwal & Yogesh Singh, “Software Engineering”, 2nd Ed, New Age
International, 2005.
 R. S. Pressman, “Software Engineering – A practitioner’s approach”, 5 th Ed.,
McGraw Hill Int. Ed., 2001.

References:

 R. Fairley, “Software Engineering Concepts”, Tata McGraw Hill, 1997.

 P. Jalote, “An Integrated approach to Software Engineering”, Narosa, 1991.
 Stephen R. Schach, “Classical & Object Oriented Software Engineering”,
IRWIN, 1996.
 James Peter, W. Pedrycz, “Software Engineering”, John Wiley & Sons.
 Sommerville, “Software Engineering”, Addison Wesley, 1999.

SUMMARY OF QUESTIONS

Downloaded by Vivek Parashar (vivekparashar.19@gmail.com)

 lOMoARcPSD|21699291

S.N. Module Section –A Section –B Section –C

(6 Marks) (10 Marks) (20 Marks)

1 I 10 07 05
2 II 10 07 05
3 III 10 07 05
4 IV 10 07 05
5 V 12 09 08
TOTAL 52 37 28

Section A

Downloaded by Vivek Parashar (vivekparashar.19@gmail.com)

 lOMoARcPSD|21699291

MODULE-1

1 .Explain the reason as why is primary goal of software development now

shifting from producing good quality software to good quality maintainable
software?
2. List the reasons for the “software crisis”?Why are CASE tools not
normally able to control it?
3 .“The software crisis is aggravated by the progress in hardware
technology?” Explain with examples.
4 .Illustrate software crisis? Was Y2K a software crisis?
5 . List out the significance of software crisis in reference to software
engineering discipline.
6. Explain the software myths affecting software process? Explain with the
help of examples.
7. State the difference between program and software. Why have documents
and documentation become very important.
8 . Describe software engineering from real life example? Is it an art, craft or a
science? Discuss.
9. Discuss the aim of software engineering? What does the discipline of
software engineering discuss?
10. Define the term “Software engineering”. Explain the major differences
between software engineering and other traditional engineering disciplines.
MODULE-2
11. List the advantages and disadvantages of involving a software engineer
throughout the software development planning process.
12. Explain the spiral model of software development. What are the
limitations of such a model?
13. Describe the rapid application development (RAD) model.Discuss each
phase in detail.
14. Describe the characteristics to be considered for the selection of the life
cycle model?

15. List out the advantages and disadvantages of the linear sequential model.

16. Explain the concept of prototyping? Discuss the software prototyping

model.
17. Discuss the significance and use of requirement engineering. What are
the problems in the formulation of requirements?
18. Requirements analysis is unquestionably the most communication
intensive step in the software engineering process. Why does the
communication path frequently break down ?
19. Describe the crucial process steps of requirement engineering ? Discuss with
the help of a diagram.

Downloaded by Vivek Parashar (vivekparashar.19@gmail.com)

 lOMoARcPSD|21699291

MODULE-3

20. Discuss the present state of practices in requirement engineering. Suggest

few steps to improve the present state of practice.
21. Explain the importance of requirements. How many types of
requirements are possible and why ?
22. Discuss the term “requirements elicitation” ? Discuss any two techniques in
detail.
23. List out requirements elicitation techniques. Which one is most popular
and why ?
24. Illustrate the various activities of software project planning?
25. Describe any two software size estimation techniques.
26. A proposal is made to count the size of ‘C’ programs by number of
semicolons, except those occurring with literal strings. Discuss the
strengths and weaknesses to this size measure when compared with the
lines of code count.
27. Design a LOC counter for counting LOC automatically. Is it language
dependent? What are the limitations of such a counter?
28. Discuss various types of COCOMO mode. Explain the phase wise
distribution of effort.
29. Explain all the levels of COCOMO model. Assume that the size of an
organic software product has been estimated to be 32,000 lines of code.
Determine the effort required to developed the software product and the
nominal development time.
30. Using the basic COCOMO model, under all three operating modes,
determine the performance relation for the ratio of delivered source code
lines per person-month of effort. Determine the reasonableness of this
relation for several types of software projects.
MODULE-4
31. Discuss the objectives of software design. How do we transform an
informal design to a detailed design?
32. Do we design software when we “write” a program? What makes
software design different from coding?
33. Explain modularity? List the important properties of a modular system.
34. Define module coupling and explain different types of coupling.
35. Define module cohesion and explain different types of cohesion.
36. Discuss the objectives of modular software design. What are the effects
of module coupling and cohesion?
37. If a module has logical cohesion, what kind of coupling is this module
likely to have with others?
38. Discuss the problems that are likely to arise if two modules have high
coupling?
39. Discuss the problems are likely to arise if a module has low cohesion?

Downloaded by Vivek Parashar (vivekparashar.19@gmail.com)

 lOMoARcPSD|21699291

MODULE-5

40. Describe the various strategies of design. Which design strategy is most
popular and practical?
41.Define software metrics. Why do we really need metrics in software?
42. Discus the areas of applications of software metrics? What are the
problems during implementation of metrics in any organizations?
43. Discuss the various categories of software metrics? Discuss with the
help of suitable example.
44. Explain the Halstead theory of software science. Is it significant in
today’s scenario of component based software development?
45. Explain software quality? Discuss software quality attributes.
46. Discuss software quality standards? Illustrate their essence
as well as benefits.
47. Describe the McCall software quality model. How many product qualities
factors are defined and why?
48. Discuss the relationship between quality factors and quality criteria in
McCall’s software quality model.
49. Explain the Boehm software quality model with the help of a block
Diagram.
50. Describe software testing? Discuss the role of software testing during
software life cycle and why is it so difficult?
51. Discuss UML diagrams using banking system.
52. Differentiate structure oriented diagrams and object oriented diagrams.

SECTION- B

MODULE-1

1.Explain the need for software testing. Who should do the testing? What
should we test? Comment on this statement. Illustrate the importance of
testing
2. Defined the following terms:
(i) fault (ii) failure
(iii) bug (iv) mistake
3 . Explain the difference between
(i) Alpha testing & beta testing
(ii) Development & regression testing

Downloaded by Vivek Parashar (vivekparashar.19@gmail.com)

 lOMoARcPSD|21699291

(iii)Functional & structural testing

4. Discuss the limitation of testing. Why do we say that complete testing is
impossible? Briefly discuss the following

(i) Test case design, Test & Test suite

(ii) Verification & Validation
(iii)Alpha, beta & acceptance testing
5. Will exhaustive testing (even if possible for every small programs)
guarantee that the program is 100% correct? Why does software fail after it
has passed from acceptance testing? Explain.
6. Discuss the various kinds of functional testing? Describe any one in detail.
What is a software failure? Explain necessary and sufficient conditions for
software failure. Mere presence of faults means software failure. Is it true?
If not, explain through an example, a situation in which a failure will
definitely occur.
7. Explain the boundary value analysis testing techniques with the help of
an example. Explain the usefulness of decision table during testing. Is it
really effective? Justify your answer.

MODULE-2
8. Describe ISO9126 standards? What are the quality characteristics and
attributes? Compare the ISO9126 with McCall software quality model and
highlight few advantages of ISO9126.
9. Discuss the basic model of software reliability. How can it be calculated.
Assume that the initial failure intensity is 6 failures/CPU hr. The failure
intensity decay parameter is 0.02/failure. We assume that 45 failures
have been experienced. Calculate the current failure intensity.
10 . Give Halstead’s software science measure for:
(i) Program Length (ii) Program volume (iii) Program level (iv) Effort
(v) Language level

11. If some existing modules are to be re-used in building a new system,

which design strategy is used and why? What is the difference between a
flow chart and a structure chart?
12. Explain why it is important to use different notations to describe
software designs. List a few well-established function oriented software
design techniques.
13. Define the following terms: Objects, Message, Abstraction, Class,
Inheritance and Polymorphism. What is the relationship between abstract
data types and classes?
14.Compute the function point value for a project with the following
information domain characteristics.

Downloaded by Vivek Parashar (vivekparashar.19@gmail.com)

 lOMoARcPSD|21699291

Number of user inputs = 30

Number of user outputs = 42
Number of user enquiries = 08
Number of files = 07
Number of external interfaces = 6
Assume that all complexity adjustment values are moderate.

MODULE-3

15. Describe the various steps of requirements engineering. Are there other
characteristics of an SRS besides listed in IEEE SRS document that are
desirable ? List a few and describe why ?
16. Describe software requirements specification (SRS) ? List out the
advantages of SRS standards.Why is SRS known as the black box
specification of a system ?
17. State the model of a data dictionary and its contents. What are its
advantages ? List five desirable characteristics of a good SRS document.
18.Discuss the relative advantages of formal requirement specifications. List the
important issues, which an SRS must address.
19. Construct an example of an inconsistent (incomplete) SRS. Discuss the
organization of a SRS. List out some important issues of this organization.
20. Describe the term Software Development Life Cycle (SDLC)? Why is it
important to adhere to a life cycle model while developing a large software
product?
21. Describe software life cycle? Discuss the generic waterfall model. List the
advantages of using waterfall model instead of adhoc build and fix model.
MODULE-4

22. Discuss the prototyping model. What is the effect of designing a

prototype on the overall cost of the project? What are the advantages of
developing the prototype of a system?
23. Describe the type of situations where iterative enhancement model might
lead to difficulties. Compare iterative enhancement model and
evolutionary process model.
24. Sketch a neat diagram of spiral model of software life cycle. As we move
outward along with process flow path of the spiral model, what can we say
about software that is being developed or maintained.
25. How does “project risk” factor effect the spiral model of software
development. Describe win-win concept used in development model.
26. Describe software process? Why is it difficult to improve it? Describe the
characteristics of software contrasting it with the characteristics of
hardware.
27. Write down the major characteristics of a software. Illustrate with a

Downloaded by Vivek Parashar (vivekparashar.19@gmail.com)

 lOMoARcPSD|21699291

diagram that the software does not wear out. What are the components of a
software? Discuss how software differs from a program.
28. Discuss major areas of the applications of the software. Is software a
product or process? Justify your answer with example.
MODULE-5

29. Write short note on “status of development team” for the selection of a
life cycle model? Discuss the selection process parameters for a life cycle
model.
31. DescribeWhat is unified process? Explain various phases along with the
outcome of each phase. Describe the unified process work products after each
phase of unified process.
33. Describe the advantages of iterative approach over sequential approach?
Why is unified process called as iterative or incremental? Why do we feel that
characteristics of requirements play a very significant role in the selection of a
life cycle model?
34. Consider the problem of library management system and design the
following:
(i) Problem statement
(ii) Use case diagram
(iii) Use cases.
35.Explain why a many to many relationship is to be modeled as an associative
entity ? What are the linkages between data flow and E–R diagrams ? What is
the degree of a relationship ? Give an example of each of the relationship
degree. Explain the relationship between minimum cardinality and optional and
mandatory participation.
36. Explain all the symbols used in class and object diagrams. Draw a class and
object diagram for library management system.

37. Discuss all the symbols used in Use case diagrams. Draw a use case
diagram for Hotel management system. Assume suitable assumptions.

Section c
MODULE-1

1 A. Draw a DFD for borrowing a book in a library which is explained

below: “A borrower can borrow a book if it is available else he/she can
reserve for the book if he/she so wishes. He/she can borrow a maximum of
three books”.

Downloaded by Vivek Parashar (vivekparashar.19@gmail.com)

 lOMoARcPSD|21699291

B. Draw the E–R diagram for a hotel reception desk management. Explain why,
for large software systems development, is it recommended that prototypes
should be “throw-away” prototype ?
2 A. A department of computer science has usual resources and usual users
for these resources. A software is to be developed so that resources are
assigned without conflict. Draw a DFD specifying the above system.
B. Draw a DFD for result preparation automation system of B. Tech.
courses (or MCA program) of any university. Clearly describe the working
of the system. Also mention all assumptions made by you.
3. A. An airline reservation is an association between passengers, a flight,
and a seat. Select a few pertinent attributes for each of these entity types and
represent a reservation in an E–R diagram.
B. Comment on the statement: “The term throw-away prototype is
inappropriate in that these prototypes expand and enhance the knowledge
base that is retained and incorporated in the final prototype; therefore they
are not disposed of or thrown away at all.”
4. A. An application has the following:
10 low external inputs, 12 high external outputs, 20 low
internal logical files, 15 high external interface files, 12
average external inquiries, and a value of complexity
adjustment factor of 1.10.
What are the unadjusted and adjusted function point counts ?

B. Suppose that a project was estimated to be 400 KLOC. Calculate the effort
and development time for each of the three modes i.e., organic, semidetached
and embedded.
MODULE-2

5. A database system is to be developed. The effort has been estimated to

be 100 Persons-Months. Calculate the number of lines of code and
productivity in LOC/Person-Month.

6. The effort distribution for a 240 KLOC organic mode software

development project is: product design 12%, detailed design 24%, code
and unit test 36%, integrate and test 28%. How would the following
changes, from low to high, affect the phase distribution of effort and the
total effort: analyst capability, use of modern programming languages,
required reliability, requirements volatility?

7. Can we have inheritance without polymorphism? Discuss the reasons for

improvement using object-oriented design. Explain the design guidelines that
can be used to produce “good quality” classes or reusable classes.

Downloaded by Vivek Parashar (vivekparashar.19@gmail.com)

 lOMoARcPSD|21699291

8. List the points of a simplified design process. Discuss the differences

between object oriented and function oriented design. What documents should
be produced on completion of the design phase? Can a system ever be
completely “decoupled”? That is, can the degree of coupling be reduced so
much that there is no coupling between modules?
9. Discuss the problems with metrics data. Explain two methods for the
analysis of such data. Show why and how software metrics can improve the
software process. Enumerate the effect of metrics on software productivity.
Why does lines of code (LOC) not measure software nesting and control
structures?
MODULE-3

10. Several researchers in software metrics concentrate on data structure to

measure complexity. Is data structure a complexity or quality issue, or
both? Some experimental evidence suggests that the initial size estimate for a
project affects the nature and results of the project. Consider two
different managers charged with developing the same application. One
estimates that the size of the application will be 50,000 lines, while the
other estimates that it will be 100,000 lines. Discuss how these estimates
affect the project throughout its life cycle.

11. List the difference of CMM and ISO9001. Why is it suggested that
CMM is the better choice than ISO9001? Explain the significance of software
reliability engineering. Discuss the advantage of using any software standard for
software development? What are the various key process areas at defined level
in CMM? Describe activities associated with one key process area.

12. Discuss the relative merits of ISO9001 certification and the SEI CMM
based evaluation. Point out some of the shortcomings of the ISO9001
certification process as applied to the software industry.

13 .Consider a simple program to classify a triangle. Its inputs is a triple of

positive integers (say x, y, z) and the date type for input parameters ensures
that these will be integers greater than 0 and less than or equal to 100. The
program output may be one of the following words:
[Scalene; Isosceles; Equilateral; Not a triangle]
Design the boundary value test cases.

14 A. Consider the program for the determination of nature of roots of a

quadratic equation. Design the Robust test case and worst test cases for this
program.
B. Discuss the Black Box and White Box testing techniques in detail.

Downloaded by Vivek Parashar (vivekparashar.19@gmail.com)

 lOMoARcPSD|21699291

MODULE-4

15. Consider a program for the classification of a triangle. Its input is a triple of
positive integers (say a,b,c) from the interval [1,100]. The output may be
[Scalene, Isosceles, Equilateral, Not a triangle].Draw the flow graph & DD Path
graph. Also find the independent paths from the DD Path graph.
16. Consider the program given in Fig. 20 for the classification of a triangle. Its
input is a triple of positive integers (say a, b, c) from the interval [1,100]. The
output may be:[Scalene, Isosceles, Equilateral, Not a triangle, Invalid inputs].
Find all du-paths and identify those du-paths that are definition clear.
17 A. Why does software testing need extensive planning? Explain. What is
meant by test case design? Discuss its objectives and indicate the steps involved
in test case design.
B. Discuss cause effect graphing technique with an example.
18. Consider a program to determine whether a number is ‘odd’ or ‘even’
and print the message
NUMBER IS EVEN
Or
NUMBER IS ODD
The number may be any valid integer. Design boundary value and equivalence
class test cases.
19. Explain regression testing? Differentiate between regression and
development testing? What is the importance of regression test selection?
Discuss with help of examples. What are selective retest techniques? How are
they different from “retest-all” techniques?
20 Describe reverse engineering? Discuss levels of reverse engineering. What
are the appropriate reverse engineering tools? Discuss any two tools in detail.
What is re-engineering? Differentiate between re-engineering and new
development.
MODULE-5

21. Explain the concept of productivity? How is it related to effort. What is the
unit of effort. Differentiate between module and software component.
Distinguish between generic and customized software products. Which one has
larger share of market and why?
22.Write short note on “status of development team” for the selection of a
life cycle model?. Discuss the selection process parameters for a life cycle
model. What is unified process? Explain various phases along with the outcome
of each phase.
23 A.Discuss typical software risks. How staff turnover problem affects
software projects?What are risk management activities? Is it possible to
prioritize the risk?
B. It seems odd that cost and size estimates are developed during software

Downloaded by Vivek Parashar (vivekparashar.19@gmail.com)

 lOMoARcPSD|21699291

project planning-before detailed software requirements analysis or design

has been conducted. Why do we think this is done? Are there circumstances
when it should not be done?

24 Differentiate Software Engineering methods, tools and procedures. Write

about Real Time Systems. Who is called as the Stakeholder? What are the
characteristics of the software?
25 Discuss the various categories of software? What are the challenges in
software? What are the fundamental activities of a software process?
What are the umbrella activities of a software process?
26. For a University registration system Draw a neat class diagram ,
object diagram and use case diagram. Assume suitable data.

27. For a company data base of ABC Pvt. Ltd. Explain the functioning and
collaborations using collaboration diagram. Assume suitable data.
28. Assume the software for Railway reservation and train monitoring systems.
Assume suitable information. Draw the followings:
a. Activity diagrams
b. Sequence diagrams
c. Deployment diagram.

Downloaded by Vivek Parashar (vivekparashar.19@gmail.com)