Offshoring is firmly entrenched in the Bay Area and that's not necessarily a bad thing. It was among the conclusions of a major study by Silicon Valley Network, the Bay Area Eco. Forum and the Stanford Project on Regions of Innovation. "Offshoring is here to stay. We're whistling in the wind if our approach is how to make it go away," said Russell Hancock, CEO of JV: Silicon Valley Network.
   
Quality Assurance Succes
New PM -> Ege Sümerol:
New office place for
Oportunities at Troysis
More >>

Quote <<
Reference Contact
<<
Standart Docs
<<
Brochure <<
Sample Code
<<
CD Presentation
<<

Quality Assurance

Methodology

We are stepping over the phases within our methodology as sighted on left. These phases - more or less regarding the business needs - are the milestones of our methodology for quality assurance on

  • On-time completion of the project,
  • Delivery of a high-quality system meeting business requirements,
  • Development of a flexible, ‘easy to use and modify’ system.

Our software development house also proved its success in developing projects with small time-boxes by using Agile Methodologies that use Parallel Processing, Extreme Programming and Fourth Generation (4GT) Techniques

Testing Standards

We make a choice out of a template pool in order to specify the appropriate standards dynamically for the testing of the particular project. Therefore, each project has its own testing standards regarding the functional requirements and business logics. For each project we dynamise these standards by configuration.

QA team use checklists to score the developed project.

We use below listed testing techniques :

Black-Box Testing : This may be called as business logic test. The QA team act as users of the application which is developed.

White-Box Testing : After test team’s analyzing the code, they try hazardous actions considering the security and raw users. Security testing is part of the testing plan.

Regression Testings :
Our testing team insistently try to find bugs. When the testing team find quality problems and/or bugs, they reject the developed application and send it back to the development team. After the problem fixing, the whole testing phase restarts for the whole application. This retesting process is what we call regression testing.
Integration testing :This test is used in order to examine whether integrated components of an application or of a distributed system function together properly.

Soak Testing :
This technique is used for the examination of the stability and uptodateness of the software application.

Unit Testing :
Checking of Coding Standards, DB Standards, FrameWork Standards

Performance Testing :
We use load, stress, installation and performance testing.

Communication

We use innovative communication technologies such as :

  • Online Project Workspaces
  • Mail Records
  • Instant Messaging
  • Conference Calls
  • Online Project Daily Report
  • Face2face Meetings

Documentation

Functional requirement, project management and testing plan documentations are used for each project. All quality standards are tested throughout checklists built by relevant teams.
Each project member reports completed daily tasks through which QA team members controls the phases of the testing process. Reports are archieved in order to handle backtracking when needed.


 

Copyright 2004 - www.troysis.com - All Right Reserved
Terms Of Use