Initial Development plan

  • Create a visual source safe database(Microsoft Visual Source Safe)
  • Create logins for each user
  • Assign client access to VSS database
  • Proceed with the development proce
Initial Development Plan

The Team Leader is responsible for assigning each Module to Developers.

We apply a module level development process for every project. We run several of these modules simultaneously for better results.

Once a certain module is completed it will be analyzed by the Quality Assurance team.

After Testing, the module is revised again by the same developer to ensure that it is bug free, the module will be assigned back to the tester to recheck on fixed bugs.

  • At the end of each day we take a backup of the VSS Database and save it on another location
  • We ensure we provide a higher level of fault tolerance. In case we lose our data due to a server crash etc. we are still able to recover them quickly.

Illustration of VSS process

Illustration of VSS process

Through VSS we achieve

  • The latest version of the recourse (.aspx/.cs/.css etc)
  • Reduced the conflicts of two users updating the same file simultaneously.

Database Development process

Database Development process

Interfacing with the Web application and the Database Application

We develop web applications according to the 3-tier architecture. Therefore the application layer and database layer is isolated with each other providing a higher degree of modularity.

Illustration of the architecture

Illustration of the architecture

Testing Process

  • Testing is Carried parallel with the development process.
  • Tester reads the SRS (System Requirement Specification Document) and develops a test plan.
  • Using the test plan, developers create use cases.
Testing Process
  • We use a separate testing server for the web application
  • We use a testing Database server for testing process. The tester is given the freedom to input/remove data from the database as he/she wishes.
Testing IP

When we publish the test release we make sure that we produce a relevant versioning. Eg- Versioning is maintained by three separated areas like xxx.xxx.xxx

  • The application undergo with smoke testing where QA tests the basic functionality of the page/form (check whether values are getting saved with the database)
  • Testing is done for both Functional testing side and Interface testing Under Interface testing, tester checks the page/form for the look and feel. They check for spelling, Grammar, contents and readability.
  • Under functional testing tester check for the internal functionality
  • Initially testing is based on module basis. After module testing, the whole application is tested for the overall performance and the continuous flow of the web application.

Bug Reporting

  • When a bug is found it's been reported by the relevant tester, we use bug tracking softwares for this process.
  • Bug is directly assigned to the team leader. The Team leader is responsible for assigning the bug to a developer.
  • Developer fixes the bug and assigns it back to the tester to test it again.
  • If testing proves that bugs still persist, the tester assigns the module to the team leader for appropriate action

Bug Life Cycle

Bug Life Cycle

Load testing

Allow multiple users to access the site concurrently and measure the performance and the speed

Implementation phase

Initially we will develop a release management plan

This plan includes

  • Location for the web application to be hosted(Application server)
  • Location of the Database server
    Some clients agree to keep the database and the application server in the same server.
  • Develop a policy for uploading .dlls
    This policy indicates when to upload a dll, How to upload the dll, who is responsible for uploading .dll, renaming .dlls

Contact us to get a custom quotation