1 Architecture and Infrastructure

Enterprise architecture

"Blueprint) for all IS and their interrelationships in an enterprise. A term used for the organizing logic for the entire organization, often specifying how information technologies will support business processes.

Mainframe architecture

A large central computer that handles all the functionality of the system. Users only need a very simple terminal to access the computer. Applications run on the mainframe, and data is stored there.

Wireless (mobile) infrastructure

Allow communication from remote locations using a variety of wireless technologies

Peer-to-Peer

Allows networked computers to share resources without a central server playing a dominant role.

Reuse

An example of SOA is a ticket processing service that identifies available concert seats and allocates them. These relatively small chunks of functionality are available for many applications or reuse.

Service-oriented architecture (SOA)

Architecture in which larger software programs are broken down into services that are then connected to each other, in a process called orchestration, to form the applications for an entire business process. Service components reside on different computers, often on the internet. SOA is increasingly popular because the design enables large units of functionality to be built almost entirely from existing software components.

Web-oriented architecture (WOAs)

Architectures in which significant hardware, software, and possibly even data elements reside on the internet

Capacity-on-demand

Availability of additional processing capability for a fee

Infrastructure

Everything that supports the flow and processing of information in an organization, including hardware, software, data, and network components.

Standards

Hardware and software that uses a common standard, as opposed to a proprietary approach, are easier to plug into an existing or future infrastructure.

Scalable

How well an infrastructure component can adapt to increased or in some cases decreased, demands.

Client/Server architecture

One software program (the client) requests and receives data and sometimes instructions from another software program (the server) running on a separate computer. The hardware, software, networking and data are arranged in a way that distributes the processing and functionality between multiple small computers.

Architecture

Provides a blueprint for translating business strategy into a plan for IS

Software-as-a-Service (SaaS) OR Web Services

Services delivered over the internet

Zachman Framework

[Much heavier use of models to showcase architectural requirements] Determines architectural requirements by providing a broad view that helps guide the analysis of the detailed view. Its perspectives range from the company's scope to its critical models and, finally, to very detailed representations of the dta, programs, networks, security and so on. The models it uses are the conceptual business model, the logical system model, and the physical technical model.

TOGAF (The Open Group Architecture Framework)

[What the books explains about translating between owner to architecture TO architecture to infrastructure] An open architecture that has been developing and continuously evolving since the mid-1990s. It seeks to provide a practical, standardized methodology (called Architecture Development Methodology) to successfully implement an enterprise architecture into a company. Designed to translate strategy into architecture and then into a detailed infrastructure; however it supports a mucuh higher level of architecture that includes more components of the enterprise.