Click here to close now.

Welcome!

@MicroservicesE Blog Authors: Elizabeth White, Lori MacVittie, Liz McMillan, Pat Romanski, XebiaLabs Blog

Related Topics: Java IoT, @MicroservicesE Blog, Open Source Cloud, IoT User Interface, 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
Manufacturing has widely adopted standardized and automated processes to create designs, build them, and maintain them through their life cycle. However, many modern manufacturing systems go beyond mechanized workflows to introduce empowered workers, flexible collaboration, and rapid iteration. Such behaviors also characterize open source software development and are at the heart of DevOps culture, processes, and tooling.
SYS-CON Events announced today that JFrog, maker of Artifactory, the popular Binary Repository Manager, will exhibit at SYS-CON's @DevOpsSummit Silicon Valley, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. Based in California, Israel and France, founded by longtime field-experts, JFrog, creator of Artifactory and Bintray, has provided the market with the first Binary Repository solution and a software distribution social platform.
Conferences agendas. Event navigation. Specific tasks, like buying a house or getting a car loan. If you've installed an app for any of these things you've installed what's known as a "disposable mobile app" or DMA. Apps designed for a single use-case and with the expectation they'll be "thrown away" like brochures. Deleted until needed again. These apps are necessarily small, agile and highly volatile. Sometimes existing only for a short time - say to support an event like an election, the Wor...
The cloud has transformed how we think about software quality. Instead of preventing failures, we must focus on automatic recovery from failure. In other words, resilience trumps traditional quality measures. Continuous delivery models further squeeze traditional notions of quality. Remember the venerable project management Iron Triangle? Among time, scope, and cost, you can only fix two or quality will suffer. Only in today's DevOps world, continuous testing, integration, and deployment upend...
Sharding has become a popular means of achieving scalability in application architectures in which read/write data separation is not only possible, but desirable to achieve new heights of concurrency. The premise is that by splitting up read and write duties, it is possible to get better overall performance at the cost of a slight delay in consistency. That is, it takes a bit of time to replicate changes initiated by a "write" to the read-only master database. It's eventually consistent, and it'...
"Plutora provides release and testing environment capabilities to the enterprise," explained Dalibor Siroky, Director and Co-founder of Plutora, in this SYS-CON.tv interview at @DevOpsSummit, held June 9-11, 2015, at the Javits Center in New York City.
The most often asked question post-DevOps introduction is: “How do I get started?” There’s plenty of information on why DevOps is valid and important, but many managers still struggle with simple basics for how to initiate a DevOps program in their business. They struggle with issues related to current organizational inertia, the lack of experience on Continuous Integration/Delivery, understanding where DevOps will affect revenue and budget, etc. In their session at DevOps Summit, JP Morgenthal...
Explosive growth in connected devices. Enormous amounts of data for collection and analysis. Critical use of data for split-second decision making and actionable information. All three are factors in making the Internet of Things a reality. Yet, any one factor would have an IT organization pondering its infrastructure strategy. How should your organization enhance its IT framework to enable an Internet of Things implementation? In his session at @ThingsExpo, James Kirkland, Red Hat's Chief Arch...
Data center models are changing. A variety of technical trends and business demands are forcing that change, most of them centered on the explosive growth of applications. That means, in turn, that the requirements for application delivery are changing. Certainly application delivery needs to be agile, not waterfall. It needs to deliver services in hours, not weeks or months. It needs to be more cost efficient. And more than anything else, it needs to be really, dc infra axisreally, super focus...
Discussions about cloud computing are evolving into discussions about enterprise IT in general. As enterprises increasingly migrate toward their own unique clouds, new issues such as the use of containers and microservices emerge to keep things interesting. In this Power Panel at 16th Cloud Expo, moderated by Conference Chair Roger Strukhoff, panelists addressed the state of cloud computing today, and what enterprise IT professionals need to know about how the latest topics and trends affect t...
DevOps tends to focus on the relationship between Dev and Ops, putting an emphasis on the ops and application infrastructure. But that’s changing with microservices architectures. In her session at DevOps Summit, Lori MacVittie, Evangelist for F5 Networks, will focus on how microservices are changing the underlying architectures needed to scale, secure and deliver applications based on highly distributed (micro) services and why that means an expansion into “the network” for DevOps.
Containers are changing the security landscape for software development and deployment. As with any security solutions, security approaches that work for developers, operations personnel and security professionals is a requirement. In his session at DevOps Summit, Kevin Gilpin, CTO and Co-Founder of Conjur, will discuss various security considerations for container-based infrastructure and related DevOps workflows.
Containers have changed the mind of IT in DevOps. They enable developers to work with dev, test, stage and production environments identically. Containers provide the right abstraction for microservices and many cloud platforms have integrated them into deployment pipelines. DevOps and Containers together help companies to achieve their business goals faster and more effectively. In his session at DevOps Summit, Ruslan Synytsky, CEO and Co-founder of Jelastic, reviewed the current landscape of...
Summer is finally here and it’s time for a DevOps summer vacation. From San Francisco to New York City, our top summer conferences list is going to continuously deliver you to the summer destinations of your dreams. These DevOps parties are hitting all the hottest summer trends with Microservices, Agile, Continuous Delivery, DevSecOps, and even Continuous Testing. Move over Kanye. These are the top 5 Summer DevOps Conferences of 2015.
Cloud Migration Management (CMM) refers to the best practices for planning and managing migration of IT systems from a legacy platform to a Cloud Provider through a combination professional services consulting and software tools. A Cloud migration project can be a relatively simple exercise, where applications are migrated ‘as is’, to gain benefits such as elastic capacity and utility pricing, but without making any changes to the application architecture, software development methods or busine...
Overgrown applications have given way to modular applications, driven by the need to break larger problems into smaller problems. Similarly large monolithic development processes have been forced to be broken into smaller agile development cycles. Looking at trends in software development, microservices architectures meet the same demands. Additional benefits of microservices architectures are compartmentalization and a limited impact of service failure versus a complete software malfunction. ...
Many people recognize DevOps as an enormous benefit – faster application deployment, automated toolchains, support of more granular updates, better cooperation across groups. However, less appreciated is the journey enterprise IT groups need to make to achieve this outcome. The plain fact is that established IT processes reflect a very different set of goals: stability, infrequent change, hands-on administration, and alignment with ITIL. So how does an enterprise IT organization implement change...
While DevOps most critically and famously fosters collaboration, communication, and integration through cultural change, culture is more of an output than an input. In order to actively drive cultural evolution, organizations must make substantial organizational and process changes, and adopt new technologies, to encourage a DevOps culture. Moderated by Andi Mann, panelists discussed how to balance these three pillars of DevOps, where to focus attention (and resources), where organizations migh...
At DevOps Summit NY there’s been a whole lot of talk about not just DevOps, but containers, IoT, and microservices. Sessions focused not just on the cultural shift needed to grow at scale with a DevOps approach, but also made sure to include the network ”plumbing” needed to ensure success as applications decompose into the microservice architectures enabling rapid growth and support for the Internet of (Every)Things.
Mashape is bringing real-time analytics to microservices with the release of Mashape Analytics. First built internally to analyze the performance of more than 13,000 APIs served by the mashape.com marketplace, this new tool provides developers with robust visibility into their APIs and how they function within microservices. A purpose-built, open analytics platform designed specifically for APIs and microservices architectures, Mashape Analytics also lets developers and DevOps teams understand w...