0% found this document useful (0 votes)
49 views7 pages

I A 1 Scheme Software Engineering

1. The document describes an internal test for a Software Engineering course being held on October 17, 2023. It is divided into three parts - Part A with 4 questions worth 5 marks each, Part B with 2 questions worth 9 marks each, and Part C with 1 compulsory question. 2. The questions cover various topics related to software engineering such as software attributes, software development life cycles, requirements classification, software design documentation standards, and modular design objectives. 3. Guidelines for business process engineering are also provided, which emphasize organizing around outcomes, centralizing resources, and controlling decision points.
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)
49 views7 pages

I A 1 Scheme Software Engineering

1. The document describes an internal test for a Software Engineering course being held on October 17, 2023. It is divided into three parts - Part A with 4 questions worth 5 marks each, Part B with 2 questions worth 9 marks each, and Part C with 1 compulsory question. 2. The questions cover various topics related to software engineering such as software attributes, software development life cycles, requirements classification, software design documentation standards, and modular design objectives. 3. Guidelines for business process engineering are also provided, which emphasize organizing around outcomes, centralizing resources, and controlling decision points.
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
You are on page 1/ 7

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

AND
DEPARTMENT OF INFORMATION SCIENCE AND ENGINEERING

INTERNAL TEST – I
Semester: III Session: AUG-DEC 2023
Course Name: Software Engineering Course Code: 22CSE141

Date: 17.10.2023 Max Marks: 50


Time: 1:30 pm to 3 pm Duration: 90 minutes
Note: i. PART - A (Question 1-5) answer any 4 full questions.
ii. PART - B (Question 6-8) answer any 2 full questions.
iii. PART - C (Question 9) is compulsory to attend

Q. Bloom’s
Questions Marks CO’s
No Level
PART -A (4×5 = 20 Marks)
Mr. Messi ,a Software Developer developed one cyber security
1. software and he claims that his software is good software. Appraise 5 CO3 L5
him the attributes of a good software which his software is going
to exhibit.
Ans:

2. Identify and describe a SDLC in which accommodating change after the 5 CO5 L2
process has started is not possible.
Ans:

• The Waterfall model sometimes called the classic life cycle,


suggests a systematic, sequential approach to software
development.
• It is a oldest paradigm for software engineering.
• Most widely used though no longer state-of-art.
• Each step results in documentation.
• May be suited to for well-understood developments using
familiar technology.
• Not suited to new, different systems because of specification
uncertainty
• Difficulty in accommodating change after the process has started.
• Can accommodate iteration but indirectly.
• Working version not available till late in process.
• Often get blocking states.

3. Prof. Pawan kalyan is in the process of segregating the requirements for


his new software into different classes. Lead and elaborate him in 5 CO2 L2
understanding the Classification of requirements.
Ans: Functional requirements :
• Describe functionality or system services, how the system should
react to particular inputs and how the system should behave in
particular situations.
• Depend on the type of software, expected users and the type of
system where the software is used
• Functional user requirements may be high-level statements of
what the system should do but functional system requirements
should describe the system services in detail.

Non-functional requirements :
• Defines system properties and constraints e.g. reliability,
response time and storage requirements. Constraints are I/O
device capability, system representations, etc.
• Can be constraints on the process too
• Use a particular CASE system, programming language or
development method
• System maybe unusable if non-functional requirements are not
satisfied (Critical)
• Non-functional classifications
Product requirements
• Requirements which specify that the delivered product must
behave in a particular way e.g. execution speed, reliability, etc.
• Organizational requirements
• Requirements which are a consequence of organizational
policies and procedures e.g. process standards used,
implementation requirements, etc.
• External requirements
• Requirements which arise from factors which are external to the
system and its development process e.g. interoperability
requirements, legislative requirements, etc.

4. Illustrate the standard format of SRS document. 5 CO2 L3


Ans:

5. Elaborate on the objectives of modular software design. 5 CO3 L2

Ans: Objectives of modular software design :


– Functional partitioning into discrete scalable , reusable
modules.
– Rigorous use of well-defined modular interface.
– Ease of change to achieve technology transparency and to
the extent possible make use of industry standards for key
interfaces.
• Modularity is the principle of keeping separate the various
unrelated aspects of a system, so that each aspect can be studied
in isolation (also called separation of concerns).
• If the principle is applied well, each resulting module will have a
single purpose and will be relatively independent of the others.
• Each module will be easy to understand and develop easier to
locate faults (because there are fewer suspect modules per fault).
Easier to change the system (because a change to one module affects
relatively few other modules)
PART -B (2×9 = 18 Marks)
6. Discuss Business process engineering along with common guidelines for 9 CO4 L3
Business process engineering.
Ans: • Business process engineering is a structured approach to
improving a company’s performance in areas such as cost,
service, quality, and speed through changes in (appropriately)
processes.
• Organize around the outcome, not the specific task. One
person owns a whole process, performing or coordinating all
steps.
• Those closest to the process should perform the process.
Instead of farming out different types of easily managed work,
the people who need the quick outcomes from simple tasks take
ownership.
• Have the people who produce the information process it.
This streamlines the outcome of the information gathered into
usable data.
• Centralize resources. Databases and other technology systems
can consolidate resources to cut down on redundancies and
increase flexibility.
• Integrate corresponding activities, not merely their results.
This keeps the content cohesive, without the gaps and
miscommunication that could cause delays.
• Control the decision points and where the work is done.
Built-in controls enable the employees who perform the work to
self-manage, so managers can become supportive rather than
directive.
• Information should be collected once and at the source. You
can erase data redundancies when processes are connected in a
central database

Common guiding principles for the stages are as follows:


• Step 0: Preparation and Coordination
• Step 1: Set the Vision
• Step 2: Assemble the Team
• Step 3: Determine the Processes
• Step 4: Redesign

7. a. If NSK is a MNC with a budget of 600Crores, 4000 employees


working in it, and using RT technologies for its software production. A
business proposal came with the requirements of 350crores budget 5 CO2 L3
,requiring 1295 employees manpower for 3 months duration making
use of RT technologies costing 250 Crores. Conduct the feasibility
study on the new proposal and conclude with convincing results .
Ans: Feasibility study Explanation with given values and conclusion is required.
NSK can accept and start the proposal as:
Available resources :
Budget=600Cr
Employees=4000

Resources required for Proposal:


Budget=(Budget of proposal Cost of RT tech.)=(350+250)=600Cr
Employees =1295
As required resources are well within the available budget, QBX can
accept the proposal and start its implementation.
b. With a neat diagram demonstrate Layered Architectural style. 4 CO3 L3

Explain
8. Along with a suitable example , illustrate behavioural models. 9 CO2 L3
Ans:
• Behavioural models are used to describe the overall behaviour of
a system
• Two types of behavioural model are shown here
• Data processing models that show how data is processed
as it moves through the system
• State machine models that show the systems response to
events
• Both of these models are required for a description of the
system’s behaviour
Explanation of Data processing models, State machine models
required.
PART -C (1×12 = 12 Marks)
9. Dr.Ganguly is venturing a new advanced software for hospital
12 CO3 L3
management in Bangalore. Dr. Ganguly is in the course of identifying
the various system engineering processes that he has to follow.
Elaborate him on the system engineering process with detailed diagram
and description.
Ans: Requirements System
definition decommissioning

System System
design evolution

Sub-system System
development installation

System
integration

Explanation of each phase is expected.

Course Bloom’s
Description
Outcomes Taxonomy Level
Apply the software engineering lifecycle models by demonstrating competence in Applying(L3)
CO1
communication, planning, analysis, design, construction, and deployment of software.
CO2 An ability to work in one or more significant application domains. Applying (L3)
Work as an individual and as part of a multidisciplinary team to develop and deliver Applying (L3)
CO3
quality software.
Demonstrate an understanding of and apply current theories, models, and techniques Applying (L3)
CO4
that provide a basis for the software lifecycle.
Demonstrate an ability to use the techniques and tools necessary for engineering Applying (L3)
CO5
practice.
CO6 Perform independent research and analysis. Analyzing(L4)

Programme Outcome(POs)
PO-1: Knowledge, PO-2: Analyze, PO-3: Design, PO-4: Conduct, PO-5: Tools, PO-6: Societal
Problems,PO-7:Sustainability,PO-8:Teamworkandleadershipqualities,PO-9:Ethics,PO-
10:Communication,PO-11:Projectandfinancemanagement,PO-12:LifetimeLearning

PO PO PO PO PO PO PO PO PO PO PO PO PSO PSO
18CS5IOT07 1 2 3 4 5 6 7 8 9 10 11 12 12 12

18CS5IOT07.1 3 2 1 0 0 0 0 1 2 1 0 1 2 2

18CS5IOT07.2 3 2 3 2 2 1 0 2 1 2 2 1 2 2

18CS5IOT07.3 3 3 1 2 2 0 0 0 0 0 0 1 2 2

18CS5IOT07.4 3 2 2 0 2 1 0 3 1 1 1 1 2 2

18CS5IOT07.5 3 3 0 1 1 1 0 0 3 0 0 1 2 2

18CS5IOT07.6 2 3 1 1 1 0 1 2 1 1 3 1 2 2
L1 L2 L3 L4 L5 L6
Remembering Understanding Applying Analyzing Evaluating Creating

* Allthe Best *

You might also like