When you use a technology term to describe a customer value you've lost the customer. And you've made 1000 assumptions without knowing!
Without a domain and context, this statement has no meaning.
Let's say we use a technical term like Command & Data Handling.
The Command and Data Handling subsystem is essentially the "brains" of the orbiter and controls all spacecraft functions. This system:
- Manages all forms of data on the spacecraft;
- Carries out commands sent from Earth;
- Prepares data for transmission to Earth;
- Manages the collection of solar power and charging of the batteries;
- Collects and processes information about all subsystems and payloads;
- Keeps and distributes the spacecraft time;
- Calculates the spacecraft's position in orbit around Mars;
- Carries out commanded maneuvers; and,
- Autonomously monitors and responds to a wide range of onboard problems that might occur.
The scientist and navigators using the C&DH (Command & Data Handling) system along with the GN&C (Guidance Navigation & Control) system those technical terms explicitly, clearly, succinctly, unambiguously, precisely, and without a doubt define the Customer Value to them, when they are doing their jobs sitting the control room at JPL (Jet Propulsion Laboratory) in Pasadena California.
So when you hear some platitude like that stated in the first line, ask in what domain, in what context, for what user is that conjecture applicable?
These no domain, no context statement are fallacious to start and then used as fodder to further the myth, the simple and simple-minded concept will fix the root causes of most all software development projects, including the problems with the development of MRO's flight and ground software.
With embedded system out numbers desk to and web app 200 to 1, if we're going to focus improving of the probability of software success, let's follow the money.
