EP3049920A1 - Procédé et dispositif de génération et de production automatiques d'au moins une application logicielle - Google Patents

Procédé et dispositif de génération et de production automatiques d'au moins une application logicielle

Info

Publication number
EP3049920A1
EP3049920A1 EP14789530.4A EP14789530A EP3049920A1 EP 3049920 A1 EP3049920 A1 EP 3049920A1 EP 14789530 A EP14789530 A EP 14789530A EP 3049920 A1 EP3049920 A1 EP 3049920A1
Authority
EP
European Patent Office
Prior art keywords
model
application
data
user
client
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
EP14789530.4A
Other languages
German (de)
English (en)
Inventor
Rudolf Markus Petri
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Publication of EP3049920A1 publication Critical patent/EP3049920A1/fr
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code
    • G06F8/35—Creation or generation of source code model driven
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/22—Indexing; Data structures therefor; Storage structures
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/20—Software design
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/10—Requirements analysis; Specification techniques

Definitions

  • the present invention relates to a method and a computer-implemented device for the automated generation and provision of at least one client / server-based, preferably web-based software application with a user interface for a user.
  • the traditional creation and delivery of software applications for use is based on methods and techniques in which software applications are first created by programming and then installed and commissioned in an operating environment.
  • Model Driven Software Development creates the architecture of the application to be created as well as parts of the source code (class model) from a model (diagram in the graphical modeling language "Unified Modeling Language", UML diagram for short).
  • GUI graphical user interface
  • the source code must be translated into machine language after generation, deprogramming and supplementation with a compiler in order to make the program machine-readable and thus executable. Even with changes to existing software, the source code must be regenerated over and over again, bundled into a program and transferred to the runtime environment.
  • the created or changed software must be installed on a computer, if necessary configured and put into operation in order to be used by the users.
  • tools must first be used to program the source code of the application, which contains, among other things, the commands to the processor controlling the later application program.
  • the source code is translated with tools to machine-readable code and linked / compiled into an application program
  • the application program can be installed on a computer
  • the object of the present invention is to provide a method and a computer-implementable device with which a client / server-based, preferably web-based software application with a user interface can be generated automatically for a user and can be used for this Allow users to access data from a database without having to install the software application on a user's computer.
  • the software application should also be adaptable to the needs of the user in a particularly simple manner and require the least possible compilation effort.
  • a generated soft application does not have to be compiled or installed either on the (client) computer of a user or on a computer for the application platform, eg a (web) server. Rather, the transition from modeling to using a software application occurs without programming, compilation, and installation, so database building, application logic programming, or user interface configuration are not required to build new or change existing software applications.
  • a method according to the invention with which at least one client / server-based, preferably web-based software application with a user interface-preferably several software applications-is automatically generated and provided comprises at least the following steps: Provision of an application platform into which a user can log in via a network, such as the Internet or an intranet, Provision of at least one client-specific database in which data can be stored
  • the application model describes the mode of operation - and thus the subject matter, content and configuration - of the software application, a user interface and the data structure, and
  • model engine on the application platform for processing at least one application model and the access to data of the client-specific database, wherein in the inventive method further the model engine after logging in a user reads the application model at runtime and only at runtime based on the An application model generates a software application with application logic and user interface, wherein the application logic defines the processes that can be executed by the software application in operation and the user can access data from the client-specific database via the user interface, and
  • Commands of the user at the user interface concerning a particular data object are passed on to the model engine at runtime and the model engine accesses the user from the client-specific database using the application model and the application logic created at runtime in order to thereby in particular display and / or edit the data and / or enter and store new data.
  • the field of application of the present invention is thus the creation of (client / server-based, preferably web-based) software applications and their provision on an application platform for immediate use, eg as "software as a service”.
  • the application platform thus provides a runtime environment in which software components, such as the model engine, are executable to generate and provide the software application.
  • the application platform therefore has the task of using system tools to combine the software applications defined in application models via the respectively defined configuration with the functional application modules contained in the application platform, make them executable and ready for use. It is thus needed to create a software application at all and provide it to a user.
  • Client-specific here means that on a computer of the application platform, ie in particular on the same server, databases of multiple clients (customers) can be stored without the individual clients have access to each other databases.
  • a client-specific database with an application model to be read can thus be one of several client-specific databases that are stored in a central database of the application platform. Accordingly, several client-specific databases and / or several preconfigured application models can be stored in a database of the application platform.
  • a model engine is understood to mean a software component which makes it possible to link metadata elements of the application model with the data from the client-specific database.
  • a model engine can thus be used by a database management system to store, read, update, and delete data from a database.
  • the model engine has a translation and coordination function to generate from data elements of the application model specific data objects of the software application as well as to interpret commands on the user interface and process conditions stored in the application model, so that the command to access data the client-specific database and is displayed in the user interface.
  • the model engine is particularly capable of an application model that after logging in a user z.
  • the model engine can also be seen as an application generating device.
  • An application model thus completely describes the software application. It defines, among other things, access to the initial (root or start) interface of the software application after the user logs in, as well as how a command entered through the provided user interface and forwarded to the model engine the data in the client-specific database leads to thereby in particular display and / or edit the data and / or enter and store new data.
  • the application model can thus specify the object, content, configuration, and operation of the software application and serve to assemble, configure, and control software applications at runtime from provisioned application building blocks.
  • the application model is described in an XML document that can be read by the model engine to generate the software application at runtime.
  • the solution according to the invention thus makes it possible to use the limited resources of a data processing system more efficiently and to save additional, often very expensive resources. If many different (specialized) software applications are needed, many different software systems may need to be used. Since each software system requires its own system resources and, if necessary, its own technical configuration, the simultaneous operation of several different systems on a computer system is not efficient and may even be critical if the technical configurations are conflicting. For example, problems often occur with a change in the overall configuration of the DP system due to the replacement or release of components. Using the solution according to the invention, all software applications can be mapped only by means of application models and no different software systems have to be used. All applications (including individual applications) are operated on just one application platform.
  • the set of data belonging to the data object is read from the client-specific database before
  • a visualization of the object instances is generated depending on the read data on the user interface.
  • the application model preferably includes at least a meta-model and an application configuration model.
  • the meta-model defines generic metadata elements as well as data field structures for the user interface and / or attributes associated with the metadata elements.
  • the application configuration model specifies such a meta-model and defines data objects for the software application that derive from metadata elements of the meta-model by assigning concrete or all metadata elements specific roles to the software application to be created and deployed in the application configuration model.
  • the metadata elements are preferably self-referential, i. they can consist of additional metadata elements.
  • the meta model is preferably read at runtime and a class instance of a specific type and a attribute defined for each attribute for a metadata element are generated for each metadata element of a given hierarchy level ,
  • the meta-model may include a schema definition that describes metadata elements.
  • the meta-model in particular defines with which view types (views) a meta-element attribute, and thus in particular with which view types (views) a data field type can be represented.
  • view types and standardized user interface elements can be implemented as building blocks in the application platform.
  • the type of visualization of object instances generated by the model engine can also be predetermined by a view type defined for the data object in the application model.
  • any change in the meta-model can also lead to a change in the structure of the data provided from the client-specific database and possibly to a change of the software application at runtime.
  • an (XML) file which contains the meta-model is modified, whereby the data management is then changed in the case of an associated change in the specifications within the meta-model.
  • XML XML
  • the meta-model describes meta-data attributes for the metadata elements and associates them with standardized user interface elements and, in the client-specific database, data field types such that the meta-model for the software application data objects defines the representation of a data field structure in the user interface.
  • an application configuration model defines one or more software applications (eg, customer relationship management (CRM), product management, event management, music database management, etc.)
  • An application configuration model is assigned, which defines the possible deployable software application (s) and is stored in the client-specific database
  • a user account is also created, which assigns the user to one or more clients
  • the user after logging in automatically via a corresponding provided on the application platform client and rights management the intended for him application configuration model by the - preferably from at least one metamodel and at least one application configuration model built - application model could
  • certain functions of the software application may be described in a machine-readable manner that can be executed at runtime. Under such a function, e.g.
  • the application model includes, preferably in addition to a meta-model and an application configuration model Organization model in which at least one organizational structure of the organization, within which the software application to be generated at runtime is to be used, and / or a business process, which is to be mapped with the software application to be generated at runtime, are stored.
  • An organizational model thus includes, for example, a (static) structural model and, in this case, authorizes authorizations for processes and / or reporting structures provided by the generated software application.
  • an organization model may specify a business process model (dynamic, ie adapted for the respective software application within the same and the same organization) and hereby specifies the business processes which are to be technically supported by the generated software application.
  • the model engine comprises for the individual (sub) models of an application model, e.g. the metamodel, the application configuration model, and the organization model, different processing modules. So it can be provided that the model engine
  • the higher-level generation unit queries the first and second processing modules after loading the meta-model by means of the first processing module and after loading the application configuration model by means of the second processing module into a main memory for generating the software application and generates the software application at runtime.
  • the model engine has a (third) processing module for reading out an organization model which is contained in the application model and via which a check of the access rights to be granted in the software application is made possible at runtime.
  • the organizational model defines this, e.g. Users (groups) and structure information.
  • a first module the meta-model processing module (also called “Meta Model Manager”), reads the meta-model into memory and at runtime generates the concrete objects (instances), ie the concrete records
  • the application configuration model processing module reads the application configuration model into the memory, that is, the XML file that describes the application context of the software application.
  • a third module, the Organizational Model Processing Module reads out a functional organizational model, checks the access rights to applications, processes / workflows, data objects, etc.
  • the information required to generate the software application is queried by the three modules, ie which data objects are specifically assigned, how they are formed at runtime (inheritance), how the display is to be displayed on the user interface and which functions are used from the application platform etc.) and generates the software application at runtime.
  • different application models can be stored in a database of the application platform for different software applications, so that only one specific application model is read by the model engine at runtime to provide one of several different software applications and a user interface based on this application model is generated. in particular a first basic or start-up user interface that is displayed directly after a user logs in.
  • At least one client-specific database and / or at least one preconfigured application model is stored in a local database of a user, while the application platform is provided by a server system.
  • the application platform can thus be operated centrally, in particular in the "cloud", while the data storage for a software application of a user generated at runtime is locally stored there.
  • standard application models and / or standard meta-models may be stored on the application platform.
  • a standard application model or standard meta-model is then modifiable by an application-modeling device executable on the application platform to make it customizable for an individual software application.
  • a modified standard application model or meta-model is then storable via the application model creation device as another application model or metamodel.
  • an application model is formed only from a reference to a standard application model and possibly a special configuration model, wherein in the configuration model only any deviations from the respective standard application model are specified.
  • a standard application model is preferably kept here in an application model memory.
  • Such an application model memory is preferably stored in a central database in which the client-specific databases are also stored.
  • a further aspect of the present invention is a computer-implemented device for the automated generation and provision of at least one client / server-based, preferably web-based software application with a user interface for a user as claimed in claim 17.
  • a device which can be used on a computer, in particular a ( Web) server is installed, can be designed and provided in particular for carrying out a method according to the invention.
  • An inventive device comprises at least the following: an application platform into which a user, preferably via a network, can log in, at least one client-specific database on the application platform in which data can be stored, at least one application model stored in the client-specific database the generation of the at least one software application, wherein the application model describes the functioning of the software application, a user interface and the data structure are processable, and a model engine on the application platform for processing at least one application model and accessing data of the client-specific database.
  • the application model can be read out by means of the model engine, and based on the application model, also by means of the model engine, a software application can be generated that contains a user interface via which the user can access data from the client-specific Database can access.
  • the model engine is designed in such a way that commands of the user at the user interface of the software application that it relates to, which are related to a specific data object are passed on to the model engine at runtime and the model engine to the user using the application model Access to data belonging to the data object allowed.
  • the application platform can have a control device which loads the application model from the client-specific database after logging in of a user and loads it into the working memory of a computer on which the device is installed.
  • a device may comprise an application model creation device and / or an application model memory.
  • an easily manageable and variable possibility is provided to use any number of models at runtime simultaneously and / or in parallel, and thus to run any number of software applications based on any number of different application models on the same platform.
  • the models can also be optimized during runtime.
  • the application model of the software application is generated from an application-independent meta-model and an application-related configuration model. Subsequently, a client-specific database is created from an empty database and the application model. At runtime, one finally reads in the application platform
  • Application generating device the model engine used in the client application-specific database and automatically generates the immediately usable software application from the application logic and interface description contained therein as well as the generic views (GUI) and functions contained in the application platform.
  • GUI generic views
  • a computer program product for operating a computer, in particular a web server, which has machine-readable code which, when executed on the computer, is designed to cause the computer to carry out a method according to the invention.
  • a further aspect of the present invention is a machine-readable storage medium having machine-readable program code which is designed to be executed on a computer, in particular a web server, and to cause the computer to execute a method according to the invention when executing the program code.
  • a computer-implemented device for producing a computer program product by means of which a method according to the invention can be executed, in which an application model comprises at least one meta model and one application configuration model.
  • an application model comprises at least one meta model and one application configuration model.
  • Such a device according to the invention comprises at least:
  • a first generation module for creating a meta-model, wherein metadata elements are defined in the meta-model and data field structures for the user interface, attributes and / or functions associated with the metadata elements are defined, and
  • a second creation module for creating an application configuration model, wherein the meta-model is specified via the application configuration model and data objects for the software application are derived from metadata elements of the meta-model by providing concrete roles in the application configuration model for the software application to be created and deployed at runtime be assigned to.
  • At least one build module defines at least one graphical user interface through which an operator may create a meta-model and / or an application-configuration model.
  • an operator may create a meta-model and / or an application-configuration model.
  • the meta-model and / or the application configuration model include at least one XML document, and the first and / or second generation modules are provided to create and / or modify an XML document to create the respective model.
  • the model engine works with application models that are described exclusively in XML documents.
  • the device comprises, in addition to the first creation module (meta-model creation module) and the second creation module (application configuration model creation module), a third creation module for creating an organization model already mentioned above (organization model creation module).
  • the individual modules of the device thus serve here to create the corresponding submodels of the application model.
  • Fig. 1 is a flowchart for a variant embodiment
  • Fig. 2 is a schematic representation of a variant embodiment
  • Fig. 3 is a schematic representation of the generation of a graphic
  • 4B is a schematic representation of the generation of a
  • 4C is a schematic representation of the generation of a
  • 5A is a schematic representation of an instantiation at runtime according to a conventional object-oriented approach for developing a software application for the embodiment of FIG.
  • FIG. 5B shows a schematic representation of an instantiation at runtime according to the inventive method for the embodiment of FIG. 4A;
  • 6A is a schematic representation of the functions of a
  • 6B is a schematic representation of the functions of
  • FIG. 1 initially shows a flow chart for an embodiment variant of a method according to the invention for the automated generation and provision of a client / server-based, preferably web-based software application AW with a user interface GUI for a user.
  • the illustrated flowchart also includes phases for the creation of an application model AM and the assignment of user rights by a tenant management device CA (English, "serves administrator"), which in advance (Section I in Figure 1) by a provider the software application AW are to be made before it is automatically generated when needed at runtime (Section II) and provided for use, ie, is usable.
  • a tenant management device CA English, "serves administrator”
  • the core of the illustrated embodiment variant is the generation and provision of the software application at runtime without programming.
  • an application model designer AM (application model designer) of an application-independent meta-model MM and an application-related configuration model or application configuration model AKM generates a (here: data-oriented) application model AM of the application. not shown) and the application model AM a client-specific database CSD (engl., "serves specific database”).
  • a model engine ME reads out the application model AM lying in the client-specific database CSD.
  • This model engine generates the software application AW from an application logic AL described in the application model AM and a surface description OB also contained therein, as well as from generic functions and generic view types (views) for the graphical user interface GUI.
  • the generic functions and view types are implemented in an application platform on which, as the runtime environment, in particular the application model creation device AMD, the client management device CA and the model engine ME are executable.
  • FIG. 1 A variant embodiment of a computer-implemented device S1 according to the invention, with which the variant of a method according to the invention described with reference to FIG. 1 is executed, is illustrated in FIG.
  • the device S1 not only an automatic generation and provision of software applications at runtime on a preferably web-based application platform is possible, but also a creation of the software applications before a first use using the application model creation device AMD and the client management device CA.
  • the device S1 includes an application platform with a (generic) user interface GUI, the model engine ME and a central database DB, in which several client-specific databases CSDi .. x are stored. From these client-specific databases, the structure of two databases CSDi and CSDx is shown in greater detail by way of example, in which data sets DS are stored.
  • the device S1 comprises the client management device CA and the application model creation device AMD, which run as tools on the application platform. Using the AMD application model builder, concrete platform-dependent meta-models and application configuration models can be created and managed based on an abstract platform-independent meta-meta-model (not shown).
  • FIG. 2 shows an individual meta-model MMi of the client-specific database CSDi and a standard meta-model MMSTANDARD.1 which are stored in an application model repository AMR of the device S1 as part of a standard application model AMSTANDARD.I becomes.
  • a metamodel MMi or MMSTANDARD.I is a schema definition that describes building blocks in the form of metadata elements. From a meta model MMi or MMSTANDARD.I, a (client-specific) database model (without figure) is derived.
  • meta-model MMi or MMSTANDARD.I defines the representation of the data field structure of the data object types in the user interface GUI by describing meta-element attributes in the metamodel MMi or MMSTANDARD.I and the generic user interface GUI data field types and standardized user interface elements (eg input fields with cardinalities ) are assigned automatically.
  • the application configuration model AKMi or AKMSTANDARD I defines the remaining part of the surface. It defines for each data object of the application AW with which view types (views) it should be displayed in which contexts (eg single view, list view).
  • the view types and standardized user interface elements are each implemented as building blocks in the application platform.
  • the presentation on the user interface GUI can be subsequently modified by means of the application model creation device AMD.
  • An application configuration model AKMi or AKMSTANDARD I describes the structure and process organization basics and conditions of a software application AW the respective client-specific database CSDi or CSDx (ie organizational units, processes, roles, users, rights), the business processes to be supported and corresponding workflows, a concrete data storage DH (compare FIG.
  • the application configuration model in FIG. 2 by way of example AKMi or AKMSTANDARD.-I, accordingly specifies the subject, content, configuration and mode of operation of an application AW and serves to assemble the application AW at runtime from the application modules, to configure them and to control their behavior.
  • An application configuration model AKMi or AKM S TANDARD is also used to specify the respective meta-model MMi or MMSTANDARD, ie to form concrete objects from the abstract objects defined with the metamodel MMi or MMSTANDARDJ by filling the abstract objects with concrete data at runtime and thus concretized, typed and configured.
  • predefined attributes can also be modified via the respective meta-model MMi or MMSTANDARDJ.
  • a meta-model MMi or MMSTANDARDJ and an application configuration model AKMi or AKMSTANDARD together form an application model AMi or a standard application model AMSTANDARD.L
  • the respective application model AMi or AMSTANDARD.1 completely describes a software application.
  • a (software) application AW is not defined by a concrete professional class model that has to be programmed, but by an application model AMi or
  • An application model can be provided here as a standard application model AMSTANDARD or as an individual application model AMi. It accordingly describes a standard software application or an individual software application.
  • an application model AM 2 for the software application AW to be generated at runtime which consists only of references V-AMSTANDARD to the standard application model AMSTANDARD, I and possibly Deviations AB-AMSTANDARD is formed by the standard application model AMSTANDARD.
  • a standard application model AMSTANDARDJ can therefore be extended or modified at any time by additional configuration information created with the application model creation device AMD, the standard application models still being kept in the application model memory AMR.
  • a final determination is not associated with the original purpose of an application model as a standard or individual application.
  • a once created application model AMi or a standard application model AMSTANDARDJ can be used as often as desired by referencing or copying and optionally modified as a new application model (in a client-specific database CSDi .. x and / or the application model memory AMR) are stored. Consequently, the device S1 can simultaneously contain and use any number of application models.
  • a data storage DH of an application is created in advance with the aid of the client management device CA.
  • an empty database (not shown) is first created, the desired application model, e.g. AMi, passed to the database.
  • the database model i.e. the concrete data structure, is generated in which the actual data can then be stored.
  • the creation of an application and at the same time its provision for use takes place automatically at runtime.
  • a control unit of the application platform right-controlled loads the application model, e.g. AMi, and it loads in the main memory of the computer (without figure) on which device S1 is installed.
  • the model engine ME which reads out the instantiated application model AMi (eg for a CRM application), evaluates the configuration information from the application model AMi and, at runtime, the corresponding one
  • the object of the application is generated by converting abstract data model objects (such as "organization") into concrete objects (such as "customer (company)”) at runtime and assigning them to the application.
  • Object relationships (such as "belong to an organization (s) persons") are also at runtime using the Application configuration model AKM evaluated and typed (ie, for example, can be assigned to a "customer” only a "contact person (customer)” and not any person).
  • the Model Engine ME forwards the necessary parameters to the generic GUI blocks with which the user interface GUI is then generated.
  • the model engine ME thus provides the objects that are necessary for the processing and display of corresponding data. If a data record is to be processed by calling a function, the model engine ME generates the required object in the working memory at runtime. Objects have the class "model instance.” The class "model instance” consists of the class “ModelElement” and the parameter defined for this "ModelElement” in the application configuration model AKM. The model engine ME therefore generates model instances for further processing by means of factory methods and evaluation of the application model AM.
  • the model engine ME is implemented in such a way that it can map and manage any models or structures.
  • a functional class model of the model engine ME itself basically consists of two classes: nodes and attributes. Nodes can contain attributes. Furthermore, nodes can be linked to any other nodes. If an application model is transferred, the model engine ME is able to derive a framework of nodes with properties (attributes) from this model.
  • a specialized logic which must already be defined in the conventional software development during the programming, is given by this mechanism only at runtime in the form of the respective application model. This will be explained in more detail in particular in connection with the attached FIGS. 4C and 5B by means of an exemplary software application.
  • Application model AM dependent on defined conditions.
  • Each request or command e.g., "Show customer data" is first directed to the model engine ME.
  • Function module on (eg "Generate document") and provides the data according to the Application model AMi defined information, ie, with the corresponding view, on the user interface GUI.
  • the application platform automatically assigns each data area a list view and corresponding basic functions - such as display, add, edit, delete, copy - to.
  • each record DS may automatically be assigned, for example, a detail view and associated basic functions - such as add, edit, save, delete, copy.
  • view type is preferably already a basic configuration deposited, which is specified by information or specifications from the associated application configuration model AKMi or possibly even changed.
  • the basic configuration may include, for example, indexing, presentation as a table with empty column names (as transfer parameters), filter functions, basis functions, etc., which may be provided by the application configuration model in the form of data object information, assigning selected fields of the data object to columns of the table , the assignment of special functions, etc. is specified (see also Figure 3).
  • the model engine ME If the user requests e.g. From a list of objects (customers, prospects, contact persons, etc.) by selecting a data object (eg customer) the associated records DS (eg the customer data), the model engine ME reads the application model (eg AMi) and generates the object instances in memory. The model engine ME requests the values for the data object from the client-specific database (CSDi) via a database access layer (component of the database DB, not shown separately) and transfers the visualization of the object instances according to the information stored in the application model (AMi) via the associated view type (here: a list view) - to the generic user interface GUI.
  • a database access layer component of the database DB, not shown separately
  • the generic user interface GUI provides the view type and, according to the assignment made in the data model, the standardized user interface elements belonging to the data object and displays them on the user interface GUI.
  • the data field structure and representation in the user interface GUI is automatically removed from the Metamodel (MMi) derived.
  • functions of the (software) applications AW are preferably also implemented in the application platform as generic function modules and are specified and configured at runtime by the respective application model, eg AMi or AM 2 .
  • the application model defines whether a function should be displayed as a button or automatically triggered. If the latter should be the case, it is further specified which conditions should lead to an execution of the function.
  • a specific function is executed after saving a data set DS if the current date is "today.”
  • the application model stores which label the button receives and which preconditions If necessary, ie, whether the execution of the function should be dependent on the rights, it is also defined in an application model which data object (eg person, task, appointment) should be transferred from the data model as transfer parameter and which postconditions exist, ie For example, if and what should be done after the function has been executed, this means, for example, that an attribute "last contact" for a data object person is updated to "today" and a follow-up is created.
  • data object eg person, task, appointment
  • a solution according to the invention differs from the conventional methods of software development and provisioning in that it involves the transition from the model definition to the use of a software application AW without programming, compilation and installation.
  • the solution according to the invention also offers the possibility of simultaneously using any number of application models AM at runtime and thus to operate any number of applications AW based on any number of different meta models MM on the same platform.
  • the application models AM can also be optimized at runtime.
  • conventional methods require a rigid metamodel.
  • the aim is to create a database application AW (called "jukebox") for the management of audio and video CDs / albums, which in addition to the elementary functions such as displaying, editing, saving and deleting, also the sorting of the data records , which allows you to print out lists and search for data, display a list of the data objects contained in list views and display the information about a data object in the form of a detailed view.
  • AW database application
  • FIG. 4A the content of an application model AM (shown in abstract) for this embodiment of a software application with its meta-model MM and its application configuration model AKM is shown in excerpts.
  • the illustrated application model AM further defines certain rules, that is, in particular functions that are to be executed at runtime, as well as workflows.
  • FIG. 4B schematically shows the generation of a data storage DH for the software application "Jukebox" from the meta-model MM
  • FIG. 4C schematically illustrates the generation of a class model with classes and class attributes from the meta-model MM at runtime by a model engine ME.
  • FIGS. 5A and 5B compare the different instantiations at runtime in a conventional object-oriented approach and in the solution according to the invention for the software application "jukebox".
  • the application model builder AMD first builds the application model AM for the Jukebox application by selecting the meta-model MM and assigning it to the application by referencing inheriting the basic properties of the data objects, which can now be extended to meet specific application needs At the same time, inherited properties can also be marked, for example, to hide data fields at runtime.
  • the metamodel MM already defines the basic functions based on a schema definition and models the user interface of the application, since the metamodel MM specifications based on referencing automatically apply to the application model AM of the "Jukebox" application Metamodel MM was created by copying a standard metamodel MMSTANDARD I.
  • the application model creation device AMD now also describes an application configuration model AKM.
  • the model for the jukebox e.g. the following specifications have been made:
  • the application configuration model for the role "artist” is described as derived from the meta-role "person” of the metamodel MM.
  • the Role “Artist” is defined here by a parameter “Role” in the application configuration model AKM, which is to be assigned the value "Artist”, where the assignment to the meta role "Person” takes place via a path.
  • Role in the application configuration model AKM, which is to be assigned the value "Artist”, where the assignment to the meta role "Person” takes place via a path.
  • the application configuration model AKM defines that for each newly created person the role "Artist” is to be set and at the same time only those persons (in the list) are shown who also have the role "Artist”.
  • a data object "Artist” is derived via a parameter "Role” from the data area "Person” of the meta-model MM
  • An adaptation or extension of the data object "Artist” could take place via further parameters by means of the application configuration model AKM.
  • the artist data item could be expanded to include an artist name field that does not exist in the person metadata element.
  • the application “Jukebox” is completely described by the application model AW comprising the meta-model MM and the application configuration model AKM, in particular its database model DBM for the database DB standing behind it (compare FIG. 4B).
  • a database (without a figure) is created, the created application model AM is transferred to the database for the "Jukebox” application, and the specific data structure is automatically generated.
  • the generation of the "Jukebox” application at runtime after a user logs in is as already described above described.
  • the abstract objects “Person” and “Product” are specified by the roles “Artist” and “Album” respectively.
  • the meta-model MM is read in at runtime for this purpose.
  • a framework of nodes with properties is derived from this, in that links already defined in the meta-model MM are read in the same way and mapped in each case as ModelAttributes.
  • the user now wants to collect data about an album and assign it to an artist ("artist"), assuming that a record for an "artist” data object has already been created and the user has opened the list of albums.
  • the marking of the desired album record and the call of the function "show” (by pressing a button "Show") on the user interface GUI causes the corresponding request to be routed to the model engine ME.
  • the command is passed to the model engine ME, which in turn reads the application model AM, evaluates the user's rights, passes the command to release the record for processing to the database DB or the client-specific database CSD and the Command to change the display in the edit / input mode to the user interface GUI passes.
  • More complex commands and functions are mapped using the rules of the application model AM.
  • the rules are defined in the application model AM according to the standards usual for rule-based systems.
  • the execution of a command defined here is triggered by a condition and a trigger and is carried out automatically.
  • a “calculatesum” function defined under “Rules” in the application model AM for the "Jukebox” application calculates the total value of the album collection based on purchase prices of each album.
  • the model engine ME reads out the application model AM with the rules stored there, evaluates the conditions according to the application model AM, transfers the parameters to the other Execution of the respective command and accepts the result for further processing, ie, for example, for display on the user interface GUI.
  • GUI-FK of a user interface of a computer-implemented device for creating, in particular, an application model AM for a software application and the application platform on which a software application can run are illustrated by way of example with FIGS. 6A and 6B.
  • FIGS. 6A and 6B surface functions GUI-FK of a user interface of a computer-implemented device for creating, in particular, an application model AM for a software application and the application platform on which a software application can run are illustrated by way of example with FIGS. 6A and 6B.
  • FIGS. 6A and 6B surface functions GUI-FK of a user interface of a computer-implemented device for creating, in particular, an application model AM for a software application and the application platform on which a software application can run are illustrated by way of example with FIGS. 6A and 6B.
  • the generation and provision of a software application AW with support of stored business processes is possible by providing an organizational model OM in addition to a meta-model MM and an application configuration model AKM.
  • FIG. 6A shows system tools whose functions can be used by an operator via a user interface in order to generate an application model AM for a software application in a simple manner and without in-depth programming knowledge.
  • an application model AM should comprise a plurality of submodels or submodels in the form of a meta model MM, an application configuration model AKM and an organization model OM.
  • the device shown schematically in FIG. 6A now has inter alia an application model creation device AMD with several modules for the individual submodels of the application model, thus a meta-model creation module MMD, an organization model creation module OMD and an application configuration model creation module AKMD.
  • a rule creation module RD in addition to the application model creation device AMD, a rule creation module RD, a workflow creation module WFE, a test tool TS, and (standard) view building blocks VW are provided.
  • the surface functions GUI-FK realized by this will be described in more detail below.
  • the meta-model creation module MMD (English, "meta model designer") is used to describe the data storage DH of a software application AW and to manage the created meta-models Using a meta-model MM, the data objects and object relationships / structures of an application AW are to be defined with it For example, the metamodel is technically available as an XML schema file
  • the organizational models OM and application configuration models AKM are also described in XML documents: XML is not a programming language, but only a metalanguage, so XML documents themselves contain no commands and loops like a programming language (and therefore no instructions the processor, as is the case with conventional "hard-coded” applications.)
  • the documents will later be evaluated by the Model Engine ME to derive the commands to create.
  • the meta model MM already defines object-related rules (in particular plausibility checks) and models the user interface GUI of the application AW. In addition, it defines the representation of the data field structure of the data object types in the user interface GUI by automatically assigning standardized GUI elements of the generic user interface (for example input fields together with cardinalities) to the data field types described in the meta model MM.
  • the view types and standardized GUI elements are implemented as building blocks in the application platform.
  • the organizational model creation module OMD model organization designer
  • OMD is used to model both the process organization and the task-related, functional structures of an organization or project (as a time-limited organization) the software application AW to be created needs to be.
  • An organizational model OM therefore includes, for example, at least one structural model, a process model and a business process model separately.
  • the structural model and the process model lay a rather static view of an organization, as it depicts its organizational structure and the ideal process organization.
  • the information from a structural model can be used, for example, to assign structural, that is, task-oriented authorizations, evaluate reporting structures in the user company differentiated according to organizational units, manage components and functions in business management, in particular HR applications, or handle tasks arising in the context of business workflows Assign to editors.
  • a process model describes the ideal process structure of an organization, based on the classic division / categorization into core, management, and support processes. The processes are broken down hierarchically and displayed in more detail from level to level.
  • the business process model is dynamically oriented. It describes the concrete business processes that are to be technically supported, among others, by the software application AW to be created.
  • the individual process modules (activities) are selected from the (static) process model according to the business processes to be supported, brought into the desired sequences and combined with linking and execution rules.
  • the business processes depicted in this way will later be used as the basis for execution as workflows.
  • the application-specific configuration settings are bundled in the application configuration model AKM, which are managed using the application configuration model creation module.
  • an application configuration model AKM serves to specify the meta model MM, ie to form concrete objects from the abstract objects defined with the meta model MM by filling the abstract objects with concrete data at runtime and thus concretizing, typing and configuring them.
  • the predefined attributes can also be modified.
  • the application configuration model AKM also specifies and configures the functions implemented in the application platform as generic function modules.
  • a function for example, it is defined whether a function should be displayed as a button or automatically triggered. If the latter is to be the case, it is further specified which conditions should lead to an execution of the function (eg after saving a data record as well as if the current date is "today".) If the function is to be displayed as a button, then The created application model AM stores, which label the button receives and which preconditions exist, eg, whether the execution of the function should be dependent on the rights.Furthermore, it is defined which data object (eg person, task, appointment) from the meta model as transfer Parameter and which postconditions exist, ie, whether and after the execution of the Function is still to take place (eg "last contact” to "update today", create follow-up, etc.).
  • data object eg person, task, appointment
  • the application model creation device AMD furthermore also has overarching functionalities which serve to create the application model AM from the abovementioned submodels and the other application components (rules, etc.).
  • Such an application model AM is created by controlling the interaction of the submodels (MM, OM and AKM), model building blocks and application components and the concrete characteristics of the business objects via configuration.
  • the various configuration options of the individual submodels and application components are functionally combined in the application model creation device AMD.
  • Some application components are z. B. can be created separately by the rule creation module RD and the workflow creation module WFE.
  • Rule Authoring Module The role of Rule Authoring Module is to define and capture business rules and facts, and to enable centralized management, review, and deployment.
  • Business rules (such as "When the sun is shining, the ice cream costs 50 cents more.") Play an important role in almost all areas of the company, describing not only the organizational knowledge and control information relevant to these areas of business, but also the business logic of Software systems designed to support these business units determine how a software system or business process controlled by an AW software application should behave.
  • the business rules are preferably managed in a central repository, maintained and stored in a revision-proof manner, to make them available for the creation of applications AW, and also for the basic behavior of an application AW later on
  • the business rules can still be changed, simulated, checked and made available at runtime Structured tasks and processes, in particular the business processes defined in the organizational / process model, should also be processed with the help of a workflow Management "can be supported in terms of information technology and, if necessary, automated, for which the workflow creation module WFE is helpful.
  • a workflow is a workflow (alternatively business transaction or general operation) that is built up of individual activities that relate to parts of a business process or other organizational processes.
  • the workflow describes the operational-technical view of the (business) processes to be supported. Ideally, this description is made so precisely that the following activity is determined by the outcome of the preceding one. The individual activities are therefore dependent on each other.
  • a workflow has a defined start, an organized process and a defined end. He is the part of the (business) process that can be carried out with IT support. Workflows are characterized by a coordinative character.
  • a workflow is typically achieved by sequencing and parallelizing the work steps. Synchronous activities are strictly separated.
  • the workflow creation module WFE is used to model and configure concrete workflows. Here it can realize the following functions:
  • the test tool TS also provides functionalities for the constructive and analytical quality assurance in order to avoid any errors in the created application model AM or in a software application AW generated thereby, or at least to be able to determine them at an early stage.
  • the model engine ME functions provided by the application platform are outlined using different functional components, such as the model engine ME.
  • a rule engine RE a workflow engine WE
  • a function module FK a system administration module SYS
  • the model engine may include different processing modules for the submodels MM, OM, and AKM of an application model AM, eg, a meta-model processing module, an application configuration model processing module, and an organization model manager processing module.
  • rule engine RE comply with common standards for rule engines and consist of e.g. out:
  • the workflow engine WE is equipped, for example, with the following technological core components:
  • functions that can be used or can be called up within an application model are made available via the function module FK.
  • Functions essentially determine what a generated software application AW can do. For example, they serve to perform operations on data and to produce processing results. In practice, the operations can be composed of a wide variety of parameters and thus can be arbitrarily complex.
  • functions are implemented as standard functions, so that they can be combined at runtime with any application models AM and application components.
  • elementary functions are ever-recurring, basic functions from which other functions can be formed. Examples include saving, copying or deleting data or sending e-mail.
  • the complex functions are composed of elementary functions by means of basic operations, concatenation, differentiation or integration. They can also be model-specific configurable. Examples of complex functions are: - sorting and searching,
  • the configurable functions must be adapted to the specific application model. Examples of such functions are:
  • the functions are implemented in the application platform as generic function blocks, which must be developed conventionally.
  • the configurable functions can be specified and configured at runtime by the application model AM.
  • the application model AM for example, - as described above - defines whether a function should be displayed as a button or automatically triggered.
  • the system administration module is a central technical component of the application platform. Its task is to provide the administrative interfaces for setting up and managing the entire system and to support its smooth operation. It preferably provides the following functionalities:
  • the invention proposes a method and a technical device for automatically generating software applications AW without having to be able to program, compile and / or install.
  • Applications are preferably first defined / described with the help of appropriate tools in holistic models and then generated and configured model-driven with the necessary data structures (classes / data and business objects), business / application logic and views.
  • an application is only created at runtime, ie when the user logs in. Only at this time is an application model AM, for which the user is authorized, loaded into the cache of the web / application server and read into a model engine ME and processed.
  • the application AW itself is generated from the application logic AL and surface description contained in the application model AM and the generic application modules contained in the application platform.
  • the application model AM In this case, in the application model AM, all information relevant for an application AW is shown (including the application purpose or context, the roles and access rights of the user, etc.). After checking the roles and rights of the user, the appropriate startup screen is generated. Also with each further action in the application AW (whether executed by the user or automatically by the system), first the application model AM is read out and processed, which then specifies the further behavior of the application AW.
  • server and client-side operations must be performed.
  • Components of an overall system comprising at least one (web) server and at least one client are accordingly in a preferred embodiment:
  • a database is not necessarily required (eg for the storage of application models AM). It is also possible to work with file systems if only XML documents / files are used. However, if a database is used, a non- Relational database server considered advantageous (eg an XML database). Nevertheless, the use of other database technologies is basically possible.
  • Each client is set up its own database.
  • the databases can be assigned to any number of database servers. These in turn can be operated completely independently of the application platform and distributed as desired.
  • the application platform can also be parallel by addressing the various databases in which the different application models AM are located to provide any number of different applications.
  • a “cloud” solution based on the invention can be achieved, moreover, that a user in his own (individual or individualized) software applications know-how and its data for security reasons secured locally and thus stored locally, without on
  • the data management and the application models AM, in which the business / application logic AL of the software applications AWA is mapped, can be distributed arbitrarily, ie also to local resources.
  • V-AMSTANDARD Reference to standardized application model VW view building blocks

Abstract

La présente invention concerne un procédé et un dispositif, mis en œuvre sur ordinateur, servant à générer et produire automatiquement au moins une application logicielle client/serveur, de préférence via l'internet, qui comporte une interface destinée à un utilisateur. Selon l'invention, il est prévu pour cela au moins : - une plate-forme d'application à laquelle un utilisateur peut se connecter, - au moins une base de données (CSD) spécifique au client dans laquelle des données peuvent être mémorisées, - au moins un modèle d'application (AM) mémorisé dans la base de données (CSD) spécifique au client et servant à générer au moins une application logicielle (AW), le modèle d'application (AM) permettant de décrire de façon traitable le mode de fonctionnement de l'application logicielle (AW), une interface utilisateur (GUI) et la structure de données, - et un moteur de modèle (ME) disposé sur la plate-forme d'application et permettant d'accéder aux données de la base de données (SDR) spécifique au client. Selon l'invention, le moteur de modèle (ME) lit au moment de l'exécution le modèle d'application (AM) après la connexion d'un utilisateur, et génère seulement au moment de l'exécution, sur la base du modèle d'application (AM), une application logicielle (AW) comportant une logique d'application (AL) et une interface utilisateur (GUI), la logique d'application (AL) définissant les processus exécutables en fonctionnement par l'application logicielle (AW) et l'utilisateur pouvant accéder aux données de la base de données (CDD) spécifique au client via l'interface utilisateur (GUI), des instructions de l'utilisateur au niveau de l'interface utilisateur (GUI), concernant un objet de données particulier, étant transmises au moment de l'exécution au moteur de modèle (ME) et le moteur de modèle (ME) permettant à l'utilisateur, avec recours au modèle d'application (AM) et à la logique d'application (AL), générée au moment l'exécution à partie de celui-ci, un accès aux données, appartenant à l'objet de données, dans la base de données (CSD) spécifique au client.
EP14789530.4A 2013-09-27 2014-09-26 Procédé et dispositif de génération et de production automatiques d'au moins une application logicielle Ceased EP3049920A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE102013219655 2013-09-27
PCT/EP2014/070663 WO2015044374A1 (fr) 2013-09-27 2014-09-26 Procédé et dispositif de génération et de production automatiques d'au moins une application logicielle

Publications (1)

Publication Number Publication Date
EP3049920A1 true EP3049920A1 (fr) 2016-08-03

Family

ID=51795610

Family Applications (1)

Application Number Title Priority Date Filing Date
EP14789530.4A Ceased EP3049920A1 (fr) 2013-09-27 2014-09-26 Procédé et dispositif de génération et de production automatiques d'au moins une application logicielle

Country Status (3)

Country Link
US (1) US10296305B2 (fr)
EP (1) EP3049920A1 (fr)
WO (1) WO2015044374A1 (fr)

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10956422B2 (en) 2012-12-05 2021-03-23 Oracle International Corporation Integrating event processing with map-reduce
WO2015044374A1 (fr) * 2013-09-27 2015-04-02 Petri Rudolf Markus Procédé et dispositif de génération et de production automatiques d'au moins une application logicielle
KR102071335B1 (ko) * 2015-06-11 2020-03-02 한국전자통신연구원 워크플로우 모델 생성 방법과 워크플로우 모델 실행 방법 및 장치
US10235191B2 (en) * 2015-12-14 2019-03-19 Sap Se Application specific configurable graphical user interface
US10789250B2 (en) 2016-09-15 2020-09-29 Oracle International Corporation Non-intrusive monitoring output of stages in micro-batch streaming
US10628424B2 (en) 2016-09-15 2020-04-21 Oracle International Corporation Graph generation for a distributed event processing system
WO2018169430A1 (fr) 2017-03-17 2018-09-20 Oracle International Corporation Logique d'intégration dans des systèmes de traitement d'événements sur la base de micro-lots
WO2018169429A1 (fr) 2017-03-17 2018-09-20 Oracle International Corporation Cadre pour le déploiement d'applications basées sur des événements
US10467335B2 (en) 2018-02-20 2019-11-05 Dropbox, Inc. Automated outline generation of captured meeting audio in a collaborative document context
US11488602B2 (en) 2018-02-20 2022-11-01 Dropbox, Inc. Meeting transcription using custom lexicons based on document history
CN109683853A (zh) * 2018-12-21 2019-04-26 云南电网有限责任公司电力科学研究院 一种基于建模的软件业务功能定义方法及系统
CN111694580B (zh) * 2019-03-13 2023-03-10 杭州宏杉科技股份有限公司 存储设备升级及初始化的方法、装置、电子设备
US11689379B2 (en) 2019-06-24 2023-06-27 Dropbox, Inc. Generating customized meeting insights based on user interactions and meeting media
JP6847382B1 (ja) * 2019-09-23 2021-03-24 株式会社デンソークリエイト 設計支援ツール
US20220394030A1 (en) * 2019-11-05 2022-12-08 Service Layers GmbH Method and System for Running an Identity and Access Management System
CN111459588A (zh) * 2020-03-27 2020-07-28 深圳融安网络科技有限公司 大数据模型设置方法、终端设备及计算机可读存储介质
US11307955B2 (en) * 2020-07-02 2022-04-19 Bank Of America Corporation Graphical user interface and analysis system for determining platform stability and resiliency
US11231913B1 (en) * 2020-07-23 2022-01-25 Tracelink, Inc. Model driven user interface

Family Cites Families (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPS57133362A (en) 1981-02-10 1982-08-18 Mitsubishi Electric Corp Frequency detector
GB9215320D0 (en) 1992-07-18 1992-09-02 Int Computers Ltd Configuration mechanism for a computer system
FR2694105B1 (fr) 1992-07-22 1994-11-25 Bull Sa Utilisation d'un langage à interprète embarqué pour la réalisation d'un outil interactif de définition d'interface utilisateurs.
DE10008632B4 (de) 2000-02-24 2004-02-26 Gunter Gemmel Verfahren und System zum Erzeugen eines Computerprogramms
US7181740B2 (en) * 2003-03-31 2007-02-20 Sony Corporation Method and system for automated provision of build images
US7694271B2 (en) 2004-02-26 2010-04-06 International Business Machines Corporation Rendering GUI widgets with generic look and feel
US8132148B2 (en) * 2005-04-29 2012-03-06 Microsoft Corporation XML application framework
DE102006038876A1 (de) 2006-08-18 2008-02-21 Giesecke & Devrient Gmbh Automatisches Erzeugen von lauffähigem Anwendungscode
US20080189679A1 (en) * 2007-02-05 2008-08-07 Jared Rodriguez Method and system for creating, deploying, and utilizing a service
US7934191B2 (en) * 2007-04-10 2011-04-26 Sap Portals IL Method and modules for generating client-server applications
US8418125B2 (en) 2007-05-03 2013-04-09 International Business Machines Corporation Incremental model refinement and transformation in generating commerce applications using a model driven architecture
US8255384B2 (en) * 2009-09-30 2012-08-28 Fujitsu Limited Client-tier validation of dynamic web applications
US8843884B1 (en) * 2009-11-23 2014-09-23 Jason Adam Koerner Interactive graphical construction of parametric components of typical cross section frameworks
US20110137872A1 (en) * 2009-12-04 2011-06-09 International Business Machines Corporation Model-driven data archival system having automated components
US20110145783A1 (en) * 2009-12-16 2011-06-16 Infosys Technologies Limited System and method for representing and validating functional requirements of a software system
US8417798B2 (en) * 2010-05-11 2013-04-09 International Business Machines Corporation Deploying artifacts for packaged software application in cloud computing environment
US8516364B2 (en) * 2010-08-30 2013-08-20 Sap Ag View model aspects of component objects
US8510373B2 (en) * 2010-08-30 2013-08-13 Sap Ag Data synchronization and disablement of dependent data fields
US8356282B1 (en) * 2011-09-13 2013-01-15 Advanced Testing Technologies, Inc. Integrated development environment for the development of electronic signal testing strategies
US8832662B2 (en) * 2012-05-08 2014-09-09 Siemens Aktiengesellschaft Rules engine for architectural governance
US8904357B2 (en) * 2012-05-08 2014-12-02 Siemens Aktiengesellschaft Dashboard for architectural governance
US9038017B2 (en) * 2012-08-23 2015-05-19 Cognizant Technology Solutions India Pvt. Ltd. Method and system for facilitating rapid development of end-to-end software applications
US9411845B2 (en) * 2013-06-13 2016-08-09 Sap Se Integration flow database runtime
WO2015044374A1 (fr) * 2013-09-27 2015-04-02 Petri Rudolf Markus Procédé et dispositif de génération et de production automatiques d'au moins une application logicielle
WO2017031459A1 (fr) * 2015-08-19 2017-02-23 Integrator Software Environnements de développement de logiciel intégrés, systèmes, procédés et modèles de mémoire
IN2015CH05184A (fr) * 2015-09-28 2015-10-16 Wipro Ltd

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
None *
See also references of WO2015044374A1 *

Also Published As

Publication number Publication date
US10296305B2 (en) 2019-05-21
WO2015044374A1 (fr) 2015-04-02
US20160239272A1 (en) 2016-08-18

Similar Documents

Publication Publication Date Title
WO2015044374A1 (fr) Procédé et dispositif de génération et de production automatiques d'au moins une application logicielle
DE10121790B4 (de) Softwarekonfigurationsverfahren zur Verwendung in einem Computersystem
DE10051645B4 (de) Prozesssteuersystem und Verfahren zum Kontrollieren eines Prozesses
DE60311805T2 (de) Erfassung, Zusammenstellung und/oder Visualisierung von strukturellen Merkmalen von Architekturen
DE60131683T2 (de) Verfahren und system zur verwaltung von mehreren netzwerk-betriebsmitteln
DE102007040823A1 (de) Editier- und Berichts-Tool für Grafische Programmiersprachenobjekte
EP1476829A2 (fr) Procede et systeme d'ingenierie destines a des systemes d'automatisation industriels
WO2015185328A1 (fr) Procédé informatisé et successions de signaux pour un programme de réutilisation de configurations logicielles exécutables pour systèmes logiciels ainsi que système informatique et programme informatique avec code programme pour mettre en œuvre le procédé
DE102006046310A1 (de) System zur Erzeugung und zum Betrieb einer Softwareapplikation für medizinische Bildgebung
DE10206903A1 (de) Softwareapplikation, Softwarearchitektur und Verfahren zur Erstellung von Softwareapplikationen, insbesondere für MES-Systeme
DE10244685A1 (de) Produktkonfigurationsverfahren und -system
DE102004043788A1 (de) Programm Generator
DE60019996T2 (de) System zum Koordinieren von Dokumenten und Aufgaben für einen Rechner
EP1202167B1 (fr) Méthode pour le développement orienté objet et basé sur un modèle d'interfaces externes pour des systèmes de logiciel distribués
DE10215653A1 (de) Verfahren und Anordung zur automatischen Erzeugung von Programmcodeabschnitten sowie ein entsprechendes Computerprogrammprodukt und ein entsprechendes computerlesbares Speichermedium
EP1387260A1 (fr) Procédé et dispositif pour la génération des logiciels
EP1490762B1 (fr) Procede, produit logiciel et systeme de traitement universel de l'information assiste par ordinateur
EP3355186A1 (fr) Génération et exécution de modules logiciels
EP1234231B1 (fr) Procede permettant de produire des interfaces utilisateur graphiques pour des programmes informatiques
DE10233971A1 (de) Verfahren und Vorrichtung zur Erzeugung von Software
WO2014131430A1 (fr) Procédé de développement logiciel de programmes basé sur des modèles avec accès à une banque de données
DE102013006949A1 (de) Verfahren zur Gewährleistung der Funktionsfähigkeit eines technischen Systems im Hinblick auf dessen Konfiguration im Rahmen einer Installation bzw. Beseitigung von Komponenten
EP1926019A1 (fr) Procédé d'échange de données et procédé de commande entre des composants logiciels et des composants logiciels réutilisables.
EP3940553A1 (fr) Procédé de fourniture de données critiques pour la sécurité au moyen d'un système serveur, système serveur et produit-programme informatique
DE102004051956A1 (de) Universalfenster (Window) für die Präsentation von in Dateien gespeicherten Inhalten

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20160412

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20170220

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

APBK Appeal reference recorded

Free format text: ORIGINAL CODE: EPIDOSNREFNE

APBN Date of receipt of notice of appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNNOA2E

APBR Date of receipt of statement of grounds of appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNNOA3E

APAF Appeal reference modified

Free format text: ORIGINAL CODE: EPIDOSCREFNE

REG Reference to a national code

Ref country code: DE

Ref legal event code: R003

APBT Appeal procedure closed

Free format text: ORIGINAL CODE: EPIDOSNNOA9E

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20221214