Page
28
4.5 Solution Dependencies
<<The integrated customer solution could require coordination between
products within a single Division / Business Unit (BU), between
products developed in more than one division / BU, and/or between
products owned by your company and a partner company / VAR (value
added reseller). Dependencies List should describe inter-product, inter-
division, and inter-company dependencies that are required to make
the integrated customer solution a success. >>
<<Dependency List Example:
Integrated Customer Solution XY will provide the following customer
functionalities (describe the functionalities here) by DD/MM/YY. In
order to achieve this, we need to build the final product prototype WX
two weeks prior to DD/MM/YY. VAR1 needs to develop WY 3 weeks
prior to DD/MM/YY. The combined solution testing will begin
immediately after WX and WY are made available to our company test
lab, and will be completed one week prior to DD/MM/YY. …>>
4.6 Implementation Phases
<<If the full functionality of the integrated customer solution is being
rolled out over a period of time and dependencies have been identified,
describe here the features, performance, plans, milestones, and dates
agreed upon by the various parties.>>
<<This section should document the plans for addressing
dependencies between deployment phases of an integrated customer
solution. In addition, the upgrade strategy between phases must be
identified. If an integrated customer solution has many phases
spanning a long period of time, it is expected that progressively fewer
details will be available for later phases. Include other future direction
©2007 Franteractive Inc. All rights reserved.
