wayground logo

Free Printable Worksheets

Font size

S
M
L
XL
Worksheets

Software Engineering Quiz-1

Total questions: 60

Worksheet time: 3600secs

Name
Class
Date
1.

Which of the following characteristics of software primarily contributes to the challenge of predicting development effort accurately?

a)

Portability

b)

Malleability

c)

Complexity

d)

Interoperability

2.

Software being intangible means:

a)

It cannot be updated once delivered

b)

It cannot be physically touched or seen

c)

It is always portable across systems

d)

It cannot be modified

3.

The fact that each software product is unique means:

a)

The development cost is always the same

b)

No two projects are exactly alike, even with similar goals

c)

Every software must use different programming languages

d)

Testing is not reusable between products

4.

Which key characteristic of software could also introduce unintended defects if not managed carefully?

a)

Changeability

b)

Security

c)

Functionality

d)

Portability

5.

A software acting as a 'vehicle' in embedded systems refers to:

a)

Delivering other products like controlling hardware components

b)

Being a standalone product for customers

c)

Operating without any hardware dependency

d)

Being a purely theoretical model

6.

Portability in software means:

a)

The software can run without security risks

b)

The software can operate across various platforms and systems

c)

The software can work only in online mode

d)

The software requires minimal maintenance

7.

Which of the following best differentiates 'software' from 'hardware'?

a)

Hardware is changeable; software is fixed

b)

Hardware degrades physically; software degrades logically

c)

Hardware is intangible; software is tangible

d)

Hardware is malleable; software is static

8.

Security as a software characteristic primarily ensures:

a)

High performance on all platforms

b)

Protection against unauthorized access and attacks

c)

Faster execution of processes

d)

Automatic adaptability to new environments

9.

Which of the following is NOT a feature of WebApps?

a)

Network-Intensive

b)

Browser-Executable

c)

Hardware-dependent execution

d)

Cross-Platform Compatibility

10.

In WebApps architecture, which component primarily handles business logic and generates responses?

a)

Web Server

b)

Application Server

c)

Database

d)

Client Browser

11.

Continuous evolution in WebApps implies:

a)

Rare updates

b)

Frequent updates and improvements

c)

Static deployment

d)

One-time release cycles

12.

Which feature ensures WebApps remain usable under different network speeds?

a)

Content-Driven Design

b)

Performance-Oriented Design

c)

Maintainability

d)

Incremental Development

13.

Availability and Accessibility in WebApps mean:

a)

They can be accessed anytime, anywhere via the internet

b)

They need specific local installation

c)

They only function on specific operating systems

d)

They are designed only for offline use

14.

The main advantage of WebApps' central maintenance is:

a)

Updates need to be installed on every user device

b)

Updates happen centrally, reducing user effort

c)

Updates are unnecessary after deployment

d)

Users can control when to apply updates

15.

Which of these is an example of a WebApp?

a)

Microsoft Word desktop version

b)

Google Docs

c)

BIOS firmware

d)

Printer driver software

16.

Which myth assumes late requirement changes are cost-free?

a)

Developer Myth

b)

Manager Myth

c)

Customer Myth

d)

Designer Myth

17.

Which is a fact contradicting the myth 'Once we write the code and it works, the job is done'?

a)

Maintenance and testing stop after delivery

b)

Maintenance, updates, and testing continue post-development

c)

Requirements never change after deployment

d)

Code never needs improvement

18.

The myth 'We have all the standards and procedures available for software development' is held by:

a)

Customers

b)

Developers

c)

Managers

d)

Testers

19.

Believing that testing is unnecessary is a myth held by:

a)

Customers

b)

Managers

c)

Developers

d)

Stakeholders

20.

Which consequence is common to all software myths?

a)

Improved decision-making

b)

Reduced project costs

c)

Unrealistic expectations and poor workflows

d)

Immediate error detection

21.

Late requirement changes mainly affect:

a)

Documentation format

b)

Cost and system stability

c)

Programming language choice

d)

File naming conventions

22.

The main difference between 'elicitation' and 'analysis' is:

a)

Elicitation collects requirements; analysis studies and organizes them

b)

Elicitation validates requirements; analysis documents them

c)

Elicitation focuses on testing; analysis focuses on coding

d)

Both are identical processes

23.

Which activity ensures requirements are correct and complete?

a)

Verification

b)

Validation

c)

Documentation

d)

Elicitation

24.

Prioritization during requirements analysis is important because:

a)

It eliminates the need for documentation

b)

It decides which requirements should be addressed first

c)

It ensures no requirements are gathered

d)

It replaces the need for testing

25.

Modeling requirements helps by:

a)

Hiding ambiguities

b)

Creating visual representations to aid understanding

c)

Eliminating the need for stakeholders

d)

Automating all coding tasks

26.

Verification of requirements ensures they are:

a)

Ambiguous and flexible

b)

Clear, unambiguous, and testable

c)

Costly and changeable

d)

Ignored in design

27.

Which requirement gathering method is most effective for capturing real-time user behavior?

a)

Interviews

b)

Observations

c)

Surveys

d)

Brainstorming

28.

Documentation of requirements is important because:

a)

It replaces coding

b)

It clearly states what is required

c)

It prevents stakeholder communication

d)

It increases ambiguity

29.

An SRS document's main role in communication is to:

a)

Reduce cost of programming languages

b)

Act as a formal agreement between customers and developers

c)

Serve as a replacement for system testing

d)

Eliminate the need for project planning

30.

Functional requirements in an SRS define:

a)

How fast the system should perform

b)

Security and reliability aspects

c)

Specific features, calculations, and user interactions

d)

Project constraints and dependencies

31.

Non-functional requirements in an SRS focus on:

a)

Describing algorithms in detail

b)

Performance, usability, and security constraints

c)

Functional modules of the system

d)

Use cases and workflows

32.

Use cases in an SRS are useful for:

a)

Providing abstract mathematical models

b)

Describing real user interactions with the system

c)

Replacing the need for test cases

d)

Detailing low-level algorithms

33.

The 'System Context' in an SRS should specify:

a)

Design patterns and classes

b)

The environment where the software will operate

c)

A list of user interface elements only

d)

Possible code libraries

34.

A well-prepared SRS reduces development costs primarily by:

a)

Eliminating the need for designers

b)

Preventing misunderstandings and rework

c)

Reducing the need for testing

d)

Avoiding requirement validation

35.

Which of the following is NOT typically included in an SRS?

a)

Functional Requirements

b)

Non-functional Requirements

c)

Source Code Implementation

d)

Use Cases

36.

The completeness of an SRS means:

a)

It only includes critical requirements

b)

It covers all functional and non-functional requirements

c)

It is free from spelling errors

d)

It contains only developer-approved content

37.

Requirements traceability primarily ensures:

a)

All requirements are implemented and tested

b)

The project scope remains undefined

c)

Functional requirements are omitted

d)

System design is skipped

38.

Change traceability is essential because it:

a)

Helps in ignoring ripple effects of modifications

b)

Tracks the impact of changes on the system

c)

Prevents the addition of new requirements

d)

Eliminates the need for regression testing

39.

Which tool is most commonly used for mapping relationships between requirements and artifacts?

a)

Gantt Chart

b)

Traceability Matrix

c)

Use Case Diagram

d)

Data Flow Diagram

40.

One key benefit of traceability is:

a)

Increased ambiguity

b)

Reduced risk

c)

Reduced requirement documentation

d)

Limited test coverage

41.

Requirements management tools with traceability features are used to:

a)

Write program code directly

b)

Manage, track, and relate requirements to design and tests

c)

Replace system models

d)

Automate debugging

42.

Improved quality from traceability mainly comes from:

a)

Ensuring requirements are never changed

b)

Ensuring requirements are consistently verified and validated

c)

Removing stakeholder input

d)

Limiting the scope of testing

43.

An unambiguous requirement in an SRS means:

a)

It can be interpreted in multiple ways

b)

It has only one clear meaning

c)

It avoids specifying outcomes

d)

It is flexible for developer interpretation

44.

Modifiability in an SRS ensures:

a)

Requirements can be updated without affecting clarity

b)

No changes can be made

c)

Changes are undocumented

d)

The document is replaced frequently

45.

Verifiability in an SRS means:

a)

Requirements are vague but testable

b)

Requirements can be tested to confirm implementation

c)

Requirements are based only on user preference

d)

Testing is not required for the requirement

46.

Feasibility ensures requirements are:

a)

Ambiguous and costly

b)

Technically and operationally possible

c)

Only aesthetically pleasing

d)

Ignored during design

47.

The main objective of IEEE 830 is to:

a)

Define programming languages for SRS

b)

Standardize the structure and content of SRS documents

c)

Automate requirement gathering

d)

Eliminate all non-functional requirements

48.

In IEEE 830, the 'Overall Description' section focuses on:

a)

Detailed algorithms

b)

High-level system overview without detailed requirements

c)

Source code listing

d)

Testing procedures

49.

The 'Specific Requirements' section in IEEE 830 includes:

a)

Functional, non-functional requirements, and interfaces

b)

Only project objectives

c)

Only high-level diagrams

d)

Developer bios

50.

Which is NOT a benefit of following IEEE 830 guidelines?

a)

Uniform format for SRS documents

b)

Clear communication among stakeholders

c)

Increased ambiguity in requirements

d)

Better planning and estimation

51.

Which section of IEEE 830 SRS would list hardware and regulatory constraints?

a)

Introduction

b)

Overall Description

c)

Specific Requirements

d)

Use Cases

52.

The 'Purpose' in the Introduction section of IEEE 830 SRS explains:

a)

Who the development team members are

b)

Why the document exists and what it aims to achieve

c)

How the source code is structured

d)

What tools are used for development

53.

Decision tables are most effective when:

a)

There are few simple rules

b)

There are multiple conditions with complex combinations

c)

No conditions are required

d)

System logic is sequential without choices

54.

In decision trees, leaf nodes represent:

a)

Initial conditions

b)

Branching options

c)

Final actions or outcomes

d)

Conflicting requirements

55.

One major advantage of decision trees over plain text is:

a)

They reduce the need for documentation

b)

They visually represent branching logic clearly

c)

They eliminate the need for testing

d)

They prevent requirement changes

56.

Formal methods are mainly applied in:

a)

Casual gaming software

b)

Safety-critical systems like medical devices

c)

Social media platforms only

d)

Simple calculator applications

57.

The key advantage of formal methods is:

a)

Delaying error detection until after coding

b)

Early detection of errors and inconsistencies

c)

Reduced need for specification

d)

Eliminating all stakeholder involvement

58.

In axiomatic specification, preconditions define:

a)

What must be true before the operation starts

b)

What is guaranteed after the operation finishes

c)

Optional steps for the operation

d)

The internal algorithm

59.

In algebraic specification, 'sorts' define:

a)

The operations on data types

b)

The data types themselves

c)

The algorithm flow

d)

The final output

60.

Which is NOT a limitation of formal methods?

a)

Require special training

b)

Can be costly and time-consuming

c)

Easy to apply to large complex systems

d)

Hard to apply to large complex systems