18BT767/3
URR-18 Write your Roll number
KAKATIYA INSTITUTE OF TECHNOLOGY & SCIENCE, WARANGAL
(An Autonomous Institute under Kakatiya University, Warangal)
FACULTY OF ENGINEERING AND TECHNOLOGY
B. Tech. (IT) VI Semester (Regular & Supplementary) Examination, May 2023
U18IT607: Software Engineering
Duration: 3 Hours] [Max. Marks : 60
Note: Answer all the questions.
CDLL CO’s
1. a. As per IEEE, define and justify the definition of Software Engineering. [1] R CO1
b. “The phrase user requirements refer to high-level abstract needs, [1] U CO1
whereas system requirements refer to a comprehensive description of
what the system should do.” Explain the distinction between user and
system needs in order to understand the above statement.
c. Which one of the following is not a software myth? Justify your answer. [1] An CO1
a) Once we write the program and get it to work, our job is done
b) Project requirements continually change, but change can be easily
accommodated because software is flexible
c) If we get behind schedule, we can add more programmers and catch
up
d) If an organization does not understand how to control software
projects internally, it will invariably struggle when it outsources software
projects.
d. Does “refactoring” mean that you modify the entire design iteratively? If [1] U CO2
not, what does it mean?
e. How are the concepts of coupling and software portability related? [1] Ap CO2
Provide examples to support your discussion.
f. Is a software design a program? If not, then what is it? Justify your [1] U CO2
answer.
g. Write about drivers and stubs. [1] R CO3
h. Will exhaustive testing (even if it is possible for very small programs) [1] U CO3
guarantee that the program is 100 percent correct?
i. What is equivalence partitioning? [1] R CO3
j. What are the Attributes of Effective S/W Metrics. [1] R CO4
k. “Unreasonable” deadlines are a fact of life in the software business. How [1] R CO4
should you proceed if you’re faced with one?
l. A software team delivers a software increment to end users. The users [1] Ap CO4
uncover eight defects during the first month of use. Prior to delivery, the
software team found 242 errors during formal technical reviews and all
testing tasks. What is the overall DRE for the project after one month’s
usage?
2. a. Umbrella activities occur throughout the software process. Do you think [6] Ap CO1
they are applied evenly across the process, or are some concentrated in
one or more framework activities.
b. Describe a process framework in your own words. When we say that [6] An CO1
framework activities are applicable to all projects, does this mean that the
same work tasks are applied for all projects, regardless of size and
complexity? Explain.
(OR)
2. c. Deployment activity encompasses three actions: delivery, support, and [6] Ap CO1
feedback. Because modern software process models are evolutionary or
incremental in nature, deployment happens not once, but a number of
Page 1 of 4
18BT767/3
times as software moves toward completion. Each delivery cycle
provides the customer and end users with an operational software
increment that provides usable functions and features. How deployment
principles will be helpful for delivering the software system?
d. Compare RAD Model and Traditional SDLC. List out various [6] An CO1
applications where RAD model can be used. Highlight the major
positives and negatives when RAD Model is used.
3. a. Transform mapping is a set of design steps that allows a DFD with [6] Ap CO2
transform flow characteristics to be mapped into a specific architectural
style. Identify the designing steps to map data flow diagrams into
software architecture.
b. Architectural design represents the structure of data and program [6] An CO2
components that are required to build a computer-based system. It
considers the architectural style that the system will take, the structure
and properties of the components that constitute the system, and the
inter relationships that occur among all architectural components of a
system. Based on the above statements analyze the importance of
architectural design.
(OR)
3. c. The design model can be viewed in two different dimensions. The [6] Ap CO2
process dimension indicates the evolution of the design model as design
tasks are executed as part of the software process. The abstraction
dimension represents the level of detail as each element of the analysis
model is transformed into a design equivalent and then refined
iteratively. Then briefly describe each of the four elements of the design
model.
d. Component level design for WebApps incorporates two elements. Based [6] An CO2
on the elements of WebApps illustrate the WebApp component.
4. a. Cyclomatic Complexity is a software metric that given the quantitative [6] Ap CO3
measure of logical complexity of the program. It 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.
Then Compute the Cyclomatic complexity for the below figure.
b. WebApp interface design should be perfect, so it answers three primary [6] An CO3
questions for the end user.
Where am I? The interface should, provide an indication of the
WebApp that has been accessed, inform the user of her location in the
Page 2 of 4
18BT767/3
content hierarchy.
What can I do now? The interface should always help the user
understand his current options, what functions are available? what links
are live? what content is relevant?
Where have I been, where am I going? The interface must facilitate
navigation. It must provide a “map” of where the user has been and
what paths may be taken to move elsewhere within the WebApp.
Then how web interface design principles are helpful in developing the
web interface.
(OR)
4. c. Classify various Test strategies for conventional software and highlight [6] Ap CO3
the procedure followed in each strategies.
d. User interface design, as the name suggests, refers to the creation of a [6] An CO3
model of a user interface that is needed for some software. A UI designer
performs this task. To build a good interface, the designer must follow
the interface design process, keeping in mind the end user. Analyze and
design the process for user interfaces framework activities of
1) interface analysis and modeling
2) interface design
3) interface construction
4) interface validation.
5. a. Compute the function point when all complexity adjustment factor (CAF) [6] Ap CO4
are average and weighting factors are high value for a project with the
following information domain characteristics:
Number of user inputs: 32
Number of user outputs: 60
Number of user inquiries: 24
Number of files: 8
Number of external interfaces: 2
Calculate the Unadjusted Functional Point.
Measurement Parameter Weighing Factors
Low Average High
Number of External Inputs (EI) 8 10 17
Number of External Outputs (EO) 7 8 12
Number of External Inquiries (EI) 5 6 8
Number of Internal Logical Files (ILF) 6 6 9
Number of External Interfaces (EIF) 4 5 5
b. Boehm suggests an approach that addresses project objectives, [6] An CO4
milestones and schedules, responsibilities, management and technical
approaches, and required resources. He calls it the W5HH Principle,
after a series of questions that lead to a definition of key project
characteristics and the resultant project plan. So, apply your knowledge
on W5HH principles and describe how those principles are helpful in
software development.
(OR)
Page 3 of 4
18BT767/3
5. c. Apply McCall’s Triangle of Quality Factors to real time scenario and [6] Ap CO4
explain how those factors influence the quality of a product.
d. You’ve selected an appropriate process model, you’ve identified the [6] An CO4
software engineering tasks that have to be performed, you estimated the
amount of work and the number of people, you know the deadline,
you’ve even considered the risks. Now it’s time to connect the dots.
That is, you have to create a network of software engineering tasks that
will enable you to get the job done on time. Once the network is created,
you have to assign responsibility for each task, make sure it gets done,
and adapt the network as risks become reality. In a nutshell, that’s
software project scheduling and tracking.
Then how project scheduling principles are helpful in overall
development of the software.
--- Question Paper Ends ---
Page 4 of 4
