UMLR-480 |
Can passive classes have ClassifierBehaviors? |
UML 2.4.1
|
|
|
open |
|
UMLR-542 |
Figure 12-15 (MOF Model Equivalent
) p.284 - MOF Model Equivalent navigation and ownership incorrect |
UML 2.4.1
|
|
|
open |
|
UMLR-582 |
What is a DurationInterval |
UML 2.4.1
|
|
|
open |
|
UMLR-584 |
What is a DurationInterval |
UML 2.4.1
|
|
|
open |
|
UMLR-528 |
Location: Figure 15-43 ActivityFinalNode example - Balancing Decision / Merge |
UML 2.4.1
|
|
|
open |
|
UMLR-530 |
Location: Page 413, 15.3.2 Abstract Syntax Control Nodes Figure 15-26 |
UML 2.4.1
|
|
|
open |
|
UMLR-354 |
State machine semantics for transition between regions of an orthogonal state |
UML 2.4.1
|
|
|
open |
|
UMLR-488 |
Interaction parameters. |
UML 2.4.1
|
|
|
open |
|
UMLR-489 |
How should context be represented? |
UML 2.4.1
|
|
|
open |
|
UML25-345 |
Location: 9.6.4 Notation p 128: Confusing indentation |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UMLR-617 |
Location: 18.1.5 Examples Figure 18-2. 689 - Explain about Navigation |
UML 2.4.1
|
|
|
open |
|
UML241-47 |
No unambiguous way in UML 2.4 to serialize StructuredActivityNode |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
UML25-682 |
InformationFlow cannot have an Activity as source or target |
UML 2.4.1
|
UML 2.5b1
|
Resolved |
closed |
|
UML25-681 |
Location p 162 ParameterSet associationends: Exceptions and parametersets |
UML 2.4.1
|
UML 2.5b1
|
Resolved |
closed |
|
UML25-671 |
an instance spec should be a legitimate value of a property typed by a classifier |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-668 |
A comment is a specialization of Element |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-667 |
Surplus classifier field serialized in Superstructure.xmi |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-670 |
Attribute is represented by Property |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-669 |
Operation "isConsistentWith" is not overridden for any RedefinableElement |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-664 |
Question About Arrows In Communication Diagramms |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-663 |
Constraint [1] uses undefined attribute "ownedAttribute |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-662 |
Inconsistency: CentralBufferNode (ch .12.3.16) and fig. 12.15 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-665 |
missing words in section 14.1 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-666 |
DurationObservation#event should be ordered |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-661 |
LifeLine instead of Lifeline |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-630 |
UML 2.3: Transitions outgoing junction vertexes should be allowed to have triggers |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-660 |
Behavior should be derived from Classifier, not Class |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-659 |
Package merge on Class metatype causes semantic issues - particularly with state machine context |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-648 |
Error in UML diagrams? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-647 |
Suggestions for editorial changes |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-654 |
how to instantiate associations between stereotypes |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-653 |
Core package caption wrong |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-658 |
Add an example for the lifeline head shape |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-657 |
color of the notation is specified |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-656 |
The property packagedElement: PackageableElement [*] is not a derived property and should not be prefixed with "/" |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-655 |
Opposite ends of derived unions should be derived unions |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-651 |
Use of term "locus of control" |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-650 |
V2.4.1 from 11-08-05 on page 14 in Figure 7.3 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-646 |
default is wrong |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-645 |
V2.4.1 from 11-08-05 on page 14 in Figure 7.3 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-649 |
Reference in index to item that does not exist in contents |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-652 |
incorrect upper value of coveredBy of Lifeline |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-632 |
ChangeEvent association mismatch |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-631 |
EnumerationLiterals in the XMI |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-635 |
"A_realization_abstraction_component" is useless |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-634 |
Subpart I and II are missing in Bookmarks |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-644 |
default value of ClassifierTemplateParameter#allowSubstitutable is "..." |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-643 |
Figure 15.2 does not include TransitionKind |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-640 |
role "interval" appears "interva" |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-639 |
OpaqueBehavior#body attributes "nonunique" truncated as "nonuni..." |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-642 |
misspelling: io-oargument |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-641 |
OpaqueBehavior#body attributes "nonunique" truncated as "nonuni..." |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-636 |
RedefinableElement (from Kernel) is preferable |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-633 |
UML Superstructure Specification |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-637 |
poor figure resolution and a misspelling: fal...( false ) |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-638 |
{ordered} is rather far from +bodyOutput |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-491 |
Conflict in use of unlimited natural |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-414 |
Location: 18.1.3 Semantics Use Cases and Actors P. 686 - Or Pre-conditions appears limiting |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-417 |
Location: 18.1.3 Semantics Use Cases and Actors P. 686 - Clarification meaning of not part of the subject |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-416 |
Location: 18.1.3 Semantics Use Cases and Actors P. 686 - Point to Figures to help explain subject vs owner |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-415 |
Location: 18.1.3 Semantics Use Cases and Actors P. 686 - Initiating ? Interacting with |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-420 |
18.1.3 Semantics Use Case and Actors Extends P. 687 - Omitted conditions are true |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-419 |
18.1.3 Semantics Use Case and Actors Extends P. 687 - Easy |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-418 |
Location: 18.1.3 Semantics Use Cases and Actors P. 686 - Additional behavior vs Additional use case |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-422 |
Location: 18.1.4 Notation P. 688 - Point to diagram |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-421 |
18.1.3 Semantics Use Case and Actors Extends P. 687 - Clarify role of owner |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-512 |
Behavior is not allowed to be source or target of an InformationFlow |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-432 |
Location: 18.1.5 Examples Figure 18-9. 690 - Description does not match figure 18-9 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-431 |
Location: 18.1.5 Examples Figure 18-2. 689 - Explain about multiplicity |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-424 |
Location: 18.1.4 Notation P. 688 - Point to diagram (03) |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-423 |
Location: 18.1.4 Notation P. 688 - Point to diagram (02) |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-429 |
Location: 18.1.4 Notation P. 688 - Point to diagram (08) |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-428 |
Location: 18.1.4 Notation P. 688 - Point to diagram (07) |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-427 |
Location: 18.1.4 Notation P. 688 - Point to diagram (06) |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-426 |
Location: 18.1.4 Notation P. 688 - Point to diagram (05) |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-430 |
Location: 18.1.5 Examples Figure 18-2. 689 - Explain about «Subsystem» |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-436 |
Location: 18.2 Classifier Descriptions Use Case Constraints. 697 - At least one actor |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-435 |
Location: 18.2 Classifier Descriptions Use Case Constraints. 697 - At least one actor |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-425 |
Location: 18.1.4 Notation P. 688 - Point to diagram (04) |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-433 |
Location: 18.1.5 Examples Figure 18-10. 691 - Duplicate Diagram |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-434 |
Location: 18.2 Classifier Descriptions Include Constraints. 696 - Includes must be a DAG |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-470 |
Section 11: feature inheritance should be orthogonal to the topology of well-formed connections in a structured classifi |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-469 |
ConnectableElement-end" has @isOrdered='true' |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-468 |
UML2.5: clarification about the semantics of redefinition |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-467 |
Lifeline has no type. |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-466 |
Location: Table B.1 UML Keywords p 778 - Use of # in Semantics col |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-451 |
Location: B.4.4 State Shapes P. 752 - State List Limitations |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-450 |
Location: B.2.4 P. 739 - confusing model and diagram |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-441 |
Location: Table 21-1 PrimitiveType semantics Real P. 726 - IEEE 754 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-440 |
Location: 21.1 Summary P. 726 - Missing header |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-438 |
Location: Figure 18-3 Example Extend p.689 - Circle on comment "anchor" not standard |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-437 |
Location: 18.1.1 Summary p 685 - emergent behavior |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-445 |
Location: Table 21-1 String P. 726 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-444 |
Location: Table 21-1 P. 726 - Title of table not great |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-443 |
Location: 21.2 Semantics P. 726 - Subsection title |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-442 |
Location: Table 21-1 PrimitiveType semantics Real P. 726 - Real Number representation |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-448 |
Location: Figure 21-3 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-447 |
Location: Table 21-1 P. 726 - Row ordering |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-446 |
Location: Table 21-1 Unlimited Natural P. 726 - Infinity |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-439 |
Location: Figure 20-4 and accompanying text P. 719 - InformationItem can represent multiple types? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-449 |
Location: B.2.3 P. 738 - confusing model and diagram |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-456 |
Location: Annex C Keywords p 777 - Capitalization of «trace» |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-455 |
Location: Annex C Keywords P. 777 - Previously unmentioned constraints given in Keywords Annex |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-453 |
Location: B.6 UMLILabel Constraints. P 766 - Use Case Oval. |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-452 |
Location: B.6 Classifier Description UMLInheritedStateBorderKind [Enumeration] Literals p 763 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-458 |
Location: Table B.1 UML Keywords p 778 - Keywords should be in index |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-457 |
Location: Annex C Keywords p 777 - Capitalization of «create» |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-464 |
Location: Index p. 796 among others - Index items with only one page |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-463 |
Location: Index p 795 - Index of "is" |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-460 |
Location: Index |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-459 |
Location: Annex C Keywords P. 780 - Bizarre definition of statemachine |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-454 |
Location B.6 UMLStateShape statelist p 770 - StateList Limitations |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-462 |
Location: Index p 793 - emergent behavior |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-465 |
Location: Index Mis. - Missing terms in the Index |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-461 |
Type: Structural - Location Index p 790, 794, |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-394 |
Location: 15.5.1 - typo |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-393 |
Location: Figure 15.57 page 426 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-399 |
Location: 17.2.3 Semantics Interaction Fragments p 607 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-398 |
17.1.5 Interaction Diagram Variants p 607 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-397 |
Location: p 484 - Exception store |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-396 |
Location: Figure 15-23 p.411 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-391 |
Location: Figure 15-23 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-390 |
Location: p. 357 StateMachine Redefinition |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-389 |
Location: p. 338 Transition execution sequence |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-388 |
Location: p. 338 Transition execution sequence |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-395 |
Location: Figure 15-63 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-387 |
Location: p. 337 Conflicting Transitions |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-392 |
Location: Page 413, 15.3.2 Abstract Syntax Control Nodes Figure 15-26 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-386 |
Location: p. 337 Conflicting Transitions |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-317 |
What is Intentionally Not specified? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-316 |
What is aggregation |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-311 |
inout parameters and effects |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-310 |
Effect Intent |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-308 |
Return Parameter order |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-307 |
Default value of readonly should be referenced |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-313 |
Parameter Sets |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-312 |
isException and direction and effect |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-320 |
Location: 9.5.3 p 122 In the common case |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-319 |
Location: 9.5.3 p 121 Why not all empty |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-314 |
Use isReadOnly default |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-315 |
Redefinition does not allow for overloading |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-318 |
What is Intentionally Not specified? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-309 |
Return Parameter pronoun |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-223 |
Two categories is not enough |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-222 |
UML Semantics |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-224 |
Semantics Areas section not clear |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-413 |
Location: 18.1.3 Semantics Use Cases and Actors P. 685 - Variants are not defined |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-412 |
Location: 18.1.3 Semantics Use Cases and Actors P. 685 - Actors need not initiate |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-411 |
Location: 18.1.3 Semantics Use Cases and Actors P. 685 - Are actors mandatory? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-405 |
Location: Pg. 615, Figure 17.4.3: Semantics, Sub-clause: Messages |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-404 |
Pg. 613, Clause 17.3.4: Notation |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-403 |
Location: Pg. 612, Clause 17.2.5 - Minor rewording to Clause 17.2.5 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-402 |
Location: Pg. 612, Figure 17.5 - Modify Figure 17.5 to enhance readability |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-410 |
Location: 18.1.1 Summary P. 685 - A Subject may only refer to a single system |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-409 |
General value lifeline Row p 647 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-408 |
Location: Table 17.6 entire table p 646 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-401 |
Pg. 611, Clause 17.2.5: Examples - : Insert formal in reference to gates in the Examples clause (17.2.5) |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-400 |
Location: 17.2.4 Notation ExecutionSpecification p608 - : Specification of color |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-407 |
Location: LostMessage Row p 639 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-406 |
Pg. 617, Figure 17.4.3: Semantics, Sub-clause: Gates - Replace formal with actual in Clause 17.4.3 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-264 |
Default value for LiteralString |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-263 |
Optional String Multiplicity |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-256 |
Excessive null checks |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-255 |
Single and set of aren't really parallel |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-252 |
Missing a |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-251 |
inconsistent spacing on diagram |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-260 |
TypedElement description could be expanded |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-259 |
It seems to me that a relationship requires a minimum of two relatedElements |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-254 |
Use of the diamond symbol (?)needs to be explained |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-253 |
Instantiate Dependency |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-261 |
Generalization Relationship to itself? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-262 |
Negatively phrased sentence |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-258 |
Sentence difficult to read |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-257 |
allNamespace description doesn't match OCL |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-338 |
Location p 152 Generalization Attributes: IsSubstitutable |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-340 |
Location p 153 complete_and_disjoint: Abstract Implication |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-339 |
Location p 153 complete_and_disjoint: Complete vs covering? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-334 |
Location: p 145 CallConcurrencyKind [Enumeration - blocks -- > locks |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-333 |
Location: p 145 (3X) Detail: simultaneously -- > concurrently |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-337 |
Location p 146 Classifier Description: isAbstract |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-336 |
Location p 145 Classifier Description: objects -> instances |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-343 |
Location p 162 two_parameter_sets: Why |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-342 |
Location p 157 isConsistentWith: missing rules |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-341 |
Location p 154 Association Ends: Instances of multiple classifiers |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-344 |
Location p 162 ParameterSet constraints input: Exceptions and parameterset |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-335 |
Location p 145 Classifier Description - objects -> instances |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-249 |
While-->And |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-248 |
Unclear description of multiplicities |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-243 |
Imports |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-242 |
ElementImport cannot be further imported |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-247 |
Confusing description of types |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-238 |
Note refers to an undiscussed concept |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-240 |
Packageable Elements and Imports |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-239 |
Missing word |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-246 |
Missing TypedElement - use of the term constrained seems to be circular |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-245 |
Missing TypedElement |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-250 |
Missing OCL |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-241 |
Packageable Elements and Imports (02) |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-244 |
Incorrect text describing diagram elements |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-358 |
Location 13.1 Summary p 305 - Use of the word emergent |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-357 |
Operations p 245 (2X) typo |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-355 |
Location Figure 11-23 s p.217 - Instance/roll names |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-354 |
Location Figure 11-22 s p.216 - Title doesnt match contents |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-351 |
Location: Constraints p 193 - Missing constraint? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-350 |
Location 10.4.4 Notations p.188 - Reception compartment |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-349 |
Location 10.3.3 Signals p.186 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-348 |
10.2.4 Notation p 184. - Enumeration attributes and operations |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-346 |
Location: 10.2.3 Enumeration p. 184: New EnumerationLiterals |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-347 |
Location: 10.2.4 Notation p 184 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-353 |
Location Figure 11-21 s p.216 - Instance/roll names |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-356 |
Location Figure 11-23 s p.217 - Instance/roll names (02) |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-352 |
Location: Figure 11-3 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-281 |
Wrong Reference |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-280 |
missing headings |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-290 |
Min/Max |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-289 |
Two anonymous invariants |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-292 |
8.6 p 100 isCompatibleWith() ..save space |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-291 |
Save Space |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-288 |
result() error |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-287 |
French |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-284 |
Invariant name |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-283 |
Improve readability of constraint names |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-295 |
Association Descriptions not that useful |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-294 |
IsNull not Boolean |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-282 |
Duration Definition |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-286 |
Set--> List |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-285 |
Why is value optional |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-293 |
Turing Machine lurking paradox? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-323 |
Location: 9.6.3 Operations p 127 Undefined ? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-322 |
Location: 9.5.3 p 121 Cant qualifiers be queries? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-330 |
Location: 9.8.4 Notation p 141 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-329 |
Location: 9.8.3 Semantics p 139 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-326 |
Location: 9.6.4 Notation p 128 Is return a reserved parameter name? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-325 |
Location: 9.6.4 Notation p 127 Simplify description of syntax |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-321 |
Location: 9.5.3 p 122 Qualifiers must be enumerated type |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-324 |
Location: 9.6.3 Operations p 127 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-328 |
Location: 9.7.5 Examples p 135 Political Correctness |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-327 |
Location: 9.7.5 Examples p 134 Generalization Sets |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-331 |
Location: 9.8.4 Notation p 141 representing the roles vs representing the instances |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-332 |
Location: 9.9 Classifier Descriptions Association Ends p 144 Behavioral --> Behavior |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-237 |
Clarification of imports |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-236 |
Namespace Abstract Syntax incorrect |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-230 |
Add reference to association notation section |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-229 |
How does dot notation work |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-227 |
Extraneous Note |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-226 |
Sentence does not make sense |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-233 |
Owning Comments |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-232 |
Root Abstract Syntax missing adornments/metamodel incorrect |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-234 |
Owning Rules |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-231 |
Owning Comments |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-225 |
Figure 6.1 does not relate to rest of Specification |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-235 |
Can Comments own comments? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-228 |
What type of slash? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-367 |
Location: Page 330, 331, 333, 14.2.3, Page 347, 14.2.4, Page 375, 14.5 PseudostateKind |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-366 |
Location: Page 329 States - Stable |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-362 |
Location: Page 315 Association ends - Explain about having no nestedClassifier |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-361 |
Location: Page 313, 13.2.4 Notation relative |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-369 |
Location: Page 341, 14.2.4 - Example for graphical expression of behavior in states |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-365 |
Location: Page 328 Regions 14.2.3 - Text about regions without initial state |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-371 |
Location: Page 346, State List Notations |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-370 |
Location: Page 341, State - More examples needed |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-368 |
Location: Page 338, Transition selection algorithm - Maximal Set |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-364 |
Location: 14.2.1 Summary - Behavior StateMachines for UseCases |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-363 |
Location: 14.1 Summary p 326 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-360 |
Location Behavior Parameters p 307 - Streaming and Multiplicity |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-359 |
Location Behavior Parameters p 307 - Optional with default value |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-304 |
Alterative Scopes? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-303 |
Multiplicity of 0..0 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-301 |
Location p.112 (9.3 Classifier Templates) |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-300 |
Incompatible with SysML |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-297 |
the parent of a Classifier is not its owner. |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-302 |
Location: p.116 (9.4.3 Semantics) |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-298 |
What is inherited or not |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-299 |
Inherited members |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-306 |
Redefinable Static attributes |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-305 |
Examples of alternative scopes? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-296 |
Objects? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-378 |
Location: p. 329 State Configurations |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-377 |
Location: p. 328 Regions - Resolve intentional ambiguity |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-373 |
Location: Transition , bottom of page 352 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-372 |
Location: Page 347, 14.2.4 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-376 |
Location: p 378 State Description - What is hidden? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-375 |
Location: p 373 outgoing_from_initial - Limitations on guards |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-374 |
Page 353, 14.2.4 - StateMachine symbols on graphical representations of Transitions |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-382 |
Location: p. 333 FinalState |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-381 |
Location: p. 331 Exiting a State - Clarification of Exiting a State |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-385 |
Location: p. 337 2nd ¶ |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-384 |
Location: p. 336 Compound transitions |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-383 |
Location: p. 333 Transitions - How do multiple triggers work? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-379 |
Location: p. 330 Deferred Events - Value of Deferred Events |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-380 |
Location: p. 331 Explicit Entry - Clarification of Explicit Entry |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-268 |
Unlimited Natural |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-267 |
String concrete syntax is missing |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-270 |
BNF rules allow for a real 0 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-269 |
Notation: Real |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-266 |
LiteralNull semantics |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-265 |
Default value for LiteralReal |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-279 |
Always non-negative |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-278 |
Duration |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-274 |
set - > list |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-273 |
Plural headers when class name is singular |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-276 |
body text strings |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-275 |
sentence unclear |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-271 |
Past vs Present |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-277 |
String expression notation missing |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-272 |
{ordered} at wrong end |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-219 |
Incarnation ? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-218 |
Show how UML is a MOF metamodel |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-214 |
Conformance definitions ? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-213 |
Impact of merging profiles isn't small |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-217 |
Keyword Usage |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-216 |
ISO version of UML 2? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-220 |
Within the System |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-212 |
Capture Submitters, Supporters, etc |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-221 |
Modeling Individuals |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-215 |
DI Conformance implies Model Interchange Conformance |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-191 |
Clarification on the semantics of Multiplicities |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-190 |
Clarification on the semantics of UML |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-189 |
Conformance point |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-193 |
Clarification on the semantics of Properties |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-192 |
Clarification on the semantics of Parameters |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-197 |
Clarification on the semantics of Manifestation |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-196 |
Clarification on the aim of Collaborations |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-195 |
Clarification on the semantics of ports in Encapsulated Classifiers |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-194 |
Clarification on the semantics of Connectors within Structured Classifiers |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-198 |
Declassifying of Annex D |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-211 |
Missing Table of Figures, Table of Tables - Location: TOC p 10 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-210 |
Minor vs Major revision |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-209 |
Section 11.5. - Clause 11: Structured Classifiers |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML241-12 |
UML type Real specification |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
UML241-11 |
Interface element - associations multiplicity not defined |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
UML241-9 |
Property::isID |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
UML241-6 |
Wrong package name on several Figures |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
UML241-10 |
Missing Namespace in Dependencies package definition? |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
UML241-3 |
typo on page 46 |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
UML241-22 |
Irritating occurrence of subsystem stereotype in use case example diagrams |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
UML241-21 |
UML 2.4: NamedElement.ownedRule could be ordered |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
UML241-19 |
property.opposite |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
UML241-18 |
ProfileApplication::appliedProfile as "importedProfile" instead of "appliedProfile" |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
UML241-25 |
ChangeEvent::changeExpression should be of type ValueSpecification |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
UML241-24 |
Validity duration of implicitly assigned parameters in SignalEvent/CallEvent |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
UML241-17 |
XMI in small caps |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
UML241-16 |
Core Package versus Construct Package |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
UML241-20 |
UML Appendix A : Figure A.3 Two Diagrams of Packages |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
UML241-15 |
XML Metadata Interchange (XMI) - p9 |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
UML241-14 |
XML Metadata Interchange (XMI) |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
UML241-23 |
Implicit parameter assignment may cause name clashes |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
UML241-13 |
Number of Compliance Levels |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
UML241-2 |
Presentation options of statemachine transitions: Figure 15.45 is ambiguous or wrong |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
UML241-1 |
Can a Generalization really be in multiple GeneralizationSets? |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
UML241-5 |
No Rules for Element Names |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
UML241-4 |
Figure 15.32 |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
UML241-8 |
Figure 15.32 |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
UML241-7 |
Typo: "joint" should say "join" |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
UMLR-504 |
Location: 18.2 Classifier Descriptions Extend Constraints. 695 - Constraint is overly restrictive |
UML 2.4.1
|
|
|
open |
|
UMLR-502 |
Location: 18.1.4 Notation P. 688 - Can Use Cases have attributes and operations? |
UML 2.4.1
|
|
|
open |
|
UMLR-496 |
Location: Figure A.5 P. 734 - Use Cases are not behavior diagrams |
UML 2.4.1
|
|
|
open |
|
UMLR-497 |
Location: Appendix A, list of frame names, p 734 - List of Namespaces suitable for diagram headers is overly restrictive |
UML 2.4.1
|
|
|
open |
|
UMLR-500 |
Location: 18.1.1 Summary p 685 - Bases of specialized stereotypes |
UML 2.4.1
|
|
|
open |
|
UMLR-501 |
Location: 19.5 Classifier Descriptions Deployment Specification Attributes P. 711 - Why a multiplicity of [0..1] |
UML 2.4.1
|
|
|
open |
|
UMLR-498 |
Location: 22.3 Standard Stereotypes «Metamodel» p. 731 - «Subsystem» should be allowed for more classifiers |
UML 2.4.1
|
|
|
open |
|
UMLR-499 |
Location: 19.5 Node Association Ends Node P. 714 - Shared ownership of nodes |
UML 2.4.1
|
|
|
open |
|
UMLR-506 |
Location: 18.2 Classifier Descriptions Extend Constraints. 695 - Extensions must be a DAG |
UML 2.4.1
|
|
|
open |
|
UMLR-495 |
Location: Figure B.3. 737 - A diagram is a PackageableElement |
UML 2.4.1
|
|
|
open |
|
UMLR-568 |
Reword isComputable |
UML 2.4.1
|
|
|
open |
|
UMLR-569 |
Location: 8.6 p 98 TimeObservation ...simplify |
UML 2.4.1
|
|
|
open |
|
UMLR-576 |
Too many alls |
UML 2.4.1
|
|
|
open |
|
UMLR-575 |
Intended to Produce |
UML 2.4.1
|
|
|
open |
|
UMLR-577 |
Bad Description, observation has no value |
UML 2.4.1
|
|
|
open |
|
UMLR-580 |
Like to overridden definition |
UML 2.4.1
|
|
|
open |
|
UMLR-573 |
Why cant the operand be a stringExpression |
UML 2.4.1
|
|
|
open |
|
UMLR-578 |
Range Confusion |
UML 2.4.1
|
|
|
open |
|
UMLR-570 |
Simplify (Location: 8.6 p 97 TimeExpression) |
UML 2.4.1
|
|
|
open |
|
UMLR-574 |
Bad Description |
UML 2.4.1
|
|
|
open |
|
UMLR-571 |
Simplify |
UML 2.4.1
|
|
|
open |
|
UMLR-572 |
What incompatible about sub-expressions and operands |
UML 2.4.1
|
|
|
open |
|
UMLR-432 |
Add condition : Constraint[0..1] to the include relationship |
UML 2.4.1
|
|
|
open |
|
UMLR-595 |
Definition of invariant condition |
UML 2.4.1
|
|
|
open |
|
UMLR-597 |
Section Unbalanced |
UML 2.4.1
|
|
|
open |
|
UMLR-592 |
Need table correlating Literals with symbols (+,-,#,~) |
UML 2.4.1
|
|
|
open |
|
UMLR-593 |
Inconsistent use of (s) |
UML 2.4.1
|
|
|
open |
|
UMLR-601 |
Section 11.7 has no content or notation for template Collaborations Clause - 11: Structured Classifiers |
UML 2.4.1
|
|
|
open |
|
UMLR-603 |
Section 11.3.4 isService clarification - Clause 11: Structured Classifiers |
UML 2.4.1
|
|
|
open |
|
UMLR-596 |
Descendants rather than specializations |
UML 2.4.1
|
|
|
open |
|
UMLR-602 |
Section 11.2.4 clarification - Clause 11: Structured Classifiers |
UML 2.4.1
|
|
|
open |
|
UMLR-600 |
List attributes whose ordered property has change in UML 2.5 |
UML 2.4.1
|
|
|
open |
|
UMLR-598 |
Bound Element Semantics overly specific |
UML 2.4.1
|
|
|
open |
|
UMLR-599 |
UML 2.5 FTF issues for Clause 18: UseCases |
UML 2.4.1
|
|
|
open |
|
UMLR-594 |
Template Notation example |
UML 2.4.1
|
|
|
open |
|
UMLR-615 |
Clarification on the semantics of CommunicationPath |
UML 2.4.1
|
|
|
open |
|
UMLR-614 |
isIntegral() |
UML 2.4.1
|
|
|
open |
|
UMLR-613 |
Capitalization of dependency |
UML 2.4.1
|
|
|
open |
|
UMLR-476 |
Node::nestedNode should subset Class::nestedClassifier, not Namespace::ownedMember. |
UML 2.4.1
|
|
|
open |
|
UMLR-477 |
Meaning of State in ProtocolStateMachines |
UML 2.4.1
|
|
|
open |
|
UMLR-479 |
Should completion event be an explicit event type? |
UML 2.4.1
|
|
|
open |
|
UMLR-481 |
Not clear if else keyword is defined for State Machines |
UML 2.4.1
|
|
|
open |
|
UMLR-482 |
State of the substates of the history state |
UML 2.4.1
|
|
|
open |
|
UMLR-473 |
It is a pity that UML does not provide the ability for Messages to correspond directly to property accesses and updates |
UML 2.4.1
|
|
|
open |
|
UMLR-474 |
Meaning of absent multiplicity notation |
UML 2.4.1
|
|
|
open |
|
UMLR-478 |
Figure 14.39 missing superclass |
UML 2.4.1
|
|
|
open |
|
UMLR-517 |
Not clear when to use ExecutionOccurrenceSpecification with ExecutionSpecification |
UML 2.4.1
|
|
|
open |
|
UMLR-518 |
Location: Pg. 617, Figure 17.4.4: Notation, Sub-clause: Message |
UML 2.4.1
|
|
|
open |
|
UMLR-508 |
18.1.3 Semantics Use Case and Actors Extends P. 687 - No Alternative Path |
UML 2.4.1
|
|
|
open |
|
UMLR-509 |
18.1.3 Semantics Use Case and Actors Extends P. 687 - First ExtensionPoint |
UML 2.4.1
|
|
|
open |
|
UMLR-513 |
Location: 18.1.3 Semantics Use Cases and Actors P. 686 - What classifiers can be a subject? |
UML 2.4.1
|
|
|
open |
|
UMLR-516 |
Location: 18. Global - No discussion of use case instances |
UML 2.4.1
|
|
|
open |
|
UMLR-511 |
Location: 18.1.3 Semantics Use Cases and Actors P. 686 - Multiplicity at Use Case end |
UML 2.4.1
|
|
|
open |
|
UMLR-510 |
18.1.3 Semantics Use Case and Actors Extends P. 687 - Show name of extension |
UML 2.4.1
|
|
|
open |
|
UMLR-514 |
Location:Page #640, 17.8.2 Example Sequence Diagram |
UML 2.4.1
|
|
|
open |
|
UMLR-512 |
Location: 18.1.3 Semantics Use Cases and Actors P. 686 - Multiple subjects require the same actors |
UML 2.4.1
|
|
|
open |
|
UMLR-507 |
18.1.3 Semantics Use Case and Actors Extends P. 687 - Single Location |
UML 2.4.1
|
|
|
open |
|
UMLR-515 |
Location: weak sequencing p. 622 |
UML 2.4.1
|
|
|
open |
|
UMLR-585 |
What is a DurationConstaint |
UML 2.4.1
|
|
|
open |
|
UMLR-586 |
Time constant |
UML 2.4.1
|
|
|
open |
|
UMLR-579 |
More detail on Express |
UML 2.4.1
|
|
|
open |
|
UMLR-590 |
Expression examples unclear |
UML 2.4.1
|
|
|
open |
|
UMLR-588 |
OCL not indexed |
UML 2.4.1
|
|
|
open |
|
UMLR-591 |
Semantics Clarification |
UML 2.4.1
|
|
|
open |
|
UMLR-587 |
Event |
UML 2.4.1
|
|
|
open |
|
UMLR-581 |
incompatible multiplicities |
UML 2.4.1
|
|
|
open |
|
UMLR-583 |
one -- > first |
UML 2.4.1
|
|
|
open |
|
UMLR-589 |
Orphan Title |
UML 2.4.1
|
|
|
open |
|
UMLR-521 |
Location: Pg. 613, Figure 17.6 - : Incorrect multiplicities in the metamodel in Figure 17.6 |
UML 2.4.1
|
|
|
open |
|
UMLR-522 |
Location: p 611 |
UML 2.4.1
|
|
|
open |
|
UMLR-524 |
Not clear when to use ExecutionOccurrenceSpecification with ExecutionSpecification |
UML 2.4.1
|
|
|
open |
|
UMLR-529 |
Location p413 Final Node - Rollback behavior |
UML 2.4.1
|
|
|
open |
|
UMLR-532 |
Location p413 Final Node - Atomic behavior |
UML 2.4.1
|
|
|
open |
|
UMLR-519 |
Location: 17.3.4 Notation Lifeline p 613 - Specification of color |
UML 2.4.1
|
|
|
open |
|
UMLR-520 |
Location: Pg. 613, Figure 17.6 - Incorrect multiplicities in the metamodel in Figure 17.6 |
UML 2.4.1
|
|
|
open |
|
UMLR-525 |
Interactions p 607 |
UML 2.4.1
|
|
|
open |
|
UMLR-523 |
Location: 16.2.3 Semantics / Opaque Actions |
UML 2.4.1
|
|
|
open |
|
UMLR-527 |
Location: Figure 15.67 page 436 |
UML 2.4.1
|
|
|
open |
|
UMLR-526 |
Location: p 504 - Marshall Actions |
UML 2.4.1
|
|
|
open |
|
UMLR-608 |
Issue for UML 2.5 FTF against Clause 9: Classifiers |
UML 2.4.1
|
|
|
open |
|
UMLR-557 |
Location: Page 265, 12.2.3 Semantics - Unchanged URIs |
UML 2.4.1
|
|
|
open |
|
UMLR-555 |
Location: 12.2.3 Semantics Package p 265 - Reference to unknown section heading |
UML 2.4.1
|
|
|
open |
|
UMLR-566 |
Location: 9.6.4 Notation p 127 Missing Infix operation syntax / discussion |
UML 2.4.1
|
|
|
open |
|
UMLR-567 |
ParameterSet Notation |
UML 2.4.1
|
|
|
open |
|
UMLR-561 |
Location: constraints class_behavior p.190 |
UML 2.4.1
|
|
|
open |
|
UMLR-562 |
Location 10.3.3 Receptions p.186 - exceptions for receptions? |
UML 2.4.1
|
|
|
open |
|
UMLR-563 |
p 118: isException and other outputs |
UML 2.4.1
|
|
|
open |
|
UMLR-560 |
Location: Constraints p 193 - All feturs must be public? |
UML 2.4.1
|
|
|
open |
|
UMLR-564 |
Location p 162 ParameterSet associationends: Exceptions and parametersets |
UML 2.4.1
|
|
|
open |
|
UMLR-558 |
Location: 12.1 Packages Summary p 264 |
UML 2.4.1
|
|
|
open |
|
UMLR-559 |
Location: Figure 11-5 (ii) p 204 |
UML 2.4.1
|
|
|
open |
|
UMLR-565 |
Query of alternative scopes? |
UML 2.4.1
|
|
|
open |
|
UMLR-486 |
Problems with XMI IDs in the UML 2.5 UML.xmi file |
UML 2.4.1
|
|
|
open |
|
UMLR-487 |
17 Semantics of interactions |
UML 2.4.1
|
|
|
open |
|
UMLR-490 |
UML Interactions do not provide the ability for Messages to correspond directly to property accesses and updates |
UML 2.4.1
|
|
|
open |
|
UMLR-493 |
Location: B.6 UML ProfileDiagrams . 768 - Profile Diagram Elements |
UML 2.4.1
|
|
|
open |
|
UMLR-492 |
Location: B.6 UMLClass Diagram P. 757 - Class namespace diagrams? |
UML 2.4.1
|
|
|
open |
|
UMLR-483 |
Overriding deferred events |
UML 2.4.1
|
|
|
open |
|
UMLR-484 |
Stable state not needed |
UML 2.4.1
|
|
|
open |
|
UMLR-491 |
Location: Annex C Keywords P. 778 - Inconsistent metaclass keywords |
UML 2.4.1
|
|
|
open |
|
UMLR-485 |
Default entry if default history transition missing |
UML 2.4.1
|
|
|
open |
|
UMLR-494 |
Location: B.2.2 P. 738 - What ISO document |
UML 2.4.1
|
|
|
open |
|
UMLR-549 |
Location: Page 270/271, 12.2.3 Semantics - Model description confusing |
UML 2.4.1
|
|
|
open |
|
UMLR-550 |
Location: Page 269, 12.2.3 Semantics - Association merge aggregation constraint is property rule |
UML 2.4.1
|
|
|
open |
|
UMLR-545 |
Location: Page 286, 12.3.3 Semantics - Incorrect if statement |
UML 2.4.1
|
|
|
open |
|
UMLR-544 |
Location: Page 285, 12.3.3 Semantics - Old behavior unnecessarily preserved |
UML 2.4.1
|
|
|
open |
|
UMLR-552 |
Page 269, 12.2.3 Semantics - Property merge transformation conflicts with constrain |
UML 2.4.1
|
|
|
open |
|
UMLR-553 |
Location: Page 267, 12.2.3 Semantics - Type and TypedElement confusion |
UML 2.4.1
|
|
|
open |
|
UMLR-556 |
Location: Page 265, 12.2.3 Semantics PackageMerge - Long-winded package merge description |
UML 2.4.1
|
|
|
open |
|
UMLR-546 |
Location: Page 281, 12.3.3 Semantics - Duplicated text |
UML 2.4.1
|
|
|
open |
|
UMLR-554 |
Page 266, 12.2.3 Semantics - Un-matched resulting elements aren't always the same |
UML 2.4.1
|
|
|
open |
|
UMLR-548 |
Location: Page 280, 12.3.3 Semantics - Note should be main text |
UML 2.4.1
|
|
|
open |
|
UMLR-551 |
Location: Page 269, 12.2.3 Semantics - Property merge rule pointless |
UML 2.4.1
|
|
|
open |
|
UMLR-547 |
Location: Page 280, 12.3.3 Semantics - Poorly indented XMI |
UML 2.4.1
|
|
|
open |
|
UMLR-543 |
Location: Page 286, 12.3.3 Semantics - Nonsensical alternative to stereotype name |
UML 2.4.1
|
|
|
open |
|
UMLR-531 |
Location: p 410 |
UML 2.4.1
|
|
|
open |
|
UMLR-537 |
Location: Page 328, 14.2.3 - UseCase cannot be the context of a StateMachine |
UML 2.4.1
|
|
|
open |
|
UMLR-536 |
Location: Signal Receipt symbol |
UML 2.4.1
|
|
|
open |
|
UMLR-534 |
Location: Page 346, State List Notations - Why must state lists be effect free? |
UML 2.4.1
|
|
|
open |
|
UMLR-538 |
Location: 13.3.5 Examples p 314 |
UML 2.4.1
|
|
|
open |
|
UMLR-540 |
Location: Opaque and Function Behaviors p 308 |
UML 2.4.1
|
|
|
open |
|
UMLR-533 |
Location: p. 336 Compound transitions - Run-to-completion Paradigm |
UML 2.4.1
|
|
|
open |
|
UMLR-539 |
Location: Page 316 redefinedBehavior - Extends |
UML 2.4.1
|
|
|
open |
|
UMLR-535 |
Location: Page 331 deep history entry - Default deep history entry |
UML 2.4.1
|
|
|
open |
|
UMLR-541 |
Location: Figure 12-13 p.281 - Incorrect use of << for «. |
UML 2.4.1
|
|
|
open |
|
UMLR-610 |
How to model a transition to history pseudostates in two orthogonal regions? |
UML 2.4.1
|
|
|
open |
|
UMLR-612 |
Clarification on the semantics of inheritance between use cases |
UML 2.4.1
|
|
|
open |
|
UMLR-264 |
OccurrenceSpecification should have at least an optional notation |
UML 2.4
|
|
|
open |
|
UMLR-262 |
Message arguments for a Signal signature too restrictive |
UML 2.4
|
|
|
open |
|
UMLR-261 |
Relation of message arguments to signature parameters ambiguous |
UML 2.4
|
|
|
open |
|
UMLR-265 |
The included use case is always required for the including use case to execute correctly |
UML 2.4.1
|
|
|
open |
|
UMLR-266 |
Abstraction::mapping should be of type ValueSpecification or OpaqueExpression |
UML 2.4
|
|
|
open |
|
UMLR-263 |
Message arguments should not be contained in a message |
UML 2.4
|
|
|
open |
|
UMLR-294 |
Cannot set an activity as the source or target of an information flow |
UML 2.4.1
|
|
|
open |
|
UMLR-254 |
Use cases specifying the same subject cannot be associated: exception |
UML 2.4
|
|
|
open |
|
UMLR-252 |
Metaclass stereotype notion (02) |
UML 2.4
|
|
|
open |
|
UMLR-251 |
Metaclass stereotype notion |
UML 2.4
|
|
|
open |
|
UMLR-250 |
Profile URI Attribute - Mingled URI Definition and Use in XMI |
UML 2.4
|
|
|
open |
|
UMLR-249 |
Package URI Attribute Uses Obsolete RFC 2396 |
UML 2.4
|
|
|
open |
|
UMLR-255 |
A deferrable trigger may have a guard |
UML 2.4
|
|
|
open |
|
UMLR-311 |
Name of Package in Figure 7.3 should be "Core" rather than "Constructs" |
UML 2.4.1
|
|
|
open |
|
UMLR-270 |
Interaction.action should subset ownedMember in lieu of ownedElement |
UML 2.4.1
|
|
|
open |
|