The failure of software projects in the late 1960s was attributed to the use of:

Which interdisciplinary field of SE contributes the "why" concept?

Which critical challenge for software engineers relates to the catastrophic failure potential in systems like aviation or nuclear control?

What defines what the system should NOT do, focusing on quality characteristics like speed and security?

Which quality of a good requirement means it must be possible to test the requirement?

The activity of discovering and gathering requirements from stakeholders is called:

Which document section provides the detailed list of all Functional and Non-Functional requirements?

In Requirements Management, the process of "freezing" a set of requirements at a specific point in time is called:

Which quality of a good requirement ensures that the requirement has only one way to be interpreted?

The interdisciplinary field of SE that contributes the "how much" concept, focusing on budgetary constraints.

The type of requirement that defines WHAT the system must do, such as processing a payment or generating a report.

The quality of a requirement that ensures no statement contradicts another requirement.

The systematic process of dealing with changing requirements during the development life cycle.

The challenge in Elicitation where stakeholders often don't know exactly what they want or find it hard to express their needs clearly.

A formal process for assessing and approving changes to requirements after they have been "frozen."

The quality of a requirement that must be included, covering everything the client needs.

The key reason SE is popular that refers to the ability of software to grow and change easily.

The quality of a requirement that allows it to be linked backward to the source and forward to design/testing elements.

The section of the Requirements Document that includes the product's system architecture and relationship to other products.

Software engineering is a disciplined and quantifiable approach to making software.

The use of SE principles leads to higher cost and lower quality in software products.

The Management Science field contributes the "how" concept to Software Engineering.

The three main Critical Challenges for software engineers include The Stakes, The Pressure, and The Complexity.

Requirements Engineering must occur before any coding or testing can begin.

Functional Requirements describe qualities like performance, security, and portability.

A good requirement must be Verifiable, meaning it must be possible to test.

Requirements Elicitation uses techniques like interviews, workshops, and reviewing documents.

The primary purpose of Requirements Management is to prevent any changes from ever occurring.

Baselining is the process of linking a requirement to its design and testing elements.

The Introduction section of the Requirements Document typically includes the background and goals of the product.

The Specific Requirements section is where the system architecture is described.

If a requirement is Unambiguous, it means it can be interpreted in several ways.

The concept of Traceability helps ensure changes do not break existing features.

The challenge of The Pressure relates to the increased market demands for fast turnaround times.

The Complexity challenge refers to the difficulty of building huge systems with millions of lines of code.

One reason SE is important is that it helps manage the development of large software projects.

The Requirements Management process is unnecessary in large projects because requirements never change.

A requirement is Complete if it is clear and has only one interpretation.

Software Engineering is an interdisciplinary field that relies solely on Computer Science principles.