System and method for automating generation of an automated sensor network

• US 8,271,937 B2
• Filed: 10/31/2007
• Issued: 09/18/2012
• Est. Priority Date: 07/05/2002
• Status: Active Grant

• Current Assignee: Eaton Intelligent Power Limited (Eaton Corporation PLC.)
• Original Assignee: Cooper Technologies Company (Eaton Corporation PLC.)
• Inventors: Anand, Minakshisundaran B., Thakkar, Rajesh, Chakravarthi, Prakash R.
• Primary Examiner(s): Nahar, Qamrun
• Application Number:
  US11/931,443
• Publication Number:
  US 20080059947A1
• Time in Patent Office: 1,784 Days
• Field of Search: 717/106, 717/107
• US Class Current: 717/106
• CPC Class Codes: G05B 19/0426 Programming the control sequence
• CPC Class Codes: G05B 2219/23293 Automated assembly of machine control software, reusable software components
• CPC Class Codes: G06F 8/00 Arrangements for software engineering testing or debugging G06F11/36; administrative, planning or organisation aspects of software project management G06Q10/06

Abstract

An application software generator automatically generates an application software unit. The application software generator includes an application composer that combines components extracted from a component repository with an application framework to generate the application software unit. Each component in the component repository includes a component shell, a component interface and a component core. The application framework includes configurable parameters that determine how the application software unit is generated and operates. The configurable parameters can be entered by a user using a graphical user interface. The user can be assisted using a wizard format. The application framework also provides connectivity between components so that they can pass messages to one another. The connectivity can be, for example, by a message bus or event registry and event dispatch. Components themselves can be automatically generated using the application software generator. Uses of the application software generator include creation of sensor/actuator networks and test script generation.

Claims

1. A system for automatically generating an application software unit, comprising:

a processor;

a component repository, the component repository comprising one or more software components associated with functions of the application software unit;

an application framework that stores parameter information regarding the one or more software components associated with the application software unit; and

an application composer, operating on the processor, that uses the parameter information in the application framework to extract the one or more software components from the component repository, configure the one or more software components according to the parameter information in the application framework, and combine the one or more configured software components and the application framework to generate the application software unit, wherein the application composer extracts and configures the one or more software components from the component repository automatically, without requiring a user to specify which software components to extract or configure.

2. The system recited in claim 1, further comprising a graphical user interface that allows a user to enter the parameter information that is stored in the application framework.

3. The system recited in claim 2, wherein the graphical user interface comprises a wizard format to guide a user in entering the parameter information.

4. The system recited in claim 1, wherein each component in the component repository comprises:

a shell comprising information regarding the component;

a core providing functionality for the component; and

an interface for allowing the component to interact with other components.

5. The system recited in claim 4, wherein the information in the shell comprises performance metric information related to execution of the component.

6. The system recited in claim 4, wherein the information in the shell comprises descriptive information describing the component.

7. The system recited in claim 1, wherein the application framework comprises:

a configurable parameter storage element to store configurable parameters that determine how the application software unit is built and how it operates;

a structure definition element that allows the components to co-exist and cooperate.

8. The system recited in claim 7, wherein the structure definition element comprises a message bus to which each component is connected that allows each component to pass a message to any other component.

9. The system recited in claim 7, wherein the structure definition element comprises:

an event registry into which each component registers those events that it will generate and those events whose occurrence the component desires notification of; and

an event dispatcher that sends notification of an event to each component that registered in the event registry to be notified of the event.

10. The system recited in claim 1, wherein the application software unit is generated in conformance with user-entered constraints.

11. The system recited in claim 1, wherein the application software unit is combined with one or more of a pre-existing operating system, a pre-existing library and a hardware driver to automatically generate a system software unit.

12. The system recited in claim 1, wherein one or more of the components stored in the component registry are generated automatically using a componentizer.

13. The system recited in claim 12, wherein the componentizer comprises:

a graphical user interface that a user uses to input information about a component to be generated;

an interface generator to generate a component interface in conformance with the user-entered information;

a shell generator to generate a component shell in conformance with the user-entered information;

a pre-generated component core; and

a component composer to combine the component core, component interface and component shell into a finished component.

14. The system recited in claim 1, wherein the application software unit generated is a test script.

15. The system recited in claim 1, wherein the application software generated is used in a network of actuators and/or sensors.

16. A method for automatically generating an application software unit, comprising the steps of:

receiving values of one or more configurable parameters for one or more software components stored in a component repository, the one or more software components associated with the application software unit;

storing the received values of the one or more configurable parameters in an application framework;

extracting and configuring the one or more software components from the component repository in accordance with the received values, wherein the one or more software components are extracted and configured automatically, without a user specifying which software components to extract or configure; and

combining the software components with the application framework to generate the application software unit.

17. The method recited in claim 16, further comprising the step of receiving the values of the one or more configurable parameters from a user using a graphical user interface.

18. The method recited in claim 17, further comprising the step of providing a wizard format to assist the user in selecting the parameter values.

19. The method recited in claim 16, further comprising the step of generating each component stored in the component repository.

20. The method recited in claim 19, further comprising the step of creating at least one component in the component repository using a componentizer.

21. The method recited in claim 20, further comprising the steps of:

receiving input information about a component to be generated;

generating a component interface in conformance with the user-entered information;

generating a component shell in conformance with the user-entered information;

combining a pre-generated component core with the component interface and the component shell to create a finished component; and

storing the finished component in the component repository.

22. The method recited in claim 16, further comprising the steps of:

removing a component shell containing information about the component from each component to form stripped components; and

storing the removed component shell, wherein the step of combining the components combines the stripped components.

23. The method recited in claim 22, further comprising the steps of:

retrieving the stored shells; and

extracting the information.

24. The method recited in claim 23, further comprising the step of generating the application software unit in accordance with the extracted information.

25. The method recited in claim 16, further comprising the step of generating the application software unit in accordance with user-entered constraints.

26. The method recited in claim 25, wherein the user-entered constraints include performance constraints.

27. The method recited in claim 16, further comprising the step of combining the generated application software unit with one or more of a pre-existing operating system, a pre-existing library and a hardware driver to automatically generate a system software unit.

28. The method recited in claim 16, further comprising the step of connecting each component to a message bus so that each component can pass a message to any other component.

29. The method recited in claim 16, further comprising the steps of registering with an event registry those events that each component will generate and those events whose occurrence each component desires notification of.

30. A system for automatically generating an application software unit, comprising:

a processor;

means for receiving values of one or more configurable parameters for one or more software components stored in a component repository, the one or more software components associated with the application software unit;

means for storing the received values of the one or more configurable parameters in an application framework;

means, performed by the processor, for extracting and configuring the one or more components from a component repository in accordance with the received values, wherein the one or more software components are extracted and configured automatically, without a user specifying which software components to extract or configure; and

means, performed by the processor, for combining the software components with the application framework to generate the application software unit.

31. The system recited in claim 30, further comprising means for receiving the values of the one or more configurable parameters from a user using a graphical user interface.

32. The system recited in claim 31, further comprising means for providing a wizard format to assist the user in selecting the parameter values.

33. The system recited in claim 30, further comprising means for generating each component stored in the component repository.

34. The system recited in claim 33, further comprising means for creating at least one component in the component repository using a componentizer.

35. The system recited in claim 34, further comprising:

means for receiving input information about a component to be generated;

means for generating a component interface in conformance with the user-entered information;

means for generating a component shell in conformance with the user-entered information;

means for combining a pre-generated component core with the component interface and the component shell to create a finished component; and

means for storing the finished component in the component repository.

36. The system recited in claim 30, further comprising:

means for removing a component shell containing information about the component from each component to form stripped components; and

means for storing the removed component shell, wherein the step of combining the components combines the stripped components.

37. The system recited in claim 36, further comprising:

means for retrieving the stored shells; and

means for extracting the information.

38. The system recited in claim 37, further comprising means for generating the application software unit in accordance with the extracted information.

39. The system recited in claim 30, further comprising means for generating the application software unit in accordance with user-entered constraints.

40. The system recited in claim 39, wherein the user-entered constraints include performance constraints.

41. The system recited in claim 30, further comprising means for combining the generated application software unit with one or more of a pre-existing operating system, a pre-existing library and a hardware driver to automatically generate a system software unit.

42. The system recited in claim 30, further comprising means for connecting each component to a message bus so that each component can pass a message to any other component.

43. The system recited in claim 30, further comprising means for registering with an event registry those events that each component will generate and those events whose occurrence each component desires notification of.

44. A system for automatically generating executable application software for a network of sensors or actuators, said executable application software comprising one or more of an executable software unit resident on embedded sensor or actuator nodes, an executable software unit resident on gateways that collect data from or control the operation of a plurality of said sensor nodes, and an executable software unit resident on a server that collects data from or controls the operation of a plurality of said gateways, said system comprising:

a processor;

a plurality of software components, each of which perform one or more logically related functions, each said software component consisting of a core that performs the function or functions of the component, an interface that allows the component to interact with other software components, and a shell that contains descriptive or quantitative information regarding the component;

a component repository that stores said plurality of software components;

an application framework that defines a structure of the executable application software and which provides an infrastructure for said software components to interact with each other; and

a graphical user interface for inputting parameters of said network of sensors or actuators;

wherein

said system for automatically generating said executable software units chooses and configures one or more software components from the component repository automatically and does not require input from a user to specify which components are to be chosen and further comprises;

means, performed by the processor, for automatically choosing, without additional user input, a second plurality of said software components based on said parameters of said network of sensors or actuators;

means for retrieving said second plurality of software components from said component repository;

means for removing said shell that contains descriptive or quantitative information regarding the component from each of said second plurality of software components; and

means, performed by the processor, for automatically combining, without additional user input, said second plurality of software components with said application framework to produce one or more of said executable application software units.

45. The system recited in claim 44, wherein said application framework comprises a message bus and a common message format such that any one of said components can communicate with any other component by exchanging messages on the message bus.

46. The system recited in claim 44, wherein said application framework comprises:

means for allowing any one of said components to send signals of events;

means for allowing any one of said components to register to receive specific signals of events and; and

means for sending each of said signals sent by components to components that have registered to receive the specific signal.

47. The system recited in claim 44, further comprising means for quantifying performance metrics for said automatically generated application software units, said metrics including but not limited to total memory usage, total code size and total computational power required in million instructions per second.

48. The system recited in claim 47, further comprising means for calculating performance metrics of said automatically generated executable application software units by extracting metric information for each of said components from said shells that contain descriptive or quantitative information regarding the component.

49. The system recited in claim 47, further comprising:

means for calculating performance metrics of said automatically generated executable application software units by extracting metric information for each of said components from said shells that contain descriptive or quantitative information regarding the component; and

means for combining said performance metrics of said automatically generated executable application software units with pre-existing information regarding equivalent metrics for said operating system kernels and hardware device driver software units.

50. The system recited in claim 44, further comprising means for combining said automatically generated executable application software units with pre-existing operating system kernels and hardware device driver software units to automatically generate complete system software units.

51. The system recited in claim 44, further comprising means for automatically generating test scripts for each of said automatically generated executable application software units through the means for combining said parameters of said network of sensors or actuators input through said graphical user interface with pre-existing test script document templates.

52. A system for generating a software component, said system comprising:

a processor;

a component repository that stores a plurality of said software components;

a graphical user interface for selecting a software core module, for specifying an interface of the software core module according to a first pre-defined format and for specifying a shell for the software core module that contains descriptive or quantitative information regarding the software core module according to a second pre-defined format; and

an application framework that stores parameter information regarding the software component, the application framework operable to be combined with the software component to generate an application software unit;

said system for generating the software component, further comprising;

means, performed by the processor, for automatically combining the software core module with the interface of the software core module and with the shell for the software core module to produce the software component, wherein combining the software core module, the interface and the shell is performed without input from a user; and

means, performed by the processor, for storing the said software component in the said component repository.