"The hardest single part of building a software system is
deciding precisely what to build" -Frederick P. Brooks
We build "solutions" not just software ...!
At Team Inertia Technologies, we believe that a success of a software
project can be measured only in relation to the benefits it gives to the
clients, the way it brings in efficiency in the operations, the better
co-ordination it offers between the interest groups and the low Total
Cost of Ownership (TOC) and finally... sustainability
of the software in the long run.
Agreement on a "solution" is arrived at after
numerous interactions with the users to gather inputs and a first hand
'feel' of the client's workflow. The 'Idea' is polished
by internal brainstorming sessions by the team members where alternative
options are explored to take care of a certain challenge. Most often,
the idea becomes wider in scope giving maximum benefit to the client in
terms of efficiency and cost.
The expertise, gained over the years building medium to large applications
for a host of clients have helped us in developing a software
development model conductive to ensure maximum participation
from the users during the i2i (Idea to Implementation
as we call it). The emphasis on the total quality management
of the entire development process have resulted in time tested systems,
manageable without programming intervention, earning us 'tough' customers
like the Indian Navy who have always come back to us
for customized software requirements in diversified areas.
The project development process is divided into 9 functional stages.
• Project Introduction (Idea)
This phase includes the initial meetings and discussions with the client(s).
Here, the purposes of the project as well as the client’s idea of
its scope and limitations are discussed.
• Feasibility Study
This phase includes a thorough study by the analysis team to ascertain
the feasibility of developing the project in question. Some of the questions
=> Does the client really need this application?
=> The cost v/s benefit to the client.
=> Can this project be completed and implemented in the time mentioned?
Only on procuring favorable answers to the above questions the project
Once the project enters the analysis stage, a thorough study is done of
the project to be developed. A plethora of material is researched, from
client specifications, to the specifications from the computer operators/
users who will actually be working on and using the system. Hard copies
of currently maintained documents and reports are also looked at.
Once the planning is initiated, careful thought is given to project deadlines,
overall scheduling, and module delegation. This phase is basically about
ensuring the logistics are in place before the coding phase begins.
• Design (User Interface and Flow)
This phase includes further interaction with the clients and the computer
operators/ system users themselves. Their points of view, opinions and
suggestions are carefully noted and discussed. Finally much thought and
discussion is given to how the proposed flow can be optimized and simplified.
Finally the coding phase begins! Here programmers, having been thoroughly
briefed about the project, its scope, schedules and deadlines, can begin
developing the source code to translate all the planning and analysis
done so far into tangible code.
Once the development of the project/module is completed, the testing phase
begins. Typically, testing is first carried out by the project developer(s),
followed by another round of testing by personnel who haven’t been
involved with the coding of the project.
• User Feedback and improvements
Upon successful in-house testing, the project/module is then implemented
at the client’s premises, where it is further tested and suggestions
or modifications are offered, as many times as deemed necessary.
Intallation of the system at the user premises, incorporation of the legacy
data if necessary, training of the user groups and initial monitoring
of the software performace and database fine tuning.
here for Software Development Portfolio