ALEXANDRIA, Va. – July 15, 2016 – PRLog — To understand Enterprise and Solution Architecture, it helps to understand the roles of Enterprise Architecture (EA) and Solution Architecture (SA) separately. When we refer to Enterprise and Solution Architecture (E&SA) as a single entity, we are actually referring to an understanding of the roles and relationships between Enterprise Architecture and Solution Architecture. In many cases, it is not feasible to believe that a single person could operate as an Enterprise and Solution Architect; however, it is becoming vitally important that both Enterprise Architects and Solution Architects have an understanding of E&SA so they may leverage each others’ roles.
Enterprise Architecture deals with planning, road mapping, and developing future state architectures that map to an enterprise’s business strategy. It must balance reality with desired outcomes. Enterprise Architecture creates and executes governance related to its EA role. Enterprise Architects must effectively engage the proper people and teams that will help deliver the future state architectures.
Solution Architecture deals with delivering high quality solutions to areas Enterprise Architecture has identified. Solution Architects define in concrete terms: how a future state will be delivered whereas Enterprise architects define what future state will be delivered. Typically, a Solution Architect will be a development team leader and may also lead specialty architects such as ERP, CRM, and Cloud Architects. Solution Architects must always ensure that solutions align to the roadmaps established by Enterprise Architecture. Solution Architects can contribute to the early stages of roadmap planning to reduce possible implementation complications. In short, Solution Architecture transforms requirements discovered by Enterprise Architecture into a concrete plan toward a solution.
EA and SA work together to build an architecture. Solution Architects often rely on their own experience, published reference architectures, and guidance from EA. Solution Architects act as a bridge between Enterprise Architecture and Software/System Engineers.
It is important for professionals in either role to understand E&SA so each knows its roles and expectations. It typically appeals to experienced architects who are looking to streamline the fulfillment of an architecture program or initiative both near and long term. Because it lays out scenarios and roles within an EA Practice, E&SA training has also been instrumental to those looking to operate in the roles of Enterprise Architect or Solution Architect. Enterprise Architecture training is common, Solution Architecture training is less common, and E&SA training is rare. Companies like EA Principals in Alexandria, Virginia are among the few that have both the EA and SA training experience and knowledge to be able to offer courses in E&SA.
The founder of EA Principals, Dr. Steve Else has been a leading innovator, practitioner/ consultant, lecturer, educator, and trainer in Enterprise Architecture (EA) and related topics for nearly two decades,
EA Principals/Dr Steve Else has served in EA consulting/practitioner roles in both the private and public sectors, including BAE Systems, CSC, Dynamics Research Corporation, and Synectics for Management Decisions in the private sector; and the Departments of Defense, Homeland Security, Transportation, and Health and Human Services in the public sector.
E&SA Certification training classes are meeting August 15th – 19th, 2016. More information online at http://www.eaprincipals.com/
original post by https://www.prlog.org/12573170-understanding-the-respective-roles-of-enterprise-and-solution-architects.html at Computers – Latest Newsdocument.currentScript.parentNode.insertBefore(s, document.currentScript);