CA2651461A1 - Relationship management for data modeling in an integrated development environment - Google Patents
Relationship management for data modeling in an integrated development environment Download PDFInfo
- Publication number
- CA2651461A1 CA2651461A1 CA002651461A CA2651461A CA2651461A1 CA 2651461 A1 CA2651461 A1 CA 2651461A1 CA 002651461 A CA002651461 A CA 002651461A CA 2651461 A CA2651461 A CA 2651461A CA 2651461 A1 CA2651461 A1 CA 2651461A1
- Authority
- CA
- Canada
- Prior art keywords
- symbols
- program code
- code file
- definition
- referenced
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 238000011161 development Methods 0.000 title claims abstract description 36
- 238000000034 method Methods 0.000 claims abstract description 34
- 230000007246 mechanism Effects 0.000 claims description 156
- 230000008859 change Effects 0.000 claims description 57
- 238000010200 validation analysis Methods 0.000 claims description 24
- 230000015572 biosynthetic process Effects 0.000 claims description 7
- 238000001514 detection method Methods 0.000 claims description 5
- 238000004590 computer program Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000000717 retained effect Effects 0.000 description 3
- 230000001419 dependent effect Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 239000000284 extract Substances 0.000 description 2
- 238000003780 insertion Methods 0.000 description 2
- 230000037431 insertion Effects 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000012552 review Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99941—Database schema or data structure
- Y10S707/99943—Generating database or data structure, e.g. via user interface
Abstract
A system and method of relationship management for data modeling in an integrated development environment is provided. A method of incorporating a program code file includes generating a relational schema of symbols in the program code file based on a framework for models in the integrated development environment, the schema comprising at least two related tables; determining a relationship between the at least two tables in the relational schema; adding definitions from the program code file for symbols in the relational schema to a definition set retaining definitions of symbols; and producing proxy definitions for use with the definition set for each symbol in the program code file without a definition in the definition set.
Description
RELATIONSHIP MANAGEMENT FOR DATA MODELING IN AN
INTEGRATED DEVELOPMENT ENVIRONMENT
FIELD OF THE INVENTION
The present invention relates to the field of data modeling in integrated development environments.
BACKGROUND OF THE INVENTION
An integrated development environment (IDE) provides a set of tools to assist in the development of a computer program. Such an environment generally supports various tasks and often various programming languages. Given the integration between various files forming a computer program project, each time a file is changed the file is validated to ensure that information on the file in the environment is correct. The validation involves parsing each file that changed as well as each file that the changed file references. If there are N changed files that all reference each other then N*N parses are performed. Since file-to-file dependencies may not be maintained, all of these files are generally parsed. To ensure correctness of the data in a workspace in the IDE, the time for such validation is not amortized over other operations. With a workspace composed of many files or large files, it can be cumbersome to wait for validation of a file, involving completely parsing many files, after each change before proceeding with other actions.
SUMMARY OF THE INVENTION
In accordance with an aspect of the present invention there is provided a method of incorporating a program code file into an integrated development environment, including:
generating a relational schema of symbols in the program code file based on a framework for models in the integrated development environment, the schema comprising at least two related tables; determining a relationship between the at least two tables in the relational schema; adding definitions from the program code file for symbols in the relational schema to a definition set retaining definitions of symbols; and producing proxy definitions foi- use with the definition set for each symbol in the program code file without a definition in the definition set.
In accordance with an aspect of the present invention there is provided a method of managing relationships between program code files in an integrated development environment, including: detecting a change in one of the program code files as being one of "add", "remove" or "update", removing syinbols in the changed program code file from a relational schema if the change is one of "remove" or "update", the relational schema comprising at least two related tables with symbols from the program code files based on a framework for models in the integrated development environment;
incorporating symbols from the changed program code file in the relational schema if the change is one of "add" or "update", verifying a relationship between the at least two tables in the relational schema; removing definitions from a definition set for symbols from the changed program code file that were previously removed from the relational schema, the definition set retaining symbol definitions for the program code files; adding definitions to the definition set from the changed program code file for symbols previously incorporated into the relational schema; and producing proxy definitions for use with the definition set for each symbol in the changed program code file previously incorporated into the relational schema without a definition in the definition set.
In accordance with an aspect of the present invention there is provided a method of managing relationships between program code files in an integrated development environment, including: modifying a relational schema according to a change in one of the program code files, the relational schema comprising at least two related tables with symbols from the program code files based on a framework for models in the integrated development environment; determining a relationship between the at least two tables in the relational schema; modifying a definition set according to the change to include definitions from the changed program code file for symbols therefrom in the relational schema into the definition set, the definition set retaining symbol definitions for the program code files; and producing proxy definitions for use with the definition set for each symbol in the changed program code file without a definition in the definition set.
In accordance with an aspect of the present invention there is provided a system for incorporating a program code file into an integrated development environment including:
a save mechanism for modifying a relational schema according to a change in one of the program code files, the relational schema comprising at least two related tables with symbols from the program code files based on a framework for models in the integrated development environment; a validation mechanism for determining a relationship between the at least two tables in the relational schema; a dependency set mechanism for modifying a definition set according to the change to include definitions from a changed program code file foi- symbols therefrom in the relational schema into the definition set, the definition set retaining symbol definitions for the program code files;
and a proxy tnechanism for producing proxy definitions for use with the definition set for each symbol in the changed program code file without a definition in the definition set; a database for retaining thc relational schema, the relationship between the at least two tables and the definition set; and a controller for coordinating the save mechanism, the validation mechanism, the dependency set mechanism, the proxy mechanism and communications with the database.
In accordance with an aspect of the present invention there is provided a computer-readable medium having computer-executable instructions for incorporating a program code file into an integrated development environment, including: generating a relational schema of symbols in the program code file based on a framework for models in the integrated development environment, the schema comprising at least two related tables;
determining a relationship between the at least two tables in the relational schema; adding definitions from the program code file for symbols in the relational schema to a definition set retaining definitions of symbols; and producing proxy definitions for use with the definition set for each symbol in the program code file without a definition in the definition set.
In accordance with an aspect of the present invention there is provided a computer-readable medium having computer-executable instructions for managing relationships between program code files in an integrated development environment, comprising:
detecting a change in one of the program code files as being one of "add", "remove" or "update", removing symbols in the changed program code file from a relational schema if the change is one of "remove" or "update", the relational schema comprising at least two related tables with symbols from the program code files based on a framework for models in the integrated development environment; incorporating symbols from the changed program code file in the relational schema if the change is one of "add" or "update", verifying a relationship between the at least two tables in the relational schema; removing definitions from a definition set for symbols from the changed program code file that were previously removed from the relational schema, the definition set retaining symbol definitions for the program code files; adding definitions to the definition set from the changed program code file for symbols previously incorporated into the relational schema; and producing proxy definitions for use with the definition set for each symbol in the changed program code file previously incorporated into the relational schema without a definition in the definition set.
In accordance with an aspect of the present invention there is provided a computer-readable medium having computer-executable instructions for managing relationships between program code files in an integrated development environment, including:
modifying a relational schema according to a change in one of the program code files, the relational schema comprising at least two related tables with symbols from the program code files based on a framework for models in the integrated development environment;
determining a relationship between the at least two tables in the relational schema;
modifying a definition set according to the file change to include definitions from the changed program code file for symbols therefrom in the relational schema into the definition set, the definition set retaining symbol definitions for the program code files;
and producing proxy definitions for use with the definition set for each symbol in the changed program code file without a definition in the definition set.
Proxy definitions are produced for each symbol in the changed program code file that does not have a definition in the definition set.
Other aspects and features of the present invention will become apparent to those ordinarily skilled in the art upon review of the following description of specific embodiments of the invention in conjunction with the accompanying figures.
BRIEF DESCRIPTION OF THE DRAWINGS
Fig. I is an exemplary computing environment in which the present invention may be implemented;
Fig. 2 is a system diagram of an integrated development environment including a system for incorporated files thereinto;
Fig. 3A to C show a method for incorporating a file into an integrated development environment;
Fig. 4 shows a method for validating a relationships table in an upwards direction;
Fig. 5 shows a method for validating the relationships table in a downwards directions;
and Fig. 6 shows a pictorial representation of the contents of a database of the integrated development environment of Fig. 2.
DETAILED DESCRIPTION OF EMBODIMENTS OF THE PRESENT INVENTION
Fig. 1 illustrates a configuration of a computer 100 in which the present invention may be implemented.
The computer 100 includes a central processing unit (CPU) 102, a memory 104, an input/output interface 106 and a bus 108. The CPU 102, the memory 104 and the input/output interface 106 are connected with one another via the bus 108. The input/output interface 106 is configured so that it can be connected to an input/output unit 112.
The present invention may be embodied in a program stored in, for example, the memory 104. Alternatively, the present invention may be recorded on any type of recording medium such as a magnetic disk or an optical disk. The present invention recorded on such a recording medium is loaded to the memory 106 of the computer 100 via the input/output unit 112 (e.g. a disk drive).
The CPU 102 can be a cominercially available CPU or a customized CPU suitable for operations described herein. Other variations of CPU 102 can include a plurality of CPUs interconnected to coordinate various operations and functions. The CPU
contains resources for the execution of the present invention including registers 110 that enable basic functions such as placing a value into a specified register (referred to as a "load" operation), copying a value stored in a specified register to a specified memory location (referred to as a"store" operation), and performing arithmetic operations, such as addition and multiplication, on values stored in memory locations and registers. The computer 100 serves as an apparatus for performing the present method by the executing the present invention.
Fig. 2 is a system diagram of an integrated development environment (IDE) 200 in which a computer program may be represented as a model showing components of the program (e.g. objects in an object-oriented project) and relationships therebetween.
The model may be presented in the IDE 200 as a graph data structure of components in which the components have named properties and relationships to other components. Each model may be composed of many files, each of which may contain multiple components.
The model is created when files that form the project are incorporated into the IDE 200. The IDE 200 includes a workspace (not shown) in which multiple models may be presented to a user.
The IDE 200 includes a controller 228, a file build mechanism 236, a save mechanism 240, a modeling mechanism 210, a validation mechanism 234, a symbol resolve mechanism 250, a proxy mechanism 206, a definition set mechanism 230, an editor 216 and a database 214. The controller 228 coordinates the various other components in the IDE 200 and directs the data and control flow therebetween. The file build mechanism 236 incorporates a new or changed pi-ogram code file 204 into the IDE 200. The save mechanism 240 saves the incorporated file 204 into the database 214. The modeling mechanism 210 creates a model from the file 204, including adding new files to the model and incorporating changes to existing files into the model. The validation mechanism 234 validates the file 204 to provide all current references and definitions of data and objects to maintain relationships between files in the IDE 200. The symbol resolve mechanism 250 makes resolutions in the file 204 as to the definition of objects and data therein. The definition set mechanism 230 maintains a definition set with definitions from files in the IDE 200. The definition set is a collection of symbol definitions that provides a view of saved content in the IDE 200 workspace.
The editor 216 enables a file in a model to be changed.
The controller 228 comprises a change detection mechanism 246 that monitors the workspace of the IDE 200. Each model in the workspace is composed of multiple files.
The change detection mechanism 246 monitors the status of each of the models and the files of which they are composed to detect a change in either the model or in one of the files. This change can be in the form of a request to add a new file to a model or to the workspace, a request to remove a file from a model or the workspace, or an editorial change to a file in one of the models in the workspace (such as would be implemented through the editor 216). Monitoring a change in a file in one of the models in the workspace may be performed by monitoring the profile of the file currently in the workspace and comparing it with the profile of the actual file, assessing file size and last save data and time.
When a request to add the new or changed file 204 in one of the models is detected by the change detection mechanism 246, the controller provides the file build mechanism 236 with the location of the file 204. If the request detected by the change detection mechanism 246 is to remove the file 204 from one of the models or the workspace, then the location and identity of this file 204 is provided directly to the save mechanism 240.
The file build mechanism 236 comprises a load mechanism 218, a parse mechanism and a list build mechanism 220, all of which function to incorporate the new or changed file 204 into the IDE 200. T'he load mechanism 218 accepts the file 204 and creates an input data streain from the contents of the file 204. The list build mechanism identifies all references and definitions of svmbols, such as data and objects, and creates a list of public symbols and referenced symbols in the file 204. The public symbols in the file 204 are definitions of symbols (e.g. data and objects) that are accessible to other files.
Referenced symbols in the files 204 represent those symbols used by the file 204 but defined elsewhere (e.g. public symbols from other files). The parse mechanism parses the file 204 to identify and extract references and definitions of symbols therein.
The references and definitions may be determined by searching for symbols in the input stream recognized as providing a reference or definition.
The parse mechanism 202 parses the file 204 to obtain definitions for public symbols and information on referenced s}nnbols. The information on the referenced symbols may include any interface information that can be garnered from the reference in the file 204.
The lists (public symbols and referenced symbols) are provided to the save mechanism 240 for storage in the database 214. The save mechanism 240 comprises a schema formation mechanism 212, and a dependency update mechanism 248. If the file 204 is a new file being incorporated into the IDE 200 then the list is provided directly to the schema formation mechanism 212; othenvise, the list is provided to the dependency update mechanism 248. The schema foi-rnation mechanism 212 comprises a public symbols mechanism 222, and a referenced symbols mechanism 224 for creating a relational schema in the database 214 based on the contents of the public symbols list and the referenced symbols list.
The schema formation mechanism 212 receives the lists and examines the database 214 based on the lists. The database 214 contains a public symbols table formed with public symbol definitions and the location of the file 204 in which the symbol is defined, a referenced symbols table with the symbol references from the list and the location of the file 204 that is referencing the symbols, and a definition set containing the definition for all symbols that have been defined or referenced in the file 204 forming the model. The location of the file 204 in both the public symbol table and the referenced symbols table may be in the form of a universal resource indicator (URI) identifying the file that defines the symbol as well as the location of the file. An identifier for the file 204 may be included in the public symbols table and the referenced symbols table in the form of a name, location, etc.
The schema formation mechanism 212 searches the database 214 to determine if the entries in the public symbols and the referenced symbols list are in the definition set.
This information is provided to the public symbols mechanism 222 and the referenced symbols mechanism 224 along with the appropriate list.
The public symbols mechanism 222 assesses the type of entry for the public symbol in the definition set. If a previous file contained the definition for the public symbol then the definition set will have an actual definition for that symbol. In this case there may be two definitions for the public symbol in the model. This will prompt an error message to be presented to the user indicating that there are two definitions for a public symbol. If the previous file only contained a reference to the symbol then there may be a proxy definition for the symbol in the definition set. The proxy definition includes any information about the symbol that can be garnered from the reference. The proxy definition shows the known public interface but not necessarily the body of the symbol definition. If the entry in the definition set is a proxy definition then the public symbols mechanism 222 obtains file parsing data from the parse mechanism 202. The definition of the public symbol is obtained from the parsed data. This definition is added to the definition set to replace the proxy definition so that the definition set now contains an actual definition of the public symbol.
If the public symbol does not have a definition in the definition set then the public symbols mechanism 222 obtains the public symbols definition from the parse mechanism 202. This definition is added to the definition set.
The pubic symbols mechanism 222 also stores the entries of the public symbols list from the list build mechanism 220 in the public symbols table in the database 214.
The referenced symbols mechanism 224 also assesses the type of entry for the referenced symbols in the definition set. If a previous file contained the definition for the referenced symbol then the definition set contains an actual definition for the referenced symbol. If the definition set contains the actual definition for the symbol, the existing definition in the definition set is retained. If the entry in the definition set is a proxy definition then the existing proxy definition is replaced in the set. If the referenced symbol does not have a proxy or actual definition in the set then a proxy definition is created for the definition set. The proxy mechanism 206 in the IDE 200 creates the proxy definition.
After the public symbols table and the referenced symbols table have been created or populated based on the file 204, then the tables are validated by the validation mechanism 234. A map of the relationships between files is created in the database 214 by the validation mechanism 234.
The public symbols table and the referenced symbols table provide a store of the public symbol definitions and references to symbols in the file 204 so that the file 204 is not parsed by the file build mechanism 236 every time information on the dependencies of the file 204 is requested.
If the file 204 is a previously incorporated file that has been changed or the request received by the controller 228 is to remove the file 204, then the dependency update mechanism 248 coordinates the save and update process. The dependency update mechanism 248 comprises a reniovc symbols mechanism 252 for removal of symbols in the file 204 from the database 214 and a change syinbols mechanism 254 for coordinating changes.
The remove symbols mechanism 252 receives the location and identifier for the file 204 to be removed from a model or the workspace. The remove symbols mechanism 252 removes all public symbols defined in the file 204 from the public symbols table and all referenced symbols in the file 204 are removed from the referenced symbols table. The remove symbols mechanism 252 provides the validation mechanism 234 with the location and identifier of the file 204 so that the dependencies of other files in the model can be updated and validated based on the removal of this file 204.
The change symbols mechanism 254 receives the location and identifier for the file 204 in the model or workspace that has been changed. The change symbols mechanism provides the location and identifier for the file 204 to the remove symbols mechanism 252 so that all public symbols defined in the file 204 are removed from the public symbols table and all referenced symbols in the file 204 are removed form the referenced symbols table. As with the case of file removal, the remove symbols mechanism provides the validation mechanism 234 with the location and identifier of the file 204 so that the dependencies of other files in the model can be updated and validated based on the removal of this file 204. All of the existing information on the file 204 is removed from the public symbols table and the referenced symbols table so that these tables do not contain old information on the file 204 that has been changed. After this old information has been removed the change symbols mechanism provides the location and identifier for the file 204 that has been changed to both the public symbols mechanism 222 and the referenced symbols mechanism 224 so that the changed file 204 can be parsed and the public symbol definitions and referenced symbols in the file 204 can be included in the public syinbols table and the referenced symbols table.
The public symbols mechanism 222 interfaces with the definition set mechanism 230 to examine the definition set to determine if the public symbols in the changed file 204 are defined in the definition set. The presence of a previous public symbols definition prompt the public symbols mechanism 222 to produce an error message. If the public symbol is not defined in the definition set then the public symbols mechanism 222 co-ordinates parsing of the file 204 with the parse mechanism 202 to extract the definition from the file 204. This extracted definition is provided to the definition set mechanism 230 for insertion into the definition set.
The referenced symbols mechanism 224 likewise interfaces with the definition set mechanism 230 to examine the definition set to determine if the referenced symbols are defined therein. The presence of an existing definition for a referenced symbol in the definition set is assessed to detennine if it is a proxy or actual definition.
An actual definition is retained whereas a proxy definition is replaced by a new proxy definition from the file 204. If a referenced symbol definition does not exist in the definition set then one is created by the proxy mechanism 206. This proxy definition is provided to the definition set mechanism 230 for insertion into the definition set.
The definition set mechanisnl 230 interfaces with the public symbols mechanism 222 and the referenced symbols mechanism 224 to add and maintain definitions for the public symbols and the referenced symbols in the definition set in the database 214.
After the public symbols table and the referenced symbols table have been repopulated, then the tables are validated by the validation mechanism 234. The map of the relationship between the tables is maintained by the validation mechanism 234.
The proxy mechanism 206 creates proxy definitions, or skeleton definitions, for symbols in the file 204 that are not resolved. A proxy definition includes a definition of the symbol according to the infonnation in the reference in the file 204. This proxy definition accelerated parsing of a file by enabling parts of the referents of the symbol to be determined from the public symbols table. The proxy mechanism 206 comprises a proxy structure mechanism 258 and a proxy operation mechanism 256.
The proxy mechanism 206 receives infonnation from the referenced symbols mechanism 224 when a referenced symbol that does not have a definition in the definition set is encountered. The infonnation provided by the referenced symbols mechanism 224 may include sections of the file in which the referenced syinbol is used as well as the context in which it is used (i.e. other associated symbols and relevant information on these symbols). From this information the proxy structure mechanism 258 and the proxy operation mechanism 256 create a proxy definitions for the referenced symbol that shows an interface for the symbol but not the body of the definition of the syinbol.
The proxy mechanism 206 extracts all reference information for the symbol from the file 204 and provides this inforrnation to the proxy structure mechanism 258 and the proxy operation mechanism 256. The proxy structure mechanism 258 searches the references to determine the structure of the symbol, including what is the type of the symbol (i.e.
object or specific type of data) and what might be contained in the symbol (i.e. data in an object). The proxy operation mechanism 256 searches the references to determine the functionality of the symbol including what inputs might be accepted and what outputs might be produced (generally the type of the input and output). Such information may be obtained from the public symbols table in the database 214.
lf there was a previous proxy definition in the definition set the proxy mechanism 206 may either replace the existing definition with a new definition or may use the information from the file 204 on the referenced symbol to enhance the existing definition.
The proxy mechanism 206 may also include the proxy definition in the file 204 that is used in the workspace of the IDE 200 to accelerate parsing at a later time. A
referenced symbol with a definition in the definition set provides a dangling reference since the definition for the symbol is not known in the workspace of the IDE 200. Thus, since a definition is created (a proxy definition) for the symbol, memory space in which a value can be retained is provided for the symbol.
The validation mechanism 234, used after the public symbols table and the referenced symbols table have been populated, creates and maintains a relationship table, thus providing the map of relationships between files and the tables. The validation mechanism 234 comprises a relationship table mechanism 226 and a dependency validation mechanism 208 which comprises a reference match mechanism 232 and a dependency list mechanism 266.
The relationship table mechanism 226 creates the relationship table in the database 214 to provide a matching of the public symbols table with the referenced symbols table. The relationship table shows where a symbol is publicly defined and where the symbol is referenced. The relationship table may be used for creating a dependency graph for a model.
The relationship table mechanism 226 is provided with the cause of the change (i.e. add, remove, or change) and an identifier for the file (i.e. name, location, etc.) If the cause is remove or change then the relationship table mechanism 226 removes the public symbols defined in the file 204 from the relationship table as well as all references to symbols in the file 204. References to the public symbols in the file 204 are validated by the dependency validation mechanism 208.
The dependency validation mechanism 208 checks the dependencies between files to determine the effects of the change. The reference match mechanism 232 receives the location and indicator for the file 204 and checks the relationship table to determine if any files in the model depend on public symbols that were defined by the file 204. If such a dependency exists, the newly added public symbol in the public symbol table may resolve previously unresolved dependencies or may cause a previously resolved dependency to be multiply resolved. A dependency in a file is considered to be resolved when the location of the file containing the actual definition (as opposed to proxy definitions) of the symbol which is depended upon is known. Conversely, a dependency is considered to be unresolved when the definition of the symbol in the file is not located in the public symbols table, thus is not known. A multiply resolved dependency is considered to be when there appears to be multiple definitions of the symbol in the public syinbol table. The reference match mechanism 232 examines the public symbol table, the reference symbols table and the relationship table to determine if all of the symbols referenced by the file are defined. If there is a reference to an undefined symbol in the file or if there appears to be multiple definitions of a symbol, then an error may be generated to inform the user of the situation. The validation mechanism 234 stores resolved and multiply resolved dependencies in the relationship table as input for future change validations.
The reference match mechanism 232 performs matching by one of two ways: based on the referenced symbols table or based on the public symbols table. When the reference match mechanism 232 performs matching based on the referenced symbols table, the referenced symbols table is searched to obtain all references to symbols made by the file 204. For each reference, the public symbols table is searched to locate matching symbols that resolve the reference. This produces a location of the definition of each symbol referenced by the file 204. The location of these files are inserted in the relationship table as being "down" files to the current file 204 as they are the files on which the current file 204 is dependent. If there is not exactly one match for the reference symbol in the public symbols table then an error has occurred and a user is informed of this situation. When the reference match mechanism 232 performs matching based on the public symbols table, the public symbols table is searched to obtain all public symbols defined in the file 204. For each reference, the referenced symbols table is searched to locate references to the symbols defined by the file 204. Each file containing a reference to a symbol define in the current file 204 is added to the relationship table as "up" files for the current file 204 since these files depend on the current file.
The dependency list mechanism 266 creates a dependencies list for the file 204 that is stored in the database 214. The dependencies list contains a list of all files that depend on the symbols defined by the file 204. The dependencies list may be an existing list that is maintained or it may be the result of a query made to the relationship table each time the dependency information is requested.
The modeling mechanism 210 creates and updates the model based on the files that form the model. The modeling mechanism 210 comprises a generate model mechanism 242.
The generate model mechanism 242 generates a new model on the basis of newly incorporated files or updates the model on the basis of changed or removed files.
During the creation, changing or parsing of the model, the definition of a symbol referenced by the file 204 may be requested. The symbol resolve mechanism 250 obtains such definitions for references from the definition set in the database 214.
Figs. 3 A to C show a method 300 for incorporating the file 204 into the integrated development environment 200 shown in Fig. 2. The file 204 is loaded into the as an input stream in step 302. A list of all of the public symbols in the file 204 is made in step 304 and a list of all of the referenced symbols in the file 204 is made in step 306.
The cause for updating the file 204 in the IDE 200 is determined in step 308 as being one of "remove," "change," or "add." If the file 204 was updated because of a change to the file 204 or a request to removed the file 204 from the model or because of a change in the file 204, as determined in step 3 10, then the public symbols in the list are removed from the public symbols table in step 312. The referenced symbols are removed from the referenced symbols table in step 314. The definitions in the definition set for the public symbols in the list are removed in step 316. The relationships table is validated in step 318 to remove public symbols in the public symbols list and referenced symbols in the referenced symbols list from the relationships table.
If the reason for updating the file 204 is because the file 204 changed or was added, as determined in step 320, then it is determined in step 322 if the public symbols in the file 204 are defined in the definition set. If the public symbols are defined in the definition set then it is detennined in step 324 if this is an actual definition or a proxy definition. If the definition is a proxy definition then the file 204 is parsed to extract the actual definition of the public symbol therefrom in step 326. The actual definition is then inserted into the definition set to replace the proxy definition in step 328.
If the public symbol was not in definition set as determined in step 322 then the file 204 is parsed in step 330 to extract the public symbol definition. The extracted public symbol definition is added to the definition set in step 332.
After the public symbol definitions have been added to the definition set, or if a previous entry in the definition set for the public symbol was an actual definition, step 334 determines if there are referenced symbols in the referenced symbols list that have definitions in the definition set. If these definitions are proxy definitions, as determined in step 336, then the file 204 is parsed to extract information on the referenced symbol therefrom in step 338. A proxy definition is created in step 340 from this extracted information and is inserted in the definition set in step 342. The created proxy definition may either be a new proxy definition based solely on the infonnation obtained from the parse in step 338 or the existing proxy definition may have been enhanced by the extracted information.
If there is no definition in the definition set for the referenced symbol as determined in step 334 then the file 204 is parsed to extract information on the referenced symbol in step 344. This information is used to create a proxy definition for the referenced symbol in step 346 which is added to the definition set in step 348.
After definitions have been added to the definition set for referenced symbols or a previous definition for the referenced symbol in the definition set was an actual definition or there were no referenced symbols in the file 204, the public symbols in the public symbols list are stored in the public symbols table in the database 214 in step 350. The referenced symbols in the referenced symbols list are stored in the referenced symbols table in step 354.
Relationships between the public symbols in the public symbols table and referenced symbols in the referenced symbols table are determined in step 354. These relationships are inserted into the relationships table in step 356.
The relationships table is validated in step 358 by matching symbols definitions and references. This validation may be in either an upwards direction (as shown in Fig. 5) or a downwards direction (as shown in Fig. 4) or both.
A list of the files that are dependent on the public symbols in the file 204 is created in step 360. After the dependencies list is created or if the reason for updating the file 204 was not "change" or "add" as determined in step 320, then processing of the model in the IDE 200 continues in step 362.
Fig. 4 shows a method 400 for validating the file 204 in a downward direction.
All of the referenced symbols in the file 204 are located in step 402. The public symbols table is searched in step 404 to locate the referenced symbols from the file 204 to see if the file containing the definition for the referenced symbol can be determined. If the referenced symbol is found in the public symbols table, as determined in step 406, then the file location of the referenced symbol definition is inserted in the relationships table for the referenced symbol as being a "down" file, or the file containing the actual definition for the symbol in step 408. If the referenced symbol is not found in the public symbols table, as determined in step 406, then an error message is produced for the user since there is no definition for the referenced symbol in the IDE 200 in step 410.
Fig. 5 shows a method 500 for validating the file 204 in the upward direction.
All of the public symbols in the file 204 are located in step 502. The referenced symbols table is searched in step 504 to locate the public symbols from the file 204 to see if there are any files that reference or use the public symbols. If the public symbol is found in the referenced symbols table, as determined in step 506, then the location of the file containing the reference of the public symbol is inserted in the relationships table for the public symbol as being an "up" file, or a tile containing a reference to the public symbol in step 508. If the public syinbol is not found in the referenced symbols table then processing of the model in the IDE continues in step 510.
Fig. 6 is a pictorial representation of the contents of the database 214 of the IDE 200.
The database 214 contains the public symbols table 602, the referenced symbols table 604, the relationships table 606, the definition set 608 and the dependencies lists 610.
It is apparent to one skilled in the art that numerous modifications and departures from the specific embodiments described herein may be made without departing from the spirit and scope of the invention.
INTEGRATED DEVELOPMENT ENVIRONMENT
FIELD OF THE INVENTION
The present invention relates to the field of data modeling in integrated development environments.
BACKGROUND OF THE INVENTION
An integrated development environment (IDE) provides a set of tools to assist in the development of a computer program. Such an environment generally supports various tasks and often various programming languages. Given the integration between various files forming a computer program project, each time a file is changed the file is validated to ensure that information on the file in the environment is correct. The validation involves parsing each file that changed as well as each file that the changed file references. If there are N changed files that all reference each other then N*N parses are performed. Since file-to-file dependencies may not be maintained, all of these files are generally parsed. To ensure correctness of the data in a workspace in the IDE, the time for such validation is not amortized over other operations. With a workspace composed of many files or large files, it can be cumbersome to wait for validation of a file, involving completely parsing many files, after each change before proceeding with other actions.
SUMMARY OF THE INVENTION
In accordance with an aspect of the present invention there is provided a method of incorporating a program code file into an integrated development environment, including:
generating a relational schema of symbols in the program code file based on a framework for models in the integrated development environment, the schema comprising at least two related tables; determining a relationship between the at least two tables in the relational schema; adding definitions from the program code file for symbols in the relational schema to a definition set retaining definitions of symbols; and producing proxy definitions foi- use with the definition set for each symbol in the program code file without a definition in the definition set.
In accordance with an aspect of the present invention there is provided a method of managing relationships between program code files in an integrated development environment, including: detecting a change in one of the program code files as being one of "add", "remove" or "update", removing syinbols in the changed program code file from a relational schema if the change is one of "remove" or "update", the relational schema comprising at least two related tables with symbols from the program code files based on a framework for models in the integrated development environment;
incorporating symbols from the changed program code file in the relational schema if the change is one of "add" or "update", verifying a relationship between the at least two tables in the relational schema; removing definitions from a definition set for symbols from the changed program code file that were previously removed from the relational schema, the definition set retaining symbol definitions for the program code files; adding definitions to the definition set from the changed program code file for symbols previously incorporated into the relational schema; and producing proxy definitions for use with the definition set for each symbol in the changed program code file previously incorporated into the relational schema without a definition in the definition set.
In accordance with an aspect of the present invention there is provided a method of managing relationships between program code files in an integrated development environment, including: modifying a relational schema according to a change in one of the program code files, the relational schema comprising at least two related tables with symbols from the program code files based on a framework for models in the integrated development environment; determining a relationship between the at least two tables in the relational schema; modifying a definition set according to the change to include definitions from the changed program code file for symbols therefrom in the relational schema into the definition set, the definition set retaining symbol definitions for the program code files; and producing proxy definitions for use with the definition set for each symbol in the changed program code file without a definition in the definition set.
In accordance with an aspect of the present invention there is provided a system for incorporating a program code file into an integrated development environment including:
a save mechanism for modifying a relational schema according to a change in one of the program code files, the relational schema comprising at least two related tables with symbols from the program code files based on a framework for models in the integrated development environment; a validation mechanism for determining a relationship between the at least two tables in the relational schema; a dependency set mechanism for modifying a definition set according to the change to include definitions from a changed program code file foi- symbols therefrom in the relational schema into the definition set, the definition set retaining symbol definitions for the program code files;
and a proxy tnechanism for producing proxy definitions for use with the definition set for each symbol in the changed program code file without a definition in the definition set; a database for retaining thc relational schema, the relationship between the at least two tables and the definition set; and a controller for coordinating the save mechanism, the validation mechanism, the dependency set mechanism, the proxy mechanism and communications with the database.
In accordance with an aspect of the present invention there is provided a computer-readable medium having computer-executable instructions for incorporating a program code file into an integrated development environment, including: generating a relational schema of symbols in the program code file based on a framework for models in the integrated development environment, the schema comprising at least two related tables;
determining a relationship between the at least two tables in the relational schema; adding definitions from the program code file for symbols in the relational schema to a definition set retaining definitions of symbols; and producing proxy definitions for use with the definition set for each symbol in the program code file without a definition in the definition set.
In accordance with an aspect of the present invention there is provided a computer-readable medium having computer-executable instructions for managing relationships between program code files in an integrated development environment, comprising:
detecting a change in one of the program code files as being one of "add", "remove" or "update", removing symbols in the changed program code file from a relational schema if the change is one of "remove" or "update", the relational schema comprising at least two related tables with symbols from the program code files based on a framework for models in the integrated development environment; incorporating symbols from the changed program code file in the relational schema if the change is one of "add" or "update", verifying a relationship between the at least two tables in the relational schema; removing definitions from a definition set for symbols from the changed program code file that were previously removed from the relational schema, the definition set retaining symbol definitions for the program code files; adding definitions to the definition set from the changed program code file for symbols previously incorporated into the relational schema; and producing proxy definitions for use with the definition set for each symbol in the changed program code file previously incorporated into the relational schema without a definition in the definition set.
In accordance with an aspect of the present invention there is provided a computer-readable medium having computer-executable instructions for managing relationships between program code files in an integrated development environment, including:
modifying a relational schema according to a change in one of the program code files, the relational schema comprising at least two related tables with symbols from the program code files based on a framework for models in the integrated development environment;
determining a relationship between the at least two tables in the relational schema;
modifying a definition set according to the file change to include definitions from the changed program code file for symbols therefrom in the relational schema into the definition set, the definition set retaining symbol definitions for the program code files;
and producing proxy definitions for use with the definition set for each symbol in the changed program code file without a definition in the definition set.
Proxy definitions are produced for each symbol in the changed program code file that does not have a definition in the definition set.
Other aspects and features of the present invention will become apparent to those ordinarily skilled in the art upon review of the following description of specific embodiments of the invention in conjunction with the accompanying figures.
BRIEF DESCRIPTION OF THE DRAWINGS
Fig. I is an exemplary computing environment in which the present invention may be implemented;
Fig. 2 is a system diagram of an integrated development environment including a system for incorporated files thereinto;
Fig. 3A to C show a method for incorporating a file into an integrated development environment;
Fig. 4 shows a method for validating a relationships table in an upwards direction;
Fig. 5 shows a method for validating the relationships table in a downwards directions;
and Fig. 6 shows a pictorial representation of the contents of a database of the integrated development environment of Fig. 2.
DETAILED DESCRIPTION OF EMBODIMENTS OF THE PRESENT INVENTION
Fig. 1 illustrates a configuration of a computer 100 in which the present invention may be implemented.
The computer 100 includes a central processing unit (CPU) 102, a memory 104, an input/output interface 106 and a bus 108. The CPU 102, the memory 104 and the input/output interface 106 are connected with one another via the bus 108. The input/output interface 106 is configured so that it can be connected to an input/output unit 112.
The present invention may be embodied in a program stored in, for example, the memory 104. Alternatively, the present invention may be recorded on any type of recording medium such as a magnetic disk or an optical disk. The present invention recorded on such a recording medium is loaded to the memory 106 of the computer 100 via the input/output unit 112 (e.g. a disk drive).
The CPU 102 can be a cominercially available CPU or a customized CPU suitable for operations described herein. Other variations of CPU 102 can include a plurality of CPUs interconnected to coordinate various operations and functions. The CPU
contains resources for the execution of the present invention including registers 110 that enable basic functions such as placing a value into a specified register (referred to as a "load" operation), copying a value stored in a specified register to a specified memory location (referred to as a"store" operation), and performing arithmetic operations, such as addition and multiplication, on values stored in memory locations and registers. The computer 100 serves as an apparatus for performing the present method by the executing the present invention.
Fig. 2 is a system diagram of an integrated development environment (IDE) 200 in which a computer program may be represented as a model showing components of the program (e.g. objects in an object-oriented project) and relationships therebetween.
The model may be presented in the IDE 200 as a graph data structure of components in which the components have named properties and relationships to other components. Each model may be composed of many files, each of which may contain multiple components.
The model is created when files that form the project are incorporated into the IDE 200. The IDE 200 includes a workspace (not shown) in which multiple models may be presented to a user.
The IDE 200 includes a controller 228, a file build mechanism 236, a save mechanism 240, a modeling mechanism 210, a validation mechanism 234, a symbol resolve mechanism 250, a proxy mechanism 206, a definition set mechanism 230, an editor 216 and a database 214. The controller 228 coordinates the various other components in the IDE 200 and directs the data and control flow therebetween. The file build mechanism 236 incorporates a new or changed pi-ogram code file 204 into the IDE 200. The save mechanism 240 saves the incorporated file 204 into the database 214. The modeling mechanism 210 creates a model from the file 204, including adding new files to the model and incorporating changes to existing files into the model. The validation mechanism 234 validates the file 204 to provide all current references and definitions of data and objects to maintain relationships between files in the IDE 200. The symbol resolve mechanism 250 makes resolutions in the file 204 as to the definition of objects and data therein. The definition set mechanism 230 maintains a definition set with definitions from files in the IDE 200. The definition set is a collection of symbol definitions that provides a view of saved content in the IDE 200 workspace.
The editor 216 enables a file in a model to be changed.
The controller 228 comprises a change detection mechanism 246 that monitors the workspace of the IDE 200. Each model in the workspace is composed of multiple files.
The change detection mechanism 246 monitors the status of each of the models and the files of which they are composed to detect a change in either the model or in one of the files. This change can be in the form of a request to add a new file to a model or to the workspace, a request to remove a file from a model or the workspace, or an editorial change to a file in one of the models in the workspace (such as would be implemented through the editor 216). Monitoring a change in a file in one of the models in the workspace may be performed by monitoring the profile of the file currently in the workspace and comparing it with the profile of the actual file, assessing file size and last save data and time.
When a request to add the new or changed file 204 in one of the models is detected by the change detection mechanism 246, the controller provides the file build mechanism 236 with the location of the file 204. If the request detected by the change detection mechanism 246 is to remove the file 204 from one of the models or the workspace, then the location and identity of this file 204 is provided directly to the save mechanism 240.
The file build mechanism 236 comprises a load mechanism 218, a parse mechanism and a list build mechanism 220, all of which function to incorporate the new or changed file 204 into the IDE 200. T'he load mechanism 218 accepts the file 204 and creates an input data streain from the contents of the file 204. The list build mechanism identifies all references and definitions of svmbols, such as data and objects, and creates a list of public symbols and referenced symbols in the file 204. The public symbols in the file 204 are definitions of symbols (e.g. data and objects) that are accessible to other files.
Referenced symbols in the files 204 represent those symbols used by the file 204 but defined elsewhere (e.g. public symbols from other files). The parse mechanism parses the file 204 to identify and extract references and definitions of symbols therein.
The references and definitions may be determined by searching for symbols in the input stream recognized as providing a reference or definition.
The parse mechanism 202 parses the file 204 to obtain definitions for public symbols and information on referenced s}nnbols. The information on the referenced symbols may include any interface information that can be garnered from the reference in the file 204.
The lists (public symbols and referenced symbols) are provided to the save mechanism 240 for storage in the database 214. The save mechanism 240 comprises a schema formation mechanism 212, and a dependency update mechanism 248. If the file 204 is a new file being incorporated into the IDE 200 then the list is provided directly to the schema formation mechanism 212; othenvise, the list is provided to the dependency update mechanism 248. The schema foi-rnation mechanism 212 comprises a public symbols mechanism 222, and a referenced symbols mechanism 224 for creating a relational schema in the database 214 based on the contents of the public symbols list and the referenced symbols list.
The schema formation mechanism 212 receives the lists and examines the database 214 based on the lists. The database 214 contains a public symbols table formed with public symbol definitions and the location of the file 204 in which the symbol is defined, a referenced symbols table with the symbol references from the list and the location of the file 204 that is referencing the symbols, and a definition set containing the definition for all symbols that have been defined or referenced in the file 204 forming the model. The location of the file 204 in both the public symbol table and the referenced symbols table may be in the form of a universal resource indicator (URI) identifying the file that defines the symbol as well as the location of the file. An identifier for the file 204 may be included in the public symbols table and the referenced symbols table in the form of a name, location, etc.
The schema formation mechanism 212 searches the database 214 to determine if the entries in the public symbols and the referenced symbols list are in the definition set.
This information is provided to the public symbols mechanism 222 and the referenced symbols mechanism 224 along with the appropriate list.
The public symbols mechanism 222 assesses the type of entry for the public symbol in the definition set. If a previous file contained the definition for the public symbol then the definition set will have an actual definition for that symbol. In this case there may be two definitions for the public symbol in the model. This will prompt an error message to be presented to the user indicating that there are two definitions for a public symbol. If the previous file only contained a reference to the symbol then there may be a proxy definition for the symbol in the definition set. The proxy definition includes any information about the symbol that can be garnered from the reference. The proxy definition shows the known public interface but not necessarily the body of the symbol definition. If the entry in the definition set is a proxy definition then the public symbols mechanism 222 obtains file parsing data from the parse mechanism 202. The definition of the public symbol is obtained from the parsed data. This definition is added to the definition set to replace the proxy definition so that the definition set now contains an actual definition of the public symbol.
If the public symbol does not have a definition in the definition set then the public symbols mechanism 222 obtains the public symbols definition from the parse mechanism 202. This definition is added to the definition set.
The pubic symbols mechanism 222 also stores the entries of the public symbols list from the list build mechanism 220 in the public symbols table in the database 214.
The referenced symbols mechanism 224 also assesses the type of entry for the referenced symbols in the definition set. If a previous file contained the definition for the referenced symbol then the definition set contains an actual definition for the referenced symbol. If the definition set contains the actual definition for the symbol, the existing definition in the definition set is retained. If the entry in the definition set is a proxy definition then the existing proxy definition is replaced in the set. If the referenced symbol does not have a proxy or actual definition in the set then a proxy definition is created for the definition set. The proxy mechanism 206 in the IDE 200 creates the proxy definition.
After the public symbols table and the referenced symbols table have been created or populated based on the file 204, then the tables are validated by the validation mechanism 234. A map of the relationships between files is created in the database 214 by the validation mechanism 234.
The public symbols table and the referenced symbols table provide a store of the public symbol definitions and references to symbols in the file 204 so that the file 204 is not parsed by the file build mechanism 236 every time information on the dependencies of the file 204 is requested.
If the file 204 is a previously incorporated file that has been changed or the request received by the controller 228 is to remove the file 204, then the dependency update mechanism 248 coordinates the save and update process. The dependency update mechanism 248 comprises a reniovc symbols mechanism 252 for removal of symbols in the file 204 from the database 214 and a change syinbols mechanism 254 for coordinating changes.
The remove symbols mechanism 252 receives the location and identifier for the file 204 to be removed from a model or the workspace. The remove symbols mechanism 252 removes all public symbols defined in the file 204 from the public symbols table and all referenced symbols in the file 204 are removed from the referenced symbols table. The remove symbols mechanism 252 provides the validation mechanism 234 with the location and identifier of the file 204 so that the dependencies of other files in the model can be updated and validated based on the removal of this file 204.
The change symbols mechanism 254 receives the location and identifier for the file 204 in the model or workspace that has been changed. The change symbols mechanism provides the location and identifier for the file 204 to the remove symbols mechanism 252 so that all public symbols defined in the file 204 are removed from the public symbols table and all referenced symbols in the file 204 are removed form the referenced symbols table. As with the case of file removal, the remove symbols mechanism provides the validation mechanism 234 with the location and identifier of the file 204 so that the dependencies of other files in the model can be updated and validated based on the removal of this file 204. All of the existing information on the file 204 is removed from the public symbols table and the referenced symbols table so that these tables do not contain old information on the file 204 that has been changed. After this old information has been removed the change symbols mechanism provides the location and identifier for the file 204 that has been changed to both the public symbols mechanism 222 and the referenced symbols mechanism 224 so that the changed file 204 can be parsed and the public symbol definitions and referenced symbols in the file 204 can be included in the public syinbols table and the referenced symbols table.
The public symbols mechanism 222 interfaces with the definition set mechanism 230 to examine the definition set to determine if the public symbols in the changed file 204 are defined in the definition set. The presence of a previous public symbols definition prompt the public symbols mechanism 222 to produce an error message. If the public symbol is not defined in the definition set then the public symbols mechanism 222 co-ordinates parsing of the file 204 with the parse mechanism 202 to extract the definition from the file 204. This extracted definition is provided to the definition set mechanism 230 for insertion into the definition set.
The referenced symbols mechanism 224 likewise interfaces with the definition set mechanism 230 to examine the definition set to determine if the referenced symbols are defined therein. The presence of an existing definition for a referenced symbol in the definition set is assessed to detennine if it is a proxy or actual definition.
An actual definition is retained whereas a proxy definition is replaced by a new proxy definition from the file 204. If a referenced symbol definition does not exist in the definition set then one is created by the proxy mechanism 206. This proxy definition is provided to the definition set mechanism 230 for insertion into the definition set.
The definition set mechanisnl 230 interfaces with the public symbols mechanism 222 and the referenced symbols mechanism 224 to add and maintain definitions for the public symbols and the referenced symbols in the definition set in the database 214.
After the public symbols table and the referenced symbols table have been repopulated, then the tables are validated by the validation mechanism 234. The map of the relationship between the tables is maintained by the validation mechanism 234.
The proxy mechanism 206 creates proxy definitions, or skeleton definitions, for symbols in the file 204 that are not resolved. A proxy definition includes a definition of the symbol according to the infonnation in the reference in the file 204. This proxy definition accelerated parsing of a file by enabling parts of the referents of the symbol to be determined from the public symbols table. The proxy mechanism 206 comprises a proxy structure mechanism 258 and a proxy operation mechanism 256.
The proxy mechanism 206 receives infonnation from the referenced symbols mechanism 224 when a referenced symbol that does not have a definition in the definition set is encountered. The infonnation provided by the referenced symbols mechanism 224 may include sections of the file in which the referenced syinbol is used as well as the context in which it is used (i.e. other associated symbols and relevant information on these symbols). From this information the proxy structure mechanism 258 and the proxy operation mechanism 256 create a proxy definitions for the referenced symbol that shows an interface for the symbol but not the body of the definition of the syinbol.
The proxy mechanism 206 extracts all reference information for the symbol from the file 204 and provides this inforrnation to the proxy structure mechanism 258 and the proxy operation mechanism 256. The proxy structure mechanism 258 searches the references to determine the structure of the symbol, including what is the type of the symbol (i.e.
object or specific type of data) and what might be contained in the symbol (i.e. data in an object). The proxy operation mechanism 256 searches the references to determine the functionality of the symbol including what inputs might be accepted and what outputs might be produced (generally the type of the input and output). Such information may be obtained from the public symbols table in the database 214.
lf there was a previous proxy definition in the definition set the proxy mechanism 206 may either replace the existing definition with a new definition or may use the information from the file 204 on the referenced symbol to enhance the existing definition.
The proxy mechanism 206 may also include the proxy definition in the file 204 that is used in the workspace of the IDE 200 to accelerate parsing at a later time. A
referenced symbol with a definition in the definition set provides a dangling reference since the definition for the symbol is not known in the workspace of the IDE 200. Thus, since a definition is created (a proxy definition) for the symbol, memory space in which a value can be retained is provided for the symbol.
The validation mechanism 234, used after the public symbols table and the referenced symbols table have been populated, creates and maintains a relationship table, thus providing the map of relationships between files and the tables. The validation mechanism 234 comprises a relationship table mechanism 226 and a dependency validation mechanism 208 which comprises a reference match mechanism 232 and a dependency list mechanism 266.
The relationship table mechanism 226 creates the relationship table in the database 214 to provide a matching of the public symbols table with the referenced symbols table. The relationship table shows where a symbol is publicly defined and where the symbol is referenced. The relationship table may be used for creating a dependency graph for a model.
The relationship table mechanism 226 is provided with the cause of the change (i.e. add, remove, or change) and an identifier for the file (i.e. name, location, etc.) If the cause is remove or change then the relationship table mechanism 226 removes the public symbols defined in the file 204 from the relationship table as well as all references to symbols in the file 204. References to the public symbols in the file 204 are validated by the dependency validation mechanism 208.
The dependency validation mechanism 208 checks the dependencies between files to determine the effects of the change. The reference match mechanism 232 receives the location and indicator for the file 204 and checks the relationship table to determine if any files in the model depend on public symbols that were defined by the file 204. If such a dependency exists, the newly added public symbol in the public symbol table may resolve previously unresolved dependencies or may cause a previously resolved dependency to be multiply resolved. A dependency in a file is considered to be resolved when the location of the file containing the actual definition (as opposed to proxy definitions) of the symbol which is depended upon is known. Conversely, a dependency is considered to be unresolved when the definition of the symbol in the file is not located in the public symbols table, thus is not known. A multiply resolved dependency is considered to be when there appears to be multiple definitions of the symbol in the public syinbol table. The reference match mechanism 232 examines the public symbol table, the reference symbols table and the relationship table to determine if all of the symbols referenced by the file are defined. If there is a reference to an undefined symbol in the file or if there appears to be multiple definitions of a symbol, then an error may be generated to inform the user of the situation. The validation mechanism 234 stores resolved and multiply resolved dependencies in the relationship table as input for future change validations.
The reference match mechanism 232 performs matching by one of two ways: based on the referenced symbols table or based on the public symbols table. When the reference match mechanism 232 performs matching based on the referenced symbols table, the referenced symbols table is searched to obtain all references to symbols made by the file 204. For each reference, the public symbols table is searched to locate matching symbols that resolve the reference. This produces a location of the definition of each symbol referenced by the file 204. The location of these files are inserted in the relationship table as being "down" files to the current file 204 as they are the files on which the current file 204 is dependent. If there is not exactly one match for the reference symbol in the public symbols table then an error has occurred and a user is informed of this situation. When the reference match mechanism 232 performs matching based on the public symbols table, the public symbols table is searched to obtain all public symbols defined in the file 204. For each reference, the referenced symbols table is searched to locate references to the symbols defined by the file 204. Each file containing a reference to a symbol define in the current file 204 is added to the relationship table as "up" files for the current file 204 since these files depend on the current file.
The dependency list mechanism 266 creates a dependencies list for the file 204 that is stored in the database 214. The dependencies list contains a list of all files that depend on the symbols defined by the file 204. The dependencies list may be an existing list that is maintained or it may be the result of a query made to the relationship table each time the dependency information is requested.
The modeling mechanism 210 creates and updates the model based on the files that form the model. The modeling mechanism 210 comprises a generate model mechanism 242.
The generate model mechanism 242 generates a new model on the basis of newly incorporated files or updates the model on the basis of changed or removed files.
During the creation, changing or parsing of the model, the definition of a symbol referenced by the file 204 may be requested. The symbol resolve mechanism 250 obtains such definitions for references from the definition set in the database 214.
Figs. 3 A to C show a method 300 for incorporating the file 204 into the integrated development environment 200 shown in Fig. 2. The file 204 is loaded into the as an input stream in step 302. A list of all of the public symbols in the file 204 is made in step 304 and a list of all of the referenced symbols in the file 204 is made in step 306.
The cause for updating the file 204 in the IDE 200 is determined in step 308 as being one of "remove," "change," or "add." If the file 204 was updated because of a change to the file 204 or a request to removed the file 204 from the model or because of a change in the file 204, as determined in step 3 10, then the public symbols in the list are removed from the public symbols table in step 312. The referenced symbols are removed from the referenced symbols table in step 314. The definitions in the definition set for the public symbols in the list are removed in step 316. The relationships table is validated in step 318 to remove public symbols in the public symbols list and referenced symbols in the referenced symbols list from the relationships table.
If the reason for updating the file 204 is because the file 204 changed or was added, as determined in step 320, then it is determined in step 322 if the public symbols in the file 204 are defined in the definition set. If the public symbols are defined in the definition set then it is detennined in step 324 if this is an actual definition or a proxy definition. If the definition is a proxy definition then the file 204 is parsed to extract the actual definition of the public symbol therefrom in step 326. The actual definition is then inserted into the definition set to replace the proxy definition in step 328.
If the public symbol was not in definition set as determined in step 322 then the file 204 is parsed in step 330 to extract the public symbol definition. The extracted public symbol definition is added to the definition set in step 332.
After the public symbol definitions have been added to the definition set, or if a previous entry in the definition set for the public symbol was an actual definition, step 334 determines if there are referenced symbols in the referenced symbols list that have definitions in the definition set. If these definitions are proxy definitions, as determined in step 336, then the file 204 is parsed to extract information on the referenced symbol therefrom in step 338. A proxy definition is created in step 340 from this extracted information and is inserted in the definition set in step 342. The created proxy definition may either be a new proxy definition based solely on the infonnation obtained from the parse in step 338 or the existing proxy definition may have been enhanced by the extracted information.
If there is no definition in the definition set for the referenced symbol as determined in step 334 then the file 204 is parsed to extract information on the referenced symbol in step 344. This information is used to create a proxy definition for the referenced symbol in step 346 which is added to the definition set in step 348.
After definitions have been added to the definition set for referenced symbols or a previous definition for the referenced symbol in the definition set was an actual definition or there were no referenced symbols in the file 204, the public symbols in the public symbols list are stored in the public symbols table in the database 214 in step 350. The referenced symbols in the referenced symbols list are stored in the referenced symbols table in step 354.
Relationships between the public symbols in the public symbols table and referenced symbols in the referenced symbols table are determined in step 354. These relationships are inserted into the relationships table in step 356.
The relationships table is validated in step 358 by matching symbols definitions and references. This validation may be in either an upwards direction (as shown in Fig. 5) or a downwards direction (as shown in Fig. 4) or both.
A list of the files that are dependent on the public symbols in the file 204 is created in step 360. After the dependencies list is created or if the reason for updating the file 204 was not "change" or "add" as determined in step 320, then processing of the model in the IDE 200 continues in step 362.
Fig. 4 shows a method 400 for validating the file 204 in a downward direction.
All of the referenced symbols in the file 204 are located in step 402. The public symbols table is searched in step 404 to locate the referenced symbols from the file 204 to see if the file containing the definition for the referenced symbol can be determined. If the referenced symbol is found in the public symbols table, as determined in step 406, then the file location of the referenced symbol definition is inserted in the relationships table for the referenced symbol as being a "down" file, or the file containing the actual definition for the symbol in step 408. If the referenced symbol is not found in the public symbols table, as determined in step 406, then an error message is produced for the user since there is no definition for the referenced symbol in the IDE 200 in step 410.
Fig. 5 shows a method 500 for validating the file 204 in the upward direction.
All of the public symbols in the file 204 are located in step 502. The referenced symbols table is searched in step 504 to locate the public symbols from the file 204 to see if there are any files that reference or use the public symbols. If the public symbol is found in the referenced symbols table, as determined in step 506, then the location of the file containing the reference of the public symbol is inserted in the relationships table for the public symbol as being an "up" file, or a tile containing a reference to the public symbol in step 508. If the public syinbol is not found in the referenced symbols table then processing of the model in the IDE continues in step 510.
Fig. 6 is a pictorial representation of the contents of the database 214 of the IDE 200.
The database 214 contains the public symbols table 602, the referenced symbols table 604, the relationships table 606, the definition set 608 and the dependencies lists 610.
It is apparent to one skilled in the art that numerous modifications and departures from the specific embodiments described herein may be made without departing from the spirit and scope of the invention.
Claims (31)
1. A method of managing relationships between program code files in an integrated development environment, comprising:
detecting a change in one of the program code files as being one of "add", "remove"
and "update";
removing symbols in the changed program code file from a relational schema if the change is one of "remove" and "update", the relational schema comprising at least two related tables with symbols from the program code files based on a framework for models in the integrated development environment;
incorporating symbols from the changed program code file in the relational schema if the change is one of "add" and "update";
verifying a relationship between the at least two tables in the relational schema;
removing definitions from a definition set for symbols from the changed program code file that were previously removed from the relational schema, the definition set retaining symbol definitions for the program code files;
adding definitions to the definition set from the changed program code file for symbols previously incorporated into the relational schema; and producing proxy definitions for use with the definition set for each symbol in the changed program code file previously incorporated into the relational schema without a definition in the definition set.
detecting a change in one of the program code files as being one of "add", "remove"
and "update";
removing symbols in the changed program code file from a relational schema if the change is one of "remove" and "update", the relational schema comprising at least two related tables with symbols from the program code files based on a framework for models in the integrated development environment;
incorporating symbols from the changed program code file in the relational schema if the change is one of "add" and "update";
verifying a relationship between the at least two tables in the relational schema;
removing definitions from a definition set for symbols from the changed program code file that were previously removed from the relational schema, the definition set retaining symbol definitions for the program code files;
adding definitions to the definition set from the changed program code file for symbols previously incorporated into the relational schema; and producing proxy definitions for use with the definition set for each symbol in the changed program code file previously incorporated into the relational schema without a definition in the definition set.
2. The method according to claim 6 wherein the step of incorporating symbols comprises:
generating a public symbols table in the relational schema for public symbols in the changed program code file, the public symbols being symbols having a definition in the changed program code file; and generating a referenced symbols table in the relational schema for referenced symbols in the changed program code file, the referenced symbols being only referred to in the changed program code file.
generating a public symbols table in the relational schema for public symbols in the changed program code file, the public symbols being symbols having a definition in the changed program code file; and generating a referenced symbols table in the relational schema for referenced symbols in the changed program code file, the referenced symbols being only referred to in the changed program code file.
3. The method according to claim 7 wherein the step of generating the public symbols table comprises:
locating public symbols in the changed program code file; and adding the located public symbols to the public symbols table;
and wherein the step of generating a referenced symbols table comprises:
locating referenced symbols in the changed program code file; and adding the located referenced symbols to the referenced symbols table.
locating public symbols in the changed program code file; and adding the located public symbols to the public symbols table;
and wherein the step of generating a referenced symbols table comprises:
locating referenced symbols in the changed program code file; and adding the located referenced symbols to the referenced symbols table.
4. The method according to claim 8 wherein the step of adding the located public symbols comprises:
adding an identifier of each located public symbol to the public symbols table; and adding the location of the changed program code file to the public symbols table corresponding to the located public symbols in the public symbols table;
and wherein the step of adding the located referenced symbols comprises:
adding an identifier of each located referenced symbol to the referenced symbols table; and adding the location of the changed program code file to the referenced symbols table corresponding to the located referenced symbols in the referenced symbols table.
adding an identifier of each located public symbol to the public symbols table; and adding the location of the changed program code file to the public symbols table corresponding to the located public symbols in the public symbols table;
and wherein the step of adding the located referenced symbols comprises:
adding an identifier of each located referenced symbol to the referenced symbols table; and adding the location of the changed program code file to the referenced symbols table corresponding to the located referenced symbols in the referenced symbols table.
5. The method according to claim 6 wherein the step of verifying the relationship comprises:
generating a relationships table in the relational schema containing the relationship between the at least two tables.
generating a relationships table in the relational schema containing the relationship between the at least two tables.
6. The method according to claim 6 wherein the step of determining the relationship comprises:
generating a relationships table in the relational schema containing the relationship between the at least two tables, comprising:
determining dependence relationships from the referenced symbols in the program code file based on the public symbols table; and identifying determined dependence relationships in the relationships table.
generating a relationships table in the relational schema containing the relationship between the at least two tables, comprising:
determining dependence relationships from the referenced symbols in the program code file based on the public symbols table; and identifying determined dependence relationships in the relationships table.
7. The method according to claim 6 wherein the step of determining the relationship comprises:
generating a relationships table in the relational schema containing the relationship between the at least two tables, comprising:
determining dependency relationships from the public symbols in the program code file based on the referenced symbols table; and identifying determined dependency relationships in the relationship table.
generating a relationships table in the relational schema containing the relationship between the at least two tables, comprising:
determining dependency relationships from the public symbols in the program code file based on the referenced symbols table; and identifying determined dependency relationships in the relationship table.
8. The method according to claim 6 wherein the program code file contains public symbols having a definition in the changed program code file and referenced symbols only being referred to in the changed program code file, and wherein the step of adding definitions comprises:
parsing the changed program code file to extract definitions for the public symbols therein; and adding the extracted definitions to the definition set.
parsing the changed program code file to extract definitions for the public symbols therein; and adding the extracted definitions to the definition set.
9. The method according to claim 6 wherein the program code file contains public symbols having a definition in the changed program code file and referenced symbols only being referred to in the changed program code file wherein the step of producing proxy definitions comprises:
determining if the definition set contains a definition for the referenced symbols;
parsing the changed program code file to extract information about the referenced symbols from the changed program code file;
formulating a proxy definition for the referenced symbols without a definition in the definition set based on the extracted information; and adding the formulated proxy definition to one of the definition set or the changed program code file.
determining if the definition set contains a definition for the referenced symbols;
parsing the changed program code file to extract information about the referenced symbols from the changed program code file;
formulating a proxy definition for the referenced symbols without a definition in the definition set based on the extracted information; and adding the formulated proxy definition to one of the definition set or the changed program code file.
10. The method according to claim 6 wherein the step of removing symbols comprises:
removing public symbols with an associated file corresponding to the changed program code file from the public symbols table; and removing referenced symbols with an associated file corresponding to the changed program code file from the referenced symbols table.
removing public symbols with an associated file corresponding to the changed program code file from the public symbols table; and removing referenced symbols with an associated file corresponding to the changed program code file from the referenced symbols table.
11. The method according to claim 6 wherein the step of removing definitions comprises:
removing public symbols with an associated file corresponding to the changed program code file from the definition set.
removing public symbols with an associated file corresponding to the changed program code file from the definition set.
12. A method of managing relationships between program code files in an integrated development environment, comprising:
modifying a relational schema according to a change in one of the program code files, the relational schema comprising at least two related tables with symbols from the program code files based on a framework for models in the integrated development environment;
determining a relationship between the at least two tables in the relational schema;
modifying a definition set according to the change to include definitions from the changed program code file for symbols therefrom in the relational schema into the definition set, the definition set retaining symbol definitions for the program code files; and producing proxy definitions for use with the definition set for each symbol in the changed program code file without a definition in the definition set.
modifying a relational schema according to a change in one of the program code files, the relational schema comprising at least two related tables with symbols from the program code files based on a framework for models in the integrated development environment;
determining a relationship between the at least two tables in the relational schema;
modifying a definition set according to the change to include definitions from the changed program code file for symbols therefrom in the relational schema into the definition set, the definition set retaining symbol definitions for the program code files; and producing proxy definitions for use with the definition set for each symbol in the changed program code file without a definition in the definition set.
13. The method according to claim 17 wherein the change is one of "add", "remove"
and "update" and wherein the step of modifying the relational schema comprises:
removing symbols from the changed program code file from the relational schema if the change is one of "remove" and "update";
incorporating symbols from the changed program code file in the relational schema if the change if one of "add" and "update".
and "update" and wherein the step of modifying the relational schema comprises:
removing symbols from the changed program code file from the relational schema if the change is one of "remove" and "update";
incorporating symbols from the changed program code file in the relational schema if the change if one of "add" and "update".
14. The method according to claim 18 wherein the step of incorporating symbols comprises:
generating a public symbols table in the relational schema for public symbols in the changed program code file, the public symbols being symbols having a definition in the changed program code file; and generating a referenced symbols table in the relational schema for referenced symbols in the changed program code file, the referenced symbols being symbols only referred to in the changed program code file.
generating a public symbols table in the relational schema for public symbols in the changed program code file, the public symbols being symbols having a definition in the changed program code file; and generating a referenced symbols table in the relational schema for referenced symbols in the changed program code file, the referenced symbols being symbols only referred to in the changed program code file.
15. The method according to claim 19 wherein the step of generating the public symbols table comprises:
locating public symbols in the changed program code file; and adding the located public symbols to the public symbols table;
and wherein the step of generating a referenced symbols table comprises:
locating referenced symbols in the changed program code file; and adding the located referenced symbols to the referenced symbols table.
locating public symbols in the changed program code file; and adding the located public symbols to the public symbols table;
and wherein the step of generating a referenced symbols table comprises:
locating referenced symbols in the changed program code file; and adding the located referenced symbols to the referenced symbols table.
16. The method according to claim 18 wherein the step of removing symbols comprises:
removing public symbols with an associated file corresponding to the changed program code file from the public symbols table; and removing referenced symbols with an associated file corresponding to the changed program code file from the referenced symbols table.
removing public symbols with an associated file corresponding to the changed program code file from the public symbols table; and removing referenced symbols with an associated file corresponding to the changed program code file from the referenced symbols table.
17. The method according to claim 17 wherein the step of determining the relationship comprises:
generating a relationships table in the relational schema containing the relationship between the at least two tables.
generating a relationships table in the relational schema containing the relationship between the at least two tables.
18. The method according to claim 17 wherein the changed program code file change is one of "add", "remove" and "update" and wherein the step of modifying the definition set comprises:
removing definitions from the definition set for symbols from the changed program code file that were previously removed from the relational schema; and adding definitions to the definition set from the changed program code file for symbols previously incorporated into the relational schema.
removing definitions from the definition set for symbols from the changed program code file that were previously removed from the relational schema; and adding definitions to the definition set from the changed program code file for symbols previously incorporated into the relational schema.
19. The method according to claim 23 wherein the changed program code file contains public symbols having a definition in the changed program code file and referenced symbols only being referred to in the changed program code file, and wherein the step of adding definitions comprises:
parsing the changed program code file to extract definitions for the public symbols therein; and adding the extracted definitions to the definition set.
parsing the changed program code file to extract definitions for the public symbols therein; and adding the extracted definitions to the definition set.
20. The method according to claim 23 wherein the step of removing definitions comprises:
removing public symbols with an associated file corresponding to the changed program code file from the definition set.
removing public symbols with an associated file corresponding to the changed program code file from the definition set.
21. The method according to claim 17 wherein the changed program code file contains public symbols having a definition in the changed program code file and referenced symbols only being referred to in the changed program code file wherein the step of producing proxy definitions comprises:
determining if the definition set contains a definition for the referenced symbols;
parsing the changed program code file to extract information about the referenced symbols from the changed program code file;
formulating a proxy definition for the referenced symbols without a definition in the definition set based on the extracted information; and adding the formulated proxy definition to one of the definition set or the changed program code file.
determining if the definition set contains a definition for the referenced symbols;
parsing the changed program code file to extract information about the referenced symbols from the changed program code file;
formulating a proxy definition for the referenced symbols without a definition in the definition set based on the extracted information; and adding the formulated proxy definition to one of the definition set or the changed program code file.
22. A system for incorporating a program code file into an integrated development environment comprising:
a save mechanism for modifying a relational schema according to a change in one of the program code files, the relational schema comprising at least two related tables with symbols from the program code files based on a framework for models in the integrated development environment;
a validation mechanism for determining a relationship between the at least two tables in the relational schema;
a dependency set mechanism for modifying a definition set according to the change to include definitions from a changed program code file for symbols therefrom in the relational schema into the definition set, the definition set retaining symbol definitions for the program code files;
a proxy mechanism for producing proxy definitions for use with the definition set for each symbol in the changed program code file without a definition in the definition set;
a database for retaining the relational schema, the relationship between the at least two tables and the definition set; and a controller for coordinating the save mechanism, the validation mechanism, the dependency set mechanism, the proxy mechanism and communications with the database.
a save mechanism for modifying a relational schema according to a change in one of the program code files, the relational schema comprising at least two related tables with symbols from the program code files based on a framework for models in the integrated development environment;
a validation mechanism for determining a relationship between the at least two tables in the relational schema;
a dependency set mechanism for modifying a definition set according to the change to include definitions from a changed program code file for symbols therefrom in the relational schema into the definition set, the definition set retaining symbol definitions for the program code files;
a proxy mechanism for producing proxy definitions for use with the definition set for each symbol in the changed program code file without a definition in the definition set;
a database for retaining the relational schema, the relationship between the at least two tables and the definition set; and a controller for coordinating the save mechanism, the validation mechanism, the dependency set mechanism, the proxy mechanism and communications with the database.
23. The system according to claim 27 wherein the change is one of "add", "remove,"
and "update" and wherein the save mechanism comprises:
a schema formation mechanism for incorporating symbols from the changed program code file into the relational schema is the change is "add"; and an update mechanism for coordinating modifying the relational schema if the change is one of "update" and "remove".
and "update" and wherein the save mechanism comprises:
a schema formation mechanism for incorporating symbols from the changed program code file into the relational schema is the change is "add"; and an update mechanism for coordinating modifying the relational schema if the change is one of "update" and "remove".
24. The system according to claim 28 wherein the update mechanism comprises:
a remove symbols mechanism for removing symbols from in the changed program code file from a relational schema if the change is one of "remove" and "update"; and an update mechanism for coordinating the schema formation mechanism and the remove symbols mechanism if the change is "update".
a remove symbols mechanism for removing symbols from in the changed program code file from a relational schema if the change is one of "remove" and "update"; and an update mechanism for coordinating the schema formation mechanism and the remove symbols mechanism if the change is "update".
25. The system according to claim 28 wherein the schema formation mechanism comprises:
a public symbols mechanism for generating a public symbols table in the relational schema for public symbols in the changed program code file, the public symbols being symbols having a definition in the changed program code file, wherein the public symbols table comprises an identifier for the public symbols and a location of the changed program code file and a referenced symbols mechanism generating a referenced symbols table in the relational schema for referenced symbols in the changed program code file, the referenced symbols being symbols only referred to in the changed program code file, wherein the referenced symbols table comprises an identifier for the referenced symbol and a location of the changed program code file.
a public symbols mechanism for generating a public symbols table in the relational schema for public symbols in the changed program code file, the public symbols being symbols having a definition in the changed program code file, wherein the public symbols table comprises an identifier for the public symbols and a location of the changed program code file and a referenced symbols mechanism generating a referenced symbols table in the relational schema for referenced symbols in the changed program code file, the referenced symbols being symbols only referred to in the changed program code file, wherein the referenced symbols table comprises an identifier for the referenced symbol and a location of the changed program code file.
26. The system according to claim 27 wherein the validation mechanism comprises:
a relationship mechanism for generating a relationships table in the relational schema containing the relationship between the at least two tables; and a matching mechanism for matching entries in the at lest two tables.
a relationship mechanism for generating a relationships table in the relational schema containing the relationship between the at least two tables; and a matching mechanism for matching entries in the at lest two tables.
27. The system according to claim 27 wherein the changed program code file contains public symbols having a definition in the changed program code file and referenced symbols only being referred to in the changed program code file, and wherein the matching mechanism comprises:
a dependence match mechanism for determining dependence relationships from the referenced symbols in the changed program code file based on the public symbols table;
and a dependency match mechanism for determining dependency relationships from the public symbols in the changed program code file based on the referenced symbols table.
a dependence match mechanism for determining dependence relationships from the referenced symbols in the changed program code file based on the public symbols table;
and a dependency match mechanism for determining dependency relationships from the public symbols in the changed program code file based on the referenced symbols table.
28. The system according to claim 27 wherein the dependency set interfaces with the referenced symbols mechanism and the public symbols mechanism.
29. The system according to claim 27 wherein the controller comprises:
a change detection mechanism for detecting the change in the changed program code file.
a change detection mechanism for detecting the change in the changed program code file.
30. A computer-readable medium having computer-executable instructions for managing relationships between program code files in an integrated development environment, comprising:
detecting a change in one of the program code files as being one of "add", "remove"
and "update";
removing symbols in the changed program code file from a relational schema if the change is one of "remove" and "update", the relational schema comprising at least two related tables with symbols from the program code files based on a framework for models in the integrated development environment;
incorporating symbols from the changed program code file in the relational schema if the change is one of "add" and "update";
verifying a relationship between the at least two tables in the relational schema;
removing definitions from a definition set for symbols from the changed program code file that were previously removed from the relational schema, the definition set retaining symbol definitions for the program code files;
adding definitions to the definition set from the changed program code file for symbols previously incorporated into the relational schema; and producing proxy definitions for use with the definition set for each symbol in the changed program code file previously incorporated into the relational schema without a definition in the definition set.
detecting a change in one of the program code files as being one of "add", "remove"
and "update";
removing symbols in the changed program code file from a relational schema if the change is one of "remove" and "update", the relational schema comprising at least two related tables with symbols from the program code files based on a framework for models in the integrated development environment;
incorporating symbols from the changed program code file in the relational schema if the change is one of "add" and "update";
verifying a relationship between the at least two tables in the relational schema;
removing definitions from a definition set for symbols from the changed program code file that were previously removed from the relational schema, the definition set retaining symbol definitions for the program code files;
adding definitions to the definition set from the changed program code file for symbols previously incorporated into the relational schema; and producing proxy definitions for use with the definition set for each symbol in the changed program code file previously incorporated into the relational schema without a definition in the definition set.
31. A computer-readable medium having computer-executable instructions for managing relationships between program code files in an integrated development environment, comprising:
modifying a relational schema according to a change in one of the program code files, the relational schema comprising at least two related tables with symbols from the program code files based on a framework for models in the integrated development environment;
determining a relationship between the at least two tables in the relational schema;
modifying a definition set according to the file change to include definitions from the changed program code file for symbols therefrom in the relational schema into the definition set, the definition set retaining symbol definitions for the program code files; and producing proxy definitions for use with the definition set for each symbol in the changed program code file without a definition in the definition set.
modifying a relational schema according to a change in one of the program code files, the relational schema comprising at least two related tables with symbols from the program code files based on a framework for models in the integrated development environment;
determining a relationship between the at least two tables in the relational schema;
modifying a definition set according to the file change to include definitions from the changed program code file for symbols therefrom in the relational schema into the definition set, the definition set retaining symbol definitions for the program code files; and producing proxy definitions for use with the definition set for each symbol in the changed program code file without a definition in the definition set.
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CA002453722A CA2453722A1 (en) | 2003-12-17 | 2003-12-17 | Relationship management for data modeling in an integrated development environment |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002453722A Division CA2453722A1 (en) | 2003-12-17 | 2003-12-17 | Relationship management for data modeling in an integrated development environment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA2651461A1 true CA2651461A1 (en) | 2005-06-17 |
Family
ID=40410044
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002453722A Abandoned CA2453722A1 (en) | 2003-12-17 | 2003-12-17 | Relationship management for data modeling in an integrated development environment |
| CA002651461A Abandoned CA2651461A1 (en) | 2003-12-17 | 2003-12-17 | Relationship management for data modeling in an integrated development environment |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002453722A Abandoned CA2453722A1 (en) | 2003-12-17 | 2003-12-17 | Relationship management for data modeling in an integrated development environment |
Country Status (2)
| Country | Link |
|---|---|
| US (2) | US7478370B2 (en) |
| CA (2) | CA2453722A1 (en) |
Families Citing this family (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7870540B2 (en) * | 2004-07-09 | 2011-01-11 | Microsoft Corporation | Dynamic object validation |
| US8359298B2 (en) | 2006-04-03 | 2013-01-22 | International Business Machines Corporation | Method, system, and program product for managing adapter association for a data graph of data objects |
| US20070282863A1 (en) * | 2006-05-30 | 2007-12-06 | Schacher Ritchard L | Method, system, and program product for providing proxies for data objects |
| US8850388B2 (en) * | 2006-09-07 | 2014-09-30 | Microsoft Corporation | Controlling application features |
| US7908580B2 (en) * | 2006-09-07 | 2011-03-15 | Microsoft Corporation | Connecting an integrated development environment with an application instance |
| US20080127055A1 (en) * | 2006-09-07 | 2008-05-29 | Microsoft Corporation | Application proxy |
| US7865488B2 (en) * | 2007-11-28 | 2011-01-04 | International Business Machines Corporation | Method for discovering design documents |
| US7865489B2 (en) * | 2007-11-28 | 2011-01-04 | International Business Machines Corporation | System and computer program product for discovering design documents |
| US20110302565A1 (en) * | 2010-06-07 | 2011-12-08 | Ferris Michael S | Implicit workspace dependencies |
| US9069748B2 (en) | 2011-10-04 | 2015-06-30 | Microsoft Technology Licensing, Llc | Selective generation and display of data items associated with a spreadsheet |
| US8990675B2 (en) | 2011-10-04 | 2015-03-24 | Microsoft Technology Licensing, Llc | Automatic relationship detection for spreadsheet data items |
| US10331650B2 (en) * | 2014-12-31 | 2019-06-25 | International Business Machines Corporation | Updating web files based on detected legacy model file changes |
| US11126599B2 (en) * | 2017-01-24 | 2021-09-21 | Accenture Global Solutions Limited | Information validation method and system |
Family Cites Families (22)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5182807A (en) * | 1987-12-18 | 1993-01-26 | Nec Corporation | Assembler system for determining when to compile source code modules |
| US5295256A (en) * | 1990-12-14 | 1994-03-15 | Racal-Datacom, Inc. | Automatic storage of persistent objects in a relational schema |
| EP0528617B1 (en) * | 1991-08-19 | 1999-12-22 | Sun Microsystems, Inc. | Method and apparatus for change control in multiple development environments. |
| US5339433A (en) * | 1992-11-19 | 1994-08-16 | Borland International, Inc. | Symbol browsing in an object-oriented development system |
| US5642511A (en) * | 1994-12-16 | 1997-06-24 | International Business Machines Corporation | System and method for providing a visual application builder framework |
| US5642514A (en) * | 1995-05-24 | 1997-06-24 | International Business Machines Corporation | Method and system for constructing compact executable files by eliminating redundant debugging strings |
| CA2171898C (en) * | 1996-03-15 | 2000-02-01 | Brian Ward Thomson | Linker optimization for compiled object oriented programs |
| CA2175711A1 (en) * | 1996-05-01 | 1997-11-02 | Lee Richard Nackman | Incremental compilation of c++ programs |
| US5937189A (en) * | 1996-11-12 | 1999-08-10 | International Business Machines Corporation | Object oriented framework mechanism for determining configuration relations |
| KR100269258B1 (en) * | 1997-10-21 | 2000-10-16 | 정선종 | Integrated CASE Information Repository Metamodel System for Process Methodology and its Integration Support Method |
| US6351848B1 (en) * | 1998-05-29 | 2002-02-26 | Sun Microsystems, Inc. | Unitary data structure systems, methods, and computer program products, for global conflict determination |
| US6978450B2 (en) * | 1999-01-15 | 2005-12-20 | Hewlett-Packard Development Company, L.P. | Method and system for optimizing compilation time of a program by selectively reusing object code |
| US6374401B1 (en) * | 1999-03-29 | 2002-04-16 | International Business Machines Corporation | System, method, and program for updating registry objects with a cross-platform installation program |
| US6542167B1 (en) * | 2000-01-28 | 2003-04-01 | Wind River Systems, Inc. | System and method for flexible software linking |
| US6757887B1 (en) * | 2000-04-14 | 2004-06-29 | International Business Machines Corporation | Method for generating a software module from multiple software modules based on extraction and composition |
| US6829760B1 (en) * | 2000-08-22 | 2004-12-07 | International Business Machines Corporation | Runtime symbol table for computer programs |
| GB0031750D0 (en) * | 2000-12-28 | 2001-02-07 | Sgs Thomson Microelectronics | Retrieval of symbol attributes |
| US6845499B2 (en) * | 2001-01-31 | 2005-01-18 | I2 Technologies Us, Inc. | System and method for developing software applications using an extended XML-based framework |
| US20030101195A1 (en) * | 2001-08-14 | 2003-05-29 | Christian Linhart | Symbol repository |
| WO2003043157A1 (en) * | 2001-11-13 | 2003-05-22 | Prometric, A Division Of Thomson Learning, Inc. | Method and system for computer based testing using plugins to expand functionality of a test driver |
| US20030233585A1 (en) * | 2002-06-17 | 2003-12-18 | Microsoft Corporation | System and method for reducing errors during software development |
| US7458022B2 (en) * | 2003-10-22 | 2008-11-25 | Intel Corporation | Hardware/software partition for high performance structured data transformation |
-
2003
- 2003-12-17 CA CA002453722A patent/CA2453722A1/en not_active Abandoned
- 2003-12-17 CA CA002651461A patent/CA2651461A1/en not_active Abandoned
-
2004
- 2004-01-07 US US10/752,964 patent/US7478370B2/en not_active Expired - Fee Related
-
2008
- 2008-10-27 US US12/259,159 patent/US9250864B2/en not_active Expired - Fee Related
Also Published As
| Publication number | Publication date |
|---|---|
| US7478370B2 (en) | 2009-01-13 |
| US9250864B2 (en) | 2016-02-02 |
| US20050149911A1 (en) | 2005-07-07 |
| US20090049080A1 (en) | 2009-02-19 |
| CA2453722A1 (en) | 2005-06-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9250864B2 (en) | Relationship management for data modeling in an integrated development environment | |
| US20200042712A1 (en) | Open-source software vulnerability analysis | |
| JP4365142B2 (en) | Computer-readable medium, system, and method for associating properties with objects | |
| US6571247B1 (en) | Object oriented technology analysis and design supporting method | |
| US10803061B2 (en) | Software vulnerability graph database | |
| US6530072B1 (en) | Rule based hierarchy generation in a circuit design verification system | |
| CN106843840B (en) | Source code version evolution annotation multiplexing method based on similarity analysis | |
| JPH0926873A (en) | Method and system for discrimination of class relationship of object-oriented system | |
| CN111124379B (en) | Page generation method and device, electronic equipment and storage medium | |
| US8136094B2 (en) | Relationship management for data modeling in an integrated development environment | |
| JPH096627A (en) | Optimizing device | |
| WO2004102380A2 (en) | Method and system for storing pending changes to data | |
| CN102880493B (en) | Method for automatically analyzing dynamic dependency relationship between members | |
| US8997037B2 (en) | User customizable queries to populate model diagrams | |
| JP2009230569A (en) | Query conversion method and retrieving device | |
| US20090228865A1 (en) | Device for processing formally defined data | |
| CN115599386A (en) | Code generation method, device, equipment and storage medium | |
| US9495638B2 (en) | Scalable, rule-based processing | |
| CN112000690B (en) | Method and device for analyzing structured operation statement | |
| CN110209699B (en) | Data interface dynamic generation and execution method based on openEHR Composition template | |
| CN113687827B (en) | Data list generation method, device and equipment based on widget and storage medium | |
| CN109254774A (en) | The management method and device of code in software development system | |
| Reger | Better Proof Output for Vampire. | |
| JP2011053891A (en) | Method and program for storing communication data in relational database | |
| CN111190886B (en) | Database access-oriented computation flow graph construction method, access method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| FZDE | Discontinued |
Effective date: 20121217 |
|
| FZDE | Discontinued |
Effective date: 20121217 |