| A. Lyons. UML for Real-Time Overview. Objectime Ltd., April 1998. http://www.objectime.com/otl/technical/umlrt. html. |
....by translation of OOP source code into a UML specification. The advantage of the UML are the different views on the software project in one methodology. This includes concepts for integration of Real Time aspects by, for instance, integration of the RealTime Object Orient Modeling method [55]. The Real Time aspect is given in this method by modelling the behaviour with state charts. The execution time of the automata can be determined (compare for example [28] and the timing behaviour of the composed system can be evaluated. Other approaches introduce the aspect of time by ....
Andrew Lyons. Uml for real-time overview. Technical report, Rational Rose, 1998.
....work provides an excellent baseline (as does our own Permabase work [8] but none provide support for the areas of multimedia design we address in this project. Relevant work on tailored solutions to UML includes the work by Objectime in association with Rational on use of UML for realtime systems [9], and that of Douglas [10] that concentrates on embedded systems. The correct specification of behaviour is particularly important in a complex multimedia system, and within UML behaviour can be specified in a number of ways (e.g. using different forms of behavioural diagram) Support is ....
A. Lyons, "UML for Real-Time Overview," ObjectTime Limited.
....the developer can recognize the existence of that class in a library, which allows it to be immediately reused. The class diagram is understood as a template for a set of applications that can be obtained from it. In other words, the class diagram is a high level generalization of the system [13]. When the developers define the way classes are interrelated, they are indicating all the systems (or all the configurations) that can be obtained from those classes. With this perspective, it is common, in several methodologies, to not build the object diagram, since it automatically results ....
A.Lyons. UML for Real-Time Overview. Technical report, ObjecTime Limited, Apr.1998.
....implemented in the ObjecTime toolset, provides an expressive modeling language supported by a powerful development methodology. The popularity of ROOM and ObjecTime has rapidly increased in the software industry worldwide with a consequence that the ROOM notation is now part of the UMLRT notation [62]. In ROOM, systems are modeled by means of communicating hierarchical state machines. The ROOM modeling language is composed of two distinct parts: a structure part, simply called ROOM Structure, and a behavior part, called ROOMCharts (inspired by statecharts [36] In this section, after ....
A. Lyons. UML for Real-Time Overview. http://www.objectime.com, 1999.
....adequate alternative for embedded systems. Several researchers have also selected UML as the notation for specifying embedded systems, which confirms the usefulness of UML for this engineering field and indicates that this notation is gaining widespread acceptance and usage within this community [4, 5, 6, 7, 8, 9]. For specifying the systems, the authors are using the main views captured by the following UML diagrams: 1) use case diagrams are utilized to catch the functional aspects of the system as viewed by its users; 2) object diagrams show the static configuration of the system, and the relations ....
A. Lyons, UML for Real-Time Overview, ObjecTime Limited, Apr., 1998.
....may not be fully automatable, there are various types of mismatches that can be identified and even resolved in an automated or semi automated fashion. 2 Motivation for View Integration in UML A number of options have recently been proposed to represent certain architectural concerns in UML [3,4,5]. However to date none of them have explored the possibility of ensuring the consistency of these new views with existing ones. We refer to this issue of ensuring consistency among different views as view integration (as opposed to mere view representation) A contribution of this paper is a ....
....the constraint above. 4] C2Components participate in at most two whole part relationships named internalObject, and dialog. LET WHOLES = SELF.OCLTYPE.ASSOCEND SELECT(AGGREGATION = COMPOSITE) WHOLE SIZE = 4) AND ( WHOLES.ASSOCIATION.NAME ASSET) SET INTERNALOBJECT , DIALOG ) SIZE=0 [5] Each operation on the internal object has a corresponding notification which is sent from the component s bottom interface. LET OPS = SELF.INTERNALOBJECT.FEATURE SELECT(F F ISKINDOF(OPERATION) LET BOTINT = SELF.OCLTYPE.INTERFACE SELECT(I I.C2POS = BOTTOM) OPS FORALL(OP ....
[Article contains additional citation context not shown here]
Lyons, A.: UML for Real-Time Overview. White Paper, ObjectTime (1998)
....may not be fully automatable, there are various types of mismatches that can be identified and even resolved in an automated or semi automated fashion. 2 Motivation for View Integration in UML A number of options have recently been proposed to represent certain architectural concerns in UML [3,4,5]. However to date none of them have explored the possibility of ensuring the consistency of these new views with existing ones. We refer to this issue of ensuring consistency among different views as view integration (as opposed to mere view representation) A contribution of this paper is a ....
....to the constraint above. 4] C2Components participate in at most two whole part relationships named internalObject, and dialog. LET WHOLES = SELF.OCLTYPE.ASSOCEND SELECT(AGGREGATION = COMPOSITE) WHOLE SIZE = 4) AND ( WHOLES.ASSOCIATION.NAME ASSET) SET INTERNALOBJECT , DIALOG ) SIZE=0 [5] Each operation on the internal object has a corresponding notification which is sent from the component s bottom interface. LET OPS = SELF.INTERNALOBJECT.FEATURE SELECT(F F ISKINDOF(OPERATION) LET BOTINT = SELF.OCLTYPE.INTERFACE SELECT(I I.C2POS = BOTTOM) OPS FORALL(OP ....
[Article contains additional citation context not shown here]
Lyons, A.: UML for Real-Time Overview. White Paper, ObjectTime (1998)
No context found.
A. Lyons. UML for Real-Time Overview. Objectime Ltd., April 1998. http://www.objectime.com/otl/technical/umlrt. html.
No context found.
A. Lyons. UML for Real-Time Overview. Objectime Ltd., April 1998. http://www.objectime.on. ca/otl/technical/umlrt.html.
No context found.
A. Lyons. UML for Real-Time Overview. Objectime Ltd., April 1998. http://www.objectime.com/otl/ technical/umlrt.html.
No context found.
A. Lyons. UML for Real-Time Overview. Objectime Ltd., April 1998. http://www.objectime.on. ca/otl/technical/umlrt.html.
No context found.
A. Lyons. UML for Real-Time Overview. Technical report, ObjecTime Limited, 1998.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC