Menu

#361 OASIS:FunctionalBreakdown - why mandatory versionId?

pending
None
accepted
5
2016-10-17
2014-08-19
Phil Spiby
No

At present the PSM allows all subtypes of ProductVersion to have [0..*] identifiers, however the templates for FunctionalBreakdown, PhysicalBreakdown and SystemBreakdown all specify a versionId as being [1] then provide a note explaining what happens when no versionId is provided.

I suggest making the versionId property of these templates [0..*] to be fully compatible with the PSM.

Related

PLCS templates: #361

Discussion

  • Phil Spiby

    Phil Spiby - 2015-09-30

    Templates Breakdown, FunctionalBreakdown, PhysicalBreakdown & SystemBreakdown have been updated. In addition to the recommended change, the name of the property havs been changed to versionIds to reflect the fact that multiple identifiers can be used for the version.

     
  • Phil Spiby

    Phil Spiby - 2015-09-30
    • status: open --> pending-accepted
     
    • Mats Nilsson - FMV

      Isn't the purpose of templates to advocate a best recommended way to use the PSM?!
      Therefore Templates doesn't need to be "compatible with the PSM".
      /M

      Från: Phil Spiby [mailto:philsp@users.sf.net]
      Skickat: den 30 september 2015 13:40
      Till: [plcslib:plcs-templates]
      Ämne: [plcslib:plcs-templates] #361 OASIS:FunctionalBreakdown - why mandatory versionId?

      • status: open --> pending-accepted

      [plcs-templates:#361]http://sourceforge.net/p/plcslib/plcs-templates/361/ OASIS:FunctionalBreakdown - why mandatory versionId?

      Status: pending-accepted
      Group: plcs-plcslib-v1.0-cs03
      Created: Tue Aug 19, 2014 03:41 PM UTC by Phil Spiby
      Last Updated: Wed Sep 30, 2015 11:33 AM UTC
      Owner: Phil Spiby

      At present the PSM allows all subtypes of ProductVersion to have [0..*] identifiers, however the templates for FunctionalBreakdown, PhysicalBreakdown and SystemBreakdown all specify a versionId as being [1] then provide a note explaining what happens when no versionId is provided.

      I suggest making the versionId property of these templates [0..*] to be fully compatible with the PSM.


      Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/plcslib/plcs-templates/361/

      To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

       

      Related

      PLCS templates: #361

  • Phil Spiby

    Phil Spiby - 2015-09-30

    I agree that just making the templates compatible with the PSM should not be a goal. However, making sure the templates reflect current best practice is required. This issue was raised by BAE Maritime Services where their breakdowns do not have version identifiers (there is only one version of the breakdown, change is managed through effectivity). Therefore in order to use the OASIS template dummy data was having to be created. I am sure the goal of PLCS is not to enforce creation of dummy data as part of the Assured Product Support Information ;-)

     
  • Phil Spiby

    Phil Spiby - 2015-10-01

    Checking in Breakdown.png;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/Breakdown/Breakdown.png,v <-- Breakdown.png
    new revision: 1.8; previous revision: 1.7
    done
    Checking in Breakdown.xmi;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/Breakdown/Breakdown.xmi,v <-- Breakdown.xmi
    new revision: 1.9; previous revision: 1.8
    done
    Checking in Template.png;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/Breakdown/Template.png,v <-- Template.png
    new revision: 1.9; previous revision: 1.8
    done
    Checking in imagemap.xml;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/Breakdown/imagemap.xml,v <-- imagemap.xml
    new revision: 1.7; previous revision: 1.6
    done
    Checking in template.xml;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/Breakdown/template.xml,v <-- template.xml
    new revision: 1.13; previous revision: 1.12
    done
    Checking in dvlp/Breakdown.notation;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/Breakdown/dvlp/Breakdown.notation,v <-- Breakdown.notation
    new revision: 1.3; previous revision: 1.2
    done
    Checking in dvlp/Breakdown.uml;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/Breakdown/dvlp/Breakdown.uml,v <-- Breakdown.uml
    new revision: 1.3; previous revision: 1.2
    done
    Checking in dvlp/Breakdown.ump;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/Breakdown/dvlp/Breakdown.ump,v <-- Breakdown.ump
    new revision: 1.4; previous revision: 1.3
    done
    Checking in dvlp/UUIDs.xml;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/Breakdown/dvlp/UUIDs.xml,v <-- UUIDs.xml
    new revision: 1.7; previous revision: 1.6
    done​

     
  • Phil Spiby

    Phil Spiby - 2015-10-01

    Checking in FunctionalBreakdown.png;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/FunctionalBreakdown/FunctionalBreakdown.png,v <-- FunctionalBreakdown.png
    new revision: 1.4; previous revision: 1.3
    done
    Checking in FunctionalBreakdown.xmi;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/FunctionalBreakdown/FunctionalBreakdown.xmi,v <-- FunctionalBreakdown.xmi
    new revision: 1.5; previous revision: 1.4
    done
    Checking in Template.png;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/FunctionalBreakdown/Template.png,v <-- Template.png
    new revision: 1.4; previous revision: 1.3
    done
    Checking in imagemap.xml;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/FunctionalBreakdown/imagemap.xml,v <-- imagemap.xml
    new revision: 1.4; previous revision: 1.3
    done
    Checking in template.xml;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/FunctionalBreakdown/template.xml,v <-- template.xml
    new revision: 1.7; previous revision: 1.6
    done
    Checking in dvlp/FunctionalBreakdown.notation;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/FunctionalBreakdown/dvlp/FunctionalBreakdown.notation,v <-- FunctionalBreakdown.notation
    new revision: 1.3; previous revision: 1.2
    done
    Checking in dvlp/FunctionalBreakdown.uml;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/FunctionalBreakdown/dvlp/FunctionalBreakdown.uml,v <-- FunctionalBreakdown.uml
    new revision: 1.3; previous revision: 1.2
    done
    Checking in dvlp/FunctionalBreakdown.ump;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/FunctionalBreakdown/dvlp/FunctionalBreakdown.ump,v <-- FunctionalBreakdown.ump
    new revision: 1.4; previous revision: 1.3
    done
    Checking in dvlp/UUIDs.xml;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/FunctionalBreakdown/dvlp/UUIDs.xml,v <-- UUIDs.xml
    new revision: 1.4; previous revision: 1.3
    done​

     
  • Phil Spiby

    Phil Spiby - 2015-10-01

    Checking in PhysicalBreakdown.png;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/PhysicalBreakdown/PhysicalBreakdown.png,v <-- PhysicalBreakdown.png
    new revision: 1.4; previous revision: 1.3
    done
    Checking in PhysicalBreakdown.xmi;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/PhysicalBreakdown/PhysicalBreakdown.xmi,v <-- PhysicalBreakdown.xmi
    new revision: 1.5; previous revision: 1.4
    done
    Checking in Template.png;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/PhysicalBreakdown/Template.png,v <-- Template.png
    new revision: 1.4; previous revision: 1.3
    done
    Checking in imagemap.xml;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/PhysicalBreakdown/imagemap.xml,v <-- imagemap.xml
    new revision: 1.4; previous revision: 1.3
    done
    Checking in template.xml;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/PhysicalBreakdown/template.xml,v <-- template.xml
    new revision: 1.7; previous revision: 1.6
    done
    Checking in dvlp/PhysicalBreakdown.notation;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/PhysicalBreakdown/dvlp/PhysicalBreakdown.notation,v <-- PhysicalBreakdown.notation
    new revision: 1.3; previous revision: 1.2
    done
    Checking in dvlp/PhysicalBreakdown.uml;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/PhysicalBreakdown/dvlp/PhysicalBreakdown.uml,v <-- PhysicalBreakdown.uml
    new revision: 1.3; previous revision: 1.2
    done
    Checking in dvlp/PhysicalBreakdown.ump;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/PhysicalBreakdown/dvlp/PhysicalBreakdown.ump,v <-- PhysicalBreakdown.ump
    new revision: 1.4; previous revision: 1.3
    done
    Checking in dvlp/UUIDs.xml;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/PhysicalBreakdown/dvlp/UUIDs.xml,v <-- UUIDs.xml
    new revision: 1.4; previous revision: 1.3
    done

     
  • Phil Spiby

    Phil Spiby - 2015-10-01

    Checking in SystemBreakdown.png;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/SystemBreakdown/SystemBreakdown.png,v <-- SystemBreakdown.png
    new revision: 1.6; previous revision: 1.5
    done
    Checking in SystemBreakdown.xmi;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/SystemBreakdown/SystemBreakdown.xmi,v <-- SystemBreakdown.xmi
    new revision: 1.8; previous revision: 1.7
    done
    Checking in Template.png;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/SystemBreakdown/Template.png,v <-- Template.png
    new revision: 1.7; previous revision: 1.6
    done
    Checking in imagemap.xml;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/SystemBreakdown/imagemap.xml,v <-- imagemap.xml
    new revision: 1.7; previous revision: 1.6
    done
    Checking in template.xml;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/SystemBreakdown/template.xml,v <-- template.xml
    new revision: 1.10; previous revision: 1.9
    done
    Checking in dvlp/SystemBreakdown.notation;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/SystemBreakdown/dvlp/SystemBreakdown.notation,v <-- SystemBreakdown.notation
    new revision: 1.3; previous revision: 1.2
    done
    Checking in dvlp/SystemBreakdown.uml;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/SystemBreakdown/dvlp/SystemBreakdown.uml,v <-- SystemBreakdown.uml
    new revision: 1.3; previous revision: 1.2
    done
    Checking in dvlp/SystemBreakdown.ump;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/SystemBreakdown/dvlp/SystemBreakdown.ump,v <-- SystemBreakdown.ump
    new revision: 1.6; previous revision: 1.5
    done
    Checking in dvlp/UUIDs.xml;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/SystemBreakdown/dvlp/UUIDs.xml,v <-- UUIDs.xml
    new revision: 1.6; previous revision: 1.5
    done​

     
  • Phil Spiby

    Phil Spiby - 2015-10-01

    Checking in dvlp/OASISBreakdown.mdxml;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/Breakdown/dvlp/OASISBreakdown.mdxml,v <-- OASISBreakdown.mdxml
    new revision: 1.12; previous revision: 1.11
    done

     
  • Phil Spiby

    Phil Spiby - 2015-10-01

    Checking in dvlp/OASISFunctionalBreakdown.mdxml;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/FunctionalBreakdown/dvlp/OASISFunctionalBreakdown.mdxml,v <-- OASISFunctionalBreakdown.mdxml
    new revision: 1.7; previous revision: 1.6
    done

     
  • Phil Spiby

    Phil Spiby - 2015-10-01

    Checking in dvlp/OASISPhysicalBreakdown.mdxml;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/PhysicalBreakdown/dvlp/OASISPhysicalBreakdown.mdxml,v <-- OASISPhysicalBreakdown.mdxml
    new revision: 1.7; previous revision: 1.6
    done

     
  • Phil Spiby

    Phil Spiby - 2015-10-01

    Checking in dvlp/OASISSystemBreakdown.mdxml;
    /cvsroot/plcslib/plcslib/data/contexts/OASIS/templates/SystemBreakdown/dvlp/OASISSystemBreakdown.mdxml,v <-- OASISSystemBreakdown.mdxml
    new revision: 1.10; previous revision: 1.9
    done

     
  • Phil Spiby

    Phil Spiby - 2016-10-17
    • status: pending-accepted --> pending
    • Resolution: none --> accepted
    • Group: plcs-plcslib-v1.0-cs03 --> plcs-plcslib-v1.1-wd01
     

Log in to post a comment.