This version of the page http://www.eleks.com/page/54/Methodology.html (0.0.0.0) stored by archive.org.ua. It represents a snapshot of the page as of 2009-11-16. The original page over time could change.
ELEKS Software: Methodology

How We Work

Our Approach

Methodology

Project Initiation

Communication

Risk Management

ELEKS TeamPro

Quick Links

  • Request for Proposal
  • Request for Information
  • Contact Us
Home / How We Work / Methodology

Methodology

We strongly believe that one size does not fit all, so we don’t work with one particular methodology, but are open to adopting the approach that would fit specific project and customer needs best of all. That is why in our company you can find application of methodologies ranging from formalized RUP to flexible XP.

We use an agile RUP-based process of project implementation that allows us applying iterative and incremental approach to development delivering incremental releases over time. The project lifecycle is based on four consecutive phases:

Inception

During the inception phase we identify high-level requirements for the system, so that the scope may be formulated and project resources obtained.  Data modeling and conceptual modeling are performed at this stage as well, if necessary. 

Elaboration

During the elaboration phase the goals are to analyze the main body of requirements, to identify system architecture, and to verify that the architecture works via an end-to-end technical prototype. Usually business architects are involved at this stage. 

Construction

During the construction phase we build a working system that is ready to be put into production. Development proceeds in iterations, during each of which a subset of the requirements is implemented via specific analysis models, design models, source code and test cases. Development artifacts evolve over time as well as database and other models. Project models can be updated when new requirements appear.

Transition

During the transition phase our goal is to user-test the system to ensure that it is ready to be put into production, to make needed corrections, and to actually deploy the system.

 

During almost each of these phases we use our own electronic database system – TeamPro. It is aimed at tracking ongoing project activities, managing issues raised by customers and team members, carrying out general team performance review, and processing department/project/employee work reports. The TeamPro system also allows real-time staff-load management and rescheduling project activities to gain maximum performance results and quality and to deliver work on time.

 

In addition, we offer our clients support and maintenance services. From the customers’ perspective the supporting stage is the most important one, because many things which are either impossible or unlikely to be foreseen at the implementation phase may happen during the inception period of the system operation.