DEPARTMENT OF COMPUTER ENGINEERING & APPLICATIONS

COURSE : B. TECH.
SEC: A/B/C

BRANCH : CSE

SUB : SOFTWARE ENGINEERING

SUBMISSION : 08.09.2016

YEAR / SEM : III / V

SUB CODE : CSE 5002

ASSIGNMENT - 1
1. Explain why the software which are developed using evolutionary approach are
difficult to maintain and test.
2. Describe various nature points of SRS and its characteristics. Discuss the relative
advantages and disadvantages of formal and informal requirements.
3. What is the most important difference between generic software product
development and custom software development? What might this mean in practice
for users of generic software products?
4. Apart from the challenges of heterogeneity, business and social change, and trust
and security, identify other problems and challenges that software engineering is
likely to face in the 21st century (Hint: think about the environment).
5. Explain why incremental development is the most effective approach for
developing business software systems. Why is this model less appropriate for realtime systems engineering?
6. Suggest why it is important to make a distinction between developing the user
requirements

and

developing

system

requirements

in

the

requirements

engineering process.
7. Describe the main activities in the software design process and the outputs of
these activities. Using a diagram, show possible relationships between the outputs
of these activities.
8. Explain why change is inevitable in complex systems and give examples (apart
from prototyping and incremental delivery) of software process activities that help
predict changes and make the software being developed more resilient to change.
9. Explain why Boehms spiral model is an adaptable model that can support both
change avoidance and change tolerance activities. In practice, this model has not
been widely used. Suggest why this might be the case.
10.
What are the advantages of providing static and dynamic views of the
software process as in the Rational Unified Process?
11.
Explain why the process of project planning is iterative and why a plan must
be continuously reviewed during software project.

12.

Some very large software projects involve writing millions of lines of code.

Explain why the effort estimation models such as COCOMO, might not work well
when applied to very large systems.
13.
Consider a project with the following function units:
Number of user inputs = 50
Number of user outputs = 40
Number of user enquiries = 35
Number of user files = 06
Number of external interfaces = 04
Assume all complexity adjustment factors and weighting factors are average.
Compute the function points of the project.
14.
Consider a project with the following function units:
Number of user inputs = 55
Number of user outputs = 48
Number of user enquiries = 25
Number of user files = 09
Number of external interfaces = 08
Assume all complexity adjustment factors are significant and weighting factors are
high. Compute the function points of the project.
15.
Suppose that a project was estimated to be 400 KLOC. Calculate the effort
and development time for each of the 3 modes organic, semidetached and
embedded.
16.
A project size of 200 KLOC is to be developed with average experience
human resource. The project schedule is not very tight. Calculate the effort,
development time, average staff size and productivity of the project.
17.
Discuss various types of COCOMO mode. Explain the phase wise distribution
of effort.
18.
The size of software product to be developed has been estimated to be
22000 LOC. Predict the manpower cost (effort) by Walston Felix model.
19.
Describe the Albrechts theory of function points in software estimation at
early stage.
20.
Suppose that a project was estimated to be 32 KLOC. Calculate the effort and
development time for organic type. Calculate the effort, development time,
average staff size and productivity of the project.
NOTE:
Attempt all questions.
Answer the questions in same sequence as they are asked.
Mention the formulas and all necessary steps in each numerical.