FREE Basic Software Engineering Questions and Answers

Question 1

What are the results of the requirements analysis and specifications phase ultimately?

Accepted Answer

The SRS Document

Answer

The requirements analysis and specifications phase culminates in the creation of the Software Requirements Specification (SRS) Document. This formal document details all functional and non-functional requirements of the software system. It serves as a comprehensive blueprint, ensuring a shared understanding between stakeholders and the development team regarding what the system should do.

Question 2

Iterative process describes requirements analysis.

Accepted Answer

True

Answer

Requirements analysis is indeed an iterative process, meaning it involves repeated cycles of elicitation, analysis, specification, and validation. As stakeholders provide feedback and new insights emerge, requirements are continuously refined and clarified over time. This iterative nature helps to reduce ambiguities and ensure the final requirements accurately reflect user needs.

Question 3

What, not how, should be specified in requirements.

Accepted Answer

True

Answer

Requirements should focus on 'what' the software system needs to do, rather than 'how' it will achieve those functionalities. Specifying 'what' allows for flexibility in design and implementation, giving developers the freedom to choose the most efficient and effective technical solutions. Prematurely defining 'how' can constrain design choices and lead to less optimal solutions.

Question 4

The Software Requirement Specifications Document (SRS) is written by whom?

Accepted Answer

System Developer

Answer

The Software Requirements Specification (SRS) document is primarily written by a System Analyst. The System Analyst acts as a crucial bridge between the stakeholders (users, clients) and the development team, gathering, analyzing, and documenting the requirements. While developers use the SRS, their primary role is implementation, not initial specification writing.

Question 5

A functional requirement is which of the following?

Accepted Answer

None of the above

Answer

Portability, robustness, and maintainability are all examples of non-functional requirements, which describe quality attributes or constraints of the system. Functional requirements, in contrast, describe specific behaviors or functions the system must perform, such as 'the system shall allow users to log in.' Therefore, none of the given options represent a functional requirement.

Software Engineering Practice Test

Software Engineering Practice Test

FREE Basic Software Engineering Questions and Answers