Issue 5022: 4.1.6 - Access Control Policy (uml-scheduling-ftf)
Source: Commissariat a l Energie Atomique-CEA (Dr. Sebastien Gerard, sebastien.gerard(at)cea.fr)
Nature: Uncategorized Issue
Severity: 
Summary: There is certainly a link to do between this concept and the ”ConcurrencyPolicy” concept managing concurrent execution of services of a given a resource. But I did not find it…

Resolution: Closed, no change
Revised Text: -- replace figure 6-3 with the following one: 
  
-- replace the first line of the "schedulingPolicy" explanation in section 7.1.4.6 by the following line: 
schedulingPolicy	(inherited from ProtectedResource) the access control policy for handling 

Actions taken:
March 20, 2002: received issue
September 24, 2004: closed issue
Discussion: 
I don't see that there is necessarily a link between these two concepts. It is unclear to me what is meant by "Concurrency Policy" in the text of the issue. In the Concurrency section there is no such concept, although there are corresponding concepts in the Schedulability and Performance analysis sections. However, in the schedulability sub-profile, the concept is a subclass of ResourceControlPolicy (which is wrong since it should be a subclass of AccessControlPolicy instead), whereas in the Performance analysis section the connection has not been made at all (although the same enumeration values are used for both cases). These two derivative issues could be fixed with a relatively minor change to the domain model with no accompanying backward compatibility problems (since they are in the abstract part of the domain model)..

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

4.1.6 - Access Control Policy

There is certainly a link to do between this concept and the