Application Development Methodology- Titan Revolve
We follow our in-house project implementation methodology
to deliver our solutions.
We call it “Titan-TeamTrack” methodology. The following
is an outline of Titan-TeamTrack methodology.
During the Analysis Stage, Titan’s project manager works
with its clients' project manager to understand the
goals and objectives of the project. We would start
with the customer as the focus, their needs and the
functionality required for each and every phase of the
project. Simultaneously, a Data Model of the solution
would be developed to map the application Design before
the actual development.
A prototype of the solution would be developed using
a very small aspect of the project to show the proof-of-concept.
During the requirement analysis of the proposed system,
we would identify all the Common User Interfaces (CUI)
and the Business Process Logic (BPL) and develop these
as reusable objects during the development of the application.
Then based on the functionality of the application we
will develop the application Framework and its individual
components in such a way that it is scalable in the
future to accommodate more features maintaining the
same look and feel for the end user.
During this stage, the Business Analyst creates a detailed
step-by-step project specifications documentation for
the development team to final design UI screens, application
actions and logic.
Development and Testing
The Development team, follows the project specifications
and assembles each modules after unit testing and then
again after integration testing. The final code is then
tested for various iterations for data integrity, logical
integrity, regression and stress testing. Any and all
defects are tracked and fixed, and code goes thru the
same testing all over again to be certified by the testing
team to move to final production and implementation
Different Application Modules are assembled for the
final integration and testing. The application is again
tested for using the replicated data (or the required
extracted data) of the existing systems involved, if
there is no such data available, then various test cases
and data will be created to check the data integrity
and functionality of each of the modules assembled.
The system would be then rolled over to go into production
with limited pilot users to test it for the following:
Load balancing on the application databases
Monitor the users feedback for overall user
Identify any production bottlenecks
Application bug fixes passed thru after testing
Any potential systems or performance problems
Go-Live and Support
After the system meets the required metrics as outlined
by the projects requirements and a final user acceptance
is signed, the system is set for production. End user
training is conducted simultaneously with a predefined
post implementation support agreement.
For more information please feel free to submit your