Issue 8765: Section: 14.3.3 Page: 508+ (uml2-rtf) Source: SINTEF (Dr. Oystein Haugen, oystein.haugen(at)sintef.no) Nature: Enhancement Severity: Significant Summary: Sequence diagrams are often used for early specification of requirements. The distinction between potential and mandatory behavior is not adequately described in UML 2.0 Interactions. To improve this we suggest an additional operator "xalt" that describes alternative operands that are mandatory meaning that any refinement should keep at least some of the behavior of each operand. See paper at <<UML2003>>: Haugen, Stølen: STAIRS - Steps to Analyze Interactions with Refinement Semantics Resolution: Revised Text: Actions taken: May 4, 2005: received issue Discussion: Due to lack of time, the RTF/FTF agrees that the following are problems that need fixing, but decided to defer their resolution to a future RTF working on this specification. End of Annotations:===== m: webmaster@omg.org Date: 04 May 2005 09:04:04 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Oystein Haugen Company: University of Oslo mailFrom: oysteinh@ifi.uio.no Notification: Yes Specification: UML 2.0 Section: 14.3.3 FormalNumber: ptc 04-10-02 Version: 2.0 RevisionDate: 10/08/2004 Page: 508+ Nature: Enhancement Severity: Significant HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) Description Sequence diagrams are often used for early specification of requirements. The distinction between potential and mandatory behavior is not adequately described in UML 2.0 Interactions. To improve this we suggest an additional operator "xalt" that describes alternative operands that are mandatory meaning that any refinement should keep at least some of the behavior of each operand. See paper at <>: Haugen, Stølen: STAIRS - Steps to Analyze Interactions with Refinement Semantics