Ultra High Reuse
May 28, 1999 - Jack Harich - Go Back
Our objective is to achieve a two orders of magnitude increase in software development productivity, using Ultra High Reuse (UHR) technology. UHR works by using a single guiding mechanism, reuse, to define an "Architecture of Concepts". Once mature UHR will open the door to entirely new uses and benefits from computer systems.
Quick Summary
UHR is ambitious, so we better play our cards right. Our Nutshell Strategy is simple: First we become very parts centric but domain neutral, and get assembling systems from reusable parts highly productive, following the principles of Structured Assembly. Then we introduce parts that do more and more of the work for us, starting with normal tasks and moving up the ladder to tasks that require more and more learning and self-directed activity, ending up with parts that are so independent the user is merely steering them around, much like a shepard and a flock of contented sheep. :-)
Corporate Perspective - This is a detailed high level introduction to UHR.It explains what UHR is, compares it to the Industiral Revolution, explores the potential impact and presents a few ideas on how to get started with UHR in your organization. In a nutshell, UHR replaces hand written code with parameter driven parts and frameworks.
The Advantages of UHR - This attempts the diffcult task of explaining how somethiing as large and novel as UHR can help you or your organization. This document includes a very interesting diagram of the 5 levels of process types, from a UHR perspective.
Key Little Visions - These are a quick read, helping you to grasp what we're up to, especially if you are new to this project.
Technology Grid - The conceptual vision is complex, so it is expressed in a large grid. This shows the 8 Phases used to develop this technology, plus the key Effects, Principles and Mechanisms. It also shows the potential Productivity Impact, which summarizes what each Phase yields if done well.
Please note this grid can only be described well in person. Expect to feel a little muddled and skeptical if understanding it from just these documents.
Grid Phases - Describes the phases to achieve the above objective. Phase sequence and successive reuse of elements accross phases is the heart of the development plan.
The Key UHR Behaviors is the closest thing we have to a "spec". This can help your understanding or even help you implement your own approach to UHR.
Magnification - UHR achieves its astounding results by a cunning maginifation of the effects of one element piled upon another and another. This is much like a multi-lens telescope or linear accelerator. Here we discuss how this is done.
What Differentiates UHR - By conceptualizing at the appropriate level of abstraction, we can see that UHR is an "Architecture of Concepts", while other historical approaches have been incremental improvements. This makes UHR a structural change capable of yielding an order of magnitude improvement.