01.11.2017 Views

BABOK_Guide_v3_member_copy

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Requirements Analysis and Design Definition<br />

Define Requirements Architecture<br />

Figure 7.4.1: Define Requirements Architecture Input/Output Diagram<br />

Input<br />

<strong>Guide</strong>lines and Tools<br />

Requirements<br />

(any state)<br />

3.4<br />

Information<br />

Management<br />

Approach<br />

6.4<br />

Solution Scope<br />

Architecture Management<br />

Software<br />

Legal/Regulatory<br />

Information<br />

Methodologies and<br />

Framework<br />

7.4.4 Elements<br />

.1 Requirements Viewpoints and Views<br />

A viewpoint is a set of conventions that define how requirements will be<br />

represented, how these representations will be organized, and how they will be<br />

related. Viewpoints provide templates for addressing the concerns of particular<br />

stakeholder groups.<br />

Requirements viewpoints frequently include standards and guidelines for the:<br />

• model types used for requirements,<br />

• attributes that are included and consistently used in different models,<br />

• model notations that are used, and<br />

7.4<br />

Define Requirements<br />

Architecture<br />

Output<br />

7.4<br />

Requirements<br />

Architecture<br />

Tasks Using This Output<br />

5.3<br />

Prioritize<br />

Requirements<br />

7.1<br />

Specify and Model<br />

Requirements<br />

5.4<br />

Assess<br />

Requirements<br />

Changes<br />

7.5<br />

Define Design<br />

Options<br />

• analytical approaches used to identify and maintain relevant relationships<br />

among models.<br />

Complimentary IIBA® Member Copy. Not for Distribution or Resale.<br />

149

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!