Issue 5051: Section 6.1.3 (uml-scheduling-ftf)
Source:  (, )
Nature: Uncategorized Issue
Severity: 
Summary:  it is said that the schedulability analysis is inherently instance-based. The instance-based description is required to identify the system load (identify the active objects and their execution distributions) and data resources (objects that can be used for synchronization purposes). But the non-blocking passive objects can be analyzed description-based, and their dynamic instantiation do not affect to the analysis because their responses do not depend on the instance (but some polymorpic behaviors). The instance-based analysis does not allow analyze systems where passive objects are created dynamically (the static analysis of systems with dynamic creation of active and resource objects is a different problem).

Resolution: Closed, no change
Revised Text: 

Actions taken:
March 20, 2002: received issue
June 30, 2003: closed issue
Discussion: 
This scenario is outside the scope of the conceptual model - this needs to be addressed by a major revision.

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

Section 6.1.3

 it is said that the schedulability analysis is inherently
 instance-based. The instance-based description is required to
 identify the system load (identify the active objects and their
 execution distributions) and data resources (objects that can be used
 for synchronization purposes). But the non-blocking passive objects
 can be analyzed description-based, and their dynamic instantiation do
 not affect to the analysis because their responses do not depend on
 the instance (but some polymorpic behaviors). The instance-based
 analysis does not allow analyze systems where passive objects are
 created dynamically (the static analysis of systems with dynamic
 creation of active and resource objects is a different problem).