CN113536542A - System engineering agile development method for uncertain demand and rapid technology change - Google Patents
System engineering agile development method for uncertain demand and rapid technology change Download PDFInfo
- Publication number
- CN113536542A CN113536542A CN202110678206.XA CN202110678206A CN113536542A CN 113536542 A CN113536542 A CN 113536542A CN 202110678206 A CN202110678206 A CN 202110678206A CN 113536542 A CN113536542 A CN 113536542A
- Authority
- CN
- China
- Prior art keywords
- level
- requirements
- layer
- unit
- prototype
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F30/00—Computer-aided design [CAD]
- G06F30/20—Design optimisation, verification or simulation
Landscapes
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Evolutionary Computation (AREA)
- Geometry (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses a system engineering agile development method facing uncertain requirements and rapid technical change, which aims to obtain engineering experience, focuses on key design parameters, focuses on top-level requirements rather than low-level requirements, achieves global optimization through continuously adjusting the current situation locally, and gradually continues to iterate downwards and deeply after the key requirements are met and verified.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a system engineering agile development method for uncertain demand and rapid technology change.
Background
At present, the Engineering and academic communities have great disputes and confusion about the meaning of System Engineering (SE) from the translation of names to concepts. The visual expression of the system engineering process has various models, which mainly comprise a waterfall model, an ellipse model, a V model, a spiral model, model-based system engineering (MBSE) and digital engineering. The waterfall model is proposed by Royce in 1970, is initially used for software development and consists of 5-7 steps or stages, and is expanded into 8 steps by Boehm in 1981, wherein the steps comprise demand analysis, demand definition, summary design, detailed design, implementation, system test, acceptance test, maintenance and the like; the ellipse model is the American military standard MIL-STD-499A released by the United states department of defense in 1974 and the MIL-STD-499B (released without formal release) which is continuously updated from the beginning of the 90 s, and makes a relatively complete summary for the classical system engineering, wherein the serial technical process comprises three steps of requirement analysis, function analysis and distribution, design synthesis and the like, and the technical management process comprises system analysis and control and is used for supporting the technical process; the V model was proposed in 1978 by Forsberg & Mooz, emphasizing the role of testing in various stages of system engineering and relating the processes of system decomposition and system integration to each other through testing; the spiral model was proposed by Boehm in 1986, with reference to Hall's work in system engineering from 1969, with the aim of introducing a risk-driven product development approach; MBSE is formally proposed by the International Committee for System Engineering (INCOSE) in Systems Engineering Vision 2020 in 2006 for 10 months, compared with the traditional document-based system Engineering process, the MBSE supports activities such as requirement definition, design definition, analysis, verification and confirmation of a system by using a modeling method, replaces a document with a model, converts nouns, verbs, adjectives and parameters describing system structures, functions, performances and specification requirements into digital model expressions, and converts the expression from 'taking a document report as a center' into 'taking the model as a center' so that the system Engineering process is manageable, reproducible and reusable; digital engineering was proposed by the department of national defense system engineering in 2016, will serve the united states military to meet the digital era by implementing digital engineering, and is the key to completing digital transformation, which is a model-based system engineering (MBSE) mode of digital version, and utilizes digital environment, digital processing, digital method, digital tool and digital design to realize support for the activities of the system in the whole life cycle, such as planning, demand, design, analysis, verification, operation and/or maintenance.
In the context of various System problems, System of systems Engineering (SoSE) has emerged. Compared with the traditional system engineering, the system engineering has more pertinence in analyzing and solving the mutual coordination and mutual operation problems among different types of independent large-scale complex systems, and focuses on solving the multi-system integration problems of the existing system and a newly-researched system, including the planning design problem of the new system and the multi-system integration problem; while system engineering focuses on solving the requirements, design and development issues of a single system (both existing and newly developed). The system engineering is the extension and expansion of the system engineering, and more focuses on converting the capacity requirement into a system solution and finally into a real system. Generally, before development, system engineering defines and establishes a strict boundary, and specifies a series of sub-requirements for the boundary, and completes design and development of a system according to the requirements. Therefore, in the current system engineering, the interoperable flexibility and the strain capacity are mainly realized by balancing and optimizing the interrelation among a plurality of systems, and a system capable of meeting the user requirements is finally constructed, but the system development and management cannot be quickly realized just because the interrelation among a plurality of systems needs to be balanced and optimized in the existing system engineering, so that how to realize the quick system development aiming at different requirements and different technologies becomes a technical problem to be urgently solved at present.
Disclosure of Invention
The invention provides a system engineering agile development method for uncertain demand and rapid technology change, which aims to solve the problem that rapid system development cannot be realized for different demands and different technologies in the prior art.
The invention provides a system engineering agile development method facing uncertain demand and rapid technology change, which comprises the following steps: the method comprises the steps of constructing unit-level prototype products based on top level requirements of a system layer and top level requirements of the system layer, performing test identification on the constructed unit-level prototype products in a preset environment or an actual measurement environment respectively, performing system integration verification, performing iteration on the unit-level prototype products step by step according to the bottom level requirements of the system layer and the bottom level requirements of the system layer to generate iterated unit-level prototype products, and performing test identification and system integration verification on the iterated unit-level prototype products to rapidly develop system engineering.
Optionally, the step of building a prototype product at a unit level based on the top level requirements of the hierarchy level comprises:
identifying key design parameters concerned by the top-level requirements of the system level based on the top-level requirements of the system level;
optimizing performance by adjusting the key design parameters to meet the top level requirements of the hierarchy level;
optimizing through simulation and simulation, building and developing unit-level prototype products based on the top-level requirements of the system layer for testing, and tracking the change of the key design parameters;
performing test qualification on the prototype product of the unit level to verify whether the prototype product of the unit level meets the top-level requirement of the system layer.
Optionally, after verifying that the prototype product at the unit level meets the top-level requirements of the hierarchy layer, the method further comprises: and iterating the bottom layer requirements of each layer of the system layer step by step according to a processing method of the top layer requirements of the system layer to respectively generate iterated unit-level prototype products, and performing test identification and system integration verification on the iterated unit-level prototype products to verify whether the iterated unit-level prototype products meet the bottom layer requirements of the corresponding system layer.
Optionally, after verifying that the prototype product of each unit level meets the underlying requirements of the corresponding system layer, the method further includes: and constructing the prototype products of each unit level to obtain an integral prototype product of the system layer, identifying the integral prototype product in a preset environment or an actual measurement environment, and performing system integration verification.
Optionally, the step of building a prototype product at a unit level based on the top level requirements of the system layer comprises:
identifying key design parameters concerned by top-level requirements of a system layer based on the top-level requirements of the system layer;
optimizing performance by adjusting the key design parameters to meet top-level requirements of the system layer;
optimizing through simulation and simulation, building and developing unit-level prototype products based on top-level requirements of the system layer for testing, and tracking changes of the key design parameters;
performing a trial qualification on the prototype product at the unit level to verify that the prototype product at the unit level meets the top-level requirements of the system layer.
Optionally, after verifying that the prototype product at the unit level meets the top-level requirements of the system layer, the method further comprises: and iterating the bottom layer requirements of each layer of the system layer step by step according to a processing method of the top layer requirements of the system layer to respectively generate iterated unit-level prototype products, and performing test identification and system integration verification on the iterated unit-level prototype products to verify whether the iterated unit-level prototype products meet the bottom layer requirements of the corresponding system layer.
Optionally, after verifying that the prototype product of each unit level meets the underlying requirements of the corresponding system layer, the method further includes: and constructing the prototype products of all unit levels to obtain an integral prototype product of a system layer, identifying the integral prototype product in a preset environment or an actual measurement environment, and performing system integration verification.
Optionally, the method further comprises: and constructing the whole prototype product of the system layer and the whole prototype product of the system layer to obtain a final whole prototype product, and identifying and integrally verifying the final whole prototype product in a preset environment or an actual measurement environment.
Optionally, before the prototype product is built based on the top-level requirements of the system layer and the top-level requirements of the system layer, the method further includes: and respectively converting the top layer requirement and the bottom layer requirement based on the system layer, and the top layer requirement and the bottom layer requirement of the system layer into technical requirements.
Optionally, the method further comprises: a system overall unit and a plurality of system development units are arranged;
the system overall unit is used for carrying out system-level strategy decision;
the system development unit is used for carrying out system-level policy decision.
The invention has the following beneficial effects:
the method aims to obtain engineering experience, focuses on key design parameters, focuses on top-level requirements rather than low-level requirements, achieves global optimization through continuous local state-of-call, and gradually continues downward deep iteration after the key requirements are met and verified.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
FIG. 1 is a schematic flow chart of a method for agile development of a system engineering for uncertain demand and rapid technology change according to an embodiment of the present invention;
FIG. 2 is a schematic flow chart of another method for agile development of a system engineering for uncertain demand and rapid technology change according to an embodiment of the present invention;
FIG. 3 is a schematic flow chart of another agile development method for system engineering facing uncertain demand and rapid technology change according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of an architectural engineering management mode of a master-slave architecture according to an embodiment of the present invention;
FIG. 5 is a diagram of an architectural engineering model provided by an embodiment of the present invention.
Detailed Description
The embodiment of the invention can not realize rapid system development aiming at different requirements and different technologies, focuses on key design parameters, focuses on top-level requirements rather than low-level requirements, achieves global optimization through continuously adjusting the current situation locally, and gradually continues downward depth iteration after the key requirements are met and verified, thereby improving the development efficiency of system engineering, saving development time, and finally effectively solving the problems that the prior work investment of the system engineering is too much, the technical state program control is strict, the system engineering is difficult to adapt to the requirements of rapid technology development and rapid requirement change on flexibility, and the like. The present invention will be described in further detail below with reference to the drawings and examples. It should be understood that the specific embodiments described herein are merely illustrative of the invention and do not limit the invention.
The embodiment of the invention provides a system engineering agile development method facing uncertain demand and rapid technology change, and the method is shown in figure 1 and comprises the following steps:
s101, constructing a unit-level prototype product based on the top-level requirement of the system layer and the top-level requirement of the system layer;
specifically, the top requirement in the embodiment of the present invention refers to a key design parameter focused by a user, or may be core concept content of a current project, for example, when the current project is a rocket, the top requirement of the user is a main structure of the rocket, and the bottom requirement in the embodiment of the present invention is other various additional structures performed to better perfect the main structure of the rocket. Of course, the above is only an example, and in the implementation, a person skilled in the art may arbitrarily set the top layer requirement and the bottom layer requirement based on specific items according to the method described in the present invention, and the present invention is not limited in detail.
Generally, the overall concept of the invention focuses on key design parameters, focuses on top-level requirements rather than low-level requirements, and achieves global optimization by continuously and locally adjusting the current situation, so that the development efficiency of the project is finally improved, and the user experience is finally improved.
S102, respectively carrying out test identification on the constructed unit-level prototype product in a preset environment or an actual measurement environment, and carrying out system integration verification;
that is, embodiments of the present invention build and test prototype products for demand.
It can be understood that, since the present invention gradually obtains the prototype product from the top requirement to the bottom requirement, the present invention will obtain a prototype product for different requirements, and the product is in an increasing relationship with the addition of different requirements, and therefore, the embodiment of the present invention defines the constructed prototype product as a prototype product of different unit levels to better distinguish the prototype product.
And S103, iterating the unit-level prototype product to generate an iterated unit-level prototype product according to the bottom layer requirement of the system layer and the bottom layer requirement of the system layer step by step, and performing test identification and system integration verification on the iterated unit-level prototype product to rapidly develop the system engineering.
Specifically, the embodiment of the invention performs test identification and system integration verification on all unit-level prototype products obtained after iteration, and finally realizes rapid development of system engineering.
Generally speaking, the embodiment of the invention mainly aims at key design parameters of top-level requirements to construct a prototype product of a main body, then carries out test identification and integrated verification on the prototype product of the main body, and then carries out local adjustment aiming at low-level requirements to finally achieve global optimization.
It should be noted that, the embodiments of the present invention are directed to various system projects with uncertain requirements and rapidly changing technologies, such as various aerospace system projects and various new technology system projects, and because design schemes of various details may be uncertain at an initial stage of a project design, the present invention proposes to focus on a key design parameter, i.e., a top-level requirement, and then continuously and deeply iterate a bottom-level requirement to rapidly develop the system project, and practice proves that the present invention can also substantially improve development efficiency of the system project.
As shown in fig. 2, in specific implementation, in the embodiment of the present invention, the processing method for the system layer specifically includes the following steps:
wherein the step of creating a prototype product at a unit level based on the top level requirements of the hierarchy level comprises: identifying key design parameters concerned by the top-level requirements of the system level based on the top-level requirements of the system level; optimizing performance by adjusting the key design parameters to meet the top level requirements of the hierarchy level; optimizing through simulation and simulation, building and developing unit-level prototype products based on the top-level requirements of the system layer for testing, and tracking the change of the key design parameters; performing test qualification on the prototype product of the unit level to verify whether the prototype product of the unit level meets the top-level requirement of the system layer.
And, after verifying that the prototype product at the unit level meets the top level requirements of the hierarchy level, the method further comprises: and iterating the bottom layer requirements of each layer of the system layer step by step according to a processing method of the top layer requirements of the system layer to respectively generate iterated unit-level prototype products, and performing test identification and system integration verification on the iterated unit-level prototype products to verify whether the iterated unit-level prototype products meet the bottom layer requirements of the corresponding system layer.
Then, after verifying that the prototype product of each unit level meets the bottom layer requirement of the corresponding system layer, the method further comprises: and constructing the prototype products of each unit level to obtain an integral prototype product of the system layer, identifying the integral prototype product in a preset environment or an actual measurement environment, and performing system integration verification.
That is to say, in the embodiment of the present invention, the driving iteration of the system layer is performed based on the top layer requirement and the bottom layer requirement, and finally, the prototype product of each unit level is constructed to obtain the whole prototype product of the system layer, and the system integration verification is performed.
As shown in fig. 2, in specific implementation, in the embodiment of the present invention, the processing method for the system layer specifically includes the following steps:
wherein the step of creating a prototype product at a unit level based on top level requirements of a system layer comprises: identifying key design parameters concerned by top-level requirements of a system layer based on the top-level requirements of the system layer; optimizing performance by adjusting the key design parameters to meet top-level requirements of the system layer; optimizing through simulation and simulation, building and developing unit-level prototype products based on top-level requirements of the system layer for testing, and tracking changes of the key design parameters; performing a trial qualification on the prototype product at the unit level to verify that the prototype product at the unit level meets the top-level requirements of the system layer.
After verifying that the prototype product at the unit level meets the top-level requirements of the system layer, the method further comprises: and iterating the bottom layer requirements of each layer of the system layer step by step according to a processing method of the top layer requirements of the system layer to respectively generate iterated unit-level prototype products, and performing test identification and system integration verification on the iterated unit-level prototype products to verify whether the iterated unit-level prototype products meet the bottom layer requirements of the corresponding system layer.
After verifying that the prototype product of each unit level meets the underlying requirements of the corresponding system layer, the method further comprises: and constructing the prototype products of all unit levels to obtain an integral prototype product of a system layer, identifying the integral prototype product in a preset environment or an actual measurement environment, and performing system integration verification.
That is to say, the embodiment of the present invention performs driving iteration of the system layer based on the top layer requirement and the bottom layer requirement, and finally constructs the prototype products of each unit level to obtain the overall prototype product of the system layer, and performs system integration verification.
In specific implementation, the method according to the embodiment of the present invention further includes: and constructing the whole prototype product of the system layer and the whole prototype product of the system layer to obtain a final whole prototype product, and carrying out identification and integrated verification on the final whole prototype product in a preset environment or an actual measurement environment so as to obtain a verified final prototype product.
The method according to an embodiment of the invention will be explained and illustrated in detail below with reference to fig. 3:
step 301: acquiring a top layer requirement;
step 302: identifying key design parameters;
step 303: adjusting key parameters to optimize performance to meet top-level requirements;
step 304: simulation and simulation, optimizing through simulation and simulation, and starting to build and develop prototype products for testing;
step 305: tracking changes in key design parameters;
step 306: testing and identifying unit-level equipment;
step 307: and carrying out integration verification to verify whether the key requirements are met.
Generally speaking, the core of the development method described in the embodiment of the present invention is to obtain engineering experience, focus on key design parameters, focus on top-level requirements rather than low-level requirements, achieve global optimization by continuously adjusting the status of local conditions, and gradually continue downward deep iteration after these key requirements are met and verified. By applying the method, the development efficiency of the system engineering is improved, the development time is saved, and the problems that the early-stage work investment of the system engineering is too much, the technical state program control is strict, the requirements of the rapid development of the technology and the rapid change of the demand on the flexibility are difficult to adapt are solved.
As shown in fig. 4, the management mode of the master-slave architecture provided in the embodiment of the present invention is an architectural engineering technology management mode, and as can be seen from fig. 4, the management mode of the embodiment of the present invention is provided with a system overall unit and a plurality of system development units; the system general unit is used for making the strategy decision at the system level, and the system development unit is used for making the strategy decision at the system level.
That is, in the aspect of the technical management process, the embodiment of the present invention provides a system engineering technical management mode of a "one master multiple slave structure" for a multi-cycle iterative process requiring a fast decision, a fast prototype development and an efficient verification, so as to simplify the decision making and transmission processes to the maximum extent, thereby improving the operation efficiency.
In the aspect of technical process, aiming at the contradiction that the requirement determination needs repeated iteration, requirements and technology are frequently changed in the system engineering process, the embodiment of the invention provides a system engineering iterative design method driven by a requirement level.
Compared with the traditional system engineering which is too heavy in design investment at the concept design stage and cannot adapt to the flexibility requirements of requirement change and technology rapid change, the agile system engineering development in the technical scheme provided by the invention focuses more on the requirement level-driven iteration, the deep excavation of the requirement is carried out in the iteration process, the upper-layer key requirements are focused more at first, the lower-layer requirements can be realized by adopting the existing or feasible scheme without paying attention first, and after the upper-layer key requirements are realized, the lower-layer requirements are gradually iterated. The method emphasizes that a product prototype is quickly presented to a user and then iteration is carried out, and the requirement depth of the prototype tends to be excavated as deep as possible in each iteration so as to reduce the number of iterations as far as possible. And the experience generated after each complete iteration reduces the overall cost of the project and meets the requirements of rapid change of the requirements and rapid change of the technology in the construction process of the system engineering in the future.
The process according to the invention will be explained and illustrated in detail below by means of a specific example:
the embodiment of the invention designs the system engineering development process into two levels and three stages, wherein the two levels are hierarchical and are divided into a system level and a system level 2 level; "three phases" means that the architecture engineering process mainly includes 3 phases of top-level design, build execution and integration verification, as shown in fig. 5. On a system level, the system capacity requirement is taken as a target, the system capacity requirement is mainly subjected to 3 stages of top layer design, system construction and integrated verification, engineering activities of the top layer design are drawn by user requirements, a system demand development process, a logic function analysis process and a system architecture design process are mainly developed, and a unified capacity requirement of the system is formed; on a system level, the system function realization is taken as a target, the system comprises system requirement analysis, system design, subsystem design, unit design, key technology attack, subsystem integration test, system integration test and system evaluation, and a system engineering method is adopted to guide engineering practice on the level. On the organization architecture, according to the concept of hierarchical organization and joint management, a joint system consisting of a system general unit and system bearing and bearing units is used for organizing and implementing engineering activities, wherein the system-level engineering activities are implemented by the system general unit, and the system-level engineering activities are implemented by the system bearing and bearing units.
In general, the system engineering process can be summarized into 8 technical processes and 8 technical management processes, wherein the 8 technical processes are as follows:
(1) demand development process
The main task of the process is to obtain requirements input from various users and then convert these system requirements into technical requirements, and the process needs to be developed separately on both the system and system levels. Wherein, the system-level engineer team focuses on the system-related requirements and focuses on converting the system capacity requirements into the system technical requirements; a team of engineers at the system level focuses on system requirements, and focuses on translating system capability requirements into system technology requirements. In addition, in the process of demand development, a team of engineers at the system level needs to understand the system capacity demand, the system capacity demand of each component system, and the demand decomposition relationship between the systems.
(2) Logical function analysis process
The main task of this process is to understand the architecture requirements and develop a range of solutions that are feasible for the logical functionality of the system. Among them, the engineer team at the system level focuses on whether the functions of the constituent systems meet the system requirements, identifies which system can provide which functions required by the system, understands the system functions required by the system and how to distribute the functions among the constituent systems that have been built, under research, and under new research.
(3) Architectural design process
The main task of this process is to transform the output of the demand development and logic analysis process into an architectural design solution. The system-level engineering team designs a system architecture and covers the system architecture to all the component systems, and a unified framework is provided for the evolution of the system. The system design solution contains changes to the constituent systems to achieve system-level capability, and the responsibility for system design changes is typically assumed by teams of engineers at the affected system level, and these design changes need to be reflected in the allocation baselines at the top level of the system and updated in the technology baselines of the affected systems.
(4) Building execution Process
The main task of this process is to create or modify the lowest level system elements in the system level architecture, where creating or modifying means that the system elements can be obtained through manufacturing, procurement and reuse. In execution, new system capabilities can be created or existing system capabilities can be enhanced by changes to the component systems and the accumulation of all changes. The system-level engineer team dominates the execution process, and plays roles in overall coordination, technical review and testing.
(5) Integration process
The main task of the process is to connect the system elements at the lower layer in a cooperative manner, so that the system elements at the lower layer are converted into the system elements at the higher level in the architecture. The system-level engineer team is responsible for executing element integration in the system, and the system-level engineer team is responsible for integrating functions and performances of the whole system. Since the execution process of each system in the system is asynchronously carried out, the integration process is also asynchronously carried out.
(6) Verification process
The main task of this process is to verify that a system or system element meets design or construction requirements. The system-level engineer team is responsible for confirming a system technical baseline and a system distribution baseline, and the system-level engineer team is required to understand a detailed test plan for developing and executing the system and supervise test results.
(7) Evaluation process
The main task of the process is to evaluate whether the system capability meets the user requirements in the operating environment. The evaluation process may be performed in an integrated test environment, or as part of a drill or field test. The system-level engineer team is required to ensure that the evaluation on the key capability of the system is included in the test identification subjects forming the system, and the system-level engineer team test identification is required to be tested according to the evaluation requirements of the system-level engineer team.
(8) Delivery process
The main task of this process is to ultimately deliver the system or system to the user in accordance with the respective established procedures.
The 8 technical management processes are as follows:
(1) decision analysis process
The main task of the process is to make a selection from among the alternatives, provide criteria and methods for evaluating and selecting alternatives. Decision analysis processes include choosing decision criteria, methods for guiding the analysis, and the like. For example, during design, the alternatives must be analyzed to select a compromise, robust, cost-effective design that supports the system objectives based on a balance of system development cost, system performance, development progress, risk exposure, and system reliability. Wherein, the system level engineer team must understand each component system and its relationship from many angles, including technical and organizational relationships. The decisions comprise option analysis, selection of a system architecture design scheme in compromise on the premise of comprehensively considering the current characteristics of the system and a future development plan, determination of which requirement should be met in which time period through evaluation under the condition of system construction target determination, and analysis of how changes of external environments in the system exert influence on the system.
(2) Process for technical planning
All 8 technical processes need technical planning, and the main task of the process is to ensure that the system engineering process is applied in the whole life cycle of the system. The technical category required in developing the constituent systems is of greater concern relative to project planning. The system-level engineer team needs to plan the technical evolution route of the system after the technical planning of each component system is determined. The technical planning at the system level is made more difficult due to the asynchrony and parallelism of the technical planning activities at the system level. In order to reduce the risk of the systematic technical planning, a systematic engineer team needs to be added into the systematic engineering process of the system level.
(3) Process for technical assessment
The main task of this process is to measure the technical progress and efficiency of demand development and technical planning, including activities related to technical performance measurement and technical review. The technical evaluation at the system level includes two aspects, technical evaluation of system capability, technical change (upgrade) of an active system, and technical evaluation of a newly developed system. Wherein a team of system-level engineers is required to evaluate the progress of each component system in defining, planning, executing, integrating, and testing technology changes that are planned and implemented primarily by system-level project managers and system engineers.
(4) Demand management process
The main task of this process is to continuously track system requirements and their changes against the developed system requirements. The system-level engineer team not only considers the system requirements, but also needs to consider the requirements of each component system; the system-level requirements are mainly managed by system engineers of respective systems by using the requirement management process of the system, the system-level engineer team needs to know the requirement management process of the system, and the system requirement management process needs to be correspondingly connected with the requirement management processes of all distribution systems.
(5) Risk management procedure
The main tasks of the process are to ensure that the goals of cost, progress, performance and the like of each stage in the whole life cycle of the system are realized, identify and determine the range of risks and manage and control the uncertainty in the development process of the system. The system risk refers to a risk related to the system itself and tasks and targets thereof, and is related to factors such as the scale of the system, the requirement of service quality, the technical maturity, the cross-system risk management coordination or the system operation risk, and the like.
(6) Configuration management process
The main tasks of the process are to establish and manage the technology baselines (including function, allocation and product baselines) at the system level, and maintain the continuity of the product attributes, including the requirements and product configuration information thereof. Wherein, the configuration management of the system level needs to know the systems supporting the system target and the relationship between the systems; the system level engineer is mainly responsible for detailed configuration management of each constituent system.
(7) Data management process
The main task of this process is to focus on processing information related to product development and maintenance or information needed. The system level data management includes information such as system development planning, system management and fund profile, and other information related to system progress. In a system environment, a key challenge to data management efforts is obtaining permission to access each constituent system data in the form of facilitating analysis of cross-constituent system problems.
(8) Interface management process
The main task of the process is to ensure interface definition, compatibility among elements constituting the system and interconnection and interoperability with other systems. The coordination of data and metadata is a problem of an interface management center, data disclosure and semantic analysis are focused, and a system cannot control interfaces forming the system; instead, the interfaces are typically managed by protocol and negotiation.
In terms of technical process, in the conventional demand iteration model, the design starts from high-level demand (i.e. completing an aviation task), slowly extends the depth of the demand level down to the lowest-level demand (i.e. designing each screw), and then adopts a given scheme to rapidly design and assemble a product prototype and deliver the product prototype to a user. And adjusting the iteration time according to the feedback data of the user at the later stage to reduce the whole iteration time. For this iterative approach, we call "hierarchy-driven iteration of over-demand". In the process of system engineering, the flow of the system engineering is V-shaped, is developed in a grading way, and refines the requirements and the design layer by layer. In the process of requirement development, user requirements are positioned at the leftmost upper corner of V, representing mandatory requirements, expectations or suggestions of users, and the user requirements are firstly converted into system top-level requirements, then can be decomposed layer by layer and distributed downwards to become system-level, sub-system-level, component and specific work unit requirements, and then design is guided.
In the iterative design of agile development, the core purpose of iteration is to acquire experience, and according to the rule of human cognition, excavation of the depth of a demand should be performed in the iterative process, namely, "iteration is driven by a demand hierarchy". During design, the key requirements of the upper layer are paid more attention initially, the requirements of the lower layer are not paid attention first, the requirements are realized by adopting the existing or simple scheme, and after the key requirements of the upper layer are realized, the requirements of the lower layer are gradually iterated. The specific work flow comprises the following steps: the method comprises the following steps: acquiring top-level requirements, wherein a system-level engineer team focuses on the top-level requirements related to a system and focuses on converting system capacity requirements into system technical requirements; a system-level engineer team focuses on system requirements and converts system capacity requirements into system technical requirements; step two: identifying key design parameters, and identifying the key design parameters of the system level and the system level by taking the top level requirements of the system level and the system level as input respectively, so as to meet the top level requirements of the system level and the system level respectively; step three: adjusting key parameters to optimize performance to meet top-level requirements, and a system-level engineer team needs to understand the decomposition support relationship between the system and the design parameters of each component system; step four: simulation and simulation, wherein global optimization is achieved through local optimization (simulation and simulation) current situation, and a prototype product is built and developed for testing; step five: monitoring key design parameters, tracking the change of the key design parameters through the iterative interaction of the processes of the third step and the fourth step, and paying attention to the corresponding change of the system level key design parameters and the system level key design parameters; step six: placing the units in an environment predicted or actually measured for identification, so that the tested equipment and the reference equipment conform to the test environment; step seven: and performing integrated verification, verifying whether the key requirements are met, if not, repeating the steps until the key requirements are met and verified, then gradually continuing downward depth iteration, starting the requirement of the next level to be met and verified, and then gradually iterating to realize.
In the aspect of technical management process, an organization management mode of a one-master multi-slave structure is adopted, so that people at each post can work efficiently, information sharing, technical sharing and personnel cooperation can be performed in time, decision making and transmission processes are simplified to the greatest extent, and operation efficiency is improved. The basic principle of the master-slave structure is that personnel at different levels select the optimal strategy of the target in the feasible region, and the upper node unit selects the optimal strategy first, wherein the target is the optimal benefit of the whole system; the lower node unit selects a strategy according to the strategy of the upper node unit, and the target is that the benefit of each development unit is optimal. Meanwhile, the system general unit influences the policy selection of each system development unit to a certain extent, but cannot completely determine the policy of each system development unit, and the policy selection made by each system development unit also influences the policy set of the system general unit decision and the achievement of the target to a certain extent, so that the system general unit also needs to consider the reaction of the system development unit to the policy during the policy selection. In addition, each layer of personnel has own interest target which can be conflicting, and the system overall unit can comprehensively coordinate each system development unit for maintaining the overall interest, and the cooperation is realized through the redistribution of the interest.
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 (10)
1. A system engineering agile development method facing uncertain demand and rapid technology change is characterized by comprising the following steps:
the method comprises the steps of constructing unit-level prototype products based on top level requirements of a system layer and top level requirements of the system layer, performing test identification on the constructed unit-level prototype products in a preset environment or an actual measurement environment respectively, performing system integration verification, performing iteration on the unit-level prototype products step by step according to the bottom level requirements of the system layer and the bottom level requirements of the system layer to generate iterated unit-level prototype products, and performing test identification and system integration verification on the iterated unit-level prototype products to rapidly develop system engineering.
2. The method of claim 1, wherein the step of building a prototype product at a unit level based on top level requirements of a hierarchy level comprises:
identifying key design parameters concerned by the top-level requirements of the system level based on the top-level requirements of the system level;
optimizing performance by adjusting the key design parameters to meet the top level requirements of the hierarchy level;
optimizing through simulation and simulation, building and developing unit-level prototype products based on the top-level requirements of the system layer for testing, and tracking the change of the key design parameters;
performing test qualification on the prototype product of the unit level to verify whether the prototype product of the unit level meets the top-level requirement of the system layer.
3. The method of claim 3, wherein upon verifying that the prototype product at the unit level meets the top-level requirements of the hierarchy layer, the method further comprises:
and iterating the bottom layer requirements of each layer of the system layer step by step according to a processing method of the top layer requirements of the system layer to respectively generate iterated unit-level prototype products, and performing test identification and system integration verification on the iterated unit-level prototype products to verify whether the iterated unit-level prototype products meet the bottom layer requirements of the corresponding system layer.
4. The method of claim 3, wherein after verifying that the prototype product at each unit level meets the underlying requirements of the corresponding hierarchy level, the method further comprises:
and constructing the prototype products of each unit level to obtain an integral prototype product of the system layer, identifying the integral prototype product in a preset environment or an actual measurement environment, and performing system integration verification.
5. The method according to any one of claims 1-4, wherein the step of building a prototype product at a unit level based on top level requirements of a system layer comprises:
identifying key design parameters concerned by top-level requirements of a system layer based on the top-level requirements of the system layer;
optimizing performance by adjusting the key design parameters to meet top-level requirements of the system layer;
optimizing through simulation and simulation, building and developing unit-level prototype products based on top-level requirements of the system layer for testing, and tracking changes of the key design parameters;
performing a trial qualification on the prototype product at the unit level to verify that the prototype product at the unit level meets the top-level requirements of the system layer.
6. The method of claim 5, wherein upon verifying that the prototype product at the unit level meets the top-level requirements of the system layer, the method further comprises:
and iterating the bottom layer requirements of each layer of the system layer step by step according to a processing method of the top layer requirements of the system layer to respectively generate iterated unit-level prototype products, and performing test identification and system integration verification on the iterated unit-level prototype products to verify whether the iterated unit-level prototype products meet the bottom layer requirements of the corresponding system layer.
7. The method of claim 6, wherein after verifying that the prototype product at each unit level meets the underlying requirements of the corresponding system layer, the method further comprises:
and constructing the prototype products of all unit levels to obtain an integral prototype product of a system layer, identifying the integral prototype product in a preset environment or an actual measurement environment, and performing system integration verification.
8. The method of claim 7, further comprising:
and constructing the whole prototype product of the system layer and the whole prototype product of the system layer to obtain a final whole prototype product, and identifying and integrally verifying the final whole prototype product in a preset environment or an actual measurement environment.
9. The method of any of claims 1-3, wherein prior to constructing a prototype product based on top-level requirements of a system layer and top-level requirements of a system layer, the method further comprises:
and respectively converting the top layer requirement and the bottom layer requirement based on the system layer, and the top layer requirement and the bottom layer requirement of the system layer into technical requirements.
10. The method according to any one of claims 1-3, further comprising: a system overall unit and a plurality of system development units are arranged;
the system overall unit is used for carrying out system-level strategy decision;
the system development unit is used for carrying out system-level policy decision.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110678206.XA CN113536542A (en) | 2021-06-18 | 2021-06-18 | System engineering agile development method for uncertain demand and rapid technology change |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110678206.XA CN113536542A (en) | 2021-06-18 | 2021-06-18 | System engineering agile development method for uncertain demand and rapid technology change |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113536542A true CN113536542A (en) | 2021-10-22 |
Family
ID=78125214
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110678206.XA Pending CN113536542A (en) | 2021-06-18 | 2021-06-18 | System engineering agile development method for uncertain demand and rapid technology change |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113536542A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113988617A (en) * | 2021-10-27 | 2022-01-28 | 中国航空综合技术研究所 | System test diagnosis demand decomposition calculation method based on comprehensive efficiency evaluation |
| CN114638031A (en) * | 2022-01-12 | 2022-06-17 | 中国船舶工业系统工程研究院 | Complex engineering system construction process improvement system and terminal |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060064178A1 (en) * | 2004-09-07 | 2006-03-23 | The Boeing Company | System, method and computer program product for developing a system-of-systems architecture model |
| CN109542397A (en) * | 2018-09-29 | 2019-03-29 | 中国航空无线电电子研究所 | Architecture tools chain integrated approach |
| CN111142845A (en) * | 2019-12-18 | 2020-05-12 | 中国北方车辆研究所 | Model-based task system demand development method |
| CN111460691A (en) * | 2020-04-26 | 2020-07-28 | 上海烜翊科技有限公司 | Monte Carlo simulation analysis system and method based on system architecture model |
-
2021
- 2021-06-18 CN CN202110678206.XA patent/CN113536542A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060064178A1 (en) * | 2004-09-07 | 2006-03-23 | The Boeing Company | System, method and computer program product for developing a system-of-systems architecture model |
| CN109542397A (en) * | 2018-09-29 | 2019-03-29 | 中国航空无线电电子研究所 | Architecture tools chain integrated approach |
| CN111142845A (en) * | 2019-12-18 | 2020-05-12 | 中国北方车辆研究所 | Model-based task system demand development method |
| CN111460691A (en) * | 2020-04-26 | 2020-07-28 | 上海烜翊科技有限公司 | Monte Carlo simulation analysis system and method based on system architecture model |
Non-Patent Citations (2)
| Title |
|---|
| 上海介方信息: "重新审视你的"系统工程"一一SpaceX对系统工程的颠覆认知", 《URL:SDRCHINA.ORG/NEWS-INFORM3.HTML》, pages 1 - 8 * |
| 林海涛等: "大型复杂电子体系工程风险传递机制研究", 《现代信息科技》, vol. 5, no. 5, pages 55 - 59 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113988617A (en) * | 2021-10-27 | 2022-01-28 | 中国航空综合技术研究所 | System test diagnosis demand decomposition calculation method based on comprehensive efficiency evaluation |
| CN114638031A (en) * | 2022-01-12 | 2022-06-17 | 中国船舶工业系统工程研究院 | Complex engineering system construction process improvement system and terminal |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Tao et al. | Digital twin modeling | |
| McKinney et al. | Interactive 4d-cad | |
| Tomiyama et al. | Design methodologies: Industrial and educational applications | |
| Berardinelli et al. | Model-driven systems engineering: Principles and application in the CPPS domain | |
| CN113536542A (en) | System engineering agile development method for uncertain demand and rapid technology change | |
| Reyes-Delgado et al. | The strengths and weaknesses of software architecture design in the RUP, MSF, MBASE and RUP-SOA methodologies: A conceptual review | |
| Eastman et al. | Introducing a new methodology to develop the information delivery manual for AEC projects | |
| McMahon | Design informatics: supporting engineering design processes with information technology | |
| Haymaker et al. | Perspectors: composable, reusable reasoning modules to construct an engineering view from other engineering views | |
| Duda et al. | Product lifecycle management (PLM) in the context of industry 4.0 | |
| Saraireh et al. | Understanding the conceptual of building information modeling: a literature review | |
| Nascimento et al. | A model-driven infrastructure for developing product line architectures using cvl | |
| Heikkinen | Transparency of design automation systems using visual programming–within the mechanical manufacturing industry | |
| Ham et al. | BIM based construction project case analysis for facility life cycle management from the perspective of the client | |
| Moones et al. | Design process and trace modelling for design rationale capture | |
| Pasquinelli et al. | Extending the system model | |
| Firat et al. | From process models towards total building project management | |
| Ren et al. | Integrated Design Platform for Model-Based Reliability System Engineering | |
| van Tooren et al. | Systems engineering and multi-disciplinary design optimization | |
| Albayati et al. | A Model-Based Engineering Approach for Evaluating Software-Defined Radio Architecture. Systems 2023, 11, 480 | |
| Choi et al. | Analyzing complex design processes: The effects of task automation and integration on process structure in microprocessor design | |
| Tommelein | Expert Systems for Civil Engineers: Integration Issues | |
| Ye | Application of Computer CAD Software Optimization in the Manufacture of Mechanical Reducer Considering Artificial Intelligence | |
| Filimonov et al. | Graph-based modelling of systems interaction in model-based systems engineering environment | |
| Lanzotti et al. | Towards the DTT configuration management platform architecture |
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 |