Issue 6082: Suspension Region (uml2-rtf)
Source: SINTEF (Dr. Oystein Haugen, oystein.haugen(at)sintef.no)
Nature: Enhancement
Severity: Minor
Summary: “Supspension region” is a concept from MSC-2000 that occurred in earlier drafts of UML 2.0. It was removed since the metamodel had not been properly updated. A suspension region is an area of a lifeline where no events should occur since the lifeline is waiting for reply from an operation call. 

This has been flagged as a potential FTF issue before. 


Resolution: Discussion:
This is a concept that highlights a syntactic requirement. Often users think that suspension is always the case between call and reply, but since lifelines may be decomposed into independent sub-parts, this is not necessarily the case. That is why it is useful to clarify a synchronization situation. Still it is a new concept, and cannot be considered critical for the use of Interactions. Let us bring this up again at a larger revision.
Disposition:	ClosedOutOfScope

Revised Text: 
Actions taken:
August 29, 2003: received issue
April 26, 2010: closed issue
April 26, 2010: closed issue
Discussion: 
This is a concept that highlights a syntactic requirement. Often users think that
suspension is always the case between call and reply, but since lifelines may be
decomposed into independent sub-parts, this is not necessarily the case. That is why it is
needed to clarify a synchronization situation. Still it is a new concept, and cannot be
considered critical for the use of Interactions.
End of Annotations:=====
MG Issue No: 6082
Title:	Suspension Region
Source:	
Ericsson (Dr. Oystein Haugen, oystein.haugen@ericsson.no oystein.haugen@ericsson.com Oystein.Haugen@eto.ericsson.se)
Summary:
.Supspension region. is a concept from MSC-2000 that occurred in earlier drafts of UML 2.0. It was removed since the metamodel had not been properly updated. A suspension region is an area of a lifeline where no events should occur since the lifeline is waiting for reply from an operation call. 
This has been flagged as a potential FTF issue before.
Discussion:
This is a new feature that is not within the scope of an FTF (whose task it is to fix inconsistencies and add clarifications.) 
Disposition:	Defer