Specifications and documentation

Specifications and documentation

Specifications and documentation

Specifications and documentation

Specifications and documentation

We will create a complete SRS for development, which includes User Story, ACL, functional requirements, test cases, and UI requirements.

We will create a complete SRS for development, which includes User Story, ACL, functional requirements, test cases, and UI requirements.

We will create a complete SRS for development, which includes User Story, ACL, functional requirements, test cases, and UI requirements.

We will create a complete SRS for development, which includes User Story, ACL, functional requirements, test cases, and UI requirements.

We have learned to quickly immerse ourselves in the task: in just 1-2 days we get an understanding of the project and can present a rough structure. Here are the results:

Example of pre-project analysis result: mindmap, structure, roles

Cmd / Ctrl + Scroll to change the scale

show demo

right here

Example of the pre-project analysis result: CJM

Use Cmd / Ctrl + Scroll to zoom in or out

show demo

right here

We have learned to quickly immerse ourselves in the task: in just 1-2 days we get an understanding of the project and can present a rough structure. Here are the results:

Example of pre-project analysis result: mindmap, structure, roles

Cmd / Ctrl + Scroll to change the scale

show demo

right here

Example of the pre-project analysis result: CJM

Use Cmd / Ctrl + Scroll to zoom in or out

show demo

right here

We have learned to quickly immerse ourselves in the task: in just 1-2 days we get an understanding of the project and can present a rough structure. Here are the results:

Example of pre-project analysis result: mindmap, structure, roles

Cmd / Ctrl + Scroll to change the scale

show demo

right here

Example of the pre-project analysis result: CJM

Use Cmd / Ctrl + Scroll to zoom in or out

show demo

right here

show demo

right here

show demo

right here

show demo

right here

Initial Specification

In order to reach a common understanding of the project, we will create an initial specification for the project, in which we will define a list of user roles, the functionality of each role, the list of main sections, and define the main entities in the project and their relationships. Often, the client comes with their initial specification, which speeds up the start of work.

Начальное ТЗ


Flowcharts and Logic

We refine the initial specification: we describe in more detail the scenarios of the system's behavior and the user in different situations, so as not to miss anything. We use flowcharts, mind maps, and diagrams, which represent the data visually and are convenient for discussion.

Блок-схемы и логика


Business Processes and BPMN Diagrams

BPMN allows us to describe business logic in a language that is understandable to all project participants. It is understood by the development team (business analysts, programmers, product managers) and the client side (owner and employees).

Бизнес-процессы и BPMN-диаграммы


Access Rights (ACL)

We create rules for dividing access to sections and functions for each role, so that the development team correctly implements ACL policies (Access Control List). This will immediately organize the architecture and role model correctly, taking into account all the sections and functions of the system.

Права доступа (ACL)


Functional Requirements

The document includes a list of modules. The main functions are described in each module. For each function, we write requirements in the format of User Story, with technical clarifications where necessary.

Функциональные требования


Functional Test Cases

For the described functionality, we create test cases in Gherkin language - a human-readable language for describing the behavior of the system in a format that allows for future implementation of automated tests or manual testing of functionality.

Пример описания тест-кейсов


Notifications and Email

We describe in the requirements the system triggers for notifications for each role, create email templates with texts, describe interface errors, and pop-up tooltips.

Пример дизайна email уведомлений для проекта


Resulting Specification

We do not set the task of creating an encyclopedia for the project, the average size of such a specification is several dozen pages (50-60). At the same time, it is a summary of all agreed project requirements from different perspectives: business logic, user behavior, technical constraints, and design requirements. Our specification has the necessary level of detail to start development and is prepared relatively quickly (4-6 weeks). Example project specification.

If you need to create a technical specification for the project, write to us on Telegram. We will be happy to help.

Initial Specification

In order to reach a common understanding of the project, we will create an initial specification for the project, in which we will define a list of user roles, the functionality of each role, the list of main sections, and define the main entities in the project and their relationships. Often, the client comes with their initial specification, which speeds up the start of work.

Начальное ТЗ


Flowcharts and Logic

We refine the initial specification: we describe in more detail the scenarios of the system's behavior and the user in different situations, so as not to miss anything. We use flowcharts, mind maps, and diagrams, which represent the data visually and are convenient for discussion.

Блок-схемы и логика


Business Processes and BPMN Diagrams

BPMN allows us to describe business logic in a language that is understandable to all project participants. It is understood by the development team (business analysts, programmers, product managers) and the client side (owner and employees).

Бизнес-процессы и BPMN-диаграммы


Access Rights (ACL)

We create rules for dividing access to sections and functions for each role, so that the development team correctly implements ACL policies (Access Control List). This will immediately organize the architecture and role model correctly, taking into account all the sections and functions of the system.

Права доступа (ACL)


Functional Requirements

The document includes a list of modules. The main functions are described in each module. For each function, we write requirements in the format of User Story, with technical clarifications where necessary.

Функциональные требования


Functional Test Cases

For the described functionality, we create test cases in Gherkin language - a human-readable language for describing the behavior of the system in a format that allows for future implementation of automated tests or manual testing of functionality.

Пример описания тест-кейсов


Notifications and Email

We describe in the requirements the system triggers for notifications for each role, create email templates with texts, describe interface errors, and pop-up tooltips.

Пример дизайна email уведомлений для проекта


Resulting Specification

We do not set the task of creating an encyclopedia for the project, the average size of such a specification is several dozen pages (50-60). At the same time, it is a summary of all agreed project requirements from different perspectives: business logic, user behavior, technical constraints, and design requirements. Our specification has the necessary level of detail to start development and is prepared relatively quickly (4-6 weeks). Example project specification.

If you need to create a technical specification for the project, write to us on Telegram. We will be happy to help.

Initial Specification

In order to reach a common understanding of the project, we will create an initial specification for the project, in which we will define a list of user roles, the functionality of each role, the list of main sections, and define the main entities in the project and their relationships. Often, the client comes with their initial specification, which speeds up the start of work.

Начальное ТЗ


Flowcharts and Logic

We refine the initial specification: we describe in more detail the scenarios of the system's behavior and the user in different situations, so as not to miss anything. We use flowcharts, mind maps, and diagrams, which represent the data visually and are convenient for discussion.

Блок-схемы и логика


Business Processes and BPMN Diagrams

BPMN allows us to describe business logic in a language that is understandable to all project participants. It is understood by the development team (business analysts, programmers, product managers) and the client side (owner and employees).

Бизнес-процессы и BPMN-диаграммы


Access Rights (ACL)

We create rules for dividing access to sections and functions for each role, so that the development team correctly implements ACL policies (Access Control List). This will immediately organize the architecture and role model correctly, taking into account all the sections and functions of the system.

Права доступа (ACL)


Functional Requirements

The document includes a list of modules. The main functions are described in each module. For each function, we write requirements in the format of User Story, with technical clarifications where necessary.

Функциональные требования


Functional Test Cases

For the described functionality, we create test cases in Gherkin language - a human-readable language for describing the behavior of the system in a format that allows for future implementation of automated tests or manual testing of functionality.

Пример описания тест-кейсов


Notifications and Email

We describe in the requirements the system triggers for notifications for each role, create email templates with texts, describe interface errors, and pop-up tooltips.

Пример дизайна email уведомлений для проекта


Resulting Specification

We do not set the task of creating an encyclopedia for the project, the average size of such a specification is several dozen pages (50-60). At the same time, it is a summary of all agreed project requirements from different perspectives: business logic, user behavior, technical constraints, and design requirements. Our specification has the necessary level of detail to start development and is prepared relatively quickly (4-6 weeks). Example project specification.

If you need to create a technical specification for the project, write to us on Telegram. We will be happy to help.

Initial Specification

In order to reach a common understanding of the project, we will create an initial specification for the project, in which we will define a list of user roles, the functionality of each role, the list of main sections, and define the main entities in the project and their relationships. Often, the client comes with their initial specification, which speeds up the start of work.

Начальное ТЗ


Flowcharts and Logic

We refine the initial specification: we describe in more detail the scenarios of the system's behavior and the user in different situations, so as not to miss anything. We use flowcharts, mind maps, and diagrams, which represent the data visually and are convenient for discussion.

Блок-схемы и логика


Business Processes and BPMN Diagrams

BPMN allows us to describe business logic in a language that is understandable to all project participants. It is understood by the development team (business analysts, programmers, product managers) and the client side (owner and employees).

Бизнес-процессы и BPMN-диаграммы


Access Rights (ACL)

We create rules for dividing access to sections and functions for each role, so that the development team correctly implements ACL policies (Access Control List). This will immediately organize the architecture and role model correctly, taking into account all the sections and functions of the system.

Права доступа (ACL)


Functional Requirements

The document includes a list of modules. The main functions are described in each module. For each function, we write requirements in the format of User Story, with technical clarifications where necessary.

Функциональные требования


Functional Test Cases

For the described functionality, we create test cases in Gherkin language - a human-readable language for describing the behavior of the system in a format that allows for future implementation of automated tests or manual testing of functionality.

Пример описания тест-кейсов


Notifications and Email

We describe in the requirements the system triggers for notifications for each role, create email templates with texts, describe interface errors, and pop-up tooltips.

Пример дизайна email уведомлений для проекта


Resulting Specification

We do not set the task of creating an encyclopedia for the project, the average size of such a specification is several dozen pages (50-60). At the same time, it is a summary of all agreed project requirements from different perspectives: business logic, user behavior, technical constraints, and design requirements. Our specification has the necessary level of detail to start development and is prepared relatively quickly (4-6 weeks). Example project specification.

If you need to create a technical specification for the project, write to us on Telegram. We will be happy to help.

If you have a complex project and need help with design, write to us. We will study the requirements, estimate the workload, and offer project ideas taking into account our accumulated experience — within 1 business day.

Frequently Asked Questions

Need design. What is required from me?

Send the existing requirements by email or Telegram. We will study the information and let you know if we can help.

Need design. What is required from me?

Send the existing requirements by email or Telegram. We will study the information and let you know if we can help.

Need design. What is required from me?

Send the existing requirements by email or Telegram. We will study the information and let you know if we can help.

Какие варианты сотрудничества?

Работаем как ООО "КРОНМЕДИА", ИНН 5504154094, аккредитованная ИТ-компания, по УСН, без НДС. Заключаем рамочный договор, условия прописываем в доп. соглашениях. Обмен по ЭДО.

Какие варианты сотрудничества?

Работаем как ООО "КРОНМЕДИА", ИНН 5504154094, аккредитованная ИТ-компания, по УСН, без НДС. Заключаем рамочный договор, условия прописываем в доп. соглашениях. Обмен по ЭДО.

Какие варианты сотрудничества?

Работаем как ООО "КРОНМЕДИА", ИНН 5504154094, аккредитованная ИТ-компания, по УСН, без НДС. Заключаем рамочный договор, условия прописываем в доп. соглашениях. Обмен по ЭДО.

How much does it cost?

Studio rate 2500 rubles per hour. Team cost 600 thousand rubles per month. The duration depends on the project scope. The cost includes prototype, UI-kit, color palettes, typography, layouts in Figma for 3-5 resolutions.

How much does it cost?

Studio rate 2500 rubles per hour. Team cost 600 thousand rubles per month. The duration depends on the project scope. The cost includes prototype, UI-kit, color palettes, typography, layouts in Figma for 3-5 resolutions.

How much does it cost?

Studio rate 2500 rubles per hour. Team cost 600 thousand rubles per month. The duration depends on the project scope. The cost includes prototype, UI-kit, color palettes, typography, layouts in Figma for 3-5 resolutions.

How much time is needed for design?

Large projects usually require 2 months. For small tasks, the estimate is a few days.

How much time is needed for design?

Large projects usually require 2 months. For small tasks, the estimate is a few days.

How much time is needed for design?

Large projects usually require 2 months. For small tasks, the estimate is a few days.

Как выглядит процесс работы?

Изучим требования, сделаем дизайн-концепцию, обсудим её на онлайн-встрече. Если всё нравится — двигаемся дальше. Раз в неделю делаем демо промежуточных результатов. Общение — в телеграм. С нашей стороны есть менеджер проекта, который отвечает за результат. Открытый доступ к проекту в Figma — можно следить за прогрессом.

Как выглядит процесс работы?

Изучим требования, сделаем дизайн-концепцию, обсудим её на онлайн-встрече. Если всё нравится — двигаемся дальше. Раз в неделю делаем демо промежуточных результатов. Общение — в телеграм. С нашей стороны есть менеджер проекта, который отвечает за результат. Открытый доступ к проекту в Figma — можно следить за прогрессом.

Как выглядит процесс работы?

Изучим требования, сделаем дизайн-концепцию, обсудим её на онлайн-встрече. Если всё нравится — двигаемся дальше. Раз в неделю делаем демо промежуточных результатов. Общение — в телеграм. С нашей стороны есть менеджер проекта, который отвечает за результат. Открытый доступ к проекту в Figma — можно следить за прогрессом.

В каком виде отдаётся результат?

Проект в Figma, который включает макеты страниц, UI-kit, типографику, и палитры. Макеты собраны на autolayout, используем переменные для размерностей и цветов. Всё организовано для удобства frontend-разработки и быстрого внесения правок при необходимости в будущем.

В каком виде отдаётся результат?

Проект в Figma, который включает макеты страниц, UI-kit, типографику, и палитры. Макеты собраны на autolayout, используем переменные для размерностей и цветов. Всё организовано для удобства frontend-разработки и быстрого внесения правок при необходимости в будущем.

В каком виде отдаётся результат?

Проект в Figma, который включает макеты страниц, UI-kit, типографику, и палитры. Макеты собраны на autolayout, используем переменные для размерностей и цветов. Всё организовано для удобства frontend-разработки и быстрого внесения правок при необходимости в будущем.

Можете сделать тестовое задание?

Да, мы можем сделать дизайн главной страницы, чтобы продемонстрировать системный подход в дизайне и удобство сотрудничества. Проведём демонстрацию концепции руководству, с обоснованием выбранных решений. Продумаем смыслы, логику и визуальный стиль вашего продукта.

Можете сделать тестовое задание?

Да, мы можем сделать дизайн главной страницы, чтобы продемонстрировать системный подход в дизайне и удобство сотрудничества. Проведём демонстрацию концепции руководству, с обоснованием выбранных решений. Продумаем смыслы, логику и визуальный стиль вашего продукта.

Можете сделать тестовое задание?

Да, мы можем сделать дизайн главной страницы, чтобы продемонстрировать системный подход в дизайне и удобство сотрудничества. Проведём демонстрацию концепции руководству, с обоснованием выбранных решений. Продумаем смыслы, логику и визуальный стиль вашего продукта.

Where to start?

Compose a list of user roles, a list of required functionality, and a list of website and personal account sections. This is sufficient for evaluation.

Where to start?

Compose a list of user roles, a list of required functionality, and a list of website and personal account sections. This is sufficient for evaluation.

Where to start?

Compose a list of user roles, a list of required functionality, and a list of website and personal account sections. This is sufficient for evaluation.

Describe the task informally to estimate the amount of work. Write, we will be glad to be useful.

Describe the task informally to estimate the amount of work. Write, we will be glad to be useful.

Describe the task informally to estimate the amount of work. Write, we will be glad to be useful.