CN107247581B - Method for constructing system analysis and summary design delivery model - Google Patents
Method for constructing system analysis and summary design delivery model Download PDFInfo
- Publication number
- CN107247581B CN107247581B CN201710134078.6A CN201710134078A CN107247581B CN 107247581 B CN107247581 B CN 107247581B CN 201710134078 A CN201710134078 A CN 201710134078A CN 107247581 B CN107247581 B CN 107247581B
- Authority
- CN
- China
- Prior art keywords
- model
- data
- design
- application
- analysis
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/10—Requirements analysis; Specification techniques
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The embodiment of the application relates to a method for constructing a system analysis and summary design delivery model, which comprises the following steps: parsing the document into a list of graphs and objects, each object containing an association table of elements with the object; constructing a definition set, an attribute set, an association set and an image set to carry out a list and an object of the image; and establishing the association between the graph set and the definition set through an attribute set, carrying the content of the graph in the document, establishing the association between the content of the graph and the definition set through a connector, and constructing a meta model of a delivery model.
Description
Technical Field
The invention relates to the technical field of data modeling, in particular to a method for constructing a system analysis and summary design delivery model.
Background
In the whole life cycle of the software project, the system analysis and summary design process meets business requirements and guides coding and testing backwards, which is a key ring of the IT project implementation process, and the efficiency of the system analysis and summary design and the quality of the result directly influence the progress of the IT project and the quality of software delivery. The system analysis and design process with documentation as the primary delivery cannot ensure that the standard analysis and design process is performed correctly in all IT projects; a large amount of repeated contents are often written in a design document, the design efficiency is low, and the problem of inconsistent data is easily caused; the clear design requirements and constraints cannot be solidified in the design result, and the quality is not guaranteed; the formation of uniform design asset specifications is difficult, and the long-term accumulation, sharing and reuse of design results are not facilitated; while the examination of the design results usually only adopts manual document examination, the examination efficiency is low, and the design efficiency and quality of large IT research and development enterprises are seriously influenced by the traditional system analysis and summary design mode which takes unstructured documents as main deliveries.
Disclosure of Invention
The embodiment of the invention provides a method for constructing a system analysis and summary design delivery model, which can quickly check the format and information of a document and ensure the consistency and accuracy of the document.
In one aspect, an embodiment of the present application provides a method for building a system analysis and summary design delivery model, where the method includes: parsing the document into a list of graphs and objects, each object containing an association table of elements with the object; constructing a definition set, an attribute set, an association set and an image set to carry out a list and an object of the image; and establishing the association between the graph set and the definition set through an attribute set, carrying the content of the graph in the document, establishing the association between the content of the graph and the definition set through a connector, and constructing a meta model of a delivery model.
Optionally, the definition set carries all objects of the document, the attribute set carries the elements included in the objects, the association set carries associations between all objects and elements, and the graph set carries graphs in the document.
Optionally, the method further comprises: and defining a script according to the type and the type of the data extracted from the meta-model, checking the extracted data, generating a statistics and checking report of the document and a delivery document for generating the delivery model, and when the information of the attribute or the element in one piece of data is checked to be wrong, generating prompting information of the information error of the attribute or the element in the delivery model. .
Optionally, the association between the graph set and the definition set is established through the attribute set, and the content of the graph in the document is carried, the association between the content of the graph and the definition set is established through a connector, and a meta model is dispatched to generate the delivery model, where the delivery model includes: the system comprises an application analysis model, an overall scheme model, an application design model, an application component design model, a data component design model, an application integration model and a data integration model.
Optionally, the delivery model is guided to perform supporting interaction and communication between the business architecture model and the IT architecture model by uniformly defining grammatical and semantic features of the elements and the definition set of the elements in the delivery model and establishing an association relationship for the elements of other models.
Optionally, the analysis result definition set is used for bearing and displaying service requirements of information system construction projects.
Optionally, the overall scheme model is used for carrying the content of system architecture design, including context, application architecture, data architecture, technology architecture, security architecture, and typical transaction line content.
Optionally, the application design model is used for bearing and displaying an application design result of an information system, and mainly includes: the system uses cases, interfaces, channels, reports, certificates, events and transaction service contents.
Optionally, the application component design model is used for bearing and displaying a service design result, and mainly includes: online services, batch services, etc.
Optionally, the data component design model is used for bearing and displaying a data object and a data object service design result, and mainly includes: logical data model, data object service content.
Optionally, the application integration model is used for bearing and displaying design results of integration and data transmission with other systems.
Optionally, the data integration model is used for carrying and presenting the result of the data integration service design.
Optionally, the method further comprises: the application analysis model comprises an association set consisting of user workflow, service function, function difference analysis, implementation effect analysis, data application demand analysis, user experience demand analysis, service migration scheme analysis, data migration range analysis, product model matching analysis and service event trigger scene analysis design elements; the overall scheme model comprises a context relationship diagram, an application architecture diagram, a data architecture diagram, a typical transaction line scene diagram, a technical architecture definition, a safety architecture definition, an operation and maintenance monitoring definition, a non-function definition and an association set consisting of application migration strategy design elements; the application design model is as follows: the system comprises an association set consisting of a system case global graph, a system case, a menu definition, a typical operation scene, a non-functional test evaluation and a system workflow design element; the application component design model comprises an online transaction online service, an online analysis online service, an associated component online service, a product assembly model, a typical operation scene, a non-functional test evaluation and a batch processing job design element to form an associated set; the data component design model comprises a logic data model, a data list, a data requirement specification, a data entity index, a parameter entity definition table, a data object service and a data component service design element to form an association set; the application integration model comprises an association set formed by design elements of an application integration function and a data transmission function; the data integration model comprises an association set consisting of design elements of data packaging service, data integration analysis report, data requirement verification report, data exchange interface design, data quality check rule and data archiving strategy.
The method for constructing the system analysis and summary design delivery model provided by the embodiment of the invention can quickly check the format and information of the document and ensure the consistency and accuracy of the document.
Drawings
FIG. 1 is a schematic diagram of a method for constructing a system analysis and summary design delivery model according to an embodiment of the present invention;
FIG. 2 is a meta-model diagram of a delivery model provided by an embodiment of the invention;
FIG. 3 is a schematic diagram of data transmission of a delivery model according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of an application analysis model provided by an embodiment of the present invention;
FIG. 5 is a schematic diagram of an overall scheme model provided by an embodiment of the present invention;
FIG. 6 is a schematic diagram of an application design model provided in an embodiment of the present invention;
FIG. 7 is a schematic diagram of an application component design model according to an embodiment of the present invention;
FIG. 8 is a schematic diagram of a data component design model provided by an embodiment of the present invention;
FIG. 9 is a schematic diagram of an application integration model according to an embodiment of the present invention;
FIG. 10 is a schematic diagram of a data integration model provided by an embodiment of the present invention;
fig. 11 is a schematic view of a working view provided by an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In order to make the objects, technical solutions and advantages of the present invention clearer, the following detailed description of specific embodiments of the present invention is provided with reference to the accompanying drawings, and the embodiments are not limited to the embodiments of the present invention.
The method for constructing a system analysis and summary design delivery model according to the embodiment of the present application is suitable for a server for constructing a delivery model for processing document data, but is not limited thereto.
For a better understanding of the advantages of the present application, reference should be made to the embodiments illustrated in the drawings and described in detail below.
FIG. 1 shows a schematic diagram of a system analysis and summary design delivery model building method. The method comprises the following steps:
Specifically, the document is parsed into a plurality of graphs and objects, the plurality of graphs exist in a list form, and each object further comprises an association table, and the association table is the association between the object and the elements.
And 102, constructing a definition set, an attribute set, an association set and an image set to carry a list and an object of the image.
Specifically, the definition set carries all objects of the document, the attribute set carries the elements included in the objects, the association set carries associations between all the objects and the elements, and the graph set carries graphs in the document.
Specifically, as shown in the meta-model diagram of the delivery model shown in fig. 2, the delivery model is developed and designed with the project as the dimension, and the delivery model of one project is stored under one project definition, and four sets are generated according to the system analysis and the construction method of the schematic design delivery model: definition set, attribute set, association set and graph set. Wherein the item definition comprises: and the project information, the application analysis model and the subsystem list contained in the project are the list and the object of the graph generated after the document is analyzed. The project information mainly includes: the business and technical goals of the project, the list of applications and the list of application components to be implemented by the project (i.e., the implementation scope of the project, which may be inherited from the business architecture model), and the implementation policies of the project. The application analysis model mainly comprises the following steps: the user workflow definition set and the service function definition set to be implemented by the project are used for bearing and displaying the analysis result definition set of the information system construction project service requirement. Each subsystem definition comprises an overall scheme model, an application integration model, a data integration model and a sub-item list contained in the subsystem, and each sub-item definition set corresponds to one application design model, one application component design model or one data component design model. The overall scheme model comprises: the system comprises a context relationship diagram, an application architecture diagram, a data architecture diagram, a technical architecture definition set, a safety architecture definition set, a typical transaction line definition set, a non-functional design definition set, an operation and maintenance monitoring design definition set and the like of the subsystem. The application integration model comprises: an application integration function definition set and a data transfer function definition set. The data integration model comprises: a set of data integration design definitions. The application design model mainly comprises: a system use case definition set, a system workflow definition set and a menu design definition set. The application component design model mainly comprises: a set of online service definitions and a set of batch service definitions. The data component design model mainly comprises: a data object, a set of data object service definitions, and an entity relationship graph (ER graph) for the data component.
The objects carried in the definition set, for example, attributes contained in the application analysis model constitute the attribute set, wherein the described entity relationships and the like constitute an association set, and the graphs contained in the list involved in the item constitute the graph set.
The system provided by the embodiment of the application analyzes and outlines the schematic diagram of the delivery model, which is used for accepting the business architecture model and the enterprise IT architecture model and transferring the data flow in the delivery model. The main implementation way for ensuring correct data transmission is to establish a relationship for two related elements in the meta model, i.e. to construct an association set. Establishing a one-to-many relationship between the three-level activities and the user workflows, enabling one or more user workflows in the application analysis model to bear one three-level activity of the business architecture model, enabling one or more business functions to bear four-level tasks, and completely inheriting standard data in the business architecture models of customers, products, channels and the like; the overall scheme model is developed and designed by taking subsystems defined in the enterprise IT architecture model as dimensions, the content of the overall scheme model of each subsystem is a subset of the enterprise IT architecture model, and the content is the decomposition, refinement and landing of the related content of the subsystem in the enterprise IT architecture model in the process of system analysis and summary design. For example: the application architecture diagram in the subsystem is a subset of an enterprise-level IT architecture model application architecture, and high-level design of the application architecture diagram is already completed in the enterprise-level application architecture, and further decomposition and refinement are needed in the overall scheme model. And in the same way, the data is orderly transmitted in the system analysis guide outline design delivery model. One or more system workflows associated with a user workflow, a system workflow comprising one or more workflow nodes, each workflow node driving a flow orchestration service; one or more system use cases are associated with a business function, the system use cases comprise one or more transaction services, one transaction service calls an online service, one online service comprises a plurality of processing logics and rules, and one processing logic and rule calls a construction service or a data object service.
And 103, establishing the association between the graph set and the definition set through an attribute set, carrying the content of the graph in the document, establishing the association between the content of the graph and the definition set through a connector, and constructing a meta model of a delivery model.
Establishing the association between the graph set and the definition set through the attribute set, carrying the content of the graph in the document, establishing the association between the content of the graph and the definition set through a connector, and dispatching a meta-model to generate the delivery model, wherein referring to fig. 3, the delivery model comprises: the system comprises an application analysis model, an integral scheme model, an application design model, an application component design model, a data component design model, an application integration model and a data integration model.
The application analysis model is the result of the application analysis process in the system analysis and summary design, and the main purpose of the application analysis model is to form and clarify the scope of the project, the business function requirement list and definition of the project to be realized and the business effect which can be achieved by implementation. As shown in fig. 4, the application analysis model is developed and designed with the project as a dimension, and the model is composed of design elements such as a user workflow, a service function, a function difference analysis, an implementation effect analysis, a data application demand analysis, a user experience demand analysis, a service migration scheme analysis, a data migration range analysis, a product model matching analysis, a service event trigger scenario analysis, and the like. And giving the association relation among the design elements by using a connector mode and taking an arrow line as an example to form an association set, namely establishing the association of the definition set by the content of the graph through the connector. One or more user workflows carry out a three-level activity (business modeling result is a unified flow after removing differentiating factors such as customers, products, channels and the like), one user workflow comprises one or more flow scenes, exception handling, a group of user interface prototypes, a user workflow diagram matched with the user workflow diagram and a plurality of user workflow nodes, and each user workflow node is associated with a business function. One or more business functions support a four-level task (business modeling result), and one business function comprises a business function description, one or more business operation steps and error processing, and comprises definitions of all interface elements on an interface corresponding to the function. One or more implementation effect definitions to present the effect that a business objective achieves after the project is implemented. And one function difference analysis definition is associated with one service function and used for storing the function difference analysis result and recording the specific implementation mode of the service function. In addition to the above structured content, applying the analytical model further comprises: the method comprises the following steps of analyzing data application requirements, analyzing user experience requirements, analyzing a service migration scheme, analyzing a data migration range, analyzing product model matching, analyzing a service event trigger scene and the like, wherein the contents exist in an attachment form.
The overall scheme model is the result of the overall scheme design process in the system analysis and summary design. The overall scheme design is the overall architecture design of a project, and the architecture solution is mainly refined according to the project function requirement range, the non-functional technical index requirement and the result of the early-stage architecture analysis. As shown in fig. 5, the overall solution model is developed and designed by taking a subsystem as a dimension, and is composed of a context diagram, an application architecture diagram, a data architecture diagram, a typical transaction line scene diagram, a technical architecture definition, a security architecture definition, an operation and maintenance monitoring definition, a non-functional definition, an application migration policy and other design elements. The context graph describes the association set of the system and the peripheral subsystems; the application architecture diagram describes the functional distribution of the subsystem, and is a subset of the enterprise-level IT application architecture; the data architecture diagram describes the data entity distribution and data access path of the subsystem, and a subset of an enterprise-level IT data architecture; the technical architecture definition describes an overall deployment scheme of the subsystem, which is a subset of an enterprise-level IT technical architecture, the safety architecture definition describes a safety scheme of the subsystem, defines a calling relationship between the subsystem and the safety subsystem, and is a subset of the enterprise-level IT safety architecture; the exemplary transaction line scenario diagram describes the system implementation of an exemplary transaction contained in the subsystem.
The application design model is the result of the application design process in the system analysis and summary design. The application design mainly comprises the steps of determining system workflows for realizing user workflows, analyzing service function definitions in application analysis one by one, and determining system cases from the aspects of user permission responsibility division, interface user experience requirements, function channel deployment requirements, technical realization constraints and the like. As shown in fig. 6, the application design model is developed and designed with sub-items as dimensions, and is used for bearing and displaying the application design result of the information system, and the model mainly includes design elements such as a system use case global diagram, a system use case, a menu definition, a typical operation scene, a non-functional test evaluation, and a system workflow. The application design model comprises one or more system use case global graphs, and one system use case global graph corresponds to one three-level activity and is used for displaying all use case operations belonging to the three-level activity; one or more system use cases are accepted and realize a business function, one system use case definition corresponds to a use case general flow chart, the system use case definition comprises use case description, all interfaces, reports, certificates, called external channels, events, transaction services, local components and application batch processing, the interfaces comprise interface navigation and interface elements, the events comprise interface events, incoming events and automatic triggering events, one interface triggers one or more interface events, one external channel triggers one external incoming event, the transaction services comprise transaction description, transaction service interfaces and transaction service call flows, and the transaction services can call online services, original system services, external system services or local component services through the transaction service call flows. One or more system workflows are carried and a user workflow is realized, one system workflow corresponds to one system workflow diagram, the system workflow is composed of system workflow description and system workflow nodes, one system workflow node is associated with one system case, and one system workflow node drives one process arrangement service. Typical operating scenarios, non-functional test evaluations, etc. are embedded in the application design model in the form of attachments.
The application component design model is the result of the application component design process in the system analysis and summary design. The application component design mainly comprises an online service design and a batch processing job design. As shown in fig. 7, the application component design model is developed and designed with sub-items as dimensions, and the model mainly includes design elements such as online transaction (OLTP), online analysis (OLAP), associated component, product assembly model, typical operating scenario, non-functional test evaluation, and batch processing job. An online service can be called by a plurality of transaction services, an OLTP online service corresponds to an online service processing flow chart, the OLTP online service is composed of an online service description, an online service interface, error output information, a service dependency relationship chart, a service combination calling relationship chart and service processing logic and rules, and the service processing logic and rules are associated with a five-level step in a business architecture model; the batch job is composed of a batch job description, a job flowchart, error output information, and a batch service. Design contents such as related component online service, product assembly model, typical operation scene, non-functional test evaluation and the like are embedded in the application component design model in an accessory mode.
The data component design model is the result of the data component design process in the system analysis and summary design. Data component design mainly defines the contents incorporated in data objects, defines the business processing operations of Data Object Services (DOS), and defines data object services according to architectural design constraints. As shown in fig. 8, the data component design model is developed and designed with sub-items as dimensions, and the model mainly includes design elements such as a logical data model (ER diagram), a data list, a data requirement specification, a data entity index, a parameter entity definition table, a data object service, and a data component service. A data object corresponds to a data entity in the logic data model, one data object can contain one or more data object services, the data object services encapsulate the operations of adding, deleting, changing and searching the database, and the data object services are composed of data object service description and service interfaces, and the online service in the application component design model calls the data object services through service processing logic and rules to realize the read-write operation of the application system on data. Design contents such as a data list, a data requirement specification, a data entity index, a parameter entity definition table and the like are embedded in the data component design model in an attachment mode.
The application integration model is the result of the application integration design process in the system analysis and summary design. The application integration design mainly defines application integration functions and data transmission functions. The application integration function mainly refers to the application integration function of the subsystem and an internal system and an external system; the data transmission function mainly refers to the data transmission function between the subsystem and the internal and external systems. As shown in fig. 9, the application integration model is developed by taking the subsystem as a dimension, and the model mainly comprises an application integration function and a data transmission function. The application integration function is divided into an external connection integration service and an internal connection integration service, the external connection integration service is composed of a service description, an external connection adapter and an interface, and the internal connection integration service is composed of a service description integration processing logic and an interface; the data transmission function is composed of function description, transmission content list, transmission processing logic, transmission interface and data transmission path diagram.
The data integration model is the result of the data integration design process in the system analysis and summary design. The data integration design mainly comprises data model design of a data integration layer, an entity list, storage areas for identifying different data and a data integration management function. As shown in fig. 10, the data integration model is developed and designed by taking a subsystem as a dimension, and the model mainly comprises design elements of data encapsulation service, a data integration analysis report, a data requirement verification report, data exchange interface design, a data quality check rule, and a data archiving policy, and is embedded in the data integration model in an attachment form.
The above-described elements are only a part of the elements of the embodiments of the present application, and not all of the design elements.
Optionally, the delivery model, the business architecture model and the IT architecture model are subjected to adapting interaction and communication by unifying grammatical and semantic features defining the elements in the delivery model and defined attributes of the elements, and establishing an association relationship for elements of other models.
Specifically, by uniformly defining grammatical and semantic features of the elements and the attributes in the plurality of integration models and establishing association relations for related model elements, carrying out accepting interaction and communication between the system analysis and summary design delivery model and the business architecture model (if existing) and the enterprise IT architecture model (if existing) and realizing ordered delivery of design elements in the system analysis and summary design delivery model. Developers or users of the IT architecture model may define syntactic and semantic features for other models using the same elements or attributes, thereby defining the same functions and operations for other models.
Optionally, the model further comprises: according to a design working view defined by a standard design process, the standard design process is solidified, association is established between each design process and the model design content to be completed by the process, the view provides a convenient design entry for a user, and the user can conveniently design and browse the design result.
Specifically, fig. 11 is a schematic diagram of a design working view provided in the embodiment of the present application. The working view shows the stages contained in a project, the analysis or design process contained in each stage, the process contained in each design process, and the model design content to be completed by the process under each process. As shown in fig. 11, the application analysis process of a project includes 9 processes of function difference analysis, CPC reduction analysis (CPC is an abbreviation of a client, a product, and a channel), interface requirement analysis, business practice scenario analysis, product model matching analysis, data analysis, business function docking analysis, user experience feedback analysis, and effect implementation analysis, where the process CPC reduction analysis is developed, and it can be seen that three definitions of a project, a user workflow, and a business function, and a user workflow diagram are listed under the process, which indicates that the process needs to complete corresponding analysis content in the three definitions, and complete drawing of the user workflow diagram.
Optionally, data is extracted from the meta-model according to the type and type definition script of the data extracted from the meta-model; checking the extracted data, generating a statistics and checking report of the document, and delivering the document; and when the information error of the attribute or the element in the data is checked, generating the prompt information of the information error of the attribute or the element in the delivery model.
The method and the server for constructing the system analysis and summary design delivery model can quickly check the format and information errors of the document, can automatically mark the same errors which occur again for the errors marked in the document, and ensure the consistency and the accuracy of the standard document.
Those of skill would further appreciate that the various illustrative components and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present embodiments.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied in hardware, a software module executed by a processor, or a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The foregoing detailed description is provided to illustrate, explain and enable the best mode of the invention, and it should be understood that the above description is only exemplary of the invention, and is not intended to limit the scope of the invention, which is defined by the following claims.
Claims (7)
1. A method for constructing a system analysis and summary design delivery model, the method comprising:
parsing the document into a list of graphs and objects, each object containing an association table of elements with the object;
constructing a definition set, an attribute set, an association set and an image set to carry out a list and an object of the image;
the definition set bears all objects of the document, the attribute set bears the elements contained in the objects, the association set bears the association relation between all the objects and the elements, and the atlas bears all the graphs in the document;
establishing the association between the graph set and the definition set through the attribute set so as to bear the content of the graph in the document, establishing the association between the content of the graph and the definition set through a connector, and constructing a meta model of a delivery model;
a display error flag synchronized with an object associated with the element when a format and information error of the element is checked, and a display error flag synchronized with an element associated with the object when a format and information error of the object is checked.
2. The method according to claim 1, wherein the definition set carries all objects of the document, the property set carries the elements contained in the objects, the association set carries associations of all objects and elements, and the graph set carries graphs in the document.
3. The method of claim 1, further comprising:
defining scripts according to the types and types of the data extracted from the meta-model, and extracting the data from the meta-model;
checking the extracted data, generating a statistics and checking report of the document, and delivering the document;
and when the information error of the attribute or the element in the data is checked, generating the prompt information of the information error of the attribute or the element in the delivery model.
4. The method of claim 1, wherein the graph set is associated with the definition set through the attribute set, and carries content of the graph in the document, and the graph content is associated with the definition set through a connector, and a meta-model is dispatched to generate the delivery model, wherein the delivery model comprises: the system comprises an application analysis model, an overall scheme model, an application design model, an application component design model, a data component design model, an application integration model and a data integration model;
the application analysis model is used for bearing and displaying an analysis result definition set of the service requirements of the information system construction project;
the integral scheme model is used for bearing the content of system architecture design, and comprises context, application architecture, data architecture, technical architecture, safety architecture and typical transaction line content;
the application design model is used for bearing and displaying application design results of an information system, and mainly comprises the following components: system use case, interface, channel, report, certificate, event and transaction service content;
the application component design model is used for bearing and displaying a service design result and mainly comprises the following steps: online services, batch services, etc.;
the data component design model is used for bearing and displaying data objects and data object service design results, and mainly comprises the following components: a logical data model, a data object service content;
the application integration model is used for bearing and displaying a design result integrated with other systems and transmitted by data;
the data integration model is used for bearing and displaying the result of the data integration service design.
5. The method of claim 1, wherein the delivery model is interfaced and communicated with a business architecture model and an IT architecture model by unifying syntactic and semantic features defining the elements and a defined set of the elements in the delivery model and establishing associations for elements of other models.
6. The method of claim 4, further comprising:
the application analysis model comprises an association set consisting of user workflow, service function, function difference analysis, implementation effect analysis, data application demand analysis, user experience demand analysis, service migration scheme analysis, data migration range analysis, product model matching analysis and service event trigger scene analysis design elements;
the overall scheme model comprises a context relationship diagram, an application architecture diagram, a data architecture diagram, a typical transaction line scene diagram, a technical architecture definition, a safety architecture definition, an operation and maintenance monitoring definition, a non-function definition and an association set consisting of application migration strategy design elements;
the application design model is as follows: the system comprises an association set consisting of a system case global graph, a system case, a menu definition, a typical operation scene, a non-functional test evaluation and a system workflow design element;
the application component design model comprises an online transaction online service, an online analysis online service, an associated component online service, a product assembly model, a typical operation scene, a non-functional test evaluation and a batch processing job design element to form an associated set;
the data component design model comprises a logic data model, a data list, a data requirement specification, a data entity index, a parameter entity definition table, a data object service and a data component service design element to form an association set;
the application integration model comprises an association set formed by design elements of an application integration function and a data transmission function;
the data integration model comprises an association set consisting of design elements of data packaging service, data integration analysis report, data requirement verification report, data exchange interface design, data quality check rule and data archiving strategy.
7. A model server, the model server comprising: a processor; a memory; an application program physically stored in the memory, the application program comprising instructions operable to cause the processor to:
parsing the document into a list of graphs and objects, each object containing an association table of elements with the object;
constructing a definition set, an attribute set, an association set and an image set to carry out a list and an object of the image;
the definition set bears all objects of the document, the attribute set bears the elements contained in the objects, the association set bears the association relation between all the objects and the elements, and the atlas bears all the graphs in the document;
establishing the association between the graph set and the definition set through the attribute set so as to bear the content of the graph in the document, establishing the association between the content of the graph and the definition set through a connector, and constructing a meta model of a delivery model;
a display error flag synchronized with an object associated with the element when a format and information error of the element is checked, and a display error flag synchronized with an element associated with the object when a format and information error of the object is checked.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710134078.6A CN107247581B (en) | 2017-03-07 | 2017-03-07 | Method for constructing system analysis and summary design delivery model |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710134078.6A CN107247581B (en) | 2017-03-07 | 2017-03-07 | Method for constructing system analysis and summary design delivery model |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107247581A CN107247581A (en) | 2017-10-13 |
| CN107247581B true CN107247581B (en) | 2020-08-14 |
Family
ID=60016471
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710134078.6A Active CN107247581B (en) | 2017-03-07 | 2017-03-07 | Method for constructing system analysis and summary design delivery model |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107247581B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110333906B (en) * | 2019-05-16 | 2023-06-16 | 广州明珞装备股份有限公司 | Method, system, device and storage medium for rapidly processing reserved equipment |
| CN111062600B (en) * | 2019-12-06 | 2022-06-14 | 中国工商银行股份有限公司 | Model evaluation method, system, electronic device, and computer-readable storage medium |
| CN115203311B (en) * | 2022-07-05 | 2023-05-02 | 南京云创大数据科技股份有限公司 | Industry data analysis mining method and system based on data brain |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101452550A (en) * | 2008-11-19 | 2009-06-10 | 中国网络通信集团公司 | Requirement information processing method for system |
| CN102495832A (en) * | 2011-12-12 | 2012-06-13 | 方正国际软件有限公司 | System for automatically generating document in software development process |
| CN102508645A (en) * | 2011-09-23 | 2012-06-20 | 武汉大学 | Behavior-oriented software requirement model visualizing method |
| CN104077137A (en) * | 2008-10-08 | 2014-10-01 | 埃森哲环球服务有限公司 | Integrated design application |
| CN105389407A (en) * | 2014-08-21 | 2016-03-09 | 波音公司 | integrated visualization and analysis of a complex system |
| CN105528418A (en) * | 2015-12-04 | 2016-04-27 | 东软集团股份有限公司 | Design document generation method and apparatus |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130097583A1 (en) * | 2011-09-27 | 2013-04-18 | The University Of Texas System | Systems and Methods For Automating the Application of a Software Methodology |
| US10303441B2 (en) * | 2015-04-28 | 2019-05-28 | Nadia Analía Huebra | Process and system for automatic generation of functional architecture documents and software design and analysis specification documents from natural language |
-
2017
- 2017-03-07 CN CN201710134078.6A patent/CN107247581B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104077137A (en) * | 2008-10-08 | 2014-10-01 | 埃森哲环球服务有限公司 | Integrated design application |
| CN101452550A (en) * | 2008-11-19 | 2009-06-10 | 中国网络通信集团公司 | Requirement information processing method for system |
| CN102508645A (en) * | 2011-09-23 | 2012-06-20 | 武汉大学 | Behavior-oriented software requirement model visualizing method |
| CN102495832A (en) * | 2011-12-12 | 2012-06-13 | 方正国际软件有限公司 | System for automatically generating document in software development process |
| CN105389407A (en) * | 2014-08-21 | 2016-03-09 | 波音公司 | integrated visualization and analysis of a complex system |
| CN105528418A (en) * | 2015-12-04 | 2016-04-27 | 东软集团股份有限公司 | Design document generation method and apparatus |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107247581A (en) | 2017-10-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8555248B2 (en) | Business object change management using release status codes | |
| US7574379B2 (en) | Method and system of using artifacts to identify elements of a component business model | |
| US9852382B2 (en) | Dynamic human workflow task assignment using business rules | |
| US8276152B2 (en) | Validation of the change orders to an I T environment | |
| US9354904B2 (en) | Applying packages to configure software stacks | |
| US7873940B2 (en) | Providing packages for configuring software stacks | |
| US11551105B2 (en) | Knowledge management using machine learning model trained on incident-knowledge relationship fingerprints | |
| US20160162819A1 (en) | Workflow definition, orchestration and enforcement via a collaborative interface according to a hierarchical procedure list | |
| US10782961B2 (en) | Analyzing components related to a software application in a software development environment | |
| US20070038683A1 (en) | Business intelligence system and methods | |
| US20080040364A1 (en) | Extensible multi-dimensional framework | |
| CN111145011B (en) | Banking system building method and device | |
| CN107247581B (en) | Method for constructing system analysis and summary design delivery model | |
| JP2009534773A (en) | Process coding | |
| US20100161676A1 (en) | Lifecycle management and consistency checking of object models using application platform tools | |
| CN111275590A (en) | Intellectual property management system based on SOA and development method thereof | |
| Oliveira et al. | Using REO on ETL conceptual modelling: a first approach | |
| Cabanillas et al. | A mashup-based framework for business process compliance checking | |
| US11442724B2 (en) | Pattern recognition | |
| US20140149186A1 (en) | Method and system of using artifacts to identify elements of a component business model | |
| CN110737427B (en) | Internet technology architecture, construction method and device thereof, electronic equipment and medium | |
| Allbee | Hands-On Software Engineering with Python: Move beyond basic programming and construct reliable and efficient software with complex code | |
| Yang et al. | Single-state state machines in model-driven software engineering: an exploratory study | |
| Familiar et al. | Data visualizations, alerts, and notifications with power BI | |
| US11537747B1 (en) | Generating and continuously maintaining a record of data processing activity for a computer-implemented system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20220314 Address after: 25 Financial Street, Xicheng District, Beijing 100033 Patentee after: CHINA CONSTRUCTION BANK Corp. Address before: 100000 Jindi Mingjing C2 1204, No. 2, liyuanli North Street, Chaoyang District, Beijing Patentee before: Liu Li |
|
| TR01 | Transfer of patent right |