Fig 4 - uploaded by Martin Hitz
Content may be subject to copyright.
Source publication
The ,object-oriented modeling ,language ,UML offers various notations for all phases of application development. The user is left alone, however, when applying UML in up-to-date application development involving distribution, data management, and component-oriented mechanisms. Moreover, various shortcomings have been encountered, most notably w.r.t...
Contexts in source publication
Context 1
... the unshaded states of Figure 4, which depicts the life cycle of a generic class RESERVATION (gray shaded states and incident transitions are considered below). A reservation object is created, the availability of the thing to be reserved is checked, and the reservation is either confirmed or a sorry letter is sent. ...
Context 2
... assume a subclass CAR_RESERVATION, which extends the inherited life cycle in that the signing of an insurance contract is added (cf. light-gray shaded states in Figure 4). This parallel extension seems to be most intuitive and a frequently recurring pattern in reality. ...
Context 3
... assume a subclass RESERVATION_WITH_CANCEL of class RESERVATION, which extends the inherited life cycle with the possibility to cancel the reservation (cf. dark-gray shaded states in Figure 4). This alternative extension implies the contravariant notion of consistent inheritance, in that no inherited conditions and no inherited types of parameters are changed. ...
Similar publications
In the class of (re)scheduling problems where humans constitute the main resource, the scheduling process is influenced by a great number of regulations. The complexity and the dynamic nature of these regulations impose the need for an efficient, flexible and user-friendly way to express and manage them. Our approach, called REDOM, in the form of a...
Model Driven Software Engineering (MDSE) is an established approach for developing complex software systems. The Unified Modelling Language (UML) is one of the most used model languages for applying the MDSE approach. UML has 14 diagram types that describe different perspectives of one software system under development. These diagrams are strongly...
Time Wrap algorithm is a well-known mechanism of optimistic synchronization in a parallel discrete-event simulation (PDES) system. It offers a run time recovery mechanism that deals with the causality errors. For an efficient use of rollback, the global virtual time (GVT) computation is performed to reclaim the memory, commit the output, detect the...
Citations
... Diagrams in version 1 are still widely used but in the "Modeling at School" project, the current version 2 is used, because of the higher number of possibilities [7]. UML is the industrial standard notation for object-oriented software modeling [8] but not restricted to software development. Eriksson and Penker [9], for instance, propose the use of UML diagrams for businesses to better understand key mechanisms, improve structures and operations or visualize structures of innovated businesses as a basis for action plans. ...
Effective learning is always an active process where students should create and construct their knowledge themselves. To support this independent work, creative strategies for elaborating, structuring, visualizing and memorizing learning contents are welcome in every domain. They are especially useful in subjects considered as difficult or for students with learning difficulties. Mind maps, concept maps and advanced organizers are familiar tools for visualization. Modeling is one of these creative learning strategies, with the benefit, that it is additionally fostering computational thinking and digital literacy. In this paper, we focus on modeling with diagrams used as learning strategy. These diagrams originally come from the field of computer science, where modeling is a crucial concept and visualizing technique. We mainly use diagrams of the Unified Modeling Language (UML), a graphic modeling language used in software engineering. With UML diagrams it is possible to cover respectively visualize a broad range of situations and learning purposes across all subjects from primary up to secondary education. Our research focuses on detecting those diagrams that are most useful and practicable for teachers and learners without computer science background. The paper introduces the use of modeling as brain-based learning strategy and describes which models and diagrams can be used for which purpose and in which context in order to support and enrich learning and teaching in different subjects. Besides giving some creative ideas and best practice examples for primary and lower secondary education, the paper summarizes qualitative results gained up to now, which build the basis for our new international project “Modeling at School”. Finally, we give an outlook on this project, its research focus and some preliminary results.
... Most of the diagrams taught in our workshops (in this paper we present class and activity diagrams) are part of the Unified Modeling Language UML, an object-oriented modeling language that offers various notations for all phases of application development. [15] Models are simplified representations of the real world. They can be represented in different ways ( Fig. 1): mental, physical or symbolic. ...
... • The behavioural perspective can be useful in all domains, but is particularly used in systems design. UML supports the behavioural perspective using Statecharts, but does not support the refinement of Statecharts in a satisfactory way according to (Hitz and Kappel 1998). • The functional (process) perspective is supported on a high level through Use Case modelling (aka. ...
... • The functional (process) perspective is supported on a high level through Use Case modelling (aka. 0-level DFD), a language that has been highly criticised for not being well-defined (Hitz andKappel 1998, Génova et al. 2002). Whereas Use-cases are meant for requirements modelling, activity diagrams can be used for simple procedural description by showing control flow and the production of data or objects in a process flow. ...
Different parts of SEQUAL can be used in a number of different ways, including:
... • The behavioral perspective can be useful in all domains, but is particularly used within design. UML supports the behavioral perspective using State charts, but does not support the refinement of Statecharts in a satisfactory way (Hitz & Kappel, 1998). ...
... The functional (i.e., process) perspective is supported on a high level through use case modeling (a.k.a. 0-level DFD), which is a language that has been highly criticized for not being well defined (Hitz &Kappel, 1998;Genova, Llorens & Quintana, 2002). Whereas Use-cases are meant for requirements modeling, activity diagrams can be used for simple procedural descriptions by showing control flow and the production of data or objects in a process flow. ...
... Due to its strong support, UML is probably the best general modeling language to adopt as a basis for object-oriented development if another language with good support tools is being used in a satisfactory way. Another positive aspect of UML, when compared to early work on OOA/OOD, is the inclusion of use-cases (Hitz & Kappel, 1998). Thanks to the inclusion of use-cases, the first step in object-oriented development does not encompass finding objects in the problem domain, but rather it encompasses the identification of the system functionality as required by the users. ...
Many researchers have evaluated different parts of UML™ and have come up with suggestions for improvements to different parts of the language. This chapter looks at UML (version 1.4) as a whole, and contains an overview evaluation of UML and how it is described in the OMG™ standard. The evaluation is done using a general framework for understanding quality of models and modeling languages in the information systems field. The evaluation is based on both practical experiences and more theoretical evaluations of UML. Based on the evaluation, we conclude that although being an improvement over it is predecessors, UML still has many limitations and deficiencies, both related to the expressiveness and comprehensibility of the language. Although work is well underway for the next version of UML (version 2.0), not all of the important problems seem to be addressed in the upcoming new version of the language.
... Our second objective is to model transfer of control through sequence diagram composition. The main decision to make is where to annotate control information. One approach is to include composition information in individual diagrams. [4] examines sequence diagram generation from use cases, and discusses the probe concept, a smaller piece of a scenario that can be inserted at a specified point in a larger scenario. [8] presents a similar approach using sub-scenarios. A second approach is to use a separate hierarchical diagram, instead of embedding control information in ...
Sequence Diagrams (SDs) have proven useful for describing transaction-oriented systems, and can form a basis for creating
statecharts. However, distributed embedded systems require special support for branching, state information, and composing
SDs. Actors must traverse many SDs when using a complex embedded system. Current techniques are insufficiently rich to represent
the behavior of real systems, such as elevators, without augmentation, and cannot identify the correct SD to execute next
from any given state of the system. We propose the application of formal language theory to ensure that SDs (which can be
thought of as specifying a grammar) have sufficient information to create statecharts (which implement the automata that recognize
that grammar). A promising approach for SD to statechart synthesis then involves ‘compiling’ SDs represented in an LL(1) grammar
into statecharts, and permits us to bring the wealth of formal language and compiler theory to bear on this problem area.
... @BULLET Looking upon detailed aspects of the language and present improvements for these areas[13]. @BULLET Using a developed framework for assessing different aspects of language quality in a certain context[14,34], or parts of language quality such as expressiveness using a general ontology such as[39])Even those using a general evaluation framework looks upon the language quality features as the goals to achieve. Contrary to this, Krogstie, Sindre, and Lindland[20,21,25]have developed a framework for discussing the quality of models such as those found in requirement's specifications and design in general. ...
... The area of volumetrics is only partly supported. @BULLET UML support the behavioral perspective using Statecharts, but do not support the refinement of Statecharts in a satisfactory way[13]. @BULLET The functional (process) perspective is supported on a high level through Use Case modeling (a.k.a. ...
... Due to its strong support, UML is probably the best to use as a basis for object-oriented development. Another positive aspect is the inclusion of use-cases[13]. Thanks to this, the very first step in object-oriented development does not encompass finding objects in the problem domain, but the identification of the system functionality as required by the users. ...
Many people have evaluated different parts of UML and have come up with suggestions for improvements to different parts of the language. This paper look at UML 1.3 as a whole, and contains an evaluation of UML and how it is supported in the modeling tool Rational Rose as a basis for creating models of high quality. The evaluation is done using a general framework for understanding quality of models and modeling languages in the information systems field. The evaluation is based on both practical experiences and existing evaluations of UML and Rational Rose. Based on the evaluation, we conclude that, although being an improvement over it is predecessors, UML still has many deficiencies. Also Rational Rose only partly supports the development of information system models of high quality, and provides too limited support for using different modeling techniques in concert within a larger methodological framework.
... It suffers from an incomplete definition of some concepts, such as the relationships between use cases. It also lacks expressiveness, for example for supporting the traceability of evolutions in class diagrams [Hitz98]. Another problem relates to the adequacy of use cases to promote a real object-oriented approach, since use cases actually promote a process-oriented approach instead of focussing on data abstractions [Meye97]. ...
... The functional (process) perspective is supported on a high level through use case modeling, a language that has been highly criticized for not being well-defined (Hitz & Kappel, 1998). Whereas use cases are meant for requirements modeling, activity diagrams can be used for simple procedural descriptions by showing control flow and the production of data or objects in a process flow. ...
... • Looking upon detailed aspects of the language and present improvements for these areas e.g. (Hitz & Kappel, 1998). • Using a framework for assessing different aspects of language quality such as expressiveness in a certain context (Hommes & van Reijswoud, 1999; Prasse, 1998). ...
... @BULLET Looking upon detailed aspects of the language and present improvements for these areas e.g. (Hitz & Kappel, 1998). @BULLET Using a framework for assessing different aspects of language quality such as expressiveness in a certain context (Hommes & van Reijswoud, 1999; Prasse, 1998). ...
... @BULLET The behavioral perspective can be useful in all domains, but is particularly used within design. UML supports the behavioral perspective using Statecharts, but does not support the refinement of Statecharts in a satisfactory way (Hitz & Kappel, 1998). @BULLET The functional (process) perspective is supported on a high level through Use Case modeling (a.k.a. ...
Many researchers have evaluated different parts of UML and have come up with suggestions for improvements to different parts of the language. This paper looks at UML (version 1.3) as a whole, and contains an overview evaluation of UML as a basis for creating models of high quality. The evaluation is done using a general framework for understanding quality of models and modeling languages in the information systems field. The evaluation is based on both practical experiences and evaluations of UML made by others. Based on the evaluation, we conclude that, although being an improvement over it is predecessors, UML still has many limitations and deficiencies.
In der UML-basierten objektorientierten Anforderungsanalyse werden funktionale Anforderungen mit Hilfe von Anwendungsfällen formuliert, ihre Dynamik z.B. durch Aktivitätsdiagramme modelliert und strukturelle Anforderungen durch Klassenmodelle beschrieben. Techniken und Abstraktionsniveaus der Teilmodelle sind sehr verschieden, so daß sich erhebliche Konsistenzprobleme für die Gesamtspezifikation ergeben. Um diese Nachteile zu überwinden, erweitern und präzisieren wir Anwendungsfälle im Hinblick auf die Modellierung ihres dynamischen Verhaltens. Granularität und Semantik des Ansatzes schließen die Lücke zwischen Anwendungsfällen und Klassenmodellen und legen die Basis für die Validierung von Anwendungsfällen und Teilen des Klassenmodells und die Verifikation des Klassenmodells gegen die Anwendungsfälle.
