Nuway Software follows the Unified Software Development Process (UP). We use UML to diagram and visually represent aspects of the system. Most clients are unfamiliar with UML and we are very happy to educate them before initiating the project.
Our proprietary NuDoc documentation technology allows us to communicate efficiently throughout the project. This format was developed after years of experience and client feedback. NuDoc eliminates the reading of out dated documentation, confusion of what changes were made, and losing track of feedback or notes.
The following synopsis outlines what our clients can expect as we work together on the project. A specific road map is provided upon commencement of a project.
During this phase, a good idea is developed into a vision of the
end product and the business case for the product is presented. Essentially,
this phase answers the following questions:
What is the system primarily going to do for each of its major users?
What could an architecture for that system look like?
What is the plan and what will it costs to develop the product?
A simplified document that contains the most critical use cases answers the first question. At this stage the architecture is tentative. It is typically just an outline containing the most crucial subsystems. In this phase, the most important risks are identified and prioritized, the elaboration phase is planned in detail, and the whole project is roughly estimated.
During the elaboration phase, most of the product's use cases are specified in detail. Most importantly, the system architecture is designed. The architecture is expressed as several diagrams of the system, which together represent the whole system. The analysis of the implementation model includes components to prove that the architecture is executable. It is imperative that the construction phase not begin until the architecture is stable.
During the construction phase the product is built. During this phase of development, the bulk of the required resources is expended. The architecture of the system is stable, however, because the constructors may discover better ways of structuring the system, they may suggest minor architectural changes to the architects. At the end of this phase, the product contains all the use cases that management and the customer agreed to develop for this release.
This phase covers the period during which the product moves into beta release (typically to a soft-release environment). A small number of experienced users try the product and report defects and deficiencies. Constructors then correct the reported problems. User documentation and training are provided during this period.
If you have always done it that way, it is probably wrong.