The Role of a Technology Architect

8/11/2019 The Role of a Technology Architect

http://slidepdf.com/reader/full/the-role-of-a-technology-architect 1/37

What is Technology Architecture?

1

Copyright ©2008 Accenture All Rights Reserved. For Internal Use Only.

MTA 2020

The Role of a Technology Architect

Internal Use Only

Hello. Welcome to this computer based training course, titled “The Role of a Technology Architect.”

This is part of a series of computer based and classroom training courses for Technology Architect

practitioners across Accenture, aimed at providing a common terminology, an understanding of key

concepts and considerations, and a consistent approach to the Architecture work we perform for our

clients. In the next slide, Paul Daugherty, Accenture’s Chief Technology Architect, will highlight our

company’s focus on this training.




2

2Copyright ©2008 Accenture All Rights Reserved. For Internal Use Only.

Paul’s Perspective

SI&T Leadership is committed to strengthening Architectdevelopment across the company, and the MasterTechnology Architect (MTA) Program is a key initiativeunderway to build architects with appropriate breadth anddepth of specialization.

The MTA CBTs are a key channel to deliver relevantarchitecture training, helping participants understand:

– Areas of specialization that are important for buildingbreadth and depth of skills

– Other principles and concepts to advance your career

as a Technology Architect

The Master Technology Architect Program is one of the most important initiatives that we’ve got

underway in Technology Architecture right now. The goal of the MTA Program is to build appropriate

depth as well as breadth of technology specialization and architecture skills in our people. The CBTs

are a very important ingredient in our MTA progression, because the CBTs really allow all of you to

get both an overview of some of the areas of specialization that are important for you to understand,

as well as to identify different areas where you can build your skills and get additional depth, either in

our specialization areas or other principles and concepts that are important to advancing your career

as a Technology Architect and pursuing advancement through the Master Technology ArchitectProgram.




3


Introduction

Intended audience

Anyone currently on or wanting to join an Architecture team

New joiners or anyone looking to understand the terminology and structure ofTechnology Architecture teams and roles at Accenture

Training environment

Presentation format

Periodic tests to reinforce key concepts

Course Navigation

Find playback control bar

Audio transcripts are located in slide notes

Change size of screen

Downloadable PDF version available from the “Attachments” list

The intended audience for this course are people currently – or looking to be – staffed on Architecture

teams. Additionally, those new to Accenture may want a better understanding of the terminology,

structure, and roles of Technology Architecture teams.

This training uses a presentation style approach, with quizzes to occasionally check your knowledge.

Once you complete the final test at the end of the course, you will be marked complete in myLearning

automatically.

Please take some time now to familiarize yourself with the screen components, like the playback

control bar, the ability to view speaker notes during the playback of the presentation, and changing the

size of the screen. Use the search tab on the left if you’d like to search any of the presentation’s

content. Sites and materials presented here are linked to within course slides and are also available

in the ‘ATTACHMENTS’ list from the top of the screen. In addition, a downloadable PDF version of

this content is available to you from the ‘ATTACHMENTS’ list. At any point during the playback of the

course, you can click on ‘SCREEN COMPONENTS OVERVIEW’ from the top of the screen to pause

the presentation and learn about the player’s screen components. A glossary of terminology used in

the course is available at the top of the player window as well. Once you have familiarized yourself

with these and are ready to continue, please click the play button at the bottom of the screen.




4


Learning Objectives

Upon completing this course, you will be able to:

Describe the need for Architects

Recognize the principal types of Architects in Accenture

Identify the role of Technology Architects in Accenture

Be familiar with the Accenture Technology Architect Career Model

After finishing this course, you should be able to describe why Architects are necessary, their overall

role and responsibilities, and general characteristics that make a good Architect. You will also learn

about the principal types of Architects on Accenture projects. In particular, you will understand the

responsibilities, duties, and skills of a Technology Architect, and how the rest of the Technology

Architecture Team fits into the “bigger picture” during the lifecycle of a typical Accenture engagement.

Finally, you will become acquainted with Accenture’s Technology Architect Career Model and the

roles of members in a Technology Architecture Team.




5


Agenda

Architects – What are They and Why are They Needed?

Architects and Managed Delivery

Technology Architect in a Delivery Project

Types of Technology Architects in Accenture Engagements

Building a Career as an Architect

Here is the course agenda. The term “Architect” is being used more often, and it seems as if

everyone and every group that does something with technology, or even functionality, is an

“Architect.” We are attempting to address this proliferation by being clear on the core types of

Architect within Accenture and how they relate. Across the firm and the methodology, the term

“Technical Architect” is used. We have adopted the term “Technology Architect” to convey the

breadth of areas that an Architect needs to cover, from infrastructure through to application, but these

terms may be used interchangeably. To start, let’s step back for a moment and think about the

underlying need this role addresses.




6


The Need for an ArchitectBuilding Architect

Owns the infrastructurecomplexity: electricalsystems, plumbing, beams,and rafters

Takes into account barriers:land size, regulations,nearby buildings

Shapes the design in a

blueprint

Technology Architect

Owns the infrastructurecomplexity: network,hardware, operatingsystems…

Takes into account barriers:existing software, internalpolitics…

Shapes the design in a

blueprint

To introduce the role of a Technology Architect in system building, it is often helpful to draw

comparisons to a Building Architect in the construction of a house.

The design and structure of a house must address many complexities and competing needs.

Construction cannot begin until a plan or blueprint is in place that describes how the house will be laid

out, including its infrastructure and services, such as plumbing and electricity. While the builders may

be able to make some of these decisions for themselves, they are unlikely to execute their workunguided or in a way that balances the desires of the homeowner with the building regulations and the

practicalities of electrical and plumbing systems. An Architect is required to own all of these

complexities and to create a design that can then be handed to the builders so that construction may

begin.

Similarly, the Technology Architect must own the complexities in information system building. The

Technology Architect must understand what is required of the system, the implications of those

requirements on the infrastructure and system software, and the constraints imposed on the system

by the environment and also by the client, such as budget and technology preferences. In addition,

the Technology Architect should define and build an Architecture that allows the developers to build

functionality without being concerned with the infrastructure details.

When designing a house, the building Architect must take existing constraints into account, such asgovernment regulations regarding numbers of floors and the existence of other nearby buildings;

these factors will influence the resulting design. Something similar happens when designing software

systems – the Technology Architect has to consider certain existing forces and constraints when

making decisions: for example, company policies, and existing software/environments. Knowing and

understanding these issues, and ensuring that the system can address requirements effectively within

the context of those environments is a key trait of successful Technology Architects.

Considering the client’s wishes, environmental barriers, and other technical and physical limitations,

the Building Architect designs the house and its infrastructure, shapes this design in blueprints, and

shows them to the client for approval. The client will not have to understand technical concerns like

pipes, electrical wiring, or rafters to approve the design. However, the Architect will have to

communicate these concerns in a language that the client understands and at an appropriate level of

detail, to allow the client to visualize the resulting house. In the same manner, the Technology

Architect will shape the design of the software system in a blueprint and will communicate it to the




8


Architect TraitsInventor

Curious – wants to understand why, how, andfor what purpose

Persistent – pursues best solutions fordifficult problems and is not easily deterred

Observant and Analytic – managescomplexity through abstractions (frameworksand reference models)

Diverse – has a broad knowledge across arange of areas

Pragmatic – does not seek to re-invent

Uses Prototypes – tests the strengths andlimitations of a solution

Cost-Efficient – factors cost as a constraint

when developing a business case

Leonardo da Vinci was a painter, draftsman, engineer, architect, visionary scientist, and sculptor; likely

the most obstinately curious man in history, and the most persistent in his search of answers. These

characteristics—curiosity and perseverance—are very important to the success of Technology

Architects, because they will need to answer questions such as why, how, and for what purpose, and

will need to pursue solutions for difficult problems without easily giving up.

Leonardo observed nature analytically and produced mental models very close to the reality that hesaw. Later, he applied those models to the design of his inventions. For example, he did a thorough

study of birds’ shapes and the mechanics of their flight, a study that he outlined in his manuscripts.

Soon after, he designed a hang-glider based on his studies and calculations, which proved to work

perfectly when built and tested in our contemporary era. Similarly, a Technology Architect studies the

complexity and the interaction between different forces in systems and builds reference models and

frameworks that provide simple plans for the technology solution. Like da Vinci, the Technology

Architect must be able to sketch out and communicate these models effectively.

Cesar Borgia hired Leonardo as a military engineer with the ultimate objective of conquering all the

territories from Florence to Rome. With this aim, Leonardo designed new military machines to

conquer the fortified palaces, ports, and coasts in the region. He leveraged his deep knowledge about

several branches of technology and applied them in innovative and improved ways to design and

develop very practical solutions, models, engines, and techniques. Likewise, the Technology

Architect must be diverse and have a broad knowledge across a range of areas and does not seek tore-invent, but instead, to reuse proven solutions with less risk.

Leonardo had to identify and understand the main challenges his solutions needed to address, while

considering factors such as the costs, availability of raw materials, and the capabilities of workers to

construct his designs. Through the understanding of these obstacles and factors, Leonardo deduced

the best solutions to address both business requirements and known limitations. In the same way, the

Technology Architect must identify and account for barriers, limits, or constraints on the solution.

These constraints can come from many sources, such as legacy systems, infrastructure, or policies.

If there were multiple reasonable solutions to a problem, Leonardo used prototypes, scale models,

and so forth to analyze and test options, and select the approach that best covered the requirements.

In the same manner, the Technology Architect will not rely solely on tools, statistics, and reports; he or

she will build prototypes to understand strengths and limitations of the possible technologies more




9


Architect Traits Advocate

Represents the interests of the client

Listens to all stakeholders involved

Communicates the need for an Architecture

Communicates the Architecture acrossthe organization

Provides intellectual leadership

Provides guidance for design anddevelopment

Facilitates change

Identifying viable solutions to problems is only part of what makes a good Architect. Similar in ways to

lawyers, Technology Architects must be strong advocates and communicators.

The Technology Architect represents the interest of the client. He or she must understand the

business domain and the strategy of the company, and properly select and apply technology trends

and solutions to help that client achieve its strategic business objectives. The use of a technology for

the technology’s sake alone does not make sense; it must be aligned with the business strategy of thecompany.

Communication is a “two way street;” it’s not just about speaking well and being understood. In order

to represent the interests of the client, the Technology Architect must carefully listen; if not, the client’s

requirements and needs will be lost. The Technology Architect must listen to all the people involved in

the business areas which will be affected, to ensure that the complete vision of the problem has been

analyzed. Complementing what is heard, the Technology Architect must also observe the client’s day-

to-day business and then design from that perspective. It is very important for the success of the

technology solution to understand how the people involved actually perform their work on a daily

basis.

Additionally, in the same way that a lawyer must communicate his/her arguments to the jury and

defend the client, the Technology Architect may have to defend the need for a certain Architecture tothe organization. Once the concept of the Architecture is accepted, the Technology Architect will have

to convince the organization that the Architecture he or she has in mind is the best technology option.

Lastly, the Technology Architect will have to clearly communicate the designed Architecture to the

organization and the developer teams, at levels appropriate to the audience. Once the system is

being built, the Technology Architect must support the client, and help address issues and risks that

may steer the system away from the client’s intended objectives.

Furthermore, the advocate organizes and structures the defense by selecting the best arguments and

facts, creates a plan to defend the client’s interests, and tries to change the mind of the jury if

necessary. The Technology Architect provides the intellectual leadership for the technology solution,

guides its design and development, and facilitates the changes required to move the client towards

the new technology solution.




10


Architect TraitsDesigner

Function

S t r u c t u r e E l e

g a n c

e

Architecture design requires balancing threeelements:

Function – the Architecture must meetthe client’s and solution’s needs

Structure – the Architecture must enablea solution to be built from the availableresources and skills

Elegance – the Architecture must displayan overall rationale that others canunderstand and appreciate, which enablesit to evolve and facilitate changes in a

structured way.

Vitruvius was the founding father of modern Architecture and lived during the Roman Empire. He

established that all Architecture was composed of three concepts: Function, Structure, and Elegance.

•Function – the reason why, the functionality, the drive for the building.

•Structure – the materials and available resources that provide the strength and robustness of the

building.

•Elegance – the foundation which is easy to understand allowing future modifications to be possible in

a logical and orderly fashion.

A building Architect must balance these three concepts to obtain a complete Architecture. In the same

manner, a Technology Architect must marry the client’s functional needs, the technology, and the

structural model to determine the resulting technology solution.

A Technology Architect designs software-based technology structures and is the owner of the design

during construction. He or she considers the technology components, function, and overall structure of

the technology solution and determines how the technology solution will work with existing software

elements. In addition, the structure of the Technology Solution should ease development, isolating

the complexities of the infrastructures from the development teams, and it must account for critical

software concerns such as reliability, performance, or maintainability. Support for these characteristics

cannot be added on to a system during construction; they must be accounted for in the design.

Once a building Architect has completed the design of the building plans, he or she passes them on tothe builders, who can review their portion of the blueprint and understand how their piece relates tothe others. This is analogous to the case of the Technology Architect; the technology infrastructuresolution must be communicated to the development teams in order for it to be constructed properly.The design must be well documented and consistent, serving as a guide to the development teams.

Anything poorly documented and communicated to the development teams at this time will likely resultin software issues that are very difficult and costly to fix, if they can be addressed at all. In addition, aschanges or extensions are required over time, a clear understanding of the system’s structure enablesnew development or maintenance to follow the same approach and evolve the system in a predictablemanner.




11


Responsibilities of an Architect

Owns the complexity

Brings order and simplification

Shields the broader team from unknowns

Creates a vision

Sets the direction Solves issues

Always insists on excellence

Many companies today design, build, and run their information systems in a

distributed manner, which greatly increases complexity and requires strong

communication.

Accenture engagements typically address th is complexity by div iding

Architects into business, organizational, functional, and technology areas.

Architect roles have similar responsibil it ies wi th in their respective areas:

With the rise of globalization, companies and their business locations are no longer defined by a country’sborders. A company’s operations are located where the work is, and companies have to extend their physicalpresence closer to their business and clients. The business model is more complex too, which affects theinformation systems that have to support these new organizations and new business models. The informationsystems are in remote locations, data is dispersed among different locations, and there is a total dependency oncommunications.

Accenture divides those rising complexities (business model, business process, people, and technology) andapplies Architectures to each area of complexity to guarantee the success of delivering information systems.

Each area of complexity will be managed with its own Architecture. So, on Accenture engagements, Architectsexist in the business, organizational, functional, and technology areas. While each one of these Architects will befocused in his/her own area, all of them share certain common responsibilities necessary to achieve success asan Architect:

-Owns the complexity. The Architects are responsible for managing the complexity and accommodating it insidetheir respective Architectures. These Architectures must be prepared to address new complexities in the future, ifthey appear. The Architect must know his/her specialization area deeply, and does so by accumulating years ofexperience in the construction of successful Architectures.

-Brings order and simplification. An Architect has a complete vision and full understanding of the pieces thatcomprise a solution and how they fit together. The complexity of the system can be spread across the variouspieces and addressed in an ordered and simplified manner.

-Shields the broader team from unknowns . The Architect is the person who knows more about his/her specialtyarea than others in the engagement. Thus the Architect may assign himself or herself the most ambiguous and/orcomplex issues to shield the rest of the team from unknown complexities.

-Creates a vision. The Architect has a complete vision of the Architecture to deliver to a client. With several yearsof experience, the Architect has seen several clients, business models, and technologies, and thus knows thebasic pieces that must compose the Architecture and how they fit together. This complete vision of the

Architecture will be shaped in a blueprint and will serve as a guide in the ongoing delivery of the project as well asthe reference point for the Architecture implementation team.

-Sets a direction. The vision of the Architecture that is shaped in the blueprint marks the working direction for the Architecture implementation teams. There is an objective and a method to achieve it, both of which areestablished by the Architect. The team follows the working method to achieve the objective. The team designs andbuilds the solution, while focusing on repeatable, predictable design and delivery.

-Solves issues. The Architect is the leader of his/her specialty in the engagement, and will have to makedecisions when issues regarding his/her area arise in the project. The Architect will establish the different options,the arguments, and the prototypes of proofs-of-concept to be carried out. Based on these results and along withhis/her knowledge and experience, the Architect will be able to make an adequate decision.

- Alw ays insists on excel lence. The Architect has a responsibility to review and validate the work realized by the Ar chitecture im lementation team. On one hand, the Architect is teachin future Architects; on the other hand, the




12


Formal Architect Roles

ARCHITECTS:

Enterprise Architect

Business Architect

Human Performance Architect

Integration Solution Architect

Technology Architect

Accenture Delivery Architectures

As we have seen, Accenture engagements break down complexity into several specialized areas, and assign adifferent Architecture to each area. Therefore, there are many types of Architectures, and all of them areinterrelated. Each Architecture type can be described individually, but it is important to understand that each typeinfluences—and is influenced by—the other Architecture types.

Accenture engagements usually deal with the following Architecture types (with some variance depending on theoverall scope of the effort):

-Enterprise Architecture,

-Business Architecture,-Human Performance Architecture,

-Integration Solution Architecture,

-Technology Architecture.

Again, these are just a sample of the more frequent Architecture types found on Accenture engagements.

An Architect of a certain type will be the owner of that type of Architecture. The objective of this course is to clarifythe Technology Architect role; however, this role needs to be understood in the context of the other Architect roleswhich typically define the organization and structure within which Technology Architects work.

An Enterprise Architect is responsible for the definition, implementation, and evolution of the Enterprise Architecture for an entire company, and the support of Enterprise Architecture for each customer organization toensure the company has the necessary information to support business needs and objectives. The Enterprise

Architect provides leadership and guidance to the entire company on the grouping and interaction of informationsystem components (e.g., business functions, data, application, technology, and infrastructure).

The Business Architect defines and maintains the overall Business Architecture, containing the business needs ofthe company and ensures that the business requirements are supported through the technology, process, andresource structure to be delivered.

The Human Performance Architect analyzes the impacts of the business requirements on the resource structure(organization) that will support the enterprise business, which is aligned with the Business Architecture. He or sheis responsible for the definition and delivery of the Human Performance Architecture that satisfies those businessrequirements, which may include job design and training.

The Integration Solution Architect is responsible for analyzing the business requirements driving the need forintegration among systems and applications inside the global solution, and explores solution options for thisintegration.

Each of the Architects discussed thus far addresses a broader landscape within which the Accenture Delivery Architectures cube resides. The Technology Architect must define and realize the relevant architecture layers,domains, and application styles depicted in the ADA cube, while conforming to the designs and structure of the

other Architectures. This Architecture allows for the construction and delivery of the integrated applications andsystems that support the enterprise business.




13


Agenda

Architects – What are They and Why are They Needed ?





Now that we understand the need for Architects and the general characteristics of successful ones,

we can see the important part they play in successful delivery for our clients. “Managed Delivery” is a

Systems Integration and Technology initiative designed to professionalize the delivery of solutions to

our clients. The primary objective is to ensure that we shape work appropriately and deliver what we

promise to our clients. This requires standardizing elements of our approach so that we can deliver

value at speed, with high quality and predictability, at a competitive cost.




14



Managed Delivery is the way in which SI&T structures and executes

systems integration work to achieve the quality and predictability our

clients expect.

Managed Delivery provides benefits for everyone:

For our Clients – access to the best Accenture has to offer

For Accenture – strengthens and standardizes delivery

For our People – develops and recognizes expertise

Today, Systems Integration work drives more than 70 percent of Accenture’s consulting revenues—a

huge part of the work that we do every day. With the implementation of the operating model in

FY2007, we saw a renewed focus on accelerating growth through specialization and industrialization.

Managed Delivery is a critical tool in achieving this growth. It defines the way in which SI&T structures

and executes systems integration work to achieve the quality and predictability our clients expect.

Managed Delivery brings benefits for our clients, for Accenture, and for each of us:

For our clients -

Our client satisfaction surveys show that delivery ranks #1 on their list of buyer values. Managed

Delivery will benefit our global clients by giving them access to the best that Accenture has to offer

every time they work with us: a global, highly skilled team of professionals, with deep specialization

and extensive experience in the delivery of large scale systems integration solutions.

For Accenture -

Our biggest challenge in the systems integration world is to extend the compelling differentiation that

Accenture already has in the minds of our clients. How can we achieve this? By bringing the best of

Accenture to our clients every time we work with them. Managed Delivery will enable us to reinforce

our strengths on the delivery side by standardizing how we deliver, optimizing our costs, increasing

productivity, and fueling growth in innovative solutions.

For our people -

Managing and standardizing our delivery approach requires deep specialization. Managed Delivery

provides the framework for each of our people to develop deep, specialized skills as Project

Managers, Solution Architects, Delivery Leads, Technology Architects, and more. Managed Delivery

also professionalizes these skills and ensures that our people receive the recognition they deserve as

world-class experts in their field. As we professionalize our approach to delivery, our SI&T

professionals will take advantage of more standardized tools, processes, and re-usable assets. This

will drive productivity and enable our professionals to focus on creating leading-edge, innovative

solutions.

Let’s focus on the Architect roles in Managed Delivery.




16


Delivery Phase

Business / Appl.Delivery

TestingLead

Define test plans, testmodel; Manage testexecution and Break Fix

Analysis / Design / Buildfor applicationfunctionality

QA Director

Delivery QA

Technology Arch itect

Realize the technologyBlueprint; provide

technical guidance tothe SI team

PMO

HR, CFM, Legal &Commercial, etc.

Conversion

Lead

Define conversion planscovering data andprograms; Manageexecution of conversion

Delivery Team DeliveryLead

DCN

Provide support services across life cycle

•Creating the Technology Architecture•Supporting development by SI teams•Developing and deploying productivity enhancing tools and/or techniques to SI teams•Identifying and managing Technology Risks

Once the project is sold and the Delivery begins, the contributions from some roles is completed, such

as Solution Architect, while other roles take on a greater importance.

During Delivery, the Delivery Lead is focused on the design, delivery, testing, and implementation of

solutions based on a Technology Architecture. Note that the Delivery Lead is not the same as a

Technology Architect; while Architects may be able to do delivery and vice versa, the roles are

distinct, but closely related. Architects are responsible for defining the structure of a system; DeliveryLeads are responsible for managing the overall implementation of the system according to that vision.

There is a QA director who monitors overall quality of delivery, client satisfaction, and financial

performance, and a Program Management Office that coordinates all of the delivery projects and

undertakes the subject of resources.

During the Delivery, there are several groups analyzing and implementing the application functionality,

defining the tests plans and models, and defining plans covering data and conversion programs.

At this phase, the responsibilities of the Technology Architect will include creating the Technology

Architecture and providing technical guidance to the System Integration and Delivery Teams. In

creating the Technology Architecture, the Technology Architect will set up the infrastructure for

development, execution, and operations environments, and can also integrate with AIMS or

Technology Consulting as needed.

As the development for the solution commences, the Technology Architect supports the SI teams

(e.g., Application, Testing, Conversion, etc.) and provides tools and processes for version control,

testing, and data management to not only manage the environments, but also increase productivity.

The teams can either be on site, or off site utilizing managed services such as Development Control

Services or Program Control Services. Throughout Delivery of the solution, the Technology Architect

must continuously assess the technology risks and manage them as they arise.




17


Agenda






At the highest level, we’ve discussed what types of Architects are involved in the Opportunity and

Delivery Phases of a project. Most Analysts, Consultants, and Managers will be involved in the

Delivery Phase of an engagement; here, we’ll go into more detail on what Technology Architects are

involved in through delivery.




19


Planning Stage

Technology Arch itect in the Planning Stage

Documents and solidifies the Architecture Guiding Principles

Recognizes and prioritizes the non-functional requirements, balancingconcerns

Drives the conceptual definition of theTechnology Architectures

Analyzes technology trends and otherbest practices

Sells the Technology Architecture tothe Business Architect and the Client

During the planning stage, the Technology Architect is responsible for the conceptual definition of the Technology Architectures (e.g., Application Architecture, Technical Architecture, and Infrastructure Architecture, or others, ifnecessary due to the complexity or size of the engagement). Also, he or she will have to recognize and prioritizethe non-functional requirements of the system, and guarantee that those non-functional requirements will beshaped in the defined conceptual Technology Architectures and in the rest of the engagement stages.

The Technology Architect works in this stage under the direction of the Business Architect. Direct responsibilitiesinclude participating in analyzing information technology trends and other best practices, along with advising theBusiness Architect on Technology Architecture issues. In addition, the Technology Architect may have to sell the

need to build the defined conceptual Technology Architecture to the client and the Business Architect.

During the Plan stage, developers are not yet engaged in the project activities.




20


Analyze and Design Stages

Technology Architect in the Analyze and Design Stages

ANALYZE

Gathers client’srequirements for theTechnology Architecture

Selects and recommendstechnologies, leveragingprinciples to addressconcerns

DESIGN

Designs the Technology Architecture for theexecution, development andoperational environments

Establishes the direction ofthe Technology Architectureteam to the design oftechnology components, orrealization of proofs-of-concept or prototypes.

Designs the most difficult or

complex components

During the Analysis and Design stages, the Technology Architect is responsible for the design of the

Technology Architecture for the execution, development, and operational environments, and ensuring

that cross-cutting concerns and non-functional requirements are being identified and addressed by

these Architectures. Other members of the Architecture team assist the Architect during these stages,

but the responsibility is still assumed by the Technology Architect.

In the Analyze stage, one of the key tasks for the Technology Architect is to collect and understandthe client’s requirements for the Technology Architecture in order to recognize the client’s needs and

propose the correct solution. The Technology Designers assist the Technology Architect in evaluating

product offerings and performance capabilities and by recommending hardware, system software,

middleware, networking, and other technology components. This may involve prototypes or

simulations to compare/contrast options.

As the project moves through its lifecycle to the Design stage, the Technology Designers will design

the components of the Technology Architectures and will need the support of the Technology

Developers, if it is necessary, to validate approaches and extend proofs of concept. In addition, the

Technology Deployment Specialists work in the Design stage to identify configuration and

implementation requirements and to define the approach to configure and implement the technology

components.

In this stage, the Technology Architect may take on the design of the most difficult or complex

components. While design and development may be performed by an Architect, it is important to note

that this coding is typically to test the design’s correct handling of relevant concerns, and to create a

reference that will serve as a guide for developers to follow as an example later.

The key differentiator between an Architect and a coder occurs in the analyze and design stages:

while coders design and implement solutions to specific requirements, their work is done within the

structure and boundaries defined by an Architect. The focus of an Architect is typically much more

broad than a coder; the impacts and resulting outcomes of design options on performance,

maintainability, security, and other concerns remain central to an Architect’s solution. The coder will

look to address requirements and solve problems as simply and effectively as possible, typically with

less regard to the broader impacts that may have on the resulting system.




22




23


Agenda






Now that we’ve discussed Technology Architects and their teams in general over the lifecycle of a

delivery, let’s examine some of the more typical Architect roles found on our engagements.




24


Types of Technology Architectson Engagements

Technology Architecture

Collection of Architects

To address the needs of

A par tic ular engagement

Integration

Application

DevelopmentEnvironment

OperationsEnvironment

As we’ve discussed, the main responsibility of the Technology Architect role on an engagement is to

define and realize the Technology Architecture, i.e. the components and overall structure of the

Architectures, domains, and application styles depicted in the ADA Cube. The complete Architecture

allows for building, operating, and delivering the applications and systems in an integrated fashion to

support the client’s business.

Due to the complexity or size of an engagement, the Technology Architecture could be divided intomore focused areas, with more granular Technology Architectures. In turn, these more granular

Architectures would be owned by different, more-specialized types of Technology Architects. Some of

the more typical Technology Architect roles found on Accenture engagements are shown here.

Remember that, depending on the size and complexity of the engagement, one person can play

multiple roles, or several people could share a particular role on a given engagement.




25


Application Architect

KNOWLEDGE & SKILL AREAS

The following are key areas to provide guidanceand better enable the analysis, design, andimplementation of proven Application

Architectures in a consistent, repeatable way:

Blueprints for each application style.

Patterns that can be reused to solve recurringproblems that occur during softwaredevelopment.

Practices, methods and processes that are usedin a typical application life cycle development -

Analyze, Design, Build, and Test.

RESPONSIBILITIES

Applies expertise in the structure,interfaces, components, and designpatterns to develop applications.

Ensures uniformity and predictability in thedevelopment of applications.

The Application Architect is a very common role existing across Accenture engagements.

The responsibility of the Application Architect is to apply expertise in the structure, interfaces, components, and design patterns that are used to

develop particular styles of applications. These elements are used by application designers and developers to ensure uniformity and predictability in the development of applications.

The Application Architect focuses on building a fr amework or “skeleton” of the various components that comprise a system and ensures that it adheres to the standards placed by the

business enterprise. This includes coding frameworks, patterns, and practices, such as model view controller (MVC). As the complexity of a system increases, some aspects of Data

Architecture may also be incorporated with the responsibilities of the Application Architect, where he or she will apply expertise in the logical design and physical implementation of the

data base schema for transactional application styles, along with other procedures for processing, storing, and utilizing data.

The Application Architect must have skills around designing and implementing blueprints for each application style, and observing patterns that can be reused to solve recurring problems

that occur during software development. Additionally, this Architect should adhere to practices, methods, and processes that are used in a typical application life cycle development.




26


Integration Architect


Event-driven/message-driven Architectures (ESB,EAI, BAM…)

Message-oriented MW

Data-driven MW

Synchronous/Asynchronous integration

Direct Data Access

ETL-based integration

SOA Reference Architecture in ADA (esp.integration sections, Web services…)

Integration and XML Messaging

RESPONSIBILITIES

Applies expertise in the technologies thatenable integration of disparate applicationswithin and across organizations.

Develops integration solutions in clientorganizations and through their extendedenterprises.

Uses established integration technologies tohelp clients achieve integration goals fasterand more cost efficiently

The Integration Architect is another type of Technology Architect very typical in the Accenture

engagements.

This Architect applies expertise in the technologies that enable integration of disparate applications within and across organizations, and develops integration solutions in

client organizations as well as through their extended enterprises. Integration Architects also use multiple generations of integration technologies to help clients achieve short and long-

term integration goals faster and more cost efficiently than with traditional integration methods.

The Integration Architect focuses on getting systems to communicate with each other effectively, efficiently, and predictably. Most of the requirements are driven by the business

enterprise, and as such there is also an aspect of governance. As some systems increase in complexity, there may also be considerations for data consolidation or conversion that need

to be taken into account, and so the Integration Architect may take on some additional responsibilities of a Data Architect.

The necessary knowledge and skills of this type of Technology Architect center around services, techniques,

frameworks, standards, technologies, and platforms for designing, building and testing software components around messaging and middleware.




28


Operations Environment Architect


Comprehensive & robust internal applicationinstrumentation (alerts and performance)

Health, Performance & SLA

Automated discovery/auditing

Configuration

Deployment

Provisioning

RESPONSIBILITIES

Applies expertise in the management ofapplications and associated hardware andsoftware components.

Designs the ongoing support andmanagement of an enterprise IT servicesinfrastructure.

Ensures that diverse systems perform asexpected by unifying control andautomating tasks

Another common Technology Architect existing in Accenture engagements is the Operations

Environment Architect.

This Technology Architect is responsible for the definition and building of the tools, procedures, and

roles required to manage applications and their associated hardware and software components. This

also includes the design of the ongoing support and management of an enterprise IT services

infrastructure, and to ensure that diverse systems perform as expected by unifying the control ofoperational procedures and automating certain operational tasks.

The Operations Environment Architect works to define system requirements and metrics to monitor, manage, and report on a system’s operation. He or she also implements processes

for the development as well as the transition from the development team to the application and operational management teams. An example of this is a library of processes known as

ITIL.

The services, techniques, and standards that the Operations Environment Architect must know, include system health, performance alerts, and other comprehensive automation within

the system as shown on the slide.




29




30


Agenda






In this last section, we’ll briefly discuss how Architects are developed, and the career path of

Architects at Accenture.




31


Technology Architectureas a Profession

Diversity and breadth of experience is crucial

Architects need to practice Architecture on an ongoing basis

“Full stack” experiences

Accenture is an excellent place for building a career as a Technology Architect based on the nature of our business:

Programs are currently in place that foster growth and recognition or Architects within Accenture, as a part of our commitment to deliveryexcellence

So far, we’ve discussed key characteristics of Architects and their roles and responsibilities on typical Accenture

engagements. Now, we will discuss how one goes about building a career as an Architect at Accenture.

The project-based nature of consulting work is ideal for developing as an Architect. It provides the following:

•Diversity & breadth – Although future Technology Architects will start specializing in a specific technology

branch, with time and project experience, a skilled Technology Architect will gain experience in a diversity of

technology specialties to be recognized in the industry and by our clients. Few companies have the ability to

provide opportunities for technology personnel to develop cross platform, cross industry, and cross technology

skills and experience.

•Practice makes perfect – project based work enables Architects to develop skills and then reapply them on a

regular basis. Initially, individuals enter Technology Architecture Practices with basic technology skills, but projects

orient them to the concepts of Technology Architecture and its practice at Accenture.

•Full stack – Our Architects increase the breadth of their experience and mastery of skills with project experience,

and will gain the ability to work with infrastructure through to the design and implementation of custom and

packaged systems.

Given the various types of Architecture Roles we’ve just described, and the varying scale and complexity of

engagements Accenture undertakes across its clients, there are many opportunities to grow. In addition,

Accenture is formalizing the certification and recognition of Technology Architects through the Master Technology

Architect (MTA) Program.




32


MTA Program

Targeted at developing market-relevant Architects, with breadth and depthacross disciplines and platforms – described using a framework.

Defines levels of mastery with defined criteria for progression, testing, andcertification over time.

Supports career progression as a Technology Architect based on workexperience, roles, stewardship, innovation and intellectual leadership.

Establishment of a global network of Architects, across workforces.

MTA Wiki (https://collaboration.accenture.com/display/MTA/Home)

Accenture’s Master Technology Architect Program provides consistentcriteria, expectations, objectives and growth opportunities for Accentureprofessionals who want to pursue a career in Technology Architecture.

The Master Technology Architect Program is a formal program to enable and recognize

specialization and advancement as a Technology Architect. The MTA Program providesconsistent criteria, expectations, objectives, and growth opportunities for Accenture professionals who

want to pursue a career in Technology Architecture.

The MTA Program is targeted at developing market-relevant Technology Architects, with breadth and

depth across disciplines and platforms. These disciplines and platforms are described using a Skills &Experience framework.

Additionally, the MTA Program defines levels of mastery with defined criteria for progression, testing,

and certification over time. This allows for the support of career progression as a Technology

Architect based on work experience, roles, stewardship, innovation, and thought leadership.

Finally, the MTA Program ensures the establishment of a global network of Architects, across

workforces, that is able to provide people with a broad range of skills.

More information can be found on the MTA Wiki at the link shown here.




33


Skills & Experience Framework

Skilled People

– Establish relevant base of skilledTechnology Architects

– Facilitate appropriate staffing withintechnology specialty

– Create network of recognized experts

Knowledge & Skill Development

– Define specialty knowledge & skill profiles

– Create skill building agenda, certifications

– Align and advance Master Architectagenda

Thought Leadership & Industrialization

– Drive greater levels of deliveryindustrialization

– Establish next generation technologyperspectives

– Play a leading role in innovation programs

Programming Languages

E s t i m a t i n g

P P M

M e t h o d ol o g y

E x e c u t i on

O p er a t i on s

D ev el o pm en t

Platforms / System Architectur es

Archite ctur e Plannin g

Infrastructure Architecture

Technical Architectur e

Infrastructure and Data Center

Networks and Network Services

System Software and Mid dleware

Data Architectur e

Applicat ion Archite ctur e

Patterns and Frameworks

Applicat ion St yles

Applicat ion Desi gn

Data Modeling

Business Process Modeling

I n t e gr a t i onA r c h i t e c t ur e

S e c ur i t y A r c h i t e c t ur e

T h e“ i l i t i e s ”

Component / Application

Services Modeling

Common Services

The Technology Architecture Practice is a “full service” Architecture group and, as such, needs to be

able to provide people with a broad range of skills. The MTA Program is targeted at building market-

relevant Architects, with breadth and appropriate depth across disciplines and platforms. A Skills &

Experience framework has been defined to cover the whole range of technology skills. This framework

is composed of areas of Architecture focus where Technology Architecture will supply skilled people

and where people will build their skills. The people in the Technology Architecture Practice will move

among these areas during their career and use the framework as a reference as they broaden their

knowledge and experience as Architects at Accenture.

The Skills & Experience framework is used to organize our efforts to sustain innovation and to

industrialize the role of Technology Architecture in our SI business. Most importantly, these

technology specialties guarantee that we have the full range of technology-oriented skills needed to

successfully sell, plan, and deliver SI work, ensuring skilled people, knowledge and skill development,

as well as thought leadership and innovation.

Architects require expertise and experience from the bottom to the top of the “stack” as depicted in the

Skills & Experience Framework. Architects will likely begin their careers in the bottom two or top two

layers – i.e. they will either be focused on Technical Architecture or on Application Architecture. A

rounded Architect must be able to bring these two disciplines together, designing a Technical

Architecture that can be used to build applications as well as building applications based on a

Technical Architecture.

Regardless of initial focus, all Architects must be proficient in integration, security, and the

implementation of “the ilities” – the quality attributes of performance, scalability, usability, availability,

and reliability. Hence, these Architectural aspects cross the core layers.

Expertise is required across a range of platforms and technologies. These are represented along the

bottom of the framework and the list presented is not exhaustive. Expertise is also required within the

three primary Architectures of development, execution, and operations. These are represented along

the left side of the framework and map to the Architectures described in ADA.

Finally, Architects need to be proficient in Accenture Delivery Methods, estimating, project

management, and program management.




36


Wrap-Up

This course provided an introduction to Technology Architect roles.There is more detail available on the topics covered here in the ‘ATTACHMENTS’ link.

Be sure to visit the Technology Architecture Training Wiki(https://collaboration.accenture.com/display/TATRAINING/)

You will be marked complete after successfully completing the nextquiz.

We touched very briefly on many different topics in this course, so be sure to visit the

‘ATTACHMENTS’ link at the top to explore areas in further detail. You can download the contents of

the presentation and audio transcripts via the same link.

You will now take a short quiz to help reinforce what you have learned. Upon completing the quiz, you

will be marked complete in myLearning for this course.

Thank you.

The Role of a Technology Architect

Documents

Transcript of The Role of a Technology Architect