Disclosure of Invention
The invention aims to solve the technical problem of customizing enterprises according to the actual conditions and management requirements of enterprise customers. And providing a corresponding customized software product through professional software development.
To solve the above technical problems, the present invention provides a software customization method, comprising,
the application layer is used for modeling the customer requirements, and the modeling is set according to a model file corresponding to the suite;
the execution layer automatically loads the corresponding model file when a user performs business operation; interpreting the model file, and then converting the model file into a service instruction;
the realization layer finishes the business operation steps according to the business instruction after receiving the business instruction;
and the adaptation layer provides a human-computer interaction interface based on the requirements of customers.
Specifically, in the application layer, customer requirements are modeled, various business functions such as addition/deletion/modification/check/approval required by customers are subjected to model design, and various application kits (such as functions of logs, plans, tasks and the like) and kit sets (such as OA, CRM, ERP and the like) are combined; each suite corresponds to a group of model files, and after the models are set, dynamic value is carried out according to user requirements. And modeling, including information such as form fields, operation definitions, process definitions, form relations and the like. The field definition comprises field name, length, data type and other related parameters and application layer model instance introduction.
The layer of execution is such that,
when a system user performs business operation, automatically loading a corresponding model file, explaining the model and converting the model into business instructions (such as adding, deleting, modifying, inquiring, displaying, importing, exporting, printing, examining and approving);
if the working log is added, the user adds an adding button, the system automatically loads the model of the working log, and the fields (date, content and the like) which need to be displayed during adding are displayed on the system interface according to the instruction corresponding to the adding button in the model for the user to fill in the content; meanwhile, the next operation instruction is displayed, such as saving the log or submitting the log to a supervisor for review.
The layers are realized in such a way that,
after receiving the service instruction, the specific operation steps (such as data loading, authority verification, file downloading, etc.) are completed according to the instruction
After the user finishes filling in the work log, clicking a 'save' button, and automatically combining the platform into a background request instruction according to the form content:
after the background receives a front-end request instruction, identifying a calling model as a work log (work _ log) according to the closed parameter, and automatically reading required parameter contents such as date, log type and log content according to the work log model;
then, the background checks the legality of the log form data, and verifies the information such as the mandatory fields, the content format and the like;
and finally, combining the form data after passing the verification into a corresponding database SQL script by the background: (ii) a And returning the operation result to the user after the data storage is finished.
The adaptation layer is provided with a plurality of layers,
the man-machine delivery is completed, and a friendly man-machine interaction interface is provided;
the front end automatically generates a human-computer interaction interface according to the model, wherein the human-computer interaction interface comprises a form, a data sheet and various pages; the UI can match and adapt according to user rights/data state/front end type.
Still further, the model file includes, an application suite and a suite set,
the application suite is used for providing a first formulation component for a user;
the kit set is configured to provide a second user-customized component,
the second formulation component is used for user relationship management, and the first formulation component is used for user content management;
and performing instruction operation in relation management and content management through the first formulating component and/or the second formulating component.
Specifically, the application suite is as follows: logs, plans, tasks, and the like;
specifically, the kit set is: OA, CRM, ERP, etc.;
specifically, the model file is used for meeting the requirements of users for addition, deletion, modification, inquiry and approval.
Furthermore, when the first formulating component is arranged, a user loads the model of the first formulating component through a control key;
displaying fields needing to be displayed according to control key instructions in the model of the first formulated component;
providing a next operation instruction of the user;
or to complete the instruction operation.
Furthermore, the model file is used for adding, deleting, modifying, inquiring and approving the first formulated component by the user.
Further, the adaptation layer comprises a Web client, a Windows client, an iOS client and an Android client.
Furthermore, after the setting of the first formulating component is finished, a background request instruction is formed according to the form content in the first formulating component;
if a request instruction is received, identifying the type in the first formulation component according to the defined parameters;
reading required parameter content according to a model file corresponding to modeling;
performing rule verification on the form, and if the form passes the verification, combining the passed form data into a corresponding database SQL script;
and if the verification fails, reselecting the model file.
According to the above method, the present invention also provides a software customization system, comprising:
the rule modeler comprises a business rule template, relevant business objects and attribute parameters thereof, and is used for configuring a business rule model meeting requirements through a model file;
the rule translator is used for dynamically loading the corresponding model file; interpreting the model file, and then converting the model file into a service instruction;
the rule file library is used for completing the business operation steps according to the business instructions after receiving the business instructions;
the adapter is used for providing a human-computer interaction interface based on customer requirements.
Still further, the rule modeler comprises, a first formulation component and a second formulation component,
and performing instruction operation in the relation management and the content management in the rule modeler through the first formulation component and/or the second formulation component.
Furthermore, the rule translator is further used for forming a background request instruction according to the form content in the first formulation component after the first formulation component is set;
and, receiving the request instruction, identifying the type in the first formulated component according to the defined parameters;
reading required parameter content according to a model file corresponding to modeling;
and performing rule verification on the forms, and if the forms pass the verification, combining the passed form data into a corresponding database SQL file script.
Furthermore, the adapter is used for loading the data of the model file in the background or loading all the data in advance when the front end of the Web/iOS/Android needs to start a function instruction
The invention has the beneficial effects that:
1) according to the software customization method, due to the application layer, modeling is carried out on customer requirements, and the modeling is carried out according to a model file set corresponding to a suite; the execution layer automatically loads the corresponding model file when a user performs business operation; interpreting the model file, and then converting the model file into a service instruction; the realization layer finishes the business operation steps according to the business instruction after receiving the business instruction; and the adaptation layer provides a human-computer interaction interface based on the requirements of customers. The software code development workload can be reduced by more than 90%, the client function is mainly realized by modeling, and developers are not required to develop programs such as background/iOS/Android/Windows and the like.
2) Because in the execution layer, when the user carries out business operation, the corresponding model file is automatically loaded; and interpreting the model file and then converting the model file into a service instruction. The delivery cycle is shortened, the software coding/testing work which consumes the largest time in the development process is saved, and the software design, namely delivery, is realized; meanwhile, the research and development efficiency is improved, the seen and obtained field design delivery is realized through dynamic model loading, the communication efficiency is improved, and the rework cost is reduced.
3) The invention is based on the following steps: loading a model: when a front end of Web/iOS/Android/Windows and the like needs to start a certain function, loading model data from a background, or loading all the model data in advance; and (3) generating a UI: the front end automatically generates a human-computer interaction interface according to the model, wherein the human-computer interaction interface comprises a form, a data sheet and various pages; the UI can carry out matching and self-adaption according to user authority/data state/front end type; user interaction: the user finishes the operation on the interactive interface, and the front end automatically converts the operation into a service instruction; executing the instruction: the front end sends the service instruction to the background through the interface, the background finishes the explanation and processing of the instruction, including authority verification, operation validity verification and the like, and returns the operation result to the front end; the instruction may continue to wait for user interaction or end after completion. By modeling the user requirements and realizing functions through the models, the traditional Java/C + +/C/C # language programming is reduced or not used.
4) The software customization system in the invention comprises: the rule modeler comprises a business rule template, relevant business objects and attribute parameters thereof, and is used for configuring a business rule model meeting requirements through a model file; the rule translator is used for dynamically loading the corresponding model file; interpreting the model file, and then converting the model file into a service instruction; the rule file library is used for completing the business operation steps according to the business instructions after receiving the business instructions; the adapter is used for providing a human-computer interaction interface based on customer requirements. Through the software customization system, the model performs function realization, and the traditional programming of languages such as Java/C + +/C/C # and the like is reduced or not used.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to specific embodiments and the accompanying drawings.
Fig. 1 is a schematic operation flow diagram of a software customization method according to an embodiment of the present invention.
The software customization method in the embodiment comprises the following steps:
step 100, modeling the client requirements in an application layer, wherein the modeling is set according to a model file corresponding to a suite; customer requirements include, but are not limited to, business requirements, administrative requirements, internal requirements, outsourcing requirements, industry requirements, and the like. For example, the service requirement may include a mortgage service for real estate services, and the input, output and key fields are set according to the real estate services of the user in the application program, so as to automatically model. For another example, the management requirements may include approval, submission, and approval of the business process. For another example, the internal requirements may include attendance of employees, leave requests, late arrival, early departure, absenteeism, going out, matters, sick and the like. The industry requirements may include financial domain big data analysis, social domain push analysis, shipping analysis in the transportation domain, and the like. The setting of the external member corresponding to one model file means that each model file has a unique corresponding external member, and different model files are formed according to different external members. The kit can be an application requirement packaged according to a set rule and an interface or a set of multiple requirements.
Step 101, automatically loading the corresponding model file when a user performs business operation on an execution layer; interpreting the model file, and then converting the model file into a service instruction; because of the modeling in step 100, form fields, operation definitions, process definitions, form relationships, and other information are included. Therefore, in step 101, the corresponding model file can be automatically loaded according to the requirement of the current user.
The model file may be interpreted based on the following rules, such as:
when the external member is set as OA, corresponding model explanation is carried out according to the form field set by the user requirement
Table module "oa" key _ name "work _ log" table _ name "work log >
Further, the data types are: text, data length is: 30:
< fields > < field key _ name ═ log number "data _ type ═ text" length ═ 30"/>, and field _ name ═ log number" data _ type ═ text "length >
Further, date and non-empty fields are set
< field key _ name ═ work _ date ═ date [ # type [ ] [ "date" ] [ # null [ ] [/] [ ]
Further, the form fields: log type
The "log _ type" field _ name "log type" data _ type "select" select _ para "value" world logtype "notnull" true "app _ type" 2"search _ enable" true "list _ width" 10"/>
Further, the form fields: description of the work
The field key _ name ═ work _ description "field _ name ═ work description" data _ type ═ html "notnull ═ true" search _ enable ═ true "list _ width ═ true" 50"/>, and the method of the present invention
Further, the operations define: audit status
The "audit state" data _ type ═ select "select _ para ═ work _ state ═ depth ═ true" app _ type ═ 4"search _ enable ═ true" list _ width ═ 10 "edge _ state ═ 2"/>, and the like
Further, the process defines: audit status
The term "field key _ name", "create _ entry", "field _ name", "person filling", "data _ type", "entry", "user", "hidden", "true" readonly "," true "not null", "true" app _ type "," 3"search _ enable", "true" list _ width "," 10 "/>", is used to describe the name of the person filling the device, and the like
<states>
<state value＝"*">
Further, the process defines: adding, storing, submitting, deleting, auditing, agreeing, refusing:
the converting into the business instructions comprises: the front end sends the service instruction to the background through the interface, the background finishes the explanation and processing of the instruction, including authority verification, operation validity verification and the like, and returns the operation result to the front end.
Step 102, after the implementation layer receives the service instruction, completing the service operation step according to the service instruction; the implementation layer comprises operation instructions such as data transmission storage, data communication, operation authority, data transmission interfaces and the like, and simultaneously corresponds to different service instructions. For example, when adding the work log, the user adds an add button, the system automatically loads the model of the work log, and displays fields (date, content, and the like) to be displayed when adding on the system interface according to an instruction corresponding to the add button in the model, so that the user can fill in the content; meanwhile, the next operation instruction is displayed, such as saving the log or submitting the log to a supervisor for review. For another example, when a work task is submitted, the user adds an add button, the system automatically loads the model of the work task, and displays fields (date, content and the like) which need to be displayed when the add button is added on the system interface according to an instruction corresponding to the add button in the model, so that the user can fill in the content; meanwhile, next operation instructions, such as saving tasks or submitting tasks to a supervisor for review or flow, are displayed. For another example, when a plan is submitted, the user adds an adding button, the system automatically loads the plan model, and according to an instruction corresponding to the adding button in the model, the fields (date, content and the like) which need to be displayed when the adding button is added are displayed on the system interface for the user to fill in the content; meanwhile, next operation instructions, such as saving the plan or submitting the plan to a supervisor for review or flow, are displayed. Wherein the supervisor or the process is provided with different operation authorities.
In step 102, after receiving the service instruction, the implementation layer completes specific operation steps, specifically, data loading, permission verification, file downloading, and the like, according to the instruction.
After the user finishes filling in the work log, clicking a 'save' button, and automatically combining the platform into a background request instruction according to the form content:
do? op added word log date 2015-10-10 log type 1 remark, here the content of the work log
After the background receives the front-end request instruction, the calling model is identified as a work log (work _ log) according to the closed parameter, and required parameter contents such as date, log type and log content are automatically read according to the work log model;
then, the background checks the legality of the log form data, and verifies the information such as the mandatory fields, the content format and the like;
and finally, combining the form data after passing the verification into a corresponding database SQL script by the background: insert _ oa _ work _ log (work _ date, log _ type, remark, create _ entry, create _ time, status) values ('2015-10-10', '1', 'here the contents of the work log', '9309283', '2015-10-1015: 00: 00', '1'); and returning the operation result to the user after the data storage is finished.
And 103, providing a human-computer interaction interface based on the customer requirements at the adaptation layer. In the adaptation layer, UI display on different clients can be realized. The front end automatically generates a human-computer interaction interface according to the model, wherein the human-computer interaction interface comprises a form, a data sheet and various pages; the UI can match and adapt according to user rights/data state/front end type.
Fig. 2 is a schematic diagram of a composition structure of the application layer model file in fig. 1.
The software customization method in the embodiment comprises the following steps:
step 100, modeling the client requirements in an application layer, wherein the modeling is set according to a model file corresponding to a suite;
step 101, automatically loading the corresponding model file when a user performs business operation on an execution layer;
step 102, after the implementation layer receives the service instruction, completing the service operation step according to the service instruction;
and 103, providing a human-computer interaction interface based on the customer requirements at the adaptation layer. In the adaptation layer, UI display on different clients can be realized.
Preferably, in this embodiment, the model file 200 includes an application suite 201 and a suite set 202, the application suite is configured to provide a first customized component 2011 of the user, and the first customized component 2011 includes but is not limited to: logs, plans, and tasks; the kit is configured to provide a user with a second customization component 2021, such as: OA, CRM, ERP; the second formulation component 2021 is used for user relationship management, including but not limited to: OA, CRM, ERP, etc. corresponding to different user relation management according to different user requirements. The first enactment component 2011 is used for user content management, including but not limited to: log management, plan management, task management, process management and the like, wherein different user requirements correspond to different user management contents. The first formulation component 2011 and/or the second formulation component 2021 perform instruction operations in relation management and content management. Specifically, the model file is used for providing requirements for realizing addition, deletion, modification, inquiry and approval of users.
Fig. 3 is a flow diagram of a model file in the execution layer of fig. 1.
In the software customization method of the embodiment, the implementation steps of the model file in the execution layer are as follows:
step 300, when the first formulated component is set, a user loads a model of the first formulated component through a control key; the first formulated component corresponds to a unique model of the first formulated component, and the model is generated in an application layer according to the requirements of a user;
step 301, displaying fields to be displayed according to control key instructions in a first formulated component model; the control key instructions include but are not limited to: uploading, downloading, synchronizing and the like. Because the form field, the operation definition, the process definition, the form relation and other information are set in the application layer, the fields to be displayed, such as key fields, names, sizes, attributes and the like, are set by the loaded model in the execution layer.
Step 302, providing a next operation instruction of a user; the next operation instruction refers to a previous operation instruction, and the user sets according to different authorities, such as { individual, group, department }; for example { member, leader, supervisor }; such as operator, supervisor, and inspector.
Step 303 is to complete the instruction operation, that is, the user does not set the operation right, and the user operation can be completed only by submitting the instruction operation.
Fig. 4 is a schematic diagram of a specific structure of the adaptation layer in fig. 1.
In the software customization method in this embodiment, in the step 102 of the adaptation layer, a human-computer interaction interface based on customer requirements is provided in the adaptation layer, where the human-computer interaction interface includes: the system comprises a Web client, an ios client, an Android client and a windows client, wherein the Web client is a service for requesting and accessing through a URL (uniform resource locator) address; the ios client is a client using an apple operating system; the Android client is a client using an Android operating system, and multiple networks support: various types of access support clients such as CMNET, CMWAP, WiFi and the like; the windows client is a client using a Microsoft operating system.
Reference may be made to fig. 7(a) -7(c) which are diagrams illustrating an implementation effect of an adapter of a software customization system, where fig. 7(a) is a schematic diagram illustrating a Web client effect, fig. 7(b) is a schematic diagram illustrating an ios client effect, and fig. 7(c) is a schematic diagram illustrating an android client effect.
Fig. 5 is a flow chart illustrating the specific operations in the execution layer of fig. 1.
In the software customization method in this embodiment, in step 101, when a user performs a business operation, the corresponding model file is automatically loaded on an execution layer; interpreting the model file, and then converting the model file into a service instruction; specifically, the method further comprises the following steps:
step 500, after the setting of the first formulation component is completed, forming a background request instruction according to the form content in the first formulation component, for example, the form content in the first formulation component includes: header, fields contained, table attributes, etc.;
step 501, whether a request instruction is received or not is judged, and if not, the request instruction is returned to an application layer;
step 502, if a request instruction is received, identifying a type in a first formulated component according to a defined parameter, wherein an application suite in the first formulated component comprises: user content management such as logs, plans and tasks;
or,
if a request command is received, identifying the type in a second formulation component according to different defined parameters, wherein the kit set in the second formulation component comprises: OA, CRM, ERP and the like.
Step 503, reading the required parameter content according to the model file corresponding to modeling;
step 504 is to perform rule verification on the forms, and if the forms pass the rule verification, the forms passing the rule verification are combined into corresponding database SQL scripts.
Fig. 6 is a schematic structural diagram of a software customization system according to an embodiment of the present invention.
The software customization system in the present embodiment includes:
the rule modeler 600 includes a business rule template, related business objects and attribute parameters thereof, and is configured to configure a business rule model meeting requirements through a model file;
a rule translator 601 for dynamically loading the corresponding model file; interpreting the model file, and then converting the model file into a service instruction;
the rule file library 602 completes the business operation steps according to the business instructions after receiving the business instructions;
the adapter 603 is used for providing a human-computer interaction interface based on the requirements of customers.
The rule modeler 600 includes a business rule template, related business objects and attribute parameters thereof, and is configured to configure a business rule model meeting requirements through a model file;
modeling the customer requirements, performing model design on various business functions such as addition/deletion/modification/check/approval and the like required by customers, and combining the business functions into various application kits (such as functions of logs, plans, tasks and the like) and kit sets (OA, CRM and ERP); each suite corresponds to a group of model files, and after the models are set, dynamic value is carried out according to user requirements.
The modeling process of the rule modeler 600 includes information such as form fields, operation definitions, process definitions, and form relationships. The field definition comprises field names, lengths, data types and other related parameters, and the application layer model instance introduction comprises the following steps:
the rule translator 601 is used for dynamically loading the corresponding model file; interpreting the model file, and then converting the model file into a service instruction;
when a system user performs business operation, automatically loading a corresponding model file, explaining the model and converting the model into a business instruction (such as adding, deleting, modifying, inquiring, displaying and the like);
for example, when adding a work log in the rule translator 601, the user adds an add button, the system automatically loads the model of the work log, and according to an instruction corresponding to the add button in the model, the fields (date, content, and the like) to be displayed when adding are displayed on the system interface for the user to fill in the content; meanwhile, the next operation instruction is displayed, such as saving the log or submitting the log to a supervisor for review.
The rule file library 602 completes the business operation steps according to the business instructions after receiving the business instructions;
after receiving the service command in the rule document library 602, the specific operation steps (such as data loading, authority verification, document downloading, etc.) are completed according to the command
After the user finishes filling in the work log, clicking a 'save' button, and automatically combining the platform into a background request instruction according to the form content:
do? op added word log date 2015-10-10 log type 1 remark, here the content of the work log
After the background receives a front-end request instruction, identifying a calling model as a work log (work _ log) according to the closed parameter, and automatically reading required parameter contents such as date, log type and log content according to the work log model;
then, the background checks the legality of the log form data, and verifies the information such as the mandatory fields, the content format and the like;
and finally, combining the form data after passing the verification into a corresponding database SQL script by the background: insert _ oa _ work _ log (work _ date, log _ type, remark, create _ entry, create _ time, status) values ('2015-10-10', '1', 'here the contents of the work log', '9309283', '2015-10-1015: 00: 00', '1'); and returning the operation result to the user after the data storage is finished.
The adapter 603 is used for providing a human-computer interaction interface based on the requirements of customers. Human-computer delivery is completed in the adapter 603, and a friendly human-computer interaction interface is provided; the front end automatically generates a human-computer interaction interface according to the model, wherein the human-computer interaction interface comprises a form, a data sheet and various pages; the UI can match and adapt according to user rights/data state/front end type.
Preferably, the rule modeler 601 comprises, a first formulation component and a second formulation component,
in the rule modeler 601, the first formulation component and/or the second formulation component perform instruction operations in relation management and content management.
Preferably, after the first formulation component is set, the rule translator 601 is further configured to compose a background request instruction according to the form content in the first formulation component;
and, receiving the request instruction, identifying the type in the first formulated component according to the defined parameters;
reading required parameter content according to a model file corresponding to modeling;
and performing rule verification on the forms, and if the forms pass the verification, combining the passed form data into a corresponding database SQL file script.
Preferably, the adapter 603 is configured to load data of the model file in a background or load all data in advance when the front end of the Web, the iOS, the Android, and the windows needs to start a function instruction.
Those of ordinary skill in the art will understand that: the present invention is not limited to the above embodiments, and any modifications, equivalent substitutions, improvements, etc. within the spirit and principle of the present invention should be included in the protection scope of the present invention.