Issue 18195: Need packages overview diagram and explicit depiction of package dependencies (uml25-ftf)
Source: Simula Research Laboratory (Mr. Bran Selic, selic(at)acm.org)
Nature: Uncategorized Issue
Severity: 
Summary: In the current 2.5 metamodel, there is a diagram that simply shows all the various packages that comprise it. Note, however, that we do not have such a diagram in the spec itself. In fact, as far as I can tell, it seems that the spec does not even mention explicitly that the metamodel is divided up into these packages. 

Furthermore, it is useful to see the dependencies between the various packages captured explicitly in diagrams. In a sense, this shows the intended couplings between the various modules, which is usually important architectural information. Not showing them explicitly either in the spec or in a metamodel diagram is obscuring this and could lead to corruption of the architecture in subsequent maintenance (e.g., the introduction of undesired and even incorrect couplings between the packages).

Resolution: 
Revised Text: 
Actions taken:
October 23, 2012: received issue
Discussion: 


End of Annotations:=====
M-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:from:date:x-google-sender-auth:message-id
         :subject:to:content-type;
        bh=EwrkAvS4o1j6yP+oUcPwkr6+3uBdUacWPn9/BRuTHas=;
        b=ZDji5d4QloyKIdhTqNaimLTl13WfUhFeFZhGren2VF47zW2jng0xbc71CmYKHtQd8V
         3i3+AzgIcYG00cXIGLJ1jg2MuMrXzci0elrqigFpNDzhnZb1YEs7S7Nb21lb40kRmYgK
         U1FBV8ErIZJqCTHTHQ2Rh+WmDpxML7JgwSBRVUpFi40fq4TAouyNRtZpE5Rtqm5GhcQb
         khCXTK46bYOvcKvxbp6Jcn2U0+WVwVUxO6SbfqXhiV04smsBCWOd9ooPiyLAxG5GnuTd
         hS5sPwNeMe9gWhkJk+J0+RYZGyawRXJCd2Izk7g3Dxw6as0LMDjSUywHJ4MFC6GxbZN4
         rKjQ==
Sender: bran.selic@gmail.com
From: Bran Selic <selic@acm.org>
Date: Tue, 23 Oct 2012 11:37:39 -0400
X-Google-Sender-Auth: pGPchjOW4ScmYZ40PL-kIt2Usew
Subject: UML 2.5: Need packages overview diagram and explicit depiction of
 package dependencies
To: issues@omg.org


In the current 2.5 metamodel, there is a diagram that simply shows all the various packages that comprise it. Note, however, that we do not have such a diagram in the spec itself. In fact, as far as I can tell, it seems that the spec does not even mention explicitly that the metamodel is divided up into these packages. 

Furthermore, it is useful to see the dependencies between the various packages captured explicitly in diagrams. In a sense, this shows the intended couplings between the various modules, which is usually important architectural information. Not showing them explicitly either in the spec or in a metamodel diagram is obscuring this and could lead to corruption of the architecture in subsequent maintenance (e.g., the introduction of undesired and even incorrect couplings between the packages).