Learn More
Flow models underlie popular programming languages and many graphical behavior specification tools. However, their semantics is typically ambiguous, causing miscommunication between modelers and unexpected implementation results. This article introduces a way to disambiguate common flow modeling constructs, by expressing their semantics as constraints on(More)
This is the fourth in a series introducing the activity model in the Unified Modeling Language, version 2 (UML 2), and how it integrates with the action model [1]. The first article gives an overview of activities and actions [2], while the second two cover actions generally and control nodes [3][4]. The remainder of the series elaborates other specific(More)
This article describes activity modeling as specified by the Systems Modeling Language (as specified by the SysML Merge Team, http://doc.omg.org/ad/2006-02-01, February 2006) and the finalization of the Unified Modeling Language version 2 (UML 2). It reviews and updates an earlier proposed alignment between Enhanced Functional Flow Block Diagrams (EFFBD),(More)
This paper presents a revised and unified view of the NIST Core Product Model (CPM) [1; 2] and the NIST Open Assembly Model (OAM) [3]. The CPM provides a base-level product model that is not tied to any vendor software; open; non-proprietary; simple; generic; expandable; independent of any one product development process; and capable of capturing the(More)
The composition model in the Unified Modeling Language, version 2 (UML 2), is a major upgrade to the familiar " black diamond " composition of earlier versions. It supports connections between parts at the same level of decomposition, in addition to the usual part-whole associations. Complex networks of entities can be represented within a single class,(More)