Arch. Description
Standardized Systems



Information Technology Architecture is evolving very rapidly.  Concepts that seemed nearly impossible a couple of years ago, are routine today.  For example, the concept of sharing data and publishing data among a half dozen data bases of different structures, which was impossible, is now, not only possible, it is routine.   This change is a direct result of the advancements in speed and capacity of hardware and therefore the ever increasing complexity of software that is loaded and manipulated.   We take this evolution into account and make assumptions about architecture as follows:

Use the standards, tools and techniques of the Internet   Architecture.  This is the least cost and simplest option to implement.  However, in reality, this is the only option. (This includes all the options of server based and peer based designs.)
Provide for individual preferences, (e.g., Mac vs. PC).  In the Internet Architecture, everything runs from a browser which does not care about the hardware or software over which it is running.
Find dramatically reduced costs for every component of the Internet Architecture.  All costs, hardware, software and communications, should be 25% or less of the costs of a decade ago.

Most users of standardized systems will not need an IT organization, an array of servers, or a communications network.   In the Internet Architecture, everything is greatly simplified for those who buy and those who provide systems services.