...

Introduction

All the necessary information from Data Center the DC side to Warren can and should be addressed as a set of simple, unambiguous questions. These questions, in turn, can be divided roughly in to into three subsets, based on the goal they are helping meant to achieve. Each subset can be expressed as a more general "umbrella question":

1. What is the current infra setup

and

2. , which components it incorporates and what are the plans for the future?

3. What services

do they offer to which clients

4. are DC offering and what expectations do they have

towards

5. to Warren?

6. What is the level of commitment of DC in cooperation with Warren and what expectations do they have to Warren?

If these topics are cleared from their side, we can provide better answers from our side as well

...

both sides, the ambiguity and misunderstanding of decisive factors that are the backbone of successful cooperation should be minimized

The first question of the above three is vital to gather the information that affects the following topics in Warren development:

1. 1.  Architectural decisions:
      1. which external libraries, components and standards to use to cope the requirements of majority of DC in target group?
      2. How to design the functionality in component systems, so that the we provide the value we claim to be offering, without causing the decrease in quality of services and processes existing there before Warren adoption?
   2.  Marketing content and business value:
      1. Can we actually offer the functionality we are claiming to be offering?
      2. Can we offer the functionality in sufficient level of reliability?
      3. Are we doing it in a sensible way, e.g. the development effort is comparable to the actual value the development result is providing?
      4. Are all the features and functionality we are/will be providing also in correlation with the actual requirements?

Conflicting nature in  service requirements

...