Search

INTRODUCTION A good understanding of the application domain is necessary to develop the requirements for information systems (IS). Such understanding can be facilitated with the use of conceptual models. Conceptual […], An important step in developing the requirements for an information system is analyzing the application domain. In this step, conceptual models are used for representing an application domain. However, while languages for software design are available and widely used, no generally accepted language exists for conceptual modeling. This work suggests the use of object-oriented software modeling languages also for conceptual modeling. Such use can support a more accurate transition from domain models to software models. As software-modeling languages were not intended for modeling application domains, their constructs lack the required semantics. While previous papers addressed the representation of structural elements of domains using object concepts, this paper addresses behavioral aspects, related to change and interaction. The proposed semantics are based on a mapping between ontological concepts that describe behavior and object-oriented constructs related to dynamics. Based on these mappings, modeling rules are proposed to guide the modeler in creating ontologically well-formed models. The mappings and rules are exemplified using UML and are demonstrated using a case study. Keywords: conceptual modeling; dynamics; ontology; object-oriented analysis; UML

INTRODUCTION Object-oriented analysis and design (OOAD) is the dominant software design method among practitioners. The Unified Modeling Language (UML) is an ISO standard graphical modeling language used in OOAD (International […], The Unified Modeling Language has been shown to be complex and difficult to learn. The difficulty of learning to build the individual diagrams in the UML, however, has received scant attention. In this article, we consider the case of the UML sequence diagram. Despite the fact that these diagrams are among the most frequently used in practice, they are difficult to learn to build. In this article, we consider the question of why these diagrams remain so difficult to learn to build. Specifically, we analyze the process of learning to build sequence diagrams in the context of cognitive complexity theory. Based on this analysis, and drawing on the theory of learner-centered design, we develop a set of recommendations for presenting the sequence diagram building task to the student analyst to reduce the complexity of learning how to build them. Keywords: cognitive complexity; learner-centered design; sequence diagrams; systems analysis and design, unified modeling language (UML)

INTRODUCTION The Unified Modeling Language (UML) offers a standard language specification to support an object-oriented approach to systems analysis and design. The use case is a text-based description defined in […], Use case modeling in the Unified Modeling Language (UML) is a popular text-based tool for systems analysis and design. Use cases can be used with or without supporting use case diagrams. This paper uses an experiment to explore the effectiveness of including a use case diagram with a set of use cases. The Cognitive Theory of Multimedia Learning is used to hypothesize that the use case diagram improves the effectiveness of use cases for novice users by providing visual cues aiding model viewers in selecting and integrating relevant information. The level of understanding developed by participants viewing either uses cases or use cases with a supporting use case diagram was measured using comprehension, retention, and problem solving tasks. Results showed that participants viewing the use cases with the supporting diagram developed a significantly higher level of understanding, as measured by performance on the problem solving task, than participants provided with use cases alone. This analysis suggests practitioners should consider combining a visual representation, such as a use case diagram, with text-based use cases to achieve higher levels of understanding in persons viewing these descriptions. Keywords: conceptual modeling; system analysis; unified modeling language (UML); use case modeling