 Needs Analysis. The first step in any software design process is to define the process and exactly
what it is that the customer actually wants. While this may seem to be a simple
and obvious step (and in fact, is often skipped by other companies), we believe
this to be one of the most important steps in the design and development process.
It is through this process that Software Principles and our customer come to a mutual
understanding and agreement of what will be delivered. Deliverable:
Needs Analysis Document
Requirements Gathering
Process.
Once the Needs Analysis process has been completed, the next stage is to define
the requirements of the business process. The deliverable for this process
is a Requirements Document. While this is a textual document with wording
to explain each individual requirement, the most important aspect of this document
is the fact that every requirement is succinctly presented and is assigned a unique
requirement number. This number will be used throughout the development process
and into the testing phase, so that we can ensure that we have met each and every
requirement.
Mockup and Development
Process.
This stage of the development process is the most time-consuming of the development
process. Software Principles utilizes an iterative design process to ensure
that the customer is pleased with the user interface and that the flow of the software
"works" for the way that the customer does business. Object-oriented design
principles are used to encapsulate business logic and provide the working functionality
of the software.
Testing Process.
A unique aspect of software developed by Software Principles is the use of a Testing
Plan. This Testing Plan document is the deliverable for this process, and
although this is the final step of the development process, this document is produced
alongside the Requirements Document. Each requirement enumerated in the Requirements
Document will have a stated plan of testing outlined. The customer will use
this document to test the delivered software for acceptance signoff.
|