CN114429083A

CN114429083A - Modeling method for system architecture design

Info

Publication number: CN114429083A
Application number: CN202210034139.2A
Authority: CN
Inventors: 沈蔚华; 姜海波; 安飞; 庄长辉; 王泊涵
Original assignee: Shanghai Sharee Tech Co ltd
Current assignee: Shanghai Sharee Tech Co ltd
Priority date: 2022-01-13
Filing date: 2022-01-13
Publication date: 2022-05-03
Anticipated expiration: 2042-01-13
Also published as: CN114429083B

Abstract

The invention relates to the technical field of modeling, in particular to a modeling method for system architecture design. The method is based on a DoDAF v2.0 framework, and uses 52 views at 8 views of covering AV global view, CV capability view, OV battle view, DIV data view, SvcV service view, SV system view, PV project creation view and StdV standard view, so that a system architecture model is more effectively and completely expressed.

Description

Modeling method for system architecture design

Technical Field

The invention relates to the technical field of modeling, in particular to a modeling method for system architecture design.

Background

When building complex architectures, engineers must have the ability to understand and manage complex relationships.

The architecture is critical to efficient design, implementation, deployment, and maintenance of the evolving systems, reducing risks, and managing the complexity of the system.

Based on the recognition of the importance of the system architecture, the united states department of defense develops the DoDAF (system defense department architecture framework) on the basis of the unified description of the C4ISR system architecture, and becomes the architecture framework description standard which is generally followed by system designers all over the world at present.

For a long time, when building architectural models of a system, engineers often use a six-step method:

1. determining the use of the architecture (including risk investor requirements, purposes, key problems, target objects, key tradeoffs, decision points and analysis modes);

2. determining the purpose and scope of the architecture (including geography, operation, functional boundaries, technical boundaries, time range, architecture resources, progress constraints);

3. determining data (including architecture data entity, detail degree, measurement unit, associated metadata) supporting architecture development

4. Collecting, organizing, associating, and storing architectural data (including automated storage libraries, activity models, data models, dynamic models, organization models, metadata registries);

5. the analysis of the support architecture target (including defect analysis, capability analysis, interoperability evaluation, business process analysis, test integrity, test accuracy and test sufficiency);

6. generating the document result (comprising architecture demonstration, architecture viewpoint, reusable architecture data and analysis report) meeting the requirements of the decision maker.

If a six-step method is used for building an architecture model, the core of the method is to perform purpose-based cropping on a visual angle, and the method provides abstract thought guidance for a modeler without a specific process. In real practice, the method is too macroscopic, and the experience abilities of architects are uneven, so that the architectural design based on the six-step method is difficult to land.

Disclosure of Invention

The technical problem to be solved by the invention is as follows: the modeling method is different from the original modeling method of a six-step method, takes a minimum set from problem to problem solution as a core, provides a specific modeling flow for the first time, is gradually mature after years of practice, and is widely applied to various system architecture model designs.

The technical scheme adopted by the invention is as follows: a modeling method for architecture design comprises the following steps:

s1, establishing an AV global view:

s1.1, establishing an AV-1 global background description view or a global architecture overview view, and describing the conception, scope, purpose, action, event and battlefield environment of a project;

s2, establishing a CV capability visual angle:

s2.1, establishing a CV-1 capability idea view, and providing strategic background and high-level visual field for the described capability;

s2.2, establishing a CV-2 capability decomposition view and describing a hierarchical structure of the capability;

s2.3, establishing a CV-4 capability dependency view to describe the dependency relationship among the capabilities;

s2.4, establishing a CV-3 capacity planning view, and describing planned capacities at different time points;

s3, establishing an OV operation view angle:

s3.1, establishing an OV-1 high-level operation concept view or a high-level graphic operation concept view, and describing a high-level operation concept;

s3.2, establishing an OV-4 combat organization relation view, and describing command relations and resource interaction relations among typical organizations and personnel composition and skills of actual organizations;

s3.3, establishing an OV-5a battle activity group decomposition view, and describing the hierarchical structure of the battle activities;

s3.4, establishing an OV-5b campaign view, and describing the relationship between the campaign and the input and output;

s4, establishing a DIV data view angle:

s4.1, establishing a DIV-1 conceptual data model view, and describing conceptual data related to a battle level;

s4.2, establishing a DIV-2 logic data model view, and describing the structural definition of the system architecture concept data;

s5, returning to the OV battle view:

s5.1, establishing an OV-2 combat troop resource flow description view or a combat unit relation view, and describing connection and information interaction between combat nodes;

s5.2, establishing an OV-3 battle resource interaction matrix view, and describing exchanged resources and exchange related attribute information;

s5.3, establishing an OV-6a battle constraint view to identify a business rule of constraint battle;

s5.4, establishing an OV-6c battle time sequence description view so as to track various activities in a scene or a series of events;

s5.5, establishing an OV-6b combat unit state conversion view to identify a business process corresponding to an event;

s6, return to CV capability perspective:

s6.1, establishing a CV-6 capacity and combat activity mapping view to describe the mapping relation between the capacity and the combat activity expressing the capacity;

s7, establishing an SvcV service view angle:

s7.1, establishing a description view of an SvcV-1 service interface, and describing the synthesis and interaction of services;

s7.2, establishing an SvcV-4 service function decomposition view or a service function flow description view to describe the functions executed by the service and the data flow among the service functions;

s7.3, establishing an SvcV-2 service relation view or a service instance resource flow description view, and describing an interface exchanged between services;

s7.4, establishing an SvcV-3b service interaction matrix view, and describing the interaction relationship between services;

s7.5, establishing an interaction matrix view of the SvcV-6 service resources, and describing relevant characteristics of service resource flows exchanged among services;

s7.6, establishing an SvcV-7 service measurement view, describing performance characteristics and measurement definition, and identifying non-functional requirements;

s7.7, establishing an SvcV-8 service evolution view, describing that a group of services are gradually developed into more efficient services to adapt to future requirements;

s7.8, establishing a SvcV-9 service technology prediction view, and describing new technologies, software/hardware and skills influencing future service development;

s7.9, establishing an SvcV-10a service constraint view to describe functional and non-functional constraints in the implementation of the system architecture;

s7.10, establishing an SvcV-10c service time sequence description view, and describing a specific service to meet a key event sequence in a battle view;

s7.11, establishing an SvcV-10b service state transition view to identify the response behavior of the service node to the event;

s7.12, establishing a mapping view of the SvcV-5 service and the fighting activity, and describing a satisfying relation between the service and the fighting activity;

s8, return to CV capability perspective:

s8.1, establishing a CV-7 capacity and service mapping view, and describing a mapping relation between capacity and service resources supporting the capacity;

s9, establishing an SV system view angle:

s9.1, establishing an SV-1 system decomposition and external interface definition view or a system personnel interface definition view to describe the interaction relationship between the system composition and the system and actual personnel;

s9.2, establishing an SV-4 system function decomposition view or a system function flow description view, describing functions of a system and data flow among the functions of the system;

s9.3, establishing an SV-2 system relationship view or a system instance resource flow description view, and describing the interface relationship exchanged between systems;

s9.4, establishing an SV-3 system interaction matrix view, and describing the relationship between systems;

s9.5, establishing an SV-6 system resource interaction matrix view, and describing system resource flow interacted among systems;

s9.6, establishing an SV-5a system function and combat activity mapping view, and describing a mapping relation from the system function to the combat activity;

s9.7, establishing an SV-5b system and combat activity mapping view, and describing a mapping relation from the system to the combat activity;

s10, return to SvcV service perspective:

s10.1, establishing a mapping view of the SvcV-3a service and a system, and describing an interactive relation between the system and the service;

s11, returning to the view angle of the SV system:

s11.1, establishing an SV-7 system measurement view, describing performance characteristics and measurement definition, and identifying non-functional requirements;

s11.2, establishing an SV-8 system evolution view, and describing a planning step of the evolution of the current system to a future system;

s11.3, establishing an SV-9 system technology prediction view, and describing an emerging technology, soft/hard, influencing future system development

Pieces and skills;

s11.4, establishing an SV-10a system constraint view, and describing constraints acting on system function design and implementation;

s11.5, establishing an SV-10c system time sequence description view, and describing a key event sequence of the system;

s11.6, establishing an SV-10b system state transition view, and describing the response of the system to an event;

s12, return to the DIV data perspective:

s12.1, establishing a DIV-3 physical data model view, and describing what basic data types constitute in the information reality in the DIV-2 logical data model view;

s13, establishing a PV project view angle:

s13.1, establishing a PV-1 project and organization mapping view or project combination relation view, describing the dependency relationship between organizations and projects, and managing the organization structure required by a group of projects;

s13.2, returning to the CV-5 visual angle, establishing a capacity and development organization mapping view, and expressing which organization the actual bearing equipment of the required combat capacity carries out actual project development;

s13.3, establishing a PV-2 project progress plan view, and describing the time progress of the project or plan;

s13.4, establishing a PV-3 project and capability mapping view, describing how to realize certain capability through a specific project or plan;

s14, establishing a StdV standard view angle:

s14.1, establishing a StdV-1 standard abstract view, and describing a standard list applied to a solution;

s14.2, establishing a StdV-2 standard prediction view, and describing the potential influence of future standards on the current solution;

s15, returning to the AV global view:

s15.1, an AV-2 global data dictionary view is established, and all terms and data in the whole system framework are described.

Compared with the prior art, the method has the following advantages that: by using the method, the establishing process of each view can be further determined on the basis of the standard of the DoDAF2.0 six-step method, the system architecture model facing various service scenes can be quickly and efficiently established, and the efficiency is improved for the problem of system architecture design transformation of various large and medium-sized enterprises in China. On the basis of the method, system architecture models of various enterprises can be cut and expanded based on the service field of the enterprises, so that the DoDAF six-step methodology method which is difficult to land can be used for quickly performing land practice.

Drawings

FIG. 1 is a flow diagram of the architectural design oriented modeling method of the present invention.

FIG. 2 is a view illustrating the overall background of AV-1 in the embodiment.

FIG. 3 is a conceptual view of the capability of CV-1 in the examples.

FIG. 4is an exploded view of the CV-2 capacity of the embodiment.

FIG. 5 is a CV-4 capability dependency graph in an example.

FIG. 6 is a diagram of CV-3 capacity planning in an example embodiment.

FIG. 7 is a conceptual view of OV-1 high-level battle in the embodiment.

FIG. 8 is a view of OV-4 combat organizational relationship in an embodiment.

FIG. 9 is an exploded view of the OV-5a campaign team in an embodiment.

FIG. 10 is a view of OV-5b combat activity in accordance with an embodiment.

FIG. 11 is a DIV-1 conceptual data model view of an embodiment.

FIG. 12 is a DIV-2 logical data model view of an embodiment.

FIG. 13 is a view illustrating the resource flow of OV-2 combat army in the embodiment.

FIG. 14 is a view of OV-3 battle resource interaction matrix in the embodiment.

FIG. 15 is a view of OV-6a battle constraints in the example.

FIG. 16 is a partial schematic view of OV-6c battle timing description view in the embodiment.

FIG. 17 is a view showing the state transition of OV-6b combat unit in the embodiment.

FIG. 18 is a CV-6 capability and campaign map of the example.

FIG. 19 is a view showing the description of the SvcV-1 service interface in the embodiment.

Fig. 20 is an exploded view of the SvcV-4 service function in the embodiment.

Figure 21 is a view of SvcV-2 service relationships in an embodiment.

FIG. 22 is a view of an interaction matrix of the SvcV-3b service in the embodiment.

Figure 23 is a view of the interaction matrix of SvcV-6 service resources in the embodiment.

Figure 24 is an example SvcV-7 service metrics view.

Figure 25 is an evolution view of the SvcV-8 service in the embodiment.

Figure 26 is a SvcV-9 service technology prediction view of an embodiment.

Figure 27 is a view of SvcV-10a service constraints in an embodiment.

FIG. 28 is a partial schematic diagram of a service timing description view of SvcV-10c in the embodiment.

Fig. 29 is a service state transition view of SvcV-10b in the embodiment.

FIG. 30 is a diagram of an embodiment of the SvcV-5 service and campaign mapping.

FIG. 31 is a CV-7 capability to service mapping view of an embodiment.

FIG. 32 is an exploded view of the SV-1 system and the definition of external interfaces in the embodiment.

FIG. 33 is a functional exploded view of the SV-4 system in the embodiment.

FIG. 34 is a view showing the relationship between SV-2 systems in the embodiment.

FIG. 35 is a view of interaction matrix of SV-3 system in the embodiment.

FIG. 36 is a view of interaction matrix of SV-6 system resources in the embodiment.

FIG. 37 is a view of SV-5a system function and combat activity mapping in the embodiment.

FIG. 38 is a view of the SV-5b system and the mapping of the campaign in the example.

Figure 39 is a view of the SvcV-3a service to system mapping in an embodiment.

FIG. 40 is a measurement diagram of the SV-7 system in the example.

FIG. 41 is an evolution diagram of an SV-8 system in the embodiment.

FIG. 42 is a diagram of SV-9 system technology prediction in an example embodiment.

FIG. 43 is a constraint view of the SV-10a system in the example.

FIG. 44 is a partial schematic diagram of a timing diagram of an SV-10c system in the embodiment.

FIG. 45 is a view showing state transition of an SV-10b system in the embodiment.

FIG. 46 is a DIV-3 physical data model view of an embodiment.

FIG. 47 is a view of the PV-1 project and organization map of an embodiment.

FIG. 48 is a CV-5 capability and development organization map view in an embodiment.

FIG. 49 is a plan view of the PV-2 project schedule in an embodiment.

FIG. 50 is a diagram of PV-3 project and capability mapping in an embodiment.

FIG. 51 is a summary view of the StdV-1 standard in the examples.

FIG. 52 is a StdV-2 standard prediction view in an example embodiment.

FIG. 53 is an AV-2 global data dictionary view in the embodiment.

Detailed Description

Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are exemplary and intended to be illustrative of the invention and are not to be construed as limiting the invention.

As shown in fig. 1, a modeling method for architecture design, as shown in fig. 1, includes the following steps:

s1, establishing an AV global view:

s1.1, establishing an AV-1 global background description view or a global architecture overview view, as shown in FIG. 2, describing the conception, scope, purpose, action, event and battlefield environment of a project;

s2, establishing a CV capability visual angle:

s2.1, establishing a CV-1 capability idea view, as shown in FIG. 3, providing strategic background and high-level visual field for the described capability;

s2.2, establishing a CV-2 capability decomposition view, as shown in FIG. 4, describing a hierarchical structure of the capability;

s2.3, establishing a CV-4 capability dependency view, as shown in FIG. 5, describing the dependency relationship among the capabilities;

s2.4, establishing a CV-3 capacity planning view, as shown in FIG. 6, describing planned capacities at different time points;

s3, establishing an OV operation view angle:

s3.1, establishing an OV-1 high-level operation concept view or a high-level graphic operation concept view, as shown in FIG. 7, and describing a high-level operation concept;

s3.2, establishing an OV-4 combat organization relation view, as shown in FIG. 8, describing command relations and resource interaction relations among typical organizations and personnel composition and skills of actual organizations;

s3.3, establishing an OV-5a battle activity group decomposition view, as shown in FIG. 9, describing the hierarchical structure of the battle activity;

s3.4, establishing an OV-5b battle activity view, as shown in FIG. 10, describing the relationship between the battle activity and the input and output;

s4, establishing a DIV data view angle:

s4.1, establishing a DIV-1 conceptual data model view, as shown in FIG. 11, describing conceptual data related to a battle level;

s4.2, establishing a DIV-2 logical data model view, as shown in FIG. 12, describing the structural definition of the system architecture concept data;

s5, returning to the OV battle view:

s5.1, establishing an OV-2 combat troop resource flow description view or a combat unit relation view, as shown in FIG. 13, describing connection and information interaction between combat nodes;

s5.2, establishing an OV-3 battle resource interaction matrix view, as shown in FIG. 14, describing exchanged resources and exchange related attribute information;

s5.3, establishing an OV-6a battle constraint view, as shown in FIG. 15, to identify business rules for constraint battle;

s5.4, establishing an OV-6c battle time sequence description view, as shown in FIG. 16, wherein only a part of the battle time sequence is described in the view so as to track various activities in a scene or a series of events;

s5.5, establishing an OV-6b combat unit state transition view as shown in figure 17 to identify a business process corresponding to an event;

s6, return to CV capability perspective:

s6.1, establishing a CV-6 capacity and campaign mapping view, as shown in FIG. 18, so as to describe the mapping relationship between the capacity and the campaign for representing the capacity;

s7, establishing an SvcV service view angle:

s7.1, establishing a description view of an SvcV-1 service interface, as shown in FIG. 19, describing the synthesis and interaction of the service;

s7.2, establishing an SvcV-4 service function decomposition view or a service function flow description view, as shown in FIG. 20, to describe the functions executed by the service and the data flow among the service functions;

s7.3, establishing an SvcV-2 service relation view or a service instance resource flow description view, as shown in FIG. 21, describing interfaces exchanged between services;

s7.4, establishing an interaction matrix view of the SvcV-3b service, as shown in FIG. 22, and describing the interaction relationship between the service and the service;

s7.5, establishing an interaction matrix view of the SvcV-6 service resources, as shown in FIG. 23, describing relevant characteristics of service resource flows exchanged between services;

s7.6, establishing an SvcV-7 service measurement view, as shown in FIG. 24, describing performance characteristics and measurement definitions, and identifying non-functional requirements;

s7.7, establishing an evolution view of the SvcV-8 service, as shown in FIG. 25, describing that a group of services are gradually developed into more efficient services to meet future requirements;

s7.8, establishing an SvcV-9 service technology prediction view, as shown in FIG. 26, describing new technologies, software/hardware and skills influencing future service development;

s7.9 establishing a SvcV-10a service constraint view, as shown in FIG. 27, to describe functional and non-functional constraints in the implementation of the architecture;

s7.10, establishing an SvcV-10c service time sequence description view, as shown in FIG. 28, describing a specific service to meet a key event sequence in a battle view;

s7.11 establishing a SvcV-10b service state transition view, as shown in FIG. 29, to identify the response behavior of the service node to the event;

s7.12, establishing a mapping view of the SvcV-5 service and the fighting activity, and describing the satisfying relation from the service to the fighting activity as shown in figure 30;

s8, return to CV capability perspective:

s8.1, establishing a CV-7 capacity and service mapping view, as shown in FIG. 31, describing the mapping relationship between the capacity and the service resources supporting the capacity;

s9, establishing an SV system view angle:

s9.1, establishing an SV-1 system decomposition and external interface definition view or a system personnel interface definition view, as shown in FIG. 32, so as to describe the interaction relationship between the system composition and the system and actual personnel;

s9.2, establishing an SV-4 system function decomposition view or a system function flow description view, as shown in FIG. 33, describing the functions of the system and the data flow among the functions of the system;

s9.3, establishing an SV-2 system relationship view or a system instance resource flow description view, as shown in FIG. 34, describing the interface relationship exchanged between systems;

s9.4, establishing an SV-3 system interaction matrix view, as shown in FIG. 35, describing the relationship between systems;

s9.5, establishing an SV-6 system resource interaction matrix view, as shown in FIG. 36, describing the system resource flow of interaction between systems;

s9.6, establishing a mapping view of SV-5a system functions and the combat activities, and describing a mapping relation from the system functions to the combat activities as shown in FIG. 37;

s9.7, establishing an SV-5b system and combat activity mapping view, as shown in FIG. 38, describing the mapping relation from the system to the combat activity;

s10, return to SvcV service perspective:

s10.1, establishing a mapping view of the SvcV-3a service and the system, as shown in FIG. 39, and describing an interactive relationship between the system and the service;

s11, returning to the SV system view angle:

s11.1, establishing an SV-7 system measurement view, as shown in a figure 40, describing performance characteristics and measurement definition, and identifying non-functional requirements;

s11.2, establishing an SV-8 system evolution view, as shown in FIG. 41, describing a planning step of the evolution of the current system to a future system;

s11.3, establishing an SV-9 system technology prediction view, as shown in FIG. 42, describing emerging technologies, software/hardware and skills which influence future system development;

s11.4, establishing an SV-10a system constraint view, as shown in FIG. 43, describing constraints acting on system function design and implementation;

s11.5, establishing an SV-10c system time sequence description view, as shown in FIG. 44, describing a key event sequence of the system;

s11.6, establishing an SV-10b system state transition view, as shown in FIG. 45, describing the response of the system to an event;

s12, return to the DIV data perspective:

s12.1, establishing a DIV-3 physical data model view, as shown in FIG. 46, describing what basic data types constitute in the information reality in the DIV-2 logical data model view;

s13, establishing a PV project view angle:

s13.1, establishing a PV-1 project and organization mapping view or project combination relation view, as shown in FIG. 47, describing the dependency relationship between organizations and projects, and the organization structure required by managing a group of projects;

s13.2, returning to the CV-5 visual angle, establishing a capacity and development organization mapping view, and as shown in FIG. 48, expressing which organization the actual bearing equipment of the required combat capacity carries out actual project development;

s13.3, establishing a PV-2 project schedule view, as shown in figure 49, describing the time schedule of the project or schedule;

s13.4, establishing a PV-3 project and capability mapping view, as shown in FIG. 50, describing how to implement a certain capability through a specific project or plan;

s14, establishing a StdV standard view angle:

s14.1 establishing a StdV-1 standard abstract view, as shown in FIG. 51, describing a standard list applied to a solution;

s14.2, establishing a StdV-2 standard prediction view, as shown in FIG. 52, describing the potential impact of future standards on the current solution;

s15, returning to the AV global view:

s15.1 establishes an AV-2 global data dictionary view, as shown in FIG. 53, describing all terms and data in the entire architecture.

Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention, and that variations, modifications, substitutions and alterations can be made to the above embodiments by those of ordinary skill in the art within the scope of the present invention.

Various alterations and modifications will no doubt become apparent to those skilled in the art after having read the above description. Therefore, the appended claims should be construed to cover all such variations and modifications as fall within the true spirit and scope of the invention. Any and all equivalent ranges and contents within the scope of the claims should be considered to be within the intent and scope of the present invention.

Claims

1. A modeling method for architecture design is characterized by comprising the following steps:

s1, establishing an AV global view:

s2, establishing a CV capability visual angle:

s3, establishing an OV operation view angle:

s3.3, establishing an OV-5a battle activity group decomposition view, and describing a hierarchical structure of the battle activity;

s4, establishing a DIV data view angle:

s5, returning to the OV battle view:

s6, return to CV capability view:

s7, establishing an SvcV service view angle:

s8, return to CV capability perspective:

s9, establishing an SV system view angle:

s9.2, establishing an SV-4 system function decomposition view or a system function flow description view, and describing functions of a system and data flow among the functions of the system;

s10, return to SvcV service perspective:

s11, returning to the view angle of the SV system:

Pieces and skills;

s12, return to the DIV data perspective:

s13, establishing a PV project view angle:

s14, establishing a StdV standard view angle:

s15, returning to the AV global view: