# Changes introduced after the meeting on 12.02.2016:
* rename *SoftwareComponent* -> *Software*
* removed *IPosition* interface that was implemented by the *End* and the *Intermediate* . Now
* Source/Destination Flow is now represented as *Flow* with single source *Software* and 1+ destination *Software*
**FlowRoute* is not exposed to the modeller. Only *Direction* s should be used from now to model routes.
* Switching in SDN-mode can be done in three ways (depending on *SdnFlowRule*):
1. Using Hardware switching table with probability defined for each tuple ( *Flow*, *Node*)
1. Using Software switching table with probability defined for each tuple ( *Flow*, *Node*)
1. Using *SdnController* with probability defined for each tuple ( *Flow*, *Node*)
**SdnController* serves only as a software container for *SdnControllerApplication* s
* Performance of switching using *SdnController* depends on:
* Mapping of *SdnControllerApplication* to: *SdnController*, *Flow*, *Node* (using *SdnFlowRule* ). *SdnControllerApplication* X will be activated only for a given combination: *Flow*, *Node* and *Controller* (if many) [[SdnControllerApp example png]][sdnapp-example.png][[SdnControllerApp example PDF]][sdnapp-example.pdf][[SdnControllerApp example2 png]][sdnapp-example2.png][[SdnControllerApp example2 PDF]][sdnapp-example2.pdf]
**SdnController* should have at least one *SdnControllerApplication* (the default one) that works for all flows
