Ans.

The term stakeholder is used to refer to any person or group who will be affected by the
system, directly or indirectly. Stakeholders include end-users who interact with the system
and everyone else in an organisation that may be affected by its installation. Other system
stakeholders may be engineers who are developing or maintaining related systems,
business managers, domain experts, and trade union representatives.
Ans 2.

This category is about all aspects of software (SW) which here is taken to include the
following categories:
 Application software (application software: office suites, word processors, spreadsheets, etc.)
 System software (system software: operating systems, device drivers, desktop environments, etc.)
 Computer programming tools (programming tools: assemblers, compilers, linkers, etc.)

Ans 3.
Quality Function Deployment (QFD)

Ans 4.

Answer:Product risk

Ans 5.
A software metric is a standard of measure of a degree to which a software system or process
possesses some property. Even if a metric is not a measurement, often the two terms are used as
synonyms.

Qustion 2 (b)
i) Ans:

Software:Software, in its most general sense, is a set of instructions or programs instructing a

computer to do specific tasks. Software is a generic term used to describe computer programs.

Software Characteristics:
• Functionality: Refers to the degree of performance of the software against its intended
purpose.
• Reliability: Refers to the ability of the software to provide desired functionality under
the given conditions.
• Usability: Refers to the extent to which the software can be used with ease.
• Efficiency: Refers to the ability of the software to use system resources in the most
effective and efficient manner.
• Maintainability: Refers to the ease with which the modifications can be made in a
software system to extend its functionality, improve its performance, or correct errors.
• Portability: Refers to the ease with which software developers can transfer software
from one platform to another, without (or with minimum) changes. In simple terms, it
refers to the ability of software to function properly on different hardware and software
platforms without making any changes in it.
In addition to the above mentioned characteristics, robustness and integrity are also
important. Robustness refers to the degree to which the software can keep on
functioning in spite of being provided with invalid data while integrity refers to the
degree to which unauthorized access to the software or data can be prevented.

B) (II)

Ans:

Software engineering is the application of principles used in the field of engineering, which
usually deals with physical systems, to the design, development, testing, deployment and
management of software systems.
Software mythos:

Management myths
Customer / end-user myths
Programmer myths

B) (III)

Ans:
SRS document is a contract among the development team and the customer. Once the SRS document is
accepted by the customer, any subsequent controversies are settled by referring the SRS document. The SRS
document is called as black-box specification. Since the system is considered as a black box whose internal
details are not known and only its visible external (i.e. input/output) behavior is recognized.

B) (IV)

Ans:

Coupling: Coupling is the measure of the degree of interdependence between the modules. A
good software will have low coupling.
Cohesion: Cohesion is a measure of the degree to which the elements of the module are
functionally related. It is the degree to which all elements directed towards performing a single
task are contained in the component
A system with high coupling means there are strong interconnections among
its modules and if two modules are involved in high coupling it means their interdependence
will be very high. ... This will extra decrease the reusability factor of individual modules and
hence lead to unsophisticated software.
 Question 3 (a)
(a) Ans:

Reliability
Efficiency
Integrity
Usability
Maintainability
Flexibility
Testability
Portability
Reusability
Interoperability

(b) Ans:

There are four requirement types within three distinct requirement levels:
 (A) Business Requirements Level. (1) Business Requirement Type. ...
 (B) User Requirements Level. (2) User Requirement Type. ...
 (C) System Requirements Level. (3) Functional Requirement Type
Requirement engineering consists of seven different tasks as follow:

1. Inception
 Inception is a task where the requirement engineering asks a set of questions
to establish a software process.
 In this task, it understands the problem and evaluates with the proper solution.
 It collaborates with the relationship between the customer and the developer.
 The developer and customer decide the overall scope and the nature of the
question.
2. Elicitation
Elicitation means to find the requirements from anybody.
The requirements are difficult because the following problems occur in
elicitation.

Problem of scope: The customer give the unnecessary technical detail rather
than clarity of the overall system objective.

Problem of understanding: Poor understanding between the customer and

the developer regarding various aspect of the project like capability, limitation
of the computing environment.
 Problem of volatility: In this problem, the requirements change from time to
time and it is difficult while developing the project.

3. Elaboration
 In this task, the information taken from user during inception and elaboration
and are expanded and refined in elaboration.
 Its main task is developing pure model of software using functions, feature and
constraints of a software.
4. Negotiation
 In negotiation task, a software engineer decides the how will the project be
achieved with limited business resources.
 To create rough guesses of development and access the impact of the
requirement on the project cost and delivery time.
5. Specification
 In this task, the requirement engineer constructs a final work product.
 The work product is in the form of software requirement specification.
 In this task, formalize the requirement of the proposed software such as
informative, functional and behavioral.
 The requirement are formalize in both graphical and textual formats.
6. Validation
 The work product is built as an output of the requirement engineering and that
is accessed for the quality through a validation step.
 The formal technical reviews from the software engineer, customer and other
stakeholders helps for the primary requirements validation mechanism.
7. Requirement management
 It is a set of activities that help the project team to identify, control and track
the requirements and changes can be made to the requirements at any time of
the ongoing project.
 These tasks start with the identification and assign a unique identifier to each
of the requirement.
 After finalizing the requirement traceability table is developed.
 The examples of traceability table are the features, sources, dependencies,
subsystems and interface of the requirement.
(c) Ans:
Types of Risk:
Schedule / Time-Related / Delivery Related Planning Risks.
 Budget / Financial Risks.
Operational / Procedural Risks.
Technical / Functional / Performance Risks.
Other Unavoidable Risks.
Risk identification is the process of determining risks that could potentially prevent the
program, enterprise, or investment from achieving its objectives. It includes documenting
and communicating the concern
Risk avoidance is the elimination of hazards, activities and exposures that can negatively
affect an organization's assets. Whereas risk management aims to control the damages
and financial consequences of threatening events, risk avoidance seeks to avoid
compromising events entirely.
Q-3 OR
(a)
Ans:

Project lifecycle: This is the cycle a project goes through from beginning to end. It
consists of five phases:

 Initiation

 Planning

 Execution

 Monitoring & controlling

 Closure

Project control cycle: The control cycle is the process of monitoring and controlling the
project.

The primary components of a project management plan are:

1. Scope Statement
2. Critical Success Factors
3. Deliverables
4. Work Breakdown Structure
5. Schedule
6. Budget
7. Quality
8. Human Resources Plan
9. Stakeholder List
10. Communication
11. Risk Register
12. Procurement Plan
A software project manager is the most important person inside a team who takes the
overall responsibilities to manage the software projects and play an important role in the
successful completion of the projects. ... Project planning. Project monitoring and control.
(b)
Ans:
Cocomo (Constructive Cost Model) is a regression model based on LOC, i.e number of
Lines of Code. It is a procedural cost estimate model for software projects and often used
as a process of reliably predicting the various parameters associated with making a project
such as size, effort, cost, time and quality.
(c)
Ans:
1. One way street:
This model is just like the one-way street. Once phase X is completed and next
phase Y has started then there is no way to going back on the previous phase.
This is one of the issues to the failure of the waterfall model.
2. Overlapping:
The waterfall model has lacked an overlapping among phase.The waterfall model
recommends that new phase can start only after the completion of the previous
phase. But in real projects, this can’t be maintained. To increase the efficiency and
reduce the cost, phases may overlap.
3. Interaction:
The waterfall model has lacked interaction among phase. Users have little
interaction with project them. This feedback is not taken during development. After
a development process starts, changes can not accommodate easily.
4. Support delivery of system:
The waterfall model does not support delivery of system in pieces. After a
development process starts, changes cannot accommodate easily.
5. Feedback path:
The waterfall model has no feedback path. In the traditional waterfall model
evolution of software from one phase to another phase is like a waterfall. The
waterfall model assumes that no error is ever committed by developers during any
phases. Hence, it does not incorporate any mechanism for error correction.
6. Not Flexible:
Difficult to accommodate change requests. The waterfall model assumes that all
the customer requirements can be completely and correctly defined at the
beginning of the project, but actually customers’ requirements keep on changing
 with time. After the requirements specification phase is completed difficult to
accommodate any change requests.
Drabacks of RAD model:
It can't be used for smaller projects
Not all application is compatible with RAD
When technical risk is high, it is not suitable
If developers are not committed to delivering software on time, RAD projects
can fail
A spiral model is made up of set different framework activities made by the software
engineering team. ... It begins at the center of the spiral model. Typically,
there are between three and six task regions. The above figure depicts a spiral model that
contains 6 task regions.

Q-4

a) Ans: Regression Testing is defined as a type of software testing to confirm

that a recent program or code change has not adversely affected existing
features. Regression Testing is nothing but a full or partial selection of already
executed test cases which are re-executed to ensure existing functionalities work
fine.
b) Ans: Supply chain
c) Ans: Test Case deisgn
d) Ans: software testing, and software engineering, verification and validation
(V&V) is the process of checking that a software system meets specifications
and that it fulfills its intended purpose. It may also be referred to as software
quality control.
e) Ans:
f) Ans:
g) Ans:

Q-5
a.
Ans: The Capability Maturity Model (CMM) is a methodology used to develop and
refine an organization's software development process. The model describes a five-
level evolutionary path of increasingly organized and systematically more mature
processes.

The Software Engineering Institute (SEI) Capability Maturity Model (CMM) specifies an
increasing series of levels of a software development organization. The higher the level, the
better the software development process, hence reaching each level is an expensive and
time-consuming process.
Levels of CMM
b. Ans:
Objectives • Defining a system • The role of computer in information systems • What are
the characteristic and element of information system • What are the various types of
information system and models • What are the different types of specialised information
system
c. Ans:

Data flow diagrams are used to graphically represent the flow of data in a business
information system. DFD describes the processes that are involved in a system to
transfer data from the input to the file storage and reports generation.

OR

[a]

Ans.
 Seven Principles of Software Testing
 #1) Testing Shows the Presence of Defects. ...
 #2) Early Testing. ...
 #3) Exhaustive Testing is Not Possible. ...
 #4) Testing is Context-Dependent. ...
 #5) Defect Clustering. ...
 #6) Pesticide Paradox. ...
 #7) Absence of Error
 Usability Testing - Usability Testing mainly focuses on the user's ease to use
the application, flexibility in handling controls and ability of the system to meet
its objectives
 Load Testing - Load Testing is necessary to know that a software solution will
perform under real-life loads.
 Regression Testing- - Regression Testing involves testing done to make sure
none of the changes made over the course of the development process have
caused new bugs. It also makes sure no old bugs appear from the addition of
new software modules over time.
 Recovery Testing - Recovery testing is done to demonstrate a software
solution is reliable, trustworthy and can successfully recoup from possible
crashes.
 Migration Testing - Migration testing is done to ensure that the software can
be moved from older system infrastructures to current system infrastructures
without any issues.
 Functional Testing - Also known as functional completeness testing, Functional
Testinginvolves trying to think of any possible missing functions. Testers might
make a list of additional functionalities that a product could have to improve it
during functional testing.
 Hardware/Software Testing - IBM refers to Hardware/Software testing as
"HW/SW Testing". This is when the tester focuses his/her attention on the
interactions between the hardware and software during system testing.

[b]

Ans.

Umbrella Activities are as follows:

 Software Project Tracking and Control.
 Formal Technical Reviews.
 Software Quality Assurance.
 Software Configuration Management.
 Document Preparation and Production.
 Re-usability Management.
 Measurement and Metrics.
 Risk Management.

[c] Ans.

Software maintenance in software engineering is the modification of a software product

after delivery to correct faults, to improve performance or other attributes. A common perception
of maintenance is that it merely involves fixing defects