Technical Architecture


Making use of a Target Technical Architecture to Support Acquisition Business Decisions

Enterprise architecture (EA) documents current conditions, future visions, and the transition plan between them. It pertains to and encompasses one or all of the following: programs, offices, segments, solutions, departments, lines of business, and agencies. IT acquisition management (ITAM) includes the set of tasks required to accomplish the directed and funded efforts to provide a new, improved, or continuing information system or services capability to satisfy a business need. Thus, an EA contains business operation information for decision support and communication and informs decision-makers about what technology to acquire and when. This article illustrates how a technical architecture can both provide a clear picture of the technical goals that lie ahead for the enterprise, as well as providing decision support to selecting and acquiring a product that will help satisfy the organizational requirements and scheduling needs.

Characteristics, Roles and Responsibilities of the Modern Day Systems Architect: Lessons from the Field

The roles, responsibilities and titles of Architects often vary in relation to the domain or environment in which they operate. Throughout our work with a wide variety of clients, we have discovered that there is a „misconception‟ with regards to both the function and deliverable of the architects. This misconception often means that inappropriate resources are allocated or targeted to tasks; this can result in either delay or in appropriate solutions being delivered. In this article we discuss the roles of Enterprise, Solution and Technical Architects and highlight some key products which are produced, together with the inter dependencies between these individuals and products.