The Process We Use to Build Your Software
New Zealand IT prefers to employ the USDP (Unified Software Development Process) as our software development methodology. This industry standard SDLC (Software Development Life Cycle) is, in our opinion, one of the best ways to manage software development. The diagram below gives an overview of the process and the text describes some of its benefits from both a business and technology perspective.
From a Business Perspective
Historically, a business was given a high level plan with one set date in the future when their software project would be ready. The business had no truly effective way of knowing whether the project was on track until the date was either met or missed. The USDP breaks the entire project up into many concrete deliverables which ensures the business has many release dates, and also allows project corrections and adjustments to be made when they are needed, not after everything has fallen apart.
The USDP is also designed to accept changes to the Business Requirements specification during the development cycle. In an ideal world a business could write a specification for a computer system, send the specification to the developers and three months later have a system delivered which meets their needs. The problem is that we do not live in an ideal world. Business environments and focuses change, important details can be left out, technologies can fail to deliver what they promised and new ideas may need to be incorporated. The USDP can not only cope with change, it expects change and is able to adapt quickly.
From a Technology Perspective
The USDP fits in very well with modern Object Oriented Analysis, Design, and Development techniques because it was designed with them in mind.
Continually imminent release dates help motivate the development team for maximum effort.
The small iterative development cycles reflect how software is best built. Design a bit, build a bit, test a bit. Each manageable part is thoroughly designed, developed and tested before moving on to the next stage.
The USDP is "architecture-centric". One of the benefits of this attribute is that the base technology for the system is proven early in the project. This avoids the horrible realization at the end of the project, for example, that the system may work, but cannot cope with commercial volumes.
There are other benefits in using the USDP from both the business and technology perspectives. Feel free to email us
with your questions.