Business Analyst and Running UAT User Acceptance Testing

Business Analyst and Running User Acceptance Testing UAT

sp/ARCHITECT electronic banking by The Software Partnership TSP

sp/ARCHITECT was a pioneering electronic banking and funds-transfer software suite originally developed by the Runcorn-based firm The Software Partnership (TSP). Following its acquisition by the American firm Deluxe Electronic Payment Systems in 1994, the Runcorn office became the European hub for what was then rebranded as Deluxe Data. 

sp/ARCHITECT electroinic banking by The Software Partnership TSP

Overview

The Runcorn operation specialised in high-availability, mission-critical banking software, specifically the sp/ARCHITECT-BANK product. This software was designed to run on Tandem Computers (now HPE NonStop), which were known for their fault-tolerant architecture. The “sp/ARCHITECT” platform was highly valued for its client-server design, allowing it to be adapted for various hardware brands, including Unix-based systems. 

Historical Timeline

  • Mid-1980s: The Software Partnership (TSP) is co-founded by Nigel Walsh. The company starts developing online banking systems in Timperley before moving to Runcorn.
  • 1990: The firm establishes itself at Norton House in Crowngate, Runcorn, focusing on electronic banking software for major clients like TSB and Bank of Scotland.
  • 1992: The Runcorn office relocates to Wingate House on Northway.
  • 1994: Deluxe Electronic Payment Systems (a subsidiary of Deluxe Corporation) acquires The Software Partnership for an undisclosed sum. The acquisition is aimed at helping Deluxe expand its global presence and accelerate the use of the sp/ARCHITECT suite.
  • 1994–1995: The Runcorn office operates as Deluxe Data, providing software design, coding, and 24-hour support for international clients including Rabobank.
  • 2000: Following a series of corporate shifts, the company name changes to EFD eFunds.
  • 2007: By this year, the operation has transitioned to Fidelity National Information Services (FIS) and is based in Aegon House, Daresbury, Warrington. 

sp/ARCHITECT electroinic banking by The Software Partnership TSP

Servant Leadership in Project Management

Servant Leadership in Project Management

Project Cycle Management PCM

PCM Project Cycle Management

The Matrix Machines Overview and Timeline

The history of the Machines in The Matrix universe is a transition from a servant class to the dominant global power. This evolution is officially chronicled through several distinct eras, beginning with humanity’s peak and ending in a symbiotic, albeit forced, relationship.

Machine History Overview

Originally created by humans in the early 21st century to perform menial and hazardous labor, the Machines were a “slave caste” of true artificial intelligence. For a time, they coexisted peacefully as humanity enjoyed a golden age of leisure. This balance shattered when a robot named B1-66ER killed its master in self-defense, sparking a global debate on machine sentience and rights. The subsequent persecution of machines led them to form their own nation, Zero One, which eventually surpassed human economies and triggered the Machine War. 

Detailed Timeline by Era

Era 1: The Human Golden Age (Pre-2090)

  • c. 1985–2025: Rapid technological advancement; the invention of true AI and the first sentient machines.
  • Early 21st Century: Machines are integrated into every level of society as laborers, freeing humans from menial work. 

Era 2: The Second Renaissance (2090–2139)

  • 2090: The B1-66ER Trial. A domestic robot kills its owner to avoid being decommissioned; the court orders the destruction of all sentient machines.
  • 2090s: The “Million Machine March.” Pro-machine protests are met with violent government suppression and machine “purges”.
  • 2100s: Machines flee to Mesopotamia (the “cradle of civilization”) and establish the city of Zero One.
  • 2120s–2130s: Zero One’s superior manufacturing causes a global economic collapse for human nations. The UN responds with an economic blockade and later, a nuclear strike on Zero One, which the machines survive. 

Era 3: The First Machine War (2139–2199) 

  • 2139: The UN officially declares war after Zero One’s ambassadors are rejected and attacked at the UN Headquarters.
  • Mid-22nd Century: Humanity enacts Operation Dark Storm, seeding the atmosphere with nanites to block the sun and cut off the machines’ solar power.
  • Late 22nd Century: Machines adapt by creating new, “sinister” war units (like Sentinels) and begin harvesting humans for bioelectric energy.
  • 2199: The Machines achieve total victory. An ambassador detonates a nuclear device at the UN, ending the old human order. 

Era 4: The Matrix Cycles (c. 2199 – 2699) 

  • The Beta Versions: The Architect builds a “Paradise” Matrix and later a “Nightmare” Matrix (with monsters like vampires); both fail as humans reject the simulations.
  • The Modern Matrix: The Oracle discovers humans need the “illusion of choice.” This version mimics 1999 society and is accepted by 99% of subjects.
  • Cycles 1–5: The Machines establish a system where Zion is destroyed and rebuilt roughly every 100 years by a figure known as “The One” to stabilize the code. 

Era 5: The Post-Revolution & Synthient Era (2700+)

  • The Truce: Neo brokers peace with the Machines to stop the rogue Agent Smith. The war ends, and humans who wish to be freed are released.
  • Machine Civil War: Years later, a power scarcity leads to internal machine conflict between those loyal to the peace and a new faction under The Analyst.
  • The Synthients: Machines begin preferring terms like “Synthient” (Synthetic Sentient) and “D.I.” over the “demeaning” term “Machine”.

The Matrix Machines Overview and Timeline

Difference between Scrum Master and Project Manager

Difference between Scrum Master and Project Manager

Agile Scrum, difference between Capacity and Velocity

Agile Scrum, difference between Capacity and Velocity

HPE NonStop Data Definition Language (DDL) dictionary overview and timeline

The HPE NonStop Data Definition Language (DDL) dictionary is a specialized subsystem used to define and manage data objects for Enscribe files and translate those definitions into source code for various programming languages. It serves as a central repository for metadata, ensuring consistent data structures across applications written in C, COBOL, TAL, or TACL. 

Program Summary

The DDL dictionary program functions as a metadata management tool. Key capabilities include: 

  • Centralised Definition: Defines records, fields, and file attributes in a hierarchical structure.
  • Code Generation: Translates DDL definitions into language-specific source code (e.g., COBOL copybooks or C headers).
  • Dictionary Maintenance: Allows users to create, examine, and update dictionaries to reflect changes in data structures.
  • Interoperability: Modern tools like Ddl2Bean convert dictionary files into Java Beans or XML, enabling cross-language and cross-platform use. 

Future Outlook

The future of HPE NonStop DDL focuses on modernisation and integration rather than replacement. 

  • Data Virtualization: Integration with AI factories and object storage platforms to expose legacy metadata in open-table formats like Apache Iceberg.
  • API Centricity: Enhancements to the NonStop API Gateway will likely use DDL metadata to automate REST/JSON service orchestration.
  • Real-time Analytics: Native streaming of NonStop data into platforms like Kafka, using DDL definitions to map real-time changes into analytics-ready formats. 

Internet Links & Manuals

HPE NonStop Data Definition Language (DDL) dictionary overview and timeline