Free Software Engineering MCQ Questions and Answers

Question 1

A system engineer collaborates with the _________ to comprehend system needs.

Accepted Answer

All of the above

Answer

A system engineer collaborates with various stakeholders to fully comprehend system needs. This includes future users who will interact with the system, the customer who commissions the project, and other stakeholders who have an interest or influence on the system. Gathering input from all these groups ensures a comprehensive understanding of requirements and a successful system.

Question 2

Requirement engineering frequently involves competing requirements, with each client arguing that their version is the correct version.

Accepted Answer

True

Answer

Requirement engineering often involves navigating competing or conflicting requirements from different stakeholders. Each client or user group may have their own priorities and perspectives, leading to disagreements about what features are most important or how certain functionalities should be implemented. Resolving these conflicts is a key challenge in the process, making the statement true.

Question 3

Requirements should only state "what," not "how."

Accepted Answer

True

Answer

A fundamental principle of good requirements engineering is to focus on 'what' the system should do, rather than 'how' it should do it. Requirements should describe the desired functionality and behavior from the user's perspective, leaving the technical implementation details to the design and development phases. This separation ensures flexibility in design choices and prevents premature design decisions.

Question 4

What is the purpose of the software development life cycle's requirements analysis and specifications phase?

Accepted Answer

Understanding the customer requirements and organize them in an informal document

Answer

The requirements analysis and specifications phase in the SDLC is primarily focused on thoroughly understanding the customer's needs and translating them into a structured, documented form. This involves gathering, analyzing, and organizing all functional and non-functional requirements to define the scope and objectives of the software project. It's about capturing and organizing what the customer wants.

Question 5

Which of the following characteristics doesn't make for a strong Software Requirements Specification (SRS)?

Accepted Answer

Ambiguous

Answer

A strong Software Requirements Specification (SRS) must be clear, precise, and unambiguous to avoid misinterpretations during development. Ambiguity in an SRS leads to confusion, rework, and potential project failures, as developers may implement features differently than intended. Therefore, an ambiguous SRS is a characteristic that *doesn't* make for a strong specification.

Software Engineering Practice Test

Software Engineering Practice Test

Free Software Engineering MCQ Questions and Answers