Architectures
Within the Enterprise, there are primarily two types of architectures. The Data Architecture and The System Architecture. The data architecture documents information exchanges throughout the enterprise. The documentation includes knowledge management plan, data models, use cases, data dictionary and object library. This is primarily at the application Layer.
The System Architecture documents the collection of hardware and software that is designed to work together to work together to provide one or more data or information functions within or between lines of business. This is at the Infrastructure layer (Server, storage, Network).
Data is the raw materials with which information, Knowledge and hopefully wisdom is derived. Without data there is no need for the system sub-architecture. In most organizations, the Applications Architect is responsible for creating and maintaining (with the help of domain experts like DBA) the application architecture. The application architecture is derived from end user requirements. Once the application architecture is created, this information can be used to create the system architecture (with the help of domain experts like server experts). Within both the data architecture and system architecture, security should be paramount. Usability is another key component. Sometimes security and usability are at crossroads; however the application architect should not lose sight of one for the other. Both are important.
From my point of view, Data is always the driver for systems architecture. Losing key data can bring the company to its knees. However, if systems are destroyed, it can be recreated - it may take some time and money, but it can be done. However, if data is lost it may be impossible to be recreated unless a working backup is available. Since both data and systems are constantly in continuously evolving, both architectures must be scalable and “future proof” as much as possible.
