0% found this document useful (0 votes)
7 views2 pages

Software Engineering Exam Questions Winter 2024

Uploaded by

contactspot1
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
7 views2 pages

Software Engineering Exam Questions Winter 2024

Uploaded by

contactspot1
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

[Link].

(Part-I) First Semester (Computer Science / Computer Software) (NEP) Winter 2024
DSE-III NIMCS-5 (3) / N1MCSWS5 (3) - Software Engineering

P. Pages : 2 AG - 6663
Time : Three Hours *4083* Max. Marks : 60
_____________________________________________________________________
Notes : 1. Assume suitable data whenever necessary.
2. Illustrate your answer with the help of neat sketches whenever necessary.

1. a) Define software Engineering? Explain the concept of evolution in product and process for 6
software development.

b) What is RAD model? State advantages and disadvantages. 4

19
OR

6:
2. a) What is software process? Explain in brief about process model types. 6

:5
b) Explain in brief about software crisis & myths. 4

08
3. a) What are software metrics and measurements? Explain software measurements. 6
24
b) What are software risks? Explain risk projection. 4
20

OR
2/

4. a) What is meant by project scope in software? Explain software project planning. 6


/1

b) What is risk refinement in software engineering. 4


20

5. a) What is task set? List out the basic principles which guide software project scheduling. 6
Explain any one of them.
C
O

b) Explain software quality concepts in detail. 4


H

OR
kC

6. a) Explain the following terms: 6


B

i) Software quality Assurance

ii) EV analysis

b) Describe the concept of software reliability in software engineering. 4

7. a) What is system Engineering? Explain requirement engineering. 6

b) What are the standards for documentation? 4

OR

AG - 6663 1 P.T.O
8. a) Explain software design process and design principles. 6

b) Explain system modelling and its significance in software engineering. 4

9. a) Define mapping. Give the steps involved in transform mapping. 6

b) What are the different types of architectural styles used for software? 4

OR

10. a) Describe translation mapping with example. 6

b) Describe the golden rules for user interface design. 4

11. a) Describe the differences between black box and white box testing models. 6

19
b) Why testing is important with respect to software? 4

6:
:5
OR

08
12. a) Explain the following terms: 6

i) Integration testing
24
ii) Validation testing.
20

b) What is debugging? State the objectives and guidelines for debugging. 4


2/

*********
/1
20
C
O
H
kC
B

AG - 6663 2

Common questions

Powered by AI

Standards for documentation ensure consistency, clarity, and completeness in software documentation. They are important for maintaining quality, facilitating communication across teams, and ensuring knowledge transfer, which is essential for long-term project maintenance and scalability .

Software metrics and measurements provide quantitative data that helps assess the quality and progress of software projects. They facilitate the tracking of performance indicators such as defect density, code complexity, and development speed, thereby enabling informed decision-making to enhance software quality .

The software process refers to the structured set of activities required to develop a software system. Different process model types, such as Waterfall, Agile, and Spiral, impact software development by providing varying approaches to managing tasks and activities. Waterfall is linear and sequential, Agile is iterative and flexible, and Spiral combines elements of both with a focus on risk assessment .

Design principles, such as modularity, abstraction, and encapsulation, guide the software design process by promoting clean, maintainable architectures that enhance understanding and facilitate efficient coding. They help designers manage complexity and ensure that user needs are adequately met .

Task sets form the basis of project scheduling by grouping related activities that must be completed to achieve project goals. Principles such as prioritizing tasks based on their dependency, allocating resources efficiently, and adjusting schedules to accommodate risk management contribute to successful project execution .

The RAD model offers advantages such as faster product delivery and increased user involvement, leading to a higher-quality final product. However, its disadvantages include potential for scope creep due to the lack of a clear project scope from the outset and challenges in managing highly skilled resources needed for continuous user feedback .

Risk refinement in software engineering allows for the identification, analysis, and prioritization of risks. It is crucial because it enables project teams to mitigate potential issues early, plan for contingencies, and allocate resources effectively to manage uncertainties .

Black box testing is focused on input/output validation without knowledge of the internal workings, whereas white box testing involves examining the internal logic and structure of the code. Black box is useful for functional verification, while white box ensures code paths and conditions are executed effectively .

System modeling provides a visual representation of the system architecture, processes, and data flows, which enhances understanding, facilitates communication, and helps identify challenges early in the design phase. It influences software effectiveness by ensuring alignment with user requirements and technical constraints .

Software reliability is a measure of the software's ability to perform its required functions under stated conditions for a specified period. It plays a critical role by ensuring that software remains functional and dependable over time, thus maintaining user trust and satisfaction .

You might also like