CN108897752B

CN108897752B - Intelligent electronic information system architecture description method

Info

Publication number: CN108897752B
Application number: CN201810424992.9A
Authority: CN
Inventors: 马雪峰; 黄辰; 周丽娜
Original assignee: China Academy of Electronic and Information Technology of CETC
Current assignee: China Academy of Electronic and Information Technology of CETC
Priority date: 2018-05-07
Filing date: 2018-05-07
Publication date: 2022-05-20
Anticipated expiration: 2038-05-07
Also published as: CN108897752A

Abstract

The invention discloses an intelligent electronic information system architecture description method, which focuses on the requirements of the development trend and high intelligence of the future network information system in deep networking and high intelligence, analyzes the concept connotation, morphological characteristics and action mechanism of the evolvable knowledge center network information system, provides an architecture description framework suitable for the design of the future intelligent network information system by enhancing the description of intelligent thinking, knowledge management, network security, service support, data and information organization and the like in an architecture view, can support the recombination and reuse of architecture products for multiple applications, and can be used for guiding the development, description and integration of the future system architecture.

Description

Intelligent electronic information system architecture description method

Technical Field

The invention relates to the technical field of electronic information, in particular to an intelligent electronic information system architecture description method.

Background

The DoDAF version 2.0 turns the focus from the architecture product to the architecture data, and particularly as shown in FIG. 1, a meta-model is used as an organization form of data, so that the collection, storage and maintenance of data required by efficient decision making are emphasized, the network center strategy of the American department of defense is supported, a solution of oriented services is described, and the creation and maintenance of a network center environment are facilitated. However, the method does not pay attention to the development trends of intellectualization, configuration, adaptability and the like of the future information system, so that the popularization and application of the DoDAF 2.0 system are limited.

Disclosure of Invention

The invention provides an intelligent electronic information system architecture description method, which aims to solve the problem that the prior art does not pay attention to the development trends of intellectualization, configuration, adaptability and the like of a future information system.

The invention provides an intelligent electronic information system architecture description method, which comprises the following steps: the combat view carries out development of combat concepts, description of combat resource flow, matrix of the combat resource flow, organization relationship, decomposition tree of the combat activity, model of the combat rule, description of the state transition of the combat and description of the tracking of the combat event from the perspective of carrying out the combat mission, and displays the combat view; the capacity view is connected with the system requirement analysis, development capacity conception and capacity classification are carried out from the perspective of integrated combined combat task support and combat guarantee capacity requirement, capacity stage relation, capacity membership relation, capacity and organization development mapping relation and capacity and combat activity mapping relation are obtained, and the capacity view is displayed; the service view describes service composition, functions and interrelations of the supporting combat business from the perspective of supporting service interoperation among cross-system, cross-department, cross-army and even cross-field, performs development service interface description, service resource flow description, system-service matrix, service function description, capability tracing service matrix, combat activity tracing service matrix, service resource flow matrix, service measurement matrix, service evolution description, service technology and skill prediction, service rule model, service state transition description and service event tracing description, and performs service view display; the system view follows the capability requirement in the capability view, the fighting intention in the fighting view and the service function in the service view, describes the information system component elements and the deployment relationship, develops the system interface description, the system resource flow description, the system-system matrix, the system function description, the fighting activity and system function tracing matrix, the fighting activity and system tracing matrix, the system resource flow matrix, the system measurement matrix, the system evolution description, the system technology and skill prediction, the system rule model, the system state transition description and the system event tracing description, and displays the system view.

Further, the method further comprises: the standard view is used for developing standard configuration files and standard predictions from the perspective of a management, design and development system, describing relevant combat, daily business, technology, industrial standard, project implementation convention, rule criteria and development concept and displaying the standard view.

Further, the method also includes: the equipment view describes equipment classification, indexes, systems and development routes required in the system view from the construction and management perspective, and requires development of equipment structure description, equipment and capability corresponding relation, equipment and combat mission corresponding relation, equipment tactical technical index description and equipment development.

Further, the method also includes: the knowledge view supports the realization of integration and sharing of knowledge resources as required from the perspective of integration, processing and application of the knowledge resources in organization, describes a knowledge operation mechanism based on representation, generation, organization, fusion, reasoning and collaborative operation of knowledge, and requires the development of knowledge interface description, knowledge resource flow description, knowledge-service matrix, knowledge-knowledge matrix, knowledge function description, capability tracing knowledge matrix, combat activity tracing knowledge matrix, knowledge resource flow matrix, knowledge measurement matrix, knowledge evolution description, knowledge technology and skill prediction, knowledge rule model, knowledge state transition description and knowledge event tracing description.

Further, the method also includes: the security view supports the construction of a unified Raspy security system, and has confidentiality, integrity, usability, traceability and resistance to data in the processes of storage, transmission, processing and release, and attack, prevention, detection, control, management and evaluation to information security environment, development of security interface description, security resource flow description, security-service matrix, security-security matrix, security function description, capability tracing security matrix, combat activity tracing security matrix, security resource flow matrix, security measurement matrix, security evolution description, security technology and skill prediction, security rule model, security state transition description and security event tracing description, and security view display.

Further, the method further comprises: the data and information view describes the requirements of combat and business information and management rules thereof, and defines the attributes, syntax and semantics of information/data of system combat and business requirements, so as to uniformly describe the information requirements and flow rules in the business process and require the development of a conceptual data model, a logical data model, a physical data model and an information view.

Further, the method further comprises: the intelligent view carries out development intelligent interface description, intelligent resource flow matrix, intelligent activity decomposition tree, intelligent activity model, intelligent rule model, intelligent state transition description and intelligent event tracking description from the perspective of intelligent application requirements in the operation process, and displays the intelligent view.

The invention has the following beneficial effects:

the invention aims at the development trend and the requirement of the future network information system in deep networking and high intellectualization, focuses on the requirement of network promotion for emerging intelligent capability, analyzes the concept connotation, morphological characteristics and action mechanism of the evolvable knowledge center network information system, provides a system structure description framework suitable for the design of the future intelligent network information system by enhancing the description of intelligent thinking, knowledge management, network safety, service support, data and information organization and the like in a system structure view, can support the recombination and reuse of a system structure product facing to a plurality of applications, and can be used for guiding the development, description and integration of the system structure of the future system.

Drawings

FIG. 1 is a schematic diagram of a prior art DoDAF 2.0 architecture;

fig. 2 is a schematic diagram of an electronic information system architecture according to an embodiment of the present invention.

Detailed Description

The embodiment of the invention provides an intelligent electronic information system architecture description method, and referring to fig. 2, the method comprises the following steps:

the combat view carries out development of combat concepts, description of combat resource flow, matrix of the combat resource flow, organization relationship, decomposition tree of the combat activity, model of the combat rule, description of the state transition of the combat and description of the tracking of the combat event from the perspective of carrying out the combat mission, and displays the combat view; the capacity view is connected with the system requirement analysis, development capacity conception and capacity classification are carried out from the perspective of integrated combined combat task support and combat guarantee capacity requirement, capacity stage relation, capacity membership relation, capacity and organization development mapping relation and capacity and combat activity mapping relation are obtained, and the capacity view is displayed; the service view describes service composition, functions and interrelations of the supporting combat business from the perspective of supporting service interoperation among cross-system, cross-department, cross-army and even cross-field, performs development service interface description, service resource flow description, system-service matrix, service function description, capability tracing service matrix, combat activity tracing service matrix, service resource flow matrix, service measurement matrix, service evolution description, service technology and skill prediction, service rule model, service state transition description and service event tracing description, and performs service view display; the system view follows the capability requirement in the capability view, the fighting intention in the fighting view and the service function in the service view, describes the information system component elements and the deployment relationship, develops the system interface description, the system resource flow description, the system-system matrix, the system function description, the fighting activity and system function tracing matrix, the fighting activity and system tracing matrix, the system resource flow matrix, the system measurement matrix, the system evolution description, the system technology and skill prediction, the system rule model, the system state transition description and the system event tracing description, and displays the system view.

In order to adapt to the transformation of the future military electronic information system in functions, structures, application modes and safety mechanisms under the requirement of integrated joint operation, the invention changes from describing the system functions to describing the task-oriented service interoperation under the requirement of task-oriented joint operation capacity; under the intelligent requirement of combat application, the method mainly changes from description information sharing to description knowledge organization and knowledge reasoning; under the requirement of the Saybook security, the Saybook threat is described, and the Saybook countermeasures are described to be changed to the task guarantee capability in the Saybook countermeasures environment.

Further, the system according to the embodiment of the present invention further includes: the standard view describes relevant combat, daily business, technology, industrial standard, project implementation convention, rule criterion and development conception from the perspective of a management, design and development system, develops standard configuration files and standard prediction, and displays the standard view.

The equipment view describes equipment classification, indexes, systems and development routes required in the system view from the construction and management perspective, and requires development of equipment structure description, equipment and capability corresponding relation, equipment and combat mission corresponding relation, equipment tactical technical index description and equipment development.

The knowledge view supports the realization of integration and sharing of knowledge resources as required from the perspective of integration, processing and application of the knowledge resources in organization, describes a knowledge operation mechanism based on representation, generation, organization, fusion, reasoning and collaborative operation of knowledge, and requires the development of knowledge interface description, knowledge resource flow description, knowledge-service matrix, knowledge-knowledge matrix, knowledge function description, capability tracing knowledge matrix, combat activity tracing knowledge matrix, knowledge resource flow matrix, knowledge measurement matrix, knowledge evolution description, knowledge technology and skill prediction, knowledge rule model, knowledge state transition description and knowledge event tracing description.

The security view is used for supporting the construction of a unified Saybolt security system, developing security interface description, security resource flow description, security-service matrix, security-security matrix, security function description, capability tracing security matrix, combat activity tracing security matrix, security resource flow matrix, security measurement matrix, security evolution description, security technology and skill prediction, security rule model, security state transition description and security event tracing description for the confidentiality, integrity, availability, traceability and anti-repudiation of data in the processes of storage, transmission, processing and distribution, and attacking, preventing, detecting, controlling, managing and evaluating information security environment, and displaying the security view.

The data and information view describes the requirements of the operational and business information and management rules thereof, defines the attributes, syntax and semantics of the information/data of the system operational and business requirements, so as to uniformly describe the information requirements and flow rules in the business process and require the development of a conceptual data model, a logical data model, a physical data model and an information view.

The intelligent view carries out development intelligent interface description, intelligent resource flow matrix, intelligent activity decomposition tree, intelligent activity model, intelligent rule model, intelligent state transition description and intelligent event tracking description from the perspective of intelligent application requirements in the operation process, and displays the intelligent view.

The system according to the invention will be explained and illustrated in detail below by means of a specific example:

the architecture products facing future system total 90, including 2 full view products, 6 capability view products, 9 battle view products, 8 intelligent view products, 14 knowledge view products, 14 security view products, 14 service view products, 13 system view products, 5 equipment view products, 3 data and information view products, 2 standard view products, the product catalog and summary description of each product are shown in table 1.

Architecture product definition and description: 1) the full view product: i. to summarize: the full view product mainly describes the abstract contents of the range, background, terms and the like of the architecture, and is the basis and foundation for the architecture development. The full view includes two products, summary and summary information (AV-1) and an integrated dictionary (AV-2).

Summary and summary information (AV-1): 1. product definition: AV-1 provides summary and summary information for the architectural design. The product is mainly used for providing planning instructive information in the initial stage of architecture development; and providing conclusion information of the architecture design after the architecture is completed. AV-1 enables a user to quickly understand the architecture and select desired content therefrom.

2. Product description: AV-1 mainly describes the purpose meaning of a development system structure, project background, development organization and other basic conditions, and the product can contribute to a high-level decision process. Summary and summary information (AV-1) consists of summary and background information of the architecture, including the identification, background, basic condition of the project, development requirement and conclusion of the architecture project.

(1) Problem background: background information describing an architecture, including missions, ordinances, goals and concepts, concepts of combat, scenarios, information security requirements, other threat conditions, geographic scope, etc., may also determine the source of rules, standards, or conventions that the architecture design must follow. (2) Item conditions: the method mainly comprises project names, project identifiers, project demonstration units and demonstration processes, project research units and users, the relationship between projects and other projects or mechanisms, development teams and the like, and further comprises the completion time and the required cost of the projects. (3) The design requirement is as follows: basic requirements for architecture development are provided, including views and products to be developed, development schedules, tools used for development, architecture data file formats, and the like. 4) And (4) conclusion: conclusions and suggestions made by the architectural work are set forth. The conclusion section also includes the identified deficiencies, recommended system implementations, and the like.

integrated dictionary (AV-2): 1. product definition: AV-2 defines all terms, abbreviations, used in architecture development and records all design elements and attributes in architecture development. AV-2 facilitates the user and designer to read and understand the developed architecture. AV-2 is a supplement to other products and can be used as a reference for designers and users.

2. Product description: AV-2 corresponds to an architectural data dictionary, containing all design elements and their attributes, terms, and abbreviations. AV-2 defines all specialized terms used in the architecture, but it is more detailed than a simple term and may contain Chinese names, English names, detailed definitions, and metadata. The abbreviation description mainly includes abbreviations, complete words, Chinese acronyms, etc. The design elements and their attributes are derived from various product design data, which are described in the form of a table in AV-2.

2) Capability view product: i. to summarize: the capacity view product designs the requirements on the development of the system capacity from the top level, determines the system capacity requirements, the capacity structure, the capacity relationship and the like to support the planning of military capacity, determines the mission and mission of battle, and overall planning the construction and development of equipment and the system. The capability view includes 6 products: capability idea (CV-1), capability classification (CV-2), capability staging (CV-3), capability membership (CV-4), capability to organization development mapping (CV-5), capability to combat activity mapping (CV-6).

Capability concept (CV-1): 1. product definition: CV-1 describes the main strategic development concept of the system, the operational security capability requirements, etc. CV-1 mainly provides macro capability requirements for system architecture design, embodies the top level goal of system construction, and provides a high level overview for various capabilities involved in the system architecture.

2. Product description: CV-1 generally describes the top level capability idea. The capability ideas generally begin by analyzing the top-level ideas, and then describe the fighting mission and the capability requirements of the top-level combat mission, further supplementing the related concepts. The information in CV-1 may come from combat concepts or from research reports. This information will provide guidance for future capability analysis, enabling equipment capability research specialists to determine future needs. In the reverse engineering of system comprehensive integration and upgrading and reconstruction implementation, the capability idea is mainly used for determining the initial capability idea of the system and the capability realized by integration or upgrading.

Capacity classification (CV-2): 1. product definition: CV-2 provides a structured list of the various capabilities and sub-capabilities required by a capability domain at a particular time, describing the definition of the capabilities, the classification of the capabilities, the partitioning of the sub-capabilities, and the dependencies. CV-2 is used for capacity classification, decomposition, analysis and review. In addition, the method can be used as a source document of top-level application cases and key user requirements of electronic information equipment construction planning and system overall design.

2. Description of the product: definition and composition of CV-2 main description capability, classification, division of child capability and dependency relationship description (root node is capability, branch node or leaf node is child capability) to obtain and organize specific capability needed by capability idea, and a structured capability list is formed. The structured list of CV-2 is a complete list of the system's deliverables required for a certain period of time. To improve the clarity and appropriate level of granularity required for late-stage capacity management, each capacity can be broken down into several sub-capacities as needed. The capability structure description is typically designed at the beginning, but may be developed at any stage. The various elements of CV-2 are not directed to a single system or piece of equipment, but rather to the effect that a group of systems together achieve, and a certain equipment or system may satisfy more than one capability. Quantitative attributes and metrics, such as processing speed, forward speed, maximum detection distance, etc., are included in the capability definition as much as possible. The magnitude of the representation is related to a particular time period, either the current value or a future target.

Capacity staging (CV-3): 1. product definition: CV-3 describes the level to which the capacity plan is to be reached during a particular time period of firing at different times (i.e., during the capacity staging).

2. Product description: CV-3 provides the ability to be available at different points in time or over specific periods of time. The capacity staging helps to determine capacity gaps, shortfalls, or capacity duplication and overlap. The capability staging may be represented by a table with rows representing capabilities from the capability classification model and columns representing time stages from the idea model, and the capability increments at the intersections of the rows and columns (i.e., cells) in the capability staging table may show the change in capabilities over that time period. If the capability spans multiple time periods, it can be represented by a rectangular bar. If the capacity of the partition does not meet the capacity requirement within a time period, the box is blank.

Capacity membership (CV-4): 1. product definition: CV-4 describes the relationship between various capabilities, determining the logical grouping of capabilities. CV-4 is used to analyze the dependencies between various capabilities and various capability groups. These dependencies and logical groupings can be illustrated to gain system capability, to link between different construction projects, to provide information for system design, adoption, and staging capability development.

2. Product description: CV-4 describes other relationships between capabilities besides dependencies, such as dependencies between capabilities, support relationships, etc., for the list of capabilities defined in CV-2. The capability dependency is generally defined in CV-2. Sometimes to elaborate on the relationships between capabilities, capability dependencies may also be present in CV-4. CV-4 describes the relationship between leaf capabilities, with emphasis on the top level of capabilities. The relationship between the capabilities of the upper layers can be embodied by the relationship between the capabilities of the leaves.

Mapping of capacity to organizational development (CV-5): 1. product definition: CV-5 describes the implementation of the processing power requirements, and the model accounts for the deployment of planned power and its interconnections at a particular stage.

2. Product description: CV-5 illustrates the ability to be deployed to a particular organizational structure, with each model of CV-5 being phase specific. At some stage, if a particular capability is or will be used by a particular organization, CV-5 will specify the mapping of capabilities to organizations. CV-5 may also specify interactions between them, which may be defined in either the system interface description or the service interface. CV-5 is typically represented in tabular form with one axis representing the appropriate organizational structure, the other axis representing the capacity, and the intersection of the two axes representing the capacity or resource object.

Capability versus campaign mapping (CV-6): 1. product definition: the CV-6 is used for describing the retrospective relationship between the capacity and the fighting activity, determining the capacity requirement of the fighting activity, facilitating quick browsing of decision-makers and users, quickly determining the difference between the fighting activity and the capacity requirement, and can be used as a basis for analyzing capacity definition or structure division, verifying the rationality and integrity of capacity planning or design, examining whether the planning or planning capacity meets the fighting requirement and the like.

2. Product description: CV-6 is a bridge between the combat view and the competency view, which describes which competency support is required to complete the undertaken combat activity. This correspondence reflects that the combat activity requires some sort of capability support to achieve the desired goal. CV-6 describes the corresponding relation of the capacity to the fighting activity in a matrix form, the capacity and the fighting activity are respectively used as the column and the row of the matrix, and each cell is marked by a symbol to express the requirement of a certain task on a certain capacity. To distinguish between different supporting relationships, different identifying icons may be used to distinguish between different relationships.

3) Battle view product

i. To summarize: the combat view details the combat mission or activity, the elements of the combat and the information exchange needed to support the combat process, and the pure combat view is system independent. However, the activities and relationships between activities may be affected by some systems that employ novice techniques, and to illustrate the improvements that the systems may facilitate in the practice of the combat, the limitations of existing systems in the practice of the combat should be documented. The battle view should be marked with some top-level system view data or added with some description of related content on the battle view product. The battle view includes 9 products: the system comprises a high-level combat concept graph (OV-1), a combat resource flow description (OV-2), a combat resource flow matrix (OV-3), an organization relation graph (OV-4), a combat activity decomposition tree (OV-5a), a combat activity model (OV-5b), a combat rule model (OV-6a), a combat state transition description (OV-6b) and a combat event-tracking description (OV-6 c).

Advanced operational concept (OV-1)

1. Product definition: the OV-1 briefly describes what the main battle missions are, who completed them, how, where, etc. Its main purpose is to provide a direct, macroscopic description of missions to high-level decision-making personnel (e.g., commanders) to support decisions.

2. Product description: OV-1 generally gives the macroscopic information of the architectural project to be developed, describes the mission/field covered by the project, and describes the viewpoints of departments and personnel such as various levels of commanders, main participation organs and other related supporting organizations concerning the project. OV-1 delineates the concept of battle, including what tasks to complete, who to complete the tasks, the order in which the tasks are completed, and the goals achieved, as well as the interaction with the environment and other external systems. OV-1 is the simplest of architectural products, has no fixed format requirements, and can be illustrated in one or more drawings and text, since the description of the mission is very abstract.

Battle resource flow description (OV-2)

1. Product definition: OV-2 describes the specific operational nodes that play an important role in the architecture, the primary operational activities they perform, the information interactions that exist between operational nodes, and the details of the information exchange. The purpose is that the graph and the text draw the logical connection relation of the fighting nodes and the exchange of fighting information between the fighting nodes, but do not describe the physical connection relation between the nodes. Where a resource flow is a simplistic representation of a path or network schema, it is often represented graphically as a connector, i.e., a line with a large amount of information.

2. Product description: OV-2 determines the operation nodes with key functions and the information exchange necessary for completing the operation activities in OV-5, and the operation information exchange relationship between the operation nodes is abstractly synthesized into the demand lines between the nodes. The operation nodes comprise operation nodes in the system structure and external nodes which do not belong to the range of the system structure and are related to the operation nodes, such as nodes which are important information sources or important information destinations of the operation nodes in the system structure, but each operation node belongs to a certain organization in OV-4. The demand line shows that information interaction relation exists between the combat nodes and information needing interaction.

According to the needs, OV-2 can be described in a layered mode, namely OV-2 can be sketched by a plurality of graphs in different layers. In describing OV-2, it is desirable to avoid having the actual physical facilities as the operational nodes, and to establish logical operational nodes based on operational missions or missions.

When a demand line is drawn, the direction of information flow is indicated by an arrow and named with a special identifier or phrase. The information to be exchanged between the nodes and the requirements for the exchanged information are given on the demand line in a literal form, but it is not necessary to explain how the information exchange is implemented. The relationship between the demand line and the information exchange is a many-to-many relationship, that is, there may be multiple information exchanges on one demand line, and one information exchange may occur on multiple demand lines. When the demand lines are drawn, the demand lines between the internal operation nodes of the system structure and the external operation nodes are provided. When indicating the demand lines between the external nodes and the external operational nodes, the demand lines should be distinguished from the demand lines between the internal operational nodes and the internal operational nodes.

If necessary, the battle activities completed by each battle node should be given on the graph, and these activities are consistent with the battle activities in the OV-5.

Battle resource flow matrix (OV-3)

1. Product definition: the OV-3 summarizes the relationship among three basic system structure data elements, namely the combat activity, the combat node and the information flow in the combat view in a table form, and describes the details of information exchange in detail, including who exchanges information with whom, the main content, the necessity and the security of the information and other information exchange characteristics. The information of interest can be traced back through the information exchange in OV-3.

2. Product description: the OV-3 should clearly describe the relevant attributes of the information exchange and associate them with the operational nodes and activities that generate or use the information, as well as with the demand lines. The information exchange describes actions and characteristics of certain information exchanged among the operation nodes, and generally comprises information element names and identifications, content description, operation node names and identifications for sending information, operation node names and identifications for receiving information, operation activity names and identifications for generating information, operation activity names and identifications for using information, information format, information exchange frequency/period, time limit requirements and the like, and also comprises characteristics of interoperation level requirements, information availability requirements, dependency requirements, integrity requirements, confidentiality, priority and the like. Wherein the information elements represent the content of the information exchanged between the combat nodes, which information elements may correspond to entities in the OV-7. Each information exchange in OV-3 is associated with a demand line and also with a campaign. The information exchange in OV-3 is in many-to-many relation with the demand line in OV-2, the information elements are not in one-to-one relation with the combat activities, and the information input and output connect the activities in OV-5c, but OV-3 does not need to describe the information input and output between the activities completed by the same node. The OV-3 does not attempt to list, without omission, the attributes involved in each information exchange of each operational node associated with the architecture, with the emphasis on characterizing the information exchange of interest to the user or designer.

Tissue relation graph (OV-4)

1. Product definition: the OV-4 describes various possible relationships among organizational layers involved in the architecture, internal organizations and external organizations, mainly command structures among the fighters, organizations or combat units playing a key role in the architecture, and command relationships, collaboration or collaboration relationships among the same.

2. Product description: OV-4 graphically depicts the various relationships that may exist between organizations in an architecture. To meet the objectives of architectural design, designers can define any required and important relationships as desired. The organization relationship in the OV-4 explains the basic role and management relationship in the battle system, and reflects how the battle nodes in the OV-2 can be connected from the perspective of the command. To better characterize the command organizational hierarchy, three types of organizations and their relationships are generally described. The organization unit and the relation thereof which are directly related to the operation nodes in the OV-2 and correspond to the operation tasks and the operation activity execution are the main part of the product design; the internal composition structure and relationship of some key units in these organization units, such as the composition units (various centers or service rooms) of the first-level combat unit (such as travel and camp) command post, and these contents are used as the supplement of the first-type design; thirdly, the organization in the first type of design is positioned in a higher level or higher level command system, and the design contents provide auxiliary information for users to understand the battle view.

Mission task exploded view (OV-5a)

1. Product definition: OV-5a briefly describes the tasks into which the main combat mission is broken down and the hierarchical relationships between the tasks.

2. OV-5a decomposes the combat mission described by OV-1 to form a task hierarchical tree, and outlines all tasks to make clear the purpose, main process and measurement index of the tasks.

Decomposition of battle activities (OV-5b)

1. OV-5a briefly describes the activities into which the primary combat mission or activity is broken down and the hierarchical relationships between the activities.

2. OV-5a decomposes the combat tasks or activities described in OV-1 to form an activity hierarchical tree, outlines all the activities, and defines the purposes, main processes and measurement indexes of the activities. To refine the description of the campaign, the campaign may be decomposed until the analysis needs of the designer are met. The decomposed combat activity forms a combat activity decomposition tree. The user can quickly view the composition and affiliation of the campaign by means of the combat campaign breakdown tree.

Action model for battle (OV-5b)

1. OV-5b describes the hierarchical decomposition relationship between the operational activities performed to complete a combat mission, as well as the input and output information flow between the operational activities. The OV-5b may specify the execution mechanisms for the campaign, the guidelines to be followed, and provide the necessary prerequisite constraints for the design of subsequent OV-6a, OV-6b, and OV-6 c.

2. Product description OV-5b may be described using a process diagram (e.g., IDEF0 diagram) containing inter-activity information flow input/output relationships. The operation nodes which finish the operation activities are considered when describing the OV-5b, and the information flow relationship existing among the activities finished by different operation nodes is mainly described. The campaign in the OV-5b may be annotated as necessary, for example, to illustrate that a campaign is being executed by "who" when, "the campaign may be annotated with the campaign node that completed the campaign and a sequence number.

Fighting rule model (OV-6a)

1. Product definition: OV-6a mainly defines the operational rules or business rules that constrain the business methods implemented within an enterprise. At the highest level, these rules should at least embody the operational concepts defined by OV-1 and provide guidelines for the development and definition of more detailed rules and behaviors that will occur during the subsequent architectural definition process.

2. Product description: OV-6a specifies the rules of operation and business that constrain the completion of business within an enterprise. At the mission level, the business rules contained in the ordinances, guidelines and engagement rules should be based. At a lower level, OV-6a describes the behavior criteria of the architecture under certain conditions. These criteria can be expressed in textual form, for example, if (these conditions) exist and (an event) occurs (these activities are performed).

Description of State transition (OV-6b)

1. Product definition: OV-6b describes how a combat activity responds to various events by changing its state. The model describes a series of events in response to an action, such as taking an action and then transitioning to another new state, each transition specifying an event and an action.

2. Product complaints are as follows: OV-6b reflects a clear sequence of events inside and outside the activity response, and OV-5a or OV-5b does not fully reflect such a sequence. OV-6b may also be used to reflect the order of internal behavioral responses to a single combat activity, or to reflect the order of responses to multiple combat activities. The OV-6b is based on a state diagram and the state machine is defined as "a specification describing all possible behaviors of some dynamic product elements. Behaviors can be viewed as state diagrams of round trips connected by one or more transition arcs, formed by the firing of instances of a series of events. During the traversal, the state machine completes a series of actions that are associated with different elements of the state machine. The graphic of the state diagram can be clearly transformed into structured text rules in a way that does not lose any information, which rules specify in detail the chronological order of the combat events and the responses to these combat events.

Event tracing description (OV-6c)

1. Product definition: OV-6c provides a time-sequential check of the resource stream according to particular scenarios. Each event tracking graph is accompanied by a description of the defined special ideas or a description of the situation. Sometimes referred to as an OV-6c sequence diagram, event scenario diagram, or timing diagram, the model may track actions within a scenario or critical event sequence.

2. Product description: the OV-6c model helps define the interaction and the battle flow, and also helps to ensure that each battle activity and site can obtain the necessary information at the correct time to complete the battle mission assigned to it. The OV-6c can track the critical sequence of actions or events in the idea. The model can be used alone or together with OV-6b to describe the dynamic behavior of business activities or to describe the dynamic behavior in mission scenarios and combat scenarios.

4) Intelligent view product

i. To summarize: the intelligent view describes the thinking activities of reasoning, learning, association, understanding, decision making, emotion and the like of the system from the perspective of the intelligent application of battle. The smart view includes 8 smart view products: intelligent interface description (IV-1), intelligent resource flow description (IV-2), intelligent resource flow matrix (IV-3), intelligent activity decomposition tree (IV-4), intelligent activity model (IV-5), intelligent rule model (IV-6a), intelligent state transition description (IV-6b), and intelligent event tracking description (IV-6 c).

Intelligent interface description (IV-1)

1. Product definition: IV-1 mainly describes the intelligent hierarchical division and its relations. The model can be used for carrying out classification management on intelligence, determining repeated and missing intelligence and whether the intelligence needs to be refined, and providing constraint and reference for the development of subsequent IV-2, IV-3 and IV-4.

2. Product description: IV-1 specifies intelligent hierarchical partitioning, which can be described using a simple treemap. With IV-1, intelligence and sub-level intelligence can be described and intelligent resource flow between the intelligence determined. The model is used to describe the intelligent resource structure, i.e., determine the main sub-levels of intelligence, actors and intelligent activities (functions) and interactions between them.

Intelligent resource flow description (IV-2)

1. Product definition: IV-2 describes specific intelligent nodes playing an important role in the architecture, the main intelligent activities they perform, the knowledge interaction relationships existing between the intelligent nodes and the details of knowledge exchange. The method has the purpose that the logic connection relation of the intelligent nodes and knowledge exchange between the intelligent nodes is drawn by the graphs and the characters, but the physical connection relation between the nodes is not described. Where a resource flow is a simplistic representation of a path or network schema, it is often represented graphically as a connector, i.e., a line with a large amount of information.

2. Product description: IV-2 is composed of intelligent nodes and intelligent resource flow among different intelligent nodes, and is consistent with IV-1 and IV-3. The content involved includes intelligent resource profile descriptions, intelligent functions, intelligent function constraints, and the like. Wherein the intelligent resource profile is a brief description of the intelligent context, requirements, categories, etc.; the intelligent function refers to specific intelligent resources provided by the intelligent resources; the intelligent function constraint is a constraint on indexes such as the execution performance of the intelligent function. IV-2 can be described using table collocation text. IV-2 determines the intelligent nodes with key functions and the knowledge exchange necessary for completing the intelligent activities in IV-4, and the knowledge exchange relationship existing between the intelligent nodes is abstractly synthesized into a demand line between the nodes. The intelligent nodes include both intelligent nodes within the architecture and external nodes not within the architecture but associated therewith, such as nodes that are sources or destinations of important information for intelligent nodes within the architecture. The requirement line shows that knowledge interaction relation exists among the intelligent nodes and knowledge needing interaction exists among the intelligent nodes.

The IV-2 can be described in a layered mode according to needs, namely the IV-2 can be drawn by a plurality of different-layer graphs. In describing IV-2, logical intelligent nodes should be built upon an intelligent task or mission.

When the demand line is drawn, the direction of the knowledge flow is indicated by an arrow and named with a special identifier or phrase. The requirement line gives the knowledge to be exchanged between the nodes and the requirements for the exchanged knowledge in a literal form, but does not need to explain how the knowledge exchange is implemented. The relationship between the demand line and the knowledge exchange is a many-to-many relationship, that is, there may be multiple knowledge exchanges on one demand line, and one knowledge exchange may occur on multiple demand lines. When the demand line is drawn, besides the demand line between the internal intelligent nodes of the system structure, the demand line between the external intelligent nodes is also provided. When representing the demand lines between the external nodes and the external intelligent nodes, the demand lines should be distinguished from the demand lines between the internal intelligent nodes and the internal intelligent nodes.

The intelligent activities performed by each intelligent node should be given on the graph as necessary, these activities being consistent with the intelligent activities in OV-4.

Intelligent resource flow matrix (IV-3)

1. Product definition: IV-3 summarizes the relationship among three basic architecture data elements, namely intelligent activities, intelligent nodes and knowledge flows, in the intelligent view in a table form, and describes the details of knowledge exchange in detail, including who exchanges knowledge with who, and knowledge exchange characteristics such as main content, necessity and security of the knowledge. The knowledge of interest can be traced through the knowledge exchange in IV-3.

2. Product description: IV-3 should clearly describe the relevant attributes of the knowledge exchange and associate them with the intelligent nodes and intelligent activities that generate or use knowledge, as well as with the demand line. The knowledge exchange describes actions and characteristics of exchanging knowledge among intelligent nodes, and generally comprises knowledge element names and identifications, content descriptions, intelligent node names and identifications for sending knowledge, intelligent node names and identifications for receiving knowledge, intelligent activity names and identifications for generating knowledge, intelligent activity names and identifications for using knowledge, knowledge formats, knowledge exchange frequency/period, time limit requirements and the like, and also comprises characteristics of interoperation level requirements, knowledge availability requirements, dependency requirements, integrity requirements, confidentiality, priority and the like. Wherein the knowledge elements represent the content of knowledge exchanged between the intelligent nodes, and the knowledge elements can correspond to the entities in the DIV-2. Each knowledge exchange in IV-3 is associated with a demand line and also with an intelligence campaign. The knowledge exchange in IV-3 is in many-to-many relation with the requirement line in IV-2, the knowledge elements are not in one-to-one relation with the intelligent activities, the knowledge input and output connect the activities in IV-4, but IV-3 does not need to explain the knowledge input and output between the activities completed by the same node. IV-3 does not attempt to list the attributes contained in each knowledge exchange of each intelligent node associated with the architecture, one for each, without omission, with the emphasis on characterizing the knowledge exchange as a user or designer is concerned.

Intelligent movable decomposition (IV-4)

1. Product definition: IV-4 briefly describes the activities into which the primary intelligent tasks or activities are broken down and the hierarchical relationships between the activities.

2. Product description: IV-4 decomposes the intelligent tasks or activities described in IV-1 to form an activity hierarchical tree, outlines all the activities, and defines the purposes, main processes and measurement indexes of the activities. To refine the description of the smart activity, the smart activity may be decomposed until the analysis needs of the designer are met. The decomposed intelligent activities form an intelligent activity decomposition tree. The user can quickly check the composition and the dependency relationship of the activities by means of the intelligent activity decomposition tree.

Intelligent activity model (IV-5)1. product definition: IV-5 describes primarily the hierarchical decomposition relationships between intelligent activities performed to accomplish an intelligent task, as well as the flow of input and output knowledge between intelligent activities. IV-5 may specify the performer of the intelligent activity, the criteria to follow, and provide the necessary prerequisite constraints for the design of subsequent IV-6a, IV-6b, and IV-6 c.

2. Product description: IV-5 may be described using a process diagram (e.g., IDEF0 diagram) that contains inter-activity knowledge flow input/output relationships. In the description of IV-5, intelligent nodes completing intelligent activities should be considered, and the knowledge flow relationship existing between activities completed by different intelligent nodes is mainly described. The intelligent activities in IV-5 may be annotated as necessary, e.g., to indicate that an intelligent activity was performed by "who" at "when," the intelligent activity may be annotated with the intelligent node that completed the intelligent activity and a sequence number.

intelligent rule model (IV-6a)1. product definition: IV-6a mainly defines intelligent rules and thinking rules that constrain the completion of intelligent thinking. At the highest level, these rules should at least embody the intelligent interface defined by IV-1 and provide guidelines for the development and definition of more detailed rules and behaviors that will occur during the subsequent architectural definition process.

2. Product description: IV-6a specifies intelligent rules and thinking rules. At the mission level, the business rules contained in the ordinances, guidelines and engagement rules should be based. At a lower level, IV-6a describes the behavior criteria of the architecture under certain conditions. These criteria can be expressed in textual form, for example, if (these conditions) exist and (an event) occurs (these activities are performed).

Description of State transition (IV-6b)1. product definition: IV-6b describes how smart activities respond to various events by changing their state. The model describes a series of events in response to an action, such as taking an action and then transitioning to another new state, each transition specifying an event and an action.

2. Product complaints are as follows: IV-6b reflects a clear sequence of events inside and outside the activity response, and IV-5a or IV-5b does not fully reflect such a sequence. IV-6b may also be used to reflect an order of internal behavioral responses to a single smart activity, or to reflect an order of responses to multiple smart activities. IV-6b are based on state diagrams, and state machines are defined as "a specification describing all possible behaviors of some dynamic product elements. Behaviors can be viewed as state diagrams of round trips connected by one or more transition arcs, formed by the firing of instances of a series of events. During the traversal, the state machine completes a series of actions that are associated with different elements of the state machine. The graph of the state diagram can be clearly transformed into structured text rules in a way that does not lose any information, which rules specify in detail the temporal order of the smart events and the responses to these smart events.

Intelligent event tracking description (IV-6c)1. product definition: IV-6c provides a timing check on the intelligent resource stream according to a special scenario. Each smart event tracking graph is accompanied by a description of the defined special ideas or a description of the situation. Sometimes referred to as a sequence diagram, event scenario diagram, or timing diagram, the model may track smart actions within a scenario or key smart event sequence.

2. Product description: the IV-6c model helps define interactions and intelligent processes, and also helps to ensure that each intelligent activity and site can acquire the necessary knowledge at the correct time to complete the intelligent tasks assigned to it. IV-6c can track the intelligent action or critical sequence of events in the thought. The model can be used alone or together with IV-6b to describe the dynamic behavior of intelligent activities, or to describe mission scenarios and dynamic intelligent behavior in intelligent scenarios.

5) Knowledge view product

i. To summarize: the knowledge view describes the composition, function and relationship of the system related knowledge from the perspective of knowledge resource management and knowledge service. The knowledge view includes 14 products: the system comprises a knowledge interface description (KV-1), a knowledge resource flow description (KV-2), a knowledge-service matrix (KV-3a), a knowledge-knowledge matrix (KV-3b), a knowledge function description (KV-4), a capability tracing knowledge matrix (KV-5a), a combat activity tracing knowledge matrix (KV-5b), a knowledge resource flow matrix (KV-6), a knowledge measurement matrix (KV-7), a knowledge evolution description (KV-8), a knowledge technology and skill prediction (KV-9), a knowledge rule model (KV-10a), a knowledge state transition description (KV-10b) and a knowledge event tracking description (KV-10 c).

Knowledge interface description (KV-1)1. product definition: KV-1 mainly describes the hierarchical division of knowledge and the relation between knowledge. The model can be used for carrying out classification management on knowledge, determining repeated and missing knowledge and whether the knowledge needs to be refined, and providing constraint and reference for the development of subsequent KV-2, KV-3 and KV-4.

2. Product description: KV-1 specifies the hierarchical division of knowledge, which can be described by a simple tree diagram. Knowledge and sub-level knowledge can be described using KV-1, and the flow of resources between knowledge can be determined. The model can be used to describe knowledge resource structures, i.e., to determine the primary sub-level knowledge, actors and activities (functions) and interactions between them.

Knowledge resource flow description (KV-2)1. product definition: the KV-2 model accounts for resource flow between knowledge and may list protocol stacks for connections to support knowledge publishing, discovery, and invocation. The KV-2 model provides an accurate connection specification between knowledge, which can be an existing connection specification or a newly-built connection specification for future connection.

2. Product description: KV-2 is composed of knowledge base and knowledge resource flow between different knowledge bases, and is consistent with KV-1 and KV-3. The content involved includes knowledge base summary descriptions, knowledge functions, knowledge function constraints, and the like. Wherein the summary description of knowledge is a brief description of the background, needs, categories, etc. of knowledge; the knowledge function refers to specific knowledge resources provided by a knowledge base; the knowledge function constraint is a constraint on an index such as the performance of executing the knowledge function. KV-2 can be described using a table with text.

Knowledge-service matrix (KV-3a)1. product definition: KV-3a mainly describes all knowledge-service resource interactions determined by KV-1, integrates knowledge resources according to contents or requirements, and packages the knowledge resources into a series of service forms suitable for various task requirements and knowledge requirements.

2. Description of the product: KV-3a can provide a summary table of knowledge and service interaction determined in KV-1, and shields differences among different platforms, different systems, different languages and different models, so that knowledge resources in the systems and organizations can be better shared and reused, and the purposes of knowledge exchange and sharing, and task cooperation and problem solving based on knowledge are achieved.

v. knowledge-knowledge matrix (KV-3b)1. product definition: the KV-3b can quickly browse the interaction of all the knowledge resources determined in the KV-1, and is mainly described as the way of realizing the same knowledge function together, how a plurality of knowledge resources are interacted cooperatively, including the interaction of the plurality of knowledge resources for completing the same knowledge function and the exchange with external knowledge modules/sub-level knowledge, and also including the interaction of fusing a plurality of knowledge into more upper-level knowledge.

2. Product description: KV-3b mainly describes the interaction process of knowledge resources, namely, the sequence of interaction between knowledge is carried out, and each interaction is triggered by what knowledge event. The knowledge event is a detailed description of interaction behavior between knowledge, and comprises a trigger condition, a related interface, interaction data and the like. The description of knowledge interaction can be divided into a plurality of scenes according to the requirement, and the described knowledge is required to be consistent with KV-3 a. KV-3b is usually represented in a matrix form.

Knowledge functional description (KV-4)1. product definition: KV-4 mainly describes the functions of various knowledge resources and ensures that the connection of knowledge functions is complete (namely, the required inputs of knowledge resources can be completely satisfied).

2. Product description: the functions of various knowledge resources in the architecture are specified by KV-4. There are two basic ways to describe KV-4:

the hierarchical mode of the classified knowledge function describes the decomposition of the knowledge function in a tree structure, and is often adopted when the tasks are cooperative but are mutually related.

And the dataflow graph is used for explaining the knowledge function of connecting the data flow arrow and the data storage library.

KV-5a describes the mapping relation between the knowledge of the required capability and the realization capability, and ensures that the knowledge is matched with the required capability. KV-5a establishes a bridge between the capacity analysis by the capacity product and the knowledge analysis by the knowledge product.

2. Description of the product: KV-5a is used to specify the relationship between the required capability set and the knowledge function set of the architecture description. KV-5a illustrates the support of specific knowledge functions by means of capability elements by means of a mapping matrix. In principle, different KV-5a can be created at each capacity development stage or at different capacity planning stages.

A battle activity tracing knowledge matrix (KV-5b)1. product definition: KV-5b mainly describes the relationship between the knowledge function and the combat activity. The knowledge function is described in KV-4 and the campaign is determined at OV-5a and OV-5 b.

2. Product description: KV-5b is used to specify the relationship between the set of combat activities and the set of knowledge functions described by the architecture. The relationship between the campaign and the knowledge function can also be viewed as a many-to-many mapping, and in general, KV-5b is represented by a matrix of relationships between the knowledge function and the campaign. Another format for KV-5b is a list to reveal the status of execution of each knowledge function.

Knowledge resource flow matrix (KV-6)1. product definition: KV-6 mainly describes the characteristics of knowledge resource streams exchanged between knowledge resources, focusing mainly on the characteristics of knowledge resource streams and the content of knowledge resource streams.

2. Product description: KV-6 specifies the characteristics of knowledge resource streams exchanged between knowledge resources. KV-6 is equivalent to OV-3, and provides detailed information for knowledge resource stream connection. Generally, KV-6 is represented in tabular form.

x, knowledge metrics matrix (KV-7)1. product definition: KV-7 describes the metric index of the knowledge resource.

2. Product description: the KV-7 matrix elaborates qualitative measurement indexes and quantitative measurement indexes of knowledge resources. The model specifies all of the metrology methods employed. The performance parameters include all performance characteristics, and the characteristics are used for developing requirements and establishing specifications. Typically, the KV-7 matrix is a table listing user-defined knowledge metrics associated with time periods.

Description of knowledge evolution (KV-8)1. product definition: KV-8 gives the evolution of the entire life cycle of knowledge resources, describing how they change over time.

2. Description of the product: KV-8 can describe the knowledge ability of different periods of time, such as past, current and future, according to the time progress. The model employs modeling elements similar to KV-1, which can describe the structure of each knowledge resource and the interactions between these knowledge resources. KV-8, when combined with other evolution models, such as CV-2, CV-3, Standard prediction (StdV-2), etc., will provide details of how the capability evolves over time. In this way, KV-8 may also support evolution or transition plans of the architecture.

xi knowledge technology and skill prediction (KV-9)

1. Product definition: KV-9 defines the possible supporting technologies and skills in the current and future knowledge fields. Future knowledge domain support techniques and skills are those that can be reasonably predicted from current techniques and skills, as well as predicted improvements and trends. Given the future-facing nature of KV-9, typical predictions are short-term, medium-term, and long-term, such as 6 months, 12 months, 18 months, and so forth.

2. Product description: KV-9 details the prediction of the knowledge technology development trend. Architects can respectively develop different KV-9 models aiming at knowledge and technology resources. The selection of the time period should be consistent with the architecture transformation plan, i.e., whether to add new capabilities or upgrade existing resources depends on the availability of new technology and related skills. The content of the prediction includes potential impact on the existing architecture and impact on the transitional and target architectures, and the focus of the prediction is on knowledge technology resources relevant to and impacting the objectives of the architecture being developed. Typically, a top level reference model or standard configuration file used by one or more suitable architectures is used at the start. By using these reference models or standard profiles, the architect can select knowledge areas and knowledge techniques that are related to the architecture.

Knowledge rule model (KV-10a)1. product definition: KV-10a mainly describes the structural and behavioral elements of the knowledge model, which are used to determine the functional and non-functional constraints in the architecture implementation. The model describes the knowledge resources, knowledge functions, and constraints on the knowledge base that make up the architecture of the knowledge model. These constraints are presented in textual form and may be functional or structural (i.e., non-functional).

2. Description of the product: the knowledge rules described in KV-10a are mainly used to control, constrain or guide the implementation of the knowledge architecture. Knowledge rules are indications of defining and constraining certain business aspects, the rules being applicable to:

a performer; knowledge resource flow; knowledge function; fourthly, a knowledge base; data elements.

Knowledge state transition description (KV-10b)1. product definition: KV-10b graphically depicts the response of a knowledge resource (or knowledge function) to different events that change its state. These graphs can basically represent the response of various knowledge resources in an activity to a series of knowledge events (taking an action to transition to a new knowledge state, one knowledge event and one action for each transition).

2. KV-10b combines knowledge events with knowledge resource states, describing the transition from one knowledge state to another. KV-10b is based on knowledge state diagrams, and simulates knowledge state changes from the perspective of building knowledge resources, the focus of which is how knowledge resources respond to stimuli (e.g., triggers and knowledge events). Similar to OV-6b, these responses may depend not only on the rule set or usage, but also on the knowledge resource status at the time the instruction was received. Each change in state is referred to as a transition. Each transition specifies a response based on a particular event and the current state.

xv. knowledge event tracing description (KV-10c)1 product definition KV-10c provides timing check of interaction between knowledge resources. The model is used for analyzing knowledge resource events influencing the fighting activity, and each knowledge event tracking chart is attached with a description defining a special idea or situation.

2. KV-10c specifies the order of knowledge resource flow element exchange in a knowledge resource or knowledge base. KV-10c provides a time-series check of knowledge resource streams that participate in exchanges between knowledge resources (external and internal knowledge resources) or knowledge bases. Knowledge event and its time may be marked as the knowledge resource flows from one knowledge resource or knowledge base to another security resource or security port.

6) Security view product

i. In summary, the security view describes the real-time Racing situation perception under Racing countermeasures and the construction of the Racing situation support security system through command control and dynamic adjustment from the perspective of constructing the Racing security system. The secure view includes 14 products: the system comprises a security interface description (SecV-1), a security resource flow description (SecV-2), a security-service matrix (SecV-3a), a security-security matrix (SecV-3b), a security function description (SecV-4), a capability tracing security matrix (SecV-5a), a campaign tracing security matrix (SecV-5b), a security resource flow matrix (SecV-6), a security metric matrix (SecV-7), a security evolution description (SecV-8), a security technology and skill prediction (SecV-9), a security rule model (SecV-10a), a security state transition description (SecV-10b) and a security event tracing description (SecV-10 c).

Description of safety interface (SecV-1)

1. Product definition: SecV-1 describes the interaction between security components and security. SecV-1 combines the tactical architecture and the security architecture model by describing how the security resources are constructed and interact.

2. Description of the product: SecV-1 specifies a secure hierarchical partition, which can be described using a simple treemap. Security and sub-level security can be described simply using SecV-1 and the flow of resources between security determined. The main purpose of the SecV-1 model is to describe the security resource structure, i.e., to determine the main sub-level security, actors and activities (functions) and interactions between them.

Secure resource flow description (SecV-2)

1. Product definition: SecV-2 illustrates the resource flow between security and may list the protocol stack for the connection. The SecV-2 model gives an accurate connection specification between the security domains, either an existing connection specification or a connection specification that is newly created for future connections.

2. Product description: the contents of the SecV-2 model include security, security ports, and security resource flows between ports. The system architect can create a graph for each secure resource flow, and can also use a graph to depict all secure resource flows when conditions allow. Each SecV-2 model can display the following information:

firstly, which security ports are connected; security provided by the security port; security using secure resource flow; defining safe resource flow according to physical connection, logic connection and connection protocol.

Security-service matrix (SecV-3a)

1. Product definition: SecV-3a mainly describes all security-service resource interactions determined by SecV-1, and integrates security resources according to contents or requirements and packages the security resources into a series of service forms which are suitable for various task requirements and security requirements.

2. Product description: SecV-3a can provide a summary table of the security and service interaction determined in SecV-1, and shield the difference between different platforms, different systems, different languages and different models, so that the security resources in the systems and organizations can be better shared and reused, and the purposes of secure exchange and sharing, and task cooperation and problem solving based on security are achieved.

Safety-safety matrix (SecV-3b)

1. Product definition: the SecV-3b can quickly browse the interaction of all the security resources determined in the SecV-1, and is mainly described in the way of realizing the same security function together, how the multiple security resources are interacted cooperatively, including the interaction of the multiple security resources for completing the same security function and the exchange with the external security module/sub-level security, and also including the interaction of combining the multiple security resources into one higher-level security.

2. Product description: SecV-3b mainly describes the interaction process of the security resources, i.e. in what order the interactions between the security are made, each interaction being triggered by what security event. The security event is a detailed description of interaction between security, and comprises a trigger condition, a related interface, interaction data and the like. The description of the security interaction can be divided into multiple scenarios as needed, and the described security needs to be consistent with SecV-3 a. SecV-3b is usually represented in a matrix form.

Description of safety function (SecV-4)

1. Product definition: SecV-4 mainly describes the function of various security resources.

2. Product description: the functions of various security resources in the architecture are specified using SecV-4. There are two basic ways to describe SecV-4: the functional hierarchical classification method describes the decomposition of the security function by a tree structure, and is often adopted when the tasks are collaborative and related to each other. And the data flow graph represents the connection of the safety function by a data flow arrow and a data storage library.

Capability traceability security matrix (SecV-5a)

1. Product definition: SecV-5a describes a mapping between the required capabilities and the security of the implementation capabilities, ensuring that the security matches the required capabilities. SecV-5a bridges the capacity analysis with capacity products and the safety analysis with safety products.

2. Product description: SecV-5a is used to specify the relationship between the required capability set and the security function set described by the architecture. SecV-5a illustrates the support of specific security functions with capability elements by way of a mapping matrix. In principle, different SecV-5a can be created at each capacity development stage or at different capacity planning stages.

Battle activity tracing safety matrix (SecV-5b)

1. Product definition: SecV-5b primarily describes the relationship between security functions and combat activity. The safety function is described in SecV-4, while the campaign is determined at OV-5a and OV-5 b.

2. Product description: SecV-5b is used to specify the relationship between the set of campaign and the set of security functions described by the architecture. The relationship between the campaign and the safety function may also be viewed as a many-to-many mapping, and in general, SecV-5b is represented by a matrix of relationships between the safety function and the campaign. Another format for SecV-5b is a list to reveal the execution status of each security function.

ix, secure resource flow matrix (SecV-6)

1. Product definition: SecV-6 primarily describes the characteristics of the knowledge resource stream exchanged between secure resources, focusing primarily on the characteristics of the secure resource stream and the content of the knowledge resource stream.

2. Product description: SecV-6 specifies the characteristics of the secure resource stream exchanged between the secure resources. SecV-6 is equivalent to OV-3 and provides detailed information for secure resource flow connections. Typically, SecV-6 is represented in tabular form.

x. safety metrics matrix (SecV-7)

1. Product definition: SecV-7 describes a metric for a secure resource.

2. Product description: the SecV-7 matrix elaborates the qualitative and quantitative metrics of the security resource. The model specifies all of the metrology methods employed. The performance parameters include all performance characteristics, and the characteristics are used for developing requirements and establishing specifications. Typically, the SecV-7 matrix is a table listing user-defined time-period-dependent safety metric indicators.

Description of safety evolution (SecV-8)

1. Product definition: SecV-8 gives an evolution of the entire life cycle of the secure resources, describing how they change over time.

2. Product description: SecV-8 can describe the security capabilities of different periods of time, past, current, and future, according to the time schedule. The model may describe the structure of each security resource and the interactions between security resources using a modeling element similar to SecV-1. SecV-8, when combined with other evolution models, such as CV-2, CV-3, Standard prediction (StdV-2), etc., will provide details of how the capability evolves over time. In this manner, SecV-8 may also support evolution or transition plans of the architecture.

xi. prediction of safety techniques and skills (SecV-9)

1. Product definition: SecV-9 defines the current and future safety areas of possible support technologies and skills. Future safety domain support technologies and skills are those that can be reasonably predicted from current technologies and skills, as well as projected improvements and trends. Given the future-oriented nature of SecV-9, typical predictions are classified as short-term, medium-term, and long-term, such as 6 months, 12 months, 18 months, etc.

2. Product description: SecV-9 details the prediction of the trend of the development of security technology. Architects can develop different SecV-9 models for security technology resources separately. The selection of the time period should be consistent with the architecture transformation plan, i.e., whether to add new capabilities or upgrade existing resources depends on the availability of new technology and related skills. The content of the prediction includes the potential impact on the existing architecture and the impact on the transitional and target architectures, and the focus of the prediction is on the security technology resources that are relevant to and impact the objectives of the architecture being developed. Typically, a top level reference model or standard configuration file used by one or more suitable architectures is used at the start. By using these reference models or standard profiles, architects can select security areas and security technologies that are relevant to the architecture.

xiii safety rules model (SecV-10a)

1. Product definition: SecV-10a primarily describes the structural and behavioral elements of the security model to determine functional and non-functional constraints in the architectural implementation. The model describes the constraints on the security resources, security functions, security data, and security ports that make up the architecture of the security model. These constraints are presented in textual form and may be functional or structural (i.e., non-functional).

2. Description of the product: the security rules described by SecV-10a are primarily used to control, constrain, or direct the implementation of the security architecture. Security rules are indications of defining and constraining certain business aspects, which apply to:

a performer; safe resource flow; the safety function; fourthly, a safety port; data elements.

Safe State transition description (SecV-10b)

1. Product definition: SecV-10b graphically depicts the response of a security resource (or security function) to different events that change its state. These graphs can basically represent the response of various security resources in an activity to a series of security events (taking an action to transition to a new security state, one security event and one action for each transition).

2. Product description: SecV-10b combines security events with security resource states and describes the transition from one security state to another. SecV-10b is based on a security state diagram, simulating security state changes from the perspective of building a security resource, with the focus on how the security resource responds to stimuli (e.g., triggers and knowledge events). Like OV-6b, these responses may depend not only on the rule set or usage, but also on the state of the secure resources at the time the instruction is received. Each change in state is referred to as a transition. Each transition specifies a response based on a particular event and the current state.

xv. Security event tracking description (SecV-10c)

1. Product definition: SecV-10c provides a timing check of the interaction between the secure resources. The model is used to analyze security resource events affecting a combat activity, each security event tracking chart should be accompanied by a description defining a particular scenario or situation.

2. Product description: SecV-10c specifies the order of secure resource flow element exchange in a secure resource or secure port environment. SecV-10c provides a timing check of the secure resource flow participating in the exchange between secure resources (external and internal) or secure ports. A security resource stream may be tagged with a security event and its time as it flows from one security resource or security port to another security resource or security port.

7) Service view product

i. To summarize: the service view describes the composition, definition, behavior characteristics, interaction relation and the like of related services of the system by using diagrams, and how the services provide support for the functions of the system. The service view includes 14 products: service interface description (SvcV-1), service resource flow description (SvcV-2), system-service matrix (SvcV-3a), service-service matrix (SvcV-3b), service function description (SvcV-4), capability tracing service matrix (SvcV-5a), campaign tracing service matrix (SvcV-5b), service resource flow matrix (SvcV-6), service metric matrix (SvcV-7), service evolution description (SvcV-8), service technology and skill prediction (SvcV-9), service rule model (SvcV-10a), service state transition description (SvcV-10b) and service event tracing description (SvcV-10 c).

Service interface description (SvcV-1)

1. Product definition: the specific definition of the SvcV-1 specifies the hierarchical division of the service and the relation among the services, can be used for carrying out classification management on the service, provides support for planning a service system, and provides constraint and reference for the development of subsequent SvcV-2, SvcV-3 and SvcV-4.

2. Product description: the SvcV-1 specifies the hierarchy division of the service in detail and can be described by a simple tree diagram. The nodes in the tree graph are services, and the relationships among the nodes are composition relationships. The upper layer service may be an abstract service, representing a class of services, composed of the lower layer services. If necessary, each service can be described in an outline in the SvcV-1, and service functions provided by each service are illustrated, and the description of the service functions is consistent with the related description in the SvcV-2.

Service resource flow description (SvcV-2)

1. Product definition: SvcV-2 illustrates the resource flow between services and lists the protocol stack used for the connection. The model is a detailed description of information such as interfaces, QoS, service functions and function related constraints of the service on the basis of the SvcV-1, and the model and the SvcV-1 form detailed definitions of all services in the system, and provide constraints and references for development of the SvcV-3 and the SvcV-4.

2. Product description: SvcV-2 shall describe the relevant content of the service in detail and shall be consistent with SvcV-1, SvcV-3. The content involved includes service profile descriptions, service interfaces, QoS, service functions, service function constraints, etc. Wherein the service profile is a brief description of the service context, requirements, etc.; the service interface refers to a port for connection between services, and one service may include a plurality of service interfaces; QoS is a description of one or more general non-functional attributes of a service, such as availability, reliability, etc.; the service function refers to specific services provided by the service through the service interface; the service function constraint is a constraint on an index such as service function execution performance. The SvcV-2 can be described using a table with text.

System-service matrix (SvcV-3a)

1. Product definition: SvcV-3a may quickly browse all system-service resource interactions identified in SvcV-1, which may provide a summary of system and service interactions identified in SvcV-1. The SvcV-3a is very useful for the existing system to transform to provide service. The matrix format can be used to quickly evaluate potential commonalities and redundant content. Depending on the context of the determination of the architectural parent, the system-service matrix may be organized in a number of ways to highlight the close connection of the system to service interactions.

2. Product description: the interaction between the SvcV-3a profiling system and the service resources can organize the system-service matrix in a variety of ways depending on the context determined by the purpose of the architecture. SvcV-1 focuses on service resources and their interactions, which are summarized in SvcV-3a and service-service matrix (SvcV-3 b). Generally, the SvcV-3a is represented in a matrix mode, an axis of the matrix represents a system, another axis represents service resources, a cell in the matrix represents an interactive relation existing between the system and the service, and the cell can represent various interactive information types. The interaction of the resources can be represented by different symbols, and can also be represented by the following figures (dots, triangles, squares) which describe different interaction characteristics.

v. service-service matrix (SvcV-3b)

1. Product definition: the interaction of all service resources determined in a plurality of SvcV-1 can be browsed quickly by the SvcV-3b, which is mainly described as the realization of the same system function together, how a plurality of services are interacted in a coordinated manner, including the interaction of the plurality of services for completing the same system function and the exchange with an external system module/subsystem, and also including the interaction of combining the plurality of services into a higher-layer service. The SvcV-3b is not only helpful for determining the service interface, but also gives data transmitted by service interaction for system designers and developers.

2. Product description: SvcV-3b describes the process of service interaction, i.e. in what order the interactions between services are made, each interaction being triggered by what service event. The service event here is a detailed description of the interaction behavior between services, including trigger conditions, related interfaces, interaction data, and the like. The description of service interaction can be divided into multiple scenarios as needed, and the described service needs to be consistent with SvcV-3 a. The SvcV-3b is generally represented in a matrix form.

Service function description (SvcV-4)

1. Product definition: the SvcV-4 model mainly describes personnel and service functions.

2. Description of the product: SvcV-4 specifies the service functions of various resources in the architecture. The correspondence of SvcV-4 to SvcV-1 is a behavior (the correspondence is the same as that of OV-2 for OV-5 b). There are two basic ways to describe SvcV-4: the classified service function hierarchy mode describes the decomposition of service functions in a tree structure, and is often adopted when tasks are collaborative but related to each other. And the dataflow graph is used for explaining the service function connected by the dataflow arrow and the data storage library.

Capability tracing service matrix (SvcV-5a)

1. Product definition: the SvcV-5a model describes the mapping relationship between the required capabilities and the services implementing the capabilities, ensuring that the services match the required capabilities. The SvcV-5a bridges the capacity analysis with the capacity product and the service analysis with the service product, and in particular the model determines how to perform the service with the various available capacity elements.

2. Product description: the SvcV-5a is used to specify the relationship between the required capabilities and the services supported by those capabilities, and the SvcV-5a illustrates the support of a particular service with a capability element by means of a mapping matrix. In principle, different SvcV-5a can be created at each capacity development stage or at different capacity planning stages.

Combat activity tracing service matrix (SvcV-5b)

1. Product definition: the SvcV-5b mainly describes the relationship between the service functions and the campaign. Service functions are described in SvcV-4, while campaign activity is determined at OV-5a and OV-5 b. The SvcV-5b describes the mapping between the service functions and the campaign, thereby determining the conversion of the campaign requirements into meaningful actions to be performed by the service solutions.

2. Product description: the SvcV-5b is used to specify the relationship between the set of operational activities and the set of service functions described by the architecture. The relationship between the campaign and the service functions may also be viewed as a many-to-many mapping. Typically, SvcV-5b is represented by a matrix of relationships between service functions and campaign activity. Another format for SvcV-5b is a list to reveal the execution status of each function.

ix, service resource flow matrix (SvcV-6)

1. Product definition: SvcV-6 mainly describes the characteristics of the service resource flow exchanged between services, focusing on resources across service boundaries.

2. Description of the product: SvcV-6 details the characteristics of the service resource flow exchanged between services. The SvcV-6 is equivalent to the OV-3 and provides detailed information for service connection, and the services realize the resource flow exchange determined in the OV-3. Whether the solution for resource stream exchange is automatic or non-automatic (e.g., verbal), it will be described in detail. Generally, SvcV-6 is represented in tabular form.

x. service metrics matrix (SvcV-7)

1. Product definition: SvcV-7 describes a metric index of the service resource. SvcV-7 extends the information described in SvcV-1 and characterizes the resources in the model.

2. Description of the product: the SvcV-7 matrix elaborates the qualitative and quantitative metrics of the service resource. The model specifies all of the metrology methods employed. The performance parameters include all performance characteristics, and the characteristics are used for developing requirements and establishing specifications. Typically, the SvcV-7 matrix is a table listing user-defined metrics associated with time periods.

xi. service evolution description (SvcV-8)

1. Product definition: SvcV-8 gives an evolution of the entire life cycle of the service resources, describing how they change over time.

2. Product description: the SvcV-8 can describe service capabilities of different periods of time, such as past, current and future, according to the time schedule. The model employs a modeling element similar to SvcV-1 that can describe the structure of each resource and the interactions between those resources. SvcV-8, when combined with other evolution models, such as CV-2, CV-3, Standard prediction (StdV-2), etc., will provide details of how the capability evolves over time. In this way, SvcV-8 may also support an evolution plan or a transition plan of the architecture.

Service technology and skill prediction (SvcV-9)

1. Product definition: SvcV-9 defines the possible support technologies and skills for current and future services. Future service support technologies and skills are those that can be reasonably predicted from current technologies and skills, as well as projected improvements and trends. In addition to providing a listing of trends, capabilities, and services, SvcV-9 can also provide an assessment of the impact of these items on the architecture. Given the future-facing nature of SvcV-9, typical predictions are short-term, medium-term, and long-term, such as 6 months, 12 months, 18 months, etc.

2. Product description: SvcV-9 details the prediction of the service technology development trend. Architects can develop different SvcV-9 models separately for service technology resources. The selection of the time period should be consistent with the architecture transformation plan, i.e., whether to add new capabilities or upgrade existing resources depends on the availability of new technology and related skills. The content of the predictions includes the potential impact on the existing architecture and the impact on the transitional and target architectures, and the focus of the predictions is on the service technology resources that are relevant to and impact the objectives of the architecture being developed. Typically, a top level reference model or standard configuration file used by one or more suitable architectures is used at the start. By using these reference models or standard profiles, architects can select service areas and services that are related to the architecture.

Service rule model (SvcV-10a)

1. Product definition: the SvcV-10a explicitly specifies functional and non-functional constraints on the implementation of the service architecture, i.e. structural elements and behavioral elements of the service view.

2. Description of the product: the service rules described by SvcV-10a are primarily used to control, constrain, or direct the architecture implementation. Service rules are indications that define and constrain certain business aspects, and these rules apply to:

a performer; servicing the resource stream; thirdly, service function; fourthly, a system port; data elements.

Service state transition description (SvcV-10b)

1. Product definition: the SvcV-10b graphically depicts the response of a service resource (or service function) to different events that change its state. These graphs can basically represent the response of various service resources in an activity to a series of service events (taking an action to transition to a new service state, one event and one action for each transition).

2. Product description: SvcV-10b combines service events with service resource states and describes the transition from one service state to another. The SvcV-10b simulates service state changes from the point of view of building service resources based on a service state diagram, the focus of which is how the service resources respond to stimuli (e.g., triggers and service events). Similar to OV-6b, these responses may depend not only on the rule set or usage, but also on the service resource status at the time the instruction was received.

xv. service event tracing description (SvcV-10c)

1. Product definition: the SvcV-10c provides for the detection of interactions between service function resources in time sequence. Each service event tracing map needs to be accompanied by a description of a particular scenario or situation.

2. Product description: the SvcV-10c specifies the order of service resource flow element exchange in a service resource or service port environment. The components of the SvcV-10c include functional resource or service ports, unique actors, and ports affiliated with the lifeline. The SvcV-10c provides a timing check of the flow of service resources that participate in the exchange between service resources (external and internal service resources) or service ports. Service events and their service times may be marked as a service resource stream flows from one service resource or service port to another service resource or service port.

8) System view product

i. To summarize: a system view product is a series of graphical representations or textual descriptions that provide (or support) a description or an interconnect relational specification of the system for each interested party that is focused on a particular physical system at a particular physical (geographic) location. The system view includes 14 products: the system comprises a system interface description (SV-1), a system resource flow description (SV-2), a system-system matrix (SV-3), a system function description (SV-4), a campaign activity and system function traceability matrix (SV-5a), a campaign activity and system traceability matrix (SV-5b), a system resource flow matrix (SV-6), a system metric matrix (SV-7), a system evolution description (SV-8), a system technology and skill prediction (SV-9), a system rule model (SV-10a), a system state transition description (SV-10b) and a system event tracking description (SV-10 c).

System interface description (SV-1)

1. Product definition: SV-1 describes the system composition and the interaction between systems. SV-1 combines the combat architecture model and the system architecture model by describing how system resources are constructed and interact to implement the logical architecture specified in OV-2.

2. Product description: SV-1 describes the system nodes that support completion of the combat activity by the combat nodes in OV-2, the systems that these system nodes comprise, and describes the flow of resources between them. A system node may be a logical classification of systems with similar capabilities or functions, or may be an entity with actual physical meaning. An integrated system, a system population, an application specific system, or a subsystem may be considered a system, if desired. If necessary, the system functions corresponding to each system may be given in SV-1, and these system functions should be identical to those in SV-4.

System resource flow description (SV-2)

1. Product definition: SV-2 is a protocol stack that describes the flow of system resources between systems and may list the connections.

2. Description of the product: the contents of the SV-2 model include the system, system ports, and resource flows between ports. The system architect may create a graph for each resource flow, and may also use a graph to depict all system resource flows when conditions allow. Each SV-2 model may display the following information:

which system ports are connected; the system to which the system port belongs; defining system resource flow by physical connectivity, logic connectivity and connection adopted protocol.

System-system matrix (SV-3)

1. Product definition: SV-3 is a product that describes the interface relationships and interface parameters in SV-2 a.

2. Product description: SV-3 describes the parameters of all interfaces given in SV-2 a. The simple representation of SV-3 can be used to represent the relationship of the system by using a matrix similar to the type "N2". In the matrix, the systems are respectively listed in the rows and the columns of the matrix, each cell represents an interface between a pair of systems, and whether the interfaces exist between the pair of systems can be determined through the identification of the cell. In SV-3, parameters of the interface can also be described by labeling the cells with different colors or symbols (i.e., icons) and adding corresponding written descriptions. These interface parameters may include: status, such as retirement, active, under-development, etc.; for purposes such as for command, intelligence, etc.; security level, such as national military standards, communication protocols, etc.; standards, such as national military standards, communication protocols, and the like; a critical interface.

v. description of System function (SV-4)

1. Product definition: SV-4 is a product that describes the system function and its data flow relationships.

2. Product description: SV-4 describes the system composition from the perspective of system function and data flow, with the system function in SV-4 being performed by the system in SV-1. The product can describe the structure of system functions by using a layered structure chart, and can also describe data flow among the system functions and corresponding data exchange by using a data flow chart form, thereby providing a foundation for the design and development of the system. SV-4 is the corresponding product of OV-5 in SV, and the decomposition of the system function in SV-4 should be determined according to the needs and the architectural purpose, and can be service-wide (without looking into the correspondence of the system and the function) or the function of a certain specific system. The description in SV-4 should not only consider the functions of a certain system, but also consider some general functions, such as human-machine interface functions. Furthermore, when describing SV-4 as a data stream, it is not limited to functions and data streams within the internal domain of the architecture, and external system data streams/receivers associated with the architecture should also be considered.

Operational activity and system function tracing matrix (SV-5a)

1. Product definition: SV-5a describes the product in which the system functions support the relationships for the campaign.

2. Product description: SV-5a is the connecting bridge between OV and SV, which establishes the correspondence between the campaign and system functions in the architecture. SV-5a describes the support of the system functions for the campaign in the form of a table, the system functions and the campaign are respectively provided as columns and rows of the table, each cell can be identified by a symbol, and the identified cells indicate that a certain system function can provide support for a certain campaign.

Action and System traceability matrix (SV-5b)

1. Product definition: SV-5b describes the association between the system identified in SV-1 and the combat activity identified in OV-5 a.

2. Product description: SV-5b is a relationship specification applicable to a variety of relationships between a series of combat activities and a series of system functions in an architectural description. The model establishes a retrospective relationship between functional system requirements and user requirements, and an SV-5b matrix is expressed as a relationship matrix between a system and combat activities.

System resource flow matrix (SV-6)

1. Product definition: SV-6 is a feature that describes the system resource flow exchanged between systems, with emphasis on resources across system boundaries.

2. Product description: SV-6 determines the characteristics of the resource flow exchanged between the systems, with the emphasis on the information exchange and data exchange automatically performed by the systems. SV-6, peer to peer with OV-3, provides detailed information on the system interconnections that implement the resource flow exchange determined by OV-3, as well as non-automated resource flow exchanges, such as verbal commands. The focus of SV-6 is that system resource flow exchange is affected by those factors that determine system details, including details of periodicity, scheduling, throughput, information assurance, and resource exchange security features. In addition, the format, media type, accuracy, metric unit, system data standard, etc. of the system resource stream elements are also described in the matrix.

System metric matrix (SV-7)

1. Product definition: SV-7 is a descriptive system metric. The system metric matrix extends the information given in the system interface description, describing the resource characteristics in SV-1.

2. Description of the product: the SV-7 matrix qualitatively and quantitatively describes the system metric, giving all system metrics. The metrics are selected for use by the end user population and are described by the architect. The main function of SV-7 is to investigate which metrics are most important for fulfilling the mission undertaken and how to meet these performance parameters. The table is a typical format of the SV-7 model, in which the user-defined metric indices and associated time periods are mainly listed.

System evolution description (SV-8)

1. Product definition: SV-8 describes images of the entire life cycle of the system, describes how they are changing over time, and also describes the correspondence of system structure to time progression.

2. Product description: SV-8 in combination with other evolution models can provide multiple definitions, can predict how system capability evolves over time, and support evolution plans or transition plans for architecture making. SV-8 may describe historical capabilities (i.e., legacy capabilities) in terms of time-schedules, may describe current capabilities and future capabilities. SV-8 uses the same modeling elements as SV-1 to illustrate the structure of each resource, describing the interactions that occur inside the resource.

Systematic technical and skill prediction (SV-9)

1. Product definition: SV-9 is a product that predicts the new technology available in a given time.

2. Product description: the SV-9 model summarizes the development trend of the prediction system technology. The architect can generate predictive models of system technology and skills, respectively. The selection of a particular time period should be coordinated with the architecture transformation plan. That is, the embedding of new capabilities and the upgrading of existing resources is dependent on, or facilitated by, the availability of new and related technologies. The predicted content includes potential impact on existing architectures, as well as impact on transitional and target architecture development. The focus of forecasting is in the field of system technology related to the purpose of architecture development, where forecasting also determines the impact on the architecture being developed.

xi. System rules model (SV-10a)

1. Product definition: SV-10a is a product that describes constraints or operating rules that have an impact on the system and system function implementation.

2. Product description: SV-10a depicts constraints that constrain the implementation of a system or system function, as well as the rules of operation of the system. The rules may be textual descriptions that define or constrain certain behaviors throughout the information system domain, or may be a series of conditional statements. The system can be run under specific conditions according to the rules given in the product. Such rules may be represented in text, for example, in the form of "if (certain conditions) exist, (certain events) occur, (certain system functions are performed)".

Description of System State transition (SV-10b)

1. Product definition: SV-10b is a product that describes the processes that the system runs and events that affect these processes.

2. Product description: SV-10b describes the response of a system (or system function) to different events that change its state, depicting the events that cause a change in the state of the system or system function. It undergoes a system state change called a transition, each of which specifies an event and an action. The system state and its associated actions determine the response of a system or system function to an event. When an event occurs, the next state of the system or system function depends on the existing state, event, and rule or condition.

Description of System event tracking (SV-10c)

1. Product definition: SV-10c is a product that describes the timing of the data exchange of the system.

2. Product description: SV-10c describes the examination of the chronological order of the exchange of system data between all involved systems and system functions in one particular scenario. The corresponding written description should be used to describe the specified ideas or situations. By tracking specified events, the order of data exchange between systems in a given session can be derived. SV-10c, in combination with SV-10b, can display the dynamic characteristics of the system. SV-10c may describe the order of data exchange between systems or between system functions, but they should be separately shown. In describing data exchanged between systems or system functions, the flow of data should be given. SV-10c is generally described by a sequence diagram of UML, wherein a lane line represents a system in SV-1 or a system function in SV-4, an event is consistent with an event in SV-10b, and a formula for calculating the occurrence time of the event can be given according to requirements when describing the sequence of the event.

9) Data and information view product

i. To summarize: the data and information view describes the requirements of the combat and business information and the management rules in the combat and business information from the perspective of data and information application requirements, and defines the attributes, syntax and semantics of the information/data of the combat and business requirements so as to uniformly describe the information requirements and the flow rules in the business process. The data and information view includes 3 products: a conceptual data model (DIV-1), a logical data model (DIV-2), and a physical data model (DIV-3).

Conceptual data model (DIV-1)

1. Product definition: DIV-1 describes the high level information concept of the combat architecture. The model is often used to write business information requirements for an architecture and rules for structuring business processes. DIV-1 describes information related to architectural information, including information items, attributes or features and their internal relationships.

2. Product description: DIV-1 describes the structuring of architectural information types and structured business process rules, whose architectural elements include descriptions of information entities and relationship types. DIV-1 is intended to describe information or data that is important to the business, such as information and data referenced in treaties, standard combat procedures (SOP).

Logical data model (DIV-2)

1. Product definition: DIV-2 may analyze architectural data definitions without regard to implementation or product details.

2. Product description: DIV-2 provides a common data definition dictionary to represent models consistently regardless of where logical layer data elements are included in the description. The model directly reflects the pattern or theory of mapping from the conceptual data model to the logical data model. Generally, DIV-2 is described in terms of an entity relationship graph.

Physical data model (DIV-3)

1. Product definition: DIV-3 defines data structures for different kinds of system data, service data, security data, etc. employed in the architectural description. The model is used to describe how the information represented in the logical data model is implemented.

2. Product description: DIV-3 is an implementation-oriented model. The model is used to describe how the information requirements represented in DIV-2 are implemented in a system view, a service view, a security view, and a knowledge view. The entities of DIV-3 represent system resource streams, system resource elements, service resource streams, service resource elements, security resource streams, security resource elements, knowledge resource streams, knowledge resource elements, trigger events, and elements. The detailed description of the entity representation is as follows: system resource flow in the system function description (SV-4). ② system resource elements determined in the system resource flow matrix (SV-6) and system event-tracking description (SV-10 c). ③ service resource flow in service function description (SvcV-4). Service resource elements determined in the service resource flow matrix (SvcV-6) and the service event-trace description (SvcV-10 c). ③ secure resource flow in the secure function description (SecV-4). The security resource elements determined in the security resource flow matrix (SecV-6) and the security event-trace description (SecV-10 c). And fifthly, describing the knowledge resource flow in the knowledge function (KV-4). Sixthly, determining knowledge resource elements in the knowledge resource flow matrix (KV-6) and the knowledge event-tracking description (KV-10 c). Seventhly, trigger events in the description of system state transition description (SV-10b), service state transition (SV-10c), safety state transition (SecV-10c) and knowledge state transition (SV-10c) are described. Eighthly, events in a system event-tracking description (SV-10c), a service event-tracking description (SvcV-10c), a security event-tracking description (SecV-10c) and a knowledge event-tracking description (KV-10 c). Ninthly, elements required by the standard in the standard profile or standard prediction.

10) Standard view product

i. To summarize: the standard view describes relevant standard specifications such as battles, daily businesses, technologies, industrial standards, engineering implementation conventions, rule criteria and the like and development concepts thereof from the perspective of a management, design and development system. The standard view includes 2 products: standard system (StdV-1) and Standard prediction (StdV-2).

Standard System (StdV-1)

1. Product definition: StdV-1 defines the various technical, operational and daily business standards to be followed, as well as the relevant guidelines, policy provisions, etc., for managing, designing and developing various types of systems. StdV-1 can be used to guide the technical implementation of the system and also to check the standard compliance of the system.

2. Product description: StdV-1 is comprised of a series of standards that govern the design and implementation of an architecture, including the standards by which systems, services, system hardware and software, communication protocols, and data formats may be employed. The standards given in StdV-1 shall have an association with the information exchange, campaign flow, system function, system data, hardware and software, communication protocol, service QoS, service composition scheme in OV-3, OV-5c, OV-6a, OV-7, SV-1, SV-2, SV-4, SV-6, SV-7, SV-11, SvcV-2, SvcV-4 products, i.e. the elements in these products shall follow the standards listed in StdV-1. tdV-1 requires the identification and listing of existing standard specifications associated with architectural items, as well as the listing of lacking guidance material. Similar to other products, the standard system in StdV-1 also specifies the corresponding time frame (as existing, pending or ongoing), which helps to differentiate new technologies. If there are multiple newborn standards in a certain time frame, further description in StdV-2 is needed. StdV-1 can either simply list the standards or tabulate the applicable range and applicable time of the standards.

Standard prediction (StdV-2)

1. Product definition: StdV-2 describes the desired changes to the technology-related standards, operational standards and business standards, etc. listed in StdV-1, and is a detailed description of the emerging standards related to system, operational and daily business activities. The time period predicted for standard evolution is to be associated with the time period predicted by the technology of SV-9, system evolution in SV-8. The predictions of the criteria are also tailored to focus on areas relevant to the purpose of the architectural project, identifying significant issues that affect the architecture. One of the primary purposes of StdV-2 is to identify the standards of key technology and their vulnerabilities, and the future impact of these technical standards on project development and system maintenance.

2. Product description: StdV-2 lists the emerging standards and revised standards associated with solutions across architectural projects, predicts the feasibility of the emerging standards, and correlates the prediction with the elements and time periods of SV-8 and SV-9 products. The selected time period (e.g., 6 months and 12 months) and the tracked standards are coordinated with the architecture migration plan (supported by SV-8), i.e., the generation of new capabilities and the upgrade of existing systems is dependent on or driven by the feasibility of the new standards. The prediction defines the underlying criteria and thus affects the current architecture as well as the implementation of the target architecture and its migration.

11) Equipment view product

i. To summarize: the equipment view mainly describes equipment classification, indexes, systems, development routes and the like required in the knowledge view, the safety view and the service view from the perspective of construction and management. The equipment view includes 4 products: an equipment structure description (EV-1), an equipment-to-capability mapping (EV-2), an equipment-to-combat activity mapping (EV-3), an equipment tactical technical indicator description (EV-4), and an equipment development description (EV-5).

Equipment structural description (EV-1)

1. Product definition: EV-1 describes a classification structure of electronic information equipment, and can be classified according to functions, forms, technical systems and the like of the equipment.

2. Product description: EV-1 defines the hierarchical division of equipment and the relation among the equipment in detail, can be used for carrying out classification management on the equipment, and provides support for planning an equipment system. The EV-1 model determines the composition structure of the electronic information equipment, and the development of the EV-1 is in accordance with the electronic information equipment system, can cover all the equipment types and important subclasses to be adopted, and can reflect the functions and forms of the equipment.

Association of Equipment with capabilities (EV-2)

1. Product definition: EV-2 describes the support of electronic information equipment on military information system capability requirements.

2. Product description: the EV-2 model needs to be capable of clearly describing the supporting relation of the equipment to the capacity requirement and ensuring that the equipment is matched with the required capacity. EV-2 is a bridge between the capability architecture and the equipment architecture. EV-2 illustrates the use of capability elements to support specific equipment by way of a mapping matrix. In principle, different EV-2's may be created at each capacity development stage or at different capacity planning stages. Mapping relationship between equipment and combat activity (EV-3)

1. Product definition: EV-3 describes support for performing a combat activity by electronic information equipment.

2. Product description: EV-3 is to clearly describe the supporting relationship of equipment to the combat activity, and the model is a bridge of OV and EV, and establishes the corresponding relationship between the combat activity and the electronic information equipment in the system structure. EV-3 describes equipment support for a combat activity in the form of a table, with equipment and combat activity being identified as columns and rows of the table, respectively, with symbols identifying each cell, with the identified cells indicating that the equipment can provide support for the combat activity.

Equipment tactical technical indicator description (EV-4), 1. product definition: EV-4 describes the performance and tactical technical indicators of a particular electronic information equipment. 2. Product description: the EV-4 description should be quantified to reflect the performance and tactical technical indicators of all equipment.

Equipment development description (EV-5)1. product definition: EV-5 describes the planning and planning of electronic information equipment construction in a certain field. 2. Product description: the description of EV-5 should clearly depict the development plan of the equipment, consistent with the weapons equipment development strategy and construction plan.

Although the preferred embodiments of the present invention have been disclosed for illustrative purposes, those skilled in the art will appreciate that various modifications, additions and substitutions are possible, and the scope of the invention should not be limited to the embodiments described above.

Claims

1. An electronic information system, comprising:

the operation view is used for developing operation concepts, describing operation resource streams, operating resource stream matrixes, organization relations, operation activity decomposition trees, operation activity models, operation rule models, operation state transition descriptions and operation event tracking descriptions from the aspect of executing operation tasks, and displaying the operation view;

the capability view is used for analyzing and linking with system requirements, carrying out development capability conception and capability classification from the perspective of integrated combined combat task support and combat guarantee capability requirements, acquiring capability stage relationship, capability membership relationship, mapping relationship between capability and organization development and mapping relationship between capability and combat activities, and displaying the capability view;

the service view is used for describing service composition, functions and interrelations of the supporting combat service from the aspect of supporting service interoperation among cross-system, cross-department, cross-army and even cross-field, carrying out development service interface description, service resource flow description, system-service matrix, service function description, capability tracing service matrix, combat activity tracing service matrix, service resource flow matrix, service measurement matrix, service evolution description, service technology and skill prediction, service rule model, service state transition description and service event tracing description, and carrying out service view display;

the system view is used for following the capacity requirement in the capacity view, the fighting intention in the fighting view and the service function in the service view, describing the component elements and the deployment relationship of an information system, developing system interface description, system resource flow description, a system-system matrix, system function description, fighting activity and system function tracing matrix, fighting activity and system tracing matrix, system resource flow matrix, system measurement matrix, system evolution description, system technology and skill prediction, system rule model, system state transition description and system event tracing description, and displaying the system view;

the knowledge view is used for supporting the realization of integration and sharing of knowledge resources as required from the perspective of integration, processing and application of the knowledge resources in an organization, describing a knowledge operation mechanism based on representation, generation, organization, fusion, reasoning and collaborative operation of knowledge, and requiring the development of knowledge interface description, knowledge resource flow description, knowledge-service matrix, knowledge-knowledge matrix, knowledge function description, capability retroactive knowledge matrix, combat activity retroactive knowledge matrix, knowledge resource flow matrix, knowledge measurement matrix, knowledge evolution description, knowledge technology and skill prediction, knowledge rule model, knowledge state transition description and knowledge event tracking description.

2. The system of claim 1, further comprising:

and the standard view is used for describing relevant combat, daily business, technology, industrial standard, engineering implementation convention, rule criterion and development conception from the perspective of a management, design and development system, developing a standard configuration file and a standard forecast, and displaying the standard view.

3. The system of claim 1 or 2, further comprising:

and the equipment view is used for describing equipment classification, indexes, systems and development routes required in the system view from the construction and management perspective, and requiring development of equipment structure description, equipment and capability corresponding relation, equipment and battle mission corresponding relation, equipment tactical technical index description and equipment development.

4. The system of claim 1 or 2, further comprising:

and the safety view is used for constructing a unified Raspy safety system, developing safety interface description, safety resource flow description, safety-service matrix, safety-safety matrix, safety function description, capability tracing safety matrix, combat activity tracing safety matrix, safety resource flow matrix, safety measurement matrix, safety evolution description, safety technology and skill prediction, safety rule model, safety state transition description and safety event tracing description for the confidentiality, integrity, availability, traceability and anti-repudiation of data in the processes of storage, transmission, processing and release, and carrying out safety view display on attack, prevention, detection, control, management and evaluation of information safety environment.

5. The system of claim 1 or 2, further comprising:

and the data and information view is used for describing the requirements of the operational and business information and the management rules therein, defining the attributes, syntax and semantics of the information/data of the system operational and business requirements, uniformly describing the information requirements and flow rules in the business process, and requiring the development of a conceptual data model, a logical data model, a physical data model and an information view.

6. The system of claim 1 or 2, further comprising:

and the intelligent view is used for developing intelligent interface description, intelligent resource flow matrix, intelligent activity decomposition tree, intelligent activity model, intelligent rule model, intelligent state transition description and intelligent event tracking description from the perspective of intelligent application requirements in the operation process, and displaying the intelligent view.