Low-code подход в разработке IT-проекта - KT.Team

Low-Code Approachin IT-Project Development

Low-code is a development concept when developers create a builder, which is a universal tool for solving complex and non-standard tasks, on the basis of which all future business requirements are formed. Low-code accelerates the implementation of new project features and helps cut the development costs.

LOW-CODE PRINCIPLES

Creating a Builder

Узнать подробнее о возможностях Low-code систем - KT.Team

Создание конструктора в Low-code системах - KT.Team

In the low-code concept, the developer is responsible for the availability of components in the builder. It often happens that you don't need to write a builder from scratch – LCDP/LCAP already have ready-made components. A business analyst gets an understandable tool for designing and implementing most of the requirements, whereas developers are responsible for delivering the top quality builder components.

Visual Modeling

Визуальное моделирование в Low-code системах - KT.Team

Low-code platforms have an intuitive drag and drop interface with built-in components for information display, which ensure the compliance with the self-documentation principle and the ease of functionality-related changes.

Reduced Development Time

Low-code системы сокращают время на разработку - KT.Team

In the code-first paradigm developer's help is needed to make even minor changes, whereas in the low-code concept many operational changes can be implemented by business analysts, and developers should only revise these changes. Thus, developers have time for other (and more important) tasks.

LOW-CODE COMPARED TO THE CODE-FIRST DEVELOPMENT

Low-code (LCDP)

Code-first

Resources for the implementation

2–3 managers (or business analysts) and 1–2 developers.

A development team (~ 7 people) and 1 manager (or a business analyst).

Time of Implementation

In the LCDP concept, development is carried out in 3 stages: task – builder – final functionality. Developers don't have to perform boring routine tasks, and in some cases the changes are implemented faster.

In the code-first paradigm, the development process is based on the "task – final solution" scheme. The Code-first cycle is longer, because in this case any edit goes through the standard development cycle.

Documentation

User interfaces, business processes, data and integrations in LCDP are visualized, allowing the business to form requests for changes more clearly and have an unambiguous and clear representation (with respect to naming conventions).

In the code-first paradigm, the code and user documentation are always separated. The documentation maintenance requires additional efforts, which does not help avoid the duplicates and ambiguity of the narrative.

Operation

LCDP is easier to put into operation due to its self-documentability and the ease of logging unification.

The launch into operation requires a high level of development culture both on part of developers and the company's management.

Retaining engineering talent

Engineers are not involved in routine tasks execution; they are responsible for reusable builder elements. This allows developers to focus on quality, and business – on the core value.

As developers are responsible for delivering and modifying the final value, engineers burn out, and the business generates fewer changes. Solving these problems implies significant investments in the communication culture and complex process development.

Cost of work

The main focus is on creating a new builder or configuring the existing one, whereas edits to the functionality can be made by the customer himself. This reduces the development time and the cost of a ready-made solution.

The cost of a ready-made solution depends not only on the development, but also on whether further improvements and technical maintenance are required, which immediately drives up the price.

ADVANTAGES OF THE LOW-CODE CONCEPT

Flexibility in tool selection

The low-code builder can be either a ready-made solution or require some further improvements. Later on, the functionality will be designed with it's tools.

Less dependence on development

Advanced users (aka. citizen developers) can adjust the ready-made functionality by themselves, whereas the IT department only develops fundamentally new elements and the logic.

The IT department is the "head", not the "hands"

The IT department is no longer an executor, but an advisor and a supervisor of the changes made.

LOW-CODE SYSTEMS

ESB →

These systems allow prompt implementation of flexible integrations between the systems, improving the end systems architecture by centralizing the integration logic in single system.

PIM/MDM →

Pimcore is a system that combines PIM and MDM functions. It ensures the provision of comprehensive information about products, helps manage the master data and the rules for publishing product information on various platforms taking into account the channel specifics.
‍