CS8494 – SOFTWARE ENGINEERING Question Bank 2017 Regulation

www.AUNewsBlog.net

UNIT I - SOFTWARE PROCESS AND AGILE DEVELOPMENT

PART – A

1. Define Software Engineering.

Software Engineering is the application of a systematic, disciplined, quantifiable
approach to the development, operation and maintenance of software, that is, the
application of engineering to software.

2. Define Software.
Software is instructions that when executed provide desired features, functions
and performance.

3. What are the characteristics of the software?

 Software is engineered, not manufactured.
 Software does not wear out.
 Most software is custom built rather than being assembled from components.

4. What are the various categories of software/software application domains?

 System software
 Application software
 Engineering/Scientific software
 Embedded software
 Web Applications
 Artificial Intelligence software

5. What are the challenges in software?

 Copying with legacy systems.
 Heterogeneity challenge
 Delivery times challenge

6. Define software process.

Software process is defined as the structured set of activities that are required to
develop the software system.

7. What are the fundamental activities of a software process?

 Specification
 Design and implementation
 Validation
 Evolution

8. What are the umbrella activities of a software process?

 Software project tracking and  Software Configuration
control. Management.
 Risk management.  Work product preparation and
 Software Quality Assurance. production.
 Formal Technical Reviews.  Reusability management.
 Measurement

9. What are the merits of incremental model?

Page 2
www.AUNewsBlog.net
CS8494 – SOFTWARE ENGINEERING Question Bank 2017 Regulation

www.AUNewsBlog.net
i. The incremental model can be adopted when there are less number of people
involved in the project.
ii. Technical risks can be managed with each increment.
iii. For a very small time span, at least core product can be delivered to the
customer.

10. List the task regions in the Spiral model.

 Customer communication – In this region it is suggested to establish customer
communication.
 Planning – All planning activities are carried out in order to define resources
timeline and other project related activities.
 Risk analysis – The tasks required to calculate technical and management risks.
 Engineering – In this the task region, tasks required to build one or more
representations of applications are carried out.
 Construct and release – All the necessary tasks required to construct, test, install
the applications are conducted.

11. What are the drawbacks of spiral model?

i. It is based on customer communication. If the communication is not proper then the
software product that gets developed will not be the up to the mark.
ii. It demands considerable risk assessment. If the risk assessment is done properly then
only the successful product can be obtained.

12. What is System Engineering?

System Engineering means designing, implementing, deploying and operating systems
which include hardware, software and people.

13. List the Prescriptive Process Models.

 The Waterfall Model
o V-Model
 Incremental Process Model
 Evolutionary Process Models
o Prototyping
o The Spiral Model
 Concurrent Models

14. What are the various steps in Waterfall Model?

 Communication
 Planning
 Modeling
 Construction
 Deployment
15. What are the advantages of evolutionary prototyping?
i. Fast delivery of the working system.
ii. User is involved while developing the system.
iii. More useful system can be delivered.
iv. Specification design and implementation work in co-ordinate manner.

16. What are the various Rapid prototyping techniques?

i. Dynamic high level language development.
Page 3
www.AUNewsBlog.net
CS8494 – SOFTWARE ENGINEERING Question Bank 2017 Regulation

www.AUNewsBlog.net
ii. Database programming.
iii. Component and application assembly

17. List the various Specialized Process Models.

 Component based development
 Formal methods model
 Aspect-Oriented software development

18. What is EVA?

Earned Value Analysis is a technique of performing quantitative analysis of the software
Project. It provides a common value scale for every task of software project. It acts as a measure
for software project progress.

19. List the 4 P’s that focus on Software Project Management.

 People
 Product
 Process
 Project

20. Define Software Project Scheduling.

Software Project Scheduling is an action that distributes estimated effort across the
planned project duration by allocating the effort to specific software engineering tasks.

21. Define Agile Process.

 The heavy weight plan based software development approach was used to develop any
software product.
 In this approach too many things are done which were not directly related to software
product being produced.
 The agile processes are the light-weight methods are people-based rather than plan-based
methods.

Page 4
www.AUNewsBlog.net
CS8494 – SOFTWARE ENGINEERING Question Bank 2017 Regulation

www.AUNewsBlog.net
PART – B

1. What are the differences between system engineering & software engineering? State and
explain the stages that distinguish the two. (April/May 2008)
2. What are the necessities of life cycle model? Elaborate on the various issues of software life
cycle. (April/May 2008)(April/May 2011)
3. Explain in detail the following software process models with a neat diagram. (April/May
2008)
i. Incremental Process Model.
ii. Evolutionary Process Model
4. Explain the spiral model. What are the task regions in the spiral model? How does the
customer wins by getting the system or product that satisfies the majority of the customer’s
needs and the developer wins by working to realistic and achievable budgets and deadline?
5. Explain the system engineering hierarchy. What does a system engineering model
accomplish? What are the restraining factors to construct a system model? (May/June
2007)(Nov/Dec 2009)
6. Explain the linear software life cycle model with suitable illustration. Bring out the demerits
of this model. (May/June 2007)
7. Explain Software Life Cycle .List all life cycle model and explain spiral model with neat
diagram(May/June 2012)(Nov/Dec 2008)
8. Describe waterfall, incremental, iterative waterfall, spiral model based on SLCS and compare.
(Nov/Dec 2012)

Page 5
www.AUNewsBlog.net
CS8494 – SOFTWARE ENGINEERING Question Bank 2017 Regulation

www.AUNewsBlog.net

UNIT: II - REQUIREMENTS ANALYSIS AND SPECIFICATION

PART – A

1. What are functional requirements?

Functional requirements are statement of services the system should provide, how
the system should react to particular input and how the system should behave in
particular situation. Functional requirements
 Describe functionality or system services
 Depend on the type of software, expected users and the type of the system
where the software is used.

2. What are non-functional requirements?

Non-functional requirements are constraints on the services or functions offered
by the system such as timing constraints, constraints on the development process and
standards. They
 Define system properties and constraints
 Process requirements may also be specified

3. Classify non-functional requirements.

Non-functional requirements are classified into following
 Product requirements
 Organizational requirements
 External requirements

4. What are User Requirements?

User requirements should describe functional and non-functional requirements so
that they are understandable by system users who don’t have detailed technical
knowledge. User requirements are defined using natural language, tables and diagrams.

5. What are System Requirements?

System Requirements are
 More detailed specification of user requirements
 Serve as a basis for designing the system.
 May be used as part of the system contract.
 They can be expressed using system models.

6. Define Requirements Engineering.

Requirements engineering is the systematic use of proven principles, techniques,
languages and tools for the cost effective analysis, documentation and on-going evolution
of user needs and the specification of the external behavior of a system to satisfy those
user needs.

7. What is meant by feasibility study?

Feasibility study decides whether or not the proposed system is worthwhile. It a
short focused study that checks
 If the system contributes to the organizational objectives

Page 6
www.AUNewsBlog.net
CS8494 – SOFTWARE ENGINEERING Question Bank 2017 Regulation

www.AUNewsBlog.net
 If the system can be engineered using current technology and within
budget.
 If the system can be integrated with other systems that are used.

8. What are the various steps in requirement engineering process?

The requirement engineering process can be described in five distinct steps
 Requirements elicitation
 Requirement analysis and negotiation
 Requirement specification
 System modeling
 Requirements validation
 Requirements management

9. What is Requirements Elicitation?

Requirements elicitation involve s asking the customers, the users and others the
objectives of the system or product, what is to be accomplished, how the system or
product fits in to the needs of the business and finally how the system or product is to be
used on a day-to-day basis.

10. What is the function of requirement analysis and negotiation?

Requirement analysis categorizes requirements and organizes them into related
subsets, explores each requirement in relationship to others; examines requirements for
consistency, omissions and ambiguity; and ranks requirements based on the needs of
customers.

11. Define SRS / Software Requirements Document.

It is an official statement of what the system developers should implement. It
should include both the user requirements of a system and a detailed specification of the
system requirements.

12. List the characteristics of SRS.

The characteristics of SRS are
 Correct
 Unambiguous
 Complete
 Consistent
 Specific
 Traceable

13. What is meant by Specification?

A specification can be a written document, a graphical model, a formal
mathematical model, a collection of usage scenarios, a prototype or any combination of
these.

14. Define Ethnography.

It is a technique of observation which is used to understand social and
organizational requirements. It can be combined with prototyping. The two types of
requirements are
 Requirements obtained from working style of people

Page 7
www.AUNewsBlog.net
CS8494 – SOFTWARE ENGINEERING Question Bank 2017 Regulation

www.AUNewsBlog.net
 Requirements obtained from inter activities performed by the people.

15. Define Requirement Validation.

Requirements validation examines the specification to ensure that all system
requirements have been stated unambiguously; that inconsistencies, omissions and errors
have been detected and corrected; and that the work products conform to the standards
established for the process, the project and the product.

16. What is the function of Requirement Management?

Requirement management is a set of activities that help the project team to
identify control, and track requirements, and changes to requirements at any time as the
project proceeds.

17. Mention the use of Petri nets.

 Petri nets can be used for design
 It possesses the expressive power necessary for specifying synchronization
aspects of real-time systems.

18. What are the four parts of Petri nets?

The four parts of Petri nets are
 A set of places P
 A set of transitions T
 An input function I
 An output function O

19. Differentiate Cardinality and Modality.

Cardinality Modality
Cardinality is the specification of the Modality of a relationship is 0 if there is no
number of occurrences of one object that explicit need for the relationship to occur
can be related to the number of occurrences or the relationship is optional. The
of another object modality is 1 if an occurrence of the
relationship is mandatory

20. Define Data Flow Diagrams (DFD).

A data flow diagram is a graphical representation that depicts information flow
and the transforms that are applied as data move from input to output.

21. List any four guidelines for creating DFDs.

The four guidelines for creating DFDs are:
 The level 0 dataflow diagram should depict the software as a bubble.
 Primary input and output should be carefully noted.
 All arrows and bubbles should be labeled with meaningful names.
 One bubble at a time should be refined.

22. Define Data Dictionary.

The data dictionary is an organized testing of all data elements that are relevant to
the system so that both the user and system analyst will have a common understanding
input, outputs, components of stores and intermediate calculations. It is proposed as
quasi-formal grammar during structured analysis.
Page 8
www.AUNewsBlog.net
CS8494 – SOFTWARE ENGINEERING Question Bank 2017 Regulation

www.AUNewsBlog.net

23. List the information that the data dictionary contains.

The data dictionary contains
 Name of the data item
 Aliases (other names)
 Description/purpose
 Related data items
 Range of value
 Data structure definition/form
 Where used/ how used
 Supplementary information

24. Differentiate ERM, ERAM and ERD.

Entity-Relationship Entity-Relationship Entity-Relationship

Modeling (ERM) Attribute Modeling Diagram (ERD)
(ERAM)
Entity-Relationship Entity-Relationship Entity-Relationship
Modeling is a semiformal Attribute Modeling shows Diagram is intended for the
data oriented technique for data entities, associated design of relational database
specifying a product. It attributes and relationship systems which is used to
emphasis on data instead of between these entities. represent data objects and
operations and specify their relationships.
databases.

PART B

1. Discuss in details about the elements in data modeling. (May/June 07).

2. Explain the various prototyping methods and tools used for requirement analysis.
(May/June07)
3. With a suitable example explain about the application of use cases in deriving the scenarios.
4. Explain software prototyping. What are the various prototyping methods and tolls.
5. Explain with example diagram the functional and behavioral modeling. How do we model
the software’s reaction to some external event?
6. State and explain the requirements engineering tasks in detail.
7. Describe the primary differences between structured analyses and object oriented analysis.
8. Write a detailed note on scenario based modeling.
9. Why is traceability an important aspect of requirements management? Why context system
models are useful for requirement validation?
10. Describe how Software requirements are documented? State the importance of
documentation.

Page 9
www.AUNewsBlog.net
CS8494 – SOFTWARE ENGINEERING Question Bank 2017 Regulation

www.AUNewsBlog.net

UNIT: III - SOFTWARE DESIGN

PART – A

1. List two principles of good design. (Nov/Dec2013)

 Models should be easily understandable
 Both internal and external interfaces should be designed with care.

2. Define interface analysis.

Interface analysis is to understand the problem before attempting to deign a solution.
It means understanding
 People
 Tasks
 Content
 Environment

3. Define architectural mapping using data flow.

A mapping technique called structural design is characterized as a data flow
oriented design method because it provides a convenient transition from a data flow
diagram to software architecture.

4. Define Software Quality. (Nov/Dec2013)

Software quality is defined as the degree to which software meets customer
requirements.

5. What are the types of prototype? (Nov/Dec2013)

 Built-in prototype
 Throw away prototype

6. Distinguish verification and validation. (May/June 2014) (April/May2011) (Nov/Dec

2010)
S.No Verification Validation
1 The set of activities that ensure that The set of activities that ensure that the
software correctly implements a software has been built is traceable to
specific funaction. customer requirements.
2 Verification represents the set of Validation represents the set of
activities that are carried out to confirm activities that ensure that the software
that the software correctly implements that has been built is satisfying the
the specific functionality. customer requirements.

7. Define Component Level design.

Page 10
www.AUNewsBlog.net
CS8494 – SOFTWARE ENGINEERING Question Bank 2017 Regulation

www.AUNewsBlog.net
A component is a modular building block for computer software.
Unified Modeling Language (UML) defines a component as a modular, deployable and
replaceable part of a system that encapsulates implementation and exposes a set of
interfaces.
8. Distinguish fan-in and fan-out. (Nov/Dec 2011)
 Fan-out means number of immediate sub-ordinates to the module.
 Fan-out means number of immediate ancestors the modules have.

9. What is Cyclomatic Complexity? (May/June 2014)

Cyclomatic complexity is software metric that provides a quantitative measure of
the logical complexity of the program.

10. Define archetype.

Archetype is a core abstraction using which the systems can be structured. Using
archetypes a small set of entities that describe the major part of system behavior can be
described.

11. List the notations used in Data Flow models. (May/June 2014)

 Process

 Entity

 Flow

 Storage

12. What is meant by real time design? (April/May2011)

Real time design is a software system where the correct functioning of
the system depends on the results produced by the system and the time at which these
results are produced. These are systems which monitor and control their environment.

13. List four design principles of a good design. (April/May2011)

 The design should minimize the distance between the problem and the proposed
software.
 The design should be traceable to analysis model.
 The design should exhibit uniformity and integration.
 The design should be an iterative process to accommodate existing changes.

14. What is the difference between organic mode and embedded mode in COCOMO Model?
(April/May2011)

Page 11
www.AUNewsBlog.net
CS8494 – SOFTWARE ENGINEERING Question Bank 2017 Regulation

www.AUNewsBlog.net
 Organic: Relatively small, simple software projects in which small teams with
good application experience. Example: Thermal analysis program developed for
heat transfer group.
 Embedded: A software project that must be developed within a set of
tight hardware, software and operational constraints. Example: Flight control
software for aircraft.
15. List the architectural model that can be developed. (Nov/Dec 2010)
 A static structural model
 A dynamic process model
 An interface model
 Relationships model
 A distribution model

16. What are the processes of risk management? (Nov/Dec 2010)

 Risk Identification
 Risk analysis
 Risk planning
 Risk monitoring
 Risk mitigation

17. What is software architecture? (May/June 2014)

Software architecture is a structure of systems which consists of various
components, externally visible properties of these and inter-relationships among these
components

18. List the architectural models that can be developed.

 Data centered architecture
 Data flow architecture
 Object oriented architecture
 Call and return architecture
 Layered architecture

19. Define data abstraction. (May/June 2013)

Data abstraction is a kind of representation of data in which the implementation details
are hidden.

20. What is the design quality attributes ‘FURPS’ meant? (Nov/Dec 2012)
 Functionality
 Usability
 Reliability
 Performance
 Supportability

Page 12
www.AUNewsBlog.net
CS8494 – SOFTWARE ENGINEERING Question Bank 2017 Regulation

www.AUNewsBlog.net
21. What is system design?
System design is the process of translating customer requirements into a software
product layout. In this process a system design model is created.

22. State design concepts.

Design concept provides the necessary framework for “getting it right”. The various
design concepts are:
 Abstraction
 Architecture
 Patterns
 Modularity
 Refinement

23. Differentiate Cohesion and Coupling. (Nov/Dec 2011)

S.No Coupling Cohesion
1 Coupling is an indication of the Cohesion is an indication of the
relative independence among functional strength of a module.
modules.
2 Coupling represents how the modules In cohesion, the cohesive module
are connected with other modules or performs only one thing.
with the outside world.
3 With coupling interface complexity is With cohesion data hiding can be done
decided.
4 The goal of coupling is to achieve The goal of cohesion is to achieve high
lowest coupling cohesion.
5 Various types of coupling are: Various types of cohesion are
 Data coupling  Logiclal cohesion
 Control coupling  Coincidental cohesion
 Common coupling  Temporal cohesion
 Content coupling  Procedural cohesion
 Communicational cohesion

24. Write down the various design notations of traditional components.

 Graphical design notation
 Tabular design notation
 Program design language

25. What are the basic design principles of designing class based components.
 The open-closed principle
 Liscov substitution principle
 Dependency inversion principle
 Interface segregation principle

26. Define User Interface Design. (Nov/Dec 2010)

Page 13
www.AUNewsBlog.net
CS8494 – SOFTWARE ENGINEERING Question Bank 2017 Regulation

www.AUNewsBlog.net
User Interface design is an iterative process in which each design process occurs
more than once. While designing the interface the designer has to follow
 Golden rules
 Model the interface
 Analyze the working environment
27. List the interface analysis and design models.
 User model
 Design model
 Mental model
 Implementation model

28. Define Design Heuristics. (May/June 2011)

The program structure is manipulated according to the design heuristics. Some of the
design heuristics are:
 Evaluate the first iteration of the program structure
 Strive for controlled entry module
 Attempt to minimize the structure

29. List out the design methods.

The two software design methods are:
 Object oriented design
 Function oriented design.

PART B

1. Illustrate and explain the importance of modularity based on observation of human problem
solving.
2. Describe transform and transactional mapping by applying design steps to an example system.

3. Explain the fundamental software design concepts in detail.

4. What are the different types of architectural styles exist for software and explain any one
software architecture in details?

5. Explain the user interface design activities.

6. Explain the basic concepts of software design.

7. Explain real time software design with an example.

8. Explain task analysis and modeling.

9. List and brief about Ten usability Heuristics design.

10. Explain the core activities involved in User Interface design process with necessary block
diagrams .

Page 14
www.AUNewsBlog.net
CS8494 – SOFTWARE ENGINEERING Question Bank 2017 Regulation

www.AUNewsBlog.net
UNIT: IV - TESTING AND MAINTENANCE

PART – A

1. Define White-box testing.

White-box testing sometimes called as the glass-box testing or structural testing is
attest case design philosophy that uses the control structure describe as part of component
level design to derive test cases. It is predicated on close examination of procedural
detail.

2. Define Basis path testing.

Basis path testing is a white-box testing technique first proposed by To McCabe.
It enables the test case designer to derive a logical complexity measure of a procedural
design and use this measure a s a guide for defining a basis set of execution paths.

3. What are the levels at which testing is done. (Nov/Dec2013)

 Unit testing
 Integration testing
 System testing
 Acceptance testing

4. Define Regression testing. (Nov/Dec2013) (April/May2011)

Regression testing is done each time a module is added or changed to check if
new functionality is working correctly and the change has not affected already existing
functionality.

5. What are the classes of loops that can be tested? (May/June 2014)
Four different classes of loops can be defined:
i. Simple loops
ii. Concatenated loops
iii. Nested loops
iv. Unstructured loops

6. What is Alpha and beta tests?

 Alpha test is the test that is conducted at the developer’s site by a
customer.
 Beta test is the test that is conducted at one or more customer sites by the
end-user of the software

7. Define equivalence partitioning.

Equivalence partitioning is a black-box testing method that divides the input
domain of a program into classes of data from which test cases can be derived.
8. What is Integration Testing? (April/May2011)

Page 15
www.AUNewsBlog.net
CS8494 – SOFTWARE ENGINEERING Question Bank 2017 Regulation

www.AUNewsBlog.net
Integration testing is a systematic technique for constructing the program structure
while at the same time conducting tests to uncover errors associated with interfacing. The
objective is to take unit-tested components and build a program structure.

9. State the various types of software errors. (April/May2011)

 Boundary related errors: Boundaries in loop, space, time, memory, mishandling of
cases outside boundary.
 Calculation errors: Bad logic, bad arithmetic, outdated constants, calculation
errors, incorrect conversion from one data representation to another, wrong
formula, incorrect approximation.

10. What are the characteristics of good tester? (Nov/Dec 2010)

 A good test has high probability of finding error
 It should not be redundant
 Should be “best of breed”
 Should be neither too simple nor too complex.

11. Define error, fault and failure. (Nov/Dec 2010)

 Fault: A fault can be defined as an “incorrect code”.
 Error: The incorrect answer is the error. In software fault tolerance, “an error is
the part of the system state that is liable to lead to a failure.
 Failure: It is when the systems behavior deviates from the intended behavior.

12. Define Software testing.

Software testing is a critical element of software quality assurance and represents
the ultimate review of specification, design and coding. The goal of testing is to find
errors and a good test is one that has a high probability of finding an error.

13. Define Black-box testing. (May/June 2013)

Black box-testing or behavioral testing focuses on the functional requirements of
the software. Black-box testing refers to tests that are conducted at the software interface.
A black-box test examines some fundamental aspect of a system with litter regard for the
internal logical structure of the software.

14. What do you mean by Control structure testing?

Control structure testing broadens testing coverage and improve the quality of white-
box testing. The various control structure testing are:
 Condition testing
 Data flow testing
 Loop testing

15. What is meant by Smoke Testing? (Nov/Dec 2010)

Page 16
www.AUNewsBlog.net
CS8494 – SOFTWARE ENGINEERING Question Bank 2017 Regulation

www.AUNewsBlog.net
Smoke testing is an integration testing approach that is commonly used when
“shrink wrapped” software products are being developed.

16. What is meant by System testing? (May/June 2011)

System testing is a series of different tests whose primary purpose is to fully
exercise the computer-based system. It verifies whether the system elements have been
properly integrated and perform the allocated functions.

17. State Unit testing.

Unit testing focuses verification on the smallest unit of software design, the
software component or module. Here the important control paths are tested to uncover
errors within the boundary of the module. The unit test is white-box oriented and the step
can be conducted in parallel for multiple components.

18. Define validation testing.

Validation testing is based on the information contained in the validation criteria
of the software requirements specification document. This testing is achieved through a
series of black-box tests that demonstrate conformity with requirements.

19. What are the various types of system testing? (May/June 2011)
 Recovery testing
 Security testing
 Stress testing
 Performance testing

20. Define Debugging. (May/June 2011)

Debugging is the process that results in the removal of error. It occurs as a
consequence of successful testing. The three categories of debugging approaches are:
 Brute-force
 Back tracking
 Cause elimination

21. List the software implementation techniques.

The various software implementation techniques are:
 Coding process
 Incremental coding process
 Test driven development
 Pair programming

22. Define refactoring.

Refactoring is a technique to improve existing code and prevent this design decay
with time caused by changes. It is a change made to the internal structure of software to

Page 17
www.AUNewsBlog.net
CS8494 – SOFTWARE ENGINEERING Question Bank 2017 Regulation

www.AUNewsBlog.net
make it easier to understand. It has the objective of improving the design that the code
implements.

23. Distinguish between stress and load testing.(May/June 2012)

Stress testing is designed to determine if the system can function when subject to
larger volumes. The areas that are stressed include input transactions, internal tables, disk
space, output etc.
Load testing is meant to test the system by constantly and steadily increasing the
load on the system till the time it reaches the threshold limit.

24. What is boundary condition testing?(May/June 2013)

In all software applications, bugs often emerge at boundary conditions. So select
test data in which values lie along data extremes. If selected test case work correctly for
these special cases then they will work correctly for all other values. For boundary
condition testing boundary value analysis is done.

PART B
1. Explain in detail the various testing strategies.
2. Why is testing important? Narrate the path testing procedure in detail with a sample
code.
3. Distinguish between black box and white box testing. Explain the different integration
testing approaches.
4. Explain the various types of black-box testing methods.
5. Explain the steps applied to derive the basis set. Use an example to illustrate each step
in the test case design.
6. Describe the testing objectives and its principles.
7. Explain the basis path testing in detail.
8. What are the attributes of a good test? Explain the test case design.
9. Explain in detail about alpha and beta testing.
10. Discuss about categories of data flow orientation in testing.

Page 18
www.AUNewsBlog.net
CS8494 – SOFTWARE ENGINEERING Question Bank 2017 Regulation

www.AUNewsBlog.net

UNIT: V - PROJECT MANAGEMENT

PART – A

1. Give the procedure of the Delphi method. (May/June 2011)

Delphi method has the following steps:
 Selection of experts
 Briefing to the experts
 Collation of estimates from experts
 Convergence of estimates and finalization

2. Write short notes on the various estimation techniques. (May/June 2011)

 Function Point Estimation
 Cost Estimation
 Function Point Estimation
 Delphi Method
 COCOMO model

3. What is Project Planning? (May/June 2012)

Project planning is an activity in which the project plan is prepared. A project
plan is a formal, approved document that is used to manage and control a project. This
plan is mainly concerned with schedule and budget.

4. What do you mean by estimation risk? (May/June 2013)

Expressing duration, intensity, magnitude and reach of the potential consequences
of a risk in quantifiable value terms is called estimation risk.

5. How can project scheduling affect integration test? (Nov/Dec 2010)

Scheduling is the approximate time frame definition for future events. Scheduling,
for example, is used in laying out the main framework activities for the project. If the
project is behind schedule, then integration testing can't even begin. Integration testing
happens after unit testing which happens after coding. Also, if scheduling is tight, then
project managers could potentially reduce the time in integration testing thus reducing the
quality or increasing the cost.

6. List the different types of risks occur in SPM. (Nov/Dec 2010)

 Schedule Risk
 Budget Risk
 Technical Risk
 Operational Risk

7. What is Software Project Management?

Software Project Management is an umbrella activity within software
engineering. It begins before any technical activity is initiated and continues throughout
the definition, development and support of computer software.

8. Define Cyclomatic complexity.

Cyclomatic complexity is a software metric that provides a quantitative measure of
the logical complexity of a program.

Page 19
www.AUNewsBlog.net
CS8494 – SOFTWARE ENGINEERING Question Bank 2017 Regulation

www.AUNewsBlog.net
9. Differentiate metric, measure and measurement.

Metric Measure Measurement

Metric is a quantitative Measure provides a quantitative Measurement is
measure of the degree to indication of the extent, amount, the act of
which a system, component dimension, capacity or size of some determining a
or process possesses a given attribute of a product or process measure.
attribute

10. Differentiate the two categories of metrics.

Size-oriented metrics Function-oriented metrics

Size-oriented metrics are derived by Function-oriented metrics use a measure of
normalizing quality and productivity the functionality delivered by the
measures by considering the size of the application as a normalization value.
software that has been produced.

Examples: Lines of Code(LOC), Example: Function point(FP), Errors per

Errors per KLOC, Defects per KLOC, $ FP, Defects per FP, $ per FP, Pages of
per KLOC, Pages of documentation per documentation per FP.
KLOC

11. What is Earned Value Analysis?

Earned Value Analysis is a technique for performing quantitative analysis of
progress of the software project. The earned value system provides a common value scale
for every task, regardless of the type of work being performed. Earned value is simply a
measure of progress.

12. What is Software Project Scheduling?

Software Project Scheduling is an activity that distributes estimated effort across
the planned project duration by allocating the effort to specific software engineering.

13. What are the two project scheduling methods that can be applied to software
development?
The two project scheduling methods that can be applied to software development
are
 Program Evaluation and Review Technique (PERT)
 Critical Path Method

14. What is meant by task network?

A task network also called as activity network is a graphical representation of the
task flow for a project. It depicts major software engineering tasks. It is used to compute
the critical path, a timeline chart and a variety of project information.

15. What is Project Plan?

A project plan is a formal, approved document that is used to manage and control
a project. This plan is mainly concerned with schedule and budget.

16. Define DRE.

Page 20
www.AUNewsBlog.net
CS8494 – SOFTWARE ENGINEERING Question Bank 2017 Regulation

www.AUNewsBlog.net
Defect Removal Efficiency (DRE) is a measure of the filtering ability of Quality
of Assurance (QA) activities as they are applied throughout all process framework
activities.
DRE = E / (E+D)
where E  number of errors found before delivery of the software
D  number of defects found after delivery

17. What is error tracking?

Error tracking is a process of finding out and correcting the errors that may occur
during the software development process at various stages sucha s software design,
coding or documenting.

18. List down few process and product metrics.

Product metrics are:
 Size metric
o LOC based metric
o FP based metric
 Complexity metric
 Quality metric
Process metrics are:
 Application of methods and tools
 Use of standards for the system
 Effectiveness of management of system
 Performance of development of system

19. Define COCOMO-II.

 COCOMO is COnstructive COst MOdel
 It is one of the most widely used cost estimation models in the industry
 COCOMO-II address the following areas
o Application Composition Model
o Early design stage model
o Post-architecture stage model

20. State RMMM plan.

The RMMM plan documents all work performed as part of risk analysis and is
used by the project manager as part of the overall project plan. RMMM stands for
 Risk Management
 Risk Monitoring
 Risk Mitigation

21. What are the two categories of software measurement?

The two categories of software measurement are
 Direct Measures
 Indirect Measures

22. List the steps in planning process.

 Define the technical approach
 Define and sequence the tasks
 Define the dependency relations between tasks

Page 21
www.AUNewsBlog.net
CS8494 – SOFTWARE ENGINEERING Question Bank 2017 Regulation

www.AUNewsBlog.net
 Estimate the resources
 Schedule all tasks
 Define budget and process

PART B

1. Explain FP based Estimation & LOC based Estimation.

2. Explain Risk Management in detail.
3. Explain Project Scheduling.
4. Explain detail about COCOMO Model.
5. Explain in detail about RFP Risk Management.

Page 22
www.AUNewsBlog.net