WiCoRe Quality Process

wicore.com | about | Quality Process


	Profile

	Vision & Core Values

	Quality Process

	Careers

	Contact

Software quality

Our transparent approach allows you to have online access to the QA system and track the quality status of the project throughout the software development cycle.

Terminology for quality attributes differs from one taxonomy or model of software quality to another; each model may have different numbers of hierarchical levels and a different total number of attributes.

Quality assurance

ISO 9000 defines quality assurance as:
"All those planned and systematic actions necessary to provide adequate confidence that a product or service will satisfy given requirements for quality."

When the "product" concerned is a safety critical system, the main objectives of a quality assurance system are:

  - To increase the quality of the product
  - To provide a foundation for the safety justification (safety case)
  - To improve development and production efficiency

The relative importance of these factors will vary greatly between projects, with less critical applications placing much emphasis on the last aspect. In contrast, in more critical applications, improvements in efficiency are invariably of less concern than other considerations.

A fundamental part of quality assurance involves defining the necessary procedures for a given project and the management structure concerned. This involves listing the tasks and the people performing them.

System Quality

Factors	Dependability	Satisfaction	Functionality	Flexibility	Performance
Criteria & Metrics	Safety Reliability Security Error-tolerance Testability	Ease of use Understandability Learnability Productivity Acceptance	Functional completeness Complexity Adequacy Integrity Traceability	Portability Modifiability Configurability Ease of testing	Scalability Stability Interaction performance Execution efficiency

  - Software Concept and Initiation Phase
  - Software Requirements Phase
  - Software Architectural (Preliminary) Design Phase
  - Software Detailed Design Phase
  - Software Implementation Phase
  - Software Integration and Test Phase
  - Software Acceptance and Delivery Phase
  - Software Sustaining Engineering and Operations Phase

Guidelines for their Use. It defines six characteristics that determine software quality. These are:

  - Functionality
  - Reliability
  - Usability
  - Efficiency
  - Maintainability
  - Portability

Defects can occur during any life cycle activity against any and all entities. How often do we see requirements that are without problems or schedules that are adequate or management that is sound? Defect Prevention activities are conducted on any defects that warrant prevention. Defect prevention techniques can be applied to a variety of items:

Project Plans, Project Schedules, Standards, Processes, Procedures, Project Resources, Requirements, Documentation, Quality Goals, Design, Code, Interfaces, Test Plans, Test Procedures, Technologies, Training, Management, Engineering.

Figure shows how data collection, analysis and management lead to the activities of Defect Prevention, Technology change management, and process change management.

Quantitative Process Management, which focuses on the process, leads to making process and technology improvements while Software Quality Management, which focuses pm quality, leads to preventing defects.