WWW.VIDYARTHIPLUS.

COM

UNIT-I
1. What is an effector process. (Nov/Dec 2005 )
The effector process is a process that verifies itself. The effector process exists
in certain criteria.

2. State Humphreys rule for software development. (Nov/Dec 2005 )

An important first step in addressing the software is to treat the entire
software task as a process that can be controlled, measured and improved. Also
successful software is designed by people who understand the application of the
software.

3. How a software process can be characterized? (May/June 2006)

Analyze and SpecifySoftware Requirements
Design and Implement Software Product
Test that ProductMeets Requirements
Deploy, Maintain, and Enhance the Product

4. How do you schedule software development? (Nov/Dec 2007)

Specification
Design and implementation
Validation
Evolution

5. What are the various techniques of cost estimation of a software project?

(Nov/Dec 2007)
Constructive cost model, developed by Barry W. Boehm. It divides the
software product into three categories of software:
organic,
semi-detached
embedded

6. Explain the difference between validation and verification of an

implementation. (April/May 2008)

validation verification

The process of evaluating work- The process of evaluating

products (not the actual final
product) of a development phase
to determine whether they meet
the specified requirements for that
phase.
software during or at the end of
the development process to
determine whether it satisfies
specified business requirements.
 WWW.VIDYARTHIPLUS.COM

7. State the benefits of water fall life cycle model for software development.
(April/May 2008)
Waterfall model is the simplest model of software development paradigm. It
says the all the phases of SDLC will function one after another in linear manner.
That is, when the first phase is finished then only the second phase will start and so
on.

8. What are the draw backs of water fall model. (Nov/Dec 2009)
This model is best suited when developers already have designed and
developed similar software in the past and are aware of all its domains.

9. Which process model follows realistic approach and more suitable to large
scale system? Why? (Nov/Dec 2009)
Spiral Model is realistic approach and more suitable to large scale
system.The spiral model is similar to the incremental model, with more emphasis
placed on risk analysis. The spiral model has four phases: Planning, Risk Analysis,
Engineering and Evaluation. A software project repeatedly passes through these
phases in iterations (called Spirals in this model).

10. Differentiate system and computer based system. (April/May 2010)

A system is a collection of elements or components that are organized for a
common purpose. The computer based system can be defined as a set or an
arrangement of elements that are organized to accomplish some predefined goal by
processing information.

11. Give at least two reasons for prototyping is problematic. (April/May 2010)
Insufficient analysis
User confusion of prototype and finished system
Excessive development time of the prototype
Expense of implementing prototyping

12. Define software process. (May/June 2011)

Fundamental activities of a software process
1. Specification
2. Design and implementation
3. Validation
4. Evolution
Software process is defined as the structured set of activities that are required
to develop the software system.
13. Mention the drawbacks in linear sequential model. (May/June 2011)
The Waterfall Model was first Process Model to be introduced. It is also
referred to as a linear-sequential life cycle model.
Once an application is in the testing stage, it is very difficult to go back and
change something that was not well-thought out in the concept stage.No
working software is produced until late during the life cycle.High amounts of
risk and uncertainty.
 WWW.VIDYARTHIPLUS.COM

Not a good model for complex and object-oriented projects.Poor model for
long and on-going projects.

14. Draw the system engineering hierarchy. (Nov/Dec 2012)

System Engineering Hierarchy
World view WV = {D1, D2, D3, ,Dn}

Composed of a set of domains (Di) which can be each be a system or system

of systems
Domain view DV = {E1, E2, E3, ,Em}

Composed of specific elements (Ej) each of whichserves some role in

accomplishing the objectiveand goals fo the domain or component
Element view EV = {C1, C2, C3, ,Ck}

Each element is implemented by specifying the technical component (Ck) that

achieve the necessary function for an element

15. Difference between waterfall model and spiral model. (Nov/Dec 2012)
The waterfall model the process goes to the next step after
completion of the previous step as first requirement then design then coding then
implementation then maintenance but here is no end user feedback taken to
consideration any change in SRS will result to start work fro first step and
goes step by step again.But in case of Spiral model for each and every step there
is testing for that step carry on simultaneously after finishing that step so that it will
easy to recover any error and fix it there. In this model we don?t have to
start work from beginning
 WWW.VIDYARTHIPLUS.COM

16.What is software engineering

Software engineering is a discipline in which theories, methods and tools are

applied to develop professional software.

17.distinguish verification and validation.

Validation is process of examining whether or not the software satisfies the user
requirements. It is carried out at the end of the SDLC. If the software matches
requirements for which it was made, it is validated.

Verification is the process of confirming if the software is meeting the business

requirements, and is developed adhering to the proper specifications and
methodologies.

18.define system engineering.

Systems engineering is an interdisciplinary approach to design, implementation

and evaluation that holds the key to the successful development of complex human-
made systems.
 WWW.VIDYARTHIPLUS.COM

Unit II

1. Why SRS must be traceable? What is traceability requirement? (Nov/Dec 2005

)
I. Correct The SRS should be made up to date when appropriate
requirements are identified.
II. Unambiguous When the requirements are correctly understood then only it
is possible to write an unambiguous software.
III. Complete To make SRS complete, it should be specified what a software
designer wants to create software.
IV. Consistent It should be consistent with reference to the functionalities
identified.
V. Specific The requirements should be mentioned specifically.
VI. Traceable

2. State the different criteria applied to evaluate an effective modular system.

(May/June 2006)
A system is considered modular if it consists of discreet components so that
each component can be implemented separately, and a change to one
component has minimal impact on other components.
Modularity is a clearly a desirable property in a system. Modularity helps in
system debugging. Isolating the system problem to a component is easier if
the system is modular.

3. In that way, an abstraction differs from a refinement? (May/June 2006)

Software abstraction examples
System requirements Generic software component in a library
specification
Subroutine spec Framework

Type, class Architecture

Pseudo code Pattern

Theory (set of statements) about a class or

Performance criteria type

Creating and using abstractions

Useful abstraction is a generalisation of several cases, which must be understood

first. Successful abstraction comes after some experience of concrete examples.
(True both when inventing the abstraction, and when explaining it to others.)
Refinementis a relation between two descriptions, which may be in the same or a
different notation.The idea is that both describe the same thing or concept, but
the abstraction contains less information than the realisation.A description may be
both the abstraction of one refinement and the realisation of another.
 WWW.VIDYARTHIPLUS.COM

4. How do you design a software project for reuse? (Nov/Dec 2007)

A clear and well-defined product vision is an essential foundation to an
software project.
An evolutionary implementation strategy would be a more pragmatic strategy
for the company.
There exist a need for continuous management support and leadership to
ensure success.

5. What are the standards for documentation? Briefly explain (Nov/Dec 2007)
IEEE Std 1028-2008
This standard defines five types of software reviews and procedures for their
execution. Review types include management reviews, technical reviews,
inspections, walk-throughs and audits.
IEEE Std 1012-2004
This standard describes software verification and validation processes that are
used to determine if software products of an activity meets the requirements of the
activity and to determine if software satisfies the user's needs for the intended
usage. The scope includes analysis, evaluation, review, inspection, assessment
and testing of both products and processes.

6. What is the major distinction between user requirement and system

requirement? (April/May 2008)
User requirements may be a set of statements or use case scenarios presented
by the client in laymans terms of which the client can easily elaborate and are
usually free of technical jargon. System requirements are built from the clients input
being what they have specified in the user requirements.

7. Which style of prototyping is most appropriate when the requirement are not
well-understood? (April/May 2008)
User Interface prototyping is most appropriate.This prototyping is used to pre-
specify the look and feel of user interface in an effective way.

8. What are context free questions? How it differs from meta questions?
(Nov/Dec 2009)
Context free questions are questions that can be used regardless of the project
under consideration. They are general questions about the nature of the project and
the environment in which the final product will be used.Meta questions are very
complex and detailed questions about the project model.

9. Specify at least four questionnaire which supports to select the prototyping

approach. (Nov/Dec 2009)
Prototype serves as a basis for deriving system specification.
Design quality can be improved.
System can be maintained easily.
Development efforts may get reduced.
System usability can be improved.

10. What is the purpose of domain analysis. (April/May 2010)

 WWW.VIDYARTHIPLUS.COM

Domain analysis, or product line analysis, is the process of analysing related

software systems in a domain to find their common and variable parts. It is a model
of wider business context for the system.

11. What is data dictionary? (May/June 2011)

The data dictionary can be defined as an organized collection of all the data
elements of the system with precise and rigorous definitions so that user and
system analyst will have a common understanding of inputs, outputs, components
of stores and intermediate calculations.

12. Give the characteristics of a good design. (May/June 2011)

The design must satisfy all the requirements explicitly included in the
requirements specification, as well as additional ``implicit'' requirements that
the customer may have.
The design must be a readable and understandable guide for the developers
who will write code for the system based on it, as well as for the developers
who will later test and maintain it.
The design should give a complete picture of the software system,
``addressing the data, functional, and behavioural domains from an
implementation perspective.''

13. Define behavioural modelling(Nov/Dec 2012)

All behavioural models really do is describe the control structure of a system.
This can be things like:
Sequence of operations
Object states
and Object interactions
Furthermore, this modelling layer can also be called Dynamic Modelling. The
activity of creating a behavioural model is commonly known as behavioural
modelling. As well as this, a system should also only have one behavioural
model much like functional modelling.
14. List the criteria of data dictionary. (Nov/Dec 2012)
Data dictionary
Contains the descriptions of all data objects consumed or produced by the
software
15. list two advantages of using traceability tables in the requirement management
phase
The benefits of implementing requirements traceability can be summarized as follows.

Certification. Traceability information can be used in product certification to

demonstrate that all requirements were implemented.
Tracking. Recording traceability data during development allows for an accurate
record of the implementation status of planned functionalities.
 WWW.VIDYARTHIPLUS.COM

15.what are the types of prototypes

Evolutionary prototyping the initial prototype is prepared and it is then refined

through number of stages to final stage.
Throw-away prototyping a rough practical implementation of the system is
produced. The requirement problems can be identified from this implementation

16.what do you mean by functional and non functional requirement?

Functional requirements are statements of services the system should

provide how the system should react to particular input and how the system should
behave in particular situation.

Non functional requirements are constraints on the services or functions offered by the
system such as timing constraints, constraints on the development process, standards,
etc..

17. list two advantage of employing prototyping in software process?

Prototype serves as a basis for deriving system specification.

Design quality can be improved.
System can be maintained easily.
Development efforts may get reduced.
System usability can be improved.

UNIT III

1. What is risk assessment? Give the algorithm (Nov/Dec 2005)

 WWW.VIDYARTHIPLUS.COM

Risk assessment is the determination of quantitative or qualitative value of risk

related to a concrete situation and a recognized threat (also called hazard).
Quantitative risk assessment requires calculations of two components of risk(R):,
the magnitude of the potential loss (L), and the probability (p) that the loss will
occur.

2. How scope of the software can be determined(May/June 2006)

SCOPING
Scoping is an activity that bounds a system or set of systems by defining those
behaviours or aspects that are "in" and those behaviours or aspects that are "out."

Classes of scope include:

Organisational scope. The external or internal organisational groups or

individuals to which the endeavour applies.
Temporal scope. The period of time for which the endeavour is relevant.
Life cycle scope. The life cycle phases, processes, activities or tasks to which
the endeavour applies.
Deliverable scope. The set of deliverables or work products to which the
endeavour applies.
Functional scope. The set of business functions or functions of a system to
which the endeavour applies.
Architectural scope. The set of architectural components to which the
endeavour applies.
Strategic scope. The set of business and/or
system goals and objectives addressed by the endeavour.

3. How do you classify metrics? (Nov/Dec 2007)

Direct metrics It refers to immediately measurable attributes.
Example Lines of code, execution speed.
Indirect metrics It refers to the aspects that are not immediately
quantifiable or measurable. Example functionality of a program.

4. According to you, which standard is best for software quality assurance?

why? (Nov/Dec 2007)
CMMI models is best for software quality assurance
CMMI models provide guidance for developing or improving processes that meet
the business goals of an organization.
 WWW.VIDYARTHIPLUS.COM

5. Identify ambiguities or omissions in the functional requirement. What

question would you ask to clarity these functional requirement? (April/May
2008)
Functional requirements are statements of services the system should provide
how the system should react to particular input and how the system should behave
in particular situation.

6. Why it is necessary to design the system architecture before the

specifications are completed? (April/May 2008)
To gather the information about the estimation and performance model the
system architecture is necessary.

7. Differentiate version control and change control. (Nov/Dec 2009)

Version control is a system that records changes to a file or set of files over time
so that you can recall specific versions later.
Change control is a systematic approach to managing all changes made to a
product or system. The purpose is to ensure that no unnecessary changes are
made, that all changes are documented, that services are not unnecessarily
disrupted and that resources are used efficiently.

8. Why modularity is important in software projects. (Nov/Dec 2009)

Modularity refers to the extent to which a software/Web application may be
divided into smaller modules. Software modularity indicates that the number of
application modules are capable of serving a specified business domain.

Modularity is successful because developers use prewritten code, which saves

resources. Overall, modularity provides greater software development
manageability.
9. Differentiate Transform flow and Transaction flow. (Apr/May 2010)

Transform Flow
Incoming flow paths where incoming information is converted to internal
representation.
Transform Center where information is being processed.
Overall flow of data occurs in sequential manner and follows one or more linear
paths.

Transaction Flow
Reception paths that converts external information into a transaction.
A transaction center (dispatcher) where the transaction is evaluated and one of the
emanating paths is activated.
Overall flow of data forms a dispatch center pattern, where the incoming data flow
(via the reception path) is directed to only one of the action paths by the transaction
centre.
10. Give the characteristics of a good design(May/Jun 2011)
 WWW.VIDYARTHIPLUS.COM

The design must satisfy all the requirements explicitly included in the
requirements specification, as well as additional ``implicit'' requirements that
the customer may have.
The design must be a readable and understandable guide for the developers
who will write code for the system based on it, as well as for the developers
who will later test and maintain it.
The design should give a complete picture of the software system,
``addressing the data, functional, and behavioural domains from an
implementation perspective.''
11. Why architectural design is important in software engineering(May/Jun 2011)
Stakeholder communication
Architecture may be used as a focus of discussion by system stakeholders
System analysis
Means that analysis of whether the system can meet its non-functional
requirements is possible
Large-scale reuse
The architecture may be reusable across a range of systems
12. What is meant by SCM.(Nov/Dec 2012)
Software configuration management (SCM) is a software engineering discipline
consisting of standard processes and techniques often used by organizations to
manage the changes introduced to its software products. SCM helps in identifying
individual elements and configurations, tracking changes, and version selection,
control, and baselining.
SCM is also known as software control management. SCM aims to control changes
introduced to large complex software systems through reliable version selection
and version control.

13. List out the design issue while developing softwares. (Nov/Dec 2012)
6 most common problems in software development segregated by different
stages of a Software Development Life CycleRequirements Gathering, Planning
&Estimation, Development,Testing, Collaboration,Deployment.

14. list two principles of good design

seven basic principles are involved. These are:

Manage using a phased life-cycle plan.

Perform continuous validation.
Maintain disciplined product control.
Use modern programming practices.
Maintain clear accountability for results.
Use better and fewer people.
 WWW.VIDYARTHIPLUS.COM

Maintain a commitment to improve the process.

UNIT IV
1. How do you describe software interfaces? (Nov/Dec 2005)
Software interfaces provide access to computer resources (such as memory, CPU,
storage, etc.) of the underlying computer system; direct access (i.e. not through well
 WWW.VIDYARTHIPLUS.COM

designed interfaces) to such resources by software can have major ramifications

sometimes disastrous onesfor functionality and stability.
2. State the guidelines for debugging. (Nov/Dec 2005)
Debugging is the process of solving a problem. Hence, individuals involved
in debugging should understand all the causes of an error before starting
with debugging.
No experimentation should be done while performing debugging. The
experimental changes instead of removing errors often increase the problem
by adding new errors in it.

3. What is behavioural testing(May/June 2006)

Black Box Testing / Functional Testing Black box testing, concrete box or
functional testing is used to check that the outputs of a program, given certain
inputs, conform to the functional specification of the program. It performs
testing based on previously understood requirements (or understood
functionality), without knowledge of how the code executes.
4. How cyclomatic complexity of a program can be computed(May/June 2006)
Cyclomatic complexity is a software metric used to measure the complexity of a
program. These metric, measures independent paths through program source
code.
Independent path is defined as a path that has atleast one edge which has not
been traversed before in any other paths.
Cyclomatic complexity can be calculated with respect to functions, modules,
methods or classes within a program.
Control flow depicts a program as a graph which consists of Nodes and Edges.
In the graph, Nodes represent processing tasks while edges represent control
flow between the nodes.

5. Distinguish black and white box testing? (Nov/Dec 2007)

Black Box Testing is a software testing method in which the internal structure/
design/ implementation of the item being tested is NOT known to the tester .
 WWW.VIDYARTHIPLUS.COM

White Box Testing is a software testing method in which the internal structure/
design/ implementation of the item being tested is known to the tester.
6. What is the role of a testing tools? (Nov/Dec 2007)
There are two methods used in executing test cases: manual and automated.
Depending on the nature of the testing, it is usually the case that a combination of
manual and automated testing is the best testing method.

7. Explain the different between black box testing and white box testing?
(April/May 2008)
Black Box Testing is a software testing method in which the internal structure/
design/ implementation of the item being tested is NOT known to the tester .
White Box Testing is a software testing method in which the internal structure/
design/ implementation of the item being tested is known to the tester.
8. List out the data structures errors identified during unit testing. (Nov/Dec
2009)
Comparison of different data types
Incorrect logical operator precedence
Expectation of equality when division error make equality unlikely.
Incorrect comparison of variables.

9. How to compute cyclomatic complexity. (Nov/Dec 2009)

The cyclomatic complexity can be computed by any one of the following ways.
1. The numbers of regions of the flow graph correspond to the cyclomatic
complexity.
Cyclomatic complexity (G), for the flow graph G, is defined as: V(G)=E-N+2, E --
number of flow graph edges, N -- number of flow graph nodes
V(G) = P+1 Where P is the number of predicate nodes contained in the flow graph.

10. Define alpha and beta testing. (April/May 2010)

Alpha and beta testing are the types of acceptance testing.
Alpha test : The alpha testing is attesting in which the version of complete
software is tested by the customer under the supervision of developer. This testing
is performed at developers site.
Beta test : The beta testing is a testing in which the version of the software is
tested by the customer without the developer being present. This testing is
performed at customers site.

11. Why LOC based estimation is not universally accepted.(April/May 2010)

Lack of Accountability:
Lack of Cohesion with Functionality
Adverse Impact on Estimation
Developers Experience
Difference in Languages
Lack of Counting Standards
 WWW.VIDYARTHIPLUS.COM

12. How cyclomatic complexity of a program can be computed (May/June 2011)

Cyclomatic complexity is a source code complexity measurement that is being
correlated to a number of coding errors. It is calculated by developing a Control
Flow Graph of the code that measures the number of linearly-independent paths
through a program module.
Lower the Program's cyclomatic complexity, lower the risk to modify and easier
to understand. It can be represented using the below formula:
Cyclomatic complexity = E - N + P
where,
E = number of edges in the flow graph.
N = number of nodes in the flow graph.
P = number of nodes that have exit points
13. Difference formal review and walkthrough(May/June 2011)
Walkthrough:A review of requirements, designs or code characterized by the
author of the object under review guiding the progression of the review.
Review:A process in which one or more persons checks changed documents or
data to determine if the changes are correct.

14. Justify the testing is essential while developing software(Nov/Dec 2012)

Software testing in terms of five essential elements:

A test strategy that tells you what types of testing and the amount of testing
you think will work best at finding the defects that are lurking in the software

A testing plan of the actual testing tasks you will need to execute to carry out
that strategy

Test cases that have been prepared in advance in the form of detailed
examples you will use to check that the software will actually meet its
requirements

Test data consisting of both input test data and database test data to use
while you are executing your test cases, and

A test environment which you will use to carry out your testing.
15. State the advantages of unit testing(Nov/Dec 2012)
Unit Testing reduces the level of bugs in production code.
Unit Testing saves you development time.
Automated tests can be run as frequently as required.
Unit Testing makes it easier to change and refactor code.
Unit Testing can improve the design of code especially with Test-Driven
Development.
Unit Tests are a form of documentation.
 WWW.VIDYARTHIPLUS.COM

16. what are the levels at which testing is done

Unit testing
Integration testing
System testing
Acceptance testing
Regression testing

17.define regression testing

Regression testing is used to check for defects propagated to other modules by

changes made to existing program. Thus, regression testing is used to reduce the side
effects of the changes.

UNIT V
 WWW.VIDYARTHIPLUS.COM

1. What are static and dynamic software testing? (Nov/Dec 2005)

Under Static Testing code is not executed.
Informal Reviews,TechnicalReviews,Walkthrough,Inspection,Static code
Review
Under Dynamic Testing code is executed
Unit Testing,IntegrationTesting,System Testing.

2. What do you mean byversion control (May/June 2006)

Software Version Control is a system or tool that captures the changes to a
source code elements: files, folders, images or binaries.
Version Control Tools track these changes and allows manipulation of versions and
baselines.Many tools do very similar tasks.

3. Define the term baseline in SCM (May/June 2006)

The goal of the baseline is to uniquely identify each version of a software
component or application, and to facilitate detection and correction of configuration
errors.

4. State different techniques of version control? (Nov/Dec 2007)

Local version control system.
Continuous version control system
Distributed version control system.

5. Name one cast tool that you are aware of and describe its features. (Nov/Dec
2007)
The computer aided software engineering tools automatic the project
management activities, manage all the work products. The CASE tools assist to
perform various activities such as analysis, design, coding and testing.

6. State the reason why defect tracking should not be used for employee
performance evaluations? (April/May 2008)
Managing, evaluating and prioritizing these defects is a difficult task. When the
numbers of defects gets quite large, and the defects need to be tracked over
extended periods of time

7. what is the influence of coupling on maintenance. (April/May 2008)

Coupling is the measure of interconnection among modules in a program
structure. It depends on the interface complexity between modules.

8. Differentiate between metric and indicators. (Nov/Dec 2009)

Metric - A quantitative measure of the degree to which a system, component, or
process possesses a given attribute
Indicator - A device or variable that can be set to a prescribed state based on the
results of a process or the occurrence of a specified condition. For example, a flag
or semaphore

9. Who are the stack holders of software projects. (Nov/Dec 2009)

 WWW.VIDYARTHIPLUS.COM

A stack holder is an individual, team, organization, or classes thereof, having an

interest in the realization of the system.
Example-System designer, Programmer, Tester.

10. Give the difference b/w Fuzzy logic sizing and function point sizing.(Apr/May
2010)
Fuzzy logic -Gather size data on previously developed programs, Subdivide
these data into size categories: very large, large, medium, small, very small,
sestablish size ranges, include all existing and expected products Subdivide each
range into subcategories.
Function point- Measure of the functionality delivered by the applications.
Functionality cant be measured directly, it must be derived. indirectly using other
direct measures. Function points are derived using an empirical relationship based
on countable (direct) measures of softwares information domain and assessments
of software complexity.

11. What are the classes of software projects in COCOMO model. (Apr/May 2010)
Constructive COstMOdel is a cost model, which gives the estimate of number of
man-months it will take to develop the software product.
COCOMO applies to three classes of software projects:
Organic projects - "small" teams with "good" experience working with "less
than rigid" requirements

Semi-detached projects - "medium" teams with mixed experience working

with a mix of rigid and less than rigid requirements

Embedded projects - developed within a set of "tight" constraints. It is also

combination of organic and semi-detached projects.(hardware, software,
operational, ...)
12. What is meant by version control(May/Jun 2011)
Software Version Control is a system or tool that captures the changes to a
source code elements: files, folders, images or binaries.
Version Control Tools track these changes and allows manipulation of versions
and baselines.
Many tools do very similar tasks.

13. List the significance of CASE tools(May/Jun 2011)

CASE tools stand forComputerAidedSoftwareEngineering tools
As the name implies they are computer based programs toincrease the
productivity of analysts

14. It is possible to use DRE as a metric for error tracking throughout a software
project?
(Nov/Dec 2012)
DRE is simply a measure of how effectively defects (bugs) are removed at each
stage of the product cycle.
Defect-removal efficiency-the percentage of bugs eliminated by software
reviews, inspections and tests-is a powerful software quality metric that should be
understood by everyone in the software business.
 WWW.VIDYARTHIPLUS.COM

15. What are the metrics used for software cost estimation (Nov/Dec 2012)
A Metric is a measurement of the degree that any attribute belongs to a system,
product or process. For example the number of errors per person hours would be a
metric. Thus, software measurement gives rise to software metrics.
Metrics are related to the four functions of management:
Planning
Organising
Controlling
Improving
Metric Classification Software metrics can be divided into two categories; product
metrics and process metrics.
Product metrics are used to assess the state of the product, tracking risks and
discovering potential problem areas. The team's ability to control quality is
assessed.
Process metrics focus on improving the long term process of the team or
organisation.

16. define software quality

The quality of software is assessed by a number of variables.

These variables can be divided into external and internal quality criteria.
External quality is what a user experiences when running the software in its
operational mode.
Internal quality refers to aspects that are code-dependent, and that are not
visible to the end-user.
External quality is critical to the user, while internal quality is meaningful to the
developer only.

17.what is software configuration management?

software configuration management (SCM) is the task of tracking and controlling

changes in the software, part of the larger cross-discipline field of configuration
management.

18. what is error tracking.

error tracking can also be used to estimate the progress of the project.
it is used to track errors in work products to access the status of a project.

the efficiency of error tracking is calculated as follows.

Defect removal efficiency,DRE=E/(E+D),

where
E-Errors found before shipment
D-errors found during operation.