Who can tell me sth about YOUR dream?

[Undertoad]

Sure Jag, I could talk about this all day! It's wild!

Basically, what happens when people set out to develop a complicated piece of software? Or even - something very complicated period, like an airport? They sit down and write specifications, sometimes in English with additional diagrams to map things out here and there. They may have a few tools like data flow diagrams and other kinds of flowcharts. They give all that to the programmer/developer/whatever to implement it, and since the specs suck horribly, the program/system/whatever doesn't work the way it was intended and/or doesn't work at all.

Some massive percentage of IT projects fail completely. Not just go over budget, not just go late... some major design decision that is critical to its operation is made incorrectly, or some connection is forgotten that can't simply be patched up without so much major rework that it's not worth completing.

My friend's idea ends all that. By placing certain specific logical constraints on how something is described, he's worked out how to avoid ANY missed connections, ANY missed information. And a system described in this way has special properties that make programming complicated systems almost *trivial*.

What my friend has developed is a new way of thinking about data design and process design. It expresses itself in flowchart form. It is utterly simple and yet utterly perfect in many different ways... ways you realize only when looking at it for days on end. It may in fact change *everything*! Everybody could develop this way. It could very well change how databases operate and even how most programming is done. We just don't know yet!!! It has to be pitched and licenses successfully sold to consulting houses, to give it the boost it needs so that we can continue to develop it, teach it, sell it.

What I wrote on the website:

---
The Business Architecture Method is a graphical business modeling tool.

It's a tool -- to document systems, processes, business rules... really, whatever you can think of. It kinda looks like a flowchart, but simpler.

Its basic, yet completely logical approach enforces how a system is documented. This, in turn, leads to huge advantages. The time to develop systems is reduced. An entire business can be modeled... and clarified to any detail. And its diagrams can be understood by just about anyone.

It creates new economies of scale. It details the scope of any system or project. It perfectly documents business processes. It produces ideal specifications to programmers. Anyone can be taught to read it in two minutes; anyone can be taught to write it in two days.

Its remarkable approach is U.S. Patent No. 5,418,942, 5,564,119, and 5,960,437.