General Electric Company

Northeastern University

Panagiotis Manolios

Meng Li

Han Yu

Michael Richard Durling

Andrew Walter Crapo

Luca Parolini

Scott Alan Stacey

Gregory Reed Sykes

Kit Yan Siu

Augusto Marasca De Conto

Timothy Lee Johnson

Italo Romani De Oliveira

Hongwei Liao

Kevin Michael Jones

Daniel Edward Russell

Daniel Joseph Russell

Alexander Walsch

Kevin John Jones

Italo Oliveira

Evgueni I Goldberg

Sundeep Roy

Augusto De Conto

A system for equivalence class analysis-based automated requirements-based test case generation includes a control processor, a data store containing textual design requirements, a textual converter unit structured to convert the textual design requirements to a machine-readable version of design requirements, a requirement partition unit configured to partition the machine-readable design requirements into one or more sets of related design requirements, an equivalence class partition unit configured to process the machine-readable design requirements and input/output variables into a set of equivalence classes, an equivalence class analyzer unit structured to analyze the set of equivalence classes to generate equivalence class tests and identify uncovered input space, and a boundary class analyzer unit structured to identify boundaries of the equivalence classes and generate boundary value tests and robustness tests. A method for equivalence class analysis-based automated requirements-based test case generation implementable on the system, and a non-transitory computer readable medium are also disclosed.

System and method for equivalence class analysis-based automated requirements-based test case generation

A method for model-based design of safety-critical software is disclosed. The method includes receiving natural-language software requirements, developing a specification model by implementing either semantic modeling or graphical modeling, applying formal requirements analysis to the specification model, auto generating requirements based and robustness test cases from the specification model, developing a design model based on the specification model, applying test cases to the design model, auto-generating source code using the design model, verifying the source code using both test cases and static analysis technology, and compiling executable object code from the verified source code. If a result of the analysis of the software specification or design models is not satisfactory then adjusting the specification or design model to correct any inconsistency, and repeating applying the analysis and test cases. A system for implementing the model-based design and a non-transitory computer readable medium are disclosed.

System and method for model based technology and process for safety-critical software development

A system and method of multi-level scheduling analysis for a general processing module of a real-time operating system. The method includes identifying any processes within respective partitions of the general processing module, for each identified process, determining if the process is local-time centric or global-time centric. The method converts global-time centric process to a local-time centric process, applies a single-level scheduling analysis technique to the processes of respective partitions, and transforms local-time based response times to global-time based response times. The method performs scheduling and response time analyses on one or more of the identified processes of respective partitions. The method can be performed on a synchronous and/or asynchronous system, and on a hierarchical scheduling system that includes a top level scheduler having a static-cyclic schedule and/or a general static schedule. A system and non-transitory computer-readable medium are also disclosed.

System and method for multi-level real-time scheduling analyses

According to some embodiments, a system includes a communication device operative to communicate with a user to obtain the one or more requirements associated with a specification model for a semantic module; a semantic module to receive the one or more requirements, store the one or more requirements and transform the one or more requirements into a semantic model; a specification module to receive the semantic model, store the semantic model, translate the semantic model and generate a specification model; a memory for storing program instructions; at least one specification model platform processor, coupled to the memory, and in communication with the specification module and the semantic module and operative to execute program instructions to: transform the one or more requirements into a semantic model by executing the semantic module; translate the semantic model into a graphical model by executing the specification module; and modify the graphical model by executing the specification module to generate the specification model; and generate a specification model that is human-readable and computer-readable for use in software design. Numerous other aspects are provided.

Method and system of software specification modeling

According to some embodiments, a system and method are provided for analyzing formal system requirements for software and hardware components in a software and hardware component specification model comprising receiving at least one requirement defined using a formal notation; determining if each of the requirements is self-conflicting via execution of a self-conflicting module; determining if two or more requirements conflict with each other via execution of a set-conflicting module after execution of the self-conflicting module; identifying each requirement involved in a conflict and how the one or more requirements conflicts via execution of an error localization module; receiving an updated requirement; repetitively analyzing each updated requirement with the self-conflicting module and the set-conflicting module; and generating an indication that requirements analysis is complete for the one or more requirements and the one or more requirements is validated for use in software design. Numerous other aspects are provided.

Scalable methods for analyzing formalized requirements and localizing errors

A new method is presented for eliminating existential quantifiers from a Boolean CNF (Conjunctive Normal Form) formula. This new method designs circuits by solving a quantifier elimination problem (QEP) by using derivation of dependency sequents (DDS). This new method begins with a first quantified conjunctive normal form formula, determines dependency sequents for the left branch and the right branch of a branching variable, resolves dependency sequents derived in both branches, and designs a circuit using a current formula having less variables than the first quantified conjunctive normal formula. Utility of this method includes verification, in particular, determining reachability of a state of a design.

Quantifier elimination by dependency sequents

Growing community of inventors

Sharon, MA, United States of America

Panagiotis Manolios