Hei Leandro,

I can't realy answer on your question as I am not sure as well what
would belong into the classes. Just start with one example (Buffer of
features) and program all the stuff you need for it. If that is done,
you go on with the next example (i.e. intersect two polygon layers).
Then.. you will see if additional things (methods, fields) are needed -
or if even something is not needed. IF you have done this you go on with
the next case (e.g. calculation of a plan graph from a line file). Now
you will see again what is good and what is missing.
You know.. so you will develop in small cycles and the content of the
abstract classes becomes more and more clear. (i think they call that
agile progamming??:
http://pt.wikipedia.org/wiki/Desenvolvimento_%C3%A1gil_de_software ..
but at least you do work iterative)

I hope you see what I mean.

stefan

Leandro Leal Parente schrieb:
> Hi Mentors:
> 
> I make same changes in my UML diagram, please take a look.
> 
> I will explain all classes:
> 
> *AbstractObject:* that classe is father of many classes into Open 
> ModelBuilder. it is contains name fields and description field;
> *
> AbstractParameter:* that classe will be a father of all parameter 
> (Raster Layer, table, String, int, Vector Layer). I don't know what 
> fields I need to put into the AbstractParamenter, because the parameters 
> are so diferents. I can't see in common variables fields for put into 
> that classe. Are you can help me ?
> 
> *AbstractAlgorthim:* that classe will be a father of all Algorithm 
> (Union Feature Collection, algorithm for process a buffer). I think that 
> classes is fundamental, because the algorithms will be compose all 
> procedures for extension. For example, if a new algorithn for calculated 
> a buffer will be discovered and I will want change my buffer algorithm 
> because it be inefficient. I simply modify my classe BufferAlgorithn and 
> all procedure that use that algorithm will be use my new buffer 
> algorithm. But I have same trouble in AbstratcAlgorithm, there are many 
> algorithms and that algorithms have many parameters diferents, how I 
> will put all types the parameters into AbstratctAlgorithm (one abstract 
> classe) ? I think in implement one classes for encapsulated all 
> parameters, same like algortihmsParamenter. So any parameter for 
> algorthtim was store into that classe, is a good solution ?
> *
> AbstractProcedure:* that classe will be a father of all procedures 
> (Union, Difference, Intersection, Buffer). That classe will be compose 
> to many algorithms and will received AbstractParameters, and return 
> AbstractParameters.
> *
> ModelProcess: *that classe will be a model whit user constructing. it 
> will contain procedures and parameters, but I don't know how I will 
> store that into data structure. I think to implement a ModelTree with 
> ProcedureNodes, is a good solution ?
> *
> Future AbstractObjects: *All abstractObjects (Parameters, Algorithms and 
> Procedures) was store into their folder (/lib/Paramenter, /lib/Algorithm 
> and lib/procedures).
> *
> Library*: one library will be encapsule abstractObject (Parameters, 
> Algorithms and Procedures). When one AbstratcObject was request the 
> class go into their folder (/lib/Paramenter, /lib/Algorithm or 
> lib/procedures) get a AbstractObject required, initialize that and 
> return it. So I need to have 3 library or just 1 ? Because one library 
> will be realize same operations.
> 
> *ModelBuiler: *that classe will encapsule all library and make a 
> modelProcess. It will be communication whit GUIModel and interpret all 
> users orders.
> 
> *GUIManagePocedures:* Manage a procedures;
> *
> GUIModelBuiled:* Construct all GUI for parameters, procedures and 
> graphic process models.
> 
> I need to decide if this is a good UML Diagram and a good solution, 
> because in next week a want implements it.
> 
> Thanks,
> Leandro Leal;
> 
> PS: Please list for me all AbstractParameters I will be implement, 
> because I so confuse about this.
> 
> ------------------------------------------------------------------------
> 
_______________________________________________
jump-devel mailing list
[EMAIL PROTECTED]
http://lists.refractions.net/mailman/listinfo/jump-devel



-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Reply via email to