Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Enhanced Service Information Model for Nested and Shared Services

Minutes

  1. serviceProperties
    1. This can be associated to serviceProperties currently is associated with Service Descriptor, but it could be related to VND as well, so it should associate with the root: design entity, Kevin will do the job of modeling update the UML papyrus for this part, he will email if need any help, Chuyi, Borislav and other people who interested if there have issues needing discussionothers could help
    2. Borislav will check implementation of these properties.whthere how to implement those properties in SDC and runtime components (OOF, SO, SDNC et al..)
    3. Chuyi has one concern of about how to model the relationship between Service descriptor and serviceProperties.
  2. maxAvailableNumber
    1. The complex structure should This structure currently in Service Descriptor should belong to VES model, Kevin will invite Alok Gupta to join next Service IM to discuss how to model this in structure in VES. Chuyi will creat a new wiki page for this topicit
  3. Slicing model construction
    1. Chuyi suggeted to start from NSMF, and show two options to model servicePropeties.
    2. The problem is how do we package the service attributes and the way using them across APIs, MEF has some similar work, Andy will talk to MEF guys to seek potential solution. 
    3. The challenge for slicing model is how run time components will consume the attributes and the nested structure; in design time, we have one input, but on run time, we may have many values, this may need a model solution, and who should take the responsiblity to give the value.  

...