Example Document (page 2) --
Major Scope Aspects

Software Development Request Management System

Major Business Objects

Problem Statement

Note that we do not define the business objects here. They should already be understood by the parties involved, as you use their own terms wherever possible (and accurate). However, if the terms are new to the business, not well understood by the business, or different groups within the business use different names for the same concept, define your terms in an appendix. We have included an appendix defining almost terms because you and I didn’t actually sit down together to figure out what needs to be done, so I can’t assume much prior knowledge on your part.

Request (Software Development)

Project

Document

Request Status History

Application

Code Unit

Action Item

Business Objective

Major Functional Transformations

Document Problem Felt by Organization into Problem Statement.

Turn Business Need into Request.

Prioritize the List of Requests.

Group Requests into Project Actions.

Major Business Events

Determine Business Need ^[1]

Submit Request.

Evaluate Request.

Reject Request.

Approve Request.

Start Software Development Project.

Assign Requests to Project.

Major Business Locations

All Company Offices World-wide-web

Major Business Actors

Request Submitter System Analyst

Project Sponsor Programmer

Business Line Expert Application User

Business Analyst

Page 2 of 4

[1] Note that this item, while listed, is grayed out and is therefore out of scope. Marking out-of-scope items in this manner is a useful technique. That way, no one can come back later and say, "Of course it is in scope! Everyone but you knows that a system to help us auto-magically determine what we want is part of a Request Management System!" Well, actually, they can come back and say it, but you can easily prove that it was not in scope. [return]