Top 25 Software Engineering Interview Questions

[LATEST 2023]
Most Frequently Asked Basic and Advanced Software Engineering Interview
Questions with Detailed Answers. Prepare with This Comprehensive List of
Common Technical Software Engineer Interview Questions for Entry Level and
Senior Professionals:
As per IEEE, Software Engineering is the application of a systematic, disciplined and
quantifiable approach towards the development, operation, and maintenance of a
software product.

It means to apply a systematic and well-defined approach to the development of a

software product.

In this tutorial, we will cover the most commonly asked Software Engineer interview
questions along with the answers in simple terms for your easy understanding.

Most Popular Software Engineering Interview

Questions
Enlisted below are the most frequently asked Software Engineer Interview Questions
with answers.

Q #1) What is SDLC?

Answer: SDLC stands for Software Development Life Cycle. It defines the step by step
approach for the development of software. SDLC involves the following phases i.e.
Requirement Gathering, System Analysis, Design, Coding, Testing, Maintenance, and
Documentation.
Given below is the high-level representation of the various phases involved in
SDLC.
[image source ]
Q #2) What are the various models available in SDLC?
Answer: There are several models available in SDLC for efficiently carrying out
software development. Some of the models include the Waterfall model, V-Model, Agile
model, etc.
Q #3) Explain the term Baseline.
Answer: A baseline is a milestone on the project which is usually defined by the project
manager. Baselines are used to track the progress of the project from time to time to
assess the overall health of the project.
Q #4) What are the responsibilities of a Software Project Manager?
Answer: A Software Project Manager is responsible for driving the project towards
successful completion. It is the responsibility of the Software Project Manager to make
sure the entire team follows a systematic and well-defined approach towards the
development of software.
A software project manager is also responsible for the following tasks:
 Project planning
 Project status tracking
 Resource management
 Risk management
 Project delivery within time and budget.
Q #5) What is Cohesion?
Answer: Cohesion is the degree to which the elements of a module are inter-related to
one another. It is like an internal glue that binds the elements of a module together.
Good software has high levels of cohesion.
Q #6) What is Coupling?
Answer: Coupling is the degree of interdependence between the modules. Good
software has low levels of coupling.
Q#7) Explain the concept of Modularization.
Answer: Modularization is used to divide software into multiple components or
modules. Each module is worked upon by an independent development and testing
team. The final result would be to combine multiple modules into a single working
component.
Q #8) What is Software Configuration Management?
Answer: Software configuration management is the process of tracking and controlling
the changes that occur during the software development lifecycle. Any change made
during software development has to be tracked through a well-defined and controlled
process.
Configuration management ensures that any changes made during software
development are being controlled through a well-defined process.

Q #9) What are the various phases of SDLC?

Answer: The following are the most common phases of SDLC.
 Requirement Analysis
 Design
 Coding
 Testing
 Maintenance
Q #10) Provide examples of Project Management tools.
Answer: Given below are some of the most commonly used project management tools
that are available in the industry today.
 Gantt Chart
 Checklists
 Status Reports
 Histograms
 Microsoft Project
Recommended Read => Top Project Management Tools That You Should Know
Q #11) What are CASE tools?
Answer: CASE stands for Computer-Aided Software Engineering tools that are utilized
to support and accelerate the various activities of the Software Development Lifecycle.
Q #12) What is Black box testing?
Answer: Black box testing involves testing the application without the knowledge of the
internal structure or code implementation. Testers would only bother about the
functionality of the software in black box testing rather than data flow and code
execution in the back end.
Q #13) What is White box testing?
Answer: White box testing is testing the application with the knowledge of the internal
structure and code implementation. This testing is generally performed by the developer
who has written the code in the form of unit tests.
Q #14) What is a Feasibility Study?
Answer: A feasibility study is conducted on a software product to assess how practical
and beneficial is the development of the software product to the organization. Software
is analyzed thoroughly to understand the economic and technical aspects of a software
product to be developed.
Q #15) How can you measure Project execution?
Answer: Project execution status can be monitored using the following techniques.
 Status Reports
 Milestone checklists
 Activity Monitoring
Q #16) What are the Functional Requirements?
Answer: Functional requirements are the features that a developed software product is
expected to perform. For example, adding a payment option at an eCommerce website
will be a functional requirement.
Q #17) What are Non-Functional Requirements?
Answer: Non-functional requirements measure the usability of the application such as
User Interface look and feel, Security, Performance, Interoperability, Reliability, etc.
Q #18) What is the difference between Quality Assurance and Quality Control?
Answer: Quality Assurance is ensuring that the delivered software has the least
number of defects possible. Quality Control is the process of ensuring that the quality of
the product is maintained in the long run.
Quality Assurance is done by the testing team of the project while Quality Control is
usually done by a dedicated support team, who is responsible for the quality of the
product even if the product is under the maintenance phase of software engineering.

Also, Read => Quality Assurance Vs Quality Control

Q #19) What is the difference between Verification and Validation?
Answer: Verification is the process of ensuring that the product is built right, from a
process and standards perspective.
Validation is the process of ensuring that we build the right product, from a customer
perspective. Verification is a static testing methodology wherein the product is tested
without executing the code, while validation is a dynamic testing methodology.

Worth Reading => Complete Study of Verification and Validation

Q #20) Which SDLC model is the best to choose for a Software Product?
Answer: There are no rules as such stating which specific SDLC model has to be used
for a software product. It depends on the type of software project being built and the
organization’s policies & procedures.
Q #21) What do you mean by Software Scope?
Answer: Software scope is the list of features provided by the developed software.
Based on the scope of the software, estimations such as time allocation, budget and
resource allocation can be done.
Q #22) What is SRS?
Answer: SRS stands for Software Requirement Specification (SRS) document. It is a
document to capture all the functional and non-functional requirements of a product. Not
all SDLC models need to follow SRS documents, some models capture requirements in
the form of user stories, whereas some models in the form of excel sheets, etc.
Q #23) What is the SDLC model that you have used in your previous project?
Answer: The answer to this question depends on the experience of an interview
candidate. If the candidate answers the SDLC model to be the Waterfall model, then the
interviewer will start asking questions about the Waterfall model and if he answers it to
be Agile, then the interviewer will start asking terms related to Agile methodology such
as Scrum, Sprint, etc.
Q #24) Explain the Waterfall model in detail.
Answer: The waterfall model is a sequential model in which the next phase starts only
after the first phase is completed. For example, the testing phase will start only after
the development phase is complete, the maintenance phase will start only after the
testing phase is complete.
Below are the various phases involved in the waterfall model. Please note that the
number of phases and sequences of phases may vary from one project to another.
 Requirements
 Design
 Coding
 Testing
 Maintenance
a) Requirements: This is the phase where the system to be developed is documented
in the form of Software Requirement Specification (SRS) document. This is the most
important phase of SDLC as a clear understanding of requirements from the client will
reduce the rework in the following phases.
b) Design: This is the phase where the architecture of the system to be developed is
finalized. Architecture can be in the form of a high-level design or a low-level design.
Architecture must also include the hardware and software specifications of the system
to be developed.
c) Coding: This is the phase where the code for the system to be developed is
written. Unit Testing and Integration Testing must be performed by the developers at
this stage before deploying the code for testing.
d) Testing: This is the phase where the product developed is tested by an independent
testing team to validate if it meets the requirements in the Software Requirement
Specification (SRS). Defects raised at this phase need to be fixed before providing sign
off on the product.
e) Maintenance: This phase comes once the testing phase is complete. It takes care of
any production issues that may arise after the product is delivered to the customer. The
duration of the maintenance phase differs from project to project and one organization
to another.
Below is the diagram to depict the waterfall model in the form of phases.
Q #25) Explain V-Model in detail.
Answer: V-Model stands for the verification and validation model. V-model is an
addition to the waterfall model, in the sense that V-model is also a sequential model. In
V-model, each phase of development is associated with a corresponding testing phase.
The image given below depicts the various phases involved in V-model.
The left side of the model is the Software Development Lifecycle while the right side of
the model is Software Testing Lifecycle. As the phases form the shape of the letter ‘V’,
this model is called V-Model.

Explanation:
Within the V-Model, SDLC is to be interpreted from top to bottom, while STLC is to be
interpreted from the bottom to the top. Initially, requirements are gathered to document
the system to be developed as per the client requirements. The testing team develops
the system test plan based on the requirements.

Then comes the high-level design and the detailed level design phases where the
architecture of the system is prepared. The testing team prepares the Integration Test
plan in these phases. Once the coding is complete on SDLC, STLC will start from unit
testing, followed by integration testing and System testing.

Conclusion
We hope this article will help you crack any Software Engineer interview successfully.
  Software Engineering is the application of a systematic, disciplined and
quantifiable approach to the development, operation, and maintenance of
software.
 There are no hard and fast rules as such on the type of Software Engineering
interview questions asked by interviewers. It varies from organization to
organization and the type of role the interview is conducted for.
All the best for your software engineer interview!!

Software Engineering
Interview Questions
Introduction to Software Engineering Interview
Questions And Answers
So you have finally found your dream job in software Engineering but are wondering

how to crack the 2023 Software Engineering Interview and what could be the probable

Software Engineering Interview Questions. Every interview is different and the scope of a

job is different too. Keeping this in mind, we have designed the most common Software

Engineering Interview Questions and Answers to help you get success in your interview.

Below is the list of 2023 software Engineering Interview Questions and Answers, which

can be asked during an interview for fresher and experience. These top interview

questions are divided into two parts:

 Part 1 – software Engineering Interview Questions (Basic)

 Part 2 – software Engineering Interview Questions (Advanced)

Part 1 – Software Engineering Interview
Questions (Basic)
This first part covers basic interview questions and answers

1. What is Software Engineering?

Answer:

Software Engineering is a process of developing a software product in a well-defined

systematic approach. In other words, developing a software by using scientific principles,

methods, and procedures.

2. What is the need to learn Software Engineering

Concepts?
Answer:

Imagine a person, who is good at building a wall may not be good at constructing a

house. In a similar way, a person who can write programs does not have the knowledge

to develop and implement the software in a well-defined systematic approach. Hence,

there is a need for programmers to adhere to software engineering concepts such as

requirements gathering, planning, development, testing, and documentation.

3. What is SDLC OR Software Development Life Cycle?

Answer:

SDLC defines a set of guidelines to develop a software product. SDLC has different
phases namely: Gathering Requirements, Analysis, Planning, Development, Testing,

Implementation, Maintenance, and Documentation. The order of the phases mentioned

in SDLC may vary depending upon the model chosen to implement.

Let us move to the next Interview Questions.

4. What are the different types of models available in SDLC?

Answer:

Many models have been proposed, to carry out the software implementation efficiently.

Some of them include the Waterfall Model, Agile Model, Spiral Model, Iterative Model,

V-Model etc.

5. Explain the role of a Software Project Manager?

Answer:

This is the common Interview Questions asked in an interview. The project Manager is

responsible for driving the software project in a systematic approach. Some of the key

roles & responsibilities of a software project manager include project planning, tracking

the progress of the project, risk management, resource management, execution of

development activities, delivering the project under cost, time and quality constraints.
6. What is a Software Project Scope?
Answer:

A scope is utilized to outline the activities performed to design, develop and deliver a

software product. In other words, scope contains information on what project is

intended to deliver and what it does not intend to. The scope also outlines information

on what software product developed contains and what it does not contain.

7. What is Software Project Estimation?

Answer:

Project Estimation is a process utilized to calculate the development costs such as effort,

time, and resources required to deliver a project. Project Estimations are derived

through past project experiences or with the help of consulting experts or with the help

of standard predefined business formulas.

Let us move to the next software Engineering Interview Questions.

8. Explain Functional Points?

Answer:

Functional points are used to measure the size of the software product. In some

businesses, scenarios play a key role in tracking and estimating project delivery.
9. What is a Baseline?
Answer:

Baselines are put forth by the project managers to track the overall project delivery.

Baselines are usually placed to track the overall tasks listed under a phase or stage.

Baselines help project managers to track and monitor the overall execution of a project.

10. What is Software Configuration Management?

Answer:

Software Configuration Management helps users to track the overall changes made

in software product delivery. Updates or changes made to the software are tracked in

terms of development and requirements gathering.

Let us move to the next software Engineering Interview Questions.

11. What is Change Control?

Answer:

Change control tracks the changes made in software to ensure consistency and updates

are incorporated as per the enterprise standards.

12. Mention few project management tools?

Answer:

Many project management tools are utilized as per the enterprise standards some of
them include: Gantt Charts, PERT Charts, Milestone Checklists, Histograms, MS project,

Status reports, etc.

13. What is a Software requirement?

Answer:

Requirements play a key role in providing a detailed description of the software product

being developed. Software requirements help the developers and other support teams

associated with project delivery, to understand the proposed target system and their

expectations on it.

Part 2 – Software Engineering Interview

Questions (Advanced)
Let us now have a look at the advanced software Engineering Interview Questions.

14. Explain the Feasibility Study?

Answer:

Feasibility Study is performed to assess the beneficial and practical attributes of a

software development Thorough analysis is performed by an organization with the help

of feasibility study to understand the economic, operational and technical aspects

involved in a software project delivery.

 Economic: Economic study involves costs related to resource management, training

costs, tools utilized, and project estimation costs

  Technical: Technical study helps the business to analyze the technical aspects involved

in software delivery such as machines, operating systems, knowledge, and skills of

resource allocated, tools utilized, and training.

 Operational: Operational study help business to study the change management and

issues involved depending on the project needs.

15. What are functional and non-functional requirements?

Answer:

Functional requirements are utilized to specify the functional features as per the

business requirements. For Example, adding a payment option to buy content from a

website. Whereas non-functional requirements provide insights into security,

performance, user interface, interoperability costs, etc.

16. What are Software Metrics?

Answer:

Metrics are utilized to guide the software product delivery as per the business standards.

Metrics can also be used to measure few features of software product delivery. Metrics

are divided into requirement metrics, product metrics, performance metrics, and process

metrics.

Let us move to the next software Engineering Interview Questions.

17. What is Modularization?
Answer:

Modularization divides the software system tasks in multiple modules. These modules

are independent to other modules and tasks invoked in each module are executed

independently.

18. Explain Concurrency and how is it achieved during the

software product delivery?
Answer:

This is the advanced software Engineering Interview Questions asked in an interview.

Concurrency is a process of executing multiple events or tasks simultaneously.

Concurrency can be achieved with the help of modules, events, and tasks associated

with the software project delivery.

19. What is Cohesion?

Answer:

Cohesion is utilized to measure the intra-dependability among various attributes

defined in a module.
20. What is coupling?
Answer:

Coupling is utilized to measure the inter-dependability of various elements defined in a

module.

21. Mention a few software analysis & Design tools?

Answer:

Some of the key software analysis & design tools are Data flow Diagrams (DFD),

Structured Charts, Data Dictionary, UML (Unified Modeling Languages) diagrams, ER

(Entity Relationship) Diagrams etc.

Let us move to the next software Engineering Interview Questions.

22. What is DFD Level 0?

Answer:

DFD (Data Flow Diagrams) Level 0 depict the entire data flow along with all abstract

details within a software information system. This type of DFD is also known as Context

level DFD.

23. What is Data Dictionary?

Answer:

A data dictionary is also known as metadata. Data Dictionary is utilized to capture the
information related to naming conventions of objects and files utilized in the software

project.

24. What is black box testing and white box testing?

Answer:

 Black Box Testing: Black box testing is performed to validate the outputs along with

valid inputs given. But, it does not test the implementation part of the program.

 White Box Testing: White Box testing is performed to validate the inputs, outputs and

program implementation involved in its execution.

Let us move to the next software Engineering Interview Questions.

25. What are the various types of software maintenance?

Answer:

Maintenance types are corrective, adaptive, perfective and preventive.

 Corrective: This type of maintenance is used to remove the errors spotted by business

users.

 Adaptive: This maintenance activity is performed to check the changes made in the

hardware and software environment.

 Perfective: This type of maintenance is used to implement changes in existing or new

user requirements
  Preventive: This maintenance activity is performed to avoid any issues in future

implementations.

26. Explain CASE tools?

Answer:

CASE (Computer-Aided Software Engineering tools) are utilized to implement, support,

and accelerate various SDLC activities involved in a software project.

SOFTWARE ENGINEERING Question Bank

Department of Computer Science and Engineering
SOFTWARE ENGINEERING
Question Bank
UNIT I - SOFTWARE PROCESS
PART - A (2 Marks)
1. Define Software Engineering.
2. What is meant by Software engineering paradigm?
3. What are the Advantages of incremental model?
4. Write any two characteristics of software as a product.
5. Identify in which phase of the software life cycle the following documents are
delivered.
i) Architectural design
ii) Test plan
iii) Cost estimate
iv) Source code document
6. Which process model leads to software reuse? Why?
7. What are the various activities in WINWIN Spiral Model?
8. What are the various elements that a computer based system makes use of?
9. Give at least two reasons for prototyping is problematic.
10. Mention the Advantage and Disadvantage of waterfall model.
11. Distinguish between process and methods.
12. Differentiate System and Computer based System.
13. Define software process. State the important features of a process.
14. Distinguish between verification & validation.
15. Define System Modeling.
16. What are the four types of changes are encountered during the support
phase?
17. State the System Engineering Hierarchy.
18. Mention some of the factors to be considered during System Modeling.
19. Define Verification &Validation.
20. What are the phases encompassed in the RAD model?
21. List the task regions in the spiral model.

PART- B (16 Marks)

1. (i) What are the major differences between system engineering and software
engineering? State
explains the stages that distinguish the two. [8]
(ii)Explain with two examples of software development projects would be amenable
to
evolutionary prototyping. Why is evolutionary prototyping suitable in these cases? [8]
2. Explain Water fall Model. What are the problems that are sometimes encountered
when the waterfall model
is applied? [16]

3. (i) Which is more important-the product or process? Justify your answer. [8]

(ii) With suitable illustration explain SPIRAL model evolutionary software

development. [8]

4. (i) Explain the Evaltionary and Incremental Model. What are the Advantages and
Disadvantages? [8]
(ii) Write a short notes an System engineering and Computer based System. [8]

5. Explain System Engineering hierarchy.What are the restraining factors to construct

a system
model? [16]

6. (i) Explain Component Based Development model in detail. [8]

(ii) How do you differentiate software engineering from system engineering? [8]
7. Explain in detail the following s/w process models with a neat diagram.
i) Evolutionary process model. [8]
ii) Incremental Process model. [8]

8. Explain the spiral model? What is the task region in the spiral model? How does the
customer wins by
getting the system or product that satisfy the majority of the customer’s needs and the
developer wins by
working to realistic and achievable budgets and deadline? [16]

9. What are the necessities of Life cycle model? Elaborate on the various issues of
Software life cycle. [16]

10. (i) How does system engineering differ from software engineering? Also write
brief notes on computer
based system and system engineering hierarchy. [8]

(ii) Differentiate product engineering and business engineering overview [8]

11. Explain the process model that combines the element of waterfall and iterative
fashion. [16]

12. Explain briefly about the following (i) business process engineering (ii) product
engineering
13.Explain briefly about the following (i) Computer based system(ii) System
engineering process

UNIT II - SOFTWARE REQUIREMENTS

PART-A (2 Marks)
1. What is requirement engineering?
2. What is meant by feasibility study?
3. What is meant by requirement validation?
4. What is meant by Requirement management?
5. What is meant by software prototyping?
6. Mention any two non-functional requirements on software to be developed.
7. Differentiate data flow diagram and state transition diagram.
8. Define cardinality and Modality of a relation.
9. Compare evolutionary and throw away prototyping?
10. Define the term product and process in software engineering?
11. List out the elements of analysis model?
12. What are all the information in data dictionary?
13. Why modularity is important in data dictionary?
14. Specify at least four questionnaire which supports to select the prototyping
approach.
15. What is known as SRS review? How is it conducted?
16. Distinguish between expected requirements and excited requirements.
17. What is meant by software prototyping?
18. What are the non-functional requirements of software?
19. What is data dictionary? How is it used in software engineering?
20. What is the role of data dictionary?
21. What is meant by Information flow Continuity?
22. Draw a DFD & CFD of a test monitoring system for Gas Turbine
23. Define Behavioral Modeling.
24. Draw the Context level DFD for the Safe home Software.
25. Define Data dictionary.
26. Define Process Specification.
27. What does data dictionary contains?
28. What is meant by Throw away Prototyping?
29. Why is it so difficult to gain a clear understanding of what the customer wants?
30. Create a data dictionary that provides with a precise definition of telephone
number, it should indicate,
where and how this data item is used and supplementary information that is relevant
to it?
31. What is the purpose of domain analysis?
32. What is the major distinction between user requirements and system
requirements?
33. What is QFD?
34. What is ERD?
35. What is DFD?
36. What are the problems makes elicitation difficult?
37. Why requirements elicitation process is difficult?
PART-B (16 Marks)
1. Explain software prototyping? What are the various prototyping methods and tools?
[16]

2. (i) Why is traceability an important aspect of requirement management? Why

context system models are
useful for requirements validation? [8]
(ii) What is requirement engineering? State its process and explain requirements
elicitation problem. [8]

3. Explain with example diagram the functional and behavioral modeling. How do we
model the software’s
reaction to some external event? [16]

4. (i) How to select the appropriate prototyping approach? Explain. [8]

(ii) Explain about the cardinality and modality with suitable example. [8]
5. Explain in detail about all modeling technique in software requirements. [16]

6. (i) Explain about rapid prototyping techniques. [8]

(ii) Differentiate functional and nonfunctional requirements. [8]

7. Why customer iteration is difficult process? Explain one formal procedure used for
customer interaction.
8. Draw an ER and DFD diagram for university information System. [16]

9. (i) Describe the primary difference between structured analysis and object oriented
analysis. [6]
(ii) Write a detailed note on scenario based modeling. [10]

10. (i) Compare functional and behavioral models. [4]

(ii) With a suitable diagram explain the elements of the analysis model [4]
(iii) With an example explain about DFD. [8]

11. (i) Differentiate functional and non functional requirements and explain. [8]

(ii) Why the customer interaction is a difficult process? Explain one formal procedure
used for
customer interaction. [8]

12. Draw an E-R diagram for university information system. Specify atleast four
cardinality and
modality relationships in this. [8]

13. (i) Explain the feasibility studies. What are the outcomes? Does it have either
implicit or explicit effects on software requirement collection? [8]

(ii) What is the prototyping technique? How prototype models are prepared for a
software process?
Discuss.

14. (i) Discuss in detail the FAST method of Requirement elicitation with an example.
[4]
(ii)What is software specification? [4]

(iii)Write short notes on data modeling? [4]

(iv)Discuss in detail the basic structure of analysis model. [4]

15. (i)Explain about the cardinality and modality with suitable example. [4]

(ii) What is Data dictionary? And explain data Modeling. [4]

(ii) What is the use of context diagram? Draw a Level-1 DFD and STD for
photocopier software.

UNIT III- DESIGN CONCEPTS AND PRINCIPLES

PART- A (2 Marks)
1. What are the common characteristics of design methods?
2. What are the different levels of abstraction?
3. What are the criteria for an effective modular system?
4. What are the elements of design model?
5. How the Architecture Design can be represented?
6. Define design process.
 7. List the principles of a software design.
8. What is the benefit of modular design?
9. What is a cohesive module?
10. What are the different types of Cohesion?
11. What is coupling?
12. What are the various types of coupling?
13. What are the common activities in design process?
14. What are the benefits of horizontal partitioning?
15. What is vertical partitioning?
16. What are the advantages of vertical partitioning?
17. What are the various elements of data design?
18. List the guidelines for data design.
19. Name the commonly used architectural styles.
20. What is Transform mapping?
21. Define real time system.
22. Define real time Executives.
23. Define Baseline.
24. What is meant by fan-in, fan-out?

2. PART- B (16 Marks)

1. Explain the fundamental software design concepts in detail. [16]

2. Explain the following

(i) SCM repository [8]
(ii) SCM process [8]

3. (i) Draw a translating diagram for analysis model into a software design. Brief
about each
translations. [8]

(ii) Give a complete template for documentation design specification. [8]

4. (i) How interrupts are handled in real time system? Explain. [8]
(ii) Explain in detail about the real time systems. . [8]

5. (i)Define the concept of cohesion and coupling. State the difference. [4]
(ii)Briefly explain the use of global variables in context of coupling cohesion? [4]
(iii)What are different types of architectural styles exist for software and explain any
one software
architecture.

6. What is transform mapping? Explain the process with an illustration. What is its
strength and weakness?

7. i) Explain about the various design concepts considered during design? [8]
ii) Write short notes on user interface design process? [8]

8. What are the different types of architectural styles exist for software and explain
any one software architecture in detail. [16]

9. i) Explain data architectural and procedural design for a software. [8]

ii) Describe the design procedure for data acquisition system. [8]

10. Describe decomposition levels of abstraction and modularity concepts in

softwareDesign. [16]

11. i) Discuss in detail about the design process in software development process. [8]

ii) Justify “Design is not coding and coding is not design”. [8]

12. i) Explain in detail about the characteristics and criteria for a good design. [8]
ii) Describe the golden rules for interface design. [4]
(iii) What is the design document? [4]

UNIT IV- TESTING

PART- A (2 Marks)
1. What is a Real time system?
2. What is SCM?
3. What is SCI?
4. Define software testing?
5. Define Smoke Testing?
6. What are the objectives of testing?
7. Define White Box Testing.
8. What are the two levels of testing?
9. What are the various testing activities?
10. Write short note on black box testing.
11. What is equivalence partitioning?
12. What is Regression Testing?
13. What is a boundary value analysis?
14. What are the reasons behind to perform white box
testing?
15. What is cyclomatic complexity?
16. How to compute the cyclomatic complexity?
17. Distinguish between verification and validation.
18. What are the various testing strategies for
conventional software?
19. Write about drivers and stubs.
20. What are the approaches of integration testing?
21. What are the advantages and disadvantages of bigbang?
22. What are the benefits of smoke testing?
23. What are the conditions exists after performing
validation testing?
24. Distinguish between alpha and beta testing.
25. What are the various types of system testing?
26. What is BRO testing?
27. List out the data structure errors identified during unit
testing.
28. What is called as glass box testing? What is the
objective of this?
29. State the objectives and guidelines for debugging.
30. What do you mean by test case management?
31. What are the roles of cyclomatic complexity value in
software resting?
32. What is the need for cyclomatic complexity?

PART- B (16 Marks)

1. i) Explain the testing objectives and its principles. [8]

(ii) Explain the basis path testing in detail. [8]

2. (i) What is the need for software maintanance and maintenance report. [8]
(ii) What are the attributes of the good test? Explain the test case design. [8]

3. (i) What are all formulas for cyclomatic complexity? Calculate cyclomatic
complexity for greatest of all
these numbers. [8]

(ii) How the RST condition is verified in black box testing? Explain with example. [8]

4. (i) What is the necessity of unit testing? Write down all unit test considerations. [8]
(ii) Explain about system testing. [8]

5. Write a note of
(i) Black box testing. [4]
(ii) Regression testing. [4]
(iii) White box testing [4]
(iv) Integration testing. [4]

6. Why is it so important to include boundary values in your black-box test data?

Illustrate with examples
in which a test suite developed using black box techniques might give the impression
that ‘everything is
OK”, while a test suite developed with whit box testing techniques (for example,
branch coverage) might
uncover a fault and vice versa. [16]

7. (i) Discuss the differences between black box and white box testing . [8]

(ii) Explain the different integration testing approaches. [8]

8. (i)Discuss how these testing models may be used together to test a program
schedule. [4]

(ii) What do you mean by system testing? Explain in detail [4]

(iii) Explain boundary value analysis. [4]

(iv) Justify the importance of testing process [4]

9. (i)Discuss in detail about alpha and beta testing. [8]

(ii)What do you mean by integration testing? Explain their outcomes. [8]

10. Explain the integration testing process and system testing process and discuss their
outcomes:
(i) What do you mean by system testing? Give a case study of a system testing
for operating system? [8]
(ii). What do you mean by boundary value analysis? Give two examples of
boundary value testing. [8]

11. Explain automated testing tools. How test cases are generated? Discuss when to
stop testing? What is performance testing? Describe. [16]

13. What are the various testing strategies to software testing? Discuss them briefly.
[16]

14.( i) Describe the testing objectives and its principles. [8]

(ii) Explain the basis path testing in detail. [8]

15. (i) What is need for software maintenance and maintenance report. [8]
(ii) What are the attributes of a good test. Explain the test case design. [8]

16. Explain the various types of black-box testing methods.

17. (i) Explain about system testing. [6]

(ii) What is the necessity of unit testing? Write down all unit test considerations. [10]

18. (i) What are all the formulas for cyclomatic complexity?Calculate cyclamatic
complexity for
greatest of three numbers? [8]

(ii) How the RST (Reflexive, Symmetric, and Transitivity) is related to black box
testing? [8]

20 i) Why Unit testing is important? Explain the concept of unit testing in detail.
ii) Write a note an regression testing.
 UNIT V- SOFTWARE PROJECT MANAGEMENT
PART- A (2 Marks)
1. What is meant by software project management?
2. What is meant by software management?
3. Define debugging.
4. What are the common approaches in debugging?
5. Write about the types of project plan.
6. Define measure.
7. Define metrics.
8. What are the types of metrics?
9. What are the advantages and disadvantages of size measure?
10. Write short note on the various estimation techniques.
11. What is the Objective of Formal Technical Reviews?
12. What is COCOMO model?
13. Give the procedure of the Delphi method.
14. What is the purpose of timeline chart?
15. What is EVA?
16. What are the metrics computed during error tracking activity?
17. Why software change occurs?
18. Write about software change strategies.
19. Define CASE Tools.
20. What is software maintenance?
21. Define maintenance.
22. What are the types of software maintenance?
23. What is architectural evolution?
24. How the CASE tools are classified?
25. What are the types of static testing tools?

2. PART- B (16 Marks)

1. i) Explain about CASE repository functions in detail. [6]
(ii) Discuss on the various method encountered in cost estimation.

2. (i) Explain in detail about Delphi technique. [6]

(ii) Discuss in detail about software software evaluation. 10]

3. (i)What are the different activities in project planning. 12]

(ii)What is error tracking? Discuss. [4]
4. (i) Brief about 3D function point measures. [8]
(ii) How to measure quality and defect removal efficiency. [8]

5. (i)How to compute a task set selector value for a project? [8]

(ii)Brief about taxonomy of case tools (at least eight) [8]

6. (i) What are the upper and lower CASE tools? What is the purpose of upper-
CASE tools? [6]
(ii) Explain in detail the COCOMO model. [10]

7. (i) Describe about software equation. [8]

(ii) Describe about the constructive cost model in detail. [8]

8. (i) Explain in detail about the maintenance process [8]

(ii) Discuss in detail about software evolution. [8]

9. Describe two metrics which are used to measure the software in detail.
Discuss clearly the advantages and disadvantages of these metrics. [16]

10. (i) Justify the statement “Software maintenance is costlier”. [8]

(ii)Discuss the concept of software maintenance process. [8]

11. (i) Brief about 3D function point measures. [8]

(ii) How to measure quality and defect removal efficiency (DRE). [8]

12. (i) How to compute Task Set Selector(TSS) value? Explain. [8]

(ii) Brief about taxonomy of CASE tools (at least eight) [8]

13. i) Explain the scheduling of software project. [8]

ii) Explain task network. Construct a schematic task network for concept
development project.

14. i) How is earned value computed to assess the progress? [8]

ii) Explain the Constructive Cost model. [8]

15. Software project scheduling does not differ from scheduling of any other
multitask engineering Projects. Discuss.

16. i) Explain the CASE repository functions in detail.

ii) Explain the various method encountered in cost estimation.