Many companies at some point come to internal informational chaos situation. Disparate IT systems with poorly described functions and unclear support procedures take more and more attention, resources, and increase risks of loss of critical business information. Good response for that problem would be an IT audit of existing systems to find and eliminate rarely used programs and data, and optimize support and development resources for business critical systems. Main results of such projects are documents describing applications functions and architecture, support specifics and other information needed for system improvement and support. Customer also gets recommendations on possible optimization of IT infrastructure, systems replacement or integration, technical support outsourcing.

• Interviewing user and technical personnel
• Analysis of existing documentation and (if needed) source code
• Complex system definition: users, criticality for business, integrations, existence of source code, documentation and other artifacts
• Prepare maintenance documentation (if needed – in compliance with country-specific standards like GOST or others)
• Provide recommendations on IT infrastructure and its support resources optimization

Definition of project goals, key business users, and their tasks and, as a result, system functional borders considered the key project success factors. When we develop complex systems with many roles and high requirements to user interface, we also develop mockups for user forms. This allows us to have common understanding with the customer of the system to be built and to specify requirements to its key functions. After system functional borders are defined everything that is needed to design is describing main system components, their interactions and system deployment plan (diagrams in UML, BPMN or other notation).

• Subject analysis and requirements collection
• Development of functional and technical specifications
• Development of mockups of screen forms
• Solution architecture design: system architecture and components, classes and interfaces, their interaction and calls sequence etc.

When developing B2C applications, both Web and mobile, well-designed UI greatly increases chances for the system to be really client-oriented and, as a result, successful. At the same time B2B applications and internal corporate systems more and more often require detailed description of UI at requirements collection phase. This is caused by the requirement to use company brandbook styles and the need to understand what certain functions will look like on screen forms.

• Development of detailed graphical design for corporate systems and portal solutions
• Graphical responsive design for mobile devices
• Solution graphical design for touch devices: kiosks, POS terminals etc.

Testing and quality assurance concepts are quite extensive and include both different types of software and hardware testing and various tools for automating and supporting this process.

• Functional testing
• Stress testing
• Using automated testing tools
• Mobile applications testing
• Testing of specialized devices: kiosks, POS terminals, auto-attendance terminals etc.
• Adaptive testing considering regional, language and other specifics of the system being tested