B.P.Douglass,Real-Time UML : Developing Efficient Objects for Embedded Systems,98.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....be made smaller and tighter. Otherwise, it will become too cumbersome and multifaceted to be really useful. I think it will gradually shrink, leaving only three or four types of diagrams that are really needed and are useful. The rest will probably become obsolete and will eventually disappear [3]. What we have here is essentially a statement of the need for conceptual integrity. Use a small number of powerful descriptions that work together to help describe the software product; provide one good way to describe every construct of interest. This will prevent the documentation from ....

Douglass, B.P. Real-time UML: developing efficient objects for embedded systems (2nd edition), Addison-Wesley, Reading, MA, 1999.

....of those classes. This is the main reason that methodologies usually impose (or suggest) class diagrams to be elaborated first than object diagrams. There is an additional task in which it must be assured that there is consistency between the information that is described by both diagrams [5]. This fact can be interpreted as a symptom that some information is being unnecessarily replicated. For instance, the existence of the singleton stereotype in UML, which indicates that a given class can only have one single instance corroborates the perspective that sees the class diagram as a ....

B. Douglass. Real-Time UML: Developing Efficient Objects for Embedded Systems. Addison-Wesley, 1998.

....As the development progresses these requirements are transferred into sequence diagrams and finally on to the relevant objects. The total time required for each object to complete its tasks is checked to be less than or equal to the time associated to the use case sequence. 2 Douglass [5] has built substantially on Jacobson s approach, providing a detailed description of the issues involved in embedded system development as well as considerable discussion on how to pictorially represent the intentions of the developer with the UML notation. The crucial rigorous proof is still ....

....the collaborating objects is preserved. That is, textual analysis, domain knowledge, preliminary study or business modeling resulting in classes and relationships as usual. Interaction diagrams In most texts on the UML, the use cases are expanded upon using sequence diagrams. Douglass [5] has shown how simple temporal parameters can be expressed on sequence diagrams. Typically these are maximum allowable response times and periods for iterative messages. By extending the syntax to support interval based parameters it is possible to temporally describe every message. Those ....

[Article contains additional citation context not shown here]

Douglass, B.P. Real time UML -- Developing Efficient Objects for Embedded Systems. Addison Wesley, 1998.

....UML adopted David Harel s statecharts [6] for the intra object behavior modeling. Statecharts is a behavioral language for the specification of real time, event driven, and reactive systems . States in a statechart are conditions of existence that persist for a significant period of time [7]. Events trigger transitions from one state to another. They may be guarded by conditions, which must evaluate to true before transitioning to the next state. Actions can occur as the result of a state transition. The statechart model can be used to support AOSD by extracting the hardwiring of ....

. Bruce Powel Douglass, "Real-Time UML: Developing efficient Objects For Embedded Systems", Addison-Wesley, 1998.

....the system while a dynamic one describes the behavioural ones. Larman s main contribution relies on proposing to define the system behaviour as a black box before proceeding to a logical design of how a software application will work. The main idea behind this solution has also been sketched in [Boo96, FS97, Mu197, Dou98, RV00]. This has a clear impact, during analysis, on the sequence diagrams definition and on the assignment of operations to classes. Sequence diagrams are considered as system sequence diagrams that show the events that external actors generate; their order and the system response to those events. On ....

B.Douglass. "Real-time UML: Developing Efficient Objects for Embedded Systems", Addison-Wesley, 1998.

....systems that enables the construction of models that could be used to make quantitative predictions regarding these characteristics . It tries to unify the various different approaches that have evolved for modeling real time application in UML. These are namely the approaches from Douglass [Dou98] that uses mainly the existing predefined UML diagrams, and the work from Selic that uses extensively the option of UML to define stereotypes (a kind of visual macros in diagrams) to impose a notation similar to ROOM (Real Time Object Oriented Modeling) Sel94] his prior modeling environment onto ....

Douglass, Bruce Powel, Real-Time UML: Developing Efficient Objects for Embedded Systems, Addison-Wesley, Reading, MA, 1998.

....a state transition. Orthogonal regions, which are shown as dashed lines in statecharts, combine multiple simultaneous descriptions of the same object. Interactions between regions occur typically through shared variables, awareness of state changes in other regions and message passing mechanisms [Dou98] such as broadcasting, and propagating events. We choose statecharts to model the behavior of objects and aspects because: 1) They provide rich set of semantics that are suitable for concurrency. 2) When using statecharts we assume a finite set of states [Paz97] which will reduce the ....

....[Har00] Modeling Orthogonal Concerns using Orthogonal Regions Statecharts support decomposition of states in an AND OR fashion, combined with the communication mechanisms to allow communications between states. Broadcast, Propagated, and the IN( operator are the main communication mechanisms [Dou98]. Broadcast events are events communicated to more than one orthogonal component. And State is when an object is in its sub states concurrently. Each of the concurrent sub state is called an orthogonal component. Statechart models govern orthogonal states whereby an object must be in exactly one ....

[Article contains additional citation context not shown here]

Bruce Powel Douglass, "Real-Time UML: Developing efficient Objects For Embedded Systems", AddisonWesley, 1998.

....wayinto objects is a critical task, since usually there is no direct one to one mapping from use cases to objects. Several use cases can give rise to one object and one use case can originate a couple of objects. Douglass presents 11 useful strategies to find identify the objects of a system [9], but they can not be directly applied to this purpose, because none of them is based on the use cases that were previously identified. A strategy, composed of some guidelines, is needed to guide the developers on how to transform use cases into objects. There are some approaches for that ....

....of those classes. This is the main reason that methodologies usually impose (or suggest) class diagrams to be first elaborated than object diagrams. This implies an additional task in whichitmust be assured that there is consistency between the information that is described by both diagrams [9]. This fact can be interpreted as a symptom that some information is being unnecessarily replicated. For instance, the existence of the singletonAE stereotype in UML, which indicates that a given class can only have one instance, corroborates the perspective that sees the class diagram as a ....

B.P.Douglass. Real-Time UML: Developing Efficient Objects for Embedded Systems. Addison-Wesley, 1998.

....TCP IP stack packages developed for the ISO network communication standard, when a project asks for a communication port, writing a new stack does not seem worth the effort. The proponent of software reuse foresees a future where software component are built and traded like brick and mortar parts [4]. For the time being, we have to settle on more primitive forms of reuse, let al..one in the embedded world. Hardware and software firmware together completes a product. The trend is that more and more load is put on the software side whereas hardware is built of standard parts. This again makes it ....

....in Process Control System Based on our observation that processor speed and memory size may not be a constraint anymore, we suggest that it is beneficial to bring object component oriented (OO) ideas into real time system development. People have already been preaching this idea for a while [4, 8]. We shall give in this section some practical reasons. First of all OO design methodology has been used in process control system development for years. The advantage of it for non real time system development equally applies to the real time system development. Consider a simple state machine ....

B. P. Douglass, Real-Time UML - Developing Efficient Objects for Embedded Systems, Addison-Wesley Publishing Company, 1998

....is particularly important for the emerging research field software performance engineering (see e.g. 22] 23] as well as for system engineering at large. As a first step in this direction, Douglass specified language extensions of the UML for specifying real time constraints such as deadlines [6]. Furthermore, there are activities of the OMG to extend the current version of the UML for modeling real time applications. Therefore, the OMG sent out a Request for Proposal (RFP) that addresses the issue of schedulability, performance, and time [16] An initial response to the RFP that was ....

....the designer to choose the types of UML diagrams best suited for the intended representation of a system. In this paper, we choose state diagrams and activity diagrams as UML building blocks for enabling quantitative system analysis with the UML. The diagrams are presented using the notation from [6]. State diagrams of the UML provide a simple but formal means of modeling the complex event driven system behavior. All semantics necessary to express behavior (i.e. states, historical properties, transitions, and compound transitional connectors) are available on the state diagram palette. The ....

B.P. Douglass, Real-time UML: Developing Efficient Objects for Embedded Systems, 2 Edition, Addison Wesley 1999.

....User defined currentState #next Transitions Figure 3. Class diagram of Statechart pattern statechart diagram is that of Harel s statecharts [9] with extensions to make that object oriented. Table 1 compares several design patterns for implementing a FSM; Conditional Statements pattern [10], State pattern [6, 7, 11] and StateTable pattern [10] which have been proposed for implementing the state transition specification. These patterns have critical problems with support of substates, mapping from diagram to code, and readability of code. In order to solve these problems, the system ....

....Figure 3. Class diagram of Statechart pattern statechart diagram is that of Harel s statecharts [9] with extensions to make that object oriented. Table 1 compares several design patterns for implementing a FSM; Conditional Statements pattern [10] State pattern [6, 7, 11] and StateTable pattern [10], which have been proposed for implementing the state transition specification. These patterns have critical problems with support of substates, mapping from diagram to code, and readability of code. In order to solve these problems, the system designer needs a new design pattern which meets the ....

B.P. Douglass, Real-Time UML - Developing Efficient Objects for Embedded Systems, Addison-Wesley, 1998.

.... However, it still requires more formalism for the Requirements Specification [7] and, if compared to Formal Techniques, presents gaps, which result in problems [3] UML (The Unified Modeling Language) 8, 9, 10] is an important step forward the standardisation of the OO models representation [11], but it doesn t provide mapping procedures between the development phases. The use of formal techniques [7, 12] allows consistence analysis and system behaviour simulation, through wellSilvino Jos Silva Bastos is MSc in Automation Applied Computing and works in Brazilian Navy. E mail: ....

....concept of packages, which are containers used to group the model elements inside a same container. 2.1 UML System Modelling Different authors [15, 16] suggest different methods to employ UML in system modelling. The method adopted in this work is based on procedures proposed by Bruce Douglass [11, 16]. It also includes some author s contributions, presented as recommendations and heuristics to guide the modelling process, which are essential in the preparation of the UML model to be transformed in a Formal SDL Specification. The following steps shall be sequentially performed during model ....

[Article contains additional citation context not shown here]

DOUGLASS, B.P. Real Time UML: Developing Efficient Objects for Embedded Systems. Addison Wesley, 1998.

....Level Framing and Integrated Layer Processing, CT90] for more info. 8 There are serially linked if all possible protocols traverse a common path, which is usually true for link and physical layers. arrived at this structure from the merger of a Interface Pattern found in the Java context [Doug98] and OSI s 9 service access points (SAP) The interface pattern provided a structure for reuse of an implementation by multiple clients, and the SAP s provided a successful framework. In our protocol structure the SAP s have become the interface objects but they no longer reside on the ....

Douglass, B. Real-Time UML: Developing Efficient Objects For Embedded Systems. Berkeley, California: Addison Wesley Longman, 1998

No context found.

B.P.Douglass,Real-Time UML : Developing Efficient Objects for Embedded Systems,98.

No context found.

Bruce Powel Douglass, Real-Time UML: Developing Efficient Objects for Embedded Systems, Addison Wesley, Reading, MA, 1998.

No context found.

Bruce Powel Douglass, Real-Time UML: Developing Efficient Objects for Embedded Systems, Addison Wesley, Reading, MA, 1998.

No context found.

Bruce Powel Douglass. Real-Time UML: Developing Efficient Objects for Embedded Systems. The Addison-Wesley Object Technology Series. Addison-Wesley, October 1999. Second Edition.

No context found.

B. Douglass. Real-Time UML: Developing Efficient Objects for Embedded Systems. Addison-Wesley, second edition, 1998.

No context found.

Bruce Powel Douglass. Real-Time UML: Developing Efficient Objects for Embedded Systems. The Addison-Wesley Object Technology Series. Addison-Wesley, October 1999. Second Edition.

No context found.

Bruce Powel Douglass. Real-Time UML: Developing Efficient Objects for Embedded Systems. The Addison-Wesley Object Technology Series. Addison-Wesley, October 1999. Second Edition.

No context found.

B. P. Douglass, Real-Time UML: Developing Efficient Objects for Embedded Systems. Addison-Wesley, 2000.

No context found.

Douglass, B.P. (1998), Real-Time UML: developing efficient objects for embedded systems, Addison Wesley Longman.

No context found.

B.P. Douglass, Real Time UML -- Developing efficient objects for embedded systems (Massachusetts: AddisonWesley, 1998).

No context found.

B.P. Douglass, Real Time UML -- Developing efficient objects for embedded systems (Massachusetts: AddisonWesley, 1998).

No context found.

). Douglass, B. P., 2000, Real-Time UML: Developing Efficient Objects for Embedded Systems, Addison-Wesley, pp. 2-12.

First 50 documents

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