UTP 1.2 NO IDEA Avatar
  1. OMG Issue

UTP12 — UTP should constitute a new conceptual package structure

  • Key: UTP12-32
  • Legacy Issue Number: 17224
  • Status: closed  
  • Source: Fraunhofer FOKUS ( Marc-Florian Wendland)
  • Summary:

    Currently, UTP consists of four conceptual (not technical) packages: test architecture, test behavior, test data and timer concepts.

    The concepts which are described within those packages (which are represented as different subsections in the normative section of the specification) can be further separated.

    For example, timing (all concepts of timer concepts package) is mainly associated with test behavior. A timer can only be started if a behavior is executed. It might be more consistent to move the concepts from timer concepts into test behavoir as well, since it is clearly dedicated to test behavior.

    Another example are some concepts which clearly belong to the test management area like TestObjective and/or TestLog. Those test management concepts are part of UTP since its adoption by OMG, so it would just be consequent to establish a new package exclusively for test management concepts.

    A more consistent conceptual package structure could look like this:

    1. Test Architecture
    2. Test Behavior
    2.1 Test Case and Defaults
    2.2 Test Actions
    2.3 Test Timer
    3 Test Data
    3.1 Wildcards
    3.2 Test Data Structure
    4. Test Management

  • Reported: UTP 1.1 — Mon, 12 Mar 2012 04:00 GMT
  • Disposition: Resolved — UTP 1.2
  • Disposition Summary:

    The RTF agreed that having a modernized and polished specification document is highly beneficial. Therefore, a new outline and new introductory chapters have been written. Except from changes in the outline and introductory sections, this resolution does not change the semantics of a stereotype.
    NOTE: For the sake of clarity, this resolution is split into two parts.
    The first part incorporates only changes from section 1 (Scope) to 6 (Additional Information). These changes are marked with the issue tag (Issue 17224 (part one)) and are incorporated into the intermediate convenience document with change bars.
    The second part incorporates changes from newly created section 7 until the end of the document. These changes are marked with the issue tag (Issue 17224 (part two)) and are incorporated into the final convenience document with change bars. The second part is responsible for several new sections, section and figure renumbering. The issue marker in the change-bared convenience document provide information whether this section has been newly incorporated or changed. This ensures a direct traceability from the old document structure to the new one.

  • Updated: Fri, 6 Mar 2015 23:16 GMT