• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    A process for designing, from models, software essential for safety, is presented. The method comprises receiving (132) software requirements in natural language, developing (133) a specification model by implementing semantic modeling (150) or graphical modeling (152), the application from a formal requirements analysis to the specification model, the automated creation of robustness test cases and based on requirements and procedures from the specification model, the application of test cases to the design model, the automated creation of source code using the design model, source code verification using test cases and static analysis technology; and compiling an executable object code from the verified source code; a result of the analysis of the specification or software design models is not satisfactory, the adjustment of the specification or software design model to correct any inconsistency, and the repetition of the application of the analysis and test cases. A system for implementing model-based design and non-transitory, computer-readable support is presented.
    公开号:FR3039908A1
    申请号:FR1657522
    申请日:2016-08-03
    公开日:2017-02-10
    发明作者:Timothy Lee Johnson；Andrew Walter Crapo；Michael Richard Durling；Alexander Walsch；Kit Yan Siu；Luca Parolini；Panagiotis Manolios；Meng Li；Han Yu；Scott Alan Stacey；Gregory Reed Sykes
    申请人:General Electric Co；
    IPC主号:
    专利说明:

    System and method for technology based models and processes for the development of software essential for safety
    The generalization of microprocessor-controlled equipment has resulted in devices with ever-increasing capabilities, but gives a more critical role to the reliability of the software that controls these embedded systems. Many potentially hazardous equipment is controlled by embedded software (eg automobiles, trains, aircraft, oil refineries, chemical processing plants, nuclear power plants, medical devices, etc.). Traditional solutions for verifying that an operational application code is suitable for these devices and systems are tricky and inefficient.
    The development of software systems essential for safety responds to the increasing size and complexity of these systems and is part of the need to maintain operations that are essential for safety. There are all kinds of software engineering processes, tools, and environments for building complex, critical systems. For example, one method is to apply model-driven engineering techniques to develop critical safety systems.
    Prior art solutions may include the use of integrated development environment (IDE) tools to perform software specification modeling, validation / verification, and test case creation and execution. Typically, these tools use rigorous processes to automate or semi-automate some of the detailed design steps while reducing the need for data entry to save time with the remaining steps. The invention will be better understood from the detailed study of some embodiments taken by way of nonlimiting examples and illustrated by the appended drawings in which: FIG. 1 represents a system for design, based on models, of essential software for security according to embodiments; FIG. 2 represents a flowchart of a process for model-based design of essential security software according to embodiments; and FIG. 3 represents a flowchart for a model-based debugging process according to embodiments.
    In accordance with embodiments of the invention, systems and methods provide an automated model-based design process for developing and creating tests for software essential to security. The implementation of systems and processes employs a domain-specific ontology and formal verification processes to enhance and extend high-level requirements. These systems and methods use a verifiable specification model (hence the term "model-based") as a basis for automated test-based creation prior to writing the software. In embodiments, the requirements-based tests are created from the specification template. A design template is used to develop the software. The rigor and automation of these steps have the effect of improving software design and reducing test work, saving time and cost savings for a software designer critical to safety.
    By including formal processes and logic models in the implementation processes, errors in specification requirements can be identified and the consistency and completeness of requirements can be verified. As errors in the specifications are detected, it can be remedied, iteratively if necessary, until they are logically complete and consistent when the test is repeated. Ontologies, semantic networks, and coverage analysis all provide explicit information to extend requirements that are incomplete.
    The implementation of systems and processes may include "safety situations" in the requirements and the corresponding verification steps (eg, model-based design). Complex temporal relationships (eg competition requirements and / or capabilities) can also be represented.
    Once the requirements of a software specification are complete and consistent, design templates and subsequent verification / validation tests can be created to test the source code. The source code may be perceived as a more detailed representation of the specified design, resulting in object and / or executable code that implements the same design requirements.
    The implementation of systems and processes has the effect of reducing errors detected during verification / validation operations. The implementation of systems and processes automates these processes, resulting in a more rigorous design / verification / validation process to reduce associated labor and development time costs by ensuring a more efficient process. High accuracy in meeting design requirements and higher speed during corrections and tests compared to manual manual tool-assisted code creation.
    The implementation of model-based systems and processes substitutes formal, mathematically rigorous logical formulations that define operational, design, and test-creation requirements for natural language-based formulations, providing an opportunity, At the beginning of the design process, improve the quality, rigor, consistency and scope of the requirements.
    Figure 1 shows a system 100 for developing an essential computer software for security according to one embodiment. The system 100 may comprise a computer (either a single computer 110 operating locally or several computers 112, 114, 11N connected to each other via an electronic communications network 120 (eg the Internet), a base associated data sheet 130 which may contain features of the software essential for safety - eg system requirements assigned to the software (SRATS) 132, a software specification template 133, a design template 134, a source code created automatically 136, an executable object code 138. The system 100 may also include a database 140 that may contain semantic networks 142, ontologies 144, test cases 146 based on requirements and cases of coverage tests 148 Although database 130 and database 140 are represented as two databases, in some implementations a single database data can contain all stored information; in other implementations, the system 100 may have more than two databases.
    According to one implementation, the single computer 110 may include structural units designed to perform actions that implement the model-based software design essential for safety. These units may include a semantic modeling unit 150, a graphical modeling unit 152, an Automated Theorem Demonstration Unit (ATP) 154, a Test Case Creation and Procedure Unit (ATCPG) 156 and a creation unit In other implementations, these units may be distributed among the different computers in relation to one another via the electronic communications network.
    Figure 2 shows a flowchart of the essential model-based software design process for security according to embodiments. The process 200 analyzes SRATS in natural language, develops a model of specifications which, after verification and acceptance, forms the basis for a design model. The term "design model" (as used in this description) refers to a conceptual model such as an object model or a Unified Modeling Language (UML) model. A design model can describe the entities and functional transformations to be performed by the application software. From the design model, a first source code can be automatically created by the process 200, and an executable object code (EOC) can also be created. The process 200 can check the design, the source code, and the EOC. The resulting EOC from this requirements-based process can then be subjected to EOC-based test procedures, which can provide additional information.
    The specification template is entered at step 205. The capture may include validation of the SRATS of the natural language system requirements provided to the system. The semantic modeling unit 150 and / or the graphical modeling unit 152 implements semantic and graphical modeling techniques to develop a specification model from the SRATS. The specification model is implemented in a structured natural language that includes a semantic model and can be accessed or modified in a graphical form.
    An analysis of the formal requirements on the specification model is performed, step 210. The ATP unit 154 can analyze the specification model and verify that it is fair and consistent by implementing automated theorem demonstration techniques. Test cases from the specification template are created automatically, step 215, by the ATCPG unit 156. According to the embodiments, the system may employ the ATCPG to automatically create test cases for the model requirements. of design itself. In other implementations the automatically created test cases can be automatically created by the system 100 using a model control or other formal analysis technology. Process 200 may return to step 205 to further enter the specification template if the requirement analysis and / or automatically created test cases indicate that the model is not as robust as necessary (c). that is, the software specification model lacks the consistency, accuracy, and / or completeness required).
    After the requirements analysis has indicated that the requirements are complete and consistent, the specification template forms the basis for developing a software design template, step 220. Test cases are created from the model specifications and are applied to the design template. After applying the test cases to the design model, model coverage is analyzed, step 225, based on its performance. Any defects and inconsistencies are corrected, then the design pattern can be checked, step 230, by repeating the scenarios of the test cases.
    The verified design pattern is used by the automated code creation unit 158 to automatically create, step 235, a source code for the software essential for security. The system 100 then checks, step 240, the source code using a static analysis technology. An executable object code is compiled, step 245, from the verified source code.
    Figure 3 shows a flow chart for a model-based development process 300 according to embodiments. The system 100 for developing a security essential computer software may include computer-implemented applications 315, 320, 335, 340, 350, 360, 370 that receive design information from stages 305, 310, 325, 330, 350, 355, 365 of the model-based development process 300. In some implementations, the received design information may be supplemented by additional commands and instructions from human users of the system 100. From the received design information, processed by the computer implementation applications of the system 100 , process 300 can produce new results - for example: completeness confirmation, design templates, new software tests, and / or messages identifying defects that specify a drawback or lack of completeness of design data for a stadium particular of the design process.
    If a fault identification message is produced, the process 300 then returns to the data of the previous step (indicated by a bidirectional arrow connecting various steps within the process 300). The defect can be corrected by a human user following a recommendation provided by the computer-implemented process 300.
    The initial SRATS data provided to process 300, step 305, includes natural language documents. System 100 for the development of critical computer software for security automatically creates the software and automatically creates test cases, as well as other diagnostic information or documents produced at earlier stages. This software, test cases, other diagnostic information or documents are based on the provided SRATS. The process 300 implemented by the system 100 improves the software design essential for safety with a decrease in manual interactions in the design process. To perform the automated debugging, according to embodiments, the process 300 includes application-based application validation based on a client model (step 315), formal requirement analysis (step 320), a formal verification of the design (step 335), analysis of the model's coverage (step 340), testing of the test-based design model (step 350), formal code verification (step 360), verification of the model EOC based on tests (step 370).
    The process 300 begins with the receipt, step 305, of text-based natural language SRATS documents derived from higher-level system requirements that include hardware and software resources. From the SRATS, a Specification Model is developed, step 310, using a combination of semantic modeling and graphical modeling technologies. According to embodiments, the system 100 implementing the process 300 has eliminated the need to take High Level Requirements (HLRs) as text. In accordance with embodiments, the conventional HLRs are replaced by a Human- and Machine-Operable Specification Model.
    The Specification Model is validated, step 315. The validation can be done using analytical representations (eg ontologies and semantic networks) of the requirements presented to a user. The accuracy and consistency of the Specifications Model is formally analyzed and verified using ATP applications, step 320. This step may identify errors in the requirements at the beginning of the process. and greatly reduce reworking at the end of the cycle.
    There is a feedback loop between requirement analysis 320 and specification model 310 input. This feedback loop responds in real time to alert a technician in the event of an error.
    After validation and formal requirements analysis, the Specification Template becomes an entry to create, step 330, a Design Template. The Design Model undergoes a formal edit using a model control, step 335. The Specification Template also serves as an entry into the Automated Case-Based Test Case Creation Process, step 325. Test cases and procedures are created automatically (eg using model control technology). The test cases are then applied, step 350, to
    Design template and analysis establishes if they are well functional.
    There is another feedback loop between the requirement-based test case creation function 325 and the specification model 310 to indicate a verification complexity measure that is proportional to the number of test cases required to verify the test pattern. specifications. The technician entering the requirements can use this information to simplify the specification model to reduce the cost / complexity of the verification. Depending on implementations, the requirements entry tool may also provide suggestions for options for entering the same information into a grammar that would be easier to verify (fewer test cases).
    If errors are detected, the design template is corrected. Defects and inconsistencies can be detected in circumstances where a sequence of steps is performed, or if the order of parallel steps is not predictable: in these circumstances, corrections can be made to the design model by repeating the sequences in reverse or by chronological ordering of otherwise unordered steps. Then, the test cases are applied to the Design Model and are subject to a model coverage analysis (step 340). This step can identify coverage gaps based on (a) errors in requirements-based tests, specification model and / or design model (eg, unintended functionality, dead code, etc.); or (b) derived requirements. In the case of derived requirements, test cases are automatically created, step 345, to satisfy the model's coverage.
    An automated test creation tool can be used to help a technician identify inaccessible code and to identify a test vector that will execute the specific section of the model. A qualified tool for automated code creation is used to create, step 355, a source code from the design template. The source code undergoes a formal analysis, step 360, using static analysis technology. The source code is compiled, step 365, to be transformed into EOC. The test-based verification of the EOC is performed, step 370, by reapplying the previously developed test suite in the process. At the end of the verification, the compiled EOC can then undergo standard unit, subsystem and system tests.
    The systems and methods according to the embodiments apply rigorous mathematical and logical modeling techniques to the problem of checking consistency, correctness and / or completeness of software requirements before creating a code. According to implementations, a collection of tools can cover all stages of preliminary design, analysis and software creation. Due diligence facilitates the use of automated code creation and the use of feedback in the design process. The implementation of processes and systems can detect errors during design and preliminary design operations. The correction of these detected errors can extend, improve, correct and / or supplement the design information before the creation of a code.
    According to some embodiments, a computer program application stored in a nonvolatile memory or on a computer-readable medium (eg, a register memory, a processor cache memory, a random access memory, a read only memory, a compact disc read-only memory, hard disk, flash memory, magnetic media, etc.) may include code or executable instructions which, when executed, may request a controller or processor, or bring a controller or a processor, to perform processes presented herein, such as a method described above for designing, from models, software essential for safety.
    The computer-readable medium may consist of computer-readable non-transitory storage media including all forms and types of memory and all computer-readable media, except for a propagating transient signal. In one implementation, nonvolatile memory or non-transitory computer-readable medium may be external memory.
    List of landmarks
    NUMBER DESIGNATION 100 Computer Software Development System Critical to Security 110 Computer 112 Computer 114 Computer 11N Computer 120 Electronic Communications Network 130 Database 132 System Requirements Assigned to Software 133 Software Specification Template 134 Design Template 136 Code automatically created source 138 Executable object code 140 Database 142 Semantic networks 144 Ontologies 146 Requirement-based test cases 148 Automatically generated model coverage test case 150 Semantic Modeling Unit 152 Graphic Modeling Unit 154 Automated Demonstration Unit theorems 156 Automated case creation unit for tests and procedures 158 Automated code creation unit
    权利要求:
    Claims (9)
    [1" id="c-fr-0001]
    A method for designing, from templates, software essential to security, the method comprising: receiving (132) software requirements in natural language; developing (133) a software specification model in a structured natural language by implementing semantic modeling (150) and / or graphical modeling (152) of software requirements in natural language; applying a formal requirements analysis to the software specification model; the development of a software design model based on the specification template; applying, to the software design model, robustness test cases based on the automatically created requirements; performing a formal analysis of the software design model; automated creation (136) of source code using the software design model; verifying the coverage and behavior of the source code by the application of automatically created test cases (148) and static analysis technology; compiling an executable object code from the verified source code; and checking the coverage and behavior of the executable object code by the application of the automatically created test cases.
    [2" id="c-fr-0002]
    The method of claim 1, comprising an automated case creation unit of tests and procedures automatically creating the test cases from the software specification template.
    [3" id="c-fr-0003]
    3. Method according to claim 1, comprising an automated theorem demonstration unit implementing automated theorem demonstration techniques for analyzing and verifying consistency and / or accuracy and / or completeness of the software specification model.
    [4" id="c-fr-0004]
    The method of claim 1 including, if a result of the analysis of the software specification model is unsatisfactory, adjusting the software specification template to correct any inconsistency with the software requirements in language. natural.
    [5" id="c-fr-0005]
    The method of claim 4 including applying the requirement analysis to the adjusted software specification module.
    [6" id="c-fr-0006]
    The method of claim 1, including an automated case creation unit of robustness and requirements based tests, and procedures automatically creating the test cases applied to the software design model.
    [7" id="c-fr-0007]
    The method of claim 1, comprising the use of a model control technology to create the robustness test cases and based on requirements applied to the software design model.
    [8" id="c-fr-0008]
    The method of claim 1 including, if a result of the analysis of the software design model is unsatisfactory, adjusting the software design template to correct any inconsistencies with the software specification template. .
    [9" id="c-fr-0009]
    The method of claim 8 including applying the test cases to the adjusted software design model.
    类似技术:
    公开号 | 公开日 | 专利标题
    FR3039908A1|2017-02-10|SYSTEM AND METHOD FOR MODEL-BASED TECHNOLOGY AND PROCESSES FOR THE DEVELOPMENT OF ESSENTIAL SOFTWARE FOR SECURITY
    US10642721B2|2020-05-05|Generation of automated testing scripts by converting manual test cases
    US8819642B2|2014-08-26|Method and system for generating and processing black box test cases
    US8745641B1|2014-06-03|Automatic verification and anomaly detection in a representational state transfer | application programming interface
    FR3044126A1|2017-05-26|SYSTEM AND METHOD FOR AUTOMATICALLY CREATING TEST CASES BASED ON REQUIREMENTS RELATING TO CRITICAL SOFTWARE
    US9170921B2|2015-10-27|Application testing automation
    US9804946B2|2017-10-31|System and method for providing automated computer language translation and verification
    US9081595B1|2015-07-14|Displaying violated coding rules in source code
    US9244510B1|2016-01-26|Bug report checks in a modeling system
    US9940215B2|2018-04-10|Automatic correlation accelerator
    US20140331209A1|2014-11-06|Program Testing Service
    US10146672B2|2018-12-04|Method and system for automated user interface | testing through model driven techniques
    JP2009087352A|2009-04-23|Configurable web services system and method to detect defects in software applications
    de Cleva Farto et al.2017|Reuse of model-based tests in mobile apps
    WO2020096665A2|2020-05-14|System error detection
    Ahmad et al.2021|Empirical analysis of practitioners' perceptions of test flakiness factors
    US20190129832A1|2019-05-02|System and method for test data generation for use in model based testing using source code test annotations and constraint solving
    Joshi et al.2007|Automatic generation of fault trees from AADL models
    CN110716855B|2021-05-14|Processor instruction set testing method and device
    Rivero et al.2013|An approach for the elicitation of usability requirements in the development of web applications
    Johnsen2018|Quality Assurance for Dependable Embedded Systems
    Tanrıöver et al.2015|An emprical analysis of early object oriented design metrics in relation to code size
    Kocbek et al.2013|Beta Testing of a Mobile Application: A Case Study.
    Jomeiri2014|Validation Tools in Software Testing Process: A Comparative Study.
    Kearns2021|Auto-Trust: Technical Report
    同族专利:
    公开号 | 公开日
    CN106528100A|2017-03-22|
    JP6621204B2|2019-12-18|
    GB2542687A|2017-03-29|
    JP2017033562A|2017-02-09|
    US10346140B2|2019-07-09|
    CN106528100B|2020-06-09|
    CA2937677A1|2017-02-05|
    GB201613356D0|2016-09-14|
    BR102016018127A2|2017-06-06|
    US20170039039A1|2017-02-09|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    US7739671B1|2003-12-22|2010-06-15|The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration|Systems, methods and apparatus for implementation of formal specifications derived from informal requirements|
    EP2369528A1|2010-03-23|2011-09-28|Siemens Aktiengesellschaft|Information processing apparatus, method and protocol for generation of formal requirements specification models|
    US6681383B1|2000-04-04|2004-01-20|Sosy, Inc.|Automatic software production system|
    US7131000B2|2001-01-18|2006-10-31|Bradee Robert L|Computer security system|
    GB0113946D0|2001-06-08|2001-11-14|Secr Defence|Automatic Development of Software Codes|
    US20050020945A1|2002-07-02|2005-01-27|Tosaya Carol A.|Acoustically-aided cerebrospinal-fluid manipulation for neurodegenerative disease therapy|
    US7480893B2|2002-10-04|2009-01-20|Siemens Corporate Research, Inc.|Rule-based system and method for checking compliance of architectural analysis and design models|
    US7228524B2|2002-12-20|2007-06-05|The Boeing Company|Method and system for analysis of software requirements|
    US20070074180A1|2003-12-22|2007-03-29|Nasa Hq's|Systems, Methods and Apparatus for Procedure Development and Verification|
    US7685576B2|2004-01-26|2010-03-23|Siemens Corporation|System and method for model based system testing of interactive applications|
    US7392509B2|2004-04-13|2008-06-24|University Of Maryland|Method for domain specific test design automation|
    GB0410047D0|2004-05-05|2004-06-09|Silverdata Ltd|An analytical software design system|
    US7865339B2|2004-07-12|2011-01-04|Sri International|Formal methods for test case generation|
    EP1622022A1|2004-07-22|2006-02-01|Siemens Aktiengesellschaft|Automatic generation of test cases|
    JP2007122135A|2005-10-25|2007-05-17|Hitachi Ltd|Development support device, development support method and development support program|
    EP1832975A1|2006-03-09|2007-09-12|Alcatel Lucent|Automatic generation of source program|
    US7523425B2|2006-04-21|2009-04-21|Alcatel-Lucent Usa Inc.|Test case generation algorithm for a model checker|
    US8176470B2|2006-10-13|2012-05-08|International Business Machines Corporation|Collaborative derivation of an interface and partial implementation of programming code|
    US20090089618A1|2007-10-01|2009-04-02|Fujitsu Limited|System and Method for Providing Automatic Test Generation for Web Applications|
    US8307342B2|2008-05-14|2012-11-06|Honeywell International Inc.|Method, apparatus, and system for automatic test generation from statecharts|
    JP2009294846A|2008-06-04|2009-12-17|Denso Corp|Test case generator, and test case generation program and method|
    US8359576B2|2008-11-14|2013-01-22|Fujitsu Limited|Using symbolic execution to check global temporal requirements in an application|
    US20110083121A1|2009-10-02|2011-04-07|Gm Global Technology Operations, Inc.|Method and System for Automatic Test-Case Generation for Distributed Embedded Systems|
    US20110125302A1|2009-10-23|2011-05-26|Gm Global Technology Operations, Inc.|Method and system for formal safety verification of manufacturing automation systems|
    US20120143570A1|2010-12-03|2012-06-07|University Of Maryland|Method and system for ontology-enabled traceability in design and management applications|
    CN102136047A|2011-02-25|2011-07-27|天津大学|Software trustworthiness engineering method based on formalized and unified software model|
    US20120246612A1|2011-03-23|2012-09-27|Siemens Corporation|System and method for verification and validation of redundancy software in plc systems|
    JP2013058068A|2011-09-08|2013-03-28|Panasonic Corp|Program of platform and terminal device mounted with the same|
    KR101408870B1|2012-11-06|2014-06-17|대구교육대학교산학협력단|Apparatus and method for multi level tast case generation based on multiple condition control flow graph from unified modeling language sequence diagram|
    WO2014087427A1|2012-12-05|2014-06-12|Tata Consultancy Services Limited|Method and system for computational design and modeling|
    WO2014115189A1|2013-01-28|2014-07-31|Nec Corporation|Method and system for transforming specification scripts to program code|
    JP2015005189A|2013-06-21|2015-01-08|株式会社オートネットワーク技術研究所|Ecu evaluation device, computer program, and ecu evaluation method|
    WO2015040735A1|2013-09-20|2015-03-26|株式会社日立製作所|Formal verification assistance device for software specifications and method thereof|
    CN103530228B|2013-09-27|2016-09-28|西安电子科技大学|A kind of method for testing software based on model|
    CN103678636A|2013-12-19|2014-03-26|中山大学深圳研究院|System and method for improving reliability of component software system|
    CN103955427B|2014-04-29|2016-08-24|探月与航天工程中心|A kind of safety concern system software security ensure implementation method|
    CN104182591A|2014-09-02|2014-12-03|浪潮电子信息产业有限公司|Software test requirement modeling method|
    CN104461882B|2014-11-29|2017-05-17|中国航空工业集团公司第六三一研究所|Method for model verification of software conforming to DO-178B/C A level|
    US10108536B2|2014-12-10|2018-10-23|General Electric Company|Integrated automated test case generation for safety-critical software|
    US9747079B2|2014-12-15|2017-08-29|General Electric Company|Method and system of software specification modeling|
    US10346140B2|2015-08-05|2019-07-09|General Electric Company|System and method for model based technology and process for safety-critical software development|US10346140B2|2015-08-05|2019-07-09|General Electric Company|System and method for model based technology and process for safety-critical software development|
    US9804954B2|2016-01-07|2017-10-31|International Business Machines Corporation|Automatic cognitive adaptation of development assets according to requirement changes|
    US9792204B2|2016-02-02|2017-10-17|General Electric Company|System and method for coverage-based automated test case augmentation for design models|
    US20180165180A1|2016-12-14|2018-06-14|Bank Of America Corporation|Batch File Creation Service|
    CN107016085A|2017-03-31|2017-08-04|海通安恒科技有限公司|A kind of computerized system verification management system|
    EP3493051A1|2017-11-30|2019-06-05|The MathWorks, Inc.|System and methods for evaluating compliance of implementation code with a software architecture specification|
    DE102018003142A1|2017-12-13|2019-06-13|The Mathworks, Inc.|Automatic setting of multitasking configurations for a code checking system|
    JP6962867B2|2018-06-04|2021-11-05|矢崎総業株式会社|Vulnerability assessment device|
    US10585779B2|2018-07-30|2020-03-10|General Electric Company|Systems and methods of requirements chaining and applications thereof|
    US10691584B2|2018-09-28|2020-06-23|Sap Se|Behavior driven development integration with test tool|
    EP3637249A1|2018-10-12|2020-04-15|Tata Consultancy Services Limited|Systems and methods for validating domain specific models|
    CN109542452A|2018-11-19|2019-03-29|万惠投资管理有限公司|A kind of operation management method and system based on AI semantic analysis|
    WO2019242868A1|2018-12-12|2019-12-26|Mitsubishi Electric Corporation|Software testing device, software testing method, and software testing program|
    FR3091106B1|2018-12-20|2021-02-12|Commissariat Energie Atomique|Formal communications supervision system|
    CN113519018A|2019-03-12|2021-10-19|三菱电机株式会社|Mobile body control device and mobile body control method|
    CN112180890B|2019-07-05|2022-01-07|北京新能源汽车股份有限公司|Test case generation method, device and equipment|
    CN110445690A|2019-08-16|2019-11-12|北京智芯微电子科技有限公司|The design method of electric power wireless public network communication unit interchangeability test software|
    US11200069B1|2020-08-21|2021-12-14|Honeywell International Inc.|Systems and methods for generating a software application|
    法律状态:
    2017-08-25| PLFP| Fee payment|Year of fee payment: 2 |
    2018-07-20| PLFP| Fee payment|Year of fee payment: 3 |
    2019-07-22| PLFP| Fee payment|Year of fee payment: 4 |
    2020-07-21| PLFP| Fee payment|Year of fee payment: 5 |
    2021-07-22| PLFP| Fee payment|Year of fee payment: 6 |
    优先权:
    申请号 | 申请日 | 专利标题
    US14/819,167|US10346140B2|2015-08-05|2015-08-05|System and method for model based technology and process for safety-critical software development|
    [返回顶部]