Welcome!

Microservices Expo Authors: Elizabeth White, Liz McMillan, PagerDuty Blog, Yeshim Deniz, JP Morgenthal

Related Topics: Java IoT, Microservices Expo, Open Source Cloud, Machine Learning , Agile Computing, Release Management

Java IoT: Article

Architecture Assurance – The Road to Success

Ensuring successful project implementation

The aim of the Architecture Assurance is to provide collaborative architecture processes for assuring complete implementation of the technical solutions that are aligned with the business drivers of an enterprise in a timely environment. The effective sharing of the information across different Business Units (BU) / departments within an enterprise and interoperability across IT systems would ensure the alignment of IT with business. The Architecture Assurance Group (AAG) is involved in reviewing the Project Architecture during the design and development phases of an application/system to help ensure successful project implementation. This review also ensures that the proposed system fits into the existing enterprise environment as well as the future architecture vision.

The goals of Architecture Assurance include some or all of the following:

  • Identify inconsistencies in the architecture early, which reduces the cost and risk of changes required later in the life cycle
  • Provide an overview of the compliance of architecture to mandated enterprise standards
  • Identify where the standards may require modification
  • Identify services that are currently application-specific but might be provided as part of the enterprise infrastructure
  • Take advantage of advances in technology
  • Communicate to management the status of the technical readiness of the project
  • Identify and communicate significant architectural gaps to product and service providers
  • Establish, own and manage Enterprise Architecture Content
  • Provide architecture governance: guidelines and recommendations on business and IT architecture
  • Ensure and enforce architecture compliance: review changes and deviations in business and IT architecture
  • Resolve architectural ambiguities, issues and conflicts at the enterprise level
  • Identify projects that have high architectural risk, and provide assistance to them early and often throughout the project
  • Provide guidance to project managers and designers to direct architecture compliance
  • Formally review projects to ensure compliance
  • Leverage third-party assessments
  • Leverage COT's products

The main benefits of these reviews are:

Project Success

  • Architecture is reviewed by a group of experienced architects across the enterprise
  • Assistance in leveraging the existing architecture promoting the reusability
  • Architecture for plug and play
  • Promote simplification and standardization
  • Proactively identify risks to the project
  • Provide enterprise-wide context to project team

Maintain the integrity of the enterprise IT environment and expand the user community's access to Enter resources

  • Does the project presents risk to the IT environment (e.g., infrastructure, other applications, users, enterprise policy)
  • Allows Architecture Review Team to proactively recognize when modifications to the architecture are required
  • Allows the project team to provide input to the extension of the proposed architecture
  • Does the project leverage the existing common services where applicable
  • Provides cost effectiveness across the enterprise

Architecture Assurance Methodology
The Architecture Assurance Group is a multi-disciplinary body that is responsible for the maintenance and enforcement of Architecture, Design standards and best practices across the programs/projects. The primary responsibility is to provide governance and ensure compliance of the defined enterprise / solution architecture.

Architecture Assurance is the key success factor in ensuring high quality deliverables for the architecture and design phases. The intent of the Architecture Assurance Process is to ensure that ongoing projects have the right architectural assumptions and that in-flight projects receive architectural guidance throughout the life cycle. This should be a collaborative effort to ensure that project designs and implementations are compliant with the defined architecture

A detailed Architecture Assurance process that achieves these goals is shown in Figure 1.

Review Preparation
Architecture/Design Review(s) should be conducted at a stage when there is still time to correct any major inconsistencies or shortcomings in the program/project.

The Architecture/Design Review is typically targeted for the Analysis SDLC phase and at a point in time when:

  • Business goals, business requirements, policies are defined
  • Ball park clarity of hardware and software requirements & decisions are not finalized
  • Project schedules / timelines are defined
  • Project risk assessment is done

Architecture Review Criteria is:

  • Start Early
  • Drive and Participate in architecture workshop
  • Establish relation with architecture & design teams
  • Involve through architecture & design
  • Involve and review the architecture and design decisions on an ongoing basis
  • Review the intermittent and final architecture deliverables
  • Share architecture best practices
  • Mentor architecture and design teams as appropriate
  • Architectural Risk Analysis and Mitigation
  • Quality attribute analysis of architecture
  • Failure and risk analysis of architecture
  • Mentor on engineering best practices
  • Mentor on Development method, tools & build practices
  • Performance and other NFR related best practices

During the review, the architecture review team needs to extract the information like impacted groups, impacted systems, data feeds, software components required such as build, buy and reuse, security requirement, availability, scalability, error handling, capacity sizing, integration with third parties, data center/hosting facility, etc.

Key activities of the Architecture Assurance Group are:

  • Conduct planned and random formal architecture review workshops for projects and programs
  • Analyze architecture quality attributes against requirements
  • Conduct architecture failure and risk analysis and mitigation plan
  • Identify areas of non-compliance and options to redress shortcomings
  • Conduct formal/informal reviews of intermediate and final architecture deliverables to ensure ongoing compliance and quality
  • Review and track architecture and design decisions

Solution Fitment
In this phase, Architecture Assurance look for a high-level functional fit and nonfunctional fitment of the solution. Also verifies the solution mapping with the design and various options provided for the solution, reasons for the choices, TCO analysis of each option, etc.

Standards Adherence
In this phase, the verification of the alignment of the solution with the architecture requirements is done. Proper realization of the Architecture Principles, Architecture Patterns, IT Strategy alignment are performed in this phase. Any deviation of the standards needs to be approved by the Architecture Assurance Group.

Report Preparation
In this phase, the report will be reviewed in terms of Business, Data, application & Technology. Also, identification of the open items, action items and next steps will be addressed & communicated to the project team

Tracking
The prepared report will be presented to the Program management & track the observations to the closure. In this Phase, we oversee the updated architecture artifacts

Architecture Review Process
To ensure smooth, timely, and low impact reviews, the involved parties should prepare within the guidelines below. The process flow is shown in Figure 2.

The project architecture team is responsible for:

  • Developing a project description that provides sufficient detail for the review team to evaluate architectural risks, including the project size, business impact, NFRs, Architecture Principles
  • Sharing project estimates

The Architecture Assurance Team is responsible for:

  • Assessing projects for architectural impact during the Proposal/Project Initiation phase of the SDLC processes
  • Providing guidance to projects through the design phase to ensure that the final design is architecturally compliant
  • Prepare/Customize Architecture Templates, Architecture Checklist
  • Participate in the Architecture Review meetings to provide support to project teams and to assist the Architecture Assurance Group in decision making.
  • Analyze the filled up Checklist, Summarize the review findings
  • Customize Architecture Metrics

As part of the Architecture Review Process the following standards of the system need to be reviewed and agreed

Business:

  • Business Strategy, Goals & Vision
  • IT Strategy
  • Existing Budgets, Resource Plans, Project Plans
  • Business Scope Description
  • Use Case Specification
  • Business Requirements Document (BRD)
  • Service Level Agreements
  • TCO Model (CAPEX/OPEX etc.) - Funding Status
  • Build/Buy/Reuse(Retrofit) Considerations
  • Business process modeling and workflow system
  • Business Process Optimization
  • Business Process Analysis
  • Business Process Monitoring & SLA's

Application:

  • Application platform
  • Programming/scripting language
  • Testing/monitoring tools
  • User interface platform
  • Enterprise application integration platform
  • Conceptual Architecture
  • Logical Architecture
  • Physical Architecture
  • Security Architecture
  • Portal platform
  • Architecture Frameworks
  • Performance Tuning Plan
  • Migration Plan
  • Tool/Vendor Selection Results

Data:

  • Data Strategy
  • Logical Data Model (LDM)
  • Physical Data Model (PDM)
  • Data integration platform
  • Reporting and data analysis platform

Infrastructure:

  • Server platform and operating system
  • Desktop platform and operating system
  • Bill of Materials
  • H/W & S/W Acquisition/Lease Plan
  • Security Implementation/Management Plan
  • Deployment Plan
  • Operational Readiness Plan
  • Release Plan
  • Network infrastructure
  • System Performance Report
  • Disaster Recovery Plan

Architecture Assurance Lead will perform the following activities:

  • Assign Review Team
  • Disagreement/Issue Resolution
  • Review Findings discussion and agreement & communication with the project/program team

Review members will:

  • Commit to review all materials in advance
  • Prepare detailed questions using this practice standard and Checklist as appropriate
  • Conduct any preliminary research as necessary to be an informed team member
  • Attend all review meetings
  • Provide a final assessment and recommendation based on their interpretation of the impact of the proposed solution architecture and design on the Enterprise Architecture.

Acknowledgments
Authors like to thank Hari Kishan Burle, General Manager, Wipro Technologies for giving us the required time and support in many ways in bringing this article as part of Architecture Assurance Practice efforts.

More Stories By Gopala Krishna Behara

Dr. Gopala Krishna Behara is a Senior Enterprise Architect in the Enterprise Architecture & Solutions division of Wipro. He has a total of 16 years of IT experience. He can be reached at [email protected]

More Stories By Prasad Palli

Prasad Palli is a Practice Partner in the Enterprise Architecture & Solutions division of Wipro. He has a total of 15 years of IT experience. He can be reached at [email protected]

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@MicroservicesExpo Stories
Culture is the most important ingredient of DevOps. The challenge for most organizations is defining and communicating a vision of beneficial DevOps culture for their organizations, and then facilitating the changes needed to achieve that. Often this comes down to an ability to provide true leadership. As a CIO, are your direct reports IT managers or are they IT leaders? The hard truth is that many IT managers have risen through the ranks based on their technical skills, not their leadership abi...
The essence of cloud computing is that all consumable IT resources are delivered as services. In his session at 15th Cloud Expo, Yung Chou, Technology Evangelist at Microsoft, demonstrated the concepts and implementations of two important cloud computing deliveries: Infrastructure as a Service (IaaS) and Platform as a Service (PaaS). He discussed from business and technical viewpoints what exactly they are, why we care, how they are different and in what ways, and the strategies for IT to transi...
After more than five years of DevOps, definitions are evolving, boundaries are expanding, ‘unicorns’ are no longer rare, enterprises are on board, and pundits are moving on. Can we now look at an evolution of DevOps? Should we? Is the foundation of DevOps ‘done’, or is there still too much left to do? What is mature, and what is still missing? What does the next 5 years of DevOps look like? In this Power Panel at DevOps Summit, moderated by DevOps Summit Conference Chair Andi Mann, panelists l...
Thanks to Docker and the DevOps revolution, microservices have emerged as the new way to build and deploy applications — and there are plenty of great reasons to embrace the microservices trend. If you are going to adopt microservices, you also have to understand that microservice architectures have many moving parts. When it comes to incident management, this presents an important difference between microservices and monolithic architectures. More moving parts mean more complexity to monitor an...
All organizations that did not originate this moment have a pre-existing culture as well as legacy technology and processes that can be more or less amenable to DevOps implementation. That organizational culture is influenced by the personalities and management styles of Executive Management, the wider culture in which the organization is situated, and the personalities of key team members at all levels of the organization. This culture and entrenched interests usually throw a wrench in the work...
Microservices (μServices) are a fascinating evolution of the Distributed Object Computing (DOC) paradigm. Initial design of DOC attempted to solve the problem of simplifying developing complex distributed applications by applying object-oriented design principles to disparate components operating across networked infrastructure. In this model, DOC “hid” the complexity of making this work from the developer regardless of the deployment architecture through the use of complex frameworks, such as C...
DevOps is often described as a combination of technology and culture. Without both, DevOps isn't complete. However, applying the culture to outdated technology is a recipe for disaster; as response times grow and connections between teams are delayed by technology, the culture will die. A Nutanix Enterprise Cloud has many benefits that provide the needed base for a true DevOps paradigm.
TechTarget storage websites are the best online information resource for news, tips and expert advice for the storage, backup and disaster recovery markets. By creating abundant, high-quality editorial content across more than 140 highly targeted technology-specific websites, TechTarget attracts and nurtures communities of technology buyers researching their companies' information technology needs. By understanding these buyers' content consumption behaviors, TechTarget creates the purchase inte...
The IT industry is undergoing a significant evolution to keep up with cloud application demand. We see this happening as a mindset shift, from traditional IT teams to more well-rounded, cloud-focused job roles. The IT industry has become so cloud-minded that Gartner predicts that by 2020, this cloud shift will impact more than $1 trillion of global IT spending. This shift, however, has left some IT professionals feeling a little anxious about what lies ahead. The good news is that cloud computin...
DevOps is often described as a combination of technology and culture. Without both, DevOps isn't complete. However, applying the culture to outdated technology is a recipe for disaster; as response times grow and connections between teams are delayed by technology, the culture will die. A Nutanix Enterprise Cloud has many benefits that provide the needed base for a true DevOps paradigm. In his Day 3 Keynote at 20th Cloud Expo, Chris Brown, a Solutions Marketing Manager at Nutanix, will explore t...
We've all had that feeling before: The feeling that you're missing something that everyone else is in on. For today's IT leaders, that feeling might come up when you hear talk about cloud brokers. Meanwhile, you head back into your office and deal with your ever-growing shadow IT problem. But the cloud-broker whispers and your shadow IT issues are linked. If you're wondering "what the heck is a cloud broker?" we've got you covered.
What if you could build a web application that could support true web-scale traffic without having to ever provision or manage a single server? Sounds magical, and it is! In his session at 20th Cloud Expo, Chris Munns, Senior Developer Advocate for Serverless Applications at Amazon Web Services, will show how to build a serverless website that scales automatically using services like AWS Lambda, Amazon API Gateway, and Amazon S3. We will review several frameworks that can help you build serverle...
Everyone wants to use containers, but monitoring containers is hard. New ephemeral architecture introduces new challenges in how monitoring tools need to monitor and visualize containers, so your team can make sense of everything. In his session at @DevOpsSummit, David Gildeh, co-founder and CEO of Outlyer, will go through the challenges and show there is light at the end of the tunnel if you use the right tools and understand what you need to be monitoring to successfully use containers in your...
In today's enterprise, digital transformation represents organizational change even more so than technology change, as customer preferences and behavior drive end-to-end transformation across lines of business as well as IT. To capitalize on the ubiquitous disruption driving this transformation, companies must be able to innovate at an increasingly rapid pace. Traditional approaches for driving innovation are now woefully inadequate for keeping up with the breadth of disruption and change facing...
In his General Session at 16th Cloud Expo, David Shacochis, host of The Hybrid IT Files podcast and Vice President at CenturyLink, investigated three key trends of the “gigabit economy" though the story of a Fortune 500 communications company in transformation. Narrating how multi-modal hybrid IT, service automation, and agile delivery all intersect, he will cover the role of storytelling and empathy in achieving strategic alignment between the enterprise and its information technology.
Microservices are a very exciting architectural approach that many organizations are looking to as a way to accelerate innovation. Microservices promise to allow teams to move away from monolithic "ball of mud" systems, but the reality is that, in the vast majority of organizations, different projects and technologies will continue to be developed at different speeds. How to handle the dependencies between these disparate systems with different iteration cycles? Consider the "canoncial problem" ...
SYS-CON Events announced today that HTBase will exhibit at SYS-CON's 20th International Cloud Expo®, which will take place on June 6-8, 2017, at the Javits Center in New York City, NY. HTBase (Gartner 2016 Cool Vendor) delivers a Composable IT infrastructure solution architected for agility and increased efficiency. It turns compute, storage, and fabric into fluid pools of resources that are easily composed and re-composed to meet each application’s needs. With HTBase, companies can quickly prov...
The rise of containers and microservices has skyrocketed the rate at which new applications are moved into production environments today. While developers have been deploying containers to speed up the development processes for some time, there still remain challenges with running microservices efficiently. Most existing IT monitoring tools don’t actually maintain visibility into the containers that make up microservices. As those container applications move into production, some IT operations t...
For organizations that have amassed large sums of software complexity, taking a microservices approach is the first step toward DevOps and continuous improvement / development. Integrating system-level analysis with microservices makes it easier to change and add functionality to applications at any time without the increase of risk. Before you start big transformation projects or a cloud migration, make sure these changes won’t take down your entire organization.
In recent years, containers have taken the world by storm. Companies of all sizes and industries have realized the massive benefits of containers, such as unprecedented mobility, higher hardware utilization, and increased flexibility and agility; however, many containers today are non-persistent. Containers without persistence miss out on many benefits, and in many cases simply pass the responsibility of persistence onto other infrastructure, adding additional complexity.