UPDM 2.0 FTF Avatar
  1. OMG Issue

UPDM2 — Concern needs to be added to the AV-1

  • Key: UPDM2-21
  • Legacy Issue Number: 17263
  • Status: closed  
  • Source: International Business Machines ( Graham Bleakley)
  • Summary:

    Currently Concern is shown as a tagged value string within the concept ViewPoint element ( a stereotype based on package). This misses the general intent in MODAF where Concern is a stereotype of Usecase and where stakeholders can be associated directly with the usecase to indicate who is interested in what within the architecture model in question. THis is done via the dependency stereotype StakeholderHasConcern where the staekoholder can be an OrganisationalResource in MODAF. I would think that in UPDM the stakeholder should be allowed as either an OrganisationalResource or an actual organisational resource.

    The UPDM elements View and Viewpoint are stereotypes of package and this actually creates something of a browser structuring problem and should in my view be deleted/ changed. In MODAF View is used as an additional reading inststruction for a concern essentially implying that for each view instance created by an architect a proxy is created in AV-1 with the same name based with this proxy being a View stereotype of Class. This can also be connected to Concern in order to indicate in which views within the architecture that a certain concern can be found. All of these elements are essentially reading instructions. The element ArchitectureProduct in MODAF is also missing, it is also tied to concern and contains a list of the architecture elements that a given concern is associated with. Its current counterpart in UPDM would seem to be View ( a stereotyped package and as indicated previously the use of packages here represent a problem). It should be noted that a given concern can apply to more than one instance of an architectural view and that elements may well apply to more than one concern i,e, in both cases there is the possibility of many to many relationships, something that makes the use of packages as a means of structuring things very difficult.

  • Reported: UPDM 2.0 — Tue, 20 Mar 2012 04:00 GMT
  • Disposition: Resolved — UPDM 2.0.1
  • Disposition Summary:

    Lars indicated that concern should be added as first class element based upon Use case.

    There is a large impact due to clash between Concerns tag in SysML from which View/Viewpoint in UPDM are derived and also the inadequacies of the View/Viewpoint specification in SysML.

    Therefore it was decided to close this issue with no change.

    Proposed Disposition: Closed, no change

  • Updated: Fri, 6 Mar 2015 20:59 GMT