Strategic Analysis and Requirements Management Quiz

The process of gathering information about stakeholder needs, including their tasks, knowledge, and desired outcomes.

A structured technique to generate ideas from a group of people for brainstorming, problem-solving, or requirement gathering.

A technique where stakeholders discuss a topic, often facilitated by a moderator, providing insights and feedback.

A method of gathering information through formal or informal conversations with individuals to understand their needs, perspectives, and requirements.

The process of observing stakeholder behaviors and interactions in their natural environment to identify needs, challenges, and opportunities.

A method of creating a sample version of a product or service to test and refine requirements with stakeholders.

A structured meeting where stakeholders collaboratively define and analyze their needs, creating a shared understanding of project goals.

A method of collecting data through questionnaires or surveys sent to a wide audience, enabling analysis of collective preferences and perspectives.

The organization's present situation, including resources, capabilities, and market position.

The organization's desired future, including goals, objectives, and how it wants to be perceived.

The roadmap or plan outlining how the organization will move from its current state to its desired target state.

A set of actions and decisions taken to achieve a strategic goal.

Understanding the overall direction and purpose of the organization.

Ensuring the documented requirements accurately reflect what the customer truly wants.

The cost of fixing an error in requirements is significantly higher than fixing a development error.

Verifying that documented requirements match the customer's expectations.

A formal review and approval process for documented requirements.

A more informal approach, but still requiring clarity and refinement before implementation.

Do the requirements accurately reflect the customer's needs and expectations?

Are there any conflicting or contradictory requirements?

Are all essential functions and constraints included in the requirements?

Requirements that change during development or when the system is in use.

Requirements that change due to the system environment or the domain.

Requirements that emerge as the understanding of the system develops.

Requirements that result from the introduction of another computer system or any other solution introduced in the business (change of work processes).

Requirements that depend on other systems or organizational processes.

The ability to trace the source of a feature or requirement from any later point in the business change or software development cycle. "What was the source for this requirement and who raised it?"

The ability to identify any requirement and track where it has been developed and implemented. "What happened to this requirement?"

Tracing a requirement up or down the requirements hierarchy.

A visual representation of how actors interact with a system and what functionalities they need.

A stick figure that represents a user or external system interacting with a software system.

A description of a specific goal an actor wants to achieve with the system, including necessary actions and expected system responses.

A rectangle in a Use Case Diagram that represents a software system in which actors interact.

A line connecting an actor with a Use Case in a diagram, indicating that an actor can interact with a specific functionality.

A special link in a Use Case Diagram that shows how one Use Case reuses steps from another Use Case, reducing redundancy and improving clarity.

A special link in a Use Case Diagram that shows how one Use Case extends another Use Case with additional steps under specific conditions.

A visual representation of entities (data items) and their relationships in a system, helping to understand and design databases.

A project approach where requirements are defined in detail upfront and changes are managed through formal processes.

A project approach where requirements are outlined early but evolve iteratively as development progresses.

A traditional project management approach where phases are sequential and completed one at a time.

An iterative and incremental agile framework that uses short cycles called sprints.

A structured document commonly used in linear projects to capture requirements in a tabular format.

A short user-centric statement describing a feature or functionality desired by users.

A framework for developing user stories, emphasizing three elements: card, conversation, and confirmation.

A standard format for writing user stories, using the 'As a...', 'I want...', 'So that...' structure.

A collection of related user stories that represent a larger feature or initiative.

A set of criteria used to evaluate whether a user story has been successfully implemented.