Top Banner
Architettura software La scelta architetturale: MVA (Model – View – Adapter/Control) The view is completely decoupled from the model such that view and the model can interact only via the mediating controller or adapter in between the view and the model”. Only the adapter or mediating controller has knowledge of both the model and the view, because it is the responsibility of solely the adapter or mediating controller to adapt or mediate between the model and the view” [Wikipedia] UNIFIED PROCESS – ELABORAZIONE 1 1
11

Architettura software La scelta architetturale: MVA (Model – View – Adapter/Control) The view is completely decoupled from the model such that view and.

May 02, 2015

Download

Documents

Letizia Abate
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Architettura software La scelta architetturale: MVA (Model – View – Adapter/Control) The view is completely decoupled from the model such that view and.

Architettura softwareLa scelta architetturale:

MVA (Model – View – Adapter/Control)

• “The view is completely decoupled from the model such that view and the model can interact only via the mediating controller or adapter in between the view and the model”.

• “Only the adapter or mediating controller has knowledge of both the model and the view, because it is the responsibility of solely the adapter or mediating controller to adapt or mediate between the model and the view” [Wikipedia]

UNIFIED PROCESS – ELABORAZIONE 11

Page 2: Architettura software La scelta architetturale: MVA (Model – View – Adapter/Control) The view is completely decoupled from the model such that view and.

Architettura software“The model and view are kept intentionally oblivious of each other”

UNIFIED PROCESS – ELABORAZIONE 12

Page 3: Architettura software La scelta architetturale: MVA (Model – View – Adapter/Control) The view is completely decoupled from the model such that view and.

Il diagramma dei packageUNIFIED PROCESS – ELABORAZIONE 23

Page 4: Architettura software La scelta architetturale: MVA (Model – View – Adapter/Control) The view is completely decoupled from the model such that view and.

Il diagramma dei packageUNIFIED PROCESS – ELABORAZIONE 14

Page 5: Architettura software La scelta architetturale: MVA (Model – View – Adapter/Control) The view is completely decoupled from the model such that view and.

Il diagramma di Deploy

Page 6: Architettura software La scelta architetturale: MVA (Model – View – Adapter/Control) The view is completely decoupled from the model such that view and.

Il diagramma delle classi – Il ClientUNIFIED PROCESS – ELABORAZIONE 16

Page 7: Architettura software La scelta architetturale: MVA (Model – View – Adapter/Control) The view is completely decoupled from the model such that view and.

Il diagramma delle classi – Il ClientUNIFIED PROCESS – ELABORAZIONE 17

Page 8: Architettura software La scelta architetturale: MVA (Model – View – Adapter/Control) The view is completely decoupled from the model such that view and.

Il diagramma delle classi – Il ServerUNIFIED PROCESS – ELABORAZIONE 18

Page 9: Architettura software La scelta architetturale: MVA (Model – View – Adapter/Control) The view is completely decoupled from the model such that view and.

Il diagramma delle classi – Il ServerUNIFIED PROCESS – ELABORAZIONE 19

Page 10: Architettura software La scelta architetturale: MVA (Model – View – Adapter/Control) The view is completely decoupled from the model such that view and.

Il diagramma delle classi – Il server

Page 11: Architettura software La scelta architetturale: MVA (Model – View – Adapter/Control) The view is completely decoupled from the model such that view and.

Il diagramma delle classi – Il server