Real flexibility and rules-based software development system and method

Abstract

The invention relates to a software ecosystem, which is a real flexible and rule-based software development system and method that enables companies or individuals who are experts in their business to create a software ecosystem where they can create their own user interfaces that will determine how the software application will behave according to the specified situations by defining the objects and workflows belonging to the jobs in their field of expertise with very simple visuals without software knowledge, and to provide users with active interactive use of the information entered in object definitions, rule creation and reporting with Artificial Intelligence (AI).

Description

[0001] DESCRIPTION

[0002] REAL FLEXIBILITY AND RULES-BASED SOFTWARE DEVELOPMENT SYSTEM AND METHOD

[0003] FIELD OF THE INVENTION

[0004] The invention relates to a software ecosystem, which is a real flexible and rule-based software development system and method that enables companies or individuals who are experts in their business to create a software ecosystem, where they can create their own user interfaces that will determine how the software application will behave according to the specified situations by defining the objects and workflows belonging to the jobs in their field of expertise with very simple visuals without software development knowledge, and to provide users with dynamic interactive use of the information entered in object definitions, rule creation and reporting with Artificial Intelligence (Al).

[0005] In particular, regardless of the number of employees, the invention is aimed at both companies that want to increase their business volume and companies with increased business volumes, both in software and non-software companies, with real flexibility, rulebased and flexible as well as “hard-coded software performance”, and Artificial Intelligence (Al) supported software that can meet software needs, industry (electronic machinery, factories with robots, etc.), military, engineering, chemistry, biology, physics, banking, health, law, construction, education and other fields.), military, engineering, chemistry, biology, physics, banking, health, law, construction, education and other fields, development of stock exchange management software, creation of the necessary base for the training of artificial intelligence software, integration with loT devices, development of software specific to the construction sector or development of software or plug-ins that will be integrated into programs used in any sector, creation of online-shop systems, development of software for the health sector (pharmacy, hospital, polyclinic, etc.), development of software for the transportation business, development of software used for both mapping and management processes for companies engaged in transportation business, development of ERP (Enterprise Resource Planning) software specific to companies, realization of software solutions that include very specific issues belonging to insurance companies, and all software applications that cannot be exemplified under this definition are related to a software ecosystem that develops applications based on integration and similar rules. PRIOR ART

[0006] Today, in companies that do not have a software development team, if there is a need for any changes in the programs currently used or a completely new program is needed;

[0007] • The product owner is involved in the development of the required program from start to finish. In order to have the required product, the product owner must explain all his / her requirements and modifications for the program or program add-on to all stakeholders. The product owner has to take the risk of both time loss and costs arising from the following problems for his / her needs; Loss of time derived from defining and documenting the requirements accurately and completely;

[0008] ■ Sometimes there may be problems in expressing the requirements. The desired situation must be explained to the software company and the software company must understand the actual requirement. As it is known, companies may experience problems in transmitting such information to companies outside their own structure, that is, companies that do not know how to operate.

[0009] ■ Even though the requirement is transmitted completely correct, sometimes the request may be misunderstood by the software developer team. Misunderstanding the employer's request (the failure of the software team to understand it correctly is discussed here) and exceeding the specified delivery time may cause technical or financial difficulties in the employer's current work. Since software companies are separate organizations, they can offer very high prices to the product owner or company.

[0010] • In some cases, a new software or new add-ins are needed to be used interactively with one or more programs currently used (with different databases, ERP, e- commerce, banking, drawing programs in the construction industry, etc.). In this case, these systems need to be accessed / connected to be used in the software development process, and therefore new modifications must be made in the infrastructure. Of course, this may cause problems in terms of both time and cost.

[0011] • The product owner may reluctantly share their company secrets, supplier information or solution partner information to another company outside their organization (software development company).

[0012] • The elapsed time to prepare a contract between the product owner and the software company is also considered a waste of time and money. In companies that have a software developer team or software companies, the majority of existing software has been developed using traditional logic. In other words, the information on the user screens / devices seen by clients is similar with the class structures of the application running in the backend and the database design with which the programs running in the background interact. These companies have to go through software development processes over and over again for each new project. During this period, a financial problem arises from the need to distribute the work to the following stakeholders:

[0013] • Software Developer-Team

[0014] • Test team,

[0015] • Project Manager

[0016] • Creation of hardware and software (operating system, database, etc.) infrastructures.

[0017] Briefly;

[0018] • Loss of time and money spent on frontend software development for the user interfaces,

[0019] • Loss of time and money spent on developing software that is hidden to clients and will run at the background,

[0020] • Loss of time and money spent on database design (DB-Design),

[0021] • License fees (database, software development environment and tools),

[0022] • Loss of time and money due to the necessity of creating frontend, backend and database (DB) infrastructures,

[0023] • Difficulties in maintaining the frontend software, backend software and database (DB) infrastructures separately for each new project,

[0024] • Problems in keeping track of updates of operating systems, software development languages, database systems and libraries used in software development,

[0025] • Since the database design is very easily accessible, data manipulation can be done easily with a little database knowledge,

[0026] • Software project developed with the software methods applied by the vast majority is not open to continuous development for many years,

[0027] • In order to implement new features added to existing programs, the operating system may be disrupted, even for a short time, and in this case, this must be announced and planned in advance to all relevant users, resulting in work, time and financial loss, time and financial losses occur due to the above-mentioned problems. Therefore, the company lags behind its competitors in terms of cost and time. As a result of the literature review, US patent application with the document number US20220206762A1 is encountered. The application in question relates only to a software system based on supply chain management (SCM). This can also be seen from the service information defined in the Entity block in the Figure 1 E diagram of the invention. There is no customized service in the software developed with the invention numbered US20220206762A1 that allows development and application in the desired field. It is not possible to develop stock exchange management software with an application focused on supply chain management, create the necessary base for the training of artificial intelligence software, ensure integration with loT devices, developing software specific to the construction sector or develop software or add-in that integrate with programmes used in any sector, develop software for the health sector (pharmacy, hospital, polyclinic, etc.), to develop software used for both mapping and management processes for companies engaged in transport business, to develop ERP (Enterprise Resource Planning) software specific to companies, and to realise software solutions that include very specific issues for insurance companies. In short, there is no system that enables the mentioned operations without writing a single line of code in every field that requires real rules or in the field of developing existing programs. Today, there is a need for a system that allows services to be created with rule definitions for similar or unique tasks or transactions with the mentioned features. The rule-based operating system in the patent document numbered US20220206762A1 is seen as guiding the codes written for the development of the program rather than expressing a definable whole. However, a system that can only create a programme with the whole of the rules and thus creates a completely flexible software, at the same time, a system that works completely with the rules determined by the users and creates the process that will work from the beginning to the end of any process is not available either in the market or in the patent document numbered US20220206762A1 .

[0028] In addition, it is not clear what is meant by the query made from the different databases specified in document number US20220206762A1 and it is not clear how this query is carried out. Because the definition of connection information to different databases is not specified here, and there appears to be a structure that implements queries that can only be made with 'aggregation' in NoSQL databases in the same way. Currently, there is a need for a software ecosystem that is offered to users query features specific to NoSQL, MS-SQL, Oracle, MySQL and Redis databases. However, a system with the mentioned features does not exist or is not available in the patent document numbered US20220206762A1 . As a result, the above-mentioned problems that cannot be solved in the light of the state of the art have made it necessary to make a new improvement in the relevant technical field.

[0029] BRIEF DESCRIPTION OF THE INVENTION

[0030] The present invention relates to a real flexible and rule-based software development system and method in order to eliminate the above-mentioned disadvantages and to bring new advantages to the relevant technical field.

[0031] The main purpose of the present invention is to enable companies / individuals to define the object definitions and flow diagrams with very simple visuals of the required jobs without software knowledge, to define how the software application will behave according to the determined situations to create user interfaces and to enable users to use the information actively interactive with artificial intelligence in object definitions, rule creation and reporting.

[0032] The other purpose of the present invention is to enable companies that want to expand or already grown their business volume and software companies to work with real flexibility, rule-based and flexible as well as “hard-coded software performance”, regardless of the number of employees, and to meet software needs in all areas.

[0033] In order to achieve all the purposes mentioned above and arising from the detailed explanation below, the present invention is software ecosystem with true flexibility and rules- based software development system, which may comprise the communication network that enables communication with real flexibility and rule-based software development system, the programmes that companies currently use, the machines / devices that are electronic or mechanical devices that companies currently use, loT devices that use the communication network where physical objects that companies currently use are connected to each other or to larger systems, the tools that companies manage their existing systems, system management which are real persons or users, integration programmes which are software that companies will integrate, integration machines / devices that companies will integrate, integration loT devices that companies will integrate, interactive tools used for the integrated system and integration management units which are real persons, can work with real flexibility, rule-based and flexible as well as “hard-coded software performance” in companies that want to expand or already grown their business volume regardless of the number of employees, either software companies or other companies except software market, develop rule-based applications in every software that can be used in all areas where software needs can be met, enables companies / individuals who are experts in their business to create a software ecosystem where they can create their own user interfaces that will determine how the software application will behave according to the specified situations by defining the objects and workflows belonging to the jobs in their field of expertise with very simple visuals without software knowledge , and provide users with active interactive use of information with artificial intelligence in object definitions, rule creation and reporting, can be controlled via all electronic devices such as computers, tablets, smartphones and smart watches, characterized in that, the present invention comprises said database / server, which contains all the definitions to be made to use the rule-based software development system with real flexibility, can also be used as a referenced library in other services, providing access to the definitions needed in other services, ensuring the communication flow between modules as smart definers, where all definitions made through smart definers are included in the current running application in real time, business service, which includes functions that enable the operation of definitions made with smart definers, database service, through which database / server operations are performed and which assumes the responsibility of database / server, smart definers, business service, cache service and database service modules in a controlled manner, on which the definitions are registered, with real flexibility and on which the result data produced by the use of neural system / neural server, which may vary depending on the environment or environments in which it is developed, the rule-based software development system are recorded, having data storage systems.

[0034] In order to understand the advantages of the present invention with its structure and additional elements, it shall be evaluated with the following defined figures.

[0035] BRIEF DESCRIPTION OF DRAWINGS

[0036] Figure 1 is a representative view illustrating how the inventive real flexibility and rule-based software development system will be used with existing software and / or systems and with the software and / or systems with which they will be / are integrated and explaining the location where the invention will be deployed.

[0037] Figure 2 is a representative view showing the communication between modules and planned in the structure of the real flexibility and rule-based software development system that is the subject of the invention.

[0038] Figure 3 is a representative view of the general lines of the submodules created in the smart definers in the real flexibility and rule-based software development system that is the subject of the invention.

[0039] Figure 4 is a representative illustration of the smart user-interface definers found in the real flexibility and rule-based software development system that is the subject of the invention. Figure 5 is a general representation of the objects that are planned to be used everywhere and at every stage of the real flexibility and rule-based software development system, which is the subject of the invention, and the part where all the features of these objects will be defined.

[0040] Figure 6 is a representative overview of the parts that will constitute the real flexibility rulebased operating system of the rule-based software development system that is the subject of the invention.

[0041] Figure 7 is a representative illustration of the smart scheduled task definer found in the real flexibility and rule-based software development system that is the subject of the invention.

[0042] Figure 8 is a representative illustration of the smart validation definer found in the real flexibility and rule-based software development system that is the subject of the invention.

[0043] Figure 9 is a representative illustration of the business service available in the real flexibility and rule-based software development system that is the subject of the invention.

[0044] Figure 10 is a representative overview of the cache service in the real flexibility and rulebased software development system that is the subject of the invention.

[0045] Figure 11 is a representative illustration of the data base service available in the real flexibility and rule-based software development system that is the subject of the invention.

[0046] Figure 12 is a representative screenshot showing the general outline of the structure responsible for creating object definitions used in an embodiment of the real flexibility and rule-based software development system and method that is the subject of the invention.

[0047] Figure 13 is a representative screenshot of how another object named name can be defined under the person object defined in an embodiment of the real flexibility and rule-based software development system and method that is the subject of the invention.

[0048] Figure 14 is a representative screenshot used to create user interface themes in an application of the real flexibility and rule-based software development system and method that is the subject of the invention.

[0049] Figure 15 is a representative screenshot created for employee information entry that users will see, with the information defined in an embodiment of the real flexibility and rule-based software development system and method that is the subject of the invention.

[0050] Figure 16 is a representative screenshot created to prepare the screen where users will log in an embodiment of the real flexibility and rule-based software development system and method that is the subject of the invention.

[0051] Figure 17 is a representative screenshot where users can define their employee information in order to log in to the application with the information defined in an embodiment of the real flexibility and rule-based software development system and method that is the subject of the invention. Figure 18 is a representative screenshot of the inclusion of code snippets developed by users as add-ins, according to their own needs, into the system, in addition to the existing structure developed in an embodiment of the real flexibility and rule-based software development system and method that is the subject of the invention.

[0052] Figure 19 is a representative screenshot where users can create rules for their own operations, in an embodiment of the real flexibility and rule-based software development system and method that is the subject of the invention and without software development knowledge.

[0053] Figure 20 is a representative screenshot showing how the definition of the rule in the real flexibility and rule-based software development system and method that is the subject of the invention will be included in the current embodiment in general terms.

[0054] Figure 21 is a representative screenshot showing the add-in definition in the real flexibility and rule-based software development system and method that is the subject of the invention. Figure 22 is an ecological representative diagram showing the communication between the business services and modules to achieve the result by using the real flexibility and rulebased software development system and method that is the subject of the invention.

[0055] Figure 23 is a representative illustration of the process of creating a user interface with a smart user-interface definer in the real flexibility and rule-based software development system and method that is the subject of the invention.

[0056] Figure 24 is a representative illustration of the object defining process of the smart object definer in the real flexibility and rule-based software development system and method that is the subject of the invention.

[0057] Figure 25 is a representative illustration of the rule defining process of the smart rule definer in the real flexibility and rule-based software development system and method that is the subject of the invention.

[0058] Figure 26 is a representative illustration of the process of defining the timed operating functions of a smart scheduled task definer in a real flexibility and rule-based software development system and method that is the subject of the invention.

[0059] Figure 27 is a representative illustration of the validation defining process of the smart validation definer in the real flexibility and rule-based software development system and method that is the subject of the invention.

[0060] Figure 28 is a representative illustration of the user-based code definition process of the smart add-in definer in the real flexibility and rule-based software development system and method that is the subject of the invention.

[0061] Figure 29 is a representative illustration of the execution of an external request and the execution of a request generated therefrom to the real flexibility and rule-based software development system and method that is the subject of the invention. The figures are not required to be scaled and the details which are not necessary for understanding the present invention may be neglected. Moreover, the elements that are at least substantially identical or have at least substantially identical functions are shown by the same number.

[0062] REFERENCE NUMBERS

[0063] 1 . Overview of the current situation

[0064] 11 . Programs

[0065] 12. Machines / devices

[0066] 13. loT devices

[0067] 14. System management

[0068] 2. Communication network

[0069] 3. Real flexibility and rules-based software development system

[0070] 4. Integration overview

[0071] 41 . Programs to be integrated

[0072] 42. Machines / devices to be integrated

[0073] 43. loT devices to be integrated

[0074] 44. Integration management

[0075] 100 Smart definers

[0076] 1001 . Smart user-interface definer

[0077] 10011. Template definer

[0078] 10012. Operation of objects unit

[0079] 100121 . OnFocus operation unit

[0080] 100122. OnExit operation unit

[0081] 100123. OnChanged operation unit

[0082] 100124. MouseHover operation unit

[0083] 10013. Page load / page close operation unit

[0084] 100131 . Operation unit page before-load

[0085] 100132. Operation unit page after-load

[0086] 100133. Operation unit page before-post

[0087] 100134. Operation unit page after-post

[0088] 100135. Operation unit page before-close

[0089] 100136. Operation unit page after-close

[0090] 100137. Operation Unit Page On-Show

[0091] 100138. Operation Unit Page OnSent Backward 10014. Page validation unit

[0092] 100141. Page Before-Load Validation Unit

[0093] 100142. Page After-Load Validation Unit

[0094] 100143. Page Before-Post Validation Unit

[0095] 100144. Page After-Post Validation Unit

[0096] 1002. Smart object definer

[0097] 10021 . Flexible object definer

[0098] 10022. Object definer

[0099] 10023. Relational definer

[0100] 10024. Multilingual definer

[0101] 1003. Smart rule definer

[0102] 10031 . Type of rule definer

[0103] 10032. Group of rule definer

[0104] 10033. Rule definer

[0105] 1004. Smart scheduled task definer

[0106] 10041 . Scheduled task definer

[0107] 1005. Smart validation definer

[0108] 10051 . Object validation unit

[0109] 100511 . OnFocus validation unit

[0110] 100512. OnExit validation unit

[0111] 100513. OnChanged validation unit

[0112] 1006. Smart add-in definer siness service

[0113] 2001 . Rule selector

[0114] 2002. Rule operator

[0115] 2003. Rule injection unit on runtime

[0116] 2004. Add-in injection unit on runtime

[0117] 2005. Consume service

[0118] 2006. Space portal

[0119] 2007. Front-end builder service

[0120] 2008. Code builder service che service / cache server

[0121] 3001 . User cache service

[0122] 3002. Page cache service

[0123] 3003. Object cache service 3004. Relational cache service

[0124] 3005. Multilingual cache service

[0125] 3006. Ecosystem's own cache service

[0126] 400. Database service

[0127] 4001 . Database / server

[0128] 4002. Insert service

[0129] 4003. Update service

[0130] 4004. Inquiry service

[0131] 500. Neural system / neural server

[0132] 100111000. Uploading the files of an interface template to be used via the smart userinterface definer and creating registration information in the system

[0133] 100111001. Selecting smart object definitions for uploaded interface templates via smart user-interface definer

[0134] 100111002. Requesting the registration of the screen definition information that users will see 100111003. Sending the information identified by the smart user-interface definer to the database / server and cache services / cache server such as page cache service, relational cache service via the neural system / neural server

[0135] 100111004. Checking the information incoming to the page cache service and relational cache service with the current cache status

[0136] 100111005. Directing processing according to the status checks of the page cache service and the relational cache service

[0137] 100111006. Sending a new registration request to the page cache service and the relational cache service

[0138] 100111007. Sending a status message to the user on his / her electronic device via the neural system / neural server to notify that the registration information has been temporarily added to the cache

[0139] 100111008. Saving the registration status sign as in progress on the user side

[0140] 100111009. Transmitting the new information to the insert service of database service via the neural system / neural server in order to save it in the database / server

[0141] 100111010. Saving the information incoming to the database service to the database / server via the insert service

[0142] 10011101 1. Informing the business service via the neural system / neural server to prepare the saved information for use 100111012. Calling the front-end builder service by looking at the message content coming to the business service

[0143] 100111013. Creating user interface front-end files using the relevant interface information via the front-end builder service

[0144] 100111014. Uploading the relevant files created for the user interface to the server

[0145] 100111015. Transmitting the transaction completion message for the registration in the cache to the neural system / neural server

[0146] 100111016. Updating the registration flag status to completed via the page cache service and the relational cache service

[0147] 100111017. Transmitting a message to the neural system / neural server that the registration process has been completed to notify the user from the user screen / device

[0148] 100111018. Updating the registration flag status to completed on the user screen / device

[0149] 100111019. Sending a request to update existing information to the page cache service and / or the relational cache service

[0150] 100111020. Transmitting the mentioned information to the update service of database service via the neural system / neural server in order to updated information in the database / server 100111021. Saving the information incoming to the database service to the database / server 100111022. Sending the saved information to the business service via the neural system / neural server to prepare it for use

[0151] 100111023. Calling the front-end builder service by looking at the message content incoming to the business service

[0152] 100111024. Creating user interface front-end files using the relevant interface information via the front-end builder service

[0153] 100111025. Uploading the relevant files created for the user interface to the server

[0154] 100111026. Transmitting the transaction completion message for the registration in the cache to the neural system / neural server

[0155] 100111027. Updating the registration flag status to completed in the page cache service and the relational cache service

[0156] 100111028. Transmitting a message to the neural system / neural server that the registration process has been completed to notify the user

[0157] 100111029. Updating the registration flag status to completed on the user screen / device

[0158] 100111030. Sending a status message to the user via his / her electronic device via the neural system / neural server to notify that the cached information has been updated

[0159] 100111031. Saving the registration status sign as in progress on the user side

[0160] 100111032. Termination of the process by informing the user via electronic device

[0161] 1002| 1000. Requesting registration of object definition information via smart object definer 1002|1001. Sending the information identified by the smart object definer to the database / server and cache services / cache server such as object cache service and relational cache service via the neural system / neural server

[0162] 1002|1002. Checking the cache status of information with incoming to the object cache service and the relational cache service

[0163] 1002|1003. Directing processes according to the status checks of the object cache service and the relational cache service

[0164] 1002|1004. Sending a new record creation request to the object cache service and the relational cache service

[0165] 1002| 1005. Sending a status message to the user on his / her electronic device via the neural system / neural server to notify that the registration information has been temporarily added to the cache

[0166] 1002| 1006. Saving the registration status sign as in progress on the user side

[0167] 1002| 1007. Transmitting the new information to the insert service of database service via the neural system / neural server in order to save it in the database / server

[0168] 1002|1008. Saving the information incoming to the database service to the database / server via the insert service

[0169] 1002|1009. Transmitting the saved information to the business service via the neural system / neural server to prepare it for use

[0170] 1002|1010. Calling the code builder service by looking at the message content incoming to the business service

[0171] 1002|1011. Converting defined object information into source code with the code builder service

[0172] 100211012. Injecting source code files into the running system

[0173] 1002|1013. Transmission of the transaction completion message regarding the registrations in the cache to the neural system / neural server

[0174] 1002| 1014. Updating the registration flag to complete flag in the object cache service and the relational cache service

[0175] 1002|1015. Transmitting a message that the registration process has been completed to notify the user to the neural system / neural server

[0176] 1002| 1016. Updating the registration flag status to completed on the user screen / device 1002|1017. Sending an update request of existing information to the object cache service and relational cache service

[0177] 1002| 1018. Transmitting the mentioned information to the update service of database service via the neural system / neural server in order to update the same in the database / server

[0178] 1002|1019. Saving the information incoming to the database service to the database / server via the update service 1002|1020. Sending the saved object information to the business service via the neural system / neural server to prepare it for use

[0179] 1002| 1021 . Calling the code builder service by looking at the message content coming to the business service

[0180] 1002|1022. Converting defined object information into source code with the code builder service

[0181] 1002| 1023. Injecting source code files into the running system

[0182] 1002|1024. Transmitting the transaction completion message regarding the registrations in the cache to the neural system / neural server

[0183] 1002|1025. Updating the registration flag status to completed in the object cache and the relational cache

[0184] 1002|1026. Transmitting a message to the neural system / neural server that the registration process has been completed to notify the user

[0185] 1002| 1027. Updating the registration flag status to completed on the user screen / device 1002|1028. Sending a status message to the user via the neural system / neural server to notify that the registration information in the cache has been updated

[0186] 1002| 1029. Saving the registration flag status as in progress on the user side

[0187] 1002|1030. Termination of the process by informing the user via electronic device

[0188] 1003| 1000. Requesting registration of the rule definition via smart rule definer

[0189] 1003|1001. Sending the information identified by the smart rule definer to the database / server and cache services / cache server such as relational cache service and ecosystem’s own cache service via the neural system / neural server

[0190] 1003|1002. Checking the information incoming to the relational cache service and the ecosystem's own cache service with the current cache status

[0191] 1003|1003. Directing the transaction according to the status checks of the relational cache service and the ecosystem's own cache service

[0192] 1003|1004. Creating a new registration in the relational cache service and the ecosystem's own cache service

[0193] 1003| 1005. Sending a status message to the user on his / her electronic device via the neural system / neural server to notify that the registration information has been added to the cache

[0194] 1003| 1006. Saving the registration status sign as in progress on the user side

[0195] 1003| 1007. Transmitting the new information to the insert service of database service via the neural system / neural server in order to save it in the database / server

[0196] 1003|1008. Saving the information incoming to the database service to the database / server via the insert service 1003|1009. Sending the saved rule information to the business service via the neural system / neural server to prepare it for use

[0197] 1003|1010. Calling the code builder service by looking at the message content incoming to the business service

[0198] 1003|1011. Converting defined rule information into source code with the code builder service

[0199] 100311012. Injecting source code files into the running system

[0200] 1003|1013. Transmission of the transaction completion message regarding the registrations in the cache to the neural system / neural server

[0201] 1003| 1014. Updating the registration flag to complete via the relational cache service and the ecosystem's own cache service

[0202] 1003|1015. Transmitting a message that the registration process has been completed to notify the user to the neural system / neural server

[0203] 1003| 1016. Updating the registration flag status to completed on the user screen / device

[0204] 1003| 1017. Updating existing information in the relational cache service and the ecosystem's own cache service

[0205] 1003| 1018. Transmitting the mentioned information to the update service of database service via the neural system / neural server in order to update the same in the database / server

[0206] 1003|1019. Saving the information incoming to the database service to the database / server via the update service

[0207] 1003|1020. Sending the updated rule information to the business service via the neural system / neural server to prepare it for use

[0208] 1003|1021 . Calling the code builder service by looking at the message content incoming to the business service

[0209] 1003|1022. Converting defined rule information into source code with the code builder service

[0210] 1003| 1023. Injecting source code files into the running system

[0211] 1003|1024. Transmitting the transaction completion message regarding the registrations in the cache to the neural system / neural server

[0212] 1003| 1025. Updating the registration flag status to completed via the relational cache service and the ecosystem's own cache service

[0213] 1003|1026. Transmitting a message to the neural system / neural server that the registration process has been completed to notify the user

[0214] 1003| 1027. Updating the registration flag status to completed on the user screen / device

[0215] 1003|1028. Sending a status message to the user via the neural system / neural server to notify that the registration information in the cache has been updated

[0216] 1003| 1029. Saving the registration flag status as in progress on the user side 1003|1030. Termination of the process by informing the user via electronic device

[0217] 1004| 1000. Requesting registration of the function definition that will run on a timed basis via the smart scheduled task definer

[0218] 1004|1001 . Sending the information defined by the smart scheduled task definer to the database / server and cache services / cache server via the neural system / neural server 1004| 1002. Checking the cache status of information incoming to the cache service

[0219] 1004| 1003. Directing the operation according to the cache service's status checks

[0220] 1004| 1004. Creating a new registration for a scheduled operation in the cache

[0221] 1004| 1005. Sending a status message to the user on his / her electronic device via the neural system / neural server to notify that the registration information has been added to the cache 1004| 1006. Saving the registration status sign as in progress on the user side

[0222] 1004| 1007. Transmitting the new information to the insert service of database service via the neural system / neural server in order to save it in the database / server

[0223] 1004|1008. Saving the information incoming to the database service to the database / server via the insert service

[0224] 1004|1009. Sending the saved timed function information to the business service via the neural system / neural server to prepare it for use.

[0225] 1004|1010. Calling the code builder service by looking at the message content incoming to the business service

[0226] 1004|101 1 . Converting timed function information defined with the code builder service into source code

[0227] 100411012. Injecting source code files into the running system

[0228] 1004|1013. Transmission of the transaction completion message regarding the registrations in the cache to the neural system / neural server

[0229] 1004| 1014. Updating the registration flag status to completed in the cache

[0230] 1004|1015. Transmitting a message that the registration process has been completed to notify the user to the neural system / neural server

[0231] 1004| 1016. Updating the registration flag status to completed on the user screen / device

[0232] 1004| 1017. Updating existing information in the cache

[0233] 1004| 1018. Transmitting the mentioned information to the update service of database service via the neural system / neural server in order to update the same in the database / server

[0234] 1004|1019. Saving the information incoming to the database service to the database / server via the update service

[0235] 1004|1020. Sending the saved timed function information to the business service via the neural system / neural server to prepare it for use. 1004|1021 . Calling the code builder service by looking at the message content incoming to the business service

[0236] 1004|1022. Converting timed function information defined with the code builder service into source code

[0237] 1004| 1023. Injecting source code files into the running system

[0238] 1004|1024. Transmitting the transaction completion message regarding the registrations in the cache to the neural system / neural server

[0239] 1004| 1025. Updating the save flag status to completed in the cache

[0240] 1004|1026. Transmitting a message to the neural system / neural server that the registration process has been completed to notify the user

[0241] 1004| 1027. Updating the registration flag status to completed on the user screen / device

[0242] 1004|1028. Sending a status message to the user via the neural system / neural server to notify that the registration information in the cache has been updated

[0243] 1004| 1029. Saving the registration flag status as in progress on the user side

[0244] 1004|1030. Termination of the process by informing the user via electronic device

[0245] 1005| 1000. Requesting registration of the validation check definition via the smart validation definer

[0246] 1005|1001. Sending the information defined by the smart validation definer to the database / server and cache services / cache server via the neural system / neural server

[0247] 1005| 1002. Checking the information incoming to the cache service with current cache status

[0248] 1005| 1003. Directing the operation according to the cache service's status checks

[0249] 1005| 1004. Creating a new record for a validation operation in the cache

[0250] 1005| 1005. Sending a status message to the user on his / her electronic device via the neural system / neural server to notify that the registration information has been added to the cache 1005| 1006. Saving the registration status sign as in progress on the user side

[0251] 1005| 1007. Transmitting the new information to the insert service of database service via the neural system / neural server in order to save it in the database / server

[0252] 1005|1008. Saving the information incoming to the database service to the database / server via the insert service

[0253] 1005|1009. Transmitting the saved validation control information to the business service via the neural system / neural server to prepare it for use

[0254] 1005|1010. Calling the code builder service by looking at the message content incoming to the business service

[0255] 1005|1011 . Converting defined validation control information into source code with the code builder service 100511012. Injecting source code files into the running system

[0256] 1005|1013. Transmission of the transaction completion message regarding the registrations in the cache to the neural system / neural server

[0257] 1005| 1014. Updating the registration flag status to completed in the cache

[0258] 1005|1015. Transmitting a message that the registration process has been completed to notify the user to the neural system / neural server

[0259] 1005| 1016. Updating the registration flag status to completed on the user screen / device

[0260] 1005| 1017. Updating existing information in the cache

[0261] 1005| 1018. Transmitting the mentioned information to the update service of database service via the neural system / neural server in order to update the same in the database / server

[0262] 1005|1019. Saving the information incoming to the database service to the database / server via the update service

[0263] 1005| 1020. Informing the business service via the neural system / neural server to prepare the saved validation information for use

[0264] 1005|1021 . Calling the code builder service by looking at the message content incoming to the business service

[0265] 1005| 1022. Converting defined validation control information into source code with the code builder service

[0266] 1005| 1023. Injecting source code files into the running system

[0267] 1005|1024. Transmitting the transaction completion message regarding the registrations in the cache to the neural system / neural server

[0268] 1005| 1025. Updating the registration flag status to completed in the cache

[0269] 1005|1026. Transmitting a message to the neural system / neural server that the registration process has been completed to notify the user

[0270] 1005| 1027. Updating the registration flag status to completed on the user screen / device 1005|1028. Sending a status message to the user via the neural system / neural server to notify that the registration information in the cache has been updated

[0271] 1005| 1029. Saving the registration flag status as in progress on the user side

[0272] 1005|1030. Termination of the process by informing the user via electronic device

[0273] 1006|1000. Requesting registration of user-based code add-in definition via smart add-in definer

[0274] 1006|1001. Sending the information defined by the smart add-in definer to the database / server and cache services / cache server via the neural system / neural server

[0275] 1006| 1002. Checking the information incoming to the cache service with current cache status 1006| 1003. Directing the operation according to the cache service's status checks

[0276] 1006| 1004. Creating a new record for a user-based code add-in in the cache 1006| 1005. Sending a status message to the user on his / her electronic device via the neural system / neural server to notify that the registration information has been added to the cache 1006| 1006. Saving the registration status sign as in progress on the user side

[0277] 1006| 1007. Transmitting the new information to the insert service of database service via the neural system / neural server in order to save it in the database / server

[0278] 1006|1008. Saving the information incoming to the database service to the database / server via the insert service

[0279] 1006|1009. Informing the saved user-based code add-in information to the business service via the neural system / neural server to prepare it for use

[0280] 1006|1010. Calling the code builder service by looking at the message content incoming to the business service

[0281] 1006|1011 . Converting user-based code add-in information into source code with the code builder service

[0282] 100611012. Injecting source code files into the running system

[0283] 1006|1013. Transmission of the transaction completion message regarding the registrations in the cache to the neural system / neural server

[0284] 1006| 1014. Updating the registration flag status to completed in the cache

[0285] 1006|1015. Transmitting a message that the registration process has been completed to notify the user to the neural system / neural server

[0286] 1006| 1016. Updating the registration flag status to completed on the user screen / device

[0287] 1006| 1017. Updating existing information in the cache

[0288] 1006| 1018. Transmitting the mentioned information to the update service of database service via the neural system / neural server in order to update the same in the database / server

[0289] 1006|1019. Saving the information incoming to the database service to the database / server via the update service

[0290] 1006|1020. Transmitting the saved user-based code add-in information to the business service via the neural system / neural server to prepare it for use

[0291] 1006|1021 . Calling the code builder service by looking at the message content incoming to the business service

[0292] 1006| 1022. Converting defined user-based code add-in information into source code with the code builder service

[0293] 1006| 1023. Injecting source code files into the running system

[0294] 1006|1024. Transmitting the transaction completion message regarding the registrations in the cache to the neural system / neural server

[0295] 1006| 1025. Updating the registration flag status to completed in the cache

[0296] 1006|1026. Transmitting a message to the neural system / neural server that the registration process has been completed to notify the user 1006| 1027. Updating the registration flag status to completed on the user screen / device

[0297] 1006|1028. Sending a status message to the user via the neural system / neural server to notify that the registration information in the cache has been updated

[0298] 1006| 1029. Saving the registration flag status as in progress on the user side

[0299] 1006|1030. Termination of the process by informing the user via electronic device

[0300] 200| 1000. Making requests from any environment, over the communication network

[0301] 200|1001 . Accepting the request from the external environment through the space portal in the business service

[0302] 200| 1002. Evaluating the validation status of the incoming request parameters by the smart validation definer, if the validation check fails, giving an invalid parameter error message to the requesting environment and returning to the process step, if the validation check is successful, transmitting the necessary information to the consume service via the neural system / neural server

[0303] 200| 1003. Checking the identity information of the incoming request source by the consume service, in case of invalid identity, sending a user error message to the requesting environment via the neural system / neural server and space portal and returning to the process step, in case the identity is confirmed, the validation check of the parameters and values of the incoming request is provided by the smart validation definer

[0304] 200| 1004. Transmitting the relevant identity information from the space portal to the consume service in the business service

[0305] 200|1005. Evaluating the validation status of the incoming request parameters in the consuming service, if the validation check fails, sending an invalid parameter error message to the requesting environment via the space portal and returning to the process step, if the validity check is successful, forwarding the request to the user cache service

[0306] 200| 1006. Checking the identity information of the request source coming to the user cache service, returning to the 200|1004 process step in case of invalid identity, continuing the operations in case of valid identity

[0307] 200|1007. Transmitting the identity information of the request source to the neural system / neural server to ensure that the identity information are saved or updated in the user cache service

[0308] 200|1008. Saving the information coming to the user cache service in a controlled manner and opening the user's session or extending the duration of the session

[0309] 200| 1009. Informing the consume service that the identity information has been registered 200|1010. Transmitting the relevant parameters of the user cache service to the neural system / nerve server and the rule selector, determining the rules and / or user-based code add-ins that will work with the rule selector 200| 1011 . Running specified rules and / or user-based code add-ins via the rule operator 200| 1012. Sending the results to the neural system / neural server for saving to the user cache service, other relevant cache services / cache server and database / server

[0310] 200| 1013. Saving the created information to the user cache service and other related cache services / cache server

[0311] 20011014. Saving the resulting information to the database / server on the database service via the insert service

[0312] 200|1015. Upon completion of the registration process, sending the registration information to the consume service.

[0313] 200| 1016. Consume service transmitting the information to the space portal

[0314] 200| 1017. Space portal transmitting the information to the external environment client

[0315] DETAILED DESCRIPTION OF THE INVENTION

[0316] In this detailed description, the real flexibility and rule-based software development system (3) and method of the invention is described by means of examples only for clarifying the subject matter such that no limiting effect is created.

[0317] In the real flexibility and rule-based software development system (3), the current overview (1 ) refers to general framework of the machines / devices (12), loT devices (13) and programs (11) that companies currently use. Programs (11) are the software that companies currently use. Machines / devices (12) are electronic or mechanical devices currently used by companies. loT devices (13) are loT (Internet of Things) elements that companies currently use. loT devices (13) use the communication network (2) in which physical objects are connected to each other or to larger systems. It is embedded with sensors, software, and other technologies to connect and exchange data with other devices and systems over the Internet. System management (14) is the tools, real people or users with which companies manage their existing systems. Communication network (2) is the network system that enable communication with real flexibility and the rule-based software development system (3). These network systems are as follows;

[0318] TCP / IP protocol,

[0319] Cloud (Azure, AWS, Google etc.) services, gRPC

[0320] Database / server (DB) methods,

[0321] Folder listener

[0322] E-mail. These network types can be increased, they are not limited to the above list. A real flexible and rule-based software development system (3) is a system that has high performance and infinite flexibility, that realises better maintenance of existing situations, that enables users to create new systems and integrate them into their existing ones, and that enables them to obtain more stable and performant system by recreating their existing systems. Integration overview (4) refers to the general framework of integration machines / devices (42), loT devices to be integrated (43) and programmes to be integrated (41 ) that companies will integrate with. It creates a bridge to integrate separate systems that used in company. Programs to be integrated (41) are the software with which companies will integrate. Integration machines / devices (42) are the machines and / or devices that companies will integrate with. loT devices to be integrated (43) are the loT devices (13) that companies will integrate with. Integration management (44) is the interactive tools and real people used for the integrated system.

[0323] Smart definers (100) are definers that contain all the definitions to be made in order to use the rule-based software development system (3) with real flexibility, can be used as a referenced library in other services, can be accessed through the definitions needed in other services, and all definitions made through them are included in the current running application in real time. The business service (200) is the unit that contains the functions that enable the definitions made with smart definers (100). The cache service (300) is a service used for fast generation of results, with a value that can be set parametrically to further increase the performance, and which can be scenarized as if the database / server (4001) operations were performed through it and the result can be given to the user, in principle, in the processes, the information is considered as temporary and not as the result of the actual operation (registration, update and deletion). The actual transaction result is always based on the result from the database / server (4001 ). Therefore, users can perform their transactions very quickly with the cache service (300). Database service (400) is the service through which database / server (4001) operations are carried out and which assumes responsibility for the database / server (4001). The database service (400) can also work as a server service. Many features of some popular databases / servers (4001) become ready for use with the invention. These database / server (4001 ) names could be as follows:

[0324] • MongoDB,

[0325] • Oracle,

[0326] MS-SQL,

[0327] MySQL

[0328] Databases / servers are not limited to the above list. The neural system / neural server (500), smart definers (100), business service (200), cache service (300) and database service (400) is a network that provides a controlled communication flow between modules, which may vary depending on the environment or environments in which they are developed. The neural system / neural server (500) also works as a communication system or communication server which provides communication between units, modules and systems. In addition, the neural system / neural server (500) can communicate with communication networks (2). Smart userinterface definer (1001), in which modular definition is made for the user screens used in electronic device interfaces such as web, desktop computer, laptop, mobile device, the necessary files of the interface template are uploaded, the modular structure is created by selecting from the uploaded files, each successful user interface definition is converted into software code with front-end builder service (2007), and it is the unit through which the definitions created with a modular structure can be used internally and / or another screen module, both facilitating the creation of very complex screens and allowing repeated use due to its modular structure, so that if an interface module needs to be used more than once, it can be used without the need for redefinition. Smart definers (100) can be used / associated with each other in user interface definitions. The smart object definer (1002) is the part that all object information that needs to be used in the smart definers (100), the business service (200), the cache service (300), the database service (400) and the neural system / nerve server (500) are defined over it. In other words; it is the place where all object information will be created which are planned to be used in the application to be developed with the invention. The objects to be used almost everywhere in the invention are in 3 different groups:

[0329] • System Objects: Users cannot change these definitions, they can only use these definitions by referring to other objects.

[0330] • Hybrid Objects: These definitions are created once the system becomes operational. These are predefined objects for user convenience, meaning users can modify them according to their own functionality.

[0331] • User Objects: these are user objects created from scratch by referencing system and hybrid objects.

[0332] In object definitions, definers can be used and associated with each other.

[0333] The smart rule definer (1003) is the unit, on which rules can be created from drawings such as Swimlane or Flow-Charts UML diagrams, rules that will be converted into software code can be defined from diagrams that many people can easily understand, from which diagrams in the external environment are transferred via Al (OCR) or JSON information, and software codes are derived from images accepted by the system, which enables that the rules are automatically converted into software code via the code builder service (2008) by transmitting the defined rules to the application and are added to the running codes of the application used, thus, which provides significant savings from the time lost in the interpretation of rules, which causes the performance problems experienced in other rulebased systems, and has a definition section through which users can create their own rules and include them in the running application, when the rule is defined, which automatically creates the necessary test environment, enables the newly added or updated rules to be translated into software code and added to the existing application(s) on runtime, in this way, which makes it possible to continue using the application without interrupting the running application, depending on the necessity and user choice of the rules, the unit is operated on two principles: synchronous and asynchronous. As mentioned, the execution of the rules is provided through two principles: synchronous and asynchronous, and thus, users can choose synchronous or asynchronous operation depending on the necessity of the rules. Usage of functions created by rule definition:

[0334] • In creating the information on the screens that the end user (Client) sees,

[0335] • In the control and registration processes of information generated by the use of end user screens,

[0336] • In the functions to be used to test input and output information according to the created scenarios for testing purposes,

[0337] • In performance tests of the application(s) to be created,

[0338] • With functional testing, certain functions in the application(s) tests,

[0339] • In partial security tests,

[0340] • In integration testing, testing whether different components of the application work together in harmony,

[0341] • In functions that specify what kind of operations and how it will be performed in the defined user interface modules,

[0342] • In the invention, control and operation of the behaviour of all used objects within themselves, the relations of the objects with each other, the state of relations between the objects and the places where the objects will be used,

[0343] • In time-defined scheduled transactions,

[0344] • In checking the validation status of the output information formed as a result of the input information,

[0345] • Bi-directional use between code snippets created by users.

[0346] • Use / Associate with all definers in rule definitions.

[0347] Smart scheduled task definer (1004) is the unit where the rules that are desired to be performed once or periodically in the created applications can be selected. It can be used / associated with all definers in time-dependent function definitions. Smart validation definer (1005) are rule definitions that provide validation control in the application of the created rules, during the input of information, during the output information generated by the input of information (not the registration process), in the smart user-interface definers (1001) and before the registration process. It can be used with all definers in validation definitions. Smart add-in definer (1006), through which companies with software capability can add their own unique program particles (Function), special requests can be solved by adding the desired libraries to the existing library, company-specific functions can be added to the application, companies can make special developments, and it is the definition part where the rules defined in the smart rule definer (1003) can be called from the added code snippets, the working type of the added code snippets can be selected as synchronous or asynchronous, the environment required for testing is automatically provided when the add-in is saved, newly added or updated add-ins can be included in the existing application while running and there is no interruption. It allows companies to contribute to their competitive dominance with their own developments. Newly added or updated add-ins will be added to the existing application on runtime. In this way, it will be possible to continue using running applications without interruption. Theme definer (10011) is the section through which the user screens will be defined. Other modules can also be included with module definitions. Thanks to this definition flexibility, the following is achieved:

[0348] • They will be able to achieve many to one: By being able to define different particles (modules) on a screen separately, concentration on the work to be done and therefore increased efficiency is achieved.

[0349] • With modularity, polymorphism has been achieved. In other words, great advantages are gained by using a module on a plurality of pages.

[0350] The event objects unit (10012) is a description of the most basic event-based functions, selected from rules defined by the smart rule definer (1003) or from add-in code snippets defined by the smart add-in definer (1006), which can be used in information input objects in modules defined by the theme definer (10011). The OnFocus event unit (100121 ) is the place where the function selected from the rules defined by the smart rule definer (1003) or the add-in code snippets defined by the smart add-in definer (1006) is defined, which is to be executed if an event is thrown when the input object is activated with the mouse or keyboard. The output event unit (100122) is the place where the function selected from the rules defined by the smart rule definer (1003) or from the add-in code snippets defined by the smart add-in definer (1006) is defined, which is to be executed when the information input object is exited and an event is thrown. The change event unit (100123) is the place where the function selected from the rules defined by the smart rule definer (1003) or from the addin code snippets defined by the smart add-in definer (1006) is defined, which is requested to be executed during each change of information in the input object and in the event of an event being thrown. The MouseHover event unit (100124) is the place where the function selected from the rules defined by the smart rule definer (1003) or from the add-in code snippets defined by the smart add-in definer (1006) is defined, which is requested to be executed when the mouse pointer hovers over the input object and an event is thrown. The page load / page close event unit (10013) is a description of a function selected from the rules defined by the smart rule definer (1003) or from the add-in code snippets defined by the smart add-in definer (1006), which can be triggered during the display of modules defined by the theme definer (10011), during the registration (new, update and delete) process and during registration closure. The operation unit page before-load (100131) is the place where the function selected from the rules defined by the smart rule definer (1003) or from the addin code snippets defined by the smart add-in definer (1006) is defined, which is to be executed before the module to be opened and the sub-modules associated with this module are loaded on the screen. The operation unit page after-load (100132) is the place where the function selected from the rules defined by the smart rule definer (1003) or from the add-in code snippets defined by the smart add-in definer (1006) is defined, which is to be executed after the module to be opened and the sub-modules associated with this module and thus all objects have been loaded on the screen. The operation unit page before-post (100133) is the place where a function is defined, selected from rules defined by the smart rule definer (1003) or add-in code snippets defined by the smart add-in definer (1006), which is triggered before the execution of the function to which the buttons for registration (insert, delete and modify) operations attached to a module. The operation unit page after-post (100134) is the place where a function is defined, selected from rules defined by the smart rule definer (1003) or add-in code snippets defined by the smart add-in definer (1006), which is triggered after the execution of the function to which the buttons for registration (insert, delete and modify) operations attached to a module. The operation unit page before-close (100135) is where a function is defined, selected from rules defined by the smart rule definer (1003) or add-in code snippets defined by the smart add-in definer (1006), which is executed before the close operation when a close request is sent to a module. The operation unit page after-close (100136) is where a function is defined, selected from rules defined by the smart rule definer (1003) or add-in code snippets defined by the smart add-in definer (1006), which is executed after the close operation when a close request is sent to a module. The Operation Unit Page On-Show (100137) is the place where a function is defined, selected from rules defined by the smart rule definer (1003) or add-in code snippets defined by the smart add-in definer (1006), which is executed after the visibility of a module has been switched from hidden to visible. The Operation Unit Page OnSent Backward (100138) is where the function is defined, selected from rules defined by the smart rule definer (1003) or add-in code snippets defined by the smart add-in definer (1006), which is executed after the visibility of a module has been switched from visible to hidden mode. The page validation unit (10014) is the place where functions selected from the rules defined by the smart rule definer (1003) or from the add-in code snippets defined by the smart add-in definer (1006) are defined for the evaluation of the validation status of objects linked to modules created by the smart user-interface definer (1001 ). The Page Before-Load Validation Unit (100141) is the place where the functions selected from the rules defined by the smart rule definer (1003) or from the add-in code snippets defined by the smart add-in definer (1006), which are defined for the evaluation of the desired validation status before loading the modules created with the smart userinterface definer (1001), are defined, so that the status of other modules and / or objects is subjected to a validation check before the relevant module is opened. The Page After-Load Validation Unit (100142) is the place where the functions selected from the rules defined by the smart rule definer (1003) or from the add-in code snippets defined by the smart add-in definer (1006), which are defined for the evaluation of the desired validation status after loading the modules created with the smart user-interface definer (1001), are defined, so that the status of other modules and / or objects is subjected to a validation check after the relevant module is opened. The Page Before-Post Validation Unit (100143) is defined for the evaluation of the desired validation status of modules created with the smart user-interface definer (1001) before registration (new, update or delete), is the place where functions selected from the rules defined with the smart rule definer (1003) or from the add-in code snippets defined with the smart add-in definer (1006) are defined, allowing the status of their own objects and / or other modules and / or objects to be checked for validity before saving (new, update, delete) in the relevant module. The Page After-Post Validation Unit (100144) is defined for the evaluation of the desired validation status of modules created with the smart user-interface definer (1001) after registration (new, update or delete), is the place where functions selected from the rules defined with the smart rule definer (1003) or from the add-in code snippets defined with the smart add-in definer (1006) are defined, allowing the status of their own objects and / or other modules and / or objects to be checked for validity after saving (new, update, delete) in the relevant module. The flexible object definer (10021 ) is the part where the object types that reference the specified objects used everywhere in the generated application. Object definer (10022) is the part where attribute and / or object properties information such as version, step, form, generated information are defined in the created application. The relational definer (10023) is the part where the relationship between all definitions that can be made with smart definers (100) is defined. Multilingual definer (10024) is the language library used to translate all definitions that can be made with smart definers (100) into the desired languages. The type of rule definer (10031 ) is the part where users can define their own rule types. In this way, it is possible to run all rules of a special rule type in rules and add-in code snippets. Here, the basic rule types of the invention are also loaded by default. The following features can be defined as the type specified by users in the rule type definition details: • Synchronous I Asynchronous operation method can be choosen,

[0351] • Can be connected to the basic rule types mentioned above.

[0352] These definitions can be used in add-ins and / or rule definitions. But the point to be considered here is; if there are different selections in the type properties in the add-in and rule definitions, it deactivates the ones in the type definitions. The group of rule definer (10032) is the part where the rules will be grouped among themselves according to any feature. A naming grouping can be made according to rule types with the type of rule definer (10031) and / or the rule group of rule definer (10032) depending on the need. In this way, it is possible to run all rules of a special rule type in rules and add-in. The feature of deactivating the previous definition is also available here. The rule definer (10033) is the definition of the desired work with flow diagrams to fulfill the company's requests. Rules can be thought of as methods or functions in software development. The purpose of this is to ensure that the application runs as if it were written during code development, without the need for rule interpreter during the execution of the rules. In this way, the problem of wasting time caused by executing the rules by commenting them line by line is solved and a significant performance increase is achieved. In the rules:

[0353] • Added functions can be called with the defined smart add-in definer (1006).

[0354] • Synchronous or asynchronous operation type can be selected.

[0355] • Return values can be selected.

[0356] The scheduled task definer (10041) is the part where tasks (rules or Add-Ins) are defined, which are requested to run in the programme(s) to which they are to be applied in certain periods, according to date and / or time value, which are automatically converted into software code with front-end builder service (2007) or code builder service (2008), and which are added to the running codes of the application used with rule injection unit on run time (2003) or add-in injection unit on run time (2004). The object validation unit (10051 ) is the validation check that can be applied to all defined objects. The OnFocus validation unit (100511) is the place where the function is defined, which can only check the validation of objects in user interfaces, which is triggered by the relevant event when the information is entered into any object to be entered, which is selected from the rules defined with the smart rule definer (1003) or from the add-in code snippets defined with the smart add-in definer (1006). The OnExit validation unit (100512) is the place where a function is defined which can only check the validity of objects in user interfaces, which is triggered by an event in the previous object when the input is made by leaving any object to be entered and selecting another object, which is selected from the rules defined by the smart rule definer (1003) or add-in code snippets defined by the smart add-in definer (1006). The OnChanged validation unit (100513) is the place where a function is defined that can check the validity of both objects in user interfaces and program objects running in the backend, triggered by a change of value (Event) of any object, selected from rules defined by the smart rule definer (1003) or from add-in code snippets defined by the smart add-in definer (1006).

[0357] The rule selector (2001) is the unit that detects the function to be triggered by the event activated by any process, which is selected from the rules defined by the smart rule definer (1003) or from the add-in code snippets defined by the smart add-in definer (1006) in order to prepare it for execution, creates the priority que according to the rule types with the type of rule definer (10031) and transmits the task to the rule operator (2002) for execution. If we want to express it in terms of classical software development; it is the binding structure in which an object is linked to the function to be executed for any event. The rule operator (2002) is the mechanism that enables the execution of a function transmitted from the rule selector (2001). If we want to express it in terms of classical software development; it is a structure that allows the function to be run in any event of an object to be triggered. The rule injection unit on run time (2003) is the mechanism that generates software development code from user-defined flowcharts and enables the rules defined by the smart rule definer (1003) to be instantly incorporated into the current running system (On Runtime). Add-in injection unit on run time (2004) is a mechanism that allows user-defined code snippets and user-developed software code to be instantly incorporated into the current running system (On Runtime) with the smart add-in definer (1006). The consume service (2005) is an intermediate layer that enables the execution of the relevant rules on demand, via the rule selector (2001 ) and the rule operator (2002), and is responsible for the transmission of the results back, enabling work requests from user interfaces and other services to communicate with other services and user interfaces only through itselves. In microservice architecture, Saga pattern or a similar pattern-theme is used to control operations and error conditions between services. Space portal (2006) is the portal, which is responsible for enabling communication with applications not developed within the invention, which can communicate with other applications in many different ways and / or according to the environment in which the invention is implemented, (Microsoft Azure, AWS, Google, customers' closed systems, etc. products) which enables the realisation of requests from environments other than the invention or information from the invention to be sent to the outer world, after making the necessary controls and arrangements for each incoming request, sends the relevant request to the consume service (2005) and waits until the request is completed, which checks and / or edits the result coming from the consume service (2005) and transmitting the result with feedback to the system which makes the request, or taking action without being transmitted to the consume service (2005) depending on the type and identity information of the request. Front-end builder service (2007) is the unit, which converts the user interface information defined by the smart user-interface definer (1001 ) into front-end software code for the web (Angular or React) or desktop (WPF), which converts the request definitions generated with the code builder service (2008) and the definitions made for the operation of the incoming responses / requests, the themes created to be used on different screens, the activities performed in the page areas, operation of objects unit (10012), OnFocus operation unit (100121 ), output operation unit (100122), change operation unit (100123), MouseHover operation unit (100124), page load / page close operation unit (10013), operation unit page before-load (100131), operation unit page after-load (100132), operation unit page beforepost (100133), operation unit page after-post (100134), operation unit page before-close (100135), operation unit page after-close (100136), operation unit page on-show (100137), operation unit page onsent backward (100138), page validation unit (10014) and their submodules into front-end software code. Code builder service (2008) is the unit, which runs after all successful registration operations with the smart object definer (1002), smart rule definer (1003), smart scheduled task definer (1004), smart validation definer (1005) and smart add-in definer (1006), which enables the defined information to be converted into software code, which is responsible for translating rule diagrams transferred to the system via Al into software code, and translating rules transferred to the system from another environment (json, xml, etc.) into software code, which allows users to automatically create themes and user interfaces without front-end software development knowledge. The user cache service (3001 ) is the service, which ensures that the request coming to the consume service (2005) with its parameters and the response to the incoming request are kept in the cache, can also be used as a temporary data storage location in transactions (evaluation or calculations) that do not require recording in the database / server (4001) and thus provides increased performance since there is no need to read large chunks of data from the database / server (4001 ) each time. Each incoming request must have a unique user number, a key is created with this identification number, and all requests and responses from the same user / system are cached with this key. Requests that require a database / server (4001) operation are first executed here as if the transaction was made in the database / server (4001 ). With this way of working, a huge performance increase is aimed in responses to requests. Of course, these operations will not be the reference records, the reference records of the registry operations are always the results coming from the database / server (4001 ). The page cache service (3002) is the service, which ensures that the information about the objects in the modules defined by the smart user-interface definer (1001 ) is preserved with the key on it, is valid for the relevant module as a result of users’ data entry, ensures that the generated data is cached, in order for the module-based results can be used from the cache, which is associated via a unique key in the user cache service (3001) and corresponding keys in the object cache service (3003). The object cache service (3003) is the service that ensures that objects identified with the smart object definer (1002) are kept in the cache and associates the objects used in the pages with the page cache service (3002) through the necessary keys. The relational cache service (3004) is the service that ensures that the relationship conditions and hierarchy of related objects are kept in the cache. The main headings of relationship types are as follows:

[0358] • Predefined Relationship: Specifies the relationships between information created for use in the application.

[0359] • Runtime Relationship: Specifies the relationships between the information created while using the application.

[0360] Multilingual cache service (3005) is the unit that caches information of each field in other languages defined by smart definers (100) for the use of the created application. The ecosystem's own cache service (3006) is the unit that ensures that the information created by the users in the developed application definer (1003), smart add-in definer (1006) and smart scheduled task definer (1004) is kept in the cache.

[0361] The database / server (4001) is the storage area on which the definitions are recorded, on which the result data produced with real flexibility and the use of the rule-based software development system (3) and method, on which all kinds of transactions are recorded by logging, and which has data storage systems created to support multi-language. Any saved information will not be actually deleted, it is stated that it has been deleted by flagging and / or by transferring to another table. There will be no possibility of deleting or changing logs, they can only be viewed (read-only). The insert service (4002) is the unit that allows the new information created to be saved to the database / server (4001). The update service (4003) is the service used when making updates on previously recorded data in the database / server (4001 ) or when making a change in the flag used to indicate that the record has been deleted. Query service (4004) is the service that queries the records in the database / server (4001) and responds to data requests.

[0362] All services, definers, units and modules used in the real flexible and rule-based software development system (3) run on at least one server (also defined as application service in cloud solutions). However, the most important feature of the real flexibility and rule-based software development system (3) is that it can work with hard-coded software performance. In existing rule-based systems serious performance decreases, server crashes, and transaction disruptions may occur while performing rule base operations. However, such problems do not occur in this real flexible and rule-based software ecosystem (3). Because the system works hard-coded and does not affect the performance of the databases / servers (4001 ). Frequently accessed hard-coded data can be stored using cache mechanisms. In this way, it helps to reduce accesses to the database / servers (4001 ) and increase the performance of the application / software / add-ins. Caching strategies can include both inmemory caches (Redis, Memcached, etc.) and file-based caches. Additionally, data updates and maintenance become more manageable due to the modular structure of the system. By using this software ecosystem, any person, firm, company, institution or organization can develop software without any software knowledge in the industry of military, engineering, chemistry, biology, physics, banking, health, law, construction, education, insurance or any other field.

[0363] Figure 1 is an overview chart illustrating the position of the invention in use, i.e. the location of the deployment of the invention, showing how the invention will be used and / or integrated with existing software and / or systems. Figure 2 is a general chart showing the modules planned in the invention structure and the communication between them. Figure 3 is an overview of the submodules that will form the smart definers (100). Figure 4 is the part where user interfaces can be created without software knowledge. In this way, it is possible to prepare the screens that end users will see, even without software knowledge, by using pre-prepared screen modules with the invention software. After registration in all submodules of this subject, web or desktop interface software codes are automatically generated and saved with the front-end builder service (2007). As can be seen from the mock-up created for the definition, the information of the selective fields consists of the information (objects, rules, add-in, etc.) of this software ecosystem created with smart definers (100). Thus, the front-end parts of web or desktop applications can be prepared without writing a single line of code for user interfaces. A mock-up is a draft view, model, sketch of an application or website in the design phase, drawn before it becomes a realistic prototype. Figure 5 is an overview chart of the part where smart object definers (1002) where objects planned to be used everywhere and at every stage of the invention, and all the features of these objects will be defined. Figure 6 shows an overview of the parts that make up the smart rule definers (1003), that is, the rule-based system to be operated, which is one of the other main subjects of the invention. The rules defined by all the sub-modules under this heading are automatically translated into software code to be imported into the application with the front-end builder service (2007) or the code builder service (2008) and inserted into the running code of the application used with the rule injection unit on run time (2003) or the add-in injection unit on run time (2004). Thus, significant time savings are made from the the interpretation of rules (Interpreter), which causes the performance problems experienced in other rule-based systems. The operation of the rules is achieved through two principles. These are synchronous and asynchronous principles. In this way, synchronous or asynchronous operation can be implemented depending on the requirements of the rules. Usage areas of functions created by rule definition:

[0364] • In creating the information on the screens that the end user (Client) sees,

[0365] • In the control and registration processes of information generated by the use of end user screens,

[0366] • In testing transactions; that is, in the functions to be used to test input and output data according to the created scenarios,

[0367] • In performance tests of the applications to be created,

[0368] • With functional testing, testing certain functions in the applications,

[0369] • In partial security tests,

[0370] • In integration testing, testing whether different components of the application work together in harmony,

[0371] • In the Figure 8, for the functions that specify what kind of operations and how to perform them in the user interface modules defined in the smart user-interface,

[0372] • In the Figure 9, in regulating and / or controlling the behaviour of all objects to be used in the invention by the smart object definer (1002) within themselves, the relations of the objects to each other, the relation conditions between the objects and the places where the objects are to be used,

[0373] • In time-defined planned operations with a smart scheduled task definer (1004) (see Fig. 11 ),

[0374] • In control of the validation status of the output data created as a result of the data entered (Input) with the smart validation definer (1005) (see Fig. 12),

[0375] • Bidirectional use is possible between code snippets created by users with the smart add-in definer (1006) (see Fig. 22 and Fig. 23).

[0376] After successful registration in all sub-modules under this heading, this data is converted into software code with the front-end builder service (2007) or code builder service (2008) and made available for use.

[0377] Figure 7 is the part where the smart scheduled task definer (1004), that is, the rules or addins that will run according to date and / or time information in the application created with the invention, is defined. Figure 8 shows the smart validation definer (1005), that is, an overview of the validation checks required for input objects and the object information generated after the operation of the rules with these input objects and before the registration (new registration, update and deletion) of objects in modules defined by the smart user- interface definer (1001). The smart validation definer (1005) validation check can be used both when the information of the objects on the user screens changes (Front-end) and when the values of the object running in the backend (Backend) change. After successful registration in all modules under the verification definer heading, they are translated into software code with the front-end builder service (2007) or code builder service (2008) and added to the running application with the rule injection unit on runtime (2003) or the add-in injection unit on runtime (2004). Figure 9 is the illustration of the business service (200) and is the part responsible for carrying out the work in the invention mechanisms of the business service (200). In other words, it is responsible for the management of all processes from initiation to completion of the invention. Figure 10 shows an overview of caching processes. Request-response data given to other services of the invention is kept in these caches for a certain period of time. The cache service (300) is responsible for making the information held in the cache available for the same requests. Caching is also done outside the servers where the cache service (300) is run. In other words, caching is of course also done on the servers where the application is run, but the work of the cache service (300) servers in the invention is only caching. Thus, it is aimed to avoid giving too much workload to the primary server on which the application runs. When servers are created for different tasks, they are easier to manage since they will be isolated servers, and they contribute significantly to increased performance. All services below the cache service (300) can instantly incorporate differences in definitions (via versioning). Figure 11 is a diagram showing the general outline of the database / server (4001 ) operations of the database service (400), that is, the information in the creation of the invention application and the information occurring during its usage. As can be guessed, CQRS (Command Query Responsibility Segregation) design from the diagram is applied. Database / server (4001 ) clusters (DB-Cluster) are created depending on the situation. Figure 12 is a mock-up screenshot showing the general outline of the structure responsible for creating the object definitions used in the application of the invention with the object definer (10022). After successful registration, the registration is translated into software code with the front-end builder service (2007) or the code builder service (2008) and inserted into the running application with the rule injection unit on runtime (2003) or add-in injection unit on runtime (2004). A representation of how the ‘Person’ object can be created with its subattributes is shown. Its equivalent in classical software development with C# language: class Person { }

[0378] . Figure 13 is a sample screenshot of how another object called ‘Name’ can be defined with the object definer (10022) under the defined ‘Person’ object. In this way, a structure similar to the class structures in classical software development can be made by people without software knowledge, thus providing infinite flexibility in class definitions. After successful registration, it is converted into software code by the front-end builder service (2007) or code builder service (2008) and added to the running application with the rule injection unit on runtime (2003) or the add-in injection unit on runtime (2004). Its equivalent in classical software development with C# language: class Person

[0379] { public string Name { get; set; }

[0380] }

[0381] . Figure 14 is a sample screen used to create user interfaces themes in smart user- interface definer (1001 ). After successful registration, it is converted into software code by the frontend builder service (2007) or code builder service (2008) and added to the running application with the rule injection unit on runtime (2003) or the add-in injection unit on runtime (2004). This is a sample (Mock-up) screenshot to prepare the user screen / device where employee information can be recorded. Figure 15 is a sample screenshot for employee information entry that users will see with the defined information. Figure 16 is a sample screenshot where user login is made via smart user-interface definer (1001). After successful registration, it is converted into software code by the front-end builder service (2007) or code builder service (2008) and added to the running application with the rule injection unit on run time (2003) or the add-in injection unit on runtime (2004). This is a sample (Mock-up) screenshot to prepare the screen where users will log in to work in the prepared application. Figure 17 is a sample screenshot where users can define themselves with employee information and create users for user login in order to log in to the application with the defined information. Figure 18 is a sample screenshot of how, in addition to the existing structure developed with the invention, users can include code snippets they have developed as add-ins (Add-In) into the system with the smart add-in definer (1006) according to their own needs. After successful registration, it is converted into software code by the front-end builder service (2007) or code builder service (2008) and added to the running application with the add-in injection unit on runtime (2004). Figure 19 is a sample screenshot where users can create rules for their own operations with the smart rule definer (1003) without software development knowledge. After successful registration, it is translated into software code with the front-end builder service (2007) or code builder service (2008) and added to the running application with the rule injection unit on run time (2003). This is a sample screen that shows how to evaluate the situation created as an example for the debt / lending transaction.

[0382] Figure 20 is a diagram illustrating how the definition of a rule with a smart rule identifier (1003) can be incorporated into an existing application in general terms and following the steps in the invention. In the diagram, not all steps of the services are shown for simplification. Figure 21 has the same processes as Figure 23, except that instead of rule definition, add-in definition is used with the smart add-in definer (1006). Of course, although the processes are the same for both requests, there are differences in content. In the diagram, not all steps of the services are shown for simplification. Figure 22 is an ecological general diagram showing the communication between the services and modules working on finding, consumption and obtaining the result, that is, the output of using the invention. Figure 23 is a representative illustration of the user interface creation process with smart user-interface definer (1001 ). Figure 24 is a representative illustration of the object defining process with smart object definer (1002). Figure 25 is a representative illustration of the rule definition process with smart rule definer (1003). Figure 26 is a representative illustration of the definition process of functions that will run on a scheduled basis with the smart scheduled task definer (1004). Figure 27 is a representative illustration of the validation control definition process with smart validation definer (1005). Figure 28 is a representative illustration of the user-based code add-in identification process with smart add-in definer (1006). Figure 29 is a representative illustration of the process of processing the request coming from outside to the invention and the request created in the invention itself.

[0383] As can be seen from the items mentioned in the prior art, the creation of the infrastructure, that is, the creation of the servers on which the application will run, and the necessity of making the network communication between these servers every time, and the security problems caused by the communication network (2), the maintenance, monitoring / tracking, and updating of the infrastructure are eliminated with our invention. In addition, thanks to the result-oriented software ecosystem, the time it takes for the desired software applications to become operational are significantly shorter. Time calculation is not directly proportional to the size of the project, and the larger the project to be commissioned, the greater the time savings.

[0384] With the software ecosystem of our invention, it is possible to develop the following operations without writing a single line of code; supply chain management, integration with loT devices (13), development of software integrated into programmes (11) used in the construction sector, development of stock exchange management software, creation of the necessary base for the training of artificial intelligence software, development of software specific to the construction sector or development of software or add-ins integrated into programmes used in any sector, creation of online-shop systems, development of software for the health sector (pharmacy, hospital, polyclinic, etc.), development of software used for both mapping and management processes for companies engaged in transport business, development of ERP (Enterprise Resource Planning) software specific to companies, realisation of software solutions that include very specific issues for insurance companies.

[0385] In the software ecosystem to be developed with our invention, query features that can be applied to NoSQL, MS-SQL, Oracle and MySQL databases / servers (4001) are offered to users. In the software ecosystem, only one program (11) can be created with all the rules. This is the content of a completely flexible software ecosystem. It is a software that works entirely with the rules determined by the users, that is, it is about creating a system that will work from the beginning to the end of any transaction.

[0386] To put it simply, if the payment of an invoice is not approved within X days, it is a rule that can be created to issue a warning for the unapproved payment. Each company determines the X day here according to itself and a rule is created accordingly. However, in our invented software ecosystem, All the information and steps required for the company's invoice creation and payment tracking processes can be defined as a rule. Our invention refers to a management model consisting of rules in every aspect.

[0387] Our invention developed with the software ecosystem can also be used in situations requiring controlled and intermediate operations between different devices and / or programmes (11). In such cases, the user interface may be unnecessary. There is no obligation to use the user interface in our invention. In other words, our invention can also be considered as an intermediate layer to be positioned between different systems and / or devices. There is an interface design that will be available to users for reporting according to the database / server (4001) used. The queries written here are recorded and these queries can also be used in rules and / or add-in definitions.

[0388] In companies without a software development team:

[0389] With our invention, the company personnel who do not have software knowledge but are experts in their field of work are given the ability to create the entire programme or programme modules in line with their own wishes based on their own company needs. Our invention is an invention that greatly simplifies the achievement of the target programme by fully or partially automating each process individually, where at least one or all of the following are needed according to the programme needs.

[0390] • Front-end development,

[0391] • Back-end development,

[0392] • Database (DB) / server (4001 ),

[0393] • Integration with other programs (11). These types of companies can find solutions within themselves in a very short time, without being dependent on outside sources, whether it is a completely new program and / or adding new features to a previously developed program with this invention, thanks to the ready environment where they can implement / develop their own requests with the invention. Thus:

[0394] • Companies do not have to wait for the software company to develop the program and therefore can implement the necessary development immediately.

[0395] • Software development costs are decreasing significantly. It is possible to transfer the financial power formerly transferred to software to other channels.

[0396] • The communication problem of conveying requests to other companies or individuals who do not have any knowledge about the operation of the company is eliminated.

[0397] • Companies do not have to disclose their confidential information, commercial operations, suppliers or solution partners to another institution or person.

[0398] In companies or software companies that have a software developer team:

[0399] With this invention, companies with software capabilities have the same advantages as those without a software development team. Furthermore;

[0400] • Customers' requests can be completed in a very short time.

[0401] • They are enabled to take part in the competition with lower costs.

[0402] • Data manipulation is very difficult and / or impossible because the database design is very complex and access is blocked. It is possible for them to create their own rules and libraries and make them available by developing add-ins with their own software developers (Figure 19).

[0403] In addition, our invention optionally eliminates either completely or most of the following requirements:

[0404] • Front-end Software Development

[0405] • Back-end Software Development

[0406] • Database (DB)-Design

[0407] • Creation of server infrastructures.

[0408] • Another problem with updates in software projects is that updates are made separately for each project. When software projects are developed with this invention, the update problem will not be a serious problem, because updating through a single project will be sufficient. Except for Add-Ins, all other updates are made available to all customers at the same time with the update of the invention, that is, customers do not have to worry about the update: Changes related to operating systems, Updates in software development language versions, Updates in database (DB) systems, Updates in the software libraries

[0409] • Thanks to this invention, it has been possible to operate the software with continuous active requests for many years. Because in this invention there is truly infinite flexibility and systematic versioning of the rules.

[0410] • In applications created with this invention, newly added features are instantly integrated into the application without any interruption. with smart user-interface definer

[0411] Users can either design an interface according to their needs by choosing one of the readymade template and user interface modules that come with the ecosystem developed with the invention, or they can upload a completely different template to this ecosystem. In order for a different template to be uploaded to the ecosystem, the files belonging to the template specified by the user can be uploaded via the file upload button via the smart user- interface definer (1001) (Figure 14). By uploading the file, the necessary registrations are created in this ecosystem and these templates become available in modular interface definitions.

[0412] The saving request made with the relevant selections from the reference data types flexible object definer (10021), object definer (10022), relational definer (10023) where the relationship between all definitions is defined, and multilingual definer (10024) information created with the smart object definer (1002) for modular interface definitions from the interface templates registered in the ecosystem developed with the invention is indicated.

[0413] In order to realise the user interface creation / update request by the smart user-interface definer (1001 ), the database / server (4001 ) is registered by sending a message to the page cache service (3002) and the relational cache service (3004) from the cache services (300) via the neural system / neural server (500). The page cache service (3002) and the relational cache service (3004) check the current cache status of the incoming request. With this control evaluation, it decides whether there is a request to create or update a new registration. In short, the process step of creation a user interface with the smart userinterface definer (1001) includes the following process steps;

[0414] • uploading the files of an interface template to be used via the smart user-interface definer (1001 ) and creating registration information in the system (100111000), • selecting smart object definitions for uploaded interface templates via the smart userinterface definer (1001 ) (100111001 ),

[0415] • requesting the registration of the screen definition information that users will see (1001 |1002),

[0416] • sending the information identified by the smart user- interface definer (1001) to the database / server (4001) and cache services (300) / cache server such as page cache service (3002), relational cache service (3004) via the neural system / neural server (500) (1001 |1003),

[0417] • checking the information incoming to the page cache service (3002) and the relational cache service (3004) with the current cache status (100111004),

[0418] • directing processing according to the status checks of the page cache service (3002) and the relational cache service (3004) (100111005),

[0419] • termination of the process by informing the user via electronic device (100111032).

[0420] Requesting the creation of a new user interface:

[0421] A new registration is created in the page cache service (3002) and / or the relational cache service (3004) with the request information. The new register creation status information in the caches is marked as in progress. This flag information is updated as success after all registration processes are successful. If an error is received in any step of the registration process, it will be updated as failed. From the cache services (300), the user receives a status message that the saved information has been temporarily added via the neural system / neural server (500). At the same time as the message is transmitted to the cache services (300), the necessary information is sent to the insertion service (4002) of the database services (400) via the neural system / neural server (500) to create the actual record in the database / server (4001 ).

[0422] The information incoming by the insert service (4002) is saved in the database / server (4001). After the registration process is completed, a message is sent to the front-end builder service (2007) of the business service (200) by the neural system / neural server (500) to make the interface definition ready for use. Front-end builder service (2007) creates a user interface (Web / Desktop / Mobile) front-end file within the framework specified by the user upon the request to the service. These files are uploaded to the relevant server and / or software as a service (SaaS) system. After the files have been uploaded to the current system, messages are sent to the page cache service (3002), the relational cache service (3004) and other relevant cache services (300), to inform the user's definition screen / device that the registration status information has been successful via neural system / neural server (500). The registration status sign information is changed to success in the page cache service (3002), relational cache service (3004) and other related cache services (300). Registration status sign information is updated as success on the user definition screen / device.

[0423] In short, if you want to create a new user interface;

[0424] • sending a new registration request to the page cache service (3002) and the relational cache service (3004) (100111006),

[0425] • sending a status message to the user on his / her electronic device via the neural system / neural server (500) to notify that the registration information has been temporarily added to the cache (100111007),

[0426] • saving the registration status sign as in progress on the user side (100111008),

[0427] • transmitting the new information to the insert service (4002) of database service (400) via the neural system / neural server (500) in order to save it in the database / server (4001) (1001 |1009),

[0428] • saving the information incoming to the database service (400) to the database / server (4001 ) via the insert service (4002) (100111010),

[0429] • informing the business service (200) via the neural system / neural server (500) to prepare the saved information for use (100111011),

[0430] • calling the front-end builder service (2007) by looking at the message content coming to the business service (200) (100111012),

[0431] • creating user interface front-end files using the relevant interface information via the frontend builder service (2007) (100111013),

[0432] • uploading the relevant files created for the user interface to the server (100111014),

[0433] • transmitting the transaction completion message for the registration in the cache to the neural system / neural server (500) (100111015),

[0434] • updating the registration flag status to completed via the page cache service (3002) and the relational cache service (3004) (100111016),

[0435] • transmitting a message to the neural system / neural server (500 that the registration process has been completed to notify the user from the user screen / device (100111017),

[0436] • updating the registration flag status to completed on the user screen / device (100111018).

[0437] In the current III definition update request:

[0438] Information regarding the page cache service (3002) and / or the relational cache service (3004) is updated with the request information. Status information for registration updates in caches is marked as processing. This flag information is updated as success after all update processes are successful, is updated as failed if an error is received in any step of the registration process. Temporary updated message status information is sent to the user via the neural system / neural server (500) of the information updated in the cache services (300). At the same time as the message is transmitted to the cache services (300), the necessary information is sent to the insertion service (4002) of the database services (400) via the neural system / neural server (500) to create the actual record in the database / server (4001). The information incoming by the update service (4003) is updated in the database / server (4001 ). After the update process is completed, a message is sent to the front-end builder service (2007) of the business service (200) by the neural system / neural server (500) to make the interface definition ready for use. Front-end builder service (2007) creates a user interface (Web / Desktop / Mobile) front-end file within the framework specified by the user upon the request to the service. These files are uploaded to the relevant server and / or software as a service (SaaS) system. After the files have been uploaded to the current system, messages are sent to the page cache service (3002), the relational cache service (3004) and other relevant cache services (300), to inform the user's definition screen / device that the registration status information has been successful via neural system / neural server (500). The registration status sign information is changed to success in the page cache service (3002), relational cache service (3004) and other related cache services (300). Registration status sign information is updated as success on the user definition screen / device.

[0439] If you want to update the existing user interface definition, the following process steps are performed;

[0440] • sending a request to update existing information to the page cache service (3002) and / or the relational cache service (3004) (100111019),

[0441] • transmitting the mentioned information to the update service (4003) of database service (400) via the neural system / neural server (500) in order to update the updated information in the database / server (4001) (100111020),

[0442] • saving the information incoming to the database service (400) to the database / server (4001) (1001 |1021),

[0443] • sending the saved information to the business service (200) via the neural system / neural server (500) to prepare it for use (100111022),

[0444] • calling the front-end builder service (2007) by looking at the message content incoming to the business service (200) (100111023),

[0445] • creating user interface front-end files using the relevant interface information via the frontend builder service (2007) (100111024), • uploading the relevant files created for the user interface to the server (100111025),

[0446] • transmitting the transaction completion message for the registration in the cache to the neural system / neural server (500) (100111026),

[0447] • updating the registration flag status to completed in the page cache service (3002) and the relational cache service (3004) (100111027)

[0448] • transmitting a message to the neural system / neural server (500) that the registration process has been completed to notify the user (100111028),

[0449] • updating the registration flag status to completed on the user screen / device (100111029),

[0450] • sending a status message to the user via his / her electronic device via the neural system / neural server (500) to notify that the cached information has been updated (1001 |1030),

[0451] • saving the registration status sign as in progress on the user side (100111031).

[0452] Figure 24: The definition process of the objects to be used in the invention with the smart object definer (1002):

[0453] The user can define an object that suits his / her needs or define a completely different object by referring to the object information that can be used anywhere in the invention and the objects that come with the ecosystem developed with the invention. In the ecosystem developed with the invention, the reference definition indicates the registration request made with the flexible object definer (10021), object definer (10022) the relational definer (10023) where the relationship between all definitions is defined, the multilingual definer (10024) and other relevant selections. A message is sent from the cache services (300) to the object cache service (3003), page cache service (3002), relational cache service (3004) and / or multilingual cache service (3005) for registration to the database / server (4001) from the database service (400) via the neural system / neural server (500) for the realisation of the user object create / update (10021 and 10022) request. The object cache service (3003) the page cache service (3002), the relational cache service (3004) and / or the multilingual cache service (3005) checks the current cache status of the request. With this control evaluation, it decides whether there is a request to create a new record or update an existing data. The process step of defining the objects to be used with the smart object definer (1002) comprises the following process steps;

[0454] • requesting registration of object definition information via smart object definer (1002) (1002|1000),

[0455] • sending the information identified by the smart object definer (1002) to the database / server (4001) and cache services (300) / cache server such as object cache service (3003) and relational cache service (3004) via the neural system / neural server (500) (1002|1001),

[0456] • checking the cache status of information with incoming to the object cache service (3003) and the relational cache service (3004) ( 100211002),

[0457] • directing processes according to the status checks of the object cache service (3003) and the relational cache service (3004) (1002| 1003),

[0458] • termination of the process by informing the user via electronic device (100211030).

[0459] When a new object is required to be create:

[0460] A new registration is sent to the request information to the object cache service (3003), page cache service (3002), relational cache service (3004) and / or multilingual cache service (3005). The new register creation status information in the caches is marked as in progress. This flag information is updated as success after all registration processes are successful, is updated as failed if an error is received in any step of the registration process.

[0461] Temporarily added message status information is sent to the user via the neural system / neural server (500) of the information saved in the cache services. At the same time as the message is transmitted to the cache services, the necessary information is sent to the insertion service (4002) of the database services (400) via the neural system / neural server (500) to create the actual record in the database / server (4001). The information coming to the insert service (4002) is saved in the database / server (4001). After the registration process is completed, a message is sent to the code builder service (2008) of the business service (200) by the neural system / neural server (500) to make the object definition ready for use. Object files are created within the framework specified by the user upon request to the code builder service (2008). These files are uploaded to the relevant server and / or software as a service (SaaS) system. After the files have been uploaded into the current system, messages are sent to the object cache service (3003), the page cache service (3002), the relational cache service (3004) and / or the multilingual cache service (3005) and other relevant cache services, as well as to the user's definition screen via the neural system / neural server (500) to inform the user of the successful registration status. The registration status flag information is updated to success with the object cache service (3003), page cache service (3002), relational cache service (3004) and / or multilingual cache service (3005) and other relevant cache services (300). Registration status sign information is updated as success on the user definition screen / device. When a new object is required to be built, the following process steps are performed:

[0462] • sending a new record creation request to the object cache service (3003) and the relational cache service (3004) (1002| 1004), • sending a status message to the user on his / her electronic device via the neural system / neural server (500) to notify that the registration information has been temporarily added to the cache (1002| 1005),

[0463] • saving the registration status sign as in progress on the user side (1002| 1006),

[0464] • transmitting the new information to the insert service (4002) of database service (400) via the neural system / neural server (500) in order to save it in the database / server (4001) (1002|1007),

[0465] • saving the information incoming to the database service (400) to the database / server (4001 ) via the insert service (4002) (100211008),

[0466] • transmitting the saved information to the business service (200) via the neural system / neural server (500) to prepare it for use (1002| 1009),

[0467] • calling the code builder service (2008) by looking at the message content incoming to the business service (200) (1002| 1010),

[0468] • converting defined object information into source code with the code builder service (2008) (1002|1011),

[0469] • Injecting source code files into the running system (1002| 1012),

[0470] • transmission of the transaction completion message regarding the registrations in the cache to the neural system / neural server (500) (1002| 1013),

[0471] • updating the registration flag to complete in the object cache service (3003) and the relational cache service (3004) (100211014)

[0472] • Transmitting a message that the registration process has been completed to notify the user to the neural system / neural server (500) (1002|1015),

[0473] • updating the registration flag status to completed on the user screen / device (100211016).

[0474] To update the existing object definition:

[0475] An update registration is sent to with the request information, to the object cache service (3003), page cache service (3002), relational cache service (3004) and / or multilingual cache service (3005). The update status information in caches is marked as processing. This flag information is updated as success after all update processes are successful, is updated as failed if an error is received in any step of the registration process.

[0476] Temporarily added message status information is sent to the user via the neural system / neural server (500) of the information updated in the cache services (300). At the same time as the message is transmitted to the cache services (300), the necessary information is sent to the update service (4003) of the database services (400) via the neural system / neural server (500) to create the actual record in the database / server (4001). The information coming to the update service (4003) is saved in the database / server (4001 ). After the registration process is completed, a message is sent to the code builder service (2008) of the business service (200) by the neural system / neural server (500) to make the object definition ready for use. Object files are created within the framework specified by the user upon request to the code builder service (2008). These files are uploaded to the relevant server and / or software as a service (SaaS) system. After the files have been loaded into the current system, messages are sent to the object cache service (3003), the page cache service (3002), the relational cache service (3004) and / or the multilingual cache service (3005) and other relevant cache services (300), as well as to the user's definition screen / device via the neural system / neural server (500) to inform the user of the successful registration status.

[0477] The registration flag status information is update to success with the object cache service (3003), page cache service (3002), relational cache service (3004) and / or multilingual cache service (3005) and other relevant cache services (300). Registration status sign information is updated as success on the user definition screen / device. If you want to update the existing object definition, the following process steps are performed;

[0478] • sending an update request of existing information to the object cache service (3003) and relational cache service (3004) (1002| 1017),

[0479] • transmitting the mentioned information to the update service (4003) of database service (400) via the neural system / neural server (500) in order to update the updated information in the database / server (4001) (1002|1018),

[0480] • saving the information incoming to the database service (400) to the database / server (4001 ) via the update service (4003) (1002|1019),

[0481] • sending the saved object information to the business service (200) via the neural system / neural server (500) to prepare it for use (1002| 1020),

[0482] • calling the code builder service (2008) by looking at the message content coming to the business service (200) (1002| 1021 ),

[0483] • converting defined object information into source code with the code builder service (2008) (1002|1022),

[0484] • Injecting source code files into the running system (1002| 1023),

[0485] • transmitting the transaction completion message regarding the registrations in the cache to the neural system / neural server (500) (1002| 1024),

[0486] • updating the registration flag status to completed in the object cache and the relational cache (1002|1025) • transmitting a message to the neural system / neural server (500) that the registration process has been completed to notify the user (1002| 1026),

[0487] • updating the registration flag status to completed on the user screen / device (100211027),

[0488] • sending a status message to the user via the neural system / neural server (500) to notify that the registration information in the cache has been updated (1002| 1028),

[0489] • saving the registration status as in progress on the user side (1002| 1029). of the rules to be used in the invention with the smart rule definer

[0490] In the invention, the definition referred to as a function is either a rule or a user add-in. In the invention ecosystem, a rule definition indicates the save request made with priority, run as, input parameters, return value and other relevant selections. The smart rule definer (1003) sends a message via neural system / neural server (500) to database service (400) and ecosystem’s own cache service (3006) of cache service (300) for the realization of the new registration / update request. The ecosystem's own cache service (3006) checks the status of the incoming request in the current cache. With this control evaluation, it decides whether there is a request to create a new registration or update an existing data. The process step of defining the rules to be used with the smart rule definer (1003) comprises the following steps;

[0491] • requesting registration of the rule definition via smart rule definer (1003) (1003| 1000),

[0492] • sending the information identified by the smart rule definer (1003) to the database / server (4001 ), cache services (300) / cache server such as the relational cache service (3004) and the ecosystem's own cache service (3006) via the neural system / neural server (500) (1003|1001 ),

[0493] • checking the information incoming to the relational cache service (3004) and the ecosystem's own cache service (3006) with the current cache status (1003| 1002),

[0494] • directing the transaction according to the status checks of the relational cache service (3004) and the ecosystem's own cache service (3006) (1003| 1003),

[0495] • termination of the process by informing the user via electronic device (100311030).

[0496] When a new rule is required to be created:

[0497] A new registration is created to the ecosystem's own cache service (3006) with the request information. The new registration creation status information in the caches is marked as in progress. This flag information is updated as success after all registration processes are successful, is updated as failed if an error is received in any step of the registration process. Temporarily added message status information is sent to the user via the neural system / neural server (500) of the information saved in the cache services (300). At the same time as the message is transmitted to the cache services (300), the necessary information is sent to the insertion service (4002) of the database services (400) via the neural system / neural server (500) to create the actual record in the database / server (4001). The information incoming to the insert service (4002) is saved in the database / server (4001 ). After the registration process is completed, a message is sent to the code builder service (2008) of the business service (200) by the neural system / neural server (500) to make the rule definition ready for use. With the request to the code builder service (2008), source code files of the rule are created within the framework specified by the user. These files are uploaded to the relevant server and / or software as a service (SaaS) system. After the files have been uploaded into the current system, messages are sent to the ecosystem's own cache service (3006), as well as to the user’s definition screen / device the neural system / neural server (500) to inform the user for the successful registration status. The registration status sign information is updated to success in the ecosystem's own cache service (3006). Registration status sign information is updated as success on the user definition screen. When a new rule is required to be created, the following process steps are performed;

[0498] • creating a new registration in the relational cache service (3004) and the ecosystem's own cache service (3006) (1003| 1004),

[0499] • sending a status message to the user on his / her electronic device via the neural system / neural server (500) to notify that the registration information has been added to the cache (1003|1005),

[0500] • saving the registration status sign as in progress on the user side (1003| 1006),

[0501] • transmitting the new information to the insert service (4002) of database service (400) via the neural system / neural server (500) in order to save it in the database / server (4001) (1003|1007),

[0502] • saving the information incoming to the database service (400) to the database / server (4001 ) via the insert service (4002) (100311008),

[0503] • sending the saved rule information to the business service (200) via the neural system / neural server (500) to prepare to prepare it for use ( 100311009),

[0504] • calling the code builder service (2008) by looking at the message content incoming to the business service (200) (1003| 1010),

[0505] • converting defined rule information into source code with the code builder service (2008) (1003|1011 ),

[0506] • Injecting source code files into the running system (1003| 1012), • transmission of the transaction completion message regarding the registrations in the cache to the neural system / neural server (500) (1003| 1013),

[0507] • updating the registration flag to complete via the relational cache service (3004) and the ecosystem's own cache service (3006) (100311014),

[0508] • transmitting a message that the registration process has been completed to notify the user to the neural system / neural server (500) (1003|1015),

[0509] • updating the registration flag status to completed on the user screen / device (100311016).

[0510] In order to update the existing rule definition:

[0511] With the request information, the information is updated to the ecosystem's own cache service (3006). Status information for registration updates in the cache is marked as Processing. This flag information is updated as success after all update processes are successful, is updated as failed if an error is received in any step of the registration process. Temporarily updated message status information is sent to the user via the neural system / neural server (500) of the information updated in the cache services (300). At the same time as the message is transmitted to the cache services (300), the necessary information is sent to the update service (4003) of the database services (400) via the neural system / neural server (500) to create the actual record in the database / server (4001). The information incoming to the update service (4003) is saved in the database / server (4001). After the registration process is completed, a message is sent to the code builder service (2008) of the business service (200) by the neural system / neural server (500) to make the rule definition ready for use. With the request to the code builder service (2008), source code files of the rule are created within the framework specified by the user. These files are uploaded to the relevant server and / or software as a service (SaaS) system. After the files have been uploaded to the current system, messages are sent to the ecosystem's own cache service (3006) as well as to the user’s definition screen / device via the neural system / neural server (500) to inform the user for the succf. The registration status sign information is changed to success in the ecosystem's own cache service (3006). Registration status sign information is updated as success on the user definition screen / device. If you want to update the existing rule definition, the following process steps are performed;

[0512] • updating existing information in the relational cache service (3004) and the ecosystem's own cache service (3006) (1003| 1017),

[0513] • transmitting the mentioned information to the update service (4003) of database service (400) via the neural system / neural server (500) in order to update the updated information in the database / server (4001) (1003|1018), • saving the information incoming to the database service (400) to the database / server (4001 ) via the update service (4003) (1003|1019),

[0514] • sending the updated rule information to the business service (200) via the neural system / neural server (500) to prepare it for use (1003| 1020),

[0515] • calling the code builder service (2008) by looking at the message content incoming to the business service (200) (1003| 1021 ),

[0516] • converting defined rule information into source code with the code builder service (2008) (1003|1022),

[0517] • Injecting source code files into the running system (1003| 1023),

[0518] • transmitting the transaction completion message regarding the registrations in the cache to the neural system / neural server (500) (1003| 1024),

[0519] • updating the registration flag status to completed via the relational cache service (3004) and the ecosystem's own cache service (3006) (1003| 1025),

[0520] • transmitting a message to the neural system / neural server (500) that the registration process has been completed to notify the user (1003| 1026),

[0521] • updating the registration flag status to completed on the user screen / device (100311027),

[0522] • sending a status message to the user via the neural system / neural server (500) to notify that the registration information in the cache has been updated (1003| 1028),

[0523] • saving the registration flag status as in progress on the user side (100311029).

[0524] Figure 26. The identification process of the functions that are to be run on a timed basis in the invention with the smart scheduled task definer (1004):

[0525] A registration request is created by defining the functions that are intended to be run at any time and / or at periodic intervals in the invention ecosystem. A message is sent to the ecosystem's own cache service (3006) of the cache services (300) for registration in the database / server (4001) of the database service (400) via the neural system / neural server (500) for the realisation of the timed function definition request with the user smart scheduled task definer (1004). The ecosystem's own cache service (3006) checks the status of the incoming request in the current cache. With this control evaluation, it decides whether there is a request to create a new data or update an existing one. The process step of defining the functions to be run on a timed basis with the smart scheduled task definer (1004) includes the following steps;

[0526] • requesting registration of the function definition that will run on a timed basis via the smart scheduled task definer (1004) (1004| 1000), • sending the information defined by the smart scheduled task definer (1004) to the database / server (4001) and cache services (300) / cache server via the neural system / neural server (500) (1004| 1001 ),

[0527] • checking the cache status of information incoming to the cache service (300) (1004| 1002),

[0528] • directing the operation according to the cache service's (300) status checks (1004| 1003), termination of the process by informing the user via electronic device (1004|1030).

[0529] In the request of the function that is desired to be run with a new time:

[0530] A new registration is created to the ecosystem's own cache service (3006) with the request information. The new registration creation status information in the caches is marked as in progress. This flag information is updated as success after all registration processes are successful, is updated as failed if an error is received in any step of the registration process. Temporarily added message status information is sent to the user via the neural system / neural server (500) of the information saved in the cache services (300). At the same time as the message is transmitted to the cache services (300), the necessary information is sent to the insertion service (4002) of the database services (400) via the neural system / neural server (500) to create the actual record in the database / server (4001). The information incoming to the insert service (4002) is saved in the database / server (4001). After completion of the registration process, a message is transmitted to the code builder service (2008) of the business service (200) by the neural system / neural server (500) to make the timed function definition ready for use. With the request to the code builder service (2008), the source code files of the timed function are generated within the framework specified by the user. These files are uploaded to the relevant server and / or software as a service (SaaS) system. After the files have been uploaded into the current system, messages are sent to the ecosystem's own cache service (3006), as well as to the user’s definition screen / device via the neural system / neural server (500) to inform the user of the successful registration status. The registration status sign information is updated to success in the ecosystem's own cache service (3006). Registration status sign information is updated as success on the user definition screen. If you want to create a new timed function, the following process steps are performed;

[0531] • creating a new registration for a scheduled operation in the cache (1004| 1004),

[0532] • sending a status message to the user on his / her electronic device via the neural system / neural server (500) to notify that the registration information has been added to the cache (1004|1005),

[0533] • saving the registration status sign as in progress on the user side (1004| 1006), • transmitting the new information to the insert service (4002) of database service (400) via the neural system / neural server (500) in order to save it in the database / server (4001) (1004|1007),

[0534] • saving the information incoming to the database service (400) to the database / server (4001 ) via the insert service (4002) (100411008),

[0535] • sending the saved timed function information to the business service (200) via the neural system / neural server (500) to prepare it for use (1004| 1009),

[0536] • calling the code builder service (2008) by looking at the message content incoming to the business service (200) (1004| 1010),

[0537] • converting timed function information defined with the code builder service (2008) into source code (100411011),

[0538] • injecting source code files into the running system (100411012),

[0539] • transmission of the transaction completion message regarding the registrations in the cache to the neural system / neural server (500) (1004| 1013),

[0540] • updating the registration flag status to completed in the cache (100411014),

[0541] • transmitting a message that the registration process has been completed to notify the user to the neural system / neural server (500) (1004|1015),

[0542] • updating the registration flag status to completed on the user screen / device (100411016).

[0543] In the update request of the status that is desired to be run with the current time setting:

[0544] With the request information, the information is updated in the ecosystem's own cache service (3006). Status information for registration updates in the cache is marked as in progress. This flag information is updated as success after all update processes are successful, is updated as failed if an error is received in any step of the registration process. Temporarily added message status information is sent to the user via the neural system / neural server (500) of the information updated in the cache services (300). At the same time as the message is transmitted to the cache services (300), the necessary information is sent to the update service (4003) of the database services (400) via the neural system / neural server (500) to create the actual record in the database / server (4001). The information incoming to the update service (4003) is saved in the database / server (4001). After completion of the registration process, a message is transmitted from the neural system / neural server (500) to the code builder service (2008) of the business service (200) to make the timed function definition ready for use. With the request to the code builder service (2008), the source code files of the timed function are generated within the framework specified by the user. These files are uploaded to the relevant server and / or software as a service (SaaS) system. After the files have been uploaded to the current system, messages are sent via the ecosystem's own cache service (3006) and also via the neural system / neural server (500) to inform the user's definition screen that the registration status has been successful. The registration status sign information is changed to success in the ecosystem's own cache service (3006). Registration status sign information is updated as success on the user definition screen. If it is desired to update the existing timed function definition, the following steps are performed;

[0545] • updating existing information in the cache (1004|1017),

[0546] • transmitting the mentioned information to the update service (4003) of database service (400) via the neural system / neural server (500) in order to update the updated information in the database / server (4001) (1004| 1018),

[0547] • saving the information incoming to the database service (400) to the database / server (4001 ) via the update service (4003) (1004|1019),

[0548] • sending the saved timed function information to the business service (200) via the neural system / neural server (500) to prepare it for use (1004| 1020),

[0549] • calling the code builder service (2008) by looking at the message content incoming to the business service (200) (1004| 1021 ),

[0550] • converting timed function information defined with the code builder service (2008) into source code (100411022),

[0551] • injecting source code files into the running system (100411023),

[0552] • transmitting the transaction completion message regarding the registrations in the cache to the neural system / neural server (500) (1004| 1024),

[0553] • updating the registration flag status to completed in the cache (100411025),

[0554] • transmitting a message to the neural system / neural server (500) that the registration process has been completed to notify the user (1004| 1026),

[0555] • updating the registration flag status to completed on the user screen / device (100411027),

[0556] • sending a status message to the user via the neural system / neural server (500) to notify that the registration information in the cache has been updated (1004| 1028),

[0557] • saving the registration flag status as in progress on the user side (100411029).

[0558] 27. Validation check definition with smart validation definer

[0559] A registration request is created by defining a validation check in the invention ecosystem. In order to save the information created / updated by the smart validation definition (1005) to the database / server (4001) of database service (400), A message is sent to the ecosystem's own cache service (3006) of the cache services (300) via the neural system / neural server (500). The ecosystem's own cache service (3006) checks the status of the incoming request in the current cache. With this control evaluation, it decides whether there is a request to create new data or update an existing one. Validation check definition step with smart validation definer (1005) comprises the following process steps:

[0560] • requesting registration of the validation check definition via the smart validation definer (1005) (1005|1000),

[0561] • sending the information defined by the smart validation definer (1005) to the database / server (4001) and cache services (300) / cache server via the neural system / neural server (500) (1005| 1001 ),

[0562] • checking the information incoming to the cache service (300) with current cache status (1005|1002),

[0563] • directing the operation according to the cache service's (300) status checks (1005| 1003),

[0564] • termination of the process by informing the user via electronic device (100511030).

[0565] When a new validation definition is required to be created:

[0566] A new registration is created to the ecosystem's own cache service (3006) with the request information. The new registration creation status information in the caches is marked as in progress. This flag information is updated as success after all registration processes are successful, is updated as failed if an error is received in any step of the registration process. Temporarily added message status information is sent to the user via the neural system / neural server (500) of the information saved in the cache services (300). At the same time as the message is transmitted to the cache services (300), the necessary information is sent to the insertion service (4002) of the database services (400) via the neural system / neural server (500) to create the actual record in the database / server (4001). The information incoming to the insert service (4002) is saved in the database / server (4001). After the registration process is completed, a message is sent to the code builder service (2008) of the business system (200) by the neural system / neural server (500) to make the validation control definition ready for use. With the request to the code builder service (2008), source code files for the validity check function are created within the framework specified by the user. These files are uploaded to the relevant server and / or software as a service (SaaS) system. After the files have been uploaded into the current system, messages are sent to the ecosystem's own cache service (3006), as well as to the user’s definition screen / device via the neural system / neural server (500) to inform the user of the successful registration status. The registration status sign information is changed to success in the ecosystem's own cache service (3006). Registration status sign information is updated as success on the user definition screen / device. When a new validation check definition is required to be built, the following process steps are performed;

[0567] • creating a new record for a validation operation in the cache (100511004), • sending a status message to the user on his / her electronic device via the neural system / neural server (500) to notify that the registration information has been added to the cache (1005|1005),

[0568] • saving the registration status sign as in progress on the user side (1005| 1006),

[0569] • transmitting the new information to the insert service (4002) of database service (400) via the neural system / neural server (500) in order to save it in the database / server (4001) (1005|1007),

[0570] • saving the information incoming to the database service (400) to the database / server (4001 ) via the insert service (4002) (100511008),

[0571] • sending the business service (200) via the neural system / neural server (500) to prepare the validation check information for use (1005| 1009),

[0572] • calling the code builder service (2008) by looking at the message content incoming to the business service (200) (1005| 1010),

[0573] • converting defined validation control information into source code with the code builder service (2008) (1005|1011 ),

[0574] • injecting source code files into the running system (100511012),

[0575] • transmission of the transaction completion message regarding the registrations in the cache to the neural system / neural server (500) (1005| 1013),

[0576] • updating the registration flag status to completed in the cache (100511014),

[0577] • transmitting a message that the registration process has been completed to notify the user to the neural system / neural server (500) (1005|1015),

[0578] • updating the registration flag status to completed on the user screen / device (100511016).

[0579] In order to update the existing validation definition:

[0580] With the request information, the information is updated to the ecosystem's own cache service (3006). Status information for registration updates in the cache is marked as in progress. This flag information is updated as success after all update processes are successful, is updated as failed if an error is received in any step of the At the same time as the message is transmitted to the cache services (300), the necessary information is sent to the update service (4003) of the database services (400) via the neural system / neural server (500) to create the actual record in the database / server (4001). The information incoming to the update service (4003) is saved in the database / server (4001). After the registration process is completed, a message is sent to the code builder service (2008) of the business service (200) by the neural system / neural server (500) to make the validation control definition ready for use. With the request to the code builder service (2008), source code files for the validity check definition are created within the framework specified by the user. These files are uploaded to the relevant server and / or software as a service (SaaS) system. After the files have been uploaded into the current system, messages are sent to the ecosystem's own cache service (3006), as well as to the user’s definition screen / device via the neural system / neural server (500) to inform the user of the successful registration status. The registration status sign information is changed to success in the ecosystem's own cache service (3006). Registration status sign information is updated as success on the user definition screen / device. If you want to update the existing validation check definition, the following process steps are performed;

[0581] • updating existing information in the cache (1005|1017),

[0582] • transmitting the mentioned information to the update service (4003) of database service (400) via the neural system / neural server (500) in order to update the updated information in the database / server (4001) (1005|1018),

[0583] • saving the information incoming to the database service (400) to the database / server (4001 ) via the update service (4003) (1005|1019),

[0584] • informing the business service (200) via the neural system / neural server (500) to prepare the saved validation information for use (1005| 1020),

[0585] • calling the code builder service (2008) by looking at the message content incoming to the business service (200) (1005| 1021 ),

[0586] • converting defined validation control information into source code with the code builder service (2008) (1005|1022),

[0587] • injecting source code files into the running system (1005| 1023),

[0588] • transmitting the transaction completion message regarding the registrations in the cache to the neural system / neural server (500) (1005| 1024),

[0589] • updating the registration flag status to completed in the cache (100511025),

[0590] • transmitting a message to the neural system / neural server (500) that the registration process has been completed to notify the user (1005| 1026),

[0591] • updating the registration flag status to completed on the user screen / device (100511027),

[0592] • sending a status message to the user via the neural system / neural server (500) to notify that the registration information in the cache has been updated (1005| 1028),

[0593] • saving the registration flag status as in progress on the user side (100511029).

[0594] Figure 28. The process of defining the add-in code snippet to be used in the invention with the smart add-in definer (1006):

[0595] In the invention, the definition referred to as a function is either a rule or a user add-in. In the invention ecosystem, it indicates the save request made with priority, run as , input parameters, return value and other relevant selections. The smart add-in definer (1006) sends a message via the neural system / neural server (500) to database service (400) and ecosystem's own cache service (3006) of cache services (300) for the realisation of the new creation / update request. The ecosystem's own cache service (3006) checks the status of the incoming request in the current cache. With this control evaluation, it decides whether there is a request to create a new data or update an existing one. The process step of defining the add-in code snippets to be used with the smart add-in definer (1006) includes the following steps;

[0596] • requesting registration of user-based code add-in definition via smart add-in definer (1006) (1006|1000),

[0597] • sending the information defined by the smart add-in definer (1006) to the database / server (4001 ) and cache services (300) / cache server via the neural system / neural server (500) (1006|1001 ),

[0598] • checking the information incoming to the cache service (300) with current cache status (1006|1002),

[0599] • directing the operation according to the cache service's (300) status checks (1006| 1003),

[0600] • termination of the process by informing the user via electronic device (100611030)

[0601] When requesting the creation of a new add-in snippet:

[0602] Request information is created to the relational cache service (3004) and the ecosystem's own cache service (3006). The new registration creation status information in the caches is marked as in processing. This flag information is updated as success after all registration processes are successful, is updated as failed if an error is received in any step of the registration process. Temporarily added message status information is sent to the user via the neural system / neural server (500) of the information saved in the cache services (300). At the same time as the message is transmitted to the cache services (300), the necessary information is sent to the insertion service (4002) of the database services (400) via the neural system / neural server (500) to create the actual record in the database / server (4001). The information incoming to the insert service (4002) is saved in the database / server (4001 ). After the registration process is completed, a message is sent to the code builder service (2008) of the business service (200) by the neural system / neural server (500) to make the add-in code snippet definition ready for use. With the request to the code builder service (2008), source code files of the add-in code snippet are created within the framework specified by the user. These files are uploaded to the relevant server and / or software as a service (SaaS) system. After the files have been uploaded to the current system, messages are sent to the ecosystem's own cache service (3006), as well as to the user’s definition screen / device via the neural system / neural server (500) to inform the user of the successful registration status. The registration status sign information is changed to success in the ecosystem's own cache service (3006). Registration status sign information is updated as success on the user definition screen / device. If you want to create a new user-based code add-in definition, the following process steps are performed;

[0603] • creating a new record for a user-based code add-in in the cache (100611004),

[0604] • sending a status message to the user on his / her electronic device via the neural system / neural server (500) to notify that the registration information has been added to the cache (1006|1005),

[0605] • saving the registration status sign as in progress on the user side (1006| 1006),

[0606] • transmitting the new information to the insert service (4002) of database service (400) via the neural system / neural server (500) in order to save it in the database / server (4001) (1006|1007),

[0607] • saving the information incoming to the database service (400) to the database / server (4001 ) via the insert service (4002) (100611008),

[0608] • informing the saved user-based code add-in information to the business service (200) via the neural system / neural server (500) to prepare it for use (1006| 1009),

[0609] • calling the code builder service (2008) by looking at the message content incoming to the business service (200) (1006| 1010),

[0610] • converting defined user-based code add-in information into source code with the code builder service (2008) (100611011 ),

[0611] • injecting source code files into the running system (100611012),

[0612] • transmission of the transaction completion message regarding the registrations in the cache to the neural system / neural server (500) (1006| 1013),

[0613] • updating the registration flag status to completed in the cache (100611014),

[0614] • transmitting a message that the registration process has been completed to notify the user to the neural system / neural server (500) (1006|1015),

[0615] • updating the registration flag status to completed on the user screen / device (100611016).

[0616] In the current add-in snippet definition update request:

[0617] Request information is updated with the relational cache service (3004) and the ecosystem's own cache service (3006). Status information for registration updates in the cache is marked in progress. This flag information is updated as success after all update processes are successful, is updated as failed if an error is received in any step of the registration process. Temporarily updated message status information is sent to the user via the neural system / neural server (500) of the information updated in the cache services (300). At the same time as the message is transmitted to the cache services (300), the necessary information is sent to the update service (4003) of the database services (400) via the neural system / neural server (500) to create the actual record in the database / server (4001). The information incoming to the update service (4003) is saved in the database / server (4001). After the registration process is completed, a message is sent to the code builder service (2008) of the insert service (200) by the neural system / neural server (500) to make the addin code snippet definition ready for use. With the request to the code builder service (2008), source code files of the add-in code snippet are created within the framework specified by the user. These files are uploaded to the relevant server and / or software as a service (SaaS) system. After the files have been uploaded to the current system, messages are sent via the ecosystem's own cache service (3006) and also via the neural system / neural server (500) to inform the user's definition screen that the registration status has been successful. The registration status sign information is changed to success in the ecosystem's own cache service (3006). Registration status sign information is updated as success on the user definition screen. If it is desired to update the existing user-based code add-in definition, the following steps are performed:

[0618] • updating existing information in the cache (1006|1017),

[0619] • transmitting the mentioned information to the update service (4003) of database service (400) via the neural system / neural server (500) in order to update the updated information in the database / server (4001) (1006|1018),

[0620] • saving the information incoming to the database service (400) to the database / server (4001 ) via the update service (4003) (1006|1019),

[0621] • transmitting the saved user-based code add-in information to the business service (200) via the neural system / neural server (500) to prepare it for use (1006| 1020),

[0622] • calling the code builder service (2008) by looking at the message content incoming to the business service (200) (1006| 1021 ),

[0623] • converting defined user-based code add-in information into source code with the code builder service (2008) (1006| 1022),

[0624] • injecting source code files into the running system (100611023),

[0625] • transmitting the transaction completion message regarding the registrations in the cache to the neural system / neural server (500) (1006| 1024),

[0626] • updating the registration flag status to completed in the cache (100611025),

[0627] • transmitting a message to the neural system / neural server (500) that the registration process has been completed to notify the user (1006| 1026),

[0628] • updating the registration flag status to completed on the user screen / device (100611027),

[0629] • sending a status message to the user via the neural system / neural server (500) to notify that the registration information in the cache has been updated (1006| 1028), saving the registration flag status as in progress on the user side (1006| 1029).

[0630] Fiqure 29. Process of processinq a request incominq to the invention from a different environment:

[0631] Incoming requests or outgoing request information from media other than the invention are provided only by communicating through this service. In this heading, only the process of a request incoming from the outside world to the invention is defined. It is possible to transfer information to the external environment without a request from the external environment for the invention. The process is started with a request incoming to the invention from the external environment via the communication network (2). User identity control is provided in the parameters of the incoming request according to the request type. If the user identity information are not valid in the space portal (2006), an invalid user error is sent to the requesting environment. If the user identity information are valid in the space portal (2006), the validity control of the request parameters and values is provided by the smart validity definer (1005). If the validity check fails in the space portal (2006), an invalid parameter error message is given to the requesting environment. If the validity check is successful in the space portal (2006), the necessary information is transferred to the consume service (2005) via the neural system / neural server (500). Within the consume service (2005), it performs user identity control according to the type of request incoming from the space portal (2006). In the consume service (2005), if the user identification information is invalid on the invention side, a user error message is transmitted to the requesting environment via the neural system / neural server (500) and the space portal (2006). If the user identification information is approved by the invention in the consume service (2005), the validation check of the parameters and values of the incoming request is provided by the smart validation definer (1005).

[0632] If the validity check fails in the consume service (2005), an invalid parameter error is sent to the space portal (2006). In the space portal (2006), the relevant error is sent to the environment making the request. If the validity check in the consume service (2005) is successful, the neural system / neural server (500) and the user cache service (3001 ) either open a new session with the necessary information and the credentials or reset / edit the expiration time of the current user. The user cache service (3001 ) transmits the request to the rule selector (2001 ) via the neural system / neural server (500) with the relevant parameters. Rules to be executed are determined in the rule selector (2001 ) according to the type and user of the incoming request, and this rule information is transmitted to the rule operator (2002) to enable the rules to be executed. The rule results run with the rule operator (2002) are sent to the user cache service (3001 ) and database service (400) via the neural system / neural server (500). The result information arriving at the user cache service (3001 ) is recorded in the relevant user information. Positive result information is sent to the consume service (2005). The information incoming to the database service (400) is saved in the database / server (4001 ). The result information is sent to the consume service (2005). The consume service (2005) transfers the result information to the space portal (2006) via the neural system / neural server (500). The process ends by transmitting the result information received to the space portal (2006) to the requesting environment via the communication network (2). If a request comes from a different environment, the following steps are performed to process the incoming request:

[0633] • making requests from any environment, over the communication network (2) (200|1000),

[0634] • accepting the request from the external environment through the space portal (2006) in the business service (200) (200| 1001 ),

[0635] • evaluating the validation status of the incoming request parameters by the smart validation definer (1005), if the validation check fails, giving an invalid parameter error message to the requesting environment and returning to the (200| 1000) process step, if the validation check is successful, transmitting the necessary information to the consume service (2005) via the neural system / neural server (500) (200| 1002),

[0636] • checking the identity information of the incoming request source by the consume service (2005), in case of invalid identity, sending a user error message to the requesting environment via the neural system / neural server (500) and space portal (2006) and returning to the (200| 1000) process step, in case the identity is confirmed, the validation check of the parameters and values of the incoming request is provided by the smart validation definer (1005) (200| 1003),

[0637] • transmitting the relevant identity information from the space portal (2006) to the consume service (2005) in the business service (200) (200| 1004),

[0638] • evaluating the validation status of the incoming request parameters in the consume service (2005), if the validation check fails, sending an invalid parameter error message to the requesting environment via the space portal (2006) and returning to the (200| 1004) process step, if the validity check is successful, forwarding the request to the user cache service (3001 ) (200|1005),

[0639] • checking the identity information of the request source incoming to the user cache service (3001 ), returning to the (200|1004) process step in case of invalid identity, continuing the operations in case of valid identity (200| 1006), • transmitting the identity information of the request source to the neural system / neural server (500) to ensure that the identity information are saved or updated in the user cache service (3001 ) (200| 1007),

[0640] • saving the information incoming to the user cache service (3001) in a controlled manner and opening the user's session or extending the duration of the session (200|1008),

[0641] • informing the consume service (2005) that the identity information has been saved (200|1009),

[0642] • transmitting the relevant parameters of the user cache service (3001) to the neural system / neural server (500) and the rule selector (2001 ), determining the rules and / or user-based code add-ins that will work with the rule selector (2001) (200|1010),

[0643] • running specified rules and / or user-based code add-ins via the rule operator (2002) (200|1011),

[0644] • sending the results to the neural system / neural server (500) for saving to the user cache service (3001), other relevant cache services (300) and database / server (4001 ) (200|1012),

[0645] • saving the created information to the user cache service (3001) and other related cache services (300) (200| 1013),

[0646] • saving the output information to the database / server (4001) on the database service (400) via the insert service (4002) (200| 1014),

[0647] • upon completion of the registration process, sending the registration information to the consume service (2005) (200| 1015),

[0648] • the consume service (2005) transmitting the output information to the space portal (2006) (200|1016),

[0649] • space portal (2006) transmitting the information to the external environment server (200|1017).

[0650] As can be seen from Figure 22, the invention is both a software ecosystem that can work on its own and an ecosystem that works interactively with external environments when desired. Figure 29 explains how external environments communicate with the invention and operate it. What is meant by an autonomous ecosystem is that it can automatically create user interfaces and environments that will work in the background interactively with these interfaces, with the definition directives specified by customers. Of course, customers may not always need a user interface, in which case the creation of programs (11) that will only run in the background will be carried out by definitions. All of these can be done by the customers themselves without any software knowledge other than the smart definers (100) and the smart add-in definer (1006). It is the neural system / neural server (500) that provides communication between the software services and / or software modules to be used in the invention. The desired results (output) are obtained by making the back-end and / or front-end software created with the invention use the defined information (rule, add-in and object) via the consume service (2005) of the invention. The name, address, e-mail address and web page address information specified in the diagrams have been added for example purposes.

[0651] Definitions made with smart definers (100) can be completely translated into software code or only partial definitions can be converted into software code. This varies depending on the size of the information to be added and / or user request. The translated codes are either injected without stopping the current running system or added to the current application as a different version (Major and / or Minor version) without interfering with the existing coding. An orchestration-based saga design pattern that follows the entire process from the beginning to the end (positive or negative) of a process is applied.

Claims

CLAIMS1. A real flexibility and rule-based software development system (3) that enables communication with a communication network (2) and may comprise any one or more of the following;• software programs (11 ) that are currently used by the company,• machines / devices (12) which are electronic or mechanical devices currently used by companies,• loT devices (13) that use the communication network (2) that companies currently use, where physical objects are connected to each other or larger systems,• system management (14), which are the tools, real people or users by which companies manage their existing systems,• programs to be integrated (41 ), which are software by which companies will integrate,• Machines / devices to be integrated (42) that companies will integrate with,• loT devices to be integrated (43) that companies will integrate with,• integration management (44), which is interactive tools and real people used for the integrated system, and for companies that want to expand their business volume regardless of the number of employees, for companies whose business volumes have grown or for software companies, with real flexibility, rule-based and flexible as well as hard-coded software performance can be used in all areas where software needs can be met, can develop rule based applications in every software, enables companies / individuals who are experts in their business to create a software ecosystem where they can create their own user interfaces that will determine how the software application will behave according to the specified situations by defining the objects and workflows belonging to the jobs in their field of expertise with very simple visuals without software knowledge, and enabling users to use information actively interactively with artificial intelligence in object definitions, rule creation and reporting, which is a software ecosystem that can be controlled through all electronic devices such as computers, tablets, smartphones and smart watches, characterized by comprising;• smart definers (100), which comprises all the definitions to be made in order to use the rule-based software development system (3) with real flexibility, which can be used as a referenced library in other services, which access the definitionsneeded in other services is provided on, and which made all definitions through them are incorporated in the current running application in real time,• a business service (200), which comprises the functions that enable the definitions made with the smart definers (100),• a database service (400) through which a database / server (4001) operations are carried out and which assumes responsibility for the database / server (4001 ),• a neural system / neural server (500) that provides a controlled communication flow between the smart definers (100), the business service (200), a cache service (300) and the database service (400) modules and which may vary depending on the environment or environments in which they are developed,• said database / server (4001), which has data storage systems, on which the definitions are stored, and on which the result data produced with real flexibility and with the use of the rule-based software development system (3) is stored.

2. The real flexibility and rule-based software development system (3) according to claim 1 , characterized by comprising; a smart user-interface definer (1001 ), on which modular definition is made for screens used in web, desktop, laptop and mobile device interfaces, through which the necessary files for the specified interface template were uploaded, modular structure setup is created by selecting the uploaded files, in which each successful user interface definition is translated into software code, which facilitates the creation of very complex user-interfaces and allows repeated use due to its modular structure and thus, if an interface module needs to be used more than once, can be used without redefinition.

3. The real flexibility and rule-based software development system (3) according to claim 1 , characterized by comprising; a smart object definer (1002) which defines over all object information needed for use in smart definers (100), business service (200), optionally cache service (300), database service (400) and neural system / neural server (500).

4. The real flexibility and rule-based software development system (3) according to claim 1 , characterized by comprising; a smart rule definer (1003) through which rules are created, with which can be defined by visuals drawn in UML diagrams, rules are defined from the mentioned UML diagrams to be translated into software code, which generates software codes by importing diagrams from external media using Al (OCR) or data transfer formats, using accepted schematic visuals , enables the rules to beautomatically translated into software code by transferring the defined rules to the application and is added to the running codes of the application used, thus, saves the time lost in the interpretation of the rules that cause the performance problems experienced in other rule-based systems, it has a definition section through which users can create their own rules and include them in the running application, automatically creates the necessary environment for testing when the rule is saved, through which the environment required for testing is provided automatically, which enables newly added or updated rules to be translated into software code and added to the existing application at run time, makes it possible to continue using the application without interrupting the running application, is operated with two principles: synchronous and asynchronous, depending on the requirements of the rules and user choice.

5. The real flexibility and rule-based software development system (3) according to claim 1 , characterized by comprising; a smart scheduled task definer (1004) from which the operations / rules that are desired to be performed on a timed, one-time or periodic basis can be selected in the created applications.

6. The real flexibility and rule-based software development system (3) according to claim 1 , characterized by comprising; a smart validation definer (1005) that provides validity checks in the application of created rules, data entries, output data produced during the operation of the application with information entries, smart user-interface definers (1001 ) and pre-registration process.

7. The real flexibility and rule-based software development system (3) according to claim 1 , characterized by comprising; a smart add-in definer (1006), through which companies with software capabilities can add their own program snippets, special requests are resolved by adding the desired libraries to the existing ones, companyspecific functions can be included in the application, companies can make special developments, the rules defined in the smart rule definer (1003) can be called from the added code snippets, in the added code snippets, the operation type can be selected as synchronous or asynchronous, when the add-in is registered, the necessary environment for testing is automatically provided, newly added or updated add-ins can be incorporated into the existing application while it is running without interruption.

8. The real flexibility and rule-based software development system (3) according to claim 2, characterized by comprising; theme definers (10011 ) through which the userinterface that users will see are defined.

9. The real flexibility and rule-based software development system (3) according to claim 2, characterized by comprising; an operation of objects unit (10012) which are the most basic event-based functions, used for the definitions in the data entry objects in the defined modules selected from defined rules or defined add-in code snippets.

10. The real flexibility and rule-based software development system (3) according to claim 2, characterized by comprising; an OnFocus operation unit (100121 ) which is configured through defined rules or defined add-in code snippets functions when the information input object is entered with the mouse or keyboard.

11. The real flexibility and rule-based software development system (3) according to claim 2, characterized by comprising; an OnExit operation unit (100122) where the function selected from defined rules or defined add-in code snippets that are desired to run when the information input object is exited and an event is thrown.

12. The real flexibility and rule-based software development system (3) according to claim 2, characterized by comprising; an OnChanged operation unit (100123) on which the function selected from defined rules or defined add-in code snippets is configured, which is intended to run during each information change in the data input object and in case an event is thrown13. The real flexibility and rule-based software development system (3) according to claim 2, characterized by comprising; a MouseHover operation unit (100124) defining the function selected from defined rules or defined add-in code snippets that is requested to run when the mouse cursor hovers over the input object and in case an event is thrown.

14. The real flexibility and rule-based software development system (3) according to claim 2, characterized by comprising; a page load / page close operation unit (10013) which are definitions of the function selected from defined rules or defined add-in code snippets, which can be triggered during the display of defined modules, registration and registration closure.

15. The real flexibility and rule-based software development system (3) according to claim 2, characterized by comprising; an operation unit page before-load (100131) defining the function selected from defined rules or defined add-in code snippets that is requested to be executed before the module to be opened and the sub-modules associated with this module are loaded to the user-interface.

16. The real flexibility and rule-based software development system (3) according to claim 2, characterized by comprising; an operation unit page after-load (100132) defining the function selected from defined rules or defined add-in code snippets that is requested to be executed after the module to be opened and the sub-modules associated with this module and therefore all objects are loaded on the user-interface.

17. The real flexibility and rule-based software development system (3) according to claim 2, characterized by comprising; an operation unit page before-post (100133) defining the function selected from defined rules or defined add-in code snippets, triggered before the execution of the function to which the buttons for record (insert, delete and modify) operations attached to a module are linked.

18. The real flexibility and rule-based software development system (3) according to claim 2, characterized by comprising; an operation unit page after-post (100134), defining the function selected from defined rules or defined add-in code snippets which is triggered after the execution of the function to which the buttons for record (insert, delete and modify) operations attached to a module are linked.

19. The real flexibility and rule-based software development system (3) according to claim 2, characterized by comprising; an operation unit page before-close (100135) defining a function selected from defined rules or defined add-in code snippets that is executed before close when a closing request is sent to a module.

20. The real flexibility and rule-based software development system (3) according to claim 2, characterized by comprising; an operation unit page after-close (100136) defining the function selected from defined rules or defined add-in code snippets that is executed after close when a closing request is sent to a module.

21. The real flexibility and rule-based software development system (3) according to claim 2, characterized by comprising; an Operation Unit Page On-Show (100137)defining a function selected from defined rules or defined add-in code snippets, which is executed after the visibility of a module has been switched from hidden to visible mode.

22. The real flexibility and rule-based software development system (3) according to claim 2, characterized by comprising; an Operation Unit Page OnSent Backward (100138) describing the function selected from defined rules or defined add-in code snippets, executed after the visibility of a module has been switched from visible to hidden mode.

23. The real flexibility and rule-based software development system (3) according to claim 2, characterized by comprising; a page validation unit (10014) defining functions selected from defined rules or defined add-in code snippets, which are configured for assessing the validation status of objects linked to modules created with the smart user-interface definer (1001).

24. The real flexibility and rule-based software development system (3) according to claim 2, characterized by comprising; a Page Before-Load Validation Unit (100141) is determined to evaluate the desired validation status before loading the modules created with the smart user-interface definer (1001 ), in which functions selected from defined rules or defined add-in code snippets are defined, which allows the states of other modules and / or objects to be validated before opening the relevant module.

25. The real flexibility and rule-based software development system (3) according to claim 2, characterized by comprising; a Page After-Load Validation Unit (100142) is determined to evaluate the desired validation status after loading the modules created with the smart user-interface definer (1001 ), in which functions selected from defined rules or defined add-in code snippets are configured, which allows the states of other modules and / or objects to be validated after opening the relevant module.

26. The real flexibility and rule-based software development system (3) according to claim 2, characterized by comprising; a Page Before-Post Validation Unit (100143) is defined for the evaluation of the desired validation status of the modules created with the smart user-interface definer (1001) before the registration process, in which functions selected from defined rules or defined add-in code snippets are configured, which enable the status of its own objects and / or other modules and / or objects to be subjected to a validity check before the registration process in the relevant module.

27. The real flexibility and rule-based software development system (3) according to claim 2, characterized by comprising; a Page After-Post Validation Unit (100144) is defined for the evaluation of the desired validation status of the modules created with the smart user- interface definer (1001) after the registration process, in which functions selected from defined rules or defined add-in code snippets are configured, which enable the status of its own objects and / or other modules and / or objects to be subjected to a validity check after the registration process in the relevant module.

28. The real flexibility and rule-based software development system (3) according to claim 3, characterized by comprising; a flexible object definer (10021) that specifies object types that reference objects used throughout the generated application.

29. The real flexibility and rule-based software development system (3) according to claim 3, characterized by comprising; an object definer (10022) where attribute and / or object properties information such as version, step, form, generated data are defined in the created application.

30. The real flexibility and rule-based software development system (3) according to claim 3, characterized by comprising; a relational definer (10023) where the relationship between all definitions that can be made with smart definers (100) is defined.

31. The real flexibility and rule-based software development system (3) according to claim 3, characterized by comprising; a multilingual definer (10024) used to translate all definitions that can be defined with smart definers (100) into the desired languages32. The real flexibility and rule-based software development system (3) according to claim 4, characterized by comprising; a type of rule definer (10031) through which users can define their own rule types, thus enabling all rules belonging to a special rule type defined in the rules and add-in code snippets to be executed.

33. The real flexibility and rule-based software development system (3) according to claim 1 and 4, characterized by comprising; a group of rule definer (10032) which can group rules defined in the smart rule definer (1003) and / or add-in code snippets defined in the smart add-in definer (1006) and / or among themselves according to any feature / type of rules and / or needs.

34. The real flexibility and rule-based software development system (3) according to claim 4, characterized by comprising; a rule definer (10033) that defines the desired work with flow diagrams to fulfil company requests.

35. The real flexibility and rule-based software development system (3) according to claim 5, characterized by comprising; a scheduled task definer (10041), which defines the tasks that are requested to run according to the date and / or time value in certain periods in the programme to be implemented, which are automatically translated into software code to be transferred to the application and added to the running codes of the application used at runtime.

36. The real flexibility and rule-based software development system (3) according to claim 6, characterized by comprising; an object validation unit (10051) with a validity check that can be applied to all defined objects.

37. The real flexibility and rule-based software development system (3) according to claim 6, characterized by comprising; an OnFocus validation unit (100511), which can only perform validity checks on objects in user interfaces, is triggered by the relevant event when entering any object in which the data is going to be entered, and defines the function selected from defined rules or defined add-in code snippets.

38. The real flexibility and rule-based software development system (3) according to claim 6, characterized by comprising; an OnExit validation unit (100512), which can only perform validity checks on objects in user interfaces, is triggered by the relevant event when exiting any object in which the data is going to be entered information, and defines the function selected from defined rules or defined add-in code snippets.

39. The real flexibility and rule-based software development system (3) according to claim 6, characterized by comprising; an OnChanged validation unit (100513), which can perform validity checks on both objects in user interfaces and program objects running at the background, is triggered on value change of any object, and defines the function selected from defined rules or defined add-in code snippets.

40. The real flexibility and rule-based software development system (3) according to claim 1 , characterized by comprising;• a rule selector (2001), which is triggered by an event activated by any operation, identifies the function selected from rules or add-in code snippets defined by smart definers (100) in order to prepare it for execution, prioritises it according to rule types and passes the task to the rule operator (2002) for execution,• a rule operator (2002), which enables the function selected from rules or addin code snippets defined with smart definers (100), triggered by an event activated due to any operation, to be run• a rule injection unit (2003) which generates software development codes from user-defined flowcharts and allows the defined rules to be instantly incorporated into the current running system,• an add-in injection unit (2004) which user-developed software code to be instantly incorporated into the existing running system,• a consume service (2005), which enables the execution of the relevant rules on demand, via the rule selector (2001) and the rule operator (2002), and is responsible for the transmission of the results back, enabling work requests from user interfaces and other services to communicate with other services and user interfaces through it,• a space portal (2006), which is responsible for enabling communication with applications not developed with the real flexibility and rule-based software development system (3), which can communicate with other applications in many different ways and / or according to the environment in which it is implemented, which enables the realisation of requests from external environments or information desired to be sent from the invention to the outside world, after making the necessary checks and adjustments to each incoming request, sends the request to the consume service (2005) and waits until the request is finalised, which checks and / or edits the result coming from the consume service (2005) and transmitting the result with feedback to the system making the request, or taking action without being transmitted to the consume service (2005) depending on the type and identity information of the request,• a front-end builder service (2007), which converts the user interface information defined by the smart user-interface definer (100) into front-end software code for the web, desktop or smart device, which enables the conversion of request definitions produced with the code builder service (2008) and definitions for processing incoming responses / requests, themes createdto be used on different screens, activities performed in page areas, smart definers (100) and submodules into front-end software codes.

41. The real flexibility and rule-based software development system (3) according to claim 1 , characterized by comprising; a code builder service (2008), which is run after all successful registration operations with the smart object definer (1002), smart rule definer (1003), smart scheduled task definer (1004), smart validation definer (1005) and smart add-in definer (1006), which are smart definers (100), enables the translation of defined information into software code, is responsible for translating the rule diagrams transferred to the system with artificial intelligence into software code and translating the rules transferred to the system from the external environment into software code and allows users to automatically create back-end code according to the needs of themes and user interfaces without front-end software development knowledge.

42. The real flexibility and rule-based software development system (3) according to claim 1 , characterized by comprising; the cache service (300), which is used to produce results quickly, can be scripted as if it were carried out through database / server (4001) transactions with a value that can be adjusted parametrically to increase performance, and the result can be given to the user, and in principle the information is accepted as temporary, not as the real transaction result, in the processes.

43. The real flexibility and rule-based software development system (3) according to claim 42, characterized by comprising;• an user cache service (3001), which ensures that the request coming to the consume service (2005) in the business service (200) with its parameters and the response to the incoming request are kept in the cache, can also be used as a temporary data storage location in transactions (evaluation or calculations) that do not require recording in the database / server (4001 ) and provides increased performance since there is no need to read chunks of data from the database / server (4001) each time,• a page cache service (3002), which ensures that the information about the objects in the modules defined by the smart user-interface definer (1001 ) among smart definers (100) is preserved with the key on it, as a result of users' information input, is valid for the relevant module and ensures that thegenerated information is cached, in order for the module-based results can be used from the cache, which is associated via a unique key in the user cache service (3001 ) and corresponding keys in the object cache service (3003),• an object cache service (3003), which ensures that objects identified with the smart object definer (1002) among smart definers (100) are kept in the cache and associates the objects used in the pages with the page cache service (3002) through the necessary keys,• a relational cache service (3004), which ensures that the relationship states and hierarchy of related objects are kept in the cache,• a multilingual cache service (3005), which ensures that the equivalents of information in other languages in each field defined by smart definers (100) are kept in the cache for the use of the created application,• an ecosystem's own cache service (3006), which enables the caching of information created by users with smart rule definer (100) such as, smart rule definer (1003), smart add-in definer (1006) and smart scheduled task definer (1004) in the developed application.

44. The real flexibility and rule-based software development system (3) according to claim 1 , characterized by comprising; in order to take advantage of changes in database / server (4001 ) commands, database / server (4001) logging changes and other changes at any time, according to the type and characteristic of the operation;• an insert service (4002) which allows the new information created to be saved to the database / server (4001),• an update service (4003) which is used when making changes to the information previously recorded in the database / server (4001),• a query service (4004) which queries the records in the database / server (4001 ) and responds to information requests.

45. A real flexibility and rule-based software development method which is software ecosystem, through which it is possible to work with real flexibility, with a rule-based and flexible as well as hard-coded software performance in companies or software companies that want to expand their business volume, regardless of the number of employees, or whose business volume has grown, and develops rules-based applications in every software that can be used in all areas where software needs can be met, enables companies or individuals who are experts in their business to createa software ecosystem where they can create their own user interfaces that will determine how the software application will behave according to the specified situations by defining the objects and workflows belonging to the jobs in their field of expertise with very simple visuals without software knowledge, and to provide users with active interactive use of the information entered in object definitions, rule creation and reporting with Artificial Intelligence (Al), characterized by comprising the following process steps;• creating a user interface with the smart user-interface definer (1001 ),• defining the objects to be used with the smart object definer (1002),• defining the rules to be used with the smart rule definer (1003),• defining the functions to be run on a timed basis with the smart scheduled task definer (1004),• performing validation check definition with smart validation definer (1005),• defining the add-in code snippets to be used with the smart add-in definer (1006),• processing the incoming request is through the consume service (2005) when a request comes from a different environment via the space portal (2006).

46. The real flexibility and rule-based software development method according to claim 45, characterized by the process step of creating a user interface with a smart userinterface definer (1001) comprising the following process steps;• uploading the files of an interface template to be used via the smart user-interface definer (1001) and creating registration information in the system (100111000),• selecting smart object definitions for uploaded interface templates via the smart user-interface definer (1001 ) (100111001),• requesting the registration of the screen definition information that users will see (1001 |1002),• sending the information identified by the smart user-interface definer (1001) to the database / server (4001 ) and cache services (300) / cache server such as page cache service (3002), relational cache service (3004) via the neural system / neural server (500) (100111003),• checking the information incoming to the page cache service (3002) and the relational cache service (3004) with the current cache status (100111004),• directing processing according to the status checks of the page cache service (3002) and the relational cache service (3004) (100111005),• if it is desired to create a new user interface, the following process steps are performed;• sending a new registration request to the page cache service (3002) and the relational cache service (3004) (100111006),• sending a status message to the user on his / her electronic device via the neural system / neural server (500) to notify that the registration information has been temporarily added to the cache (100111007),• saving the registration status sign as in progress on the user side (1001 |1008),• transmitting the new information to the insert service (4002) of database service (400) via the neural system / neural server (500) in order to save it in the database / server (4001) (100111009),• saving the information incoming to the database service (400) to the database / server (4001) via the insert service (4002) (100111010),• informing the business service (200) via the neural system / neural server (500) to prepare the saved information for use (100111011 ),• calling the front-end builder service (2007) by looking at the message content coming to the business service (200) (100111012),• creating user interface front-end files using the relevant interface information via the front-end builder service (2007) (100111013),• uploading the relevant files created for the user interface to the server (1001 |1014),• transmitting the transaction completion message for the registration in the cache to the neural system / neural server (500) (100111015),• updating the registration flag status to completed via the page cache service (3002) and the relational cache service (3004) (100111016),• transmitting a message to the neural system / neural server (500 that the registration process has been completed to notify the user from the user screen / device (100111017),• updating the registration flag status to completed on the user screen / device (100111018),• if it is desired to update the existing user interface definition, the following process steps are performed;• sending a request to update existing information to the page cache service (3002) and / or the relational cache service (3004) (100111019),• transmitting the mentioned information to the update service (4003) of database service (400) via the neural system / neural server (500) inorder to update the updated information in the database / server (4001) (1001 |1020),• saving the information incoming to the database service (400) to the database / server (4001 ) ( 100111021 ) ,• sending the saved information to the business service (200) via the neural system / neural server (500) to prepare it for use (100111022),• calling the front-end builder service (2007) by looking at the message content incoming to the business service (200) (100111023),• creating user interface front-end files using the relevant interface information via the front-end builder service (2007) (100111024),• uploading the relevant files created for the user interface to the server (1001 |1025),• transmitting the transaction completion message for the registration in the cache to the neural system / neural server (500) (100111026),• updating the registration flag status to completed in the page cache service (3002) and the relational cache service (3004) (100111027)• transmitting a message to the neural system / neural server (500) that the registration process has been completed to notify the user (1001 |1028),• updating the registration flag status to completed on the user screen / device (100111029),• sending a status message to the user via his / her electronic device via the neural system / neural server (500) to notify that the cached information has been updated (100111030),• saving the registration status sign as in progress on the user side (1001 |1031 ),• termination of the process by informing the user via electronic device (1001 |1032).

47. The real flexibility and rule-based software development method according to claim 45, characterized by process step of defining the objects to be used with the smart object definer (1002) comprising the following steps;• requesting registration of object definition information via smart object definer (1002) (1002|1000),• sending the information identified by the smart object definer (1002) to the database / server (4001) and cache services (300) / cache server such as object cache service (3003) and relational cache service (3004) via the neural system / neural server (500) (1002| 1001 ),• checking the cache status of information with incoming to the object cache service (3003) and the relational cache service (3004) (1002| 1002),• directing processes according to the status checks of the object cache service (3003) and the relational cache service (3004) (1002| 1003),• when a new object is required to be create, the following process steps are performed:• sending a new record creation request to the object cache service (3003) and the relational cache service (3004) (1002| 1004),• sending a status message to the user on his / her electronic device via the neural system / neural server (500) to notify that the registration information has been temporarily added to the cache (1002| 1005),• saving the registration status sign as in progress on the user side (1002|1006),• transmitting the new information to the insert service (4002) of database service (400) via the neural system / neural server (500) in order to save it in the database / server (4001) (1002| 1007),• saving the information incoming to the database service (400) to the database / server (4001) via the insert service (4002) (1002| 1008),• transmitting the saved information to the business service (200) via the neural system / neural server (500) to prepare it for use (1002| 1009),• calling the code builder service (2008) by looking at the message content incoming to the business service (200) (1002|1010),• converting defined object information into source code with the code builder service (2008) (100211011 ),• Injecting source code files into the running system (100211012),• transmission of the transaction completion message regarding the registrations in the cache to the neural system / neural server (500) (1002|1013),• updating the registration flag to complete in the object cache service (3003) and the relational cache service (3004) (1002|1014)• Transmitting a message that the registration process has been completed to notify the user to the neural system / neural server (500) (1002|1015),• updating the registration flag status to completed on the user screen / device (1002| 1016),• if it is desired to update the existing object definition, the following process steps are performed;• sending an update request of existing information to the object cache service (3003) and relational cache service (3004) (1002| 1017),• transmitting the mentioned information to the update service (4003) of database service (400) via the neural system / neural server (500) in order to update the updated information in the database / server (4001 ) (1002|1018),• saving the information incoming to the database service (400) to the database / server (4001 ) via the update service (4003) (1002|1019),• sending the saved object information to the business service (200) via the neural system / neural server (500) to prepare it for use (1002| 1020),• calling the code builder service (2008) by looking at the message content coming to the business service (200) (1002| 1021 ),• converting defined object information into source code with the code builder service (2008) (1002| 1022),• Injecting source code files into the running system (100211023),• transmitting the transaction completion message regarding the registrations in the cache to the neural system / neural server (500) (1002|1024),• updating the registration flag status to completed in the object cache and the relational cache (1002| 1025)• transmitting a message to the neural system / neural server (500) that the registration process has been completed to notify the user (1002|1026),• updating the registration flag status to completed on the user screen / device (1002| 1027),• sending a status message to the user via the neural system / neural server (500) to notify that the registration information in the cache has been updated (1002|1028),• saving the registration status as in progress on the user side (1002|1029),• termination of the process by informing the user via electronic device (1002|1030).

48. The real flexibility and rule-based software development method according to claim 45, characterized by process step of defining the rules to be used with the smart rule definer (1003) comprising the following steps;• requesting registration of the rule definition via smart rule definer (1003) (1003|1000),• sending the information identified by the smart rule definer (1003) to the database / server (4001), cache services (300) / cache server such as the relational cache service (3004) and the ecosystem's own cache service (3006) via the neural system / neural server (500) (1003| 1001 ),• checking the information incoming to the relational cache service (3004) and the ecosystem's own cache service (3006) with the current cache status (1003|1002),• directing the transaction according to the status checks of the relational cache service (3004) and the ecosystem's own cache service (3006) ( 100311003),• when a new rule is required to be create, the following process steps are performed;• creating a new registration in the relational cache service (3004) and the ecosystem's own cache service (3006) ( 100311004),• sending a status message to the user on his / her electronic device via the neural system / neural server (500) to notify that the registration information has been added to the cache ( 100311005),• saving the registration status sign as in progress on the user side (1003|1006),• transmitting the new information to the insert service (4002) of database service (400) via the neural system / neural server (500) in order to save it in the database / server (4001) (1003| 1007),• saving the information incoming to the database service (400) to the database / server (4001) via the insert service (4002) (1003| 1008),• sending the saved rule information to the business service (200) via the neural system / neural server (500) to prepare to prepare it for use (1003|1009),• calling the code builder service (2008) by looking at the message content incoming to the business service (200) (1003|1010),• converting defined rule information into source code with the code builder service (2008) (100311011 ),• Injecting source code files into the running system (1003| 1012),• transmission of the transaction completion message regarding the registrations in the cache to the neural system / neural server (500) (1003|1013),• updating the registration flag to complete via the relational cache service (3004) and the ecosystem's own cache service (3006) (1003|1014),• transmitting a message that the registration process has been completed to notify the user to the neural system / neural server (500) (1003|1015),• updating the registration flag status to completed on the user screen / device (100311016),• if it is desired to update the existing rule definition, the following process steps are performed;• updating existing information in the relational cache service (3004) and the ecosystem's own cache service (3006) (1003|1017),• transmitting the mentioned information to the update service (4003) of database service (400) via the neural system / neural server (500) in order to update the updated information in the database / server (4001 ) (1003|1018),• saving the information incoming to the database service (400) to the database / server (4001 ) via the update service (4003) (1003| 1019),• sending the updated rule information to the business service (200) via the neural system / neural server (500) to prepare it for use (1003| 1020),• calling the code builder service (2008) by looking at the message content incoming to the business service (200) (1003| 1021 ),• converting defined rule information into source code with the code builder service (2008) (1003| 1022),• Injecting source code files into the running system (1003| 1023),• transmitting the transaction completion message regarding the registrations in the cache to the neural system / neural server (500) (1003|1024),• updating the registration flag status to completed via the relational cache service (3004) and the ecosystem's own cache service (3006) (1003|1025),• transmitting a message to the neural system / neural server (500) that the registration process has been completed to notify the user (1003|1026),• updating the registration flag status to completed on the user screen / device (1003| 1027),• sending a status message to the user via the neural system / neural server (500) to notify that the registration information in the cache has been updated (1003|1028),• saving the registration flag status as in progress on the user side (1003|1029),• termination of the process by informing the user via electronic device (1003|1030).

49. The real flexibility and rulebased software development method according to claim 45, characterized by the process step of defining the functions to be run on a time basis with the smart scheduled task definer (1004) comprising the following process steps;• requesting registration of the function definition that will run on a timed basis via the smart scheduled task definer (1004) (1004| 1000),• sending the information defined by the smart scheduled task definer (1004) to the database / server (4001 ) and cache services (300) / cache server via the neural system / neural server (500) (1004| 1001 ),• checking the cache status of information incoming to the cache service (300) (1004|1002),• directing the operation according to the cache service's (300) status checks (1004|1003),• if it is desired to create a new timed function, the following process steps are performed;• creating a new registration for a scheduled operation in the cache (1004|1004),• sending a status message to the user on his / her electronic device via the neural system / neural server (500) to notify that the registration information has been added to the cache (1004| 1005),• saving the registration status sign as in progress on the user side (1004|1006),• transmitting the new information to the insert service (4002) of database service (400) via the neural system / neural server (500) in order to save it in the database / server (4001) (1004| 1007),• saving the information incoming to the database service (400) to the database / server (4001) via the insert service (4002) (1004| 1008),• sending the saved timed function information to the business service (200) via the neural system / neural server (500) to prepare it for use (1004|1009),• calling the code builder service (2008) by looking at the message content incoming to the business service (200) (1004| 1010),• converting timed function information defined with the code builder service (2008) into source code (100411011),• injecting source code files into the running system (1004| 1012),• transmission of the transaction completion message regarding the registrations in the cache to the neural system / neural server (500) (1004|1013),• updating the registration flag status to completed in the cache (1004|1014),• transmitting a message that the registration process has been completed to notify the user to the neural system / neural server (500) (1004|1015),• updating the registration flag status to completed on the user screen / device (1004| 1016),• if it is desired to update the existing timed function definition, the following steps are performed;• updating existing information in the cache (1004| 1017),• transmitting the mentioned information to the update service (4003) of database service (400) via the neural system / neural server (500) in order to update the updated information in the database / server (4001) (1004|1018),• saving the information incoming to the database service (400) to the database / server (4001) via the update service (4003) (1004| 1019),• sending the saved timed function information to the business service (200) via the neural system / neural server (500) to prepare it for use (1004|1020),• calling the code builder service (2008) by looking at the message content incoming to the business service (200) (1004|1021 ),• converting timed function information defined with the code builder service (2008) into source code (1004| 1022),• injecting source code files into the running system (1004| 1023),• transmitting the transaction completion message regarding the registrations in the cache to the neural system / neural server (500) (1004|1024),• updating the registration flag status to completed in the cache (1004|1025),• transmitting a message to the neural system / neural server (500) that the registration process has been completed to notify the user (1004|1026),• updating the registration flag status to completed on the user screen / device (1004| 1027),• sending a status message to the user via the neural system / neural server (500) to notify that the registration information in the cache has been updated (1004|1028),• saving the registration flag status as in progress on the user side (1004|1029),• termination of the process by informing the user via electronic device (1004|1030).

50. The real flexibility and rule-based software development method according to claim 45, characterized by process step of defining the validation check with the smart validation definer (1005) comprising the following process steps;• requesting registration of the validation check definition via the smart validation definer (1005) (1005| 1000),• sending the information defined by the smart validation definer (1005) to the database / server (4001) and cache services (300) / cache server via the neural system / neural server (500) (1005| 1001 ),• checking the information incoming to the cache service (300) with current cache status (1005| 1002),• directing the operation according to the cache service's (300) status checks (1005|1003),• when a new validation check definition is required to be create, the following process steps are performed;• creating a new record for a validation operation in the cache (1005|1004),• sending a status message to the user on his / her electronic device via the neural system / neural server (500) to notify that the registration information has been added to the cache (1005| 1005),• saving the registration status sign as in progress on the user side (1005|1006),• transmitting the new information to the insert service (4002) of database service (400) via the neural system / neural server (500) in order to save it in the database / server (4001) (1005| 1007),• saving the information incoming to the database service (400) to the database / server (4001) via the insert service (4002) (1005|1008),• sending the business service (200) via the neural system / neural server (500) to prepare the validation check information for use (1005| 1009),• calling the code builder service (2008) by looking at the message content incoming to the business service (200) (1005| 1010),• converting defined validation control information into source code with the code builder service (2008) (100511011),• injecting source code files into the running system (1005| 1012),• transmission of the transaction completion message regarding the registrations in the cache to the neural system / neural server (500) (1005|1013),• updating the registration flag status to completed in the cache (1005|1014),• transmitting a message that the registration process has been completed to notify the user to the neural system / neural server (500) (1005|1015),• updating the registration flag status to completed on the user screen / device (1005| 1016),• if it is desired to update the existing validation check definition, the following process steps are performed;• updating existing information in the cache (1005|1017),• transmitting the mentioned information to the update service (4003) of database service (400) via the neural system / neural server (500) in order to update the updated information in the database / server (4001) (1005|1018),• saving the information incoming to the database service (400) to the database / server (4001) via the update service (4003) (1005| 1019),• informing the business service (200) via the neural system / neural server (500) to prepare the saved validation information for use (1005|1020),• calling the code builder service (2008) by looking at the message content incoming to the business service (200) (1005| 1021 ),• converting defined validation control information into source code with the code builder service (2008) (1005| 1022),• injecting source code files into the running system (1005| 1023),• transmitting the transaction completion message regarding the registrations in the cache to the neural system / neural server (500) (1005|1024),• updating the registration flag status to completed in the cache (1005|1025),• transmitting a message to the neural system / neural server (500) that the registration process has been completed to notify the user (1005|1026),• updating the registration flag status to completed on the user screen / device (1005| 1027),• sending a status message to the user via the neural system / neural server (500) to notify that the registration information in the cache has been updated (1005|1028),• saving the registration flag status as in progress on the user side (1005|1029),• termination of the process by informing the user via electronic device (1005|1030).

51. The real flexibility and rule-based software development method according to claim 45, characterized by process step of defining the add-in code snippets to be used with the smart add-in definer (1006) comprising the following process steps;• requesting registration of user-based code add-in definition via smart add-in definer (1006) (1006|1000),• sending the information defined by the smart add-in definer (1006) to the database / server (4001) and cache services (300) / cache server via the neural system / neural server (500) (1006| 1001 ),• checking the information incoming to the cache service (300) with current cache status (1006| 1002),• directing the operation according to the cache service's (300) status checks (1006|1003),• if it is desired to create a new user-based code add-in definition, the following process steps are performed;• creating a new record for a user-based code add-in in the cache (1006|1004),• sending a status message to the user on his / her electronic device via the neural system / neural server (500) to notify that the registration information has been added to the cache (1006| 1005),• saving the registration status sign as in progress on the user side (1006|1006),• transmitting the new information to the insert service (4002) of database service (400) via the neural system / neural server (500) in order to save it in the database / server (4001) (1006| 1007),• saving the information incoming to the database service (400) to the database / server (4001) via the insert service (4002) (1006| 1008),• informing the saved user-based code add-in information to the business service (200) via the neural system / neural server (500) to prepare it for use (100611009),• calling the code builder service (2008) by looking at the message content incoming to the business service (200) (1006| 1010),• converting defined user-based code add-in information into source code with the code builder service (2008) (1006| 1011 ),• injecting source code files into the running system (1006| 1012),• transmission of the transaction completion message regarding the registrations in the cache to the neural system / neural server (500) (1006|1013),• updating the registration flag status to completed in the cache (1006|1014),• transmitting a message that the registration process has been completed to notify the user to the neural system / neural server (500) (1006|1015),• updating the registration flag status to completed on the user screen / device (1006| 1016),• if it is desired to update the existing user-based code add-in definition, the following steps are performed:• updating existing information in the cache (1006|1017),• transmitting the mentioned information to the update service (4003) of database service (400) via the neural system / neural server (500) in order to update the updated information in the database / server (4001) (1006|1018),• saving the information incoming to the database service (400) to the database / server (4001) via the update service (4003) (1006| 1019),• transmitting the saved user-based code add-in information to the business service (200) via the neural system / neural server (500) to prepare it for use (100611020),• calling the code builder service (2008) by looking at the message content incoming to the business service (200) (1006| 1021 ),• converting defined user-based code add-in information into source code with the code builder service (2008) (1006| 1022),• injecting source code files into the running system (1006| 1023),• transmitting the transaction completion message regarding the registrations in the cache to the neural system / neural server (500) (1006|1024),• updating the registration flag status to completed in the cache (1006|1025),• transmitting a message to the neural system / neural server (500) that the registration process has been completed to notify the user (1006|1026),• updating the registration flag status to completed on the user screen / device (1006| 1027),• sending a status message to the user via the neural system / neural server (500) to notify that the registration information in the cache has been updated (1006|1028),• saving the registration flag status as in progress on the user side (1006|1029),• termination of the process by informing the user via electronic device (1006|1030).

52. The real flexibility and rule-based software development method according to claim 45, characterized by the process step of processing the incoming request if a request comes from a different environment comprising the following process steps:• making requests from any environment, over the communication network (2) (200|1000),• accepting the request from the external environment through the space portal (2006) in the business service (200) (200| 1001 ),• evaluating the validation status of the incoming request parameters by the smart validation definer (1005), if the validation check fails, giving an invalid parameter error message to the requesting environment and returning to the (200| 1000) process step, if the validation check is successful, transmitting the necessary information to the consume service (2005) via the neural system / neural server (500) (200| 1002),• checking the identity information of the incoming request source by the consume service (2005), in case of invalid identity, sending a user error message to the requesting environment via the neural system / neural server (500) and space portal (2006) and returning to the (200| 1000) process step, in case the identity is confirmed, the validation check of the parameters and values of the incoming request is provided by the smart validation definer (1005) (200|1003),• transmitting the relevant identity information from the space portal (2006) to the consume service (2005) in the business service (200) (200| 1004),• evaluating the validation status of the incoming request parameters in the consume service (2005), if the validation check fails, sending an invalid parameter error message to the requesting environment via the space portal (2006) and returning to the (200|1004) process step, if the validity check is successful, forwarding the request to the user cache service (3001 ) (200|1005),• checking the identity information of the request source coming to the user cache service (3001 ), returning to the (200|1004) process step in case of invalid identity, continuing the operations in case of valid identity (200| 1006),• transmitting the identity information of the request source to the neural system / neural server (500) to ensure that the identity information are saved or updated in the user cache service (3001) (20011007),• saving the information coming to the user cache service (3001) in a controlled manner and opening the user's session or extending the duration of the session (200|1008),• informing the consume service (2005) that the identity information has been saved (200|1009),• transmitting the relevant parameters of the user cache service (3001 ) to the neural system / neural server (500) and the rule selector (2001), determining the rules and / or user-based code add-ins that will work with the rule selector (2001 ) (200|1010),• running specified rules and / or user-based code add-ins via the rule operator (2002) (200|1011),• sending the results to the neural system / neural server (500) for saving to the user cache service (3001 ), other relevant cache services (300) and database / server (4001) (200|1012),• saving the created information to the user cache service (3001) and other related cache services (300) (200| 1013),• saving the output information to the database / server (4001) on the database service (400) via the insert service (4002) (200|1014),• upon completion of the registration process, sending the registration information to the consume service (2005) (200| 1015),• the consume service (2005) transmitting the output information to the space portal (2006) (200|1016),• space portal (2006) transmitting the information to the external environment server (200|1017).

Images