Diagramas Uml

In: Computers and Technology

Submitted By jorgecc
Words 1330
Pages 6
Mg. Juan José Flores Cueto jflores@usmp.edu.pe Ing. Carmen Bertolotti Zuñiga cbertolotti@usmp.edu.pe INTRODUCCIÓN
UML (Unified Modeling Language) es un lenguaje que permite modelar, construir y documentar los elementos que forman un sistema software orientado a objetos. Se ha convertido en el estándar de facto de la industria, debido a que ha sido impulsado por los autores de los tres métodos más usados de orientación a objetos: Grady Booch, Ivar Jacobson y Jim Rumbaugh. En el proceso de creación de UML han participado, no obstante, otras empresas de gran peso en la industria como Microsoft, Hewlett-Packard, Oracle o IBM, así como grupos de analistas y desarrolladores. En UML 2.0 hay 13 tipos diferentes de diagramas. Para comprenderlos de manera concreta, a veces es útil categorizarlos jerárquicamente:  Diagramas de estructura enfatizan en los elementos que deben existir en el sistema modelado: 1. 2. 3. 4. 5. 6.  Diagrama de clases Diagrama de componentes Diagrama de objetos Diagrama de estructura compuesta (UML 2.0) Diagrama de despliegue Diagrama de paquetes

Diagramas de comportamiento enfatizan en lo que debe suceder en el sistema modelado: 7. Diagrama de actividades 8. Diagrama de casos de uso 9. Diagrama de estados

Diagramas de Interacción, un subtipo de diagramas de comportamiento, que enfatiza sobre el flujo de control y de datos entre los elementos del sistema modelado: 10. Diagrama de secuencia 11. Diagrama de comunicación 12. Diagrama de tiempos (UML 2.0) 13. Diagrama de vista de interacción (UML 2.0)

Un diagrama de clases es un tipo de diagrama estático que describe la estructura de un sistema mostrando sus clases, atributos y las relaciones entre ellos. Los diagramas de clases son utilizados durante el proceso de análisis y diseño de los sistemas, donde se crea el diseño conceptual…...

Similar Documents

Object-Relational Database Modeling Using Uml

...Running Head: OBJECT-RELATIONAL DATABASE MODELING USING UML Table of Contents Introduction……………………………………………………………………………………..4 Overview of ER Modeling and UML…………………………………………………………...4 UML Meta-model……………………………………………………………………………… 6 UML Components………………………………………………………………………………7 UML Data Profile……………………………………………………………………………….9 UML Diagrams……………………………………………………………………………….....10 UML Diagram Classification – Static, Dynamic, and Implementation…....................................12 4+1 View of UML Diagrams……………………………………………………………………13 Object-oriented Class Model and Relational Database Model..............................................…...14 Use of UML to develop Ontologies…………………………………………………………..…17 References……………………………………………………………………………………….19 Abstract The Unified Modeling Language (UML) is being used as the de-facto standard in the software industry. With the adoption of UML 2.0, the new enhancements allow this version to describe many of the elements found in today's software technology as well as Model Driven Architecture and Service-Oriented Architecture. Many existing software applications involve complex application layer implemented in object-oriented programming languages and at the same time use relational database systems as the back-end data store. Modeling the whole system in a consistent manner will help developers and end users better understand the application. The Unified Modeling Language (UML) is a standard language for modeling software and......

Words: 3708 - Pages: 15

Uml Case Diagrams

...invocation of the relationship or to indicate the primary actor within the use case. The arrowheads are typically confused with data flow and as a result I avoid their use.  System boundary boxes (optional). You can draw a rectangle around the use cases, called the system boundary box, to indicates the scope of your system. Anything within the box represents functionality that is in scope and anything outside the box is not. System boundary boxes are rarely used, although on occasion I have used them to identify which use cases will be delivered in each major release of a system. Figure 2 shows how this could be done.  Packages (optional). Packages are UML constructs that enable you to organize model elements (such as use cases) into groups. Packages are depicted as file folders and can be used on any of the UML diagrams, including both use case diagrams and class diagrams. I use packages only when my diagrams become unwieldy, which generally implies they cannot be printed on a single page, to organize a large diagram into smaller ones. Figure 3 depicts how Figure 1 could be reorganized with packages. In the example depicted in Figure 1 students are enrolling in courses with the potential help of registrars. Professors input the marks students earn on assignments and registrars authorize the distribution of transcripts (report cards) to students. Note how for some use cases there is more than one actor involved. Moreover, note how some associations have......

Words: 1128 - Pages: 5

Uml Modeling Language

...Unified Modeling Language (UML) UML stand for Unified Modeling Language and will forever change the world of modeling. UML was introduced more than 10 years ago in 1997 with the combined of three modeling advocates techniques. One of the first to adopt the system was The Object Management Group (OMG), the immediately set the stage for a new world of modeling with UML leading the way. The UML version 1.x was composed of 9 distinct but was break down into three types; they are structural, behavioral, and interaction. Of course no system was prefect there were issues as well that lead to more researches. First of UML is very complex and not users friendly and doubt it’ll get any less according to the article. They required experience user and have to get users to learn it language. (Erickson, J. (2008))   The impact on modeling that UML was seen years later. Now most of the businesses around the world use it in their daily working and communication. The systems on which these businesses run are based on languages, which make the design of these systems easier than it would have been otherwise. System design and engineering complexities are greatly reduced by use of diagrams that convey much more than reams of paper would consume by way of text. Also, these diagrams used in modeling help to design the system faster and quicker. Unified Modeling Language (UML) is now one such Modeling language, used to make designing of systems faster and quicker. The UML is thus a......

Words: 636 - Pages: 3

Using Uml to Model System

...INTRODUCTION This IDoc describes use of the Unified Modeling Language (UML) to model and document Accounting Information Systems (AIS). The objective of modeling AIS is multifaceted and can be to: visualize, understand, summarize, detail, analyze, design, develop, implement, operate, secure, control, or audit the AIS. UML is a powerful modeling language and technique for all of these modeling tasks and is more robust and semantically superior to the commonly used Structured Analysis (SA) modeling tools of flowcharts (FC), data flow diagrams (DFD), and entity-relationship diagrams (ERD). Dr. White suggests that using UML diagrams as a tool to document AIS is a viable alternative to the Structured Analysis’s diagrams of FC, DFD, and ERD. What follows in Section II is a brief comparison of the two alternative approaches to systems documentation: Structured Analysis (SA) and Object Orientation (OO). Section III presents the definition and description of the major structural and behavioral elements used in UML including classifiers, instances, relationships, collaborations, activities, interactions, and states. Section IV discusses the organization and presentation of UML documentation of AIS as a collection of diagrams and packages. Section V contains various UML diagrams of the business revenue cycle (system) as examples of how to use UML to document a business system. Section VI contains examples of UML models of two special systems of great importance to accountants:......

Words: 9812 - Pages: 40

Analisis Uml Pada Lbb Ssc

...TUGAS SYSTEM ANALYSIS AND DESIGN ANALISIS DAN PERANCANGAN BERBASIS OBJEK UNIFIED MODELING LANGUAGE (UML) DI LBB SONY SUGEMA COLLEGE “disusun untuk memenuhi salah satu tugas dari Mata Kuliah System Analysis and Design” Disusun oleh: Kelompok 3 Nahdiah Nur M. Wulan Ayu Mulika Putri S. Novia Damayanti A. Riyadi Adi P. (110400221) (110400235) (110400292) (110400295) (110400298) INSTITUT MANAJEMEN TELKOM Jl. Telekomunikasi no. 1 Bandung 2012  DFD LEVEL 0 1. SKENARIO / TUTORIAL Aktor Staff Pendaftaran Skenario Aktor hanya dapat mengakses Menu Kelola User, Kelola Kelas, Kelola Siswa, dan Kelola Absensi. Sebelum semua menu di atas dapat diakses oleh actor, actor harus melakukan login terlebih dahulu dengan memasukkan username & password yang telah terdaftar. Dalam semua menu tersebut, actor dapat melakukan tambah, ubah, dan hapus terhadap data-data yang telah disimpan sebelumnya Bagian Akademik Aktor hanya dapat mengakses Menu Kelola Try Out dan Kelola Pengiriman Hasil Try Out. Sebelum masuk ke menu tersebut, actor harus melakukan proses login terlebih dahulu. Jika login telah dinyatakan valid, maka kedua menu telah dapat diakses. Di Menu Kelola Try Out, actor dapat melakukan proses tambah, cari, ubah, cetak terhadap data-data try out seperti soal, kunci jawaban, dll. Sedangkan dalam Menu Kelola Pengiriman Hasil Try Out, actor dapat melakukan proses tambah, ubah, hapus, terhadap data-data hasil try out siswa dan juga melakukan kirim datadata hasil try out......

Words: 467 - Pages: 2

Diagrama Proyecto

...DATABASE AND CLIENT/SERVER APPLICATIONS Mid-Semester Exam Name: avalos demetrio maria guadalupe INSTRUCTIONS 1. Use the word processor on the computer to fill in this assessment. 2. Start by inserting your name in the space above. 3. Before you begin answering these questions, save this file using the required file name format: “<YourStudentID> Mid_Semester_Exam.doc” where <YourStudentID> is your StudentID and there is a blank between it and the Mid_Semester_Exam. When you are finished with the assessment, save the document again and then upload it to the LMS. 4. Click the Choose File button. 5. Locate the file for attachment. 6. Once the file is attached, click Upload File. ASSESSMENT QUESTIONS 1. Design a customer database. It should support listing: • customers with their name, a customer identifier, a billing address (assume U.S. addresses), a shipping address that may be different, a contact with associated phone number and email address. • orders including an order number, customer id, order date, product identifiers with quantity and price at order time. • products with a name, identifier, description, current price, and weight (we will not worry about other size measures that might be useful in shipping). • inventory of products in stock including where in the warehouse it is (Aisle, Shelf, Bin), and quantity there. Draw an entity relationship diagram in third normal form for this database. You may use......

Words: 954 - Pages: 4

An Experimental Comparison of Er and Uml Class Diagrams for Data Modelling

...Empir Software Eng (2010) 15:455–492 DOI 10.1007/s10664-009-9127-7 An experimental comparison of ER and UML class diagrams for data modelling Andrea De Lucia · Carmine Gravino · Rocco Oliveto · Genoveffa Tortora Published online: 11 December 2009 © Springer Science+Business Media, LLC 2009 Editor: Erik Arisholm Abstract We present the results of three sets of controlled experiments aimed at analysing whether UML class diagrams are more comprehensible than ER diagrams during data models maintenance. In particular, we considered the support given by the two notations in the comprehension and interpretation of data models, comprehension of the change to perform to meet a change request, and detection of defects contained in a data model. The experiments involved university students with different levels of ability and experience. The results demonstrate that using UML class diagrams subjects achieved better comprehension levels. With regard to the support given by the two notations during maintenance activities the results demonstrate that the two notations give the same support, while in general UML class diagrams provide a better support with respect to ER diagrams during verification activities. Keywords Controlled experiments · Entity-relation diagrams · UML class diagrams · Design notations · Comprehension · Maintenance · Verification The work described in this paper is supported by the project METAMORPHOS (MEthods and Tools for migrAting software systeMs towards...

Words: 16567 - Pages: 67

Object Oriented Programming and Uml

...Object Oriented Programming and UML Implementation modeling is “the development stage for adding fine details to a model that transcend languages. Implementation modeling is the immediate precursor to the actual implementation.”(Blaha & Rambaugh, 2005) Implementation modeling uses the following four steps: fine-tune classes, fine-tune generalizations, realize associations, and preparing for testing. Steps one and two are driven by the theory of transformations. Transformations “is a mapping from the domain of models to the range of models”(Blaha & Rambaugh, 2005) The first step in implementation modeling is fine-tuning classes. It is best to fine-tune classes before writing code because it will help to simplify development or to improve performance. If for some reason you have to alter the design first consider the following possibilities; partition a class, merge classes, partition or merge attributes, or promote an attribute or demote a class. The next step in implementation modeling is fine-tuning generalizations. It is helpful to remove generalization or to add one prior to coding. The third step is realizing associations. This is what holds the class model together by providing paths between objects. The final step is testing. “Testing is a quality assurance mechanism for catching residual errors.” (Blaha & Rambaugh, 2005) It also measures the quality of your software. “Implementation is the final development stage that addresses the...

Words: 319 - Pages: 2

History of Uml

...known for two of the most popular object-oriented modeling approaches. The first one being Rumbaugh’s object modeling technique and the other being Grady Booch's object oriented design. Next they were assisted by Ivar Jacobson who developed object-oriented software engineering and Jaconson joined Rational shortly. The three of them together at Rational developed the unified method version 0.9 in 1996. The aim is not to create a new series of symbols but to but to adapt, expand, and simplify the existing and widely used object oriented methods. Other well-known companies started to join them to further the development of unified method. In 1997, they developed version 1.0 which was then renamed to unified modeling language (UML) and the latest version UML 2.5 was released in October 2012....

Words: 269 - Pages: 2

Uml是Unified Modeling Language的簡稱

...UML是Unified Modeling Language的簡稱,中譯為「統一塑模語言」。其中: Unified:UML是一種標準語言,廣泛運用於全世界。 Modeling:UML用途在於塑模(Modeling),也就是畫軟體藍圖。 Language:UML是一種塑模語言,而非程式語言或標示語言。 也就是說,UML是軟體系統發展人員用以建造模型,而這些模型使得工作團隊能夠:將系統具象化(Visualization)、將系統結構及行為規格化(Specification)、建構(Construction)系統、以及記錄(Documentation)發展系統過程中之各項決策。 什麼是塑模? 作曲家會將其腦袋中的旋律譜成樂曲,建築師會將其設計之建築物畫成藍圖,行銷廣告人員會將其創意製作成簡報;這些樂曲、藍圖及簡報就是模型(Model),而建構這些模型的過程就稱為塑模(Modeling)。 軟體開發如同音樂譜曲及建築設計,其過程中也必須將需求、分析、設計、實作、佈署等各項工作流程之構想與結果予以呈現,這就是軟體系統之塑模。 為什麼要塑模? 絕大部份的音樂演奏都需要樂譜(除了少數即性式表演外)! 絕大部份的建築施工都需要藍圖(除非要蓋的是一間狗屋)! 同樣的,所有軟體系統的建構最好都有適當的分析設計藍圖,因為軟體開發的過程絕對不是任意的、隨性的、且戰且走的、天馬行空的。 UML在軟體塑模中所扮演的角色是什麼? 1.軟體發展之方法論中包含了程序(Process)及表示法(Notation)兩個部份,其中: 程序指的是系統開發的流程,例:瀑布模式、漸增模式、擴展模式、雛型模式、螺旋模式等。 2.表示法指的是建構軟體模型中所會用到之符號及規則。 3.UML所涵蓋的內容是表式法而非程序,UML是與程序無關的(Process Independent),也就是說,無論以任何程序來開發軟體系統,都可以使用UML來建構軟體模型。 UML與物件導向方法之關係 1.UML之訂定與物件導向方法的確有非常密切之關係。 2.UML中的各種符號及規則與物件導向語言(Java,C++)之結構有完整對應。 但是,UML絕對不僅限用在物件導向軟體開發,UML中有些概念與圖形甚至可說是與物件導向無關 例:Use Case Diagram及Statechart Diagram 因此,軟體開發時無論是否採用物件導向方法,UML都是適用的。 UML的重要性 1.UML是OMG公佈的官方標準。 2.UML已為全世界軟體業者所廣泛採用,各大軟體公司(Microsoft、IBM、Oracle等) 3.在其產品中均支援UML。 4.UML的應用領域越來越廣(資料庫設計、韌體設計、資訊管理等)。 UML的現行版本 UML現行版本為1.5版(http://www.omg.org/technology/documents/formal/uml.htm),但2.0版將近完成,應會在短期內正式公佈(http://www.omg.org/uml)。 UML的內容到底是什麼? UML對於軟體開發相關人員而言,其實就只是一組符號及規則,其中包括: 1.Basic Building Blocks(都有其相對的符號) (1)......

Words: 5884 - Pages: 24

Which of the Following Is Not Part of a Uml Diagram

...HELPIDO.COM -------------------------------------------------------------------------- FOLLOW THIS LINK TO GET THE TUTORIAL http://helpido.com/which-of-the-following-is-not-part-of-a-uml-diagram/ ------------------------------------------------------------------------------ 1. (TCO 2) Which of the following is not part of a UML diagram? (Points : 2) Object Name Attribute Method All of the above 2. (TCO 2) Java, C#, and C++ all allow for the use of comments. Which of the following represent(s) valid comments in these three languages? (Points : 2) */ Comment */ / Comment / – Comment – All of the above None of the above 3. (TCO 2) Attributes represent the _____ of an object because they store information about that object. (Points : 2) state behaviors size accessibility 4. (TCO 2) If a programmer explicitly defines a constructor that accepts parameters, he or she should also define a _____ version, as a best practice. (Points : 2) private public static default None of the above 5. (TCO 2) Encapsulation _____ and provides _____ for program components. (Points : 2) protects an object’s data from unwanted modifications; independence protects an object’s methods from unwanted modifications; independence provides universal access to an object’s attributes; a stable implementation provides universal access to an object’s methods; a stable implementation None of the above 6. (TCO...

Words: 442 - Pages: 2

Uml Term Papaer on Domain Analysis

...LOVELY PROFESSIONAL UNIVERSITY TERM PAPER ON Extending UML to Support Domain Analysis SUBMITTED TO:- SUBMITTED BY:- Mr. SANDEEP SINGH AKANSHU KUMAR Reg No:-11112286 ROLL No:- A21 SECTION:- K1107 Abstract:- The process of modelling and developing commonality and variability for system families should be supported by suitable methods and notations. The object-oriented methods and their notations, which are used at present, focus on the development of a single system at a time. In this paper we analyse feature models as a representation of the common parts and variants contained in a system family, and propose using a feature diagram as a basic representation of commonality, variability and dependencies. We examine various approaches to customizing the standard modelling language UML to model system families and propose how to extend the UML for the purposes of modelling variants in object-oriented analysis and design techniques. We recommend the use of UML standard lightweight extensibility mechanisms (stereotypes combined with tagged values) without changing the UML metamodel. This enables us to join the advantages of feature models with UML and provides the traceability of a concept throughout......

Words: 3255 - Pages: 14


...Redis está escrito en ANSI C y funciona en la mayoría de sistemas POSIX como Linux, BSD, Mac OS X. Redis es software libre bajo licencia BSD. [35] *  Redis se destaca por ser una base de datos con un rendimiento muy elevado, esto es porque se define como una base de datos en memoria con persistencia para datos (que puede ser desactivada).  Como trabaja Redis. En sus raíces, Redis es un servidor de un solo subproceso. Esto significa Que un solo hilo lee conexiones entrantes utilizando un paradigma basado en eventos tales como  consultas. Cuando ocurre un evento específico en un descriptor de archivo, los procesa y escribe de nuevo las respuestas. En el siguiente diagrama de secuencia UML muestra cómo se procesa la orden recibida por el cliente internamente por Redis: [35] Figura 12. Diagrama UML del funcionamiento interno de redis. Las solicitudes se gestionan mediante comandos. Los cuales se pueden leer en la tabla de comandos de acuerdo a los puertos del controlador de comandos y de ahí se invoca para realizar la acción deseada. Funcionamiento Redis: Redis más allá de ser una simple base de datos clave-valor cuenta con una gran cantidad de funcionalidad que la diferencias de las bases de datos convencionales. [36] * Administración de conexiones al servidor (incluyendo autenticación) * Operaciones con cadenas (tipo clave-valor) * Operaciones sobre las claves (TTL, renombrado, expiración, tamaño total) * Operaciones......

Words: 733 - Pages: 3

Diagrama de Lexis

...Parcial diagrama de Lexis CAMILA AMAYA PAULA TOVAR VANESA BUITRAGO DANIEL ORTIZ PROFESOR ÁLVARO SUAREZ BOGOTÁ DC PONTIFICIA UNIVERSIDAD JAVERIANA FACULTAD DE CIENCIAS ECONOMICAS Y ADMINISTRATIVAS CARRERA DE ECONOMIA CONTEXTO BOGOTANO Antes de comenzar con nuestro trabajo, es importante explicarle al lector que el presente documento trata de contextualizar y reunir datos que le permitan acercarse un poco más a la situación actual de Bogotá. Este trabajo entonces es quizás un poco un análisis coyuntural y no histórico, tratando los temas que representan mayor importancia para la capital del país. Comencemos con un análisis general de la composición actual de Bogotá. Nuestra capital cuenta en el momento aproximadamente con 7.029.928 de habitantes, ubicada en el Centro del país, en la cordillera oriental, ramal de los Andes americanos y pertenecientes al altiplano cundiboyacense, la capital del país conocida como la Sabana de Bogotá, tiene una extensión aproximada de 33 kilómetros de sur y norte y 16 kilómetros de oriente a occidente. Descansa sobre la extensión noroccidental de la cordillera de Los Andes en una sabana con gran variedad de climas, tipos de suelos, cuerpos de aguas y otras formaciones naturales. Como Bogotá está ubicada entre montañas, estas sirven como barrera natural que restringe el flujo de humedad, influyendo en el régimen de lluvias. La temperatura varía de acuerdo con los meses del año, en diciembre, enero y marzo son altas, al......

Words: 3636 - Pages: 15

Sdlc + Uml Introduction (Systems Analysis and Design)

...SDLC Intro Systems Development Life Cycle, or SDLC, is the entire process of building, deploying, using, and updating an information system (Object-Oriented Analysis and Design with the Unified Process – Satzinger, Jackson, and Burd). It is a conceptual model that is used in project management and describes the stages that are comprised within an information system. One of the oldest models of SDLC is the Waterfall Approach. It is a series of junctures in which the output of each juncture becomes the input for the next. The 7 phases involved in this model are Project Planning, Systems Analysis, Systems Design, Implementation, Integration/Testing, Deployment, and Maintenance. Project Planning establishes the objectives and goals of the intended project. It also determines how to accomplish the project in the best possible way. Systems Analysis filters project goals into well-defined functions and operation of the intended project. This phase analyzes end-user information needs. Systems Design defines desired features and operations in detail. It includes screen layouts, business rules, process diagrams, pseudo code and other documentation. Implementation deals with the actual development of the system where it is built and programmed. Integration/Testing is the phase where the system is put into test. It is checked for errors, bugs, and interoperability. Deployment Phase is the final stage of the initial development. The system is carried out and put into......

Words: 447 - Pages: 2