UML issues

[keni7385]

Yesterday we discussed briefly the UML at the end of the class. I have reviewed it again. There were some inheritance problems. Have you revised them?

I'm talking about the constraints, since there are many sub-classes inheriting from Constraint that have different methods among each other. Actually the relation is with Constraint, so the static description will contain only its methods. Same for effects, weapons and square.

Please, fix ASAP

[PaoloC96]

Buonasera, ci stiamo adottando a modificare l'uml per migliorarlo, grazie per la segnalazione.

Paolo Capra.

[PaoloC96]

Abbiamo finito di riorganizzare l'UML del Model, aggiungendo una classe helper per sistemare i problemi di passaggio di parametri su Effect, mentre per le altri classi abbiamo creato metodi astratti per gestire le sottoclassi. Speriamo di aver sistemato.

[keni7385]

Okay, it seems fine. Just a couple of points to think about:

• Check out if the Constraint, Effect and TargetParameter can be used to model the effects of powerups.
• I read in the TargetParameter's note, that it's used between client and server. But actually the code in the client shouldn't get access to model objects. Therefore doesn't have references to Player and Room objects in order to build a TargetParameter variable. Anyway it's enough for the client to transmit back a raw version of TargetParameter, such as an integer index of the player chosen to be targeted, the position of a square and so on... then the controller can help in validate the choice and map the index to the current objects on the model.

Finally I want to remind you that there is a soft deadline for your network rationale on the 7th of May. Finish your model implementation and get some working tests, especially for the weapons, ASAP. There is not so much time.

[PaoloC96]

Grazie mille per i consigli, ci metteremo a lavorarci subito sopra.