SE Important Questions

Essay Questions

1. Discuss in detail about waterfall process model.

2. Define software? Explain in detail about software myths?
3. Explain CMMI model with a neat sketch?
4. What is feasibility study? Explain types.
5. Explain about requirement elicitation and analysis in briefly?
6. Define software engineering. Explain about process patterns.
7. Explain about software requirement specification in detailed?
8. Explain about functional requirements and non-functional requirements with an example
9. What is a SDLC? Explain about incremental model in detail.
10. Explain the bulling blocks of UML?
11. Briefly explain about Behavioral models with an example.
12. Develop SRS document for college management system.
13. Give an overview of unified process model.
14. Explain the following
i) Prototyping model
ii) ii) Spiral Model.

15. Briefly explain about the following diagrams with example:

a) Sequence diagram

b) Use case diagram

 Short Answers
1. Explain change nature of software?

The 7 broad categories of computer software present continuing challenges for software engineers:

System software
Application software

Engineering/scientific software

Embedded software

Product-line software

Web Application Software

Artificial intelligence software

2. Explain about context model?

Context models are used to illustrate the operational context of a system - they show
what lies outside the system boundaries. Social and organizational concerns may affect
the decision on where to position system boundaries. Architectural models show the
system and its relationship with other systems.
The context of an ATM system:

3. What is requirement management?

Requirements management is the process of managing changing requirements
during the requirements engineering process and system development.
Requirements are inevitably incomplete and inconsistent
New requirements emerge during the process as business needs change and a
better understanding of the system is developed;
4. Explain interface specification?

Interface specification, in the context of software development and computer systems, refers to a
detailed description or set of rules that define how different software components or modules
should interact with each other. It acts as a contract or agreement that ensures seamless
communication and integration between various parts of a software system.

In simpler terms, an interface specification outlines the rules and guidelines for how different
parts of a software application should "talk" to each other, exchange data, and cooperate to
perform specific tasks. These interfaces can be between software modules, software and
hardware components, or even between different software systems.

5. Explain about process framework?

A process framework establishes the foundation for a complete software process by

identifying a small number of framework activities that are applicable to all software projects,
regardless of their size or complexity.
The process framework encompasses a set of umbrella activities that are
applicable across the entire software process.
Each framework activity is populated by a set of software engineering actions
Each software engineering action is represented by a number of different
task sets- each a collection of software engineering work tasks, related work
products, quality assurance points, and project milestones.

6. What is legacy software?

The older programs which are developed decades ago that are still in use by performing
modifications in order to meet the business requirements. The rapid increase of such systems
may cause the risk to the larger organizations as they may require outdated hardware and
operating system.
Many legacy systems remain supportive to core business functions and are important to
business. Hence, legacy software is characterized by longevity and business criticality.

7. Define software myths and its types?

Software myths are beliefs about software and the process used to build it.
Management myths: Manages with software responsibility, like managers in most
disciplines, are often under pressure to maintain budgets, keep schedules from slipping, and
improve quality.
Customer myths: The customer believes myths about software because software managers
and practitioners do little to correct misinformation. Myths lead to false expectations and
ultimately, dissatisfaction with the developer.
8. What is feasibility study?

A feasibility study involves information assessment, information collection and report writing

A feasibility study decides whether or not the proposed system is

worthwhile. The input to the feasibility study is a set of preliminary business
requirements, an outline description of the system and how the system is
intended to support business processes. The results of the feasibility study
should be a report that recommends whether or not it worth carrying on with
the requirements engineering and system development process.

9. Differentiate between user requirement and system requirement.

User requirements are statements about what the user needs the system to do to solve a specific
problem or meet a specific need.

They are generally written in the language of the user and describe the desired outcomes,
features, or functions of the system.

On the other hand, system requirements are technical descriptions of how the system should be
built to meet the user requirements.

They define the specifications for the system components, interfaces, performance, security, and
other technical aspects necessary to build the system.

10. What are software engineering layers?

SOFTWARE ENGINEERING - A LAYERED TECHNOLOGY:

Tools

Methods

Process

A quality focus
11. Explain about evolving role of software?

Software takes dual role. It is both a product and a vehicle for delivering a product.
As a product: It delivers the computing potential embodied by computer Hardware
or by a network of computers.
As a vehicle: It is information transformer-producing, managing, acquiring, modifying,
displaying, or transmitting information that can be as simple as single bit or as complex as a
multimedia presentation. Software delivers the most important product of our time-
information.
It transforms personal data
It manages business
information to enhance
competitiveness It provides a
gateway to worldwide
information networks
It provides the means for acquiring information

12. Write about process assessment?

The existence of a software process is no guarantee that software will be delivered on time,
that it will meet the customer‘s needs, or that it will exhibit the technical characteristics that
will lead to long-term quality characteristics. In addition, the process itself should be assessed
to be essential to ensure that it meets a set of basic process criteria that have been shown to be
essential for a successful software engineering.

13. Define function and non functional requirement?

Functional requirements
 These describe the functionality of a system -- how a system should react to a particular set
of inputs and what should be the corresponding output.
Non-Functional requirements
 They are not directly related what functionalities are expected from the system.
 However, NFRs could typically define how the system should behave under certain situations.
 For example, a NFR could say that the system should work with 128MB RAM.

14. Discuss about requirements validation in brief?