Model-based information system modeling method

Abstract

The invention belongs to the field of system engineering, and particularly relates to a model-based information system modeling method, which comprises the following steps of: S1, determining an operation scene and a benefit-critical party of an information system, and constructing a first demand analysis chart associated with the operation scene and the benefit-critical party; s2, determining behaviors of all the benefit critical parties in all the operation scenes, and forming a second demand analysis chart containing demand entries; s3, layering the functions and composition of the information system, determining the transfer relationship of substances, energy or signals among the functional layers to form a first functional analysis chart, and determining the hierarchical architecture of each composition layer to form an architecture analysis chart; step S4, determining information circulation of each function among a plurality of nodes in each layer of the hierarchical architecture to form a second function analysis chart; and S5, based on the hierarchical architecture, determining a performance parameter relationship of adjacent hierarchies, and constructing a performance analysis chart. The method can effectively support the demand design of a complex information system and improve the scheme design quality.

Description

Technical Field

[0001] The present application belongs to the field of system engineering, and in particular relates to a model-based information system modeling method. Background Art

[0002] In order to improve the quality and efficiency of information systems, the MBSE design method based on model-based systems engineering is adopted. It is a system engineering methodology that uses models as the core of system design and analysis, aiming to replace the traditional document-driven method to improve efficiency and reduce errors. The development background of MBSE stems from the increasing complexity and challenges in the field of system engineering. With the rapid development of technology, system engineers need to coordinate changing requirements, predict future technological trends, and deal with potential risks. In order to meet these challenges, the MBSE methodology came into being.

[0003] Modeling methods are an important foundation for implementing MBSE. For complex system design processes, modeling methods are used to guide engineers to abstract design objects and processes, and ultimately form a complete set of models to support analysis and simulation. In the MBSE practice process, due to the limitations of MBSE methods and information tools, there is currently no concise and effective modeling method. There are many problems in the process of requirement description, system solution design, etc., such as incomplete analysis, inaccurate definition, and low efficiency. Summary of the invention

[0004] In order to solve the above problems, this application provides a model-based information system modeling method from the perspective of requirements-function-architecture-performance, forms a model of the design process, and displays the model through a modeling tool.

[0005] The model-based information system modeling method provided in this application mainly includes:

[0006] Step S1: determining the operation scenarios and stakeholders of the information system, and constructing a first demand analysis diagram associated with each of the operation scenarios and each of the stakeholders;

[0007] Step S2: determining the behavior of each stakeholder under each of the operation scenarios, and forming a second demand analysis diagram including demand items;

[0008] Step S3, layering the functions and components of the information system, determining the transmission relationship of matter, energy or signal between each functional layer, forming a first functional analysis diagram, and determining the hierarchical structure of each component layer, forming an architecture analysis diagram;

[0009] Step S4, determining the information flow of each function between multiple nodes in each layer of the hierarchical architecture to form a second function analysis diagram;

[0010] Step S5: Based on the hierarchical architecture, determine the performance parameter relationship between adjacent hierarchies and construct a performance analysis diagram.

[0011] Preferably, step S1 further comprises:

[0012] Step S11, determining the boundary of the information system, the concept and boundary of stakeholders of the information system;

[0013] Step S12: describing various operation scenarios of the information system through use cases;

[0014] Step S13: According to the stakeholders involved in each operation scenario, each operation scenario is associated with each stakeholder, and the formed use case diagram is used as the first requirement analysis diagram.

[0015] Preferably, in step S2, the second demand analysis diagram is made using an activity diagram.

[0016] Preferably, in step S2, the second demand analysis diagram is made using a sequence diagram.

[0017] Preferably, in step S3, a functional flow diagram is used to draw the transfer relationship of matter, energy or signals between each functional layer, and a block definition diagram is used to draw the hierarchical structure of each component layer.

[0018] Preferably, in step S4, each function is assigned to a plurality of nodes, and a sequence diagram is used to draw the information flow of the function between the nodes.

[0019] This application can significantly improve the modeling efficiency and quality of engineering designers, thereby effectively supporting the demand design of complex information systems and improving the quality of solution design. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 It is a flow chart of a preferred embodiment of the model-based information system modeling method of the present application.

[0021] Figure 2 It is a schematic diagram of the overall modeling architecture organization of the model using the package diagram.

[0022] Figure 3 This is the first demand analysis diagram.

[0023] Figure 4 This is the second requirements analysis diagram.

[0024] Figure 5 It uses functional flow diagram to draw a schematic diagram of the transfer relationship of matter, energy or signals between various functional layers.

[0025] Figure 6 It uses block definition diagram to draw a hierarchical architecture diagram of each component layer.

[0026] Figure 7 It is a schematic diagram of information flow between different subsystems.

[0027] Figure 8 It is a schematic diagram of the performance parameters of the information system. DETAILED DESCRIPTION

[0028] In order to make the purpose, technical scheme and advantages of the implementation of this application clearer, the technical scheme in the implementation of this application will be described in more detail in combination with the drawings in the implementation of this application. In the drawings, the same or similar reference numerals throughout represent the same or similar elements or elements with the same or similar functions. The described implementation is a part of the implementation of this application, not all of the implementations. The implementation described below with reference to the drawings is exemplary and is intended to be used to explain this application, and cannot be understood as a limitation on this application. Based on the implementation in this application, all other implementations obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application. The implementation of this application is described in detail below in combination with the drawings.

[0029] This application provides a model-based information system modeling method, such as Figure 1 As shown, it mainly includes:

[0030] Step S1: determining the operation scenarios and stakeholders of the information system, and constructing a first demand analysis diagram associated with each of the operation scenarios and each of the stakeholders;

[0031] Step S2: determining the behavior of each stakeholder under each of the operation scenarios, and forming a second demand analysis diagram including demand items;

[0032] Step S3, layering the functions and components of the information system, determining the transmission relationship of matter, energy or signal between each functional layer, forming a first functional analysis diagram, and determining the hierarchical structure of each component layer, forming an architecture analysis diagram;

[0033] Step S4, determining the information flow of each function between multiple nodes in each layer of the hierarchical architecture to form a second function analysis diagram;

[0034] Step S5: Based on the hierarchical architecture, determine the performance parameter relationship between adjacent hierarchies and construct a performance analysis diagram.

[0035] This application constructs a demand analysis diagram through steps S1 and S2, constructs a function analysis diagram through steps S3 and S4, constructs an architecture analysis diagram through step S3, and constructs a performance analysis diagram through step S5. Therefore, this application is a functional logic modeling method based on demand-function-architecture-performance, and uses a package diagram to organize the model as a whole. Figure 2 shown.

[0036] In some optional implementations, step S1 further includes:

[0037] Step S11, determining the boundary of the information system, the concept and boundary of stakeholders of the information system;

[0038] Step S12: describing various operation scenarios of the information system through use cases;

[0039] Step S13: According to the stakeholders involved in each operation scenario, each operation scenario is associated with each stakeholder, and the formed use case diagram is used as the first requirement analysis diagram.

[0040] In this embodiment, the boundary can be understood as being used to limit the scope of the information system to be modeled, such as the functions or usage scope that the smart office system should implement. Similarly, stakeholders also need to define and limit its scope of application, such as which personnel are general staff, which personnel are general staff of other departments, which personnel are section leaders, which personnel are department leaders, etc. The operation scenario is the usage scenario of the information system to be modeled, such as the smart office system as the analyzed system; the operation scenario of the system is realized through use cases including sign-in, meeting notification, work notification, to-do display, work data query, etc. In step S13, the first demand analysis diagram formed is as follows: Figure 3 shown.

[0041] In some optional implementations, in step S2, the second demand analysis diagram is made using an activity diagram.

[0042] In some optional implementations, in step S2, the second demand analysis diagram is made using a sequence diagram. In this embodiment, the behaviors of each stakeholder in each scenario are clarified, the requirements are clarified, and the requirement items are formed, such as Figure 4 The requirement items for meeting notification of intelligent office system are given and drawn as a sequence diagram.

[0043] In some optional implementations, in step S3, a functional flow diagram is used to draw the transfer relationship of matter, energy or signals between each functional layer, and a block definition diagram is used to draw the hierarchical structure of each component layer.

[0044] In this embodiment, a functional flow diagram is used to draw the transfer relationship of materials, energy or signals between each functional layer. Figure 5 As shown, Figure 5 In the example, a function has two sub-functions. These two sub-functions obtain data prm_1 from the outside. Sub-function 1 processes the data prm_1 to obtain prm_2. Sub-function 2 processes the data prm_2 to obtain prm_3. Use the block definition diagram to draw the hierarchical structure of each component layer. Figure 6 As shown, Figure 6 In the information system, the information system includes multiple subsystems, each subsystem has multiple subsystems, each subsystem may be the lowest layer or the middle layer, when it is the middle layer, each subsystem also has multiple sub-subsystems.

[0045] In some optional implementations, in step S4, each function is assigned to a plurality of nodes, and a sequence diagram is used to draw the information flow of the function between the nodes.

[0046] In this embodiment, a sequence diagram is used to allocate functions to different components, so as to clarify the information flow of a certain function between different subsystems, such as Figure 7 As shown, subsystem 1 processes and generates message message_0, which is passed to subsystem 2. Subsystem 2 processes and generates message_1, which is passed to subsystem X. Subsystem X processes and generates message_2, which is passed to subsystem 3.

[0047] Finally, in step S5, a performance analysis is performed to define the important parameters in the system and clarify the relationship between the important parameters, such as Figure 8 As shown, the information system has a certain performance parameter, such as resource utilization rate M0, which is the sum of resource utilization rates of four systems, namely, subsystem 1, subsystem 2, subsystem X, and subsystem 3, that is, M0 = M1 + M2 + M3 + MX.

[0048] The method provided by this application simplifies the operation process and the threshold for using modeling tools, and can effectively assist designers in conducting functional logic analysis to support optimal solution trade-offs and technical decisions. Relevant practices have shown that this application can significantly improve the modeling efficiency and quality of engineering designers, thereby effectively supporting the demand design and solution design quality of complex information systems, and has extremely strong engineering promotion and application value.

[0049] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. A model-based information system modeling method, characterized in that: include: Step S1: determining the operation scenarios and stakeholders of the information system, and constructing a first demand analysis diagram associated with each of the operation scenarios and each of the stakeholders; Step S2: determining the behavior of each stakeholder under each of the operation scenarios, and forming a second demand analysis diagram including demand items; Step S3, layering the functions and components of the information system, determining the transmission relationship of matter, energy or signal between each functional layer, forming a first functional analysis diagram, and determining the hierarchical structure of each component layer, forming an architecture analysis diagram; Step S4, determining the information flow of each function between multiple nodes in each layer of the hierarchical architecture to form a second function analysis diagram; Step S5: Based on the hierarchical architecture, determine the performance parameter relationship between adjacent hierarchies and construct a performance analysis diagram.

2. The model-based information system modeling method according to claim 1, characterized in that: Step S1 further comprises: Step S11, determining the boundary of the information system, the concept and boundary of stakeholders of the information system; Step S12: describing various operation scenarios of the information system through use cases; Step S13: According to the stakeholders involved in each operation scenario, each operation scenario is associated with each stakeholder, and the formed use case diagram is used as the first requirement analysis diagram.

3. The model-based information system modeling method according to claim 1, characterized in that: In step S2, the second demand analysis diagram is made using an activity diagram.

4. The model-based information system modeling method according to claim 1, characterized in that: In step S2, the second demand analysis diagram is made using a sequence diagram.

5. The model-based information system modeling method according to claim 1, characterized in that: In step S3, a functional flow diagram is used to draw the transfer relationship of materials, energy or signals between each functional layer, and a block definition diagram is used to draw the hierarchical structure of each component layer.

6. The model-based information system modeling method according to claim 1, characterized in that: In step S4, each function is assigned to a plurality of nodes, and a sequence diagram is used to draw the information flow between the functions of each node.

Images