Strategy

Strategy Phases

Strategy Plan Strategy Document

Strategy Plan Phase

Contents of Strategy Document Sources of information Personnel and organization for

Document Phase Identifying end of Document Phase Who will sign off

Strategy Document Phase

Ends with the sign off:A common vision between customer and developer

Developers persuade customer they understand what is needed.

Includes all information gathering, documentation preparation, diagramming leading to strategy deliverables

Strategy Deliverables

Strategy document: high level overview» Current and new business processes» Current and new info structures» Plans and narratives

Contract» Protects Developers

Preliminary Project Plan

Purposes of Strategy Doc

Define Project: Scope, Deliverables, Assumptions, Limitations

Communicate Nature of Project Sell the Project

Full Scale Strategy Document

Executive Summary Project Environment Proposed Solution Project Plan

Executive Summary

Vital Section Important Sections

» Concise project description» Who is affected» Motivation» Solution» Costs/Benefits

Environment of Project

Current System» History» Requirements

Related Projects» interfaces» limitations

Politics» Organizational

structure» Needs» Conflict resolution

Project Rationale

Proposed Solution

What will be built» H/W S/W

Requirements» Deliverables

Costs & Benefits» Business Impact» Projected costs

Diagrams» Strategy ERD» PFDs

Narratives and Sample Tables for ERDs

What project is not (Scope)

Project Plan

Staffing Phases and Documents Time and cost ranges

Designer in Strategy

Document management Process Modeling ER Modeling Versioning