J. Rumbaugh’s scientific contributions

... The (early, 1991) CDIF standard was based on a three-level hierarchy (as summarised more recently in [6]). A few years later, suggestions by Carmichael [7] and Henderson-Sellers [8] led to the proposal to use this approach to bring together the plethora of object-oriented modelling notations then extant [9,10]. The first standard to utilise this idea of metamodelling for object technology standards was the UML [1], standardised by the Object Management Group (OMG), which introduced the four-level hierarchy of Fig. 1, with an expressed aim of providing an infrastructure ''to support the creation, manipulation and interchange of meta models'' [11]. ...

Reference:

Ontological and linguistic Metamodelling revisited: A language use approach

... However, recognizing that screening twice may be infeasible, PCORI softened the IOM requirement of dual review (IOM standard 3.3.3) [8] , stating ''factchecking may be sufficient'' (PCORI SR-1 standard, p. 5) [9]. The long-term goal of our programmatic research is to support systematic reviewers by reducing the burden associated with screening citations and by offering guidance as to which studies to reconsider based on their judgments, effectively offering quality assurance or 'fact-checking.' ...

Reference:

Feature Engineering and a Proposed Decision-Support System for Systematic Reviewers of Medical Evidence

... Visual Programming [7,31] or Graphical Programming uses richer representation and interaction to define software behavior. Here, the developer uses a visual representation, e.g., following the visual models of the UML [40], to create software. The visual representation can provide greater flexibility than text because it is not constrained to be strictly sequential and is often supported through direct manipulation for effective interaction. ...

Reference:

Extending Jupyter with Multi-Paradigm Editors

... 17, No. 1, Mes: Enero, 2024, Pág. 32-41 Esta Además, se siguieron las etapas de desarrollo de software (Jacobson et al., 2000), (Canós et al., 2003): ...

Reference:

UCIcrono: a mobile application to explore the history of the University of Informatic Sciences

... A partir del paradigma orientado a objetos han surgido diferentes métodos y lenguajes de especificación. De todos modos, desde 1997, el lenguaje UML (Booch, Rumbauch, & Jacobson, 1998) constituye el estándar para modelar sistemas. En la próxima sección, introducimos brevemente UML. ...

Reference:

Tecnología de la información en las organizaciones

... For practical consideration, it is beneficial to begin with general natural language requirements and refine them into graphical notations, such as Unified Model Language (UML) diagrams. 33,34 However, the original requirement within the specification must always be bidirectionally linked to allow traceability. It should be possible to describe and follow the life of requirements in all directions. ...

Reference:

Guideline for Software Life Cycle in Health Informatics

... As described in [WILL95] scenarios represent a common point of departure between object-oriented requirements or design models and SPE models. Scenarios may be represented in a variety of ways [JACO92], [WILL94]. ...

Reference:

Performance Evaluation of a Distributed Software Architecture

... In the HCI community, they are used to elaborate on usability issues [7,16,26] and to help the expression and understanding of the goals of the design [12,14,22]. In the SE community, scenarios serve mainly as a front end to object oriented design [3,20,23,24,27]. Scenarios can be expressed in various ways : text, animation, prototypes, etc. but textual ones are recommended by several authors [5,10,13,16,18]. ...

Reference:

Describing Business Processes with a Guided Use Case Approach

... Ziel ist die Generierung der Artefakte eines Softwaresystems aus formalen Modellen und die damit einhergehen-de "Automatisierung in der Softwareherstellung"(Pietrek & Trompeter 2007: 11). Modeldriven Engineering entstand um die Jahrtausendwende aus dem Computer-Aided Software Engineering (CASE, Fuggetta 1993: 25-38) als Weiterentwicklung objektorientierter Modellierungswerkzeuge. Dazu zählen insbesondere die Ansätze Object-Modeling Technique (OMT,Rumbaugh et al. 1991), Object-Oriented Design (OOD, Booch 1994) und Object-Oriented Software Engineering (OOSE, Jacobson et al. 1992, die als Unified Modeling Language (UML,Rumbaugh, Jacobson & Booch 1997) zusammengeführt wurden. Seitdem wird UML als Standard durch die OMG weiterentwickelt (OMG 2013b) und findet breite Verwendung in der Softwaretechnik. ...

Reference:

Barrierefreiheit im virtuellen Raum - benutzungszentrierte und modellgetriebene Entwicklung von Weboberflächen

... UML-ADs are a specification of UML [88] that focuses on the representation of workflows. There, control flows are represented by activities, decision nodes, gates, and directed control flow edges (Req. 1 (PD), see Figure 7). ...

Reference:

Towards Flexible Control of Production Processes: A Requirements Analysis for Adaptive Workflow Management and Evaluation of Suitable Process Modeling Languages