Vision
(Business Analyst)
The Vision defines the stakeholder’s view of the product to be
developed, specified in terms of the stakeholders key features, and main
constraints. It Contains an outline of the envisioned core requirements,
and provides the contractual basis for the more detailed technical
requirements.
Business Case (Project Manager)
The Business Case provides the necessary information from a business
standpoint, to determine whether or not this project is worth investing
in.
For a commercial software product, the business case should include a
set of assumptions about the project and the order of magnitude return
on investment (ROI) if those assumptions are true. For example, the ROI
will be a magnitude of five if completed in one year, two if completed
in two years, and a negative number after that. These assumptions are
checked again at the end of the elaboration phase when the scope and
plan are defined with more accuracy.
Risk List (Project Manager)
A sorted list of known, open risks to the project, sorted in
decreasing order of importance, associated with specific mitigation or
contingency actions.
Software Development Plan (Project Manager)
The Software Development Plan is a comprehensive, composite artifact
which gathers all information required to manage the project. It
encloses a number of artifacts developed during the Inception phase and
is maintained throughout the project.
Initial phases, their durations and objectives identified. Resource
estimates (specifically the time, staff, and development environment
costs in particular) in the Software Development Plan must be consistent
with the Business Case.
The resource estimate may encompass either the entire project through
delivery, or only an estimate of resources needed to go through the
elaboration phase. Estimates of the resources required for the entire
project should be viewed as very rough, a "guesstimate" at
this point. This estimate is updated in each phase and each iteration,
and becomes more accurate with each iteration.
Depending on the needs of the project, one or more of the enclosed
"Plan" artifacts may be conditionally completed
Iteration (Project Manager)
A time-sequenced set of activities and tasks, with assigned
resources, containing task dependencies, for the iteration; a
fine-grained plan
Product
Acceptance Plan (Project
Manager)
The Product Acceptance Plan describes how the customer will evaluate
the deliverable artifacts from a project to determine if they meet a
predefined set of acceptance criteria. It details these acceptance
criteria, and identifies the product acceptance tasks (including
identification of the test cases that need to be developed) that will be
carried out, assigned responsibilities and resources required. In a
smaller scale project, this plan may be embedded within the Software
Development Plan
Development Case (Systems Analyst)
The development-case description describes the development process that
you have chosen to follow in your project.
Use Case Model and Guidelines (Systems Analyst)
The use-case model is a model of the system's intended functions and
its environment, and serves as a contract between the customer and the
developers. The use-case model is used as an essential input to activities
in analysis, design, and test.
Glossary of Terms (Systems Analyst)
The Glossary defines important terms used in the project.
Business Object Model (System Analyst)
The business object model is an object model describing the realization
of business use cases.
Project-Specific
Templates (Systems
Analyst)
Templates for document artifacts and reports used in the project. There
can also be templates for models and modeling elements, such as the design
model.
Tools (Architecture Group)
The tools to support the software-development effort.
Prototype (Development Team)
One or more proof of concept prototypes, to support the Vision and
Business Case, and to address very specific risks
