Skip to content

OUR WORKING PROCESS WITH CLIENTS

In order for us to best serve our clients and to provide satisfactory service, we follow specific process that helps us better understand client's needs and requirements.

  • one (1)

    Initial contact with client

    This is our first contact with our potential client. We conduct an introductory conference call usually over Skype, with a client and our team, to align values and expectations from both sides. At this state we begin to formulate what is required and how we can help. Usually after all parties are happy with the initial proposal, we sign the contract and move to the discovery phase.

  • two

    Discovery phase

    Most projects that use innovative technology such as Artificial Intelligence will require this stage to be carried out before production. During this phase our experts (business analyst, project manager, tech lead, etc) will work closely with you to conduct an in depth analysis of your business, identify its strengths and weaknesses, conduct statistical comparisons and determine the processes that are subject to reconstruction.

    Discovery phase let's us clarify the scope of the project in detail. All nuances of the development, limitations and best direction will be evident after the discovery phase. For projects with unclear or non-functional requirement discovery phase is a must.

  • three

    Software Requirements Specification (SRS)

    A software requirements specification is a complete description of the behavior of the program that a client wants us to develop. It includes a number of options for interaction between users and software.

    Customer requirements are collected during the discovery phase and presented in the form of user stories and use cases.

    Further Vision and Scope document are developed. It defines what the customer or company has in mind as well as describes the work process necessary to reach that vision. It also defines the boarders of the project, prioritize the functional requirements, and assess the profit from the project implementation.

    The functional requirements obtained from the use cases and the Vision and Scope document are further presented in suitable UML diagrams.

    Finally the functional requirements added by non-functional requirements are formalized in Software Requirements Specification (SRS). It includes the purpose, scope, functional and nonfunctional requirements, software and hardware requirements of the project. In addition to this, it also contains the information about environmental conditions required, safety and security requirements, software quality attributes of the project etc.

     

     

     

  • four

    Proof of Concept

    This is where modeling of the software is done. 

    • Type of compilation is decided and selected
    • What type of programming will be used etc.
  • five

    Maintenance and Debugging

    At this stage we conduct in depth quality assurance and make sure that the live software works flawlessly. We make appropriate optimizations, tweaks, remove bugs and make fixes.

NEED HELP WITH YOUR PROJECT?

If you are not sure, we can help you with you next project's specifications & requirents! Get in touch with us and our Business Analyst will contact you.

share

Get help with your project requirements

Enter your details below and our business analyst will get in touch with you to discuss your project.

Would you like more information about our products and services?

Our product manager will be happy to assist you and answer your questions. Fill out the form with your details and we'll get back to you as soon as possible.

tatsiana-product-manager-1

Product Manager

Tatsiana

Ask Your Questions