CN111142845B - Model-based task system demand development method - Google Patents
Model-based task system demand development method Download PDFInfo
- Publication number
- CN111142845B CN111142845B CN201911309480.9A CN201911309480A CN111142845B CN 111142845 B CN111142845 B CN 111142845B CN 201911309480 A CN201911309480 A CN 201911309480A CN 111142845 B CN111142845 B CN 111142845B
- Authority
- CN
- China
- Prior art keywords
- task
- model
- requirement
- requirements
- package
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/10—Requirements analysis; Specification techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/35—Creation or generation of source code model driven
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention belongs to a task system demand development method based on a model. According to the method, a top-down requirement analysis and verification flow of the task system is established, and a SysML is adopted to accurately describe and establish a requirement model, so that a complex system-oriented requirement development method based on the model is formed, analysis on the operation scene, system capacity, function and interface requirements of the complex task system and requirement tracing and verification are realized through decomposition and model visual expression of a task system requirement development process, and scheme design and integrated verification of the task system can be better supported.
Description
Technical Field
The invention relates to a requirement development method for a complex system, in particular to a task system requirement development method based on a model.
Background
Traditional task system demand development is mainly based on structured decomposition of documents. The structured decomposition of the user requirements is generally suitable for more mature equipment or improved equipment requirement analysis, the type of equipment is provided with clear battle technical index requirements, and the structured decomposition is suitable for use. However, with the systematic development of the existing weaponry, the task system is more and more complex, and the problems of unclear use concept, incomplete system capability, incomplete index system, unclear requirement and the like exist, so a task-driven top-down system requirement development method should be adopted. Meanwhile, the development based on the requirement of the document is mainly described in a word, and the word description has the greatest defect of ambiguity. Different requirements developers may have different understandings of the same function or behavior, with consequent inconsistency of requirements. Therefore, a new task system requirement development method needs to be developed.
Disclosure of Invention
Objects of the invention
The invention aims to provide a task system requirement development method based on a model, which can not only standardize the requirement development and verification process of a complex system with uncertain requirements, but also provide a modeling description method, thereby supporting the requirement demonstration process of a task system.
(II) embodiment of the invention
A task system requirement development method based on a model comprises the following steps: the method comprises nine key steps:
1. importing user demand capacity;
inputting the top-level combat demand into a modeling system as a modeling initial point and a subsequent modeling reference;
2. identifying a system operating environment;
the context of the task system is identified, including superior, passengers, friends, targets and the like, and the command relationship of the passengers, so that the understanding of the operating environment of the task system is facilitated; defining a typical battle scene as a model basis of subsequent demand analysis activities;
3. decomposing and modeling a task;
performing task decomposition on a typical battle scene to form stage tasks, and performing any flow design so as to identify detailed use cases;
4. capacity requirements and stage task tracking;
establishing a retrospective relation between the input combat demand and the stage task to ensure that the combat demand is completely expressed in the scenario;
5. designing and modeling stage tasks;
according to the decomposed stage tasks, parallelly or iteratively expanding service case analysis work, refining information flow and control flow relation among subtasks, and simultaneously facilitating contraction of system analysis boundaries, focusing on a task system from a large system as a basis for analyzing a use scene of the task system;
6. deducing task requirements;
analyzing a use scene of the task system based on a service case of the task system, refining the operation and expectation of a participant on the system, and simultaneously deducing corresponding task requirements;
7. deducing a system case;
clustering the functions of a task system from task requirements, and abstracting a relatively independent system case;
8. exporting high-level and system requirements;
according to the system use cases and the task requirements, high-level system use cases are derived;
9. forming a demand model;
and constructing a demand model organization structure of the task system, wherein the demand model organization structure comprises a task and function model, a design model and a modeling process model.
Further, the step one further comprises:
(1) decomposing the fighting requirements of the top layer by layer, and importing the fighting requirements into a modeling system to form a requirement tree structure;
(2) and displaying the top-level combat demand in a demand modeling environment in a demand table view mode by using the demand tree.
Further, the second step further comprises:
step2.1 recognition of System context
(1) Describing system context by a module definition diagram, representing a task system, a platform at the upper level, a superior level and a friend system by modules, representing the power of both passengers and friends and enemies by participants, and representing the relationships among the modules and between the modules and the participants by incidence relationship, directional combination relationship, aggregation relationship and the like;
(2) describing seat configuration and command relationship of the passengers identified in the last step by using a packet diagram, defining different types of passengers by using different packets, representing the relationship between the passengers by using a dependency relationship, and representing a command relationship type by using a constructor;
step2.2 configuration system task scene
(1) Defining a battle task scene by using a case in the use case diagram, and marking the case as a 'task scene' by using a constructor;
(2) expressing the forces of the two parties of red and blue related to the thought by the participants, and using a structural mark;
(3) representing relationships between participants and task scenarios in associative relationships
(4) The description of the scene is added using a requirements element, which is marked as a "scene description" using a constructor.
Further, the third step further includes:
(1) adding an activity diagram for a task scene, describing a task flow and showing to a stage task level;
(2) adding an activity pin on the activity in the activity diagram represents the enemy and my strength involved in the task at this stage;
(3) exposing each stage task in the form of a use case by using the use case diagram;
(4) the relationship between the task use cases and the stage task use cases is expressed by a constructor 'include';
(5) and taking the equipment system where the task system is located as the system boundary of the use case diagram, and delimiting the scope of the task system.
Further, the fourth step further includes:
(1) displaying the combat demand and stage tasks decomposed in the third step by adopting a matrix view;
(2) adding a relation 'trace' for the combat demand and the stage task with the retrospective relation through a matrix view;
(3) a requirement graph can be separately created for each stage task, and the relationship between the requirement graph and all the fighting requirements related to the requirement graph is displayed;
further, the fifth step further includes:
(1) a 'stage task' use case which is solved by the activity diagram refining step;
(2) describing information flow among the subtasks in the stage through activities, object nodes, activity pins and object flow;
(3) describing the control flow among the phase subtasks through activities, control flows and the like;
(4) each subtask is presented by using an example graph, and the relationship between the phase task and the subtask case is expressed by a constructor 'include';
(5) in the use case diagram, the use cases completed by the task system are identified by the system boundary.
Further, the sixth step further includes:
(1) within the system boundary of the task system, a sequence diagram is used for refining a 'stage task' use case;
(2) the life line and the system boundary in the timing diagram express various users of the integrated task system;
(3) the operation of each user under the task at the stage is described by the sequence of 'message', 'event', 'interactive operator', 'separator', 'partition line', etc.;
(4) the functions of the system under the task at this stage are described by the sequence of 'message', 'event', 'interactive operator', 'separator' and 'partition line';
(5) developing user requirements by using at least one requirement element as a single 'message' or 'event' for requirement description;
(6) uniformly storing user demand elements in a model tree, and displaying the user demand elements in a demand modeling environment through a table view;
(7) the identified itemized requirements serve as derived user requirements for review.
Further, the seventh step further comprises:
(1) clustering functions of the system obtained by analyzing the task scene sequence diagram, and abstracting a system case;
(2) drawing a usage diagram, and expressing the relationship between the system usage and external participants, the system usage and functions. Further, the seventh step further includes:
(1) identifying functions in the system use case as system requirements;
(2) establishing a tracking relation of high-level system requirements to task requirements, wherein each task requirement is covered by at least one high-level system requirement, establishing the high-level system requirements by constructing a mapping matrix, and the tracking relation of the task requirements meets one task requirement and is covered by at least one high-level system requirement;
(3) and exporting and managing high-level system requirements.
Further, in the ninth step, the task and function model includes a participant package, a requirement analysis package and a function analysis package 3, the participant package stores all participant models of the task, the requirement analysis package stores a task system requirement model, and the function analysis package stores a task system function model;
the design model comprises a design comprehensive package and an interface package 2, the design comprehensive package stores a system architecture and software configuration item design model, and the interface package stores an internal interface model and an external interface model of the system; the design comprehensive package is divided into three layers: the first layer structure describes basic description and operation flow of operation task through use diagram and activity diagram; the second layer structure describes the decomposition description of the tasks of each stage, which is presented by using an illustration. And the retrospective relationship between the decomposed stage tasks and the combat requirements is presented on the layer through a matrix view; the third layer structure describes the task flow decomposition and operational interaction of single-phase tasks, presented by use of illustrations, activity diagrams, and timing diagrams. And the user requirements are refined and stored as derived requirements. The interface package mainly comprises an information interface and a man-machine interface which are decomposed from an internal block diagram and a block diagram;
the modeling process model comprises a requirement modeling process model and a navigation package, a task system general configuration package, a SysML package and a Harmony SE package 4, wherein the requirement modeling process model and the navigation package are used for displaying the modeling overall process model, the task system general configuration package stores a task system reusable configuration file, and the SysML package and the Harmony SE package store a modeling basic configuration file.
Effects of the invention
By decomposing the task system requirement development process and visually expressing the model, the analysis of the operation scene, the system capability, the function and the interface requirement of the complex task system and the requirement tracing and verification are realized, and the scheme design and the integrated verification of the task system can be better supported.
Drawings
FIG. 1 is a schematic flow diagram of the process of the present invention;
FIG. 2 is a schematic diagram of a demand model organization structure of a task system.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings.
Referring to fig. 1, the method for developing task system requirements based on models provided by the present invention includes the following steps:
1. user demand capability import
And inputting the battle requirements of the top layer into a modeling system to serve as a modeling starting point and a subsequent modeling reference. Specifically, the method comprises the following steps:
(3) and decomposing the battle requirements on the top layer by layer, and importing the battle requirements into a modeling system to form a requirement tree structure.
(4) In a requirement modeling environment, a requirement tree shows the top-level battle requirement in a requirement Table View (Requirements Table View) mode, so that the use and reference of a subsequent model are facilitated.
2. Identifying system operating environments
And identifying the context of the task system, including upper systems, passengers, system peripheral neighbors, superior levels, targets and the like, and command relations of the passengers, and helping to understand the operating environment of the task system. And (4) defining a fighting scenario from the view angle of the large system to which the task system belongs, and using the fighting scenario as a model foundation of subsequent demand analysis activities.
Step2.1 recognition of System context
The context of the task system is identified, including superior, passengers, friends, targets and the like, and the command relationship of the passengers, so that the understanding of the operating environment of the task system is facilitated, and specifically:
(1) describing system context by a module definition diagram (BDD), representing a task system, a platform at the upper level, an upper level and a friend system by modules, representing the forces of passengers, enemies and my parties by participants, and representing the relationships among the modules and between the modules and the participants by incidence relationships, directional combination relationships, aggregation relationships and the like;
(2) the seat configuration and command relationship of the passengers identified in the last step are described by a packet diagram, different types of passengers are defined by different packets, the relationship between the passengers is represented by a dependency relationship, and a constructor type can be used for representing a command relationship type.
Step2.2 construction system task scene
Defining a typical battle scene as a model basis of subsequent demand analysis activities, specifically:
(1) in the use case diagram, a combat task scene is defined by a use case, and the use case can be marked as a 'task scene' by adopting a constructor;
(2) the participants represent the forces of the two parties of red and blue related to the idea, and a tectonic mark can be used;
(3) representing relationships between participants and task scenarios in associative relationships
(4) The description of the scene is added using a requirements element, which may be labeled as a "scene description" using a constructor.
3. Task decomposition and modeling
And performing task decomposition on a typical combat scene to form a phase task, and performing any flow design so as to identify the detailed use case. Specifically, the method comprises the following steps:
(1) adding an activity diagram for a task scene, describing a task flow, and showing a stage task level;
(2) adding an activity pin to the activity in the activity diagram represents the enemy and my power involved in the task at this stage;
(3) each stage task is shown in a use case form by using the use case diagram, so that the subsequent detailed analysis can be carried out, and a constructive 'stage task' can be added for the use case to serve as a mark;
(4) the task use cases and the stage task use cases express the relationship by a constructor 'include';
(5) and taking the equipment system where the task system is located as the system boundary of the use case diagram, and delimiting the scope of the task system.
4. Capability requirement and phase task tracking
Establishing a retrospective relationship between the input combat demand and the stage task to ensure that the combat demand is completely expressed in the thought, specifically:
(1) displaying the combat demand and stage tasks decomposed in the third step by adopting a matrix view;
(2) adding a relation 'trace' for the combat demand and the stage task with a retrospective relation through a matrix view;
(3) a demand graph may be created for each stage task separately showing the relationship between it and all the fighting demands associated on it
5. Phase task design and modeling
According to the decomposed stage tasks, service case analysis work is parallelly or iteratively expanded, information flow and control flow relations among subtasks are refined, meanwhile, system analysis boundaries are conveniently contracted, and focusing is conducted from a large system to a task system to serve as the basis of using scene analysis of the task system. Specifically, the method comprises the following steps:
(1) refining the use case of the 'stage task' decomposed in the fourth step by using an activity diagram;
(2) describing information flow among the subtasks in the stage through activities, object nodes, activity pins and object flow;
(3) describing the control flow among the sub-tasks in the phase through activities, control flows and the like;
(4) each subtask is presented by using an example graph, and the relationship between the phase task and the subtask case is expressed by a constructor 'include';
(5) in the use case diagram, the use cases completed by the task system are identified through the system boundary
6. Task requirement derivation
Based on the service use case of the task system, the use scene of the task system is analyzed, the operation and expectation of the participants on the system are detailed, and meanwhile, the corresponding task requirements are deduced. Specifically, the method comprises the following steps:
(1) within the system boundary of the task system, a sequence diagram is used for refining a 'stage task' use case;
(2) the life line and the system boundary in the timing diagram express various users of the integrated task system;
(3) the operation of each user under the task at the stage is described by the sequence of 'message', 'event', 'interactive operator', 'separator', 'partition line', etc.;
(4) the functions of the system under the task at this stage are described by the sequence of 'message', 'event', 'interactive operator', 'separator' and 'partition line';
(5) at least one requirement element is used for carrying out requirement description for a single 'message' or 'event', and user requirements are developed;
(6) user requirement elements are uniformly stored in a model tree and displayed in a requirement modeling environment through a Table View (Table View), so that subsequent checking and use are facilitated.
(7) The identified itemized requirements serve as derived user requirements for review.
7. Deriving system use cases
And clustering the functions of the task system from the task requirements, and abstracting a relatively independent system case. Specifically, the method comprises the following steps:
(1) sorting functions which a system obtained by analyzing in a task scene sequence diagram should have;
(2) clustering functions and abstracting a system use case;
(3) drawing a usage diagram, expressing the relationship between the system use case and external participants, the system use case and functions, deriving high-level and system requirements
And according to the system use case and the task requirement, deriving a high-level system use case. Specifically, the method comprises the following steps:
(1) identifying functions in the system use case as system requirements;
(2) establishing a tracking relation of high-level system requirements to task requirements, wherein each task requirement is covered by at least one high-level system requirement, establishing the high-level system requirements by constructing a mapping matrix, and the tracking relation of the task requirements meets one task requirement and is covered by at least one high-level system requirement;
(3) and exporting and managing high-level system requirements.
9. Forming demand models
And constructing a requirement model organization structure of the task system, wherein the requirement model organization structure comprises a task and function model hierarchy, a design model hierarchy and a modeling process model hierarchy, and is shown in FIG. 2.
Task and function models;
the task and function model comprises a participant package, a requirement analysis package and a function analysis package 3, wherein the participant package stores all participant models of the task, the requirement analysis package stores a task system requirement model, and the function analysis package stores a task system function model.
Designing a model: the system comprises a design comprehensive package and an interface package 2, wherein the design comprehensive package stores a system architecture and a software configuration item design model, and the interface package stores an internal interface model and an external interface model of the system; the design comprehensive package is divided into three layers: the first layer structure describes basic description and fighting process of fighting task scenario through use of illustration and activity diagram; the second layer structure describes the decomposition description of the tasks of each stage, which is presented by using an illustration. And the retrospective relationship between the decomposed stage tasks and the combat requirements is presented on the layer through a matrix view; the third layer structure describes the task flow decomposition and operational interaction of single-phase tasks, presented by use of illustrations, activity diagrams, and timing diagrams. And the user requirements are refined and stored as derived requirements. The interface package mainly comprises an information interface and a man-machine interface which are decomposed from an internal block diagram and a block diagram.
Modeling a process model: the system comprises a demand modeling process model, a navigation package, a task system general configuration package, a SysML package and a Harmony SE package 4. The demand modeling process model and the navigation package are used for displaying a modeling overall process model, the task system general configuration package stores task system reusable configuration files, and the SysML package and the Harmony SE package store modeling basic configuration files.
Key point of the invention
1. The task system requirement development process is provided, and requirement analysis and verification of complex systems with unclear use concepts, ambiguous requirement scenes, incomplete system capacity and the like are achieved.
2. A demand description mode based on a model is provided, the consistency expression of demands of each stage of demand analysis is realized, and the accurate description and tracing of the demands of a task system are realized.
Effects of the invention
By decomposing the task system requirement development process and visually expressing the model, the analysis of the operation scene, the system capability, the function and the interface requirement of the complex task system and the requirement tracing and verification are realized, and the scheme design and the integrated verification of the task system can be better supported.
Claims (9)
1. A task system requirement development method based on a model is characterized by comprising the following steps:
1. importing user demand capacity;
inputting the top-level combat demand into a modeling system as a modeling initial point and a subsequent modeling reference;
2. identifying a system operating environment;
identifying the context of the task system, including superior, passenger, friend, target and passenger command relation, and helping to understand the operating environment of the task system; defining a typical combat scene as a model basis of subsequent demand analysis activities;
3. decomposing and modeling a task;
performing task decomposition on a typical combat scene to form stage tasks, and performing task flow design to facilitate detailed case identification;
4. capacity requirements and stage task tracking;
establishing a retrospective relation between the input combat demand and the stage task to ensure that the combat demand is completely expressed in the scenario;
5. designing and modeling stage tasks;
according to the decomposed stage tasks, parallelly or iteratively expanding service case analysis work, refining information flow and control flow relation among subtasks, and simultaneously facilitating contraction of system analysis boundaries, focusing on a task system from a large system as a basis for analyzing a use scene of the task system;
6. deducing task requirements;
analyzing a use scene of the task system based on a service case of the task system, refining the operation and expectation of a participant on the system, and simultaneously deducing corresponding task requirements;
7. deducing a system use case;
clustering the functions of a task system from task requirements, and abstracting an independent system case;
8. deriving high-level and system requirements;
according to the system use cases and the task requirements, high-level system use cases are derived;
9. forming a demand model;
constructing a demand model organization structure of a task system, wherein the demand model organization structure comprises a task and function model, a design model and a modeling process model;
in the ninth step, the task and function model comprises a participant package, a requirement analysis package and a function analysis package 3, wherein the participant package stores all participant models of the task, the requirement analysis package stores a task system requirement model, and the function analysis package stores a task system function model;
the design model comprises a design comprehensive package and an interface package 2, the design comprehensive package stores a system architecture and software configuration item design model, and the interface package stores an internal interface model and an external interface model of the system; the design comprehensive package is divided into three layers: the first layer structure describes basic description and fighting process of fighting task scenario through use of illustration and activity diagram; the second layer structure describes the decomposition description of each stage task, and is presented by using an illustration; and the retrospective relationship between the decomposed stage tasks and the combat requirements is presented on the layer through a matrix view; the third layer structure describes the task flow decomposition and operation interaction of a single-phase task, and is presented by using an illustration chart, an activity chart and a time sequence chart; user requirements are refined and stored as derivative requirements; the interface package mainly comprises an information interface and a man-machine interface which are decomposed from an internal block diagram and a block diagram;
the modeling process model comprises a requirement modeling process model and a navigation package, a task system general configuration package, a SysML package and a Harmony SE package 4, wherein the requirement modeling process model and the navigation package are used for displaying the modeling overall process model, the task system general configuration package stores task system reusable configuration files, and the SysML package and the Harmony SE package store modeling basic configuration files.
2. The model-based task system requirement development method of claim 1, wherein the step one further comprises:
(1) decomposing the fighting requirements of the top layer by layer, and importing the fighting requirements into a modeling system to form a requirement tree structure;
(2) and displaying the top-level combat demand in a demand modeling environment in a demand table view mode by using the demand tree.
3. The model-based task system requirement development method of claim 2, wherein the second step further comprises:
step2.1 recognition of System context
(1) Describing system context by a module definition diagram, representing a task system, a platform at the upper level, a superior level and a friend system by modules, representing the strength of both a passenger and a friend by participants, and representing the relationship among the modules and the participants by an incidence relationship, a directional combination relationship and an aggregation relationship;
(2) describing seat configuration and command relationship of the passengers identified in the previous step by using a package diagram, defining different types of passengers by using different packages, representing the relationship between the passengers by using a dependency relationship, and representing a command relationship type by using a construction type;
step2.2 configuration system task scene
(1) Defining a battle task scene by using a case in the use case diagram, and marking the case as a 'task scene' by using a constructor;
(2) the participants express the forces of the two parties of the red and the blue which are thought to be involved, and the constructive mark is used;
(3) representing relationships between participants and task scenarios in associative relationships
(4) The description of the scene is added using a requirements element, which is marked as a "scene description" using a constructor.
4. The model-based task system requirement development method of claim 3, wherein the step three further comprises:
(1) adding an activity diagram for a task scene, describing a task flow, and showing a stage task level;
(2) adding an activity pin on the activity in the activity diagram represents the enemy and my strength involved in the task at this stage;
(3) exposing each stage task in the form of a use case by using the use case diagram;
(4) the task use cases and the stage task use cases express the relationship by a constructor 'include';
(5) and taking an equipment system where the task system is located as a system boundary of the use case diagram, and delimiting the scope of the task system.
5. The model-based mission system requirement development method of claim 4, wherein the fourth step further comprises:
(1) displaying the combat demand and the stage tasks decomposed in the third step by adopting a matrix view;
(2) adding a relation 'trace' for the combat demand and the stage task with the retrospective relation through a matrix view;
(3) a demand graph is created for each stage mission separately, showing the relationship between each stage mission and all the combat demands associated thereon.
6. The model-based task system requirement development method of claim 5, wherein the step five further comprises:
(1) a 'stage task' use case which is solved by the activity diagram refining step;
(2) describing information flow among the subtasks in the stage through activities, object nodes, activity pins and object flow;
(3) describing the control flow among the phase subtasks through activities and control flows;
(4) each subtask is presented by using an example graph, and the relationship between the phase task and the subtask case is expressed by a constructor 'include';
(5) in the use case graph, the use cases completed by the task system are identified by the system boundary.
7. The model-based mission system requirement development method of claim 6, wherein the sixth step further comprises:
(1) within the system boundary of the task system, a sequence diagram is used for refining a 'stage task' use case;
(2) the life line and the system boundary in the timing diagram express various users of the integrated task system;
(3) the operation of each user under the task at the stage is sequentially described through 'message', 'event', 'interaction operator', 'separator' and 'partition line';
(4) the functions of the system under the task at the stage are sequentially described through 'message', 'event', 'interactive operator', 'separator' and 'partition line';
(5) utilizing at least one requirement element to carry out requirement description for a single 'message' or 'event', and developing user requirements;
(6) uniformly storing user demand elements in a model tree, and displaying the user demand elements in a demand modeling environment through a table view;
(7) the identified itemized requirements serve as derived user requirements for review.
8. The model-based task system requirement development method of claim 7, wherein the seventh step further comprises:
(1) clustering functions of the system obtained by analyzing the task scene sequence diagram, and abstracting a system case;
(2) drawing a usage diagram, and expressing the relationship between the system usage and external participants, the system usage and functions.
9. The model-based task system requirement development method of claim 8, wherein the seventh step further comprises:
(1) identifying functions in the system use case as system requirements;
(2) establishing a tracking relation of high-level system requirements to task requirements, wherein each task requirement is covered by at least one high-level system requirement, establishing the high-level system requirements by constructing a mapping matrix, and the tracking relation of the task requirements meets one task requirement and is covered by at least one high-level system requirement;
(3) and exporting and managing high-level system requirements.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911309480.9A CN111142845B (en) | 2019-12-18 | 2019-12-18 | Model-based task system demand development method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911309480.9A CN111142845B (en) | 2019-12-18 | 2019-12-18 | Model-based task system demand development method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111142845A CN111142845A (en) | 2020-05-12 |
| CN111142845B true CN111142845B (en) | 2023-03-28 |
Family
ID=70518722
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911309480.9A Active CN111142845B (en) | 2019-12-18 | 2019-12-18 | Model-based task system demand development method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111142845B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112068805B (en) * | 2020-09-02 | 2024-05-03 | 中国航空无线电电子研究所 | Demand development method |
| CN112527245B (en) * | 2020-12-04 | 2022-06-28 | 中国航空工业集团公司成都飞机设计研究所 | Equipment system function demand analysis method based on model |
| CN113111441B (en) * | 2021-04-26 | 2023-01-31 | 河北交通职业技术学院 | Method for constructing cluster unmanned aerial vehicle task model based on adjacency relation |
| CN113536542A (en) * | 2021-06-18 | 2021-10-22 | 中国电子科技集团公司电子科学研究院 | System engineering agile development method for uncertain demand and rapid technology change |
| CN117311691B (en) * | 2023-10-07 | 2024-06-11 | 山东大学 | MBSE-based design method for monitoring and early warning system of hazardous chemical substance transport vehicle |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103984814A (en) * | 2014-05-13 | 2014-08-13 | 燕雪峰 | Modeling method of complex equipment system |
| CN108897752A (en) * | 2018-05-07 | 2018-11-27 | 中国电子科技集团公司电子科学研究院 | Method is described towards intelligentized electronic information system architecture |
| CN109491642A (en) * | 2018-11-01 | 2019-03-19 | 成都信息工程大学 | A kind of Requirements Modeling system and method based on scene, information data processing terminal |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130097583A1 (en) * | 2011-09-27 | 2013-04-18 | The University Of Texas System | Systems and Methods For Automating the Application of a Software Methodology |
-
2019
- 2019-12-18 CN CN201911309480.9A patent/CN111142845B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103984814A (en) * | 2014-05-13 | 2014-08-13 | 燕雪峰 | Modeling method of complex equipment system |
| CN108897752A (en) * | 2018-05-07 | 2018-11-27 | 中国电子科技集团公司电子科学研究院 | Method is described towards intelligentized electronic information system architecture |
| CN109491642A (en) * | 2018-11-01 | 2019-03-19 | 成都信息工程大学 | A kind of Requirements Modeling system and method based on scene, information data processing terminal |
Non-Patent Citations (2)
| Title |
|---|
| 段采宇.武器装备需求建模、量化、集成的理论与方法研究.《中国博士学位论文全文数据库 工程科技Ⅱ辑》.2010,C032-2. * |
| 王本胜 等.基于任务-能力匹配的联合作战需求建模.《指挥信息系统与技术》.2011,第2卷(第3期),第5-9页. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111142845A (en) | 2020-05-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111142845B (en) | Model-based task system demand development method | |
| Hofmeister et al. | Generalizing a model of software architecture design from five industrial approaches | |
| CN113781856B (en) | Training simulation system for combined combat weapon equipment and implementation method thereof | |
| Tomiyama et al. | Design methodologies: Industrial and educational applications | |
| Krygiel | Behind the wizard's curtain: An integration environment for a system of systems | |
| Zeising et al. | Towards a common platform for the support of routine and agile business processes | |
| US20070156374A1 (en) | Complex process modeling and simulation system and method | |
| Ossher et al. | Flexible modeling tools for pre-requirements analysis: conceptual architecture and research challenges | |
| CN109522002A (en) | A kind of unmanned aerial vehicle station open architecture based on model-driven | |
| Favre | Cacophony: Metamodel-driven software architecture reconstruction | |
| JP2008544407A (en) | Technical methods and tools for capability-based multiple family of systems planning | |
| Cestari et al. | A method to diagnose public administration interoperability capability levels based on multi-criteria decision-making | |
| CN108897752B (en) | Intelligent electronic information system architecture description method | |
| CN113902394A (en) | Service platform for realizing artificial intelligence industry ecology | |
| Hallberg et al. | Agile architecture framework for model driven development of C2 systems | |
| CN112949061B (en) | Village and town development model construction method and system based on reusable operator | |
| JP2001005651A (en) | Method for determining software, method for using software, recording medium, processor, method for maintaining software, method for transporting software, method for managing software, and method for preparing processing route diagram, method for preparating pallet function, method for deciding pallet region, method for preparing pallet-chain-function, method for preparing phase element, method for preparing logical element, method for preparing operation element, method for mounting software, method for developing software, method for replacing data structure, method for replacing data value, method for analizing conventional program, method for developing and managing software, method for method for applicating and managing software, parallel computer and judgement supporting device. | |
| Bermell-Garcia | A metamodel to annotate knowledge based engineering codes as enterprise knowledge resources | |
| Winkler et al. | Towards a Technique for Modeling New Forms of Collaborative Work Practices–The Facilitation Process Model 2.0 | |
| CN102902519A (en) | Method for achieving composite prediction calculation based on dynamic system | |
| CN115328442B (en) | Hazardous chemical substance enterprise safety risk management and control platform constructed based on low code platform | |
| Derrick | A visual simulation support environment based on a multifaceted conceptual framework | |
| Gena | Suitability of Model Based Systems Engineering for Agile Automotive Product Development | |
| Li et al. | General Architecture Framework and General Modelling Framework: Interoperability of Enterprise Architecture | |
| KR102130774B1 (en) | Internal property based software asset architecture creation system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |