Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

ECBA - II edycja > Requirements Analysis & Design Definition - part 1 > Flashcards

Requirements Analysis & Design Definition - part 1 Flashcards

1
Q

What is the purpose of Specify and Model Requirements?

A
  • Analyze
  • Synthesize
  • Refine elicitation results into requirements and designs
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What is the purpose of Verify Requirements?

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What is the purpose of Validate Requirements?

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

When and what for Matrices are used?

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What are the Diagrams?

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Acceptance and Evaluation Criteria

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Business Capability Analysis

A

Used to represent features or functions of an enterprise.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Business Model Canvas

A

Used to describe the rationale for requirements.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Business Rules Analysis

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Concept Modelling

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Data Dictionary

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Data Flow Diagrams

A

Used to visualize data flow requirements.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Data Modelling

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Decision Modelling.

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Functional Decomposition

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Glossary

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Interface Analysis

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Non-Functional Requirements Analysis

A

Used to define and analyze the quality of service attributes.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Organizational Modelling

A

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

20
Q

Process Modelling

A

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

21
Q

Prototyping

A

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

22
Q

Roles and Permissions Matrix

A

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

23
Q

Root Cause Analysis

A

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

24
Q

Scope Modelling

A

Used to visually show a scope boundary.

25
Q

Sequence Diagrams

A

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

26
Q

Stakeholder List, Map, or Personas

A

Used to identify the stakeholders and
their characteristics.

27
Q

State Modelling

A

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

28
Q

Use Cases and Scenarios

A

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.

29
Q

User Stories

A

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

30
Q

Specify and Model Requirements model categories can include:

A
  • People and Roles
  • Rationale
  • Activity Flow
  • Capability
  • Data and Information
31
Q

Modelling Notations/Standards

A

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

32
Q

Modelling Tools

A

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

33
Q

Requirements Architecture

A

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

34
Q

Requirements Life Cycle Management Tools

A

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

35
Q

Solution Scope

A

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

36
Q

What are 4 Verify Requirements techniques?

A
  • Acceptance and Evaluation Criteria
  • Item Tracking
  • Metrics and Key Performance Indicators (KPIs)
  • Reviews
37
Q

What are 7 Validate Requirements techniques?

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

Characteristics of Requirements and Designs Quality

A

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

39
Q

Validate Requirements Tools

A
  • Business Objectives
  • Future State Description
  • Potential Value
  • Solution Scope
40
Q

Document Analysis

A

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

41
Q

Financial Analysis

A

Used to define the financial benefits associated with requirements.

42
Q

Item Tracking

A

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

43
Q

Metrics and Key Performance Indicators (KPIs)

A

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

44
Q

Reviews

A

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

45
Q

Risk Analysis and Management

A

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

ECBA - II edycja (11 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions