Enterprise Architecture

At STI we specialize in helping our clients address business processes, standards, and security relating the EA to the corporate strategy and objectives. Furthermore, we provide direction and guidance on how to develop the sequencing plan/transition strategy to move from the baseline architecture to the target architecture.

Recent research on Information Technology project planning and development indicate that more than 50 percent of IT projects typically do not achieve their stated goals. Having someone to ensure a company's technology objectives are aligned to its business goals is vital is the role of the Enterprise Architect. This role becomes more important as companies begin to adopt service-oriented architecture (SOA) approaches toward application development.

The EA describes how the elements transition to support the organization’s strategic plans. Federal agencies are required to develop an EA to facilitate capital planning and IT development sequencing. In addition, the EA defines high level interoperability needs and specifies standards. An EA framework should, at a minimum, organize information types and describe the relationships between business processes, data, IT mission systems, and IT infrastructure used to perform the enterprise mission and planned to achieve the future strategy of the enterprise.

We view the EA as both a management and a technology tool which has many facets and uses that are overlapping and intertwined. From an evaluation standpoint, we focus on the following areas: