• No labels

2 Comments

  1. Comments on this model:

    1.  General
      1. You should use GenDoc to generate the definitions of all your classes/attributes/datatypes, etc. on this wiki page so that the reader can see what they are.
      2. Many of your classes/attributes don't have definitions in Papyrus, thus I don't know what they mean.
      3. No decision has been made by the modeling team to use terms like "onboarded" or "internal" in class names to distinguish between the two. My opinion on this is that the distinction should be at the sub-model level in Papyrus and not at the class level.
      4. Many of your classes have attributes that should be in higher level classes from which your sub-classes inherit. We need to work through this to abstract them out.
      5. You are missing the lifecycle stereotype on all your classes/attributes (i.e. "Experimental")
    2. ResourceDesc after next Monday will be in the Resource model. You shouldn't create a copy here, but put the one from the Resource model on your diagram.
    3. InternalServiceDesciptor (which should be ServiceDescriptor)
      1. ServiceDescriptor should inherit from Descriptor which will be in the Common sub-model and contain many of the attributes you have specified here like: id, name, description, version, etc.
      2. ServiceType and ServiceRole belong in the instance only. The way you have defined it is redundant.
      3. Category and ServiceType appear to be the same thing.
      4. ProviderDetails should be an association to an NSD and not an attribute (that is undefined by the way)
      5. What's the difference between SLA and serviceLevel?
      6. bandwidth and QoS are global concepts that need to go into Common, not Service.
    4. Both GlobalType and CustomizedType can be defined by the MetaData class that will be in the Root model. Since you define neither one in the model, could you please define the difference between the two and why you think you need 2 classes?
    5. OnboardedNSdescriptor - Please don't create your own classes when the class exists in a different model. There is an NSD already in the model.
    6. There is nothing specific to Service about an Attachment. This is a BusinessObject that will be in the Common model and should be referenced once it is created.
    7. Your sliceProfile should be defined as MetaData.
    8. Your serviceInstance class doesn't need to have its attributes defined with the prefix "serviceInstance", i.e. serviceInstanceId.
    9. Your "wrappedAsNetworkService" seems to be incorrect. Your association is between ServiceDescriptors, not services.


    1. Hi Jessie,

      Thanks a lot for your comments. Actually this is a draft work based on the assupmtion the NS decriptor might be combined into service descriptor. We discussed about this draft work per time in Service IM call before.   I agree with most of your suggestions.

      I haven't done the alignment work yet with the root model since I think there are too much thing that is not clear like how to model NS internally and this draft work may need to be obsolete.

      I'm not sure whether are we going to use the root model or core model?

      For other details and my confusion of some operations, I would like to consult you and kevin during the Papyrus call.