Remote component and connection architecture

• US 7,735,058 B2
• Filed: 01/31/2005
• Issued: 06/08/2010
• Est. Priority Date: 01/31/2005
• Status: Active Grant

• Current Assignee: Northrop Grumman Systems Corporation (Northrop Grumman Corporation)
• Original Assignee: Northrop Grumman Systems Corporation (Northrop Grumman Corporation)
• Inventors: Sumner, Roger Theodore, Kinsella, Kevin
• Primary Examiner(s): Zhen; Wei Y
• Assistant Examiner(s): Nahar; Qamrun
• Application Number:
  US11/047,132
• Publication Number:
  US 20060174221A1
• Time in Patent Office: 1,954 Days
• Field of Search: 717/106, 717/107, 717/108, 717/109, 717/136, 717/140
• US Class Current: 717/106
• CPC Class Codes: G06F 8/36 Software reuse

Abstract

A method of developing software comprises the steps of defining a plurality of component objects for receiving input data and producing output data, defining a plurality of connection objects for passing data between the component objects, and executing an initialization script to define a behavioral model for the system by defining relationships between the component objects and the connection objects. A software development system that performs the method is also provided.

Claims

1. A computer implemented method of developing software comprising the steps of:

defining a plurality of component objects for receiving input data and producing output data, wherein each of the component objects defines a run method for processing the input data to produce the output data and operates at a defined run rate;

defining a plurality of connection objects for passing data between the component objects; and

executing an initialization script to define relationships between the component objects and the connection objects, and to register the component objects with a dispatch manager component to execute at a specific run rate, wherein the dispatch manager component calls each of the component objects in accordance with the run rate of the component objects.

2. The method of claim 1, further comprising the step of:

controlling one or more of the connection objects to view a signal, perturb the signal or inject a fault.

3. The method of claim 1, wherein:

each of the component objects represents a hardware component or a software component of a flight control system.

4. The method of claim 1, wherein the connection objects comprise one or more of:

scalar connections for passing single data elements;

vector connections for passing arrays of data; and

stream connections for passing sequences of similar data.

5. The method of claim 1, wherein:

control of data flow timing between the component objects is established by a topological sort.

6. The method of claim 5, wherein:

the topological sort is made using a directed acyclic graph of the component objects by run rate and connection type.

7. The method of claim 5, wherein:

the component objects and the connection objects are sorted by component object run rate, component object type, and connection object type.

8. The method of claim 1, wherein:

the component objects are controlled through a fixed rate activation sequence ordered by a creation of the component objects in the initialization script.

9. The method of claim 1, wherein:

the component objects are run in a deterministic periodic execution environment.

10. The method of claim 1, wherein:

the component objects are decoupled from each other to run on different computers.

11. The method of claim 1, further comprising the steps of:

saving internal states of the component objects; and

calling a restore method to restart the software.

12. A software development system comprising:

a computer including a processor for executing an initialization script to define relationships between a plurality of component objects, each defining a run method for processing input data to produce output data and operating at a defined run rate, and a plurality of connection objects, wherein the initialization script registers the component objects with a dispatch manager component to execute at a specific run rate, wherein the dispatch manager component calls each of the component objects in accordance with the run rate of the component objects, the component objects receive the input data and produce the output data, and the connection objects pass data between the component objects.

13. The system of claim 12, further comprising:

an interface for controlling one or more of the connection objects to view a signal, perturb the signal or inject a fault.

14. The system of claim 12, wherein:

each of the component objects represents a hardware component or a software component of a flight control system.

15. The system of claim 12, wherein the connection objects comprise one or more of:

scalar connections for passing single data elements;

vector connections for passing arrays of data; and

stream connections for passing sequences of similar data.

16. The system of claim 12, wherein:

control of data flow timing between the component objects is established by a topological sort.

17. The system of claim 16, wherein:

the topological sort is made using a directed acyclic graph of the component objects by run rate and connection type.

18. The system of claim 16, wherein:

the component objects and the connection objects are sorted by component object run rate, component object type, and connection object type.

19. The system of claim 12, wherein:

the component objects are controlled through a fixed rate activation sequence ordered by a creation of the component objects in the initialization script.

20. The system of claim 12, wherein:

the component objects are run in a deterministic periodic execution environment.

21. The system of claim 12, wherein:

the component objects are decoupled from each other to run on a same or different computers.

22. The system of claim 12, further comprising the steps of:

saving internal states of the component objects; and

calling a restore method to restart a software.