Phase 1: Analysis Workshop
An Analysis Workshop is used to begin gathering requirements, and develops the vision into a service product definition with a discrete list of customer-centric capabilities. To make sure we are all focused on delivering what you truly need, we outline what business processes and events are affected by the software solution.

Deliverables
Business Process Analysis documents that outline all business processes, their related activities and events.

High Level Use Cases that outline and categorize the scenarios, which are in scope.

Detail Scenarios that define variations of the High Level Use Cases. The Detail Scenarios will eventually be translated into test plans and acceptance criteria for the software product.

An initial System Inventory documenting the actual screens, reports, interfaces and engines required as part of the software solution. This will allow the team to scope the final design and construction phases.

In our custom home building metaphor, after this workshop you'd have a defined list of the number of rooms; amenities such as fireplace and walk-in closets; an idea of the target square feet of living area; and your preferences for interior and exterior appearances.

A "next steps" recommendation with cost estimates for the RefinedSite.com Prototype Workshop.

Approach
Week 1
Working as a team, you and RefinedSite.com work together for approximately 2 days in a JAD (Joint Application Development) session, outlining the application we will build and what business processes and activities are affected by the product.

This initial requirements session focuses on identifying what the overall goals of the software are, and defines the criteria that determine when we are finished building the software.

After the group meeting, RefinedSite.com completes the documentation and identifies any issues or assumptions we need you to confirm or clarify.

Week 2-3
This week begins with a one-day review of the BPA deliverables of session 1-the process map and high-level use cases.

The second day, we begin walking through various scenarios the software must support, process by process. These scenarios are also known as Use Cases. These scenarios will also allow us to generate a System Inventory of the screens, reports, interfaces and engines required by the software solution.

Prototype Workshop is the next step in Phase 1.