Development
Visual and natural programming for non-programmers - a false hope?
Author: Craig Errey | Date: 25/09/2006
This paper will provide a crash course of the basic concepts behind programming in order to show that it is a non-trivial activity and, that in order to programme, you need to think in a certain way to successfully describe what you want to do so the computer can carry out your instructions. Is visual programming a false hope? Perhaps, but we're looking at it from a very different perspective.
The pattern perspective
Author: Jalal Radwan, Systems Engineer | Date: 01/09/2006
Systems Engineer Jalal Radwan explains what a pattern is, how they are useful for UI design, and how patterns allow you to create predictable applications that really work for users.
Designing and building reliable software
Author: Craig Errey | Date: 17/06/2006
'Designing and building reliable software' introduces the software design tool, Alloy, and the necessity behind rigorously testing and modelling software even before code is written. This approach, coupled with PTG Global's XPDesign methodology, should allow for software that is both reliable and easy to use.
Debunking the myths of IT development
Author: Craig Errey | Date: 01/03/2006
A number of myths have emerged from the forty odd years of IT applications development. Technologists and management alike have come to accept that software iteration is a good thing and expect that offshore outsourcing will solve the cost of IT problems. There are however, alternatives to these misconceptions and solutions to avoid repeating these troubles.
Rethinking the software development lifecycle
Author: Craig Errey | Date: 07/07/2005
It's generally accepted that around 50 - 80% of all major IT projects fail - over budget, late, missing requirements or poor user acceptance. Failures are often blamed on insufficient time or money, bad requirements, bad technology, not enough testing, stupid users or management without any vision. The solution has been to throw more and more time, money and technology at it all to no avail. These issues are merely symptoms, not the real problems. Why? Let's take a look at the way traditional IT development is handled.
