Software Engineering-I MCQs with Answers
Practice important Software Engineering-I MCQs with answers and explanations.
Chapter: 4
Q81:
Which type of requirement is described from the user’s perspective?
A. Functional requirement
B. Non-functional requirement
C. Business requirement
D. User requirement
Correct Answer:
D
Chapter: 4
Q82:
________ is a key reason for project failure according to studies on over 8300 projects.
A. Over-budgeting
B. Lack of user input
C. High-quality requirements
D. Non-functional requirements
Correct Answer:
B
Chapter: 4
Q83:
Requirements that define "what to build" instead of "how to build" are often described as ________.
A. Functional
B. Non-functional
C. Ambiguous
D. Minimal
Correct Answer:
A
Chapter: 4
Q84:
Stakeholders' vague or general requirements can lead to ________.
A. well-defined features
B. project success
C. requirement misunderstandings
D. improved project tracking
Correct Answer:
C
Chapter: 4
Q85:
Involving ________ in the requirement process is essential to prevent project failure.
A. only management
B. all user types
C. developers
D. technical writers
Correct Answer:
B
Chapter: 4
Q86:
A requirement engineer should be aware that stakeholders' inputs are often ________.
A. detailed and specific
B. clear and concise
C. general and vague
D. easy to understand
Correct Answer:
C
Chapter: 4
Q87:
An example of a non-functional requirement might be ________.
A. high processing speed
B. user-friendly interfaces
C. meeting user needs
D. running on specific platform
Correct Answer:
D
Chapter: 4
Q88:
Business requirements are primarily focused on ________.
A. coding standards
B. high-level objectives
C. specific user tasks
D. system design
Correct Answer:
B
Chapter: 4
Q89:
Which requirement type often includes constraints like hardware and platform specifications?
A. Business
B. User
C. Functional
D. Non-functional
Correct Answer:
D
Chapter: 4
Q90:
The use of ambiguous language in requirements often results in ________.
A. cost savings
B. reduced project timeline
C. misunderstandings
D. higher product acceptance
Correct Answer:
C
Chapter: 4
Q91:
The identification of all ________ is essential in the requirement engineering process.
A. developers
B. stakeholders
C. project managers
D. coders
Correct Answer:
B
Chapter: 4
Q92:
What is another name for Requirement Statement?
A. Functional Requirement
B. Requirement Definition
C. User Requirement
D. System Specification
Correct Answer:
B
Chapter: 4
Q93:
Requirement Specification is used to document ________.
A. user requirements
B. design requirements
C. functional requirements
D. non-functional requirements
Correct Answer:
C
Chapter: 4
Q94:
A complete requirement should ________.
A. fully describe the functionality
B. prioritize each requirement
C. handle all errors
D. have a flexible structure
Correct Answer:
A
Chapter: 4
Q95:
Which characteristic ensures a requirement meets system capabilities?
A. Complete
B. Feasible
C. Verifiable
D. Unambiguous
Correct Answer:
B
Chapter: 4
Q96:
An unambiguous requirement is one that ________.
A. can have multiple interpretations
B. has only one consistent interpretation
C. varies according to users
D. is very flexible
Correct Answer:
B
Chapter: 4
Q97:
A verifiable requirement allows the user to ________.
A. write more tests
B. revise code
C. inspect its implementation easily
D. devise tests to check proper implementation
Correct Answer:
D
Chapter: 4
Q98:
Requirements that are _______ can be linked to their origin, design, and tests.
A. consistent
B. modifiable
C. traceable
D. ambiguous
Correct Answer:
C
Chapter: 4
Q99:
Modifiable requirements allow changes while maintaining ________.
A. functionality
B. a history of changes
C. ambiguous specifications
D. all user requests
Correct Answer:
B
Chapter: 4
Q100:
Which of the following is a non-functional requirement in an embedded system?
A. Written in Ada
B. Fit in a large memory
C. Handle all errors
D. Maintain software documentation
Correct Answer:
A