Generation of subsystems
Described herein is a method for generating a subsystem that enables a base architecture ( 100 ) to be adapted for a plurality of different applications ( 112, 114, 116, 118 ). For example, the base architecture relates to a mission support system for a vehicle and the platforms comprise a number of different individual vehicles in which the mission support system for each individual vehicle will need to be interfaced with other systems in the vehicle, for example, its control system.
1 - 9 . (canceled)
10 . A method of generating a mission support system for a plurality of platforms, the method comprising the steps of:
a) defining a basic architecture for the mission support system;
b) deriving a universal subsystem from the architecture;
c) defining the universal subsystem in terms of a data model;
d) storing the data model in a relational database; and
e) interfacing with the relational database to adapt the mission support system for each of the platforms.
11 . A method according to claim 10 , wherein step d) comprises storing the data model in tables within the relational database.
12 . A method according to claim 11 , wherein the tables include subsystem definition tables and subsystem data tables.
13 . A method according to claim 12 , wherein step e) includes the further steps of:
f) populating the subsystem definition tables;
g) populating the subsystem data tables;
h) deriving a graphical user interface; and
i) connecting the graphical user interface to the relational database.
14 . A method according to claim 13 , wherein step f) includes the additional steps of:
j) selecting classes from the data model to add to the subsystem definition tables;
k) using a corresponding specification for each selected class to add a new entry in a class description table; and
l) for each attribute within a selected class, adding a new entry in a class attribute description table.
15 . A method according to claim 14 , wherein step g) includes the additional step of making a database table for each of the classes specified in the class description table.
16 . A method according to claim 10 , wherein step a) includes deriving a plurality of key mechanisms that are characteristic of the basic architecture.
17 . A method according to claim 16 , wherein step d) comprises storing the data model in tables within the relational database.
18 . A method according to claim 17 , wherein the tables include subsystem definition tables and subsystem data tables.
19 . A method according to claim 18 , wherein step e) includes the further steps of:
f) populating the subsystem definition tables;
g) populating the subsystem data tables;
h) deriving a graphical user interface; and
i) connecting the graphical user interface to the relational database.
20 . A method according to claim 19 , wherein step f) includes the additional steps of:
j) selecting classes from the data model to add to the subsystem definition tables;
k) using a corresponding specification for each selected class to add a new entry in a class description table; and
l) for each attribute within a selected class, adding a new entry in a class attribute description table.
21 . A method according to claim 20 , wherein step g) includes the additional step of making a database table for each of the classes specified in the class description table.
22 . A method according to claim 11 , wherein the key mechanisms comprise public key mechanisms and private key mechanisms.
23 . A method according to claim 22 , wherein step d) comprises storing the data model in tables within the relational database.
24 . A method according to claim 23 , wherein the tables include subsystem definition tables and subsystem data tables.
25 . A method according to claim 24 , wherein step e) includes the further steps of:
f) populating the subsystem definition tables;
g) populating the subsystem data tables;
h) deriving a graphical user interface; and
i) connecting the graphical user interface to the relational database.
26 . A method according to claim 25 , wherein step f) includes the additional steps of:
j) selecting classes from the data model to add to the subsystem definition tables;
k) using a corresponding specification for each selected class to add a new entry in a class description table; and
l) for each attribute within a selected class, adding a new entry in a class attribute description table.
27 . A method according to claim 26 , wherein step g) includes the additional step of making a database table for each of the classes specified in the class description table.
28 . A method according to claim 12 , wherein at least one of the public key mechanisms can be accessed in step e).
29 . A method according to claim 28 , wherein step d) comprises storing the data model in tables within the relational database.
30 . A method according to claim 29 , wherein the tables include subsystem definition tables and subsystem data tables.
31 . A method according to claim 30 , wherein step e) includes the further steps of:
f) populating the subsystem definition tables;
g) populating the subsystem data tables;
h) deriving a graphical user interface; and
i) connecting the graphical user interface to the relational database.
32 . A method according to claim 31 , wherein step f) includes the additional steps of:
j) selecting classes from the data model to add to the subsystem definition tables;
k) using a corresponding specification for each selected class to add a new entry in a class description table; and
l) for each attribute within a selected class, adding a new entry in a class attribute description table.
33 . A method according to claim 32 , wherein step g) includes the additional step of making a database table for each of the classes specified in the class description table.