Q.151.How do we compute the “Expected
Value” for Software Size?
• Ans. Expected value for estimation
variable (size), S, can be compute as Weighted Average of Optimistic (opt) most
likely (m), and Pessimistic (pess) estimates.
• S = (opt + 4 m + pess ) / 6
Q.152. What is an Object Point?
Ans. Object Point means: Count is determined by
multiplying original number of object instances by weighting factor and summing
to obtain total object point count.
Q.153. List out the basic principles
of software project scheduling?
Ans. Basic Principles of Software Project Scheduling
are:
•
Compartmentalization •
Interdependency
•
Time Allocation •
Effort Validation
•
Defined Responsibilities Defined Outcomes
•
Defined Milestones.
Q.154. Write the objective of project
planning?
Ans. It is to provide a framework that enables the
manager to make reasonable estimates of resources, cost and schedule.
Q.155. What is FP? How it is used for
project estimation?
Ans. Function Point: It is used as the estimation
variable to size each element of the software. It requires considerably less
details. It is estimated indirectly by estimating the number of inputs,
outputs, data files, external interfaces.
Q.156. What is LOC? How it is used for
project estimation?
Ans. LOC: Lines of Code. It is used as estimation
variable to size each element of the software. It requires considerable level
of detail.
Q.157. Write the formula to calculate
the effort in persons-months used in Dynamic multi variable Model?
Ans. Software Equation: E = [LOC’ B°333/P]3 ‘(l/tj
Where E is effort in person-months, t is project duration, B is special skills
factor, P is productivity parameter.
Q.158. What is called as an object
point?
Ans. It is an
indirect software measure that is computed using counts of the number of
screens, reports and components.
Q.159. Define measure.
Ans. Measure is defined as a quantitative indication of
the extent, amount, dimension, or size of some attribute of a product or
process.
Q.160. Define metrics.
Ans. Metrics is defined as the degree to which a system
component or process possesses a given attribute.
Q. 161. What are the types of metrics?
Ans. The types of metrics are:
Ø
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.
Q.162. What are the advantages and
disadvantages of size measure?
Ans. The advantages and disadvantages of size measure
are:
Advantages:
Ø
Artifact
of software development which is easily counted.
Ø
Many
existing methods use LOC as a key input.
Ø
A
large body of literature and data based on LOC already exists.
Disadvantages:
Ø
This
method is dependent upon the programming language.
Ø
This
method is well designed but shorter program may get suffered.
Ø
It
does not accommodate non procedural languages.
Ø
In
early stage of development it is difficult to estimate LOC.
Q.163.
Write short notes on the various estimation techniques.
Ans. The various estimation techniques are:
Ø
Algorithmic cost modeling: The cost estimation is based on the
size of the software.
Ø
Expert Judgement : The experts from software development
and the application domain use their experience to predict software costs.
Ø
Estimation by analogy : The cost of a project is computed by
comparing the project to a similar project in the same application domain and
then cost can be computed.
Ø
Parkinson’s law : The cost is determined by available
resources rather than by objective assessment.
Ø
Pricing to win : The project costs whatever the
customer is ready to spend on it.
Q.164.
What is COCOMO model?
Ans. Constructive Cost Model is a cost model, which
gives the estimate of number of man-months it will take to develop the software
product.
Q.165.
Give the procedure of the Delphi method.
Ans. The procedure of the Delphi method consists of:
1. The co-ordinator presents a
specification and estimation form to each expert.
2. Co-ordinator calls a group meeting in
which the experts discuss estimation issues with the co-ordinator and each
other.
3. Experts fill out forms anonymously.
4. Co-ordinator prepares and distributes
a summary of the estimates.
5. The Co-ordinator then calls a group
meeting. In this meeting the experts mainly discuss the points where their
estimates vary widely.
6. The experts again fill out forms
anonymously.
7. Again co-ordinator edits and
summarizes the forms, repeats steps 5 and 6 until the co-ordinator is satisfied
with the overall prediction synthesized from experts.
Q.166.
What is the purpose of timeline chart?
Ans. The purpose
of the timeline chart is to emphasize the scope of the individual task. Hence
set of tasks are given as input to the timeline chart.
Q.167 What is EVA?
Ans. Earned Value Analysis is a technique of
performing quantitative analysis of the software project. It provides a common
value scale for every task of the software project. It acts as a measure for
software project progress.
Q.168. What is Metrics?
Ans. Metrics in a project management context is about
measurements. Measuring your progress in order to know where you are and what
mid course corrections you need to take to achieve your goals.
Q.168. What are the formal models of
size estimation?
Ans. The formal models of size estimation are:
• Lines of code
• Function points
Q.169. What is variance?
Ans. For any estimate the metric to determine its
effectiveness is the variance.
Q.170. How to define variance?
Ans. Variance
= (planned-Actual)/Planned * 100
Q.171. What is meant by activity
schedule?
Ans. Activity schedule indicates the planned start and
completion dates for each activity.
Q.172. What is mean by resource
schedule?
Ans. Resource schedule shows the date on which each
resource will be required and the level of that requirements are identified.
Q.173. What are the various types of
charts used in visualizing progress?
Ans. The various types of charts used in visualizing
progress are:
• Gannt chart, • Slip chart
• Bar chart • Time line chart.
Q.174. What is review point?
Ans. Project level progress reviews that generally take
place at particular points during the life cycle of project is known as review
point.
Q.175. What are the Basic Principles
of Software Testing?
Ans. Basic Principles of Software Testing are:
·
Traceable
to Customer Requirements
·
Planned
long before Testing begins
·
Pareto
Principles applied to software testing
·
Begin
small and progress towards testing.
·
Exhaustive
testing is not possible.
·
Conducted
by independent third party.
Q.176.
List out the Characteristics of Testability of Software?
Ans.
Characteristics of
Testability of Software?
• Operability • Observability
• Controllability • Decomposability
• Simplicity •
Stability
• Understandability
Q.176. List out Various Methods for
Finding Cyclomatic Complexity?
Ans.
Various Methods for
finding Cyclomatic Complexity are:
·
Number
of Regions
·
Cyclomatic
Complexity V(G) , for flow Graph
V(G)=E-N+2
·
Cyclomatic
Complexity
V(G)=P+2
·
Error
diagnosis and Correction are simplified.
·
Progress
is easy to assess.
Q.11.
Define Smoke Testing ?
Ans.
Smoke Testing is
Integration Testing and Commonly used when software products are being
developed.
Q.11.
What are the attributes of Good Test?
Ans.
Attributes of Good
Test are:
|
·
High
Probability of Finding errors
·
“Best
of Breed”
|
·
Not
Redundant
·
Neither
too Simple nor too complex
|
Q.11.
Define White Box Testing?
Ans. White Box Testing is also called Glass
Box Testing in this test case design uses control Structure of Procedural
Design to derive test cases
Q.11.
Define Basic path Testing
Ans.
Basic Path Testing:
·
White
Box Testing
·
Enable
test case designer to derive a logical complexity measure of a procedural
design.
·
Use
this measure as a Guide for defining a basis set of execution paths.
Q.11.
Define the terms:
a)
Graph Matrices.
b)
Connection Matrices.
Ans.
Graph Matrices:
·
To
develop software tool the data structure used is graph Matrix.
·
Square
Matrix
·
Size
equals number of nodes on the Flow graph
Connection
Matrices:
·
It
Link Weight = 1= > Connection Exists
·
It
Link Weight=1=>Connection Does not Exists.
Q.11.
What is Behavioural Testing?
Ans.
Behavioral Testing :
·
Also
know as Black Box Testing.
·
Focuses
on Functional Requirement of software.
·
Enables
Software engineer to derive set of input condition that fully exercise all
functional requirement of a software.
Q.11.
What are the benefits of Smoke Testing?
Ans.
Benefits of doing Smoke
Testing are:
·
Integration
Risk is Minimized.
·
Quality
of end-product is improved.
·
Error
diagnosis and Correction are simplified.
·
Progress
is easy to assess.
Q.11.
What errors are commonly found during Unit Testing?
Ans.
Errors commonly found
during Unit Testing are:
·
Misunderstood
or incorrect arithmetic precedence
·
Mixed
Mode Operations
·
Incorrect
Initializations
·
Precision
Accuracy
·
Incorrect
Symbolic representation of expression.
Q.177.What problems may be encountered
when Top-Down Integration is chosen?
Ans. Following problems may be encountered when Top
Down Integration is chosen:
·
Develop
stubs that perform limited functions that simulate the actual module.
·
Integrate
the software from the bottom of the hierarchy upward.
Q.
178. What are the Steps in Bottom-Up Integration?
Ans. Steps in Bottom-Up Integration are:
·
Low
level components are combined into clusters perform specific software sub
function.
·
Driver
is written to coordinate test case input and output.
·
Cluster
is tested.
·
Drivers
are removed and clusters are combined moving inward in program structure.
Q.
179. What is Regression Testing?
Ans. Regression Testing means Re-execution of subset of
tests that have already been conducted and to ensure changes have not
propagated unintended side effects.
Q.
180. What are the Characteristics of “Critical Module”?
Ans. Characteristics of “Critical Module”
are
·
Addresses
several software requirements
·
Has
High Level of Control
·
Complex
or error prone
·
Has
Definite Performance Requirements.
Q.
181. What are the Properties of Connection Matrices?
Ans.
Properties of
Connection Matrices are:
·
Probability
that link will execute
·
Processing
time expended during traversal of link
·
Memory
required during traversal of link
·
Resource
required during traversal of link.
Q.
182. What is Flow Graph Notation?
Ans. Flow Graph Notation means Simple notation for
representing Control Flow. It is drawn only when Logical Structure of component
is complex.
Q.183.
Define Cyclomatic Complexity?
Ans. Cyclomatic Complexity is a Quantitative measure of
Logical Complexity and it is the number of Independent Paths in the basis set
program.
Q. 184. What is Equivalence Partition?
Ans. Equivalence Partitions Derives a input domain of
a program into classes of data from which test cases are derived. it is a Set
of Objects have link by relationships as Symmetric, Transitive and Reflexive an
equivalence class is present.
Q.185. List out the possible errors of
Black Box Testing?
Ans. Errors of Black Box Testing are:
·
Incorrect
or Missing Functions
·
Interface
Errors
·
Errors
in Data Structures or external databases
·
Behavioural
or Performance errors
·
Initialization
or Termination errors.
Q.186. What are the steps followed in
testing?
Ans. The steps followed in testing are:
i.)
Unit testing : The individual components are tested
in this type of testing.
ii.)
Module testing: Related collection of independent
components are tested.
iii.)
Sub-system testing : This is a kind of integration
testing. Various modules are integrated into a sub-system and the whole
sub-system is tested.
iv.)
System testing: The whole system is tested in this
system.
v.)
Acceptance testing : This type of testing involves testing
of the system with customer data if the system behaves as per customer need
then it is accepted.
Q.187.
Define software testing? -
Ans. Software testing is a critical element of
software quality assurance and represents the ultimate review of specification,
design, and coding.
Q.188. What are the objectives of
testing?
Ans. The objectives of testing are:
(i)
Testing
is a process of executing a program with the intend of finding an error.
(ii)
A
good test case is one that has high probability of finding an undiscovered
error.
(iii)
A
successful test is one that uncovers as an-yet undiscovered error.
Q.189. What are the testing principles
the software engineer must apply while performing the software testing?
Ans. The testing principles to be applied are:
(i)
All
tests should be traceable to customer requirements.
(ii)
Tests
should be planned long before testing begins.
(iii)
The
pareto principle can be applied to software testing-80% of all errors uncovered
during testing will likely be traceable to 20% of all program modules.
(iv)
Testing
should begin “in the small” and progress toward testing “in the large”.
(v)
Exhaustive
testing is not possible.
(vi)
To
be most effective, an independent third party should conduct testing.
Q.190. What are the two levels of
testing?
Ans. The two levels of testing are
(i)
Component testing: Individual components are tested.
Tests are derived from developer’ s experience.
(ii)
System Testing The group of components are integrated
to create a system or sub-system is done. These tests are based on the system
specification.
Q.191. What are the various testing
activities?
Ans. The various testing activities
are:
(i) Test
planning (ii) Test case design
(iii Test
execution (iv) Data collection
(v) Effective
evaluation
Q.192.
Write short note on black box testing.
Ans. The black
box testing is also called as behavioral testing. This method fully focuses on
the functional requirements of the software. Tests are derived that fully
exercise all functional requirements.
Q.193.
What is equivalence partitioning?
Ans.
Equivalence partitioning is a black box technique that divides the input domain
into classes of data. From this data test cases can be derived. Equivalence
class represents a set of valid or invalid states for input conditions.
Q.194.
What is a boundary value analysis?
Ans. A boundary value analysis is a testing
technique in which the elements at the edge of the domain are selected and
tested. It is a test case design technique that complements equivalence
partitioning technique. Here instead of focusing on input conditions only, the
test cases are derived from the output domain.
Q.195. What are the reasons behind to
perform white box testing?
Ans. There are three main reasons behind performing the
white box testing.
1. Programmers may have some incorrect
assumptions while designing or implementing some functions. Due to this there
are chances of having logical errors in the program. To detect and correct such
logical errors procedural details need to be examined.
2. Certain assumptions on flow of control
and data may lead programmer to make design errors. To uncover the errors on
logical path, white box testing is must.
3. There may be certain typographical
errors that remain undetected even after syntax and type checking mechanisms.
Such errors can be uncovered during white box testing.
Q.196.
What is cyclomatic complexity?
Ans.
Cyclomatic complexity is software metric that gives the quantitative measure of
logical complexity of the program.
The Cyclomatic
complexity defines the number of independent paths in the basis set of the
program that provides the upper bound for the number of tests—that must be
conducted to ensure that all the statements have been executed at least once.
Q.197.
How to compute the cyclomatic complexity?
Ans. 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.
2. Cyclomatic complexity, V(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
3. V(G)
= P + 1
Where P is the number
of predicate nodes contained in the flow graph.
Q.198. What are the various testing
strategies for conventional software?
Ans. The various testing strategies are:
(i) Unit testing (ii) Integration testing
(iii) Validation
testing (iv) System testing.
Q.199.
Write about drivers and stubs.
Ans. Drivers and stub software need to be developed to
test incompatible software.
Ø
The
“driver” is a program that accepts
the test data and prints the relevant results.
Ø
The
“stub” is a sub-program that uses
the module interfaces and performs the minimal data manipulation if required.
Q.200.
What are the approaches of integration testing?
Ans. The
integration testing can be carried out using two approaches.
1. The
non-incremental testing.
2. Incremental
testing.
Q.201. What are the advantages and
disadvantages of big-bang?
Ans. The advantages and disadvantages of big bang are:
Advantages:
Ø
This
approach is simple.
Disadvantages:
Ø
It
is hard to debug.
Ø
It
is not easy to isolate errors while testing.
Ø
In
this approach it is not easy to validate test results.
Ø
After
performing testing, it is impossible to form an integrated system.
Q.202. What are the benefits of smoke
testing?
Ans. The benefits of smoke testing are:
Ø
Integration
risk is minimized.
Ø
The
quality of the end-product is improved.
Ø
Error
diagnosis and correction are simplified.
Ø
Assessment
of program is easy.
Q.203.
Distinguish between Alpha and Beta testing.
Ans. 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 developer’s 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 customer’s site.
Q.203. What are the types of static
testing tools?
Ans. There are three types of static testing tools.
Ø
Code based testing tools : These tools take source code as
input and generate test cases.
Ø
Specialized testing tools : Using this language the detailed test
specification can be written for each test case.
Ø
Requirement-based testing tools: These tools help in designing the as
per user requirements.
Q.204.
What are the activities that make up testing?
Ans. The activities that make up testing
are:
• Test
specification • Test design
• Test
development • Test registration
• Test
execution • Test maintenance.
Q.205. List the various types of
testing done during product life cycle.
Ans. The various types of testing done
during product life cycle are:
• White box
testing • Black box testing
• Integration
testing • System testing
• Installation
testing • Regression testing
• Acceptance
testing
Q.206.
What is testing?
Ans. Testing
refers to the activities that are carried out to ensure that the final software
product meets the requirements that the product is intended to satis1r.
Q.207.
What are the activities that make up testing?
Ans. The activities that make up testing
are:
• Test
specification • Test design
• Rest
development • Test Registration
• Test
execution • Test maintenance
Q.208.
What is done in test design step?
Ans. The details of the layout, tooling and standards
required for test development are designed in this stage.
Q.209.
List some of the testing done during SDLC.
Ans. White box testing, black box testing, integration
testing, system testing, installation testing. Regression testing, Acceptance
testing.
Q.210.
What is functionality testing?
Ans. It is a black box testing which exercises the
basic functionality of the product from an external; perspective.
Q.211.
What is interface testing?
Ans. Testing which tests the interfaces
among modules.
Q.212.
What do system testing do?
Ans. System testing focus on stressing the system
under extreme conditions and ensuring that if there is any failure, it is well
managed.
Q.213. What are the steps carried out in installation
testing?
Ans. The steps carried out in installation testing
are:
•
Packaging • Documenting
• Installing • Verifying.
Q.214.
Define regression testing.
Ans. Regression tests are defined as those tests that
are run to verify that problems do not resurface or regress.
Q.215 Explain Integrated testing team
model?
Ans. There in one project manage who manages both the
development and the testing functions.
Q.216 What are the objective of Formal
Technical Reviews.
Ans. The Objective of Formal Technical Reviews are:
·
Uncover
errors in function, logic and implementation for representation of software.
·
Software
represented according to predefined standard.
·
Verify
software under review meets requirements
·
Achieve
software developed in Uniform Manner.
·
Make
projects more manageable.
Q.217
What are the various types of system testing?
Ans.
Various types of
system testing are:
1. Recovery testing- is intended to check the system’ a ability to
recover from failures.
2. Security
testing- verifies
that system protection mechanism prevent improper penetration or data
alteration.
3. Stress
testing- Determines
breakpoint of a system to establish maximum service level.
4. Performance
testing- evaluates
the run time performance of the software, especially real- time software.
Q.218
Define debugging.
Ans. Debugging is defined as the process of removal of
defect. It occurs as a consequence of successful testing.
Q.219 What are the common approaches
in debugging?
Ans. The common approaches tin debugging are:
·
Brute force method: The memory dumps and run- time tracks
are examined and program with write statements in loaded to obtain clues to
error causes.
·
Back tracking method: The source code is examined by looking
backwards from symptom to potential causes or errors.
·
Causes eliminations method: This method uses binary partitioning
to reduce the number of location where errors can exists.
Q.220
Write about the types of project plan.
Ans.
The types of project
plan are.
Ø
Quality plan: This plan describes the quality
procedures and standards that will be used in a project.
Ø
Validation plant: This plan describes the approach,
resources and schedule required for system validation.
Ø
Configuration management plan: This plan focuses on the
configuration management procedures and structures to be used.
Ø
Maintenance plan: The purpose of maintenance plan is to
predict the maintenance requirements of the system, maintenance cost and effort
required.
Ø
Staff development plan: This plan describes how to develop
this skills and experience of the project team members.
Q.221 What are the metrics computed
during error tracking activity?
Ans. The metrices computed during error tracking
activity are:
Ø
Errors
per requirement specification page.
Ø
Errors
per component- design level.
Ø
Errors
per component- code level.
Ø
DRE-
requirement analysis
Ø
DRE-
architectural analysis
Ø
DRE-
component level design
Ø
DRE-
coding .
Q.222
Why software change occurs?
Ans.
Software change
occurs because of the following reasons:
Ø
New
requirements emerge when the software is used.
Ø
The
business environment changes.
Ø
Errors
need to be repaired.
Ø
New
equipment must be accommodated.
Ø
The
performance or reliability may have to be improved.
Q.223
Write about software change strategies.
Ans. The software change strategies that could be
applied separately or together are:
Ø
Software maintenance: The changes are made in the software
due to requirements.
Ø
Architectural transformation: It is the process of changing one
architecture into another form.
Ø
Software re-engineering:
New feature can be added to existing system and then the system is
reconstructed for better use of it in future.
Q.224
Define maintenance.
Ans. Maintenance is defined as the process in which
changes are implemented by either modifying the existing system’s architecture
or by adding new components to the system.
Q.225 What are the types of software
maintenance?
Ans. Types of software maintenance are :
Ø
Corrective Maintenance: Means the maintenance for correcting
the software faults.
Ø
Adaptive maintenance; Means maintenance for adapting the
change in environment.
Ø
Perfective maintenance: Means modifying or enhancing the
system to meet the new requirements.
Ø
Preventive maintenance: Means changes made to improve future
maintainability.
Q.226
Who reviews or approves the change request?
Ans. The configuration control board review and
approves the change request.
Q.227
Give some design principles for maintainability.
Ans. Some design principles for maintainability are:
·
Module
level accountability
·
Proper
documentation
Q.228
What is done is maintenance phase?
Ans. The maintenance phase deals with the process of
evaluating the customer’s product change request, making necessary changes to
the product.
Q.229
List the activities done in maintenance phase.
Ans. The activities done in maintenance phase are.
·
Problem
reporting.
·
Problem
resolution.
·
Solution
distribution.
·
Proactive
defect prevention.
Q.230
What is problem reporting?
Ans. Once the user finds the difference in using the
product behavior and the behaviors that it has to be, the problem reporting
takes place.
Q.231. What is the Use of Process Technology
Tools?
Ans. Use of Process Technology Tools is to help
Software Organizations to:
1. Analyze their current process
2. Organize work task
3. Control And Monitor Progress
4. Manage Technical Quality 5.
Q.232. List out the basic principles
of software project scheduling?
Ans. Basic Principles of Software
Project Scheduling are:
·
Compartmentalization
• Interdependency
·
Tune
Allocation • Effort Validation
·
Defined
Responsibilities • Defined Outcomes
·
Defined
Milestones.
Q.233. What Architectures are defined
and developed as part of BPE?
Ans. Following Architectures are defined and developed
as part of BPE:
·
Data
Architecture ‘Applications Architecture
·
Technology
Architecture.
Q.234. What is the Origin of changes
that are requested for software?
Ans. Following are the Origin of Changes:
·
New
Business or Market Condition
·
New
Customer Needs
·
Reorganization
or business growth/downsizing
·
Budgetary
or Scheduling constraints.
Q.235.
List out the Elements of SCM?
Ans. Elements of SCM arc:
• Component Elements • Process Elements
• Construction
Elements • Human Elements.
Q.236. What are the Features supported
by SCM?
Ans. Features supported by SCM are:
·
Versioning
·
Dependency
tracking and change Management
·
Requirements
tracking
·
Configuration
Management
·
Audit
trails.
Q.237. What are the Objectives of SCM
Process?
Ans. Objectives of SCM Process are:
o
Identify
all items, collectively define software
configuration
o
Manage
changes to one or more these items
o
Facilitate
construction of different version of an application
o
Ensure
that the software quality is maintained.
Q.238.
What are the Issues to be considered for developing tactics for Web App
Configuration Management?
Ans.
The issues to
be considered for developing tactics for Web App Configuration Management are:
• Context • People
• Stability.
Q.239.
Define CASE Tools.
Ans. CASE Tools stands for Computer Aided Software
Engineering. It is a System software that provide Automated support for
software process activities. It Includes program used to support software
process activities such as Requirement Analysis, System Modeling. Debugging and
Testing.
Q.24O. What are the type of CASE
Tools?
Ans. There are two types of CASE Tools:
·
Upper
CASE Tools
·
Lower
CASE Tools.
Q.241.
Write a short note on 4GT.
Ans. Fourth Generation Techniques. 4GT encompasses a
broad array, of software tools. Each tool enables the software developer to
speci1’ some characteristics of software at a higher level.
Q.242. List the tools or methods
available for rapid prototypiug.
Ans. The tools or methods available for rapid
prototyping are:
i.
4GT.
ii.
Reusable software components.
iii.
Specification and prototyping environment.
Q.
243. What are the aspects of software reuse?
Ans.
The aspects of
software reuse are:-
1) Software development with reuse
2) Software development for reuse
3) Generator based reuse
4) Application system reuse.
Q.244.
Define SCM.
Ans. It. is an umbrella activity that is applied
throughout software process. It has a set of tracking and control activities
that begin when a software engineering project begins and terminates only when
the software project is taken out of operation.
Q.245.
List the SCM Activities.
Ans. The SCM Activities are:
i.)
Identify
a change
ii.)
Control
change
iii.)
Ensure
that change is being properly implemented
iv.)
Report
changes to others who may have an interest.
Q.246.
What is meant by software reusability?
Ans. A
software component should be designed and implemented so that it can be reused in
many different programs.
Q.247.
What is CASE?
Ans. CASE: Computer Aided Software Engineering CASE
provides the engineer I the ability to automate manual activities and to
improve engineering insight.
Q.248. Write the distinction between
SCM and Software Support.
Ans. SCM : Lt has a set of tracking and
control activities that begin when a Software engineering project begins and
terminates only when the software project is taken out of operation.
Software
support: It has a set
of software engineering activities that occur a software has been delivered to
the customer and put into operation.
Q.249. What is the difference between
basic objects and aggregate objects used software configuration.
Ans. Basic
Objects: It represents unit of text. e.g., Section of requirement specifications,
Source listing for a component.
Aggregate
Objects: Collection
of basic: objects. And other aggregate objects e.g Full design specification
is.
Q.250. What is software reuse? Explain
the various aspects of software reuse.
Ans. Software reuse means a software component should
be designed and implement so that it can be reused in many different programs.
The various aspects of software reuse:
o
Software
development with reuse
o
Software
development for reuse Generator based reuse
o
Application
system reuse
Comments
Post a Comment