Welcome!

Microservices Expo Authors: Elizabeth White, Gopala Krishna Behara, Sridhar Chalasani, Tirumala Khandrika, Liz McMillan

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.


Microservices Articles
More and more companies are looking to microservices as an architectural pattern for breaking apart applications into more manageable pieces so that agile teams can deliver new features quicker and more effectively. What this pattern has done more than anything to date is spark organizational transformations, setting the foundation for future application development. In practice, however, there are a number of considerations to make that go beyond simply “build, ship, and run,” which changes how...
DevOpsSummit New York 2018, colocated with CloudEXPO | DXWorldEXPO New York 2018 will be held November 11-13, 2018, in New York City. Digital Transformation (DX) is a major focus with the introduction of DXWorldEXPO within the program. Successful transformation requires a laser focus on being data-driven and on using all the tools available that enable transformation if they plan to survive over the long term.
As Enterprise business moves from Monoliths to Microservices, adoption and successful implementations of Microservices become more evident. The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Documenting hurdles and problems for the use of Microservices will help consultants, architects and specialists to avoid repeating the same mistakes and learn how and when to use (or not use) Microservices at the enterprise level. The circumstance w...
Containers, microservices and DevOps are all the rage lately. You can read about how great they are and how they’ll change your life and the industry everywhere. So naturally when we started a new company and were deciding how to architect our app, we went with microservices, containers and DevOps. About now you’re expecting a story of how everything went so smoothly, we’re now pushing out code ten times a day, but the reality is quite different.
Traditional IT, great for stable systems of record, is struggling to cope with newer, agile systems of engagement requirements coming straight from the business. In his session at 18th Cloud Expo, William Morrish, General Manager of Product Sales at Interoute, will outline ways of exploiting new architectures to enable both systems and building them to support your existing platforms, with an eye for the future. Technologies such as Docker and the hyper-convergence of computing, networking and...
While some developers care passionately about how data centers and clouds are architected, for most, it is only the end result that matters. To the majority of companies, technology exists to solve a business problem, and only delivers value when it is solving that problem. 2017 brings the mainstream adoption of containers for production workloads. In his session at 21st Cloud Expo, Ben McCormack, VP of Operations at Evernote, discussed how data centers of the future will be managed, how the p...
The explosion of new web/cloud/IoT-based applications and the data they generate are transforming our world right before our eyes. In this rush to adopt these new technologies, organizations are often ignoring fundamental questions concerning who owns the data and failing to ask for permission to conduct invasive surveillance of their customers. Organizations that are not transparent about how their systems gather data telemetry without offering shared data ownership risk product rejection, regu...
Containers and Kubernetes allow for code portability across on-premise VMs, bare metal, or multiple cloud provider environments. Yet, despite this portability promise, developers may include configuration and application definitions that constrain or even eliminate application portability. In this session we'll describe best practices for "configuration as code" in a Kubernetes environment. We will demonstrate how a properly constructed containerized app can be deployed to both Amazon and Azure ...
CloudEXPO New York 2018, colocated with DXWorldEXPO New York 2018 will be held November 11-13, 2018, in New York City and will bring together Cloud Computing, FinTech and Blockchain, Digital Transformation, Big Data, Internet of Things, DevOps, AI, Machine Learning and WebRTC to one location.
The now mainstream platform changes stemming from the first Internet boom brought many changes but didn’t really change the basic relationship between servers and the applications running on them. In fact, that was sort of the point. In his session at 18th Cloud Expo, Gordon Haff, senior cloud strategy marketing and evangelism manager at Red Hat, will discuss how today’s workloads require a new model and a new platform for development and execution. The platform must handle a wide range of rec...