Modeling of real time software systems (RTSS) consist of different components with UML 2.0 leads to a design model using various diagrams. To get a consistent model, a consistency concept for different diagrams type is needed that takes into account real time constraints. Ensuring consistency of The Unified Modeling Language (UML) model is very crucial as it is effect to the quality of UML model and directly gives impact to good implementation of Information System. Although there are increasing researches on consistency management, there is still lack of researches of consistency driven by Use Case. With this motivation, in this paper, we have proposed few consistency rules between Use Case, Sequence and Timing diagrams which focus on the establishment of timing constraints. Elements of each diagram involved in the proposed rules are formalized. Using an example, we show how the diagrams fulfill our proposed consistency rules.

No abstract

No abstract

The behaviors of real time software systems do not depend only on the values of input and output signals, but also on the times of their occurrences. Real time systems (RTS) interact with their environments using time constrained input/output signals. The complexity of Real Time Systems is continually increasing which makes their design very challenging. In RTS, the scheduling of tasks with hard deadlines has been an important area of research. Unified Modeling Language (UML), the standard visual object-oriented modeling language, is suitable to deal with this complexity. The main objective of this paper is to compare two protocols using UML 2.0 models. The shortcomings of the existing Priority Inheritance protocol are represented using one UML model. Further, the Stack Based Priority Ceiling protocol is used to overcome this difficulty using an improved model.

No abstract