SysML Flexibility including multiplicity

[Ted Speers]

I am trying to understand mutliplicity (among other things)

Things I would like to do include:
Declare cardinality of block (say 0..*) (either on the block itself or on the composing connector) and then in the IBD add three individual instances of the resultant part and connect them up differently ... eg part[0] to part 'a' and part [1] to part 'b'.  Instead, if I declare cardinality on the block, I get a part labled 'part[0..*] and no obvious way to single out part[1] from part[2].  I can't put two instances of a part in a diagram as I was expecting.

Include a part in the ibd that inherits from one of the composing parts ... say part a, b and c are specializations of d.  I want to say e is composed of 3 d's and then in the ibd, use 1 each of a, b and c.

Among the many things I don't understand (I've been at EA for 30 days, SysML for a weekend):

I can't tell when some things are information and others have a real impact on the model ... i can make the cardinality of a block 2 and then have a connector with multiplicity 3 attached to it ... seems illegal

If a declare a port has multplicity of [0..2], how do a connect port[0] to block 'a', port[1] to block 'b', etc?  Now say the block has a multiplity of [0..1] ... I want to connect block[1]port[0] to block 'a' and bloclk[0]port[0] to block 'b'.

Does the import connector do anything?  If I import pkg 'a' into pkg b' and 'a' contains 'c' ... how do i refer to b.c ... i would also expect to be able to display the imported contents inside the package

[qwerty]

Chances are better to get an answer if you ask a single question per thread, rather than "explain me UML and SysML".

q.