Software Engineering Question Bank

1. Generic View Of Software Engineering.

A generic view of software engineering involves a systematic approach to developing software

products. It encompasses a set of principles, methods, and tools that help in designing,
developing, testing, and maintaining software systems. Software engineering aims to produce
high-quality software products that meet the required specifications, are delivered on time,
and are within budget.

2. Process Models- Waterfall model, Incremental, Evolutionary process models- Prototype,

Spiral And Concurrent Development Model Agile Development Agility and Agile Process
model

There are several process models in software engineering, including:

 Waterfall model: A linear approach where each phase is completed before moving on
to the next one.
 Incremental model: A iterative approach where the software is developed in
increments, with each increment building on the previous one.
 Evolutionary process models:
 Prototype model: A model where a prototype is developed and refined based
on user feedback.
 Spiral model: A risk-driven approach that combines elements of the waterfall
and prototype models.
 Concurrent Development Model: A model where multiple activities are performed
concurrently to reduce the overall development time.
 Agile Development: An iterative and incremental approach that focuses on flexibility
and customer satisfaction. Agile process models include Scrum, Kanban, and Lean software
development.

3. Explain SDLC Lifecycle.

The Software Development Life Cycle (SDLC) is a framework that outlines the stages involved
in developing software. The SDLC lifecycle typically includes:

1. Planning: Defining project scope, goals, and timelines.

2. Requirements gathering: Collecting and documenting user requirements.
3. Analysis: Breaking down requirements into smaller, manageable parts.
4. Design: Creating a detailed design of the software system.
5. Implementation: Writing the code and developing the software.
6. Testing: Verifying that the software meets the required specifications.
7. Deployment: Releasing the software to the end-users.
8. Maintenance: Updating, fixing, and enhancing the software over time.
 4. Explain the 4P's in software engineering.

The 4P's in software engineering are:

1. People: The individuals involved in the software development process, including

developers, testers, project managers, and users.
2. Product: The software system being developed, including its features, functionality,
and quality attributes.
3. Process: The set of activities, methods, and tools used to develop the software system.
4. Project: The overall endeavor of developing the software system, including the scope,
schedule, budget, and resources.

5. Explain Prototype model and compare it with Waterfall process model

The Prototype model is a software development process model that involves creating a
working model of the software system to demonstrate its features and functionality. The
prototype is refined based on user feedback, and the final product is developed iteratively.

In contrast, the Waterfall model is a linear approach where each phase is completed before
moving on to the next one. There is no feedback loop, and changes are difficult to incorporate
once the development process has started.

6. Importance of Team Management Planning a Software Project Scope and Feasibility.

Team management is crucial in software project planning as it ensures that the project is
completed on time, within budget, and to the required quality standards. Effective team
management involves:

 Defining project scope and feasibility

 Identifying and allocating tasks to team members
 Establishing communication channels and collaboration tools
 Monitoring progress and addressing issues promptly
 Ensuring that the team has the necessary skills and resources

7. What is SRS document.

A Software Requirements Specification (SRS) document is a formal document that outlines the
functional and non-functional requirements of a software system. It provides a detailed
description of the software's features, functionality, and performance expectations. The SRS
document serves as a guide for the development team and ensures that the software meets
the user's requirements.

8. Software Projects Vs other types of Projects

Software projects differ from other types of projects in several ways:

 Software projects involve intangible products, whereas other projects involve physical
products.
 Software projects require a high degree of creativity and innovation.
 Software projects are often iterative and incremental, with frequent changes and
updates.
 Software projects require specialized skills and knowledge, such as programming
languages and software development methodologies.

9. Contract Management and Technical Project Management

Contract management involves managing the contractual agreements between the

organization and its stakeholders, including vendors, suppliers, and customers. Technical
project management involves managing the technical aspects of a software project, including
the development process, resources, and timelines.

10. W5HH Principle.

The W5HH principle is a framework for problem-solving and decision-making that involves
asking the following questions:

 Who: Who is involved in the problem or decision?

 What: What is the problem or decision?
 When: When does the problem or decision need to be addressed?
 Where: Where is the problem or decision located?
 Why: Why is the problem or decision important?
 How: How can the problem be solved or the decision be made?
 How much: How much will it cost to solve the problem or make the decision?

11. Software Projects Vs other types of Projects

Software projects differ from other types of projects in several ways:

 Software projects involve intangible products, whereas other projects involve physical
products.
 Software projects require a high degree of creativity and innovation.
 Software projects are often iterative and incremental, with frequent changes and
updates.
 Software projects require specialized skills and knowledge, such as programming
languages and software development methodologies.

12. Management Planning a Software Project Scope and Feasibility,

Management planning involves defining the project scope, goals, and timelines. It also
involves identifying the resources, budget, and risks associated with the project. Feasibility
analysis is conducted to determine whether the project is viable and worth pursuing.
 13. Effort Estimation, Schedule and staffing

Effort estimation involves estimating the time and resources required to complete a task or
project. Scheduling involves creating a timeline for the project, including milestones and
deadlines. Staffing involves allocating the necessary personnel to complete the project tasks.

14. Quality Planning

Quality planning involves defining the quality objectives, standards, and procedures for a
software project. It includes identifying the quality metrics, testing strategies, and defect
management processes.

15. Risk management- identification, assessment, control, project monitoring plan, Detailed
Scheduling

Risk management involves identifying, assessing, and mitigating risks that could impact the
software project. It includes developing a risk management plan, identifying risk mitigation
strategies, and monitoring the project for potential risks.

16. control, project monitoring plan, Detailed Scheduling

Control involves monitoring and controlling the project progress, including tracking the
project schedule, budget, and quality. Project monitoring involves regularly reviewing the
project status and identifying areas for improvement. Detailed scheduling involves creating a
detailed project schedule, including task dependencies and timelines.

17. Generic View Of Software Engineering

A generic view of software engineering involves a systematic approach to developing software

products. It encompasses a set of principles, methods, and tools that help in designing,
developing, testing, and maintaining software systems.

18. Requirement Analysis and Requirement Elicitation

Requirement analysis involves analyzing the user requirements to identify the functional and
non-functional requirements of the software system. Requirement elicitation involves
gathering the requirements from the stakeholders through various techniques, such as
interviews, surveys, and focus groups.

19. Understanding the Requirement

Understanding the requirement involves interpreting and clarifying the user requirements to
ensure that the software system meets the user's expectations. It involves identifying the
ambiguities, inconsistencies, and contradictions in the requirements and resolving them
through negotiation and compromise.

20. Other process models of Agile Development and Tools

Other process models of Agile development include:

 Scrum: A framework that emphasizes teamwork, accountability, and iterative progress.

 Kanban: A visual system for managing work, emphasizing continuous flow and
limiting work in progress.
 Lean software development: A methodology that aims to minimize waste, maximize
value, and optimize the development process.
 Extreme Programming (XP): A methodology that emphasizes technical practices, such
as pair programming, continuous integration, and refactoring.

Agile development tools include:

 Jira: A project management tool for tracking issues, projects, and workflows.
 Trello: A visual project management tool for organizing tasks and workflows.
 Asana: A work management platform for tracking tasks, projects, and workflows.
 GitHub: A web-based platform for version control and collaboration.