UNIT 1

SHORT QUESTIONS
 Define software engineering?
Software engineering is the systematic approach to designing, developing, testing,
and maintaining software efficiently.

  Differentiate between program and software.

A program is a single set of instructions, while software is a collection of programs,
documentation, and data that performs a task.

  What is SDLC?
Software Development Life Cycle (SDLC) is a structured process that defines the
stages of software development from planning to maintenance.

  List some of the software development process models.

Common software development models include Waterfall, Agile, Spiral, V-Model, and
Prototype Model.

  Define Feasibility Study.

A feasibility study evaluates the practicality, cost, and benefits of a proposed software
project before development begins.

LONG QUESTIONS
1 ITERATION MODEL AND WATER FALL MODEL

Waterfall Model: A linear software development model where each phase

(requirement, design, implementation, testing, deployment, maintenance) is
completed before moving to the next.

✅ Advantage: Clear structure and well-defined phases.

❌ Disadvantage: Rigid, making it difficult to accommodate changes.

Iteration Model: A cyclic approach where development is done in repeated cycles

(iterations), allowing refinement and feedback at each stage.

✅ Advantage: Allows flexibility and continuous improvements.

❌ Disadvantage: Can lead to scope creep and extended timelines.

2 REQUIREMENT ENGINEERING PROCESS AND ITS COMPONENTS

Requirement Engineering Process: It is the process of gathering, analyzing,
documenting, and managing software requirements.

Components:

Elicitation – Collecting requirements from stakeholders.

Analysis – Refining and validating gathered requirements.

Specification – Documenting requirements formally.

Validation – Ensuring correctness and feasibility.

Management – Handling changes and maintaining traceability.

3 COST AND BENEFITS ANALYSIS IN REQUIREMENT ENGINEERING

PROCESS

Cost and Benefit Analysis (CBA) in IT

Costs:

Direct Costs – Hardware, software, and maintenance.

Indirect Costs – Training, infrastructure, and support.

Operational Costs – Cloud services, IT staff salaries.

Benefits:

Tangible Benefits – Cost savings, increased revenue.

Intangible Benefits – Better security, customer satisfaction.

Competitive Advantage – Faster processes, market growth.

UNIT 2
SHORT QUESTIONS
 Mention the characteristics of a good requirements and validation technique?
Good requirements should be clear, complete, consistent, feasible, testable, and
relevant, while validation ensures correctness and completeness.
  Define Requirement Engineering?
Requirement Engineering is the process of gathering, analyzing, documenting, and
managing software requirements to meet user needs.

  Discuss about Stakeholder?

A stakeholder is any individual, group, or organization affected by or involved in a
project, such as users, clients, and developers.

  What is stakeholder analysis?

Stakeholder analysis identifies, categorizes, and evaluates stakeholders based on their
interest, influence, and impact on a project.

  What is the planning phase?

The planning phase defines the project scope, objectives, resources, schedule, and
risks to ensure a structured development process.

  What are validation techniques?

Validation techniques include inspections, reviews, walkthroughs, prototyping, and
testing to ensure software meets requirements.

LONG QUESTIONS
1 REQUIREMENT SPECIFICATION,MANAGEMENT PROCESS AND DISCOVERING
TECHNIQUES

Requirement Specification: A structured document that defines system

functionalities, constraints, and expectations to ensure clarity in development.

Requirement Management Process: Involves gathering, analyzing, documenting,

tracking, and updating requirements throughout the project lifecycle.

Requirement Discovery Techniques:

Interviews – Direct discussions with stakeholders.

Surveys & Questionnaires – Collecting structured feedback.

Prototyping – Creating mock-ups for validation.

2 SRS

Software Requirement Specification (SRS)

SRS is a formal document that defines the functional and non-
functional requirements of a software system.

Key Components:
Introduction – Purpose, scope, and definitions.

Overall Description – Product perspective, functions, and constraints.

Specific Requirements – Functional, non-functional, and interface

requirements.

Importance:

Ensures clarity between stakeholders.

Serves as a baseline for development and testing.

Reduces ambiguity and project risks.

3 TRACEABILITY

Traceability refers to the ability to track and link software

requirements throughout the development lifecycle to ensure
all requirements are met.

Types of Traceability:

Forward Traceability – Links requirements to design, implementation, and

testing.

Backward Traceability – Ensures that each implementation and test case

traces back to a requirement.

Bidirectional Traceability – Maintains both forward and backward

traceability for complete tracking

4 REQUIREMENT CHANGE MANAGEMENT

Requirement Change Management is the process of handling modifications to

requirements throughout the software development lifecycle while minimizing risks
and ensuring project stability.

Change Identification – Recognizing the need for a change.

Impact Analysis – Assessing effects on cost, timeline, and functionality.

Approval & Prioritization – Evaluating and deciding whether to implement

the change.

Implementation & Tracking – Applying changes while maintaining

traceability.
Verification & Validation – Ensuring the change meets requirements without
introducing defects.

UNIT 3
SHORT QUESTIONS
 Define class.
A class is a blueprint or template for creating objects, defining attributes and
behaviors in object-oriented programming.

  Define object.
An object is an instance of a class that contains data (attributes) and methods
(functions) to perform operations.

  What is data modeling?

Data modeling is the process of structuring and organizing data using diagrams and
rules to define relationships and constraints.

  What is inter-organizational communication?

Inter-organizational communication is the exchange of information, resources, and
collaboration between different organizations for business or strategic goals.

  Define cohesion.
Cohesion refers to the degree to which the elements of a module or class are related
and work together to perform a single task effectively.

LONG QUESTIONS
1 Architectural Styles in Software Engineering

Layered Architecture – Organizes software into layers (e.g., UI, Business,

Data) for modularity.

Client-Server Architecture – Divides system into clients (users) and servers

(service providers).

Microservices Architecture – Uses independent, small services

communicating via APIs.

Event-Driven Architecture – Components react to events for asynchronous

processing.

Model-View-Controller (MVC) – Separates application into Model (data),

View (UI), and Controller (logic).
2 Architectural Design Principles

Modularity – Divides the system into independent, manageable components.

Scalability – Ensures the system can handle growth efficiently.

Separation of Concerns – Organizes code by distinct functionalities to

improve maintainability.

Reusability – Encourages using existing components to reduce redundancy.

Flexibility – Allows easy modifications and adaptability to changing

requirements.

3 Object-Oriented Analysis and Design (OOAD)

Encapsulation – Bundles data and methods together while restricting direct

access.

Abstraction – Hides complex implementation details, exposing only essential

features.

Inheritance – Enables a class to derive properties and behaviors from another

class.

Polymorphism – Allows objects to be treated as instances of their parent class,

enabling flexibility.

Modularity – Breaks down the system into independent, reusable objects for
better maintainability.

4 CLASS DIAGRAM

A UML diagram that represents the structure of a system using classes, attributes,
methods, and relationships.

Classes – Define objects with attributes (variables) and methods (functions).

Relationships – Show associations between classes (e.g., inheritance,

composition, aggregation).

Multiplicity – Specifies the number of instances in a relationship (e.g., one-to-

many).

Visibility Modifiers – Indicate access levels (public +, private -, protected #).

UNIT 4
SHORT QUESTIONS
 What is code reuse?
Code reuse is the practice of using existing code to reduce redundancy and improve
development efficiency.

  Define UML.
UML (Unified Modeling Language) is a standardized visual language for designing
and documenting software systems.

  Define Sequence Diagram.

A sequence diagram is a UML diagram that represents object interactions in a time-
ordered sequence to show message flow.

  What are agile methods in software development?

Agile methods are iterative and flexible software development approaches that focus
on collaboration, customer feedback, and incremental delivery.

  What is a Design Pattern?

A design pattern is a reusable solution to common software design problems,
providing best practices for structuring code.

  What is a Decision Tree?

A decision tree is a graphical model used for decision-making, representing choices
and their possible outcomes in a tree-like structure.

LONG QUESTIONS
1 SEQUENCE DIAGRAM
A UML diagram that represents object interactions in a time-ordered
sequence.

Example of a Sequence Diagram

Scenario: User Login Process

Actors: User, Login System, Database

Lifelines: Represent User, Login System, and Database interactions.

Messages:

User → Login System: Enter username & password

Login System → Database: Validate credentials

Database → Login System: Return authentication result

Login System → User: Grant or deny access

Activation Bars: Show Login System and Database processing requests.

Loop (Optional): If authentication fails, prompt for re-entry.

2 Decision Tree & Decision Table

Decision Tree – A graphical representation of decision-making, using nodes

for conditions and branches for outcomes.

Root Node – Represents the starting decision point in the tree.

Branches – Paths that connect decisions to possible outcomes.

Leaf Nodes – Represent final decisions or actions based on conditions.

Decision Table – A tabular format listing conditions and corresponding

actions for structured decision-making.

3 Good Coding Practices

Readable Code – Use meaningful variable and function names for clarity.

Proper Indentation – Maintain consistent formatting for better structure.

Code Reusability – Write modular functions and avoid redundancy.

Error Handling – Implement exception handling to prevent crashes.

Documentation – Add comments and docstrings to explain logic.

4 Component-Based Software Engineering (CBSE)

An approach that focuses on building software using reusable, independent
components.

Modularity – Divides the system into self-contained, interchangeable

components.

Reusability – Promotes using pre-built components to reduce development

effort.

Maintainability – Simplifies updates by modifying individual components

without affecting the whole system.

Scalability – Allows easy integration of new components for system

expansion.

UNIT 5
SHORT QUESTIONS
 What is software testing?
Software testing is the process of evaluating a software application to identify defects
and ensure it meets requirements.

  Define software quality.

Software quality refers to the degree to which a software product meets functional
and non-functional requirements with minimal defects.

  Define testing phase.

The testing phase is a stage in the software development lifecycle where a system is
evaluated to detect and fix errors before deployment.

  Specify the metrics for assessing software quality.

Common metrics include defect density, code coverage, reliability, maintainability,
performance efficiency, and user satisfaction.

  Define class coupling.

Class coupling refers to the degree of dependency between classes, where high
coupling reduces maintainability and low coupling improves modularity.

  Differentiate between testing and debugging.

Testing identifies defects in software, while debugging is the process of fixing those
defects by analyzing and modifying the code.

LONG QUESTIONS
1 Quality Management Models

ISO 9001 – International standard ensuring quality management and

continuous improvement.

Capability Maturity Model Integration (CMMI) – Framework for process

improvement and software quality enhancement.

Six Sigma – Data-driven methodology focused on reducing defects and

improving efficiency.

Total Quality Management (TQM) – Organization-wide approach

emphasizing customer satisfaction and process optimization.

Lean Software Development – Eliminates waste, improves workflow, and

enhances software quality.

2 Test Cases

A set of conditions or inputs to verify a software application's functionality.

Test Case ID – A unique identifier for tracking.

Test Scenario – Describes the feature or functionality to be tested.

Input Data – Specific values used to execute the test.

Expected Output – The correct system response for given inputs.

3 Software Verification & Validation (V&V) Process

Verification – Ensures the software meets design specifications through

reviews, inspections, and static testing.

Validation – Confirms the software meets user requirements through dynamic

testing.

Requirement Review – Checks if specifications align with customer needs.

Testing (Unit, Integration, System, Acceptance) – Evaluates software

functionality at different levels.

Defect Tracking & Resolution – Identifies, logs, and fixes issues before
release.
4 Quality Standards

ISO 9001 – International standard for quality management and continuous

improvement.

ISO/IEC 25010 – Defines software product quality attributes like usability,

reliability, and security.

CMMI (Capability Maturity Model Integration) – Framework for process

improvement in software development.

IEEE 829 – Standard for software test documentation.

Six Sigma – Data-driven methodology for minimizing defects and improving

process quality.