January 1994
·
9 Reads
·
6 Citations
This page lists works of an author who doesn't have a ResearchGate profile or hasn't added the works to their profile yet. It is automatically generated from public (personal) data to further our legitimate goal of comprehensive and accurate scientific recordkeeping. If you are this author and want this page removed, please let us know.
January 1994
·
9 Reads
·
6 Citations
January 1993
·
15 Reads
·
6 Citations
January 1993
·
13 Reads
·
1 Citation
947 Reads
·
38 Citations
Traducción de: The Unified Modeling Language User Guide En 1997, James Rumbaugh, Ivar Jacobson y Grady Booch dieron a conocer el UML (Unified Modeling Language), que rápidamente se convirtió en una notación estándar para el modelado de sistemas computacionales. En esta obra, los creadores de UML ofrecen una guía tutorial de los principales conceptos de este lenguaje de programación y de la ingeniería de software.
274 Reads
Traducción de: The Unified Modeling Language Reference Manual En 1997, James Rumbaugh, Ivar Jacobson y Grady Booch dieron a conocer el UML (Unified Modeling Language), que rápidamente se convirtió en una notación estándar para el modelado de sistemas computacionales. En esta obra, los creadores de UML ofrecen una serie de artículos en que, alfabéticamente, se explican los principales conceptos de este lenguaje de programación y de la ingeniería de software.
134 Reads
·
90 Citations
Existe una edición impresa con el título: The Unified Modeling Language Reference Manual En 1997, James Rumbaugh, Ivar Jacobson y Grady Booch dieron a conocer el UML (Unified Modeling Language), que rápidamente se convirtió en una notación estándar para el modelado de sistemas computacionales. En esta obra, los creadores de UML ofrecen una serie de artículos en que, alfabéticamente, se explican los principales conceptos de este lenguaje de programación y de la ingeniería de software. En el presente disco compacto se incluyen también las especificaciones semánticas y de notación para UML que establece el Object Management Group (OMG) para el desarrollo de software basado en este lenguaje. Contiene los documentos del manual para UML y las especificaciones del OMG, así como los archivos de texto que explica su utilización y html de índices de otros libros de la serie Object Technology.
21 Reads
·
529 Citations
18 Reads
·
12 Citations
35 Reads
·
12 Citations
6 Reads
·
9 Citations
... 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]. ...
January 1994
... 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.' ...
October 1994
ACM SIGPLAN Notices
... 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. ...
July 2004
... Metodología RUP La metodología RUP es un lenguaje basado en casos, centrado en la arquitectura, iterativo e incremental. El proceso unificado se repite en una serie de ciclos, donde cada ciclo forma una versión del sistema (Jacobson, Booch y Rumbaugh, 2000;Castro, Cervantes y Velazco, 2016). Un ciclo en RUP consta de cuatro fases discretas en los procesos de desarrollo de software, que son: • Comienzo. ...
... 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. ...
January 1998
... 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. ...
January 1999
... 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]. ...
... 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]. ...
... 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. ...
... 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). ...
January 1996