Hmm, apples and pears being compared here? An instance is something concrete made from a blueprint. A property is something that makes the blueprint (and its instance) unique.
q.
I define a System-of-systems where a system is defined as
An integrated set of elements, subsystems, or assemblies that accomplish a defined objective. These elements include products (hardware, software, firmware), processes, people, information, techniques, facilities, services, and other support elements.
Every system is consists of an organization and a technical subsystem (which can consist of several systems).
The organization have roles.
What I have a hard time grasping is how "deep" the blueprint should be.
We want to use the blueprint for different occasions, let's say two times a year. Role A and Role B are defined as properties, blueprinted, of the organization for System 1.
I create an instance of System 1 for the first occasion, and inherit, the organization and roles. I can select from the parts/properties window which role should be a part of the system 1 organization instance.
Lets say for the first occasion and instance we only have Role A, and the multiplicity is 3.
The next occasion, I create a new instance of System 1, inherit the Organization and once again use the parts/properties window to select roles. This time I choose both Role A and Role B. For Role A I change the multiplicity to 2, and the multiplicity for Role B is 1.
But since I now changed the multiplicity for Role A, if I have a look at the instance for the first occasion and organization, it says Role A has a multiplicity of 2, which is not correct.
I might be over explaining this, because I think you all catch my drift, and I guess my main issue is:
What should be blueprinted (parts/properties) and what should be instances? When do I inherit parts/properties?
