EXCHANGE OF FILES AND META-INFORMATION BETWEEN SYSTEM DESIGN TOOLS AND BEHAVIOR MODELING TOOLS AND/OR SIMULATORS FOR THE CREATION OF ECU SOFTWARE
First Claim
1. A method for exchanging files and/or information for an overall development project between two development projects, the method comprising:
- providing a computer system that includes a first development environment with a first development project and a second development environment with a second development project to develop software for an electronic control unit, the computer system having a first memory region, in which a number of different types of files belonging to a first development project, and a first file collection container or set of containers, which contains all files relevant for the overall development project and belonging to the first development project, are stored;
providing, in the first development environment, a first management unit, in which initial information for all files belonging to the first development project are stored;
checking, via the first management unit for the purpose of export, whether all files relevant to the overall development project and belonging to the first development system are inserted in a current version in the first file collection;
updating, via a management unit, the first file collection, in that all files relevant to the overall development project and belonging to the first development system are included in a most recent version in the first file collection or left in the current version and deleting obsolete files;
providing the updated first file collection to the second development environment, the second development environment having a second management unit, in which second information on all files belonging to the second development project are stored, the computer system having a second memory region, in which a number of different types of files belonging to the second development project and a second file collection, in which all files relevant to the overall development project and belonging to the second development project are included, are stored,synchronizing and/or updating, via the second management unit, the second file collection and the files belonging to the second development project via the exported first data collection and importing the updated files into the second development project;
storing a rule set in the first memory region and/or in the second memory region, the exporting of the first file collection and/or the importing of the second file collection occurs by the respective management unit according to the rules defined in the rule set;
defining different types of files and categories for the different types of files in the rule set; and
assigning via the first management unit, during the incorporation of files in the file collection, at least one category to the file.
3 Assignments
0 Petitions
Accused Products
Abstract
A computer project management system and method for the creation of an electronic control unit software is provided. The system has a software architecture tool configured to design a graphical model of an electronic control unit for a motor vehicle. A behavior model tool converts the graphical model into a computer readable production code. A software container has a file generated based on the electronic control unit. A container manager compares the software container with a prior software container during the importation or exportation of the software container to or from the software architecture tool or the behavior model tool, and a comparison list is generated indicating whether interface modifications for the electronic control unit were made. The comparison list is then displayed to a user on a display screen.
-
Citations
24 Claims
-
1. A method for exchanging files and/or information for an overall development project between two development projects, the method comprising:
-
providing a computer system that includes a first development environment with a first development project and a second development environment with a second development project to develop software for an electronic control unit, the computer system having a first memory region, in which a number of different types of files belonging to a first development project, and a first file collection container or set of containers, which contains all files relevant for the overall development project and belonging to the first development project, are stored; providing, in the first development environment, a first management unit, in which initial information for all files belonging to the first development project are stored; checking, via the first management unit for the purpose of export, whether all files relevant to the overall development project and belonging to the first development system are inserted in a current version in the first file collection; updating, via a management unit, the first file collection, in that all files relevant to the overall development project and belonging to the first development system are included in a most recent version in the first file collection or left in the current version and deleting obsolete files; providing the updated first file collection to the second development environment, the second development environment having a second management unit, in which second information on all files belonging to the second development project are stored, the computer system having a second memory region, in which a number of different types of files belonging to the second development project and a second file collection, in which all files relevant to the overall development project and belonging to the second development project are included, are stored, synchronizing and/or updating, via the second management unit, the second file collection and the files belonging to the second development project via the exported first data collection and importing the updated files into the second development project; storing a rule set in the first memory region and/or in the second memory region, the exporting of the first file collection and/or the importing of the second file collection occurs by the respective management unit according to the rules defined in the rule set; defining different types of files and categories for the different types of files in the rule set; and assigning via the first management unit, during the incorporation of files in the file collection, at least one category to the file. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16)
-
-
17. A computer project management system comprising:
-
a software architecture tool configured to design/model a software architecture having software components, data files and interface definitions for an electronic control unit; a behavior model tool configured to convert a graphical model for a control program for an electronic control unit into a computer readable production code to be included into the software components; a software container having a file generated for development of software for the electronic control unit, the software container being imported or exported by either the software architecture tool or the behavior model tool; and a container manager configured to compare the software container with a prior software container during the importation or exportation of the software container to or from the software architecture tool or the behavior modeling tool, the container manager generating a comparison list indicating whether modifications in any of the software files/components for the electronic control unit were made and indicating a category for at least one of the software files, the comparison list being displayed to a user on a display screen, the container manager synchronizing the software container with the prior software container according to a predefined set of rules. - View Dependent Claims (18, 19, 20, 21)
-
-
22. A container manager for a computer project management system, the container manager comprising:
-
a rule set stored in a memory area, the rule set defining file categories and import and/or export behavior according to the file categories; and a comparison component configured to compare a first software container having a first set of data files including an AUTOSAR XML file generated by a software architecture tool based on a software architecture for an electronic control unit for a motor vehicle that is defined/modeled in the architecture modeling tool and compare first data files with a second software container having a second set of data files and a second AUTOSAR XML file or a second version of the first AUTOSAR XML file generated by a behavior modeling tool, wherein the comparison component generates a comparison list indicating modifications in any of the software files/components for the electronic control unit, and wherein the container manager synchronizes the first software container with the second software container according to a predefined set of rules. - View Dependent Claims (23, 24)
-
Specification