DON BOSCO TECHNICAL COLLEGE

ARCHITECTURE DEPARTMENT
736 GENERAL KALENTONG ST., MANDALUYONG CITY

______________________________________________________________________
Name: GUERRERO, Ronne Louise B. Professor: Arch. Danilo T. Gonzales, FPIA, UAP
Year: 5th Year Architecture Date: September 4, 2023
Subject: BMA 1 Homework: BMA-1-HW # 3.1

Who are the stakeholders or players that the Architect work or interact with directly or
indirectly during the project cycle? Define their roles.

A Software Architect drives the technology and technical best practices in an engineering team.
The architect role is pivotal for any organization because this is where product management,
project management, and technology come hand in hand and speak a common language.

For an architect, identifying and managing important stakeholders is crucial; not only for him or
her to succeed in the role but also for the overall success of the product and eventually the
organization.

Any job role requires thorough identification, classification, and management of its stakeholders.
This is not an exception in any technical role as well, especially for a technical leadership role
such as a Software Architect.

It should start from the identification of the stakeholders and then stratifying them against a
matrix of "Interest" and "Power" of corresponding stakeholders.
 DON BOSCO TECHNICAL COLLEGE
ARCHITECTURE DEPARTMENT
736 GENERAL KALENTONG ST., MANDALUYONG CITY

Developer

Developers are architect's comrades-in-arms. If the architecture and the design don't resonate
with the developers while they implement the solution or if the developers are not well equipped
with the coding and designing guidelines and best practices, the product is bound to face
inevitable failure.

Along with active participation in the design and code reviews, architects need to engage with
developers in imparting and establishing clean coding and designing best practices and
guidelines. An architect should also play a crucial role in motivating and mentoring the
developers for the bigger interest of the team, product and organizational goal.
 DON BOSCO TECHNICAL COLLEGE
ARCHITECTURE DEPARTMENT
736 GENERAL KALENTONG ST., MANDALUYONG CITY

Product Manager

Any architectural and design decision should always be driven by the requirement. For an
architect, the product manager is the person with whom s/he grooms the product road-map,
customer needs and define and refine the technical blueprint from that. Architect's involvement
with a product manager is important in aligning the architecture and high-level design of the
product towards the customer needs.

Continuous collaboration also happens the other way around. The product manager also looks
for feedback from the technical feasibility and design perspective while formulating the market
requirements.

Program/Project Manager

The program/project manager needs to know the timeline, budget, and risk associated with an
architectural or design solution of a problem.

Architecture is all about trade-offs and more often than not, these trade-offs also depend on the
project management constraints of time-cost-budget-quality. Hence, it is of utmost importance
that architects do "manage" the program/project managers well and keep them aligned with the
whereabouts of the product architecture and design.

DevOps Engineer

DevOps Engineers are responsible for the release and deployment of the product. They also
take care of the network and deployment of infrastructure requirements, testing, and
development. Software Architects are equally responsible for defining the release, packaging,
and deployment strategies best suited for the product. CI/CD pipeline strategies,
update/upgrade strategies, etc. are usually defined by the software architect and executed
along with collaboration with the DevOps Engineers.

Alongside the DevOps engineers, architects play the important role in rolling out the SDLC best
practices, integration of internal quality matrices (static code analysis, etc.), choosing the right
automation framework and tools for developing and maintaining automated CI/CD pipelines.

Customer

The customer is king! Well, if not always, it is still a prevailing philosophy for software
engineering. Even though the Product Management team helps in interfacing with the market
requirement analysis, it is always a value-added facet for an architect to have a direct liaison
with the customer.

Architects often use this direct collaboration to read between the lines of customer requirements
to derive and device technical blueprints not only from the functional aspect but also from the
non-functional perspective of the product.
 DON BOSCO TECHNICAL COLLEGE
ARCHITECTURE DEPARTMENT
736 GENERAL KALENTONG ST., MANDALUYONG CITY

Stakeholder Management is an important discipline that successful architecture practitioners

can use to win support from others. It helps them ensure that their projects succeed where
others fail.

The benefits of successful Stakeholder Management are that:

 The most powerful stakeholders can be identified early and their input can then be used
to shape the architecture; this ensures their support and improves the quality of the
models produced.
 Support from the more powerful stakeholders will help the engagement win more
resource, thus making the architecture engagement more likely to succeed.
 By communicating with stakeholders early and frequently, the architecture team can
ensure that they fully understand the architecture process, and the benefits of enterprise
architecture; this means they can support the architecture team more actively when
necessary.
 The architecture team can more effectively anticipate likely reactions to the architecture
models and reports, and can build into the plan the actions that will be needed to
capitalize on positive reaction while avoiding or addressing any negative reactions.
 The architecture team can identify conflicting or competing objectives among
stakeholders early and develop a strategy to resolve the issues arising from them.

It is essential in any initiative to identify the individuals and groups within the organization who
will contribute to the development of the architecture, identify those that will gain and those that
will lose from its introduction, and then develop a strategy for dealing with them.

Stakeholder analysis should be used during Phase A (Architecture Vision) to identify the key
players in the engagement, and also be updated throughout each phase; different stakeholders
may be uncovered as the engagement progresses through into Opportunities & Solutions,
Migration Planning, and Architecture Change Management.

Complex architectures are extremely hard to manage, not only in terms of the architecture
development process itself, but also in terms of obtaining agreement from the large numbers of
stakeholders touched by it.

For example, just as a building architect will create wiring diagrams, floor plans, and elevations
to describe different facets of a building to its different stakeholders (electricians, owners,
planning officials), so an enterprise architect must create different views of the business,
information system, and technology architecture for the stakeholders who have concerns related
to these aspects.

TOGAF specifically identifies this issue throughout the ADM through the following concepts:

 Stakeholders
 Concerns
 Views
 Viewpoints
 DON BOSCO TECHNICAL COLLEGE
ARCHITECTURE DEPARTMENT
736 GENERAL KALENTONG ST., MANDALUYONG CITY

References

Dutta, N. (2020). The 5 most important stakeholders in an architect’s day at work. C# Corner.
https://www.c-sharpcorner.com/article/5-most-important-stakeholders-in-an-architects-
day/

Group, O. (2011). Stakeholder Management. Stakeholder management.

https://pubs.opengroup.org/architecture/togaf91-doc/arch/chap24.html