Software Engineering Chapter 2: Requirements Engineering

<p>Identifying stakeholders (A)</p> Signup and view all the answers

<p>Experiencing budget overruns (C)</p> Signup and view all the answers

<p>Operational Feasibility (A)</p> Signup and view all the answers

<p>It is an iterative process (D)</p> Signup and view all the answers

<p>Requirement Validation (D)</p> Signup and view all the answers

<p>To ensure completeness, consistency, accuracy, and stakeholder satisfaction (D)</p> Signup and view all the answers

<p>Tracking changes and maintaining communication with stakeholders (C)</p> Signup and view all the answers

<p>Checking that requirements are specified correctly and are error-free (C)</p> Signup and view all the answers

<p>Error propagation to later stages leading to modifications and rework (C)</p> Signup and view all the answers

<p>By ensuring all changes are documented and communicated effectively (C)</p> Signup and view all the answers

<p>Keeping track of different versions of the requirements document (C)</p> Signup and view all the answers

<p>System Requirements Specification (SRS) (B)</p> Signup and view all the answers

<p>User experience enhancement (C)</p> Signup and view all the answers

<p>Ensures the software is developed according to stakeholder needs (A)</p> Signup and view all the answers

<p>It can be time-consuming and costly if not managed well (D)</p> Signup and view all the answers

<p>Stakeholder engagement (C)</p> Signup and view all the answers

<p>Linking requirements to design, testing, and validation (B)</p> Signup and view all the answers

<p>Effective monitoring and reporting (A)</p> Signup and view all the answers

<p>To outline software goals for stakeholders (D)</p> Signup and view all the answers

<p>Code Review (C)</p> Signup and view all the answers

<p>Both functional and non-functional requirements (A)</p> Signup and view all the answers

<p>Monitor and analyze stakeholder work (A)</p> Signup and view all the answers

<p>They are written in natural language for end users. (C)</p> Signup and view all the answers

<p>Validate the system against documented requirements (C)</p> Signup and view all the answers

<p>Is created after the development phase (C)</p> Signup and view all the answers

<p>To facilitate group discussions among stakeholders (A)</p> Signup and view all the answers

An initial evaluation to determine if a project is worth pursuing.

Examines if a project can be completed given the available technology, skills, and resources.

Analyzes if the software will effectively address the business problem and align with the user's needs.

Analyzes the cost of developing the software and compares it to the potential benefits.

Examines if the project complies with legal regulations and ethical standards.

Assesses the time needed to complete the project and its feasibility within that timeframe.

The process of gathering and analyzing information about user needs, system requirements, and other stakeholder expectations.

Identifying and understanding all the individuals or groups who have an interest in the software project.

A technique used in requirements engineering to gather information directly from stakeholders through structured conversations.

A technique that utilizes questionnaires distributed among stakeholders to collect data on requirements.

A group discussion method where a small group of stakeholders collectively explore and discuss requirements.

A technique where analysts observe stakeholders' work processes and interactions to gather information on needs and requirements.

A document that outlines the software's goals, objectives, and how they align with the business's overall goals.

A document that describes the software's functionalities and features from the user's perspective.

A formal document that comprehensively describes all the requirements gathered and analyzed.

Requirements related to the software's functionality, such as the tasks it should perform or the data it should handle.

Linking requirements to design, testing, and validation to ensure everything aligns and works together.

Communicating requirements clearly to everyone involved, and managing any changes quickly.

Keeping track of the requirements process and reporting progress, ensuring everything is on track.

The process of defining the needs and expectations of a software system.

The ability of software to meet the needs and expectations of stakeholders. It is a key benefit of Requirements Engineering.

A document detailing the system's functionality, its features, and how it interacts with users, often using models for clarity.

The process of ensuring that the requirements are accurate, complete, consistent, and meet the expectations of all stakeholders.

The process of checking if the requirements are correctly defined and free from errors.

The process of determining if the requirements actually meet the needs and expectations of the stakeholders.

Managing and controlling changes to requirements throughout the software development process, while ensuring communication with stakeholders.

Tracking changes to requirements requested by customers or stakeholders.

Maintaining different versions of the requirements document (SRS) and keeping track of their changes.