System and method for identifying and adding files to a project manifest

• US 8,719,766 B1
• Filed: 10/16/2006
• Issued: 05/06/2014
• Est. Priority Date: 10/16/2006
• Status: Active Grant

• Current Assignee: The MathWorks, Inc.
• Original Assignee: The MathWorks, Inc.
• Inventors: Aberg, Robert O., Walker, Gavin William, Wood, Malcolm Alexander
• Primary Examiner(s): Dao, Thuy
• Assistant Examiner(s): HAYIM, SAMUEL E
• Application Number:
  US11/582,064
• Time in Patent Office: 2,759 Days
• Field of Search: None
• US Class Current: 717/100
• CPC Class Codes: G06F 8/34 Graphical or visual programming
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

A mechanism for identifying and adding files to a project manifest is discussed. A combination of techniques is used in order to identify the files that should be listed in a project manifest. The combined techniques include the programmatic examination of a storage location marked as associated with a project to identify project files. The identified files are automatically added to a project manifest. In one embodiment the identified files are subjected to filtering criteria before being added to the project manifest. In addition, embodiments of the present invention perform a static analysis of at least one file associated with the project to identify file dependencies. The identified files are also added to the project manifest. The integrated development environment (IDE) also provides a user interface enabling a user to manually add files to the project manifest.

Claims

1. A computing device-implemented method comprising:

obtaining in an Integrated Development Environment (IDE) at least one file referenced by a project, where;

the at least one file includes a plurality of file dependencies,

the project is associated with an executable graphical model being developed in the IDE,

the project has a project manifest, the project manifest identifying files associated with the project, and

the project is executable when associated with the project manifest;

examining, with a verification facility in the IDE, a plurality of files associated with the at least one file referenced by the project, the plurality of files including files required to execute the project and files not-required to execute the project, the examining comprising;

identifying a filtered set of files from the files required to execute the project and the files not-required to execute the project;

adding the filtered set of files to the project manifest;

automatically performing, without user intervention, a static analysis of the at least one file referenced by the project;

automatically identifying, without user intervention, at least one additional file not included in the filtered set of files, the automatically identifying based on the static analysis, the automatically identifying comprising;

retrieving, from storage, the project manifest, and

adding the at least one additional file, not included in the filtered set of files, to the project manifest, where the project is executable prior to and after the automatic addition of the at least one additional file, not included in the filtered set of files, to the project manifest;

automatically identifying, without user intervention, at least one IDE-selected file, the least one IDE-selected file created based on performing a task on the at least one file referenced by the project; and

automatically adding, without user intervention, the at least one IDE-selected file to the project manifest, the project being executable when the at least one IDE-selected file is in the project manifest.

2. The method of claim 1, further comprising;

adding at least one user-selected file to the project manifest.

3. The method of claim 2, wherein the at least one IDE-selected file is added to the project manifest after programmatically comparing one of a name, a version and an author of the selected file to the files in the project manifest and identifying absence of the IDE-selected file from the list of files in the project manifest.

4. The method of claim 1, wherein a group of files identified by a label is added to the project manifest.

5. The method of claim 4, wherein the label identifies one of an application, an application plug-in, a toolbox and a blockset.

6. The method of claim 5, wherein the label also identifies a version identifier for one of the application, the application plug-in, the toolbox and the blockset.

7. The method of claim 1, wherein the static analysis is performed on the executable graphical model.

8. The method of claim 1, wherein the static analysis is performed on a textual model associated with the executable graphical model.

9. The method of claim 1, further comprising:

providing the project manifest to version control software.

10. The method of claim 1, further comprising:

transferring the at least one file referenced by the project and the project manifest to a second IDE;

examining the project manifest in the second IDE; and

identifying at least one file in the project manifest as missing from the second IDE.

11. The method of claim 10, further comprising:

retrieving to the second IDE the file identified as missing from the second IDE from a location outside the second IDE.

12. The method of claim 11, further comprising:

executing the at least one file referenced by the project in the second IDE using at least one file in the project manifest.

13. The method of claim 1, further comprising:

subtracting, automatically, without user intervention, at least one selected file from the project manifest, the at least one selected file subtracted from the project manifest after automatically comparing one of a name, a version and an author of the selected file to the files in the project manifest and identifying presence of the selected file in the files provided by the project manifest.

14. The method of claim 1, wherein the task performed on the at least one file is performance of a coverage report on the executable graphical model.

15. A system comprising:

a processor to;

retrieve at least one file referenced by a project into an Integrated Development Environment (IDE), where;

the project includes a plurality of file dependencies,

the project is associated with an executable graphical model being developed in the IDE,

the project has a project manifest, the project manifest identifying files associated with the project, and

the project is executable when associated with the project manifest;

execute a verification facility that examines a plurality of files associated with the at least one file referenced by the project, where;

the plurality of files includes files required to execute the project and files not-required to execute the project,

the examining identifies a filtered set of files from the files required to execute the project and the files not-required to execute the project;

add the filtered set of files to the project manifest, where the project verification facility;

automatically performs, without user intervention, a static analysis of the at least one file referenced by the project,

automatically identify, without user intervention, at least one additional file not included in the filtered set of files, the automatically identifying based on the static analysis, the automatically identifying comprising;

retrieving, from storage, the project manifest, and

adding the at least one additional file, not included in the filtered set of files, to the project manifest, where the project is executable prior to and after the automatic addition of the at least one additional file, not included in the filtered set of files, to the project manifest;

automatically identify, without user intervention, at least one IDE-selected file, the least one IDE-selected file created based on performing a task on the at least one file referenced by the project; and

automatically add, without user intervention, the at least one IDE-selected file to the project manifest, the project being executable when the at least one IDE-selected file is in the project manifest.

16. The system of claim 15, wherein the processor is further configured to:

add the at least one IDE-selected file to the project manifest after automatically comparing, without user intervention, a name of the IDE-selected file to the files in the project manifest and identifying absence of the IDE-selected file in the files in the project manifest.

17. The system of claim 15, wherein the processor is further configured to:

add a group of files identified by a label to the project manifest.

18. The system of claim 15, wherein the processor is further configured to:

perform the static analysis on one of the executable graphical model and a textual model associated with the executable graphical model.

19. The system of claim 15, wherein the project manifest includes at least one metatag.

20. The system of claim 19, wherein the at least one metatag indicates one of a default model and a top model.

21. The system of claim 15, wherein the task performed on the at least one file is performance of a coverage report on the executable graphical model that creates at least one file.

22. A non-transitory computer-readable medium storing:

one or more instructions that, when executed by a processor, cause the processor to;

obtain in an Integrated Development Environment (IDE) at least one file referenced by a project, where;

the at least one file includes a plurality of file dependencies,

the project is associated with an executable graphical model being developed in the IDE,

the project has a project manifest, the project manifest identifying files associated with the project, and

the project is executable when associated with the project manifest;

examine, with a verification facility in the IDE, a plurality of files associated with the at least one file referenced by the project, the plurality of files including files required to execute the project and files not-required to execute the project, the examining comprising;

identifying a filtered set of files from the files required to execute the project and the files not-required to execute the project;

add the filtered set of files to the project manifest;

automatically perform, without user intervention, a static analysis of the at least one file referenced by the project;

automatically identify, without user intervention, at least one additional file not included in the filtered set of files, the automatically identifying based on the static analysis, the automatically identifying comprising;

retrieving, from storage, the project manifest, and

adding the at least one additional file, not included in the filtered set of files, to the project manifest, where the project is executable prior to and after the automatic addition of the at least one additional file, not included in the filtered set of files, to the project manifest;

automatically identify, without user intervention, at least one IDE-selected file, the least one IDE-selected file created based on performing a task on the at least one file referenced by the project; and

automatically add, without user intervention, the at least one IDE-selected file to the project manifest, the project being executable when the at least one IDE-selected file is in the project manifest.

23. The medium of claim 22, further storing:

one or more instructions that, when executed by the processor, cause the processor to;

add at least one user-selected file to the project manifest.

24. The medium of claim 22, wherein the at least one IDE-selected file is added to the project manifest after automatically comparing, without user intervention, a name of the IDE-selected file to the files in the project manifest and identifying absence of the IDE-selected file from the files in the project manifest.

25. The medium of claim 22, wherein a group of files identified by a label is added to the project manifest.

26. The medium of claim 25, wherein the label identifies one of an application, an application plug-in, a toolbox and a blockset.

27. The medium of claim 26, wherein the label also identifies a version identifier for one of the application, the application plug-in, the toolbox and the blockset.

28. The medium of claim 22 wherein the static analysis is performed on one of the executable graphical model and a textual model associated with the executable graphical model.

29. The medium of claim 22, further storing:

one or more instructions that, when executed by the processor, cause the processor to;

provide the project manifest to version control software.

30. The medium of claim 22, further storing:

one or more instructions that, when executed by the processor, cause the processor to;

transfer the at least one file referenced by the project and the project manifest to a second IDE;

examine the project manifest in the second IDE; and

identify at least one file listed in the project manifest as missing from the second IDE.

31. The medium of claim 30, further storing:

one or more instructions that, when executed by the processor, cause the processor to;

retrieve to the second IDE the file identified as missing from the second IDE from a location outside the second IDE.

32. The medium of claim 31, further storing:

one or more instructions that, when executed by the processor, cause the processor to;

execute the at least one file referenced by the project in the second IDE using at least one file in the project manifest.

33. The medium of claim 22, wherein the task performed on the at least one file is performance of a coverage report on the executable graphical model.

34. A system comprising:

a processor executing instructions to;

obtain, in an Integrated Development Environment (IDE), at least one file referenced by a project, where;

the at least one file includes a plurality of file dependencies,

the project is associated with an executable graphical model being developed in the IDE,

the project has a project manifest, the project manifest identifying files associated with the project, and

the project is executable when associated with the project manifest;

examine, with a verification facility in the IDE, a plurality of files associated with the at least one file referenced by the project, the plurality of files including files required to execute the project and files not-required to execute the project, the examining comprising;

identifying a filtered set of files from the files required to execute the project and the files not-required to execute the project;

add the filtered set of files to the project manifest;

automatically perform, without user intervention, a static analysis of the at least one file referenced by the project;

automatically identify, without user intervention, at least one additional file not included in the filtered set of files, the automatically identifying based on the static analysis, the automatically identifying comprising;

retrieving, from storage, the project manifest, and

adding the at least one additional file, not included in the filtered set of files, to the project manifest, where the project is executable prior to and after the automatic addition of the at least one additional file, not included in the filtered set of files, to the project manifest;

automatically identify, without user intervention, at least one IDE-selected file, the least one IDE-selected file created based on performing a task on the at least one file referenced by the project; and

automatically add, without user intervention, the at least one IDE-selected file to the project manifest, the project being executable when the at least one IDE-selected file is in the project manifest.

35. The system of claim 34, wherein the processor further executes instructions to:

add at least one user-selected file to the project manifest.

36. A computing device-implemented method comprising:

obtaining in an Integrated Development Environment (IDE) an executable graphical model referenced by a project, where;

the executable graphical model includes a plurality of file dependencies,

the project has a project manifest, the project manifest identifying files associated with the project, and

the project is executable when associated with the project manifest;

examining, with a verification facility in the IDE, a plurality of files associated with the executable graphical model, the plurality of files including files required to execute the project and files not-required to execute the project, the examining including;

identifying a filtered set of files from the files required to execute the project and the files not-required to execute the project;

adding the filtered set of files to the project manifest;

automatically performing, without user intervention, a static analysis of the executable graphical model;

automatically identifying, without user intervention, at least one additional file not included in the filtered set of files, the automatically identifying based on the static analysis, the automatically identifying comprising;

retrieving, from storage, the project manifest, and

adding the at least one additional file, not included in the filtered set of files, to the project manifest, where the project is executable prior to and after the automatic addition of the at least one additional file, not included in the filtered set of files, to the project manifest;

adding at least one user-selected file to the project manifest; and

automatically identifying, without user intervention, at least one IDE-selected file, the least one IDE-selected file created based on performing a task on the at least one file referenced by the project; and

automatically adding, without user intervention, the at least one IDE-selected file to the project manifest, the project being executable when the at least one IDE-selected file is in the project manifest.

37. The method of claim 36, wherein the task performed on the at least one file is performance of a coverage report on the executable graphical model.

38. A computing device-implemented method comprising:

obtaining, with a computing device, at least one file referenced by a project, where;

the at least one file includes a plurality of file dependencies,

the project is associated with an executable graphical model,

the project has a project manifest, the project manifest identifying files associated with the project, and

the project is executable when associated with the project manifest;

examining, with a verification facility in the computing device, a plurality of files associated with the at least one file referenced by the project, the plurality of files including files required to execute the project and files not-required to execute the project, the examining comprising;

identifying a filtered set of files from the files required to execute the project and the files not-required to execute the project;

adding the filtered set of files to the project manifest;

automatically performing, without user intervention, a dynamic analysis of the at least one file referenced by the project;

automatically identifying, without user intervention, at least one additional file not included in the filtered set of files, the automatically identifying based on the dynamic analysis, the automatically identifying comprising;

retrieving, from storage, the project manifest, and

adding the at least one additional file, not included in the filtered set of files, to the project manifest, where the project is executable prior to and after the automatic addition of the at least one additional file, not included in the filtered set of files, to the project manifest;

automatically identifying, without user intervention, at least one selected file, the least one selected file created based on performing a task on the at least one file referenced by the project; and

automatically adding, without user intervention, at least one selected file to the project manifest, the project being executable when the at least one selected file is in the project manifest.

39. The method of claim 38, wherein the task performed on the at least one file is performance of a coverage report on the executable graphical model.

40. A computing device-implemented method comprising:

obtaining at least one file referenced by a project, where;

the at least one file includes at least one file dependency,

the project is associated with an executable graphical model,

the project has a project manifest, the project manifest identifying files associated with the project, and

the project is executable when associated with the project manifest;

examining with a verification facility executing in a computing device a list of files associated with the project, the files including files required to execute the project and files not-required to execute the project, the examining comprising;

identifying a filtered set of files from the files required to execute the project and the files not-required to execute the project;

adding the filtered set of files added to the project manifest;

automatically performing, without user intervention, a static analysis of the at least one file referenced by the project;

automatically identifying, without user intervention, at least one additional file not included in the filtered set of files, the automatically identifying based on the static analysis, the automatically identifying comprising;

retrieving, from storage, the project manifest, and

adding the at least one additional file, not included in the filtered set of files, to the project manifest, where the project is executable prior to and after the automatic addition of the at least one additional file, not included in the filtered set of files, to the project manifest;

automatically identifying, without user intervention, at least one selected file, the least one selected file created based on performing a task on the at least one file referenced by the project; and

automatically adding, without user intervention, the at least one selected file to the project manifest, the project being executable when the at least one IDE-selected file is in the project manifest.

41. The method of claim 40, wherein at least one file identified by the static analysis is not added to the project manifest because of being listed on an exclusion list.

42. The method of claim 40, wherein the task performed on the at least one file is performance of a coverage report on the executable graphical model.