Our services
Documentation development

A distinctive feature of GOST 19 and 34 standards is a regulated sequence of information system development stages with a specific set of documents created at every stage. This allows us to determine project timing and cost more accurately. Application of these standards in government-related projects is often a compulsory requisition in the project contract.

Our knowledge and experience with documentation developing by the specified standards and use of competent technical language significantly reduces the risk having to do the work over again.

For example as a subcontractor we have successfully developed a Technical Requirements in accordance with GOST 34 up to 1500 (one thousand five hundred) pages, and a documentation kit for a Technical project volume of more than 4,200 (four thousand two hundred) pages. Our professional team can help you to significantly cut your costs and will increase the likelihood that your customer will accept the results from the first time.

Some of our clients, for example Gazprom and its daughter companies, due to the industry-specified Russian tradition, use SNIP 11-01-95 building code standard when developing documentation for automated information systems. So the documentation is developed in accordance with GOST 34 standard but it gets executed by SNIP standard.

When working with Ministry of Defence or Ministry of Internal Affairs in Russia among GOST 34 and 19 we also use military codes GOST 15 and 27. Occasionally, when working with projects of international significance or with research-related or scientific cases we use the appropriate GOST 7.32-2001.

Below are some examples of documentation types that we develop:

  •       Conception of Information System
  •       Survey reports
  •       Technical Requirements
  •       Detail Design and Technical project documentation
  •       Documents of stage Working Documentation (user manuals, instructions, admin manuals, trial methods, ets.)     
  •       International experience analysis in the framework of the given topic
  •       Functions and interactions regulations development           
  •       Operating instructions and manuals
  •       Calculating systems/subsystems reliability   

Information System modeling is one of the most effective ways to lower IT project risks. System models will clearly demonstrate to anyone what the system is designed to do and how the internal and external processes will work. The model will show in a graphic way any necessary requirements and important system components connections. It will serve to resolve any disagreements between the parties involved in the project at the early stages and will help understand all the major aspects of system's functionalities throughout.

This will result in a more precise budget evaluation, more accurate completion date estimation and the most satisfying final project outcome.

Our team has experience with business-processes  modeling IDEF0, DFD, UML, eEPC, BPMN and information modeling (logical & physical) according to IDEF1x, UML.

Among our tools we use the following:

  • IDS Scheer ARIS Toolset (еEPC, UML);
  • IBM Rational Rose (UML);
  • AllFusion ERWin Data Modeler (IDEF1X);
  • Microsoft Visio (IDEF0, IDEF3, DFD, EPC, UML, BPMN);
  • Enterprise Architect (UML) and others.

The choice of any one modelling language is based upon your demands and project specifics.

Business analysis is the process of identifying how business works, business needs and determining solutions to business problems. The process will show areas that need improvement and places where use of resources may be reduced. It will help to optimize functionality, cut costs, increase efficiency and apply any required changes in the most effective way.

Industry experience tells that business-processes analysis almost always is closely connected with analysis of the existing business information systems. This allows real-world visual representation of how the business is operating. The representation will clearly show all the business functions and along with it a list with optimization suggestions. This method can be used to identify all the cases where processes can be automated or if any organizational changes are needed.