Roles and responsibilities of the Domain teams:

Domain Owners
The domain owner has management responsibility for the principles, standards, technologies, services and patterns within the particular domain. The technology domains are owned by members of the ARB. The owners may designate a project manager to help with the day to day activities of the domain architecture project
PM Responsibilities
Help identify the subject matter experts that will participate on the domain teams.
Manage tasks assigned to team members.
Help with domain documentation and presentation to the ARB.
Domain Team Members
Technology domain teams are composed of subject matter experts that work within the EA function for brief and/or periodic assignments. The experts are formed into domain teams and work to define domain architectures.
Domain Team Responsibilities
Develop technology architectures using the domain architecture deliverables.
Collaborate with the EACT in the development of domain architecture principles that align with the IT guiding principles.
Select product and technology standards.
Define technical services and implementation patterns.
Document currently implemented technologies.
EA Architect
An architect from the EA core team is assigned to work with each domain team. The architect will provide guidance as necessary in the development of the architecture deliverables.
EA Architect Responsibilities
Assist the domain owner with meeting logistics and agendas.
Assist with recording meeting minutes and assigned tasks.
Provide education about EA concepts and provide guidance to the domain teams.
Note: EA Architects that have domain specific subject matter expertise may also play the role of Domain Team Member.

 top

Enterprise Technology Architecture (ETA) Model Overview                                            from Gartner
The figure shows the relationships. Click on the links below to learn more.

The domain team artifacts are being created and stored in Excel spreadsheets.  The template for the spreadsheet is the  Enterprise Technology Template Document  on the EA SharePoint. Enterprise Technical Architecture includes the following:

• Technology component is defined as the largest physical item, including hardware and software, used as part of a design and is purchasable as a product. The lowest level definition of the ETA is a Technology Component Catalog, the second sheet in ETA spreadsheets.
   
• Non-component technology element is a non-physical item used in the design and development of IT solutions. Examples of non-component technology elements include configurations, data model layouts, naming conventions, and application code standards. These non-component standards are not part of the current Domain team effort.
   
• Domain is an organizing concept that groups individual component technologies and actual product by technology and organizational affinity - common domains include network, database, integration, security etc. 
   
• A Pattern model is designed to serve as the standard model for a set or class of applications that use the same — or highly similar — technology designs.  Patterns will evolve from the domain team work.  We don't currently have any patterns defined.
   
• Services are "infrastructure applications" that shift responsibility for certain services out of the application domain into the infrastructure domain; Services are a set of components implemented and reused as a single unit – Common services include security, data movement, Network connections etc. 

 top