My name is Robert Crewdson.   I have worked in the software development industry for more than 40 years as a software developer, the owner of a software development company and a senior executive/director of major software development tool vendors.  My passion project throughout that time has been the automation of software systems development.

​

My original interest was not so much automation of software development but a consistent method that would enable me to confidently quote a price and time frame for delivery of a software system.  The method that we developed was very successful.  The key to success was the creation of a systems specification that was always the single source of truth.  It could be understood and signed off by the client and was precise enough for developers to build the system without the need of further specification.  The method was so successful that it enabled me to take a 5 year sabbatical travelling with my young family.  During this period, I began to think of ways of improving the method and reducing risk by automating the build of the software system.

 

On return to the real world, I commenced work on this project while also running the Asia/Pacific operations of prominent software development tool vendors whose clients were large enterprises and government departments.   

  

My intention on starting this project, was to create a prototype that would convince a powerful industry player to commit to this method.  Over time my various interactions with the major players did not prove successful, however, my prototype was growing and starting to look more and more like a production system.  A number of opportunities arose where we could use our automated method. These opportunities all had the same characteristics, they were desirable but complex and had limited budgets.  The projects were for organisations with large IT departments and incumbent software and service providers. The proposed project had either been tried and failed or the incumbent providers were not willing to take on the project within the budget constraints.

​

In each case, we were able to provide a system specification that the client could understand and feel comfortable in signing off.  We could quote a fixed price within their budget and time constraints.  We were able to integrate the required third party products and in-house systems. The executable systems were built directly from the specification using automation.  You can find more information about some of these projects on this site.

​

Although each project was successful and very profitable, I only accepted projects that came to us and did not seek out new business. The specification-only method is enabled with software tools and platforms.  Our tools proved to be effective and efficient but long-term and widespread use of the method will require the support of a proven and trusted provider of software tools and platforms. 

​

So what is this site all about?

​

I’m not trying to sell you anything and I’m not trying to collect your personal information.  You don't need to register and there are no cookies.

 

I was recently asked to review some commercial software development projects and found them to be chaotic and poorly managed. This was having serious impact on the client company and conflict with the developers.  The contrast with specification-only development was stark and prompted me to create this site.

​

It's a place to explain the specification-only method in more detail, advocate for its use and promote interest and discussion.  The clear point of difference is the specification as the single source of truth that connects the client contract right through to the running system; providing certainty and dramatically lowering costs over the life of a software system.

 

All feedback is welcome provided it is civil (thoughtful would be good too).

​