SPTP 1.0 NO IDEA Avatar
  1. OMG Issue

SPTP — 4.1.6- Excusive Service

  • Key: SPTP-61
  • Legacy Issue Number: 5023
  • Status: closed  
  • Source: Commissariat a l Energie Atomique-CEA ( Dr. Sebastien Gerard)
  • 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.

  • Reported: SPTP 1.0b1 — Wed, 20 Mar 2002 05:00 GMT
  • Disposition: Resolved — SPTP 1.0
  • Disposition Summary:

    Closed, no change

  • Updated: Fri, 6 Mar 2015 20:58 GMT