Issue 5023: 4.1.6- Excusive Service (uml-scheduling-ftf)
Source: Commissariat a l Energie Atomique-CEA (Dr. Sebastien Gerard, sebastien.gerard(at)cea.fr)
Nature: Uncategorized Issue
Severity: 
Summary: We propose to suppress this association for following reason: It has been demonstrated (REF. MCH 94: C. McHale, “Synchronization in concurrent, object oriented languages: expressive power, genericity and inheritance.”, PhD thesis, Department of Computer Science, Trinity College, Dublin, Ireland, October 1994) that specifying mutual exclusion constraint among services by listing explicitly conflicting services penalizes maintainability, evolutivity of the system. Namely, this point leads to the question of inheritance anomaly. Indeed, it does not allow to change the interface (i.e. set of service it provides to clients) without reanalyzing whole concurrency issues. herefore, specifying concurrency constraints of services by declaring the set of used resource and their using mode (modifying, querying, …) ensures that the specification of each services remains independent. And thus it will remove the drawbacks mentioned before.

Resolution: Closed, no change
Revised Text: 
Actions taken:
March 20, 2002: received issue
June 30, 2003: closed issue
Discussion: 
There is a difference between good design practices and ones that we need to support because people do them anyway; I will check this out, but my inclination is to reject since I am not convinced that we should be dictating how people do things (Bran)

End of Annotations:=====
This is issue # 5023

4.1.6- Excusive Service

We propose to suppress this association for following reason: It has
been demonstrated (REF. MCH 94: C. cience, Trinity College, Dublin,
Ireland, October 1994) that specifying mutual exclusion constraint
among services by listing explicitly conflicting services penalizes
maintainability, evolutivity of the system. Namely, this point leads
to the question of inheritance anomaly. Indeed, it does not allow to
change the interface (i.e. set of service it provides to clients)
without reanalyzing whole concurrency issues. herefore, specifying
concurrency constraints of services by declaring the set of used
resource and their using mode (modifying, querying, McHale, ) ensures
that the specification of each services remains independent. And thus
it will remove the drawbacks mentioned before.