Eriksson, H., and M. Penker. 1998. UML Toolkit. New York: John Wiley & Sons.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....Ensuring the quality of such software systems from the initial stages is a challenging task. UML use cases are becoming the standard form for requirements specification. An UML use case describes some functionality offered by a system as perceived by the user or an external actor of the system [1, 2, 9]. The user sees the system as a black box that responds to inputs with a specified output. Use cases are very often specified using a combination of text and diagrams that must be interpreted by the system designers and translated into a more concrete representation. It would be beneficial to ....

....approach for refining use cases specified with MSC into design MSC in a stepwise manner. The resulting MSC is then used as input for our MSC to SDL translation approach. In our approach, a use case model is developed through interactions with the system designers and the customers as described in [1, 2, 9]. The result of this represents the functional requirements of the system under construction. Once the use cases have been agreed on, the designers must specify the architecture of the system. Guided by this architecture, the use cases are then refined in a stepwise manner. We distinguish between ....

H. E. Eriksson and M. Penker, "UML Toolkit", John Wiley & Sons Inc., 1998.

....that are commonly used for CORBA based systems. This way, the framework can be easily integrated with various development tools and methodologies. Second, we require the framework to support the usual style of UML modeling as proposed in the UML standard [Rat97] and in the literature (e.g. [Eri98, Jac98, Dou99, Rum99]) This way, it is possible to extend exist ing functional models into performance models without rewrit ing them. Third, we require the framework to clearly distinguish between different architectural aspects of CORBA based distributed systems. The framework should allow designers to keep ....

....some parts of the system without modifying other parts. This requirement is elaborated in Section 2.5 once the CORBA platform has been presented in more detail. Fourth, the framework should support incremental development style, since this is commonly used with object oriented analysis and design [Eri98, Jac98, Sou98]. In particular, it should be possible to build abstract and solvable performance models already in the analysis phase when the infrastructure and hardware issues are still unknown. Also, it should be possible to upgrade the first tentative models into more accurate ones without the need to write ....

[Article contains additional citation context not shown here]

Eriksson, H-E., Penker, M., UML Toolkit, John Wiley & Sons, New York, 1998.

....comprises a membrane (controlling wrapper) and plasm (internals of the component) The concrete model refines the general model to reflect an implementation (in the Java language) by introducing type system based on the Java type system etc. 2. 3 UML related work OMG Unified Modeling Language [18] is a recognized industrial standard for graphical modeling of software systems by a set of standardized, semiformal diagrams. Therefore, we devote this section to the discussion of UML based strategies for describing the behavior of components and the relation of UML to ADLs. 2.3.1 Standard UML ....

H.E. Eriksson, M. Penker, UML Toolkit, John Wiley & Sons, 1998.

....the technical side of the system and a quick overview of the user interface. Further, we will show the restfits of an end user evaluation and the conclusions drawn from it. 4. 1 DESIGN CHOICES Architecture of Carrot was designed in Unified Modeling Language (UML) Booch et al. 99] OMG, 01] Eriksson and Penker, 98] use case model was created, actors and system 27 Carrot should be available at http: www idss.cs.put.poznan.pl carrot 57 functions were distinguished. Unfortunately, as it usually is the case when time constraints generate friction with documentation neatness, the UML model was abandoned ....

Eriksson H. E., Penker M.: UML Toolkit, John Wiley & Sons, 1998.

....pairs of typed interfaces (collaborations) A collaboration description includes a protocol described as a set of sequencing constraints based on a transition system. Another option of how to describe a component behavior is to employ the UML collaboration, interaction, and state diagrams [29]. These diagrams are primarily used for a semi formal description of object behavior, but the notation can be used for describing component behavior as well. For employing a behavior description of a component, the notation used has to strongly support description of the call interplay on the ....

....as a whole is not considered; consequently, no concepts similar to our frame and architecture protocols are present. Thus, the protocol description in [28] is less suitable for reasoning about component composition, replacement, etc. The UML collaboration, interaction, and state diagrams [29] are used for a semi formal description of object behavior. Nevertheless, collaboration and interaction diagrams can describe only important traces of execution so that they cannot be used for a complex description of component behavior. Although state diagrams are, in principle, finite state ....

H.E. Eriksson, M. Penker, UML Toolkit, John Wiley & Sons, 1998.

....and SCM similarities and differences The Association of Swedish Engineering Industries 2001 There are a number of languages capable of handling product information together with semantics. The two languages used most today are the lexical language EXPRESS [Sch94] and the visual language UML [Eri97]. Both these languages are defined by international standards and are not based on any specific implementation technique or specific programming language. The advantages of EXPRESS, compared with UML, are its capacity to handle rules and the fact that it specifically was designed to describe ....

Eriksson, H. E., Penker, M., "UML Toolkit", Wiley & Sons, Chichester, 1997.

....et al. [2] indicates that the sequence diagrams are a means to model some aspect of the dynamic behavior of the system and can be used in context of the whole system, a sub system or they can be attached to a use case. Some indicate that a sequence diagram should be drawn, at least per use case [6, 19, 5, 18]. When a sequence diagram is developed for a use case, the use case descriptions can be used to develop at least the initial draft of a sequence diagram. Throughout the design process the use case diagram can be revised based on the results of the sequence diagram, and vise versa, until both ....

Eriksson, H. and Penker, M. (1998). UML Toolkit. New York: John Wiley, Inc.

.... TrustHealth1 the Magdeburg Medical Informatics Department has been involved in [5, 6, 30] For analysis of system requirements, system design, specification, implementation, and maintenance, a generic component model approach and the Unified Modelling Language (UML) methodology have been applied [8, 9, 15]. The usability of the methodology regarding the composition of different levels of abstraction and granularity enabling different views has been demonstrated in [3] SECURITY SERVICES BEING ADDRESSED Security is a very complex concept considering security, safety and quality as important ....

Eriksson H-E, Penker M (1998) UML Toolkit. John Wiley & Sons, Inc., New York

....and has specific stereotype design requirements associated with it. For each class, we give a first cut set of guidelines for designing and defining stereotypes of this class. To our knowledge, there is almost no related work on classification and design of stereotypes. Eriksson and Penker [5] classify the standard (i.e. predefined) stereotypes of UML according to the language concept they are applied to. For user defined stereotypes, however, there is no classification. In the literature on UML and OML (e.g. 12] 5] 6] the design and definition of stereotypes is treated in a very ....

....work on classification and design of stereotypes. Eriksson and Penker [5] classify the standard (i.e. predefined) stereotypes of UML according to the language concept they are applied to. For user defined stereotypes, however, there is no classification. In the literature on UML and OML (e.g. 12][5][6] the design and definition of stereotypes is treated in a very vague and superficial fashion only. In an earlier paper in German [10] we have introduced the idea of our classification framework along with some examples and a preliminary discussion of weaknesses and benefits. The rest of the ....

Eriksson, H.-E., Penker, M. (1998): UML Toolkit. NewYork: John Wiley & Sons.

....to any software design methods that model behavior using graphical notations to represent data or control flow among semantic elements arrayed in directed graphs. For example, the semantic concepts in COBRA appear quite similar in intent to stereotypes in the Unified Modeling Language (UML) [6, 31 33]. UML collaboration diagrams appear similar in conception to flow diagrams used in COBRA. UML collaboration diagrams, properly labeled with stereotypes and augmented with additional information, could possibly be input to a design generator to produce a concurrent design. In another extension, ....

Eriksson, H. E., and Penker, M. (1998) UML Toolkit, Wiley Computer Publishing, 1998.

....to any software design methods that model behavior using graphical notations to represent data or control flow among semantic elements arrayed in directed graphs. For example, the semantic concepts in COBRA appear quite similar in intent to stereotypes within the Unified Modeling Language (UML) [6, 31 33]. UML collaboration diagrams appear similar in conception to flow diagrams used in COBRA. UML collaboration diagrams, properly labeled with stereotypes and augmented with Draft 11 15 98 32 additional information, could possibly be input to a design generator to produce a concurrent design. In ....

Eriksson, H. E., and Penker, M. (1998) UML Toolkit, Wiley Computer Publishing, 1998.

....providing treatment to the patient) an attending physician attends one or many patients. In many systems, relationships are modeled implicitly by capturing information about the relationship in one or more of the entities involved in the relationship. In fact, modeling languages like UML[8] allow different types of relationships to be captured implicitly (as an attribute in one or more of the entities involved) 2 . 2 Relationships, in the context of this discussion, are also referred as associations in UML. However, in some application domains, there is a need to define ....

Eriksson, A., Penker M., UML Toolkit. John Wiley & Sons. 1998

....to model the behavior of a single object class, especially if the class demonstrates significant dynamic behavior. Statechart diagrams show the life history of a given class, the events that that take a transitions from a state to another, and the action as that result from a state change [Eric98]. A state is a situation during the life of an object, which satisfies some condition, performs some activity or waits from some event. An action is an activity performed on an object while the object is in a given state. Figure 7. A Cellular telephone Statechart Diagram In this example, a ....

Eriksson , Hans-Erik et al., UML toolkit, Wiley, 1998

....of concern for social and organizational factors. Yet, many system development methodologies mainly focus on the technical aspects and do not support the analysis of the organizational elements that determine success or failure. This even holds for the recent object oriented approaches such as UML [Eriksson and Penker, 1998], and for much of the work in the knowledge management area coming from the IT community (see, e.g. Wolf and Reimer, 1996] 1 Therefore, there is a clear practitioner s need to bridge the gap between organization and systems issues. It is essential to have knowledge management and engineering ....

....model consists of 9 the following dimensions: 1. Functional view: decomposition into subtasks, their inputs and outputs, and the I O flow connecting these subtasks into an overall information flow network. Traditional dataflow diagrams (DFDs) are a widely used technique here. In the UML notation [Eriksson and Penker, 1998] the best candidate is an activity diagram. 2. Static information structure: a description of the information content and structure of objects that are handled in the task, such as its input and output objects, in terms of entities and their relationships (or objects and associations) The UML ....

H-E. Eriksson and M. Penker. UML Toolkit. Wiley, New York, 1998.

No context found.

Eriksson, H., and M. Penker. 1998. UML Toolkit. New York: John Wiley & Sons.

No context found.

H.-E. Eriksson, M. Penker, B. Lyons, and D. Fado, UML 2 toolkit. Indianapolis, Ind.: Wiley Pub., 2004.

No context found.

Eriksson HE., Penker M, Lyons B, Fado D (2004) UML 2 toolkit. Wiley, Indianapolis

No context found.

H.-E. Eriksson, M. Penker, B. Lyons, and D. Fado, UML 2 toolkit. Indianapolis, Ind.: Wiley Pub., 2004.

No context found.

H.-E. Eriksson, M. Penker, B. Lyons, and D. Fado, UML 2 toolkit. Indianapolis, Ind.: Wiley Pub., 2004.

No context found.

H. Eriksson, M. Penker, B. Lyons and D. Fado, UML 2 Toolkit, Wiley, October, 2003.

No context found.

Eriksson, H. & Penkar, M., UML Toolkit, John Wiley & Sons, Inc., 1998.

No context found.

Hans-Erik Eriksson and Magnus Penker, UML Toolkit, John Wiley & Sons, 1998.

No context found.

H-E. Eriksson and M. Penker, UML Toolkit, Wiley, 1998.

No context found.

H.E. Eriksson, M. Penker, UML Toolkit, John Wiley & Sons, 1998.

No context found.

Eriksson, H., and Penker, M. (1998) UML Toolkit. John Wiley and Sons, London.

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