Temporal Engineering

Software as an asset is problematic because of the if-then-else and case-switch (ITE) structure. ITE doesn't allow software to provide beyond type introspection. The asset value is based on professional guessing about what the software contains and what the software is capable of providing. Temporal engineering provides the framework for traditional type introspection plus extensive logic introspection. Logic introspection can actually examine what the software logic is capable of performing. Temporal engineering is based on the technology described Breaking the Time Barrier by Gordon Morrison; the book is available at Amazon.

Costly Tool or Company Asset

Think of traditional software as a bucket of nuts, bolts, and washers. There's no order, the bucket's contents appear to be random. Temporal engineering provides an organized container with drawers; holding bins separating the nuts, bolts, and washers. Any size nut, bolt, or washer can easily be found by an organized search; an inventory can easily be created once the organization is completed. The greater asset value is intrinsic in consistently organized technology and products. This order is accomplished using Vector State Machines.

Bucket-of-Bolts or Engineered Quality

Nature doesn't like order. The bucket-of-bolts represent a complete lack of order which unfortunately represents ALL software development that is not based on temporal engineering.
Order requires an engineering discipline. Software engineers are not known for their discipline. The terms 'herding cats', 'hacking', 'spaghetti code', and failed projects are synonymous with software projects. In general software projects lack 'adult supervision' and that's where temporal engineering comes to play. Contact VS Merlot for our consulting services at Consulting@VSMerlot.com.