Empowering engineers and others to create software

With my PhD work, there was extensive prototyping of software solutions created and feedback from engineers. At first engineers tended to ask for software that followed the strategy of the business and met its deadlines. What emerged over time though was a desire from engineers to have more control over the software so that they could do this themselves and have input into this strategy. With a top down strategy and inflexible software and rules about what can be used and installed, missing of deadlines, and problems in meeting aims were built into the system, and engineers realised this.

So even in engineering, an industry that by its nature has to be conservative, due to safety needs, it is realised that empowerment is necessary in software development. So there was a need to empower the engineers by provision of collaborative software that could be installed and used as easily as possible and be adaptable. Empowering the engineers to be fully involved in the creation and maintenance of such software, because they're interested in the software and what it can do, was essential to make the use, re-use and maintenance of the software practical. This is necessary because it would not be possible to achieve application of useful software by any top down strategy, with limited involvement of higher managers and software suppliers. Visualisation and modelling of the software by a large range of people can be achieved by use of diagrams to show the problem and software structure, as part of the software and how it is used.

Further feedback was obtained from others via an online survey of a greater cross section of others rather than only engineers. This bore out that people want more control and involvement in software development and use, and that visual editing of the software over the web is the best way to achieve this.