Services > How we work
development of all our projects is divided into four RUP
phases, starting with an inquiry and ending with a working
system, approved by the customer. The purpose of having
a structured and well-organized System Development
Process (SDP) is to have a common understanding
of how projects are run and to ease the introduction of
new team members internally. In a fast growing and geographically
distributed company like Reli-e-Marg, this is an important
prerequisite for success.
We constantly update and revise our systems development
processes since we feel that our strategies should evolve
as the competence, experience and surrounding methodology/technology
- On-time completion of the project
- Delivery of a high-quality system meeting your business
- Development of a flexible, modular, easy to use and
scalable system and
- Fast and easy additions of plug-ins, new features,
Phase 1 — Inception:
The good idea: specifying the end-product
vision and its business case, defining the scope of the
When we get your inquiry, we investigate it, ask for
additional information or details, and then prepare an
overview of all your requirements. We then give you a
proposal with a rough estimate as well as a preliminary
Project Plan. We can also accept a specification prepared
by you, which we will study thoroughly to ensure that
it exactly reflects and meets your requirements and needs.
Phase 2 — Elaboration:
Planning the necessary activities and required
resources; specifying the features and designing the architecture
Once we have received your approval of our preliminary
proposal, we conclude a contract with you and create an
exact Specifications and Project Plan.
- A detailed definition of the system along with system
processes and dependencies is made during this phase.
Key technology decisions are made in conjunction with
the estimates and schedules.
- We analyze your needs from a software engineering
and technology perspective. Keeping the time frames
and strategic needs in mind we develop a complete engineering
plan for you that will take care of your current and
- A high level design of the system is made taking all
the above 'discoveries' and 'definitions' into account.
We also address the high level needs of scalability,
reliability and ease of maintenance in this phase.
Phase 3— Construction:
Building the product and evolving the vision,
the architecture, and the plans until the product--the
completed vision--is ready for transfer to its users'
Those parts of the system that face most uncertainty
and ambiguity are rapidly prototyped during this phase
and decisions made through client interaction. The UI
and high technical uncertainty portions that threaten
the execution of the project are addressed in this phase.
During this phase the system and technology architecture
for the product is developed. When you approve the results
of the previous stage, we work out the Specification in
all details, develop the Test Plan, and agree to the Acceptance
Testing Criteria with you.
- Programmers begin coding using the Specification.
- Testers develop test cases and test scripts using
the Test Plan, test the system and verify that it operates
according to the Specification.
- Designers develop necessary elements of the user
interface and make it ergonomically correct.
- Technical Writers create necessary user and system
documentation. During the construction stage, the performance
of team members is monitored, project progress is reported,
changes requested and defects discovered in the software
Phase 4 — Deployment:
Making the transition from the product to
its user's community, which includes manufacturing, delivering,
training, supporting, maintaining the product until the
users are satisfied.
The system is installed in test mode, required data conversions
are made and end-users are trained. When you accept the
system, it is installed in production mode. We will also
provide maintenance for the system if required.