An independent Quality Assurance (QA) is standard in the industry, to ensure the quality of software. We provide not only testing itself, but a complete Quality Assurance services. |
|
| Quality AssuranceQuality Assurance is an entire set of management and technical activities that ensure the product matches all requirements. In fact, QA is paramount at XTLabs, Inc. and everything we do comes down to Quality Assurance. The well-known diagram below best illustrates our approach towards improving our process and towards a constant increase in quality. Plan stepAll jobs on the project, on every level, start with planning. Everything begins with envisioning, specification on various levels, and plans. Do stepHere we have a defined policy on how things should be organized. We follow the basic principles of the Rational Unified Process (RUP) from Rational Technologies. This is a de-facto leading standard for software development methodology, employed by the best companies in the industry. Companies like Microsoft and IBM are partnering with Rational to make use of RUP and create joint products supporting RUP. Check stepThis step is about checking to ensure whether what has been done meets planned requirements and specifications. Checking is done in various areas:
The "price-time-functionality equation" is a powerful metaphor. Failing to set all three corners of this triangle on firm footing can mean high project risk. We carefully discuss each requirement and business constraint with the client to make sure we arrive at the most desirable 'triangle' for the client. Software Quality Control is a crucial part of the process. The testing facility (used in the first step) allows us to test our applications on various platforms, such as Windows, Windows 2000, Windows XP, Macintosh, and in UNIX -family (Linux, FreeBSD etc.) environments.
Act stepThe ACT step is about analyzing the results of the previous step (CHECK) and making appropriate decisions on how to improve the quality of the process or product. • Coding A programmer needs to write a procedure. First, he plans the algorithm and defines the input and output parameters. Next, he writes the code - the "DO" part. Checking whether the procedure works correctly under various circumstances is the "CHECK" part. Subsequently, he decides whether this procedure should be included in the code repository. • Management A project needs to be completed. First, the specs are written, the team assembled, and resources are allocated. Next, the development begins. Last of all come testing and bug-fixing, and only then the project is analyzed and documentation goes to the "knowledge base." |
© 1999-2024 XTLabs, Inc. All rights reserved. |