Blue Sky

A speculation about how a situation could finally end up. The ultimate solution to an issue that ignores constraints of implementation cost, resource availability and current technical abilities.

It is common to contrast the AsIs and ToBe situations with the Blue Sky one. While everyone knows that the Blue Sky version is not achievable it at least defines the direction that improvements should head us in.

In some locations different versions of a system are given code names, for example calling them after person's names. So we may have the "Amy", "Bruce" and "Chloe" versions. In this scheme a "Zack feature" is a description of how the ultimate version would perform some function.

Often the Information Architect should be more concerned with these type of long lasting design constraints rather than issues that are determined by the particular technologies that will be used in the next release.

Links to this page

The following pages link to here: ToBe