Example Workshop Charter
CONTEXT DIAGRAM
Purpose Statement & Agenda
Example Workshop Charter: Context Diagram
Purpose Statement & Agenda
PAYMENT PROCESSOR
WORKSHOP CHARTER
Purpose
The purpose of this workshop is to identify user roles that interface
with the Payment Processor.
Scope
The scope of this workshop includes only user roles that interact directly with
the Payment Processor. The inputs to and the outputs from the
Payment Processor will be identified respective to each user role.
Objective
The objective of this workshop is to create a visual model of the
user roles that interact with the Payment Processor.
Deliverable
The deliverable of this workshop is a CONTEXT DIAGRAM with the
Payment Processor as the system boundary.
*************************************************************************************
Payment Processor Workshop Agenda
 Introduction
 Identify the System Boundary
 Identify User Roles
 Identify Information Flow
 Review & Wrap Up
Page 2 – Example Workshop Charter
Copyright © 2017 Requirements Quest®. All rights reserved.
Example Workshop Charter: Context Diagram
Annotated Agenda
Annotated Agenda
Payment Processor Workshop Annotated Agenda
WORKSHOP START

Introduce Myself and the Documenter

Two Truths and a Lie Introductions

Review the Workshop Purpose Statement
Show Purpose Statement visual aid.
Purpose
The purpose of this workshop is to identify user roles that
interface with the Payment Processor.
Scope
The scope of this workshop includes only user roles that
interact directly with the Payment Processor. The inputs to and
the outputs from the Payment Processor will be identified
respective to each user role.
Objective
The objective of this workshop is to create a visual model of the
user roles that interact with the Payment Processor.
Deliverable
The deliverable of this workshop is a context diagram with the
Payment Processor as the system boundary.

Review the current-state Relationship Map
Show Relationship Map (for the project) visual aid.
Copyright © 2017 Requirements Quest®. All rights reserved.
Example Workshop Charter – Page 3
Annotated Agenda

Example Workshop Charter: Context Diagram
Describe the agenda
Show Agenda visual aid.
Agenda





Introduction
Identify the System Boundary
Identify User Roles
Identify Information Flow
Review & Wrap Up
Show EXAMPLE Context Diagram visual aids while explaining agenda steps.
Step 1: Identify the System Boundary
Example: In the context of the Shopping Cart Project, one of the entities that are affected is
the RQ Website. The RQ Website is an example of a system boundary.
Step 2: Identify User Roles
Example: Examples of user roles that interact directly with the RQ Website are Website
Administrator, Customer, and Payment Processor.
Step 3: Identify Information Flow
Example: Inputs to the RQ Website from the customer include product selections and
payment information. Outputs from the RQ Website to the Customer include product
information and purchase confirmation.

Review the ground rules
Show Ground Rules visual aid.
Ground Rules







Page 4 – Example Workshop Charter
All participants are equal.
No job titles.
One conversation at a time.
Be punctual. Return from breaks on time.
Listen to others.
Contribute solutions.
Defer judgment.
Copyright © 2017 Requirements Quest®. All rights reserved.
Example Workshop Charter: Context Diagram
Annotated Agenda
WORKSHOP PROCESS
Agenda Step 1: Identify the System Boundary
Estimated 5 minutes
Time
Purpose Identify a specific entity that is the focal point of the discussion (system
boundary).
Process 1. Define “system boundary” for the participants.
Steps
Show visual aid:
2. Ask the participants to identify the entity within the scope of the project that
they want to focus on. [In this example, Payment Processor.]
3. Draw a circle in the center of a flip chart to represent the system boundary, and
add a label (inside the circle).
REMINDER: Put a red checkmark in the box on the agenda visual aid to show
that the step is complete.
Document Draw a circle with label of the entity chosen as the system boundary.
Agenda Step 2: Identify User Roles
Estimated 30 minutes (5 minutes per user role; assume up to 6 user roles are in
Time scope)
Purpose Identify all user roles that have direct interaction with the system boundary
chosen in agenda step 1.
Process 1. Define “user role” for the participants.
Steps
Show visual aid:
2. Ask the participants to identify all user roles that have direct interaction with the
system boundary.
3. In the perimeter around the system boundary, draw a rectangle for each user
role identified, and label (inside the rectangle) each user role.
4. Ask the participants to collaborate on a description of each user role. Write the
descriptions on a separate sheet of flip chart paper.
REMINDER: Put a red checkmark in the box on the agenda visual aid to show
that the step is complete.
Document Capture a rectangle (with label) for each user role identified.
Capture user descriptions in a 2-column User Table.
(left column header: User Role; right column header: Description)
Copyright © 2017 Requirements Quest®. All rights reserved.
Example Workshop Charter – Page 5
Annotated Agenda
Example Workshop Charter: Context Diagram
Agenda Step 3: Identify Information Flow
Estimated Up to 90 minutes (assume up to 6 user roles—15 minutes per role)
Time
Purpose To identify the inputs of information and materials to the system boundary, as well
as the outputs of information and materials from the system boundary.
Process 1. Define “inputs” and “outputs” for the participants.
Steps
Show visual aid:
2. For each User Role, ask the participants, “What information and materials does
X User Role provide as input to the system boundary?”
For each User Role, ask the participants, “What information and materials does X
User Role received as outputs from the system boundary?”
On a separate sheet of flip chart paper, record inputs and outputs.
[See Example Inputs/Outputs Table below.]
Repeat until all User Roles have been reviewed.
[Note: a User Role can have inputs only, or a User Role can have outputs only. If
a User Role has no inputs or outputs, then it likely doesn’t have direct interaction
with the system boundary and should be removed.]
3. For each input and output identified, draw a line with an arrowhead to show the
direction of flow.
4. Label each line with a name of the information or materials.
REMINDER: Put a red checkmark in the box on the agenda visual aid to show
that the step is complete.
Document Capture each input and output with a line and arrow head to show the direction of
flow to (input) the system boundary and from (output) the system boundary.
Example Inputs/Outputs Table
ROLE
ID
A
USER ROLE
INPUT to System Boundary
OUTPUT from System Boundary
RQ Website
AO1 – Payment Authorization
Response
B
Accounting
Department
AI1 – Payment Authorization Request
AI2 – Account Information
AI3 – Purchase Transaction Information
BI1 – Account Profile Data
BI2 – Sales Report Criteria
Page 6 – Example Workshop Charter
BO1 – Sale Notification
BO2 – Sales Report
Copyright © 2017 Requirements Quest®. All rights reserved.
Example Workshop Charter: Context Diagram
Annotated Agenda
WORKSHOP FINISH
 Review the deliverable(s)

Identify next steps

Assign open items

Evaluate the workshop

Close
Copyright © 2017 Requirements Quest®. All rights reserved.
Example Workshop Charter – Page 7