Welcome!

Microservices Expo Authors: Stackify Blog, Aruna Ravichandran, Dalibor Siroky, Kevin Jackson, PagerDuty Blog

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
How is DevOps going within your organization? If you need some help measuring just how well it is going, we have prepared a list of some key DevOps metrics to track. These metrics can help you understand how your team is doing over time. The word DevOps means different things to different people. Some say it a culture and every vendor in the industry claims that their tools help with DevOps. Depending on how you define DevOps, some of these metrics may matter more or less to you and your team.
For many of us laboring in the fields of digital transformation, 2017 was a year of high-intensity work and high-reward achievement. So we’re looking forward to a little breather over the end-of-year holiday season. But we’re going to have to get right back on the Continuous Delivery bullet train in 2018. Markets move too fast and customer expectations elevate too precipitously for businesses to rest on their laurels. Here’s a DevOps “to-do list” for 2018 that should be priorities for anyone w...
If testing environments are constantly unavailable and affected by outages, release timelines will be affected. You can use three metrics to measure stability events for specific environments and plan around events that will affect your critical path to release.
In a recent post, titled “10 Surprising Facts About Cloud Computing and What It Really Is”, Zac Johnson highlighted some interesting facts about cloud computing in the SMB marketplace: Cloud Computing is up to 40 times more cost-effective for an SMB, compared to running its own IT system. 94% of SMBs have experienced security benefits in the cloud that they didn’t have with their on-premises service
DevOps failure is a touchy subject with some, because DevOps is typically perceived as a way to avoid failure. As a result, when you fail in a DevOps practice, the situation can seem almost hopeless. However, just as a fail-fast business approach, or the “fail and adjust sooner” methodology of Agile often proves, DevOps failures are actually a step in the right direction. They’re the first step toward learning from failures and turning your DevOps practice into one that will lead you toward even...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Microservices being modular these are faster to change and enables an evolutionary architecture where systems can change, as the business needs change. Microservices can scale elastically and by being service oriented can enable APIs natively. Microservices also reduce implementation and release cycle time and enables continuous delivery. This paper provides a logical overview of the Mi...
While walking around the office I happened upon a relatively new employee dragging emails from his inbox into folders. I asked why and was told, “I’m just answering emails and getting stuff off my desk.” An empty inbox may be emotionally satisfying to look at, but in practice, you should never do it. Here’s why. I recently wrote a piece arguing that from a mathematical perspective, Messy Desks Are Perfectly Optimized. While it validated the genius of my friends with messy desks, it also gener...
The next XaaS is CICDaaS. Why? Because CICD saves developers a huge amount of time. CD is an especially great option for projects that require multiple and frequent contributions to be integrated. But… securing CICD best practices is an emerging, essential, yet little understood practice for DevOps teams and their Cloud Service Providers. The only way to get CICD to work in a highly secure environment takes collaboration, patience and persistence. Building CICD in the cloud requires rigorous ar...
The enterprise data storage marketplace is poised to become a battlefield. No longer the quiet backwater of cloud computing services, the focus of this global transition is now going from compute to storage. An overview of recent storage market history is needed to understand why this transition is important. Before 2007 and the birth of the cloud computing market we are witnessing today, the on-premise model hosted in large local data centers dominated enterprise storage. Key marketplace play...
The cloud revolution in enterprises has very clearly crossed the phase of proof-of-concepts into a truly mainstream adoption. One of most popular enterprise-wide initiatives currently going on are “cloud migration” programs of some kind or another. Finding business value for these programs is not hard to fathom – they include hyperelasticity in infrastructure consumption, subscription based models, and agility derived from rapid speed of deployment of applications. These factors will continue to...
Some people are directors, managers, and administrators. Others are disrupters. Eddie Webb (@edwardawebb) is an IT Disrupter for Software Development Platforms at Liberty Mutual and was a presenter at the 2016 All Day DevOps conference. His talk, Organically DevOps: Building Quality and Security into the Software Supply Chain at Liberty Mutual, looked at Liberty Mutual's transformation to Continuous Integration, Continuous Delivery, and DevOps. For a large, heavily regulated industry, this task ...
Following a tradition dating back to 2002 at ZapThink and continuing at Intellyx since 2014, it’s time for Intellyx’s annual predictions for the coming year. If you’re a long-time fan, you know we have a twist to the typical annual prediction post: we actually critique our predictions from the previous year. To make things even more interesting, Charlie and I switch off, judging the other’s predictions. And now that he’s been with Intellyx for more than a year, this Cortex represents my first ...
"Grape Up leverages Cloud Native technologies and helps companies build software using microservices, and work the DevOps agile way. We've been doing digital innovation for the last 12 years," explained Daniel Heckman, of Grape Up in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
The Toyota Production System, a world-renowned production system is based on the "complete elimination of all waste". The "Toyota Way", grounded on continuous improvement dates to the 1860s. The methodology is widely proven to be successful yet there are still industries within and tangential to manufacturing struggling to adopt its core principles: Jidoka: a process should stop when an issue is identified prevents releasing defective products
We seem to run this cycle with every new technology that comes along. A good idea with practical applications is born, then both marketers and over-excited users start to declare it is the solution for all or our problems. Compliments of Gartner, we know it generally as “The Hype Cycle”, but each iteration is a little different. 2018’s flavor will be serverless computing, and by 2018, I mean starting now, but going most of next year, you’ll be sick of it. We are already seeing people write such...
Defining the term ‘monitoring’ is a difficult task considering the performance space has evolved significantly over the years. Lately, there has been a shift in the monitoring world, sparking a healthy debate regarding the definition and purpose of monitoring, through which a new term has emerged: observability. Some of that debate can be found in blogs by Charity Majors and Cindy Sridharan.
It’s “time to move on from DevOps and continuous delivery.” This was the provocative title of a recent article in ZDNet, in which Kelsey Hightower, staff developer advocate at Google Cloud Platform, suggested that “software shops should have put these concepts into action years ago.” Reading articles like this or listening to talks at most DevOps conferences might make you think that we’re entering a post-DevOps world. But vast numbers of organizations still struggle to start and drive transfo...
Let's do a visualization exercise. Imagine it's December 31, 2018, and you're ringing in the New Year with your friends and family. You think back on everything that you accomplished in the last year: your company's revenue is through the roof thanks to the success of your product, and you were promoted to Lead Developer. 2019 is poised to be an even bigger year for your company because you have the tools and insight to scale as quickly as demand requires. You're a happy human, and it's not just...
"Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.