Software quality assurance at PlexiTech involves the entire software development process - monitoring and improving the process, making sure that any agreed-upon standards and procedures are followed, and ensuring that problems are found and dealt with. Software quality assurance at PlexiTech is oriented to 'prevention'.

How is Quality Assurance implemented?

  •   Testing involves operation of all systems or applications created by PlexiTech under controlled conditions and evaluating the results. Project teams include a mix of testers and developers who work closely together, with overall QA processes monitored by project managers.
  •   Verification typically involves reviews and meetings to evaluate documents, plans, code, requirements, and specifications. Validation typically involves actual testing and takes place after verifications are completed.
  •   An inspection is typically held using a document such as a requirements spec or a test plan, and the purpose is to find problems and see what's missing, not to fix anything.
  •   Solid requirements are established - clear, complete, detailed, cohesive, attainable, testable requirements that are agreed to by all players.
  •   Realistic schedules allow adequate time for planning, design, testing, bug fixing, re-testing, changes, and documentation; personnel should be able to complete the project without burning out.
  •   Good internal design is ensured by software code whose overall structure is clear, understandable, easily modifiable, and maintainable; is robust with sufficient error-handling and status logging capability; and works correctly when implemented.
  •   Insuring that communication is clear and that information/documentation is available and up-to-date.

PlexiTech uses the above methods to ensure that quality software is bug-free, delivered on time and within budget, meets requirements and/or expectations, and is maintainable.