Legacy Is Our Legacy
Whether you label certain endpoints, links, or nodes in your organization as legacy, the time is now to start your digital transformation journey.
Join the DZone community and get the full member experience.Join For Free
after our halloween webcast tales in testing – paranormal service virtualization use cases , i discovered the terrifying truth that i’m officially a millennial (by 13 weeks). at the same time, if i had been an information technology (it) system that was delivered over four decades ago, i would have most likely been written in cobol and found lurking on dectape somewhere in a dark server room! it’s official: i am legacy!
but what if i told you that the statement “legacy is our future” is not a contradiction and that everything within it is just a node?
why should you care about your legacy today?
modern organizations and applications are built off legacy systems and therefore depend on them. we’ll demonstrate this by building an imaginary connected device.
let us say our device is a simple physical switch that has two straightforward states, either a zero or a one. this is the legacy upon which the device will be built.
the switch alone is simple enough to check; it is either on or off. but what if you add another five physical switches and then have to account for all the possible orders in which they could be activated? suddenly, the possibilities that could be checked are roughly the same as the number of atoms in the universe.
this device is still simple by modern standards and is built with legacy parts. what if we now add a simple microservice to the switch and connect the system into an internet of things (iot) mesh that can be controlled directly from an amazon echo?
suddenly, we have gone from a simple legacy toggle switch to a machine to machine device, and then to an iot-connected device powered by artificial intelligence and enabled with deep learning algorithms.
if this is not enough to worry about, there are the added digital risks that come with cognitive adaptive technology to digital predators. just look at the recent examples of hackers exploiting iot connected crock pots . how do you currently fail-forward or self-heal from systemic failure? how can you keep alive after a massive distributed denial of service? think of the recent botnet attacks stemming from iot cannons in our recent blog . these modern threats feel better placed within an episode of mr. robot rather than the new reality for c-level executives (such as chief digital officers and chief risk officers).
all this potential risk to your brand just so i can ask alexa to turn on my heating in my uk home while presenting onstage at starwest’s think you can just ‘test’ that api? think again event in california last month. the cognitive adaptive technology that we are discussing already exists. and if you aren’t already testing it both functionally (remember: no uis) but more importantly non-functionally (security, performance, and resilience), then you need to become ready, capable, and enabled.
just think of the number of information transformations ( turing [i] machines – an abstract entity that can transform information ) and api calls (or equivalent programmable looms and punch cards) you need to make to bring these legacy technologies out of the dark ages and into the modern world. now imagine testing all of those!
what is legacy?
put simply, it is an unknown node that was once known. something of value that a human operator in the past has delivered into the ecosystem, but which is not self-managing or regulating. often, knowledge of these valuable components leaves with whoever created them. for example, in the late 1950s the cobol programming language was first introduced, nearly 50 years later in 1997, gartner estimated that there were 200 billion lines of cobol in existence, which ran 80% of all business programs.
what's the problem with having legacy for testing?
understanding. unless you completely understand every component and the related behaviors of your ecosystem of ecosystems, then the intention, know-how, and logic behind a system are questionable. without sufficient knowledge of the system, testers and developers are left to question the purpose of the system component. such uncertainty is the enemy of assurance, and we should aim to reduce epistemic uncertainty, striving to make all knowable knowledge known.
working with completely undocumented legacy systems is one of the core challenges the ca agile requirements designer development team has had to contend with. the complexity of these systems means that there are more possibilities to be tested than there are atoms in the universe. before a change, these organizations often attempt to gather knowledge from across as many teams as possible in the organization and rely on individual subject matter experts to create tests. the time spent planning a change sometimes then dwarfs the development time spent executing it — nowhere near reactive enough to develop systems that can keep up with constantly changing user needs.
how can you understand your legacy?
as the above examples suggest, you need to understand legacy components and how they relate to everything developed after them. to test systems enough to achieve true assurance, this understanding should go right down to the node level and how they relate.
the traditional approach to observing legacy systems that are not self-describing is reflection. today, the standard approach is to apply heuristic techniques to problem-solving, learning, or discovery, creating cognitive maps that reflect the current understanding of how the known nodes relate. these maps can then be maintained and built upon as knowledge is discovered.
the challenge with creating cognitive maps that route from a single node is that they typically only represent known knowledge insofar as it can be expressed by the teams that contribute to the maps. it can therefore exclude the quantitative intelligence necessary to provide the bigger picture, which means the cognitive maps do not represent all the possibilities present in the individual nodes. by contrast, true assurance requires the ability to sufficiently test against these possibilities.
how can you re-discover legacy enough to test it sufficiently?
legacy systems can be discovered by probing nodes as part of an exploratory approach. this involves probing by searching, investigating, and interrogating to obtain the contextual interrelationships of nodes and offer an acceptable and scientific approach to discovery.
this probing aims to uncover and record all knowable information in a self-discoverable manner. the purpose is to discover the behaviors of the underlying nodes within the subsystem, as well as the key interactions that make up the nervous system across the ecosystem. the end goal is to encapsulate the whole system holistically, leveraging a systems thinking approach and lean systems engineering techniques to apply the correct mindset, heuristics, and business goals.
once a visualization of the whole ecosystem has been achieved, the understanding of the legacy system can be maintained. this will be a constant iterative process of uncovering more knowledge (including that obtained through testing) and might encompass technologies such as machine learning, training algorithms, and intelligent analytics.
how can i test legacy?
full life cycle virtualization enables you to test hypotheses from day zero even for the most complex ecosystems of ecosystems. before a single line of code has been written, testing can be achieved via the virtualization of
- functional cx (globally unique identifiers).
- nonfunctional ux (link virtualization).
- security and penetration (endpoints virtualization).
with legacy, you are not testing from day zero; you are starting at the other end and trying to recover the knowledge that should have been established and maintained from the start. testing legacy therefore means moving from existing poorly understood operations to the design phases (i.e., opsdesign). with the knowledge needed to test a system upfront, best practices can be tested to provide true assurance that the legacy systems and everything built on them is functioning as it should.
using the above principles of discovery, imagine the potential of opening pandora’s box and discovering the entire biosphere of legacy components.
whether you label certain endpoints (as/400, 80s), links (ipx, 80s), or nodes (db2, 70s) within your organization as legacy or even retro, the time is now to start your digital transformation journey to digitally remastering the exponential innovation within your organizations.
the next step is to unlock your organization's digitalized dna so that you can become enterprise digital and go beyond legacy (remember that legacy is our legacy!).
Published at DZone with permission of Jonathon Wright, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
Manifold vs. Lombok: Enhancing Java With Property Support
Front-End: Cache Strategies You Should Know
How To Use Pandas and Matplotlib To Perform EDA In Python
Comparing Cloud Hosting vs. Self Hosting