UML 1.4 NO IDEA Avatar
  1. OMG Issue

UML14 — Corrections and improvements to glossary definitions

  • Key: UML14-377
  • Legacy Issue Number: 6447
  • Status: closed  
  • Source: Pivot Point ( Cris Kobryn)
  • Summary:

    Description: Consider the following corrections and improvements to Terms
    and Definitions:

    Activation ­ Consider changing from “the execution of an action” to
    “initiating the execution of an action”.

    Analysis ­ Delete the term “software”.

    Artifact ­ Delete the term “software”.

    Comment ­ Replace term “note” with “comment”.
    Runtime. run-time for a physical system, to imply execution of the
    operational system. (S-pg 252)

    Deployment diagram ­ Replace “software artifacts as nodes” with “artifacts
    on nodes”. Delete the term software and change as to on.

    Design ­ Delete the term “software”. Delete “required functional and
    quality”. This is too restrictive, and doesn't include physical
    requirements, etc.

    Design time - Delete the term “software”.

    Development process - Delete the term “software”.

    Diagram ­ Update the types of diagrams to be consistent with the proposal
    (i.e. timing diagrams, structure diagrams, information flow, etc)

    Generalization ­ Insert “indirect” prior to “instance of the general

    Inheritance ­ Delete last fragment “related by behavior”.

    Interaction diagram ­ Include reference to timing diagram.

    Interaction overview diagram ­ delete “s” on nodes

    Layer ­ Don’t restrict the use of the term partition to reflect a vertical
    slice of the architecture. This is too limiting. Add a qualifier such as

    Modeling time - Delete the term “software”.

    Module - Delete the term “software”.

    Object diagram ­ should this be replaced with Instance diagram.

    Part ­ Add the following after classifier instance “or roles of a
    classifier”. Reference the definition for “Role”, which provides

    Partition - Don’t restrict the use of the term partition too much. Partition
    can reflect the grouping of any set of model elements based on a set of

    Run time ­ Insert after “computer program” “or a system”.

    Specification ­ Consider changing the definition to “a set of requirements
    for a system or other classifier.

    Subsystem ­ Replace “See package” with “See system”

    System ­ Replace system definition with the following: A component which
    contains parts, and has observable properties and behaviors.

    Trace ­ Add the following ­ A dependency between a derived requirement and a
    source requirement

    Use case diagram ­ Change from “A diagram that shows the relationships among
    actors and use cases within a system” to “A diagram that shows the
    relationships among actors, the subject (system), and use cases

  • Reported: UML 1.5 — Thu, 6 Nov 2003 05:00 GMT
  • Disposition: Resolved — UML 1.4.2
  • Disposition Summary:

    No Data Available

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