Modular computer system and related method

• US 20040031018A1
• Filed: 06/09/2003
• Published: 02/12/2004
• Est. Priority Date: 06/16/2000
• Status: Abandoned Application

• Current Assignee: Nextwave Solutions LP
• Original Assignee: Nextwave Solutions LP
• Inventors: Marty, Emmanuel
• Application Number:
  US10/311,526
• Publication Number:
  US 20040031018A1
• Time in Patent Office: Days
• US Class Current: 717/120
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques
• CPC Class Codes: G06F 8/20 Software design

Abstract

The invention relates to a process for developing computer projects intended to be implemented by a computer system, process comprising a phase of functional analysis with a view to cataloguing the functionalities which are to be catered for, a phase of creating components of the project with the aid of computer means so as to fulfil the said functionalities, a phase of declaration on the same system of the components created during the creation phase, and a phase of loading the said components into a memory area of the system for their implementation by the system,

characterized in that:

during the components creation phase, each functionality is completely fulfilled by the component associated therewith,

during the components declaration phase, each component created is declared to a system loading component, and

during the components loading phase, there are provided means for, in association with each functionality requested by a loaded component, automatically searching for a component offering the said functionality.

Claims

1. Process for developing computer projects (P1, P2) intended to be implemented by a computer system, process comprising a phase of functional analysis (601) with a view to cataloguing the functionalities which are to be catered for, a phase of creating components (C1, C2) of the project with the aid of computer means so as to fulfil the said functionalities, a phase of declaration on the same system of the components created during the creation phase, and a phase of loading the said components into a memory area of the system for their implementation by the system, characterized in that:

during the components creation phase, each functionality is completely fulfilled by the component associated therewith,

during the components declaration phase, each component created is declared to a system loading component, and

during the components loading phase, there are provided means (GD) for, in association with each functionality requested by a loaded component, automatically searching for a component offering the said functionality.

2. Process according to the preceding claim, characterized in that the said automatic search is performed while taking a condition into account.

3. Process according to the preceding claim, characterized in that the said condition is expressed as a function of criteria expressed as a function of properties associated individually with each component.

4. Process according to one of the preceding claims, characterized in that during the creation of a component, the following steps are carried out:

creation (602) of an interface source file of the component, with a view to constituting an “

interface”

part (INT) of the component,

creation (603) of at least one code source file making it possible to realize the functionality of the component, with a view to constituting an “

implementation”

part (IMP) of the component.

5. Process according to the preceding claim, characterized in that each code source file created with a view to constituting an “

implementation”

part of the component can be formulated in any programming language.

9. Process according to one of the preceding claims, characterized in that each component (C1) can be dynamically replaced by another component (C′

1) which exports the same functionality.

10. Process according to the preceding claim, characterized in that the said replacement deploys the following steps:

saving of the current state of the component to be replaced,

loading and initialization of the new component,

transmission of the current state of the component to be replaced to the new component,

establishment of a communication channel between the component calling the functionality and the new component,

unloading of the component to be replaced.

11. Process according to the preceding claim, characterized in that if the loading or the initialization of the new component is not performed correctly, means are provided for returning an error message.

25. Process according to one of the preceding claims, characterized in that each component can be associated with a level of privileges which conditions the possibilities of access of the component to other components, as a function of the respective levels of privileges of the said other components.

26. Process according to one of the preceding claims, characterized in that means are provided for automatically unloading each component where the functionality which it offers'"'"' is no longer necessary for the operation of the computer projects.

27. Process according to the preceding claim, characterized in that the said means comprise a usage counter for each component.

28. Process according to the preceding claim, characterized in that the said counter counts the number of components which import a functionality of the component with which the counter is associated, and the said component is unloaded as soon as its usage counter has decreased to zero.

29. Process according to the preceding claim, characterized in that there are provided means (GD) for automatically freeing the resources used by the said unloaded component.

6. Process according to one of the preceding two claims, characterized in that each component can fulfil the functionality associated therewith by deploying software and/or hardware means.

7. Process according to one of the preceding four claims, characterized in that the interface file of each component comprises a description of the functionality fulfilled by the said component, independent of the manner in which this functionality is fulfilled by the component.

8. Process according to the preceding claim, characterized in that the interface file also comprises a description of the functionalities that the component needs to import from other components in order to fulfil its own functionality.

12. Process according to one of the preceding four claims, characterized in that during the creation of a component, the following steps are also carried out:

creation (604) of a makefile in which are specified;

the language(s) used for the source file(s) created during the code source file(s) creation step,

the code source file(s) corresponding to the “

implementation”

part of the component, creation (605) of a prototype of the component,

editing of links (606) between the “

interface”

part and the “

implementation”

part of the component, so as to generate an executable component prototype,

deployment of the makefile (609) so as to compile the component individually, and constitute a respective object file for the interface source file of the “

interface”

part of the component as well as for the or each code source file of the “

implementation”

part of the component,

encapsulation (610) of the object files created during the preceding step into a single executable module.

13. Process according to the preceding claim, characterized in that during the creation of the prototype of a component, a prototype comprising:

an object interface resulting from the compilation of the interface source file of the component,

a prototype object file in respect of each code source file of the “

implementation”

part of the component, is created.

14. Process according to the preceding claim, characterized in that during the compilation of the interface source file of the component, there is carried out:

the analysis and the verification of the consistency of the source file of the interface,

the translation of the source file of the interface into binary data,

the automatic generation of at least one file so as to call the functionalities which are to be imported by the component.

15. Process according to one of the preceding three claims, characterized in that after the step of editing links between the “

interface”

part and the “

implementation”

part of the component so as to generate an executable component prototype, an automatic integrity testing step (607) is carried out during which one verifies whether the project is consistent and closed.

16. Process according to the preceding claim, characterized in that during the automatic integrity test, for each functionality required in the project, there is an automatic search, from among a list of accessible components, for a component which fulfils the said functionality.

17. Process according to the preceding claim, characterized in that in the case where several components fulfilling the requested functionality are identified, a particular component can be chosen from among these components.

18. Process according to one of the preceding two claims, characterized in that in the case where the integrity test reveals that the project is not correctly closed, an error message is issued indicating the inconsistencies so as to be able to modify certain components and/or add some.

19. Process according to one of the preceding seven claims, characterized in that for each component loaded into the system, the description of the functionalities that the component needs to import from other components so as to fulfil its own functionality is permanently accessible to the said means (GD) of automatic component search.

20. Process according to one of the preceding eight claims, characterized in that during the encapsulation (610) of the object files created during the preceding step into a single executable module, one verifies that all the functionalities supplied by the various interface parts of the project have actually been described fully in an associated source file and have been compiled.

21. Process according to one of the preceding nine claims, characterized in that the process comprises the storage in a random access memory area of the system of a map (G) of the components loaded into the system.

22. Process according to the preceding claim, characterized in that the said map is intended to be consulted when a calling component calls a functionality, so as to determine whether a component of the said map is able to supply the functionality called up.

23. Process according to the preceding claim, characterized in that it is the said means (GD) of automatic component search which are able to consult the said map.

24. Process according to one of the preceding three claims, characterized in that the said map is updated in real time during the operation of the system, as a function of the components loaded into the system.