My objectives x Current state

        -Get ArgoUML Critics ready for UML1.4 (3513) /2.0
        - take into account the issue 1255
        - study UML 1.4/2.0 WFR (Well Formed Rules) and propose an extension
            to the current implementation in order to make it
            able to implement all the WFR.
                + Updated the comments in all currently implemented WFRs,
                  referencing the correct metaclass, critic number and page 
number
                  in UML 1.4.2 Specification

                + I also made a "map" of the current ArgoUML critics coverage, 
it
                  can be found in issue 5260

                + organized the current critics in profiles (the WFRs are
                  in the UML 1.4 profiles and the other are in other profiles)
                  so that, when we update to UML 2.0 we just need to change
                  the ProfileUML class (or keep both). The new profiles are:
                        + Critics for Good Practices
                        + Critics for Code Generation

                + I concluded that no deep change was needed to make the critics
                  subsystem able to implement UML 1.4/2.0 critics, apart from
                  a better template for the "description" field.


         - implement some of the missing ones critics
           (as a proof of concept)

                + instead of implementing only some of them as a proof of 
concept,
                  I implemented most of the WFRs in the core package

                  (the list of missing ones can be found in issue 5260)

                + Added new critics to cover the WFRs over the utilization of 
the
                  ProfileMeta (in the next item) (issue 5305)

        - take into account future eclipse compatibility
        - move current profile things to a text file decriptor
                + the future eclipse compatibility was taken into account by
                  enabling the creation of new profiles by defining their 
characteristics
                  in the jar manifest and in the XMI, by the means of 
TaggedValues
                  defined by the ProfileMeta. This reduced the dependency 
between
                  the profile's code and the ArgoUML code, so that, if ArgoUML
                  goes to eclipse in the future, we will just change the 
interpretation
                  of the description files.

                + this compatibility was also enabled by the ocl interpreter,
                  which allows the critics being specified directly in OCL

                + this work was taken into account in issue 5029

        - OCL interpreter for specifying critics
                + I implemented a great part of the OCL language, and 
implemented
                  tests for it. The current coverage can be seen by the means
                  of the comments in the EvaluateExpression class and by the 
tests
                  in the TestEvaluateExpression class.

                + The implementation is organized in a flexible way, such that,
                  it would be easy to update it to UML/OCL 2.0, or to extend it
                  to other uses of OCL.
        
                + Replaced OclEvaluator with my new interpreter
        
                + this work was taken into account in issue 5042
                
        - define the wizard definition language
        - implement a parser for this language
        - implement the GUI generator
                + NOT DONE

the report in http://maurelio1234.googlepages.com/gsoc2008 was also
updated, but I also need to add some of the new TaggedValues defined
by the meta profile.

maas

-- 
-
http://www.marcosaurelio.com
*1984 +2057

"...acredito que basicamente é um retrocesso você querer evoluir e
progredir na sua vida e ao mesmo tempo pedir ajuda e intervenção
divina. Os nossos problemas nos tornam melhores, evoluidos,
precavidos, experientes, etc. então porque diabos eu iria querer me
livrar deles?"

mandrake

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to