In 2273, a Starfleet monitoring station, Epsilon Nine, detects an alien ship, hidden in a massive cloud of energy, moving through space towards Earth.
At the center of the massive ship, V’Ger is revealed to be Voyager 6, a 20th-century Earth space probe believed lost.
The damaged probe was found by an alien race of living machines that interpreted its programming as instructions to learn all that can be learned, and return that information to its creator.
The machines upgraded the probe to fulfill its mission, and on its journey the probe gathered so much knowledge that it achieved consciousness. – Star Trek Star Trek: The Motion Picture.
Although Voyager started out as a small and simple probe, over time it evolved into a massive self-aware system.
What is a V’Ger System?
V’Ger systems started life as small single purpose components that were written in order to satisfy a certain set of requirements.
Over time bugs were fixed, security patches were applied and requirements were added.
As turnover takes place, the core team that has maintained the system is no longer doing so and a new team is branching out of its core architecture in order to keep satisfying the ever evolving business requirements.
As branching takes place, the system evolves beyond its original purpose and design, adding new code pathways that are proving to be difficult to understand and maintain.
Eventually over the lifetime of the system, software patterns become anti patterns, new features take longer to implement and bugs fixes may cause other bugs to appear.
The system is now difficult to maintain and requires a larger investment in resources.
The Cost of Heaving No Creator
V’Ger systems are usually created in under documented software when turnover takes place and the core team is replaced.
Domain knowledge is key in the development effort and knowledge transfer between teams can mean the difference between extending the lifespan of the system or a slow deterioration of the code.
The creator has intimate knowledge of the system and its functions and can direct teams to stay within the original architectural design, or decide when it’s time to branch out or even add a new system.
How to Get Away From a V’Ger System
If you find you are increasingly spending time and resources maintaining your systems, you might have a V’Ger on your hands.
Migrating from a legacy V’Ger System to modern software might require an Inverted Software tailored migration plan.
We provide such plans as a part of our Phase Zero sprint, or as a part of our management packages.
Contact us today to see how we can help!