Requirements Analysis & Design Definition - part 1

Question 1

What is the purpose of Specify and Model Requirements?

Answer 1

• Analyze
• Synthesize
• Refine elicitation results into requirements and designs

Question 2

What is the purpose of Verify Requirements?

Answer 2

Ensure that requirements and designs specifications and models meet quality standards and are usable for the purpose they serve.

Question 3

What is the purpose of Validate Requirements?

Answer 3

Ensure that all requirements and designs align to the business requirements and support the delivery of needed value.

Question 4

When and what for Matrices are used?

Answer 4

When the business analyst is modelling a requirement or set of requirements that have a complex but uniform structure. Matrices may be used for data dictionaries, requirements traceability, prioritizing requirements or for gap analysis.

Question 5

What are the Diagrams?

Answer 5

Visual, often pictorial, representation of a requirement or set of requirements. Especially useful to depict complexity in a way that would be difficult to do with words.

Question 6

Acceptance and Evaluation Criteria

Answer 6

Used to represent the acceptance and evaluation criteria attributes of requirements.

Question 7

Business Capability Analysis

Answer 7

Used to represent features or functions of an enterprise.

Question 8

Business Model Canvas

Answer 8

Used to describe the rationale for requirements.

Question 9

Business Rules Analysis

Answer 9

Used to analyze business rules so that they can be specified and modelled alongside requirements.

Question 10

Concept Modelling

Answer 10

Used to define terms and relationships relevant to the change and the enterprise.

Question 11

Data Dictionary

Answer 11

Used to record details about the data involved in the change. Details may include definitions, relationships with other data, origin, format, and usage.

Question 12

Data Flow Diagrams

Answer 12

Used to visualize data flow requirements.

Question 13

Data Modelling

Answer 13

Used to model requirements to show how data will be used to meet stakeholder information needs.

Question 14

Decision Modelling.

Answer 14

Used to represent decisions in a model in order to show the elements of decision making required.

Question 15

Functional Decomposition

Answer 15

Used to model requirements in order to identify
constituent parts of an overall complex business function.

Question 16

Glossary

Answer 16

Used to record the meaning of relevant business terms while analyzing requirements.

Question 17

Interface Analysis

Answer 17

Used to model requirements in order to identify and validate inputs and outputs of the solution they are modelling.

Question 18

Non-Functional Requirements Analysis

Answer 18

Used to define and analyze the quality of service attributes.

Question 19

Organizational Modelling

Answer 19

Used to allow business analysts to model the
roles, responsibilities, and communications within an organization.

Question 20

Process Modelling

Answer 20

Used to show the steps or activities that are performed in the organization, or that must be performed to meet the desired change.

Question 21

Prototyping

Answer 21

Used to assist the stakeholders in visualizing the appearance and capabilities of a planned solution.

Question 22

Roles and Permissions Matrix

Answer 22

Used to specify and model requirements
concerned with the separation of duties among users and external interfaces in utilizing a solution.

Question 23

Root Cause Analysis

Answer 23

Used to model the root causes of a problem as part of rationale.

Question 24

Scope Modelling

Answer 24

Used to visually show a scope boundary.

Question 25

Sequence Diagrams

Answer 25

Used to specify and model requirements to show how processes operate and interact with one another, and in what order.

Question 26

Stakeholder List, Map, or Personas

Answer 26

Used to identify the stakeholders and their characteristics.

Question 27

State Modelling

Answer 27

Used to specify the different states of a part of the solution throughout a life cycle, in terms of the events that occur.

Question 28

Use Cases and Scenarios

Answer 28

Used to model the desired behaviour of a solution, by showing user interactions with the solution, to achieve a specific goal or accomplish a particular task.

Question 29

User Stories

Answer 29

Used to specify requirements as a brief statement about what people do or need to do when using the solution.

Question 30

Specify and Model Requirements model categories can include:

Answer 30

* People and Roles * Rationale * Activity Flow * Capability * Data and Information

Question 31

Modelling Notations/Standards

Answer 31

Allow requirements and designs to be precisely specified and help to ensure that the right information is provided about the requirements.

Question 32

Modelling Tools

Answer 32

Software products that facilitate drawing and storing matrices and diagrams to represent requirements.

Question 33

Requirements Architecture

Answer 33

The requirements and interrelationships among them can be used to ensure models are complete and consistent.

Question 34

Requirements Life Cycle Management Tools

Answer 34

Software products that facilitate recording, organizing, storing, and sharing requirements and designs.

Question 35

Solution Scope

Answer 35

The boundaries of the solution provide the boundaries for the requirements and designs models.

Question 36

What are 4 Verify Requirements techniques?

Answer 36

* Acceptance and Evaluation Criteria * Item Tracking * Metrics and Key Performance Indicators (KPIs) * Reviews

Question 37

What are 7 Validate Requirements techniques?

Answer 37

* Acceptance and Evaluation Criteria * Document Analysis, Item Tracking * Financial Analysis * Metrics and Key Performance Indicators (KPIs) * Reviews * Risk Analysis and Management

Question 38

Characteristics of Requirements and Designs Quality

Answer 38

Atomic, Complete, Consistent, Concise, Feasible, Unambiguous, Testable, Prioritized, Understandable.

Question 39

Validate Requirements Tools

Answer 39

* Business Objectives * Future State Description * Potential Value * Solution Scope

Question 40

Document Analysis

Answer 40

Used to identify previously documented business needs in order to validate requirements.

Question 41

Financial Analysis

Answer 41

Used to define the financial benefits associated with requirements.

Question 42

Item Tracking

Answer 42

Used to ensure that any problems or issues identified during validation are managed and resolved

Question 43

Metrics and Key Performance Indicators (KPIs)

Answer 43

Used to select appropriate performance measures for a solution, solution component, or requirement.

Question 44

Reviews

Answer 44

Used to confirm whether or not the stakeholder agrees that their needs are met.

Question 45

Risk Analysis and Management

Answer 45

Used to identify possible scenarios that would alter the benefit delivered by a requirement.