Welcome!

SDN Journal Authors: Daniel Gordon, John Walsh, Elizabeth White, Liz McMillan, Sven Olav Lund

Related Topics: @CloudExpo, SDN Journal, @ThingsExpo

@CloudExpo: Blog Post

SDLC Tool Integration Requires Domain Understanding | @CloudExpo #Cloud

These impedance mismatch examples require an understanding of the underlying business problem specific to software delivery

Consider the following integration scenarios: Moving medical records between EMR systems; financial information between banking systems; HR information between ERP systems; and software development information between SDLC tools.

At first glance the approaches required for these integrations may seem the same. But if you look slightly deeper you will realize that this can't be the case because of impedance mismatch. I'm defining impedance mismatch as the friction that occurs when trying to align two things or concepts that don't naturally/actually match. Because many of the hardest impedance mismatches are domain specific, to overcome them you have to have a layer of domain understanding "baked into" your integration software to address business problems.

That's what too often has been missing, because historically integration has primarily been perceived as being accomplished by overcoming a series of low-level, generic technical problems.

This misconception about addressing integration becomes evident as soon as someone comes into your office to sell you integration software. Invariably, the conversation quickly turns to questions such as: What is your message queue policy? How do you handle conflict management? What value transformations are available?

Those are secondary questions. Of course every application that you use should have those qualities. Shouldn't any integration application have a robust message queue implementation?

If you think of integration as nothing more than a series of low-level technical problems then you're going to default to those questions. No business person knows or cares about message queues, conflict management or value transformations. They care about getting the information they need when they want it. And that requires domain awareness.

Domain Expertise
Begin to move away from that misguided thinking about integration. There are virtually no troublesome technical hurdles anymore. Integration is a business problem that requires higher level technology solutions that are domain specific. And for different categories of business problems you need very different technical solutions. As a result, the next wave of integration will be all about domain expertise and nuance.

This brings us back to impedance mismatch. When you have something that has "friction" because there are fundamental differences between the two sides, what do you do?

Consider this example: If you are integrating requirements between IBM Doors Next Generation (DNG) and Atlassian JIRA, you need to know that JIRA only allows two levels of hierarchy (three if you include sub-task, but sub-task is used differently in JIRA to other artifact types). However DNG has an infinite number of them.

This business problem can only be solved by having the domain experts (the business analysts and the developers) decide how they will structure DNG such that the right layer in the tree translates to the epic/story in JIRA. JIRA can't handle more than two levels, and no amount of technical magic will help that. The only solution is to add a layer of domain expertise by practitioners, who must make some decisions. And the underlying integration software has to be "domain aware" to know that this situation can occur and what to do about it.

Here is another example. Let's say your organization is implementing the Scaled Agile Framework (SAFe). You need to have the high-level status of either "Ready for Release" or "In Development" at the Feature level. That is all the portfolio manager needs to know - and his tool is configured to handle those statuses.

But your developers have gotten deep into kanban, so the statuses for them are not just "In Development,"  but rather "Ready for SWAG," "Ready for UX Design," "Ready for Scoping," "Ready for Done Review," etc. What do you do?

Any integration software will know to provide a transformation that allows for multiple statuses in one tool to map to a single status in another tool. But domain aware integration software will provide a much needed level of ease of configuration (i.e. no coding) and should be able to automate the transformation needed. This is only possible if you "layer on" the domain expertise on top of the underlying technical engine.

General integration solutions that are nonspecific to the problem simply can't do this because they have no semantic understanding of the underlying information. Without really understanding the meaning of the data, which requires domain expertise, it is much harder to craft solutions that actually address the business problem you are trying to solve.

Dumb vs. Smart Integration
Consider this next example of integration using what I call dumb (generic) integration and smart (domain aware) integration techniques: Your organization needs to flow defects between itself and all suppliers. Defects are probably the most well understood and clearly defined artifacts that exist in software development. A dumb integration approach would simply list all the attributes that all defects have and then have you map each attribute to an attribute on the other side. If you have no insight into the actual goals of why these defects need to flow between systems, it would be legitimate to use this approach.

Since you are crossing organizational boundaries, you might want to create a "smart" integration to ensure that no proprietary attributes are being flowed outside your organization. And you may wish to limit attributes, for example, only to primary attributes such as priority and status to ensure efficient flow.

Rather than starting from scratch and working through all of the many impedance mismatches (e.g. one tool uses two attributes to represent priority and the other one uses only one attribute to represent priority), it makes sense for the integration tool to tell you what aspects of a defect should be flowed between tools and offer suggestions regarding when and how to best transform information when necessary. Without a layer of domain expertise, this can't be done.

Is the Tool Domain Aware?
All of these impedance mismatch examples require an understanding of the underlying business problem specific to software delivery that is being solved. As such, they are not low-level technology problems. And thus, it is critical that the first question that anyone asks when considering the right tools to help with integration is, "Is this tool domain aware?"

When moving medical records between EMR systems, consider software from a vendor that understands the healthcare industry. The same approach holds true for financial software. Software development is no different. Your approach to integrating SDLC tools should start from a place of domain expertise. Because to do SDLC integration well, you can't just simply throw technology at it. You have to bake in domain knowledge. It's as simple as that.

More Stories By Nicole Bryan

Nicole Bryan has extensive experience in software and product development, focused primarily on bringing data visualization and human considerations to the forefront of Application Lifecycle Management, and is currently Vice President of Product Management at Tasktop. Prior to this she served as Director of Product Management at Borland Software/Micro Focus, where she was responsible for creating a new Agile development management tool. Prior to Borland, she was a Director at the New York Stock Exchange (NYSE) Regulatory Division, where she managed some of the first Agile project teams at the NYSE, and VP of Engineering at OneHarbor (purchased by National City Investments).

Nicole holds a Master of Science in Computer Science from DePaul University. She is passionate about improving how software is created and delivered – making the experience enjoyable, fun and yes, even delightful.

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.


@CloudExpo Stories
DX World EXPO, LLC, a Lighthouse Point, Florida-based startup trade show producer and the creator of "DXWorldEXPO® - Digital Transformation Conference & Expo" has announced its executive management team. The team is headed by Levent Selamoglu, who has been named CEO. "Now is the time for a truly global DX event, to bring together the leading minds from the technology world in a conversation about Digital Transformation," he said in making the announcement.
"Space Monkey by Vivent Smart Home is a product that is a distributed cloud-based edge storage network. Vivent Smart Home, our parent company, is a smart home provider that places a lot of hard drives across homes in North America," explained JT Olds, Director of Engineering, and Brandon Crowfeather, Product Manager, at Vivint Smart Home, in this SYS-CON.tv interview at @ThingsExpo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
SYS-CON Events announced today that Conference Guru has been named “Media Sponsor” of the 22nd International Cloud Expo, which will take place on June 5-7, 2018, at the Javits Center in New York, NY. A valuable conference experience generates new contacts, sales leads, potential strategic partners and potential investors; helps gather competitive intelligence and even provides inspiration for new products and services. Conference Guru works with conference organizers to pass great deals to gre...
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...
In his Opening Keynote at 21st Cloud Expo, John Considine, General Manager of IBM Cloud Infrastructure, led attendees through the exciting evolution of the cloud. He looked at this major disruption from the perspective of technology, business models, and what this means for enterprises of all sizes. John Considine is General Manager of Cloud Infrastructure Services at IBM. In that role he is responsible for leading IBM’s public cloud infrastructure including strategy, development, and offering m...
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...
Companies are harnessing data in ways we once associated with science fiction. Analysts have access to a plethora of visualization and reporting tools, but considering the vast amount of data businesses collect and limitations of CPUs, end users are forced to design their structures and systems with limitations. Until now. As the cloud toolkit to analyze data has evolved, GPUs have stepped in to massively parallel SQL, visualization and machine learning.
"Evatronix provides design services to companies that need to integrate the IoT technology in their products but they don't necessarily have the expertise, knowledge and design team to do so," explained Adam Morawiec, VP of Business Development at Evatronix, in this SYS-CON.tv interview at @ThingsExpo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
To get the most out of their data, successful companies are not focusing on queries and data lakes, they are actively integrating analytics into their operations with a data-first application development approach. Real-time adjustments to improve revenues, reduce costs, or mitigate risk rely on applications that minimize latency on a variety of data sources. In his session at @BigDataExpo, Jack Norris, Senior Vice President, Data and Applications at MapR Technologies, reviewed best practices to ...
"ZeroStack is a startup in Silicon Valley. We're solving a very interesting problem around bringing public cloud convenience with private cloud control for enterprises and mid-size companies," explained Kamesh Pemmaraju, VP of Product Management at ZeroStack, 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.
Large industrial manufacturing organizations are adopting the agile principles of cloud software companies. The industrial manufacturing development process has not scaled over time. Now that design CAD teams are geographically distributed, centralizing their work is key. With large multi-gigabyte projects, outdated tools have stifled industrial team agility, time-to-market milestones, and impacted P&L stakeholders.
Enterprises are adopting Kubernetes to accelerate the development and the delivery of cloud-native applications. However, sharing a Kubernetes cluster between members of the same team can be challenging. And, sharing clusters across multiple teams is even harder. Kubernetes offers several constructs to help implement segmentation and isolation. However, these primitives can be complex to understand and apply. As a result, it’s becoming common for enterprises to end up with several clusters. Thi...
"Infoblox does DNS, DHCP and IP address management for not only enterprise networks but cloud networks as well. Customers are looking for a single platform that can extend not only in their private enterprise environment but private cloud, public cloud, tracking all the IP space and everything that is going on in that environment," explained Steve Salo, Principal Systems Engineer at Infoblox, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Conventio...
In his session at 21st Cloud Expo, James Henry, Co-CEO/CTO of Calgary Scientific Inc., introduced you to the challenges, solutions and benefits of training AI systems to solve visual problems with an emphasis on improving AIs with continuous training in the field. He explored applications in several industries and discussed technologies that allow the deployment of advanced visualization solutions to the cloud.
The question before companies today is not whether to become intelligent, it’s a question of how and how fast. The key is to adopt and deploy an intelligent application strategy while simultaneously preparing to scale that intelligence. In her session at 21st Cloud Expo, Sangeeta Chakraborty, Chief Customer Officer at Ayasdi, provided a tactical framework to become a truly intelligent enterprise, including how to identify the right applications for AI, how to build a Center of Excellence to oper...
"IBM is really all in on blockchain. We take a look at sort of the history of blockchain ledger technologies. It started out with bitcoin, Ethereum, and IBM evaluated these particular blockchain technologies and found they were anonymous and permissionless and that many companies were looking for permissioned blockchain," stated René Bostic, Technical VP of the IBM Cloud Unit in North America, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Conventi...
In his session at 21st Cloud Expo, Carl J. Levine, Senior Technical Evangelist for NS1, will objectively discuss how DNS is used to solve Digital Transformation challenges in large SaaS applications, CDNs, AdTech platforms, and other demanding use cases. Carl J. Levine is the Senior Technical Evangelist for NS1. A veteran of the Internet Infrastructure space, he has over a decade of experience with startups, networking protocols and Internet infrastructure, combined with the unique ability to it...
22nd International Cloud Expo, taking place June 5-7, 2018, at the Javits Center in New York City, NY, and co-located with the 1st DXWorld Expo will feature technical sessions from a rock star conference faculty and the leading industry players in the world. Cloud computing is now being embraced by a majority of enterprises of all sizes. Yesterday's debate about public vs. private has transformed into the reality of hybrid cloud: a recent survey shows that 74% of enterprises have a hybrid cloud ...
"Cloud Academy is an enterprise training platform for the cloud, specifically public clouds. We offer guided learning experiences on AWS, Azure, Google Cloud and all the surrounding methodologies and technologies that you need to know and your teams need to know in order to leverage the full benefits of the cloud," explained Alex Brower, VP of Marketing at Cloud Academy, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clar...
Gemini is Yahoo’s native and search advertising platform. To ensure the quality of a complex distributed system that spans multiple products and components and across various desktop websites and mobile app and web experiences – both Yahoo owned and operated and third-party syndication (supply), with complex interaction with more than a billion users and numerous advertisers globally (demand) – it becomes imperative to automate a set of end-to-end tests 24x7 to detect bugs and regression. In th...