Activity monitor
An activity monitor for a modular software system, the system having a first software component for use in configuring operation of a second software component via a proxy and stub interface, the activity monitor comprising; an input arranged to monitor a first event associated with the first software component and a second event associated with the proxy; a processor arranged to compare the first and second events to a schedule of events to assess compliance with the schedule of events; and an output arranged to generate an error message in response to non-compliance with the schedule of events, the error message being for use in treating the error. A method of generating an activity monitor for monitoring operation of a modular software system.
1. An activity monitor for a modular software system, the system having a first software component for use in configuring operation of a second software component via a proxy and stub interface, the activity monitor comprising;
an input arranged to monitor a first event associated with the first software component and a second event associated with the proxy;
a processor arranged to compare the first and second events to a schedule of events to assess compliance with the schedule of events; and
an output arranged to generate an error message in response to non-compliance with the schedule of events, the error message being for use in treating the error.
2. The activity monitor of claim 1 wherein the schedule of events includes either or both timing and order of the events.
3. The activity monitor of claim 1 wherein the first software component is stored on a first memory space and the second software component is stored on a second memory space.
4. A system comprising a first software component and a second software component, the first software component for use in configuring operation of the second software component, the system comprising a proxy and stub interface for routing events to the second software component and the system comprising the activity monitor of claim 1 .
5. The system of claim 4 wherein the system is a vehicle system.
6. The system of claim 5 wherein the vehicle system is a cruise control system.
7. The system of claim 5 wherein the second software component comprises a drivetrain component.
8. The system of claim 4 wherein the first software component comprises a logic component arranged to generate a command event to control the second software component based on an input event.
9. The system of claim 8 wherein the input event comprises a sensor reading obtained from a sensor component.
10. The system of claim 9 wherein the sensor component is a speed sensor component.
11. The system of claim 9 wherein the input event is obtained in response to a polling event initiated by the logic component.
12. The system of claim 11 wherein the event associated with the first software component is selected from a list including the input event, the polling event, and the command event.
13. The system of claim 4 comprising a troubleshooting component arranged to treat the error in response to receiving the error message.
14. The system of claim 4 comprised in a vehicle.
15. A method of monitoring activity in a modular software system, the system having a first software component for use in configuring operation of a second software component via a proxy and stub interface, the method comprising;
monitoring a first event associated with the first software component and a second event associated with the proxy;
comparing the first and second events to a schedule of events to assess compliance with the schedule of events; and
generating an error message in response to non-compliance with the schedule of events, the error message being for use in treating the error.
16. A method as claimed in claim 15 comprised of computer-readable instructions stored on a computer storage medium.
17. A method as claimed in claim 15 comprised of executable computer program instructions stored on a non-transitory computer-readable storage medium.