Our Values

Compared to previous methodologies the planning of the system does not focus on the definition of an idealistic database structure and the UI. The aim of the planning is the identification of well defined business entities (domains), and the definition of related business processes, required operation and functionality.
Important part of the methodology is the defining and using of common language by the product owner and the users delegated to the project. The correct and homogenous usage of concepts, descriptions, titles helps to avoid misunderstanding of logical and functional requirements, and ensures using correct titles in accordance with the real life operation.

One of the main benefits of using the DDD methodology is that instead of the database structure, exclusively the functions related to business events and the connections and dependencies between functions define the business logic.

Graphic examples of employing Domain Driven Design methodology:
• In case the data of a person must be handled from diverse business perspectives, then the core personal data and the person related data related to the unique business perspectives must be separated in the system. This way no business rules are encoded, ‘engraved’ into standard data read, edit, store, update procedures.

• The business processes are implemented in the system by representation of all real business events, for example the sales of a product is an event of the system, and the confirmation mail is sent as a response to the completion of this event. Later further related events can be linked to the completion of this event (for example comission calculation), or the operation of linked events can be altered according to the changing business processes.

• In case great amount of data from diverse business entities must be requested regularly from the system, or data derived from one or more business entities must be reported, than new derived business entities can be defined, those automatic update, synchronization is implemented in the system. As a result for a report with complex dataset the system does not require to query many linked entities (and datatables with multiple links), that can slow down the operation of the system. Thanks to the optimized data handling the system can provide the prepared specific dataset for the complex reports with high number of records.
• In case the data of a person must be handled from diverse business perspectives, then the core personal data and the person related data related to the unique business perspectives must be separated in the system. This way no business rules are encoded, ‘engraved’ into standard data read, edit, store, update procedures.

• The business processes are implemented in the system by representation of all real business events, for example the sales of a product is an event of the system, and the confirmation mail is sent as a response to the completion of this event. Later further related events can be linked to the completion of this event (for example comission calculation), or the operation of linked events can be altered according to the changing business processes.

• In case great amount of data from diverse business entities must be requested regularly from the system, or data derived from one or more business entities must be reported, than new derived business entities can be defined, those automatic update, synchronization is implemented in the system. As a result for a report with complex dataset the system does not require to query many linked entities (and datatables with multiple links), that can slow down the operation of the system. Thanks to the optimized data handling the system can provide the prepared specific dataset for the complex reports with high number of records.
DOMAIN DRIVEN DESIGN
Graphic examples of employing Domain Driven Design methodology:
• In case the data of a person must be handled from diverse business perspectives, then the core personal data and the person related data related to the unique business perspectives must be separated in the system. This way no business rules are encoded, ‘engraved’ into standard data read, edit, store, update procedures.

• The business processes are implemented in the system by representation of all real business events, for example the sales of a product is an event of the system, and the confirmation mail is sent as a response to the completion of this event. Later further related events can be linked to the completion of this event (for example comission calculation), or the operation of linked events can be altered according to the changing business processes.

• In case great amount of data from diverse business entities must be requested regularly from the system, or data derived from one or more business entities must be reported, than new derived business entities can be defined, those automatic update, synchronization is implemented in the system. As a result for a report with complex dataset the system does not require to query many linked entities (and datatables with multiple links), that can slow down the operation of the system. Thanks to the optimized data handling the system can provide the prepared specific dataset for the complex reports with high number of records.
Graphic examples of employing Domain Driven Design methodology:

Compared to previous methodologies the planning of the system does not focus on the definition of an idealistic database structure and the UI. The aim of the planning is the identification of well defined business entities (domains), and the definition of related business processes, required operation and functionality.

Compared to previous methodologies the planning of the system does not focus on the definition of an idealistic database structure and the UI. The aim of the planning is the identification of well defined business entities (domains), and the definition of related business processes, required operation and functionality.

Compared to previous methodologies the planning of the system does not focus on the definition of an idealistic database structure and the UI. The aim of the planning is the identification of well defined business entities (domains), and the definition of related business processes, required operation and functionality.

Important part of the methodology is the defining and using of common language by the product owner and the users delegated to the project. The correct and homogenous usage of concepts, descriptions, titles helps to avoid misunderstanding of logical and functional requirements, and ensures using correct titles in accordance with the real life operation.
One of the main benefits of using the DDD methodology is that instead of the database structure, exclusively the functions related to business events and the connections and dependencies between functions define the business logic.

Important part of the methodology is the defining and using of common language by the product owner and the users delegated to the project. The correct and homogenous usage of concepts, descriptions, titles helps to avoid misunderstanding of logical and functional requirements, and ensures using correct titles in accordance with the real life operation.
One of the main benefits of using the DDD methodology is that instead of the database structure, exclusively the functions related to business events and the connections and dependencies between functions define the business logic.

Important part of the methodology is the defining and using of common language by the product owner and the users delegated to the project. The correct and homogenous usage of concepts, descriptions, titles helps to avoid misunderstanding of logical and functional requirements, and ensures using correct titles in accordance with the real life operation.
One of the main benefits of using the DDD methodology is that instead of the database structure, exclusively the functions related to business events and the connections and dependencies between functions define the business logic.

Compared to previous methodologies the planning of the system does not focus on the definition of an idealistic database structure and the UI. The aim of the planning is the identification of well defined business entities (domains), and the definition of related business processes, required operation and functionality.

Compared to previous methodologies the planning of the system does not focus on the definition of an idealistic database structure and the UI. The aim of the planning is the identification of well defined business entities (domains), and the definition of related business processes, required operation and functionality.

Compared to previous methodologies the planning of the system does not focus on the definition of an idealistic database structure and the UI. The aim of the planning is the identification of well defined business entities (domains), and the definition of related business processes, required operation and functionality.

Important part of the methodology is the defining and using of common language by the product owner and the users delegated to the project. The correct and homogenous usage of concepts, descriptions, titles helps to avoid misunderstanding of logical and functional requirements, and ensures using correct titles in accordance with the real life operation.
One of the main benefits of using the DDD methodology is that instead of the database structure, exclusively the functions related to business events and the connections and dependencies between functions define the business logic.

Important part of the methodology is the defining and using of common language by the product owner and the users delegated to the project. The correct and homogenous usage of concepts, descriptions, titles helps to avoid misunderstanding of logical and functional requirements, and ensures using correct titles in accordance with the real life operation.
One of the main benefits of using the DDD methodology is that instead of the database structure, exclusively the functions related to business events and the connections and dependencies between functions define the business logic.

Important part of the methodology is the defining and using of common language by the product owner and the users delegated to the project. The correct and homogenous usage of concepts, descriptions, titles helps to avoid misunderstanding of logical and functional requirements, and ensures using correct titles in accordance with the real life operation.
One of the main benefits of using the DDD methodology is that instead of the database structure, exclusively the functions related to business events and the connections and dependencies between functions define the business logic.

Benefits of using cloud native technologies:
• the operation and management of core hardware and software infrastructure can be outsourced

• the operation and management of core hardware and software infrastructure can be centralized or separated

• the required functionality is implemented based on a stable, standard hardware and software infrastructure with high level (24/7, 99,X%) reliability, ensuring that all elements of the software operation can be effectively scaled in response to the changes in level of load
Benefits of using cloud native technologies:
CLOUD NATIVE OPERATION
• the operation and management of core hardware and software infrastructure can be outsourced

• the operation and management of core hardware and software infrastructure can be centralized or separated

• the required functionality is implemented based on a stable, standard hardware and software infrastructure with high level (24/7, 99,X%) reliability, ensuring that all elements of the software operation can be effectively scaled in response to the changes in level of load
Benefits of using cloud native technologies:
• the operation and management of core hardware and software infrastructure can be outsourced

• the operation and management of core hardware and software infrastructure can be centralized or separated

• the required functionality is implemented based on a stable, standard hardware and software infrastructure with high level (24/7, 99,X%) reliability, ensuring that all elements of the software operation can be effectively scaled in response to the changes in level of load
The development proceeds in iterations - the required functionality of the system is implemented as functions or group of functions that are based on eachother. The benefits of this operation:
•Already in the early stage of the development completely usable functionality is handed over for testing - those required functionality is known by both sides,

•the smaller, well defined functionality can be thoroughly tested in the following two weeks, and the required functional modifications, fine-tunings are revealed in early stage of development - this way the related development tasks and bugfixes can be completed in planned way in the following sprints.

•the user acceptance tests are completed using the predefined test cases, in compliance with the jointly accepted acceptance criteria according to the test plan - approaching the closing of the project the users of the client and the developers can focus on completion of the tasks required to the going live of the system.

• Green-blue deployment: The software updates and functional extensions, amendments can be deployed without shutting down the system, even in those cases when the changes indicate also database structure modifications.
The development proceeds in iterations - the required functionality of the system is implemented as functions or group of functions that are based on eachother. The benefits of this operation:
CONTINUOUS DELIVERY
• Already in the early stage of the development completely usable functionality is handed over for testing - those required functionality is known by both sides,

• the smaller, well defined functionality can be thoroughly tested in the following two weeks, and the required functional modifications, fine-tunings are revealed in early stage of development - this way the related development tasks and bugfixes can be completed in planned way in the following sprints.

• the user acceptance tests are completed using the predefined test cases, in compliance with the jointly accepted acceptance criteria according to the test plan - approaching the closing of the project the users of the client and the developers can focus on completion of the tasks required to the going live of the system.

• Green-blue deployment: The software updates and functional extensions, amendments can be deployed without shutting down the system, even in those cases when the changes indicate also database structure modifications.
The development proceeds in iterations - the required functionality of the system is implemented as functions or group of functions that are based on eachother. The benefits of this operation:
• Already in the early stage of the development completely usable functionality is handed over for testing - those required functionality is known by both sides,

• the smaller, well defined functionality can be thoroughly tested in the following two weeks, and the required functional modifications, fine-tunings are revealed in early stage of development - this way the related development tasks and bugfixes can be completed in planned way in the following sprints.

• the user acceptance tests are completed using the predefined test cases, in compliance with the jointly accepted acceptance criteria according to the test plan - approaching the closing of the project the users of the client and the developers can focus on completion of the tasks required to the going live of the system.

• Green-blue deployment: The software updates and functional extensions, amendments can be deployed without shutting down the system, even in those cases when the changes indicate also database structure modifications.
We have chosen the agile methodology for the management of our projects. Before the start of the development our consultants define the functional requirements of the software and the planned schedule of the development in close cooperation with the users delegated to the project by our client. The development proceeds in two week sprints. The client side project manager, the architect and the consultant (product owner) define together the development tasks required to implement all required functionality and the acceptance criteria related to that.
AGILE METHOLODGY
We have chosen the agile methodology for the management of our projects. Before the start of the development our consultants define the functional requirements of the software and the planned schedule of the development in close cooperation with the users delegated to the project by our client. The development proceeds in two week sprints. The client side project manager, the architect and the consultant (product owner) define together the development tasks required to implement all required functionality and the acceptance criteria related to that.
We have chosen the agile methodology for the management of our projects. Before the start of the development our consultants define the functional requirements of the software and the planned schedule of the development in close cooperation with the users delegated to the project by our client. The development proceeds in two week sprints. The client side project manager, the architect and the consultant (product owner) define together the development tasks required to implement all required functionality and the acceptance criteria related to that.
previous arrow
next arrow
Slider

1054 Budapest, Alkotmány utca 4. 4. em. 15.

Learn more about us on Linkedin


Privacy Policy | plensys.hu @ Copyright 2020