Menu
▾
▴
[Sblim-commit] ecute ToDo.txt,1.10,1.11 .project,1.2,1.3 TODOsForEcuteRSA.txt,1.6,NONE
|
From: Benjamin B. <bg...@us...> - 2005-05-19 14:53:36
|
Update of /cvsroot/sblim/ecute In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv4982 Modified Files: ToDo.txt .project Removed Files: TODOsForEcuteRSA.txt Log Message: Updated ToDo list Index: .project =================================================================== RCS file: /cvsroot/sblim/ecute/.project,v retrieving revision 1.2 retrieving revision 1.3 diff -u -d -r1.2 -r1.3 --- .project 7 Oct 2004 15:23:55 -0000 1.2 +++ .project 19 May 2005 14:53:26 -0000 1.3 @@ -1,6 +1,6 @@ <?xml version="1.0" encoding="UTF-8"?> <projectDescription> - <name>com.ibm.ecute</name> + <name>ecute</name> <comment></comment> <projects> </projects> Index: ToDo.txt =================================================================== RCS file: /cvsroot/sblim/ecute/ToDo.txt,v retrieving revision 1.10 retrieving revision 1.11 diff -u -d -r1.10 -r1.11 --- ToDo.txt 1 Apr 2005 17:41:04 -0000 1.10 +++ ToDo.txt 19 May 2005 14:53:26 -0000 1.11 @@ -1,7 +1,7 @@ ToDo List for ECUTE ------------------- -Last updated: 01-Apr-2005 AM +Last updated: 19-May-2005 BB 1. Problem: In Rose, there are two places where the Description qualifier for @@ -91,7 +91,6 @@ hierarchy top base classes, but cannot navigate back to the derived class or classes. - Solution: - Add a combo list with derived classes to the "Edit Qualifiers" dialog. @@ -225,7 +224,7 @@ - new screen shots 22. Add support to the UMLBuffer for qualifier definitions. Currently both - MOF plugins support qualifier definitions. This would also requiere to + MOF plugins support qualifier definitions. This would also require to update the Rose plugins to store this information in the package. Question: how could the user add/edit qualifier definitions in Rose? @@ -430,7 +429,7 @@ 34. Add a check&repair option for role names in associations. - The check would detect missing override qualifiers betwen equally named reference + The check would detect missing override qualifiers between equally named reference properties in a inheritance sequence as well as any change of role names along a chain of reference properties connected with override qualifiers. @@ -468,6 +467,59 @@ at com.ibm.ecute.EntryPoint.<init>(EntryPoint.java:216) at com.ibm.ecute.EntryPoint.main(EntryPoint.java:108) -38. (was 36.) The entry in the list of installed software (Win XP: Control - Panel / Add or Remove Programs) should state the version being installed. +ToDo's for Ecute integration into RSA +---------------------------------------- + +1. Edit Qualifiers Dialog: + 1. Implementation of the inheritance of the Qualifiers (using the "defined in" column). + 2. Implementation of "Remove Value" in the values tab. + 3. Replace the flavor column(s) in the edit and definition tab with one column called "Inheritance Behavior" which can + contain three values "Restricted", "ToSubclass EnableOverride", "ToSubclass DisableOverride" + 4. Remove the scope column from the values tab + 5. Implementation of apply and undo in the values tab as it is implemented in the definition tab + 6. Implementation of context menus for the tables in the Qualifiers Property Tab and the Edit Qualifiers Dialog + 7. Implementation of Back und Forward buttons in the values tab for a betteer navigation + 8. Implementation of a "Create overwritten property" function which automates the process of overwriting a class + property and setting the override qualifier + 9. Implementation of Clear, Load and Save buttons in the defintition tab + +2. Qualifers Property Tab + 1. Implementation of the qualifiers property tab for the model which should show the qualifier definitions for the + model only + +3. MOF Import + 1. Import of a XXX_Qualifiers.mof file should now update the qualifiers definitions in the model constraint instead + of the QualifiersList.txt + +4. Diagrams + 1. Implementation of a new CIM-Style for the CIM-Diagrams. Like it is done for Rose-Diagrams (see Window-Preferences-Modeling-Appearance-Apperance Style). (Maybe this can be done in the CIM-Profile) + 2. Auto applaying of the new CIM-Style for new Diagrams. + 3. Fixing the problem that the associations are not shown in the diagram. (see Point 2 of knownRSAProblems.txt). + 3. Implementation of the Associations-Diagrams (depends on the Point 4 of knownRSAProblems.txt). + +5. Wizards and Processing + 1. Implementation of F1-Help in the wizards. + 2. Improvement of the threading. Today while processing the wizard and the log dialog freezes in. + 3. Check the implementation of the CANCEL-Button. + 4. Make improvement of the ProgressBar. Today the progress bar will be initialized two times. Once for the Input-Plugin and once for the Output-Plugin. If your are parsing one big mof file, i. e. CIM_Schema.mof you see no proceeding progress. Better is a implementation of one initializing and a constant proceeding. + 5. To find out why the first processing(import/export) is much slower than the following processes (imports/exports). + 6. Implemenation of check and repair plug-in / check the Model Analysis which is provided by RSA maybe it is good enough. (See menuitem Modeling - Model Analysis) Check also the possiblilty to extend the Model Analysis to avoid multiple inheritance, associations without a association class and that a association class inherits form a normal class in the model. + 7. Implemenation of a Wizard to import CIM-Rose-Models + +6. CIM-UML-Mapping + 1. Implementation of 3-way-Associations (appears in CIM v. 2.9). 3-way-Associations are not possible in Rose, but are possible in RSA. Therefore the MOF-Parser must be changed. + 2. If qualifier ArrayType is of value "Ordered" or "Indexed" the derived Property attribute "isOrderd" should be set to "true". + +7. MOFParser + 1. Make error messages clearer. In example: + The (incorrect) Line : "string ClassName; /7 was an override of Name" results in the following error message: "Error: ws-cim-example3.mof(160): Token 256.0 not expected." Make these error messages clearer. + +8. RSAModelCreator + 1. Implementation of the Qualifier-Inheritance. Already done is inheritance of Min, Max and Aggregate. Inheritance of all other Qualfiers are left. + +9. RSAParser + 1. Problem: The direkt mapped qualifiers of type boolean will always set in case of true default, respectively will never set in case of false default. Because of their direct mapping you can not differ if they were state explicitly or by default. + The concerned qualifers are: Octetstring, Out, Static, Write + The In qualifier is not concerned because he should be always stated. + 2. Problem: The Min, Max, Key and Aggregate qualifiers should only be set if they are not stated in the superclass. --- TODOsForEcuteRSA.txt DELETED --- |
