|
[
Technology
|
Project Management
|
Process & Methodology
|
Quality
]
Quality Process
Quality is more than just conformation to requirements of software. The quality we aim to achieve is to exceed expectations of end users for each software product or service we provide.
At WebVirtue Software Solutions, we follow Software Quality Assurance (SQA) methods that adhere to the quality assurance at every phase of SDLC (Software Development Life Cycle). A quality control checklist is developed for all phases of SDLC. We aim to provide quality and consistent results through automated process that have been tested over time. Purpose of the SQA Plan is to establish a uniform Web / Software Development Process, which is applicable throughout the software development life cycle.
Quality is like improving yourself up to endless limit. We always aim for ongoing relationship and we believe that the only way to satisfy client is by delivering better quality. We need to constantly improve our deliverables to match the increasing expectations of our clients. Stringent quality checks ensure that the quality of the software development work delivered is superior by all standards.
Checklists are prepared at various phases of SDLC (Software Development Life Cycle) . The checklists prepared at various levels are as follows:
 INITIAL CHECKLIST is filled by PM \ PL at the end of requirement analysis phase and ensures that all the requirements are complete and well understood, before the development begins.
TEST CASES In the Project Planning stage Test Case Reports are created by QA.
DATABASE CHECKLIST is filled once the database design is complete and helps to know whether the database conventions were followed for the project database.
DEVELOPMENT CHECKLIST is used to ensure that the development or coding is completed according to the requirements, design specifications and Style guide is followed during development.
QA CHECKLIST is filled at the end of testing phase and ensures that the project as a whole has been reviewed by the QA.
RELEASE CHECKLIST confirms that the project is organized and all the project documents are available.
Testing And Debugging
All components of every web/software application, goes through a cycle of rigorous testing and debugging phases before release for the use of the client. These testing phases will consist of:
Functional testing - which occurs after a major module or interface form has been coded,
Build testing - which occurs after all modules and forms have been coded and accepted as functional, and after they have been built to interact with one another,
System testing - which occurs after the system is complete.
We see testing as an integral part of the development process and a means to assure a quality product. All functions, modules, and components must meet or exceed the functional specifications in order to pass testing. Failure in any testing phase requires the documentation of the defect, debugging and re-testing to ensure that no new product defects were introduced into the system. Once determined error free, the application will then be provided to the client for acceptance testing.
|
