 | |
 
The qSDS Philosophy
Quality Software
The qPrise Software Development System (qSDS) is based on the principle that software quality is a mandate,
not an option. By our definition, a high-quality software solution:
 | Has deployment objectives that are clear and unambiguous
|
| Has been designed and built according to sound engineering principles
|
| Has been thoroughly tested in both laboratory and field environments
|
We believe that:
| The extra effort expended in high-quality work is always returned in:
 | Suitability to purpose
|
| Increased reliability
|
| Reduced iterations
|
| Ease of modification
|
|
| Software quality is achieved by careful management of the software
development process, including:
| An orderly, planned approach
|
| Clear, documented communication
|
| Active monitoring and feedback at all stages
|
|
Any systematic approach to software development must be oriented and adapted
to the specific needs of the organisation. It must also be audited regularly
for:
| Suitability to the ongoing and changing needs of the organisation
|
| Effective and practical compliance
|
An Ordered Software Development Process
The qSDS promotes the following things:
| A well-ordered approach to software development
|
| The use of objective metrics in assessing the system
|
| A 'predictive understanding' of the solution, so that how a task is
to be executed is known before it is executed
|
| 'Early notification' of issues affecting the outcomes of the development
|
| Flexibility for the introduction of changes
|
Thus, our approach to software development is based on the following
principles:
- All the requirements of the system must be clearly stated and understood before
a solution is proposed.
- A proposed solution to the requirements (in the form of a design) must be
verified against the stated requirements to ensure that:
- No requirement is violated by any element of the design
- All requirements are covered by the design
- The implementation (of the design) must be verified against the design and
the requirements (validation against requirements is the work of formal
testing).
- Changes in requirements and design must be carefully managed and analysed to ensure
that all implications of the change for requirements and design are exposed.
- The relationships between requirements, design elements, implementation
elements and verification (testing) procedures must be clear and understood
by all participants in the work.
With these objectives and principles in mind, we create a documented
and managed process, on which specific, step-by-step procedures are based. Our
procedures give rise to tools that enable and assist their execution.
|
