NR-410209-Principles of Software Engineering

Set No.
Code No:410209
IV B.Tech. I-Semester Regular Examinations, November-2003.
PRINCIPLES OF SOFTWARE ENGINEERING

(Electrical and Electronics Engineering)
Time: 3 hours
Max. Marks: 80
Answer any FIVE questions
All questions carry equal marks
---
1.a)
b)
What is software engineering? Explain three key elements of the software

engineering?
With a neat diagram, explain the prototype model giving its advantages and
disadvantages.
2.a)
b)
Describe the difference between process and project metrics.

Explain the importance of software measurement.
3.
Why often there is tension between a software engineering group and an

independent software quality assurance group? Is this healthy?
4.
Discuss in detail about System Engineering hierarchy.
5.
Define stepwise refinement. Apply a stepwise refinement approach to develop

three levels of procedural abstractions for the program to develop a check
writer that, given a numeric dollar amount, will print the amount in words that is
normally required on a check.
6.
Discuss the principles required for data specification with suitable examples.
7.a)
b)
What is Test Case? How it is designed?

Draw and explain the information flow pattern for testing.
8.a)
b)
Describe Validation testing for software.

Draw and explain the Debugging process.
---
Set No.
Code No:410209

Time: 3 hours
1.a)
b)
Max. Marks: 80
--With a neat diagram, explain the rapid application development software process
model.
List the merits and demerits of the waterfall model.
2.
Explain the
examples.
size-oriented
metrics
and
function-oriented
metrics
with
3.
What are the configuration items that are target for configuration management
techniques and form a set of baselines.
4.a) Discuss software prototyping.

b) Explain review of a software requirements specification.
5.a)
b)
How are the concepts of coupling and software portability related? Provide
examples to support your discussion.
Explain design heuristics for effective modularity.
6.
Some designers contend that all data flow may be treated as transform oriented.
Discuss how this contention will affect the software structure that is derived
when a transaction oriented flow is treated as a transform. Use an example
flow to illustrate important points.
7.a)
State and explain the categories in which Black Box testing attempts to find
errors.
Describe Boundary Value Analysis (BVA) testing for software.
b)
8.a)
b)
Is Unit testing possible or even desirable in all circumstances? Justify your

answer.
Who should perform the validation test: the software developer or the software
user? Justify your answer.
---
Code No:410209
Set No.

Time: 3 hours
Max. Marks: 80
--1.a) Explain the characteristics of software that are considerably different than those
of hardware.
b)
Explain software re-usability.
2.
Discuss the software risk management.
3.
Describe identification of objects in the software configuration

a) Describe version control
b) Describe change control
4.a)
b)
Draw a context-level model for a simple invoicing system for a small business.
What are the differences between cardinality and modality?
5.
Suppose you wish to model the elevator system of a multi floor building. The
system is composed of m floors and n elevators. Each elevator has a set of
buttons, one for each floor. These light up when pressed and cause the elevator to
visit the corresponding floor. The light goes out upon the elevators reaching the
floor. Each floor has two buttons, one to request an up elevator and one to request
a down elevator. The illumination goes out when the elevator visits the floor and
is either moving direction or has no outstanding request. Each elevator has an
emergency button which, when pressed, causes a warning signal to be sent to the
site manager. The elevator has a mechanism to cancel its out-of-service status.
Model this system using software design concepts.
6.
Discuss the relative merits and difficulties of applying data flow oriented design
in the following areas:
(a) Embedded microprocessor applications. (b) Communication software design.
7.a)
Explain with one example the Cause-effect Graphing techniques for test
case design.
Explain in detail the Comparison testing.
b)
8.a)
b)
What are the objectives of software testing? Briefly discuss any three Software
Engineering testing methods.
Describe necessity of the Stress testing.
---
Set No.
Code No:410209
Time: 3 hours
Max. Marks: 80
--1.a) Write all the different software process models? Explain any one with neat
diagram
b) Write short notes on Documentation in software development.
2.
Define and explain a task set for the software project.
3.a)
Describe the role of CCA and suggest formats for the change request, the
change report and the ECO.
Develop a checklist for use during configuration audits.
b)
4.
Analyse the computer science department system and develop a software

requirement specification.
5.
The department of public works for a large city has decided to develop a
computerized pothole tracking and repair system (PHTRS). As potholes are
reported, they are assigned an identifying number and stored by street address,
size (on a scale of 1 to 10), location (middle, curb, etc. ), district ( determined
from street, address), and repair priority ( determined from the size of the
pothole). Work order data are associated with each pothole and include pothole
location and size, repair crew identifying number, number of people on crew,
equipment assigned, hours applied to repair, hole status ( work in progress,
repaired, temporary repair, not repaired), amount of filler material used, and cost
of repair. Finally, a damage file is created to hold information about reported
damage due to the pothole and includes citizens name, address, phone number,
type of damage, and dollar amount of damage. PHTRS is an on-line system,
queries are to be made interactively. Decompose PHTRS into modules using
effective modular design principles.
6.
Define flow boundaries and map the DFD into a software structure using the
transform mapping technique for an automated course registration system for a
university.
7.a)
b)
What is Basis Path testing? Explain Cyclometric Complexity?

Describe Loop testing.
8.a)
b)
What are the prerequisites to go for validation testing for software?

What is configuration review? Why it is required?
---

NR-410209-Principles of Software Engineering

Uploaded by

Copyright:

Available Formats

NR-410209-Principles of Software Engineering

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NR-410209-Principles of Software Engineering

Uploaded by

Copyright:

Available Formats

Set No.

PRINCIPLES OF SOFTWARE ENGINEERING

What is software engineering? Explain three key elements of the software

Describe the difference between process and project metrics.

Why often there is tension between a software engineering group and an

Discuss in detail about System Engineering hierarchy.

Define stepwise refinement. Apply a stepwise refinement approach to develop

What is Test Case? How it is designed?

Describe Validation testing for software.

PRINCIPLES OF SOFTWARE ENGINEERING

4.a) Discuss software prototyping.

Is Unit testing possible or even desirable in all circumstances? Justify your

PRINCIPLES OF SOFTWARE ENGINEERING

Explain software re-usability.

Discuss the software risk management.

Describe identification of objects in the software configuration

Define and explain a task set for the software project.

Analyse the computer science department system and develop a software

What is Basis Path testing? Explain Cyclometric Complexity?

What are the prerequisites to go for validation testing for software?

You might also like