SEN QUESTION BANK

1. Define software on engineering. [2M] - S19

2. What is agile process.[4M] - S17
3. State any four principle of communications for software engineering.[4M] - S19
4. List seven task of requirement engineering.[4M] S15 2
5. What is SRS ? [4M]S17 2
6. Enlist & explain software characteristic.[4M] S18
7. Explain software engineering as a layered technology approach. [4M] - S19
8. State need of software requirement specification
9. Explain the waterfall model.
10. Explain the principles of analysis modeling.
11. What do you mean by process framework? Explain with suitable diagram.[4M] -
Textbook
12. Give difference between waterfall model and incremental model.[4M] - Textbook
13. Explain spiral model with diagram
14. Elaborate the software characteristic “software does not wear out “.

Software engineering as a layered technology approach means applying

engineering principles to software development in a structured and
systematic way. The four layers are:
● Tools: The software engineering tools provide automated or semi-
automated support for the process and the methods. Examples of
tools are IDEs, testing tools, debugging tools, etc.
● Methods: The software engineering methods provide the technical
how-to’s for building software. Examples of methods are
requirement analysis, design modeling, coding, testing, etc.
● Process: The software engineering process defines a framework for
the activities, actions, and tasks required to develop high-quality
software. Examples of process models are waterfall, agile, spiral,
etc.
● Quality: The software engineering quality focuses on ensuring that
the software meets the customer’s needs and expectations, and
adheres to the standards and best practices of software
engineering. Examples of quality attributes are functionality,
reliability, usability, efficiency, maintainability, and portability.
Q. Certainly! The waterfall model is a software development life cycle
model that follows a structured and sequential approach. Here are the
key points about the waterfall model:
1. Sequential Phases: The waterfall model involves a linear breakdown
of development activities into distinct phases. Each phase depends
on the deliverables of the previous one, creating a cascade effect.
The phases are completed one after the other without iteration or
overlap.
2. Phases in Waterfall Model:
○ Requirements Gathering and Analysis: In this initial phase,
project stakeholders’ requirements are collected and
analyzed. Understanding the scope and objectives of the
project is crucial.
○ Design Phase: Once the requirements are clear, the design
phase begins. Detailed design documents are created,
specifying the software architecture, user interface, and
system components.
○ Implementation and Unit Testing: The implementation phase
involves coding based on the design specifications.
Simultaneously, unit testing ensures that each software
component functions correctly.
3. Document-Driven Approach: The waterfall model heavily relies on
documentation. Clear and comprehensive documentation ensures
the track of projects.
The waterfall model is suitable for large-scale projects with well-defined
requirements and clear goals. However, it’s essential to recognize that
it’s an idealistic approach and may not always align with the dynamic
nature of modern software development123.
Q- Certainly! The Spiral Model is a software development life cycle (SDLC)
model that combines elements of other process models, such as
incremental, waterfall, or evolutionary prototyping. Here are the key
points about the Spiral Model:
 1. Risk-Driven Approach: The Spiral Model focuses on managing risk
throughout the software development process. It acknowledges
that uncertainties and risks exist and aims to address them
iteratively. Each iteration of the spiral represents a complete
software development cycle.
2. Phases of the Spiral Model:
○ Planning: In the initial phase, the project scope is determined,
and a plan is created for the next iteration.
○ Risk Analysis: Risks associated with the project are identified
and evaluated.
○ Engineering: Software development occurs based on
requirements gathered in the previous iteration.
○ ->(Imp. & Test)Evaluation: The software is evaluated to
ensure it meets customer requirements and maintains high
quality.
○ The next iteration begins with a new planning phase,
informed by the evaluation results.
3. Flexibility and Risk Handling: The Spiral Model is well-suited for
complex and large projects. It allows for a flexible and adaptable
approach, making it useful when dealing with significant
uncertainty or high levels of risk. The radius of the spiral represents
project expenses, while the angular dimension indicates progress
within the current phase1234.
Certainly! Here are two simple points explaining why software doesn’t
wear out:
1. No Physical Deterioration:
○ Unlike hardware, software doesn’t suffer from physical wear and tear.
○ It doesn’t rust, degrade, or accumulate dust over time.
○ Software remains resilient and adaptable.
2. Easy Modifications and Updates:
○ Developers can easily modify or update software based on user
demands.
○ Software adapts to evolving requirements without needing physical
changes.
○ Bugs can be fixed, and new features added without wearing out the
software.
Remember, software is like a digital chameleon—it evolves, but it doesn’t
wear out!
Q) Certainly! Here are additional points about the software process framework:

Software Process Framework Overview:

1. A software process framework provides an abstraction of the software

development process.
2. It serves as a foundation for organizing and understanding the steps
involved in creating software.
3. Key components within the framework include:
1. Tasks: Focused on specific, small objectives (e.g., gathering
requirements).
2. Actions: Sets of tasks that produce major work products (e.g.,
coding, testing).
3. Activities: Groups of related tasks and actions for significant
objectives (e.g., modeling, deployment).

Framework Activities:

1. The process framework defines five core activities in software

engineering:
1. Communication:
1. Involves gathering customer requirements and
understanding system objectives.
2. Communication with stakeholders to determine software
needs.
2. Planning:
1. Establishes an engineering work plan, identifies technical
risks, allocates resources, and defines schedules.
2. Describes work produced during the project.
3. Modeling:

Creates architectural models and designs to better understand

the problem and find optimal solutions.

1. Includes analyzing requirements and designing system

components.
 4. Construction:

1. Involves creating code, testing the system, fixing bugs, and

ensuring all criteria are met.
2. Translates the software design into executable code.
5. Deployment:

1. Represents the complete or partially complete product to

customers for evaluation and feedback.
2. Feedback drives modifications for better product delivery.

8) Certainly! Here are three key points about Software Requirement Specifications
(SRS):

Purpose of SRS:

1. The SRS serves as a complete specification and description of software

requirements.
2. It ensures successful development by capturing both functional and non-
functional requirements.

Components of SRS:

1. General Description:
1. Describes the purpose, features, and importance of the software.
2. Includes information about user characteristics and benefits.
2. Functional Requirements:
1. Specifies the expected behavior of the system.
2. Defines the relationship between input and output.
3. Interface Requirements:

1. Describes how the software communicates with other

components.

Importance of SRS:

4. Provides clarity, agreement, and a solid foundation for software

development.
5. Enables alignment with project goals and efficient execution.