Consultation and analysis


Analysis is conducted and consultation is provided by experienced members of our business analysis team. Our analysts serve as either domain experts or general analysts.

A domain expert very well knows the subject area and analyses the requirements using previously acquired experience; in our case, this primarily involves projects in the area of banking.

A general analyst impartially determines and documents the requirements, thus progressively enhancing his knowledge in the subject area.

Our analysts' key capabilities include particularly the ability to:

  • conduct managed analytical discussions with the guarantor and customer;
  • convey the requirements from the perspective of the necessary aspects of system (functional) analysis;
  • comprehensibly document the requirements and all aspects thereof;
  • take responsibility for bilateral communication with customer and implementation team;
  • maintain the history and monitor the context of the project in the interest of adopting conceptual solutions;
  • support co-workers with other areas of specialisation (project managers, developers, technical-support personnel and personnel conducting application tests).


Where work processes are concerned, these are always to a significant extent subordinate to the nature of the project and requirements as well as to the customer's practices and corporate culture, deadlines and other important aspects of the project. We always strive to ensure the creation of useful project artefacts, as the objective is always the final product, not just consultation or analysis in and of itself.

For those customers who rather rely on our recommendations, we have the following process prepared to meet their needs:

  1. Definition of the focus and rules of the project: We help the customer to define what is expected from the project and to identify what must be done in order to achieve that. The output is usually the Vision, i.e. a document which, in the case of large projects, describes the available alternatives or multiple phases of the solution's progressive development.
  2. Determination and analysis of requirements: We compile a list of "business" requirements and, in cooperation with the customer, identify their benefits and priorities. Based on this list, we formulate a qualified offer, which sets forth estimates for determining the project's budget and milestones according to the anticipated labour intensity of implementing the requirements.
  3. System analysis: We identify the necessary functional properties of the software solution. The output has the form of functional specifications or, as the case may be, a single aggregate analytical model (depending on the customer's preference). In both cases, we use visual modelling in addition to a textual description. We describe all important aspects, such as related processes, functional properties, behaviour of the application (usage cases), screen designs, demands on the solution or, conversely, accepted constraints. The prepared documentation serves not only as the materials for designing the solution, but also as the basis for preparing materials required for testing as well as documentation for risk and change management.
  4. Solution design consists in transforming the conducted analysis into implementation requirements. During the course of designing the solution, the analyst collaborates with the software architect in order to achieve concurrence at the level of the fundamental technical properties of the solution. This guarantees a smooth transition from the analytical to the developmental phase of the project while significantly reducing the risk of delay and cost overruns.

Within larger projects, we conduct all phases of the analytical process (see above) iteratively. Analysis continues until the finished solution is handed over to the customer. On the other hand, we strive during the course of analysis to present a functional prototype of the solution, which serves as an illustrative example to help the customer more precisely define the necessary requirements.

Best practices

We proceed especially from RUP (Rational Unified Process) recommendations while adapting to any methodology preferred by the customer (in this respect, we have a wealth of experience gained from projects for customers - companies - bound to maintaining company standards).


With only slight exaggeration, it is said that an analyst's most important tools are a pen and paper, which of course applies only at the beginning of analysis. We use case tools (Enterprise Architect), drawing tools (MS Visio) and specialised tools (XML editors) as needed, as well as development tools on occasion (especially for verifying an analysis against the existing implementation where changes in the delivered solution are involved).


Windows Azure, Windows Server 2008