Dr Darren says:
This is one of the biggest misconceptions I encounter, in part because the MagicDraw SysML and Cameo tools unnecessarily "hide" standard Ports in many places (presumably under the impression that just because SysML introduces something extra only that should be used). Read these relevant "snippets" from the spec and you'll see it is simply not true!
From the SysML-1.6 specification itself:
SysML-1.6: 'Proxy and full ports support the capabilities of ports in general, but these capabilities are also available on ports that are not declared as proxy or full.'
SysML-1.6: 'Modelers can choose between proxy or full ports at any time in the development lifecycle, or not at all, depending on their methodology.'
SysML-1.6: 'Modelers have the option of applying stereotypes for proxy and full ports to indicate whether ports are specifying features of their owners and internal parts (proxy), or for themselves separately (full). This is a concern when defining ports, rather ...'
SysML-1.6: 'Using existing blocks with ports only requires knowing the port types, because they define the features available for linking or communication with those ports via connectors.'
SysML-1.6: 'Modelers can apply stereotypes for proxy and full ports at any stage of model development, or not all if the stereotype constraints are not needed.'
SysML-1.6: 'Figure 9-7 happens to use unstereotyped ports on a general block distributed to users, and stereotyped ports on its specializations for implementation, but the modelers might have not used stereotypes at all, if they did not care whether the model met ...'
SysML-1.6: 'Unstereotyped ports do not commit to whether they are proxy or full, and do not prevent or dictate future application of the stereotypes, except for ports that violate constraints of the stereotypes.'
SysML-1.6: 'Unstereotyped ports have the basic functionality of stereotyped ones, including flow properties and nested ports, so they can be used as long as the modeler is not concerned with the distinction between proxy and full, and the constraints they impose.'
SysML-1.6: 'All ports and nested ports (i.e., proxy, full, and ports with no stereotype applied), and their type definitions (e.g., interface blocks, blocks) can include compartments with textual and graphical representations to display their features ...'Therefore:
Webel Best Practice strongly recommends that you DO NOT commit to using ProxyPort or FullPort early on in projects unless you are a true expert and know exactly why you are doing it. And not using ProxyPort and FullPort will also save you a lot of notational clutter.It will help if you "un-tweak" some things in MagicDraw/Cameo: