🎧 New: AI-Generated Podcasts Turn your study notes into engaging audio conversations. Learn more

IIBA Requirements Analysis and Design
37 Questions
0 Views

IIBA Requirements Analysis and Design

Created by
@ProblemFreeGiant

Podcast Beta

Play an AI-generated podcast conversation about this lesson

Questions and Answers

What is the purpose of Specify and Model Requirements?

To analyze, synthesize, and refine elicitation results into requirements and designs.

What are the outputs referred to as when the focus is on understanding the need?

  • Requirements (correct)
  • Models
  • Solutions
  • Designs
  • Models serve as a descriptive and visual way to convey information to a __________ audience.

    specific

    Match the following model categories with their representations:

    <p>People and Roles = Organizations, groups of people, roles, and relationships Rationale = 'Why' of a change Activity Flow = Sequence of actions, events, or course taken</p> Signup and view all the answers

    What is the purpose of Verify Requirements?

    <p>To ensure that requirements and designs meet quality standards and are usable for their purpose.</p> Signup and view all the answers

    Which of the following are characteristics of quality requirements and designs? (Select all that apply)

    <p>Complete</p> Signup and view all the answers

    Verification activities in the requirements analysis process are only performed once at the end.

    <p>False</p> Signup and view all the answers

    Checklists are used for quality control when ___________ requirements and designs.

    <p>verifying</p> Signup and view all the answers

    What does the Requirements Analysis and Design Definition knowledge area cover?

    <p>Discovering requirements during elicitation activities</p> Signup and view all the answers

    Business analysts play a key role in modeling needs, requirements, designs, and solutions.

    <p>True</p> Signup and view all the answers

    What is the main difference between requirements and designs?

    <p>usage</p> Signup and view all the answers

    The Business Analysis Core Concept Modelâ„¢ describes the relationships among __ core concepts.

    <p>six</p> Signup and view all the answers

    Match the following core concepts with their definitions:

    <p>Change = the act of transformation in response to a need Need = a problem or opportunity to be addressed Solution = a specific way of satisfying one or more needs within a context Stakeholder = a group or individual with a relationship to the change, the need, or the solution Value = the worth, importance, or usefulness of something to a stakeholder within a context Context = the circumstances that influence, are influenced by, and provide understanding of the change</p> Signup and view all the answers

    What are some techniques used to represent capabilities?

    <p>All of the above</p> Signup and view all the answers

    Which of the following are techniques used to represent data and information?

    <p>All of the above</p> Signup and view all the answers

    Business analysts should use the same models for all stakeholders.

    <p>False</p> Signup and view all the answers

    What is the purpose of decomposing business analysis information?

    <p>To further examine the components for necessary changes, what should remain the same, missing components, unnecessary components, and constraints or assumptions.</p> Signup and view all the answers

    Requirements should exhibit the characteristics of __________ and designs quality.

    <p>requirements</p> Signup and view all the answers

    Match the following techniques with their descriptions:

    <p>Data Dictionary = Used to record details about the data involved in the change State Modelling = Specify the different states of a part of the solution throughout a life cycle Decision Modelling = Represent decisions in a model to show the elements of decision making required Prototyping = Assist stakeholders in visualizing the appearance and capabilities of a planned solution</p> Signup and view all the answers

    What is the purpose of Validate Requirements?

    <p>To ensure that all requirements and designs align to the business requirements and support the delivery of needed value.</p> Signup and view all the answers

    Which of the following are considered inputs for Validate Requirements? (Select all that apply)

    <p>Guidelines and Tools</p> Signup and view all the answers

    Validated requirements and designs are those that do not align with the business goals and objectives of the change.

    <p>False</p> Signup and view all the answers

    Identify one technique used in Validate Requirements that involves identifying previously documented business needs.

    <p>Document Analysis</p> Signup and view all the answers

    What helps ensure that a set of requirements is complete?

    <p>architecture</p> Signup and view all the answers

    What quality criteria should relationships between requirements satisfy?

    <p>Defined</p> Signup and view all the answers

    Architecture management software can help manage the volume, complexity, and versions of relationships within requirements architecture.

    <p>True</p> Signup and view all the answers

    Data Modelling is used to describe the requirements structure as it relates to ___________.

    <p>data</p> Signup and view all the answers

    What is requirements architecture?

    <p>Requirements architecture is the structure of all requirements of a change, fitting individual models and specifications together to support business objectives and produce useful outcomes for stakeholders.</p> Signup and view all the answers

    What are the purposes of using requirements architecture according to the content?

    <p>Understand appropriate models for the domain, solution scope, and audience.</p> Signup and view all the answers

    Traceability is intended to demonstrate how elements work in harmony to support business requirements.

    <p>False</p> Signup and view all the answers

    A ________ is a set of conventions that define how requirements will be represented, organized, and related, providing templates for different stakeholder groups.

    <p>viewpoint</p> Signup and view all the answers

    Match the following viewpoints with their descriptions:

    <p>Business process models = Representation of how business processes operate Data models and information = Organization of data and related information User interactions = Focus on user experience and use cases Audit and security = Concerned with auditing processes and security measures Business models = Overview of the business structure and operations</p> Signup and view all the answers

    What is the purpose of the solution approach in defining design options?

    <p>To decide whether solution components will be created or purchased, or a combination of both.</p> Signup and view all the answers

    What are the types of solution approaches mentioned in the text?

    <p>All of the above</p> Signup and view all the answers

    Requirements allocation is the process of assigning design options to solution components.

    <p>False</p> Signup and view all the answers

    Identify Improvement Opportunities involves comparing opportunities to improve the operation of the business such as increasing ____________.

    <p>efficiencies</p> Signup and view all the answers

    Match the following with their descriptions:

    <p>Increase Efficiencies = Automate or simplify work processes Improve Access to Information = Provide greater amounts of information to staff Identify Additional Capabilities = Highlight potential capabilities that can provide future value</p> Signup and view all the answers

    Study Notes

    Requirements Architecture

    • A requirements architecture is the structure of all requirements of a change, ensuring they form a cohesive whole that supports business objectives and produces a useful outcome for stakeholders.
    • It organizes requirements into structures relevant to different stakeholders, illustrating how they interact and relate to each other.
    • It ensures all requirements work together to achieve overall objectives and facilitates trade-off decisions considering overall objectives.

    Purpose of Requirements Architecture

    • Not intended to demonstrate traceability, but to show how elements work in harmony to support business requirements.
    • Ensures requirements work together to achieve overall objectives, making trade-off decisions possible.

    Inputs to Define Requirements Architecture

    • Information Management Approach: defines how business analysis information is stored and accessed.
    • Requirements (any state): every requirement should be stated once and incorporated into the requirements architecture for completeness evaluation.
    • Solution Scope: must be considered to ensure the requirements architecture aligns with the desired solution boundaries.

    Elements of Requirements Architecture

    Viewpoints and Views

    • A viewpoint is a set of conventions defining how requirements will be represented, organized, and related.
    • Viewpoints provide templates for addressing stakeholder concerns, including model types, attributes, notations, and analytical approaches.
    • Examples of viewpoints include business process models, data models, user interactions, audit and security, and business models.
    • Each viewpoint has different model notations and techniques, and each is important for a cohesive final solution.
    • A view is the actual requirements and designs for a particular solution from a chosen viewpoint.
    • A collection of views makes up the requirements architecture for a specific solution.

    Template Architectures

    • An architectural framework is a collection of viewpoints standard across an industry, sector, or organization.

    • Frameworks can be used as predefined templates to start defining an architecture.### Definition of Requirements Analysis and Design

    • The Requirements Analysis and Design Definition knowledge area describes the tasks that business analysts perform to structure and organize requirements discovered during elicitation activities, specify and model requirements and designs, validate and verify information, identify solution options that meet business needs, and estimate the potential value that could be realized for each solution option.

    Tasks in Requirements Analysis and Design

    • Specify and Model Requirements: describes a set of requirements or designs in detail using analytical techniques.
    • Verify Requirements: ensures that a set of requirements or designs has been developed in enough detail to be usable by a particular stakeholder, is internally consistent, and is of high quality.
    • Validate Requirements: ensures that a set of requirements or designs delivers business value and supports the organization's goals and objectives.
    • Define Requirements Architecture: structures all requirements and designs so that they support the overall business purpose for a change and that they work effectively as a cohesive whole.
    • Define Solution Options: identifies, explores, and describes different possible ways of meeting the need.
    • Analyze Potential Value and Recommend Solution: assesses the business value associated with a potential solution and compares different options, including trade-offs, to identify and recommend the solution option that delivers the greatest overall value.

    The Business Analysis Core Concept Model

    • The Business Analysis Core Concept Model (BACCM) describes the relationships among the six core concepts: Change, Need, Solution, Stakeholder, Value, and Context.
    • Within the context of Requirements Analysis and Design Definition, the core concepts are used to:
      • Transform elicitation results into requirements and designs (Change).
      • Analyze the needs in order to recommend a solution that meets the needs (Need).
      • Define solution options and recommend the one that is most likely to address the need and has the most value (Solution).
      • Tailor the requirements and designs so that they are understandable and usable by each stakeholder group (Stakeholder).
      • Analyze and quantify the potential value of the solution options (Value).
      • Model and describe the context in formats that are understandable and usable by all stakeholders (Context).

    Specify and Model Requirements

    • The purpose of Specify and Model Requirements is to analyze, synthesize, and refine elicitation results into requirements and designs.
    • This task includes capturing information about attributes or metadata about the requirements.
    • The specifying and modeling activities relate to all requirement types.
    • Models can be used to:
      • Convey information to a specific audience in order to support analysis, communication, and understanding.
      • Confirm knowledge, identify information gaps, and identify duplicate information.
    • Business analysts choose from one or more of the following modeling formats:
      • Matrices: used for data dictionaries, requirements traceability, or gap analysis.
      • Diagrams: used to depict complexity in a way that would be difficult to do with words.
    • Model categories can include:
      • People and Roles: models represent organizations, groups of people, roles, and their relationships within an enterprise and to a solution.
      • Rationale: models represent the ‘why’ of a change.
      • Activity Flow: models represent a sequence of actions, events, or a course that may be taken.### Requirements Architecture
    • A framework can be populated with domain-specific information to form a collection of views that serves as a template to build architecture from.
    • Ensures that a set of requirements is complete, cohesive, and tells a full story.
    • Helps identify gaps in requirements through iterations of elicitation, specification, and analysis activities.

    Completeness

    • The entire set of requirements should be understood by the audience in a way that determines completeness.
    • No requirements should be missing, inconsistent, or contradictory to one another.
    • Structuring requirements according to different viewpoints helps ensure completeness.

    Relate and Verify Requirements Relationships

    • Requirements may be related to each other in several ways, and business analysts examine and analyze these relationships.
    • Relationships should be defined, necessary, correct, unambiguous, and consistent.
    • Tracing requirements helps represent these relationships.

    Business Analysis Information Architecture

    • The structure of business analysis information is an information architecture.
    • Defines how all business analysis information for a change relates.
    • Describes relationships for types of information such as requirements, designs, models, and elicitation results.

    Guidelines and Tools

    • Architecture management software helps manage the volume, complexity, and versions of relationships within the requirements architecture.
    • Legal/regulatory information, methodologies, and frameworks also impact the requirements architecture.

    Techniques

    • Data modelling, functional decomposition, interviews, organizational modelling, scope modelling, and workshops are used to define the requirements structure.

    Stakeholders

    • Domain subject matter experts, implementation subject matter experts, project managers, sponsors, testers, and any stakeholder may assist in defining and confirming the requirements architecture.

    Outputs

    • The requirements architecture includes the requirements and their interrelationships, as well as contextual information.

    Define Design Options

    • The purpose of Define Design Options is to define the solution approach, identify opportunities to improve the business, allocate requirements across solution components, and represent design options.
    • Design options exist at a lower level than the change strategy and are tactical rather than strategic.

    Inputs

    • Change strategy describes the approach to transition to the future state.
    • Validated and prioritized requirements are considered in design options.
    • Requirements architecture is important for defining design options that can address the holistic set of requirements.

    Studying That Suits You

    Use AI to generate personalized quizzes and flashcards to suit your learning preferences.

    Quiz Team

    Description

    This quiz covers the definition and tasks involved in the Requirements Analysis and Design knowledge area, as described by the IIBA. It is a crucial part of strategy analysis and involves understanding the business needs.

    Use Quizgecko on...
    Browser
    Browser