 |
 |
 |
 |
|
|
|
|
|
|
| |
|
|
|
SOFTWARE
SOLUTIONS |
Think IT Services has a standard
proven methodology and development process. The development
process is tailored depending on the complexity and magnitude
of the requirements for each project. The generic development
process would consist of |
System
Study and Requirements Analysis - Sign off
Interact
with client users to get requirements
Requirement document
showing requirements in a structured manner and
allows easy referencing.
Study of
technical issues, if needed, with prototypes to address risks
/ feasibility.
Dummy screens with
navigation to clarify exact requirements
Development of
test plan.
Design
High level
design
Identifying logical components of the system and the
technologies to use
Detailed design
Details of
APIs and rough code structure for important
functions
Development / Coding and
Testing
Implementation of the specifications
and testing of the functionality.
Integration
testing
Integration of various modules and
testing across modules
System
Testing
Testing across different Operating
environments (OS, software platform
etc.)
On-going support based on customer
agreement |
Think IT Services strives to provide each customer with very high
visibility into their project, with deliverables at each
stage. Most of the above steps (1-6) end with reviews and
feedback corrections to ensure quality throughout the process.
We try to eliminate all technical uncertainties from the
project up-front, in order to make it as linear as
possible. |
| |
| Software Quality Assurance (SQA) Process
: |
Think IT Services's has a strong
SQA team that reviews and verifies that the processes within
and across projects are applied as per Think IT Services's
procedures. It also provides management with appropriate
visibility into the process being used by the software project
and of the products being built by providing metrics and
quality factors. Quality factors are characteristics, which a
software product exhibits, that reflect the degree of
acceptability of the product to the user. SQA gives process
metrics as well which help tune the processes. SQA audits that
the process to ensure compliance to the client's requirements
during the project's start-up phase, implementation phase and
end phase. |
| |
| Quality Control
Process: |
| |
The
test team will begin designing their detailed test plans and
test cases, as the development team is designing and coding.
Defect management system will be used to track the defects.
Testing consists of several rounds of running test cases on
builds and logging defects for correction and bug fixing.
Based on the acceptance criteria defined, the product is
finally released to the customer.
A test bed will be
prepared by developing team. The development team will be
responsible for installing the partial new builds into the
existing structure of the system test environment, and
updating the test bed if necessary. Once the build is dropped
to QA by the development team, a series of testing, called the
basic functionality testing, will be run to ensure that the
shipment from development is in a state that is ready for
testing. The test cases designed for each module will be
executed here.
|
| |
Code review
Before
releasing to testing, the code will be reviewed at the
appropriate stage during development to detect bugs earlier in
the lifecycle.
Unit Testing
Approach:
Individual Unit of the software is tested
in isolation from other part of program. Black box functional
testing approach will be followed in this stage. The user
interface will be reviewed for adherence to GUI guidelines and
completeness.
Integration Testing
Approach:
The interfaces and the inter
process communications are tested mainly. This way the program
units are ensured that they communicate to each other.
Internal, external interfaces, with request and response are
to be rested.
System Testing
Approach:
The aim of System testing is to
ensure that the developed system adheres to functionality
defined in the Requirements Analysis Document.
Black Box
testing approach will be followed for the System Testing. The
approach will be more positive in System Testing by testing
what a normal user will do with the application. The
environment for System testing will be a replica of the
Production
environment(s).
|
Acceptance
Test:
The client shall provide an acceptance test
plan, after completion & submission of requirement
analysis document by Think IT Services. This would typically
include test cases, expected results, conditions such as the
number of medium and low priority bugs found. If these are
cleared, the release is considered as completed.
On
submission of the planned releases, the client shall carry out
the test as per the acceptance plan. A full test report must
be delivered detailing test coverage and bugs found. On the
first release high priority bugs will be fixed and the lower
priority bugs documented. On further releases the rest of the
bugs will be cleared.
|
| |
| |
|
" Customer Satisfaction
through Total Ownership
Experience"
|
|
|
| |
|