DOCSLIB.ORG

Unified Modeling Language (UML) What Is UML? Object Management

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Unified Modeling Language (UML) What Is UML? Object Management Unified Modeling Language (UML) Object Management Group (OMG) ● An international, open membership, not-for-profit technology standards consortium that was founded in 1989. https://www.omg.org/ Péter Jeszenszky ● Standards: Faculty of Informatics, University of Debrecen – MetaObject Facility (MOF) https://www.omg.org/mof/ [email protected] – Model Driven Architecture (MDA) https://www.omg.org/mda/ – Systems Modeling Language (SysML) Last modified: April 11, 2021 https://www.omg.org/spec/SysML/ – Unified Modeling Language (UML) https://www.uml.org/ – XML Metadata Interchange (XMI) https://www.omg.org/spec/XMI/ – … 3 What is UML? History ● „The OMG's Unified Modeling Language (UML) ● UML is based on other object-oriented methodologies for helps you specify, visualize, and document software systems development: models of software systems, including their – Booch (Grady Booch) structure and design [...]. (You can use UML for – OMT (Object-Modeling Technique) (James E. Rumbaugh et al.) business modeling and modeling of other non- – OOSE (Object-Oriented Software Engineering) (Ivar Jacobson) software systems too.)” ● „Three Amigos”: Booch, Jacobson, and Rumbaugh – UML were developed under their leadership. – See: Introduction To OMG's Unified Modeling ● Language See also: https://www.omg.org/UML/what-is-uml.htm – The Unified Modeling Language – Versions of UML Versions of UML https://www.uml-diagrams.org/ 2 4 Current Standards XML Metadata Interchange (XMI) ● OMG Unified Modeling Language (OMG UML) Version 2.5.1. ● An XML format for metadata exchange between December 2017. https://www.omg.org/spec/UML/2.5.1/ applications. ● Diagram Definition (DD) Version 1.1. June 2015. https://www.omg.org/spec/DD/1.1/ ● Most often, it is used for the exchange of UML ● XML Metadata Interchange (XMI) Version 2.5.1. June 2015. models, however, it can be used to serialize any https://www.omg.org/spec/XMI/2.5.1/ type of metadata whose metamodel can be ● OMG Meta Object Facility (MOF) Core Specification Version expressed in MOF. 2.5.1. November 2016. https://www.omg.org/spec/MOF/2.5.1/ ● Object Constraint Language Version 2.4. February 2014. https://www.omg.org/spec/OCL/2.4/ 5 7 Object Constraint Language (OCL) Model ● A formal language used to describe expressions on UML models. ● A model is a description of a system, where “system” is meant in ● OCL is not a programming language, instead, it is a modeling the broadest sense and may include not only software and language. hardware but, for example, organizations and processes. – OCL expressions are not directly executable. ● It describes the system from a certain viewpoint for a certain ● OCL expressions are guaranteed to have no side effects. category of stakeholders (e.g., designers, users, or customers of the system) and at a certain level of abstraction. ● OCL is a typed language so that each OCL expression has a type. ● A model is complete in the sense that it covers the whole system, ● OCL can be used for a number of different purposes: although only those aspects relevant to its purpose (i.e., within – As a query language. the given level of abstraction and viewpoint) are represented in – To specify invariants on classes and types in the class model. the model. – To describe pre- and post conditions on operations. – See: OMG Unified Modeling Language (OMG UML) Version 2.5.1. – … December 2017. https://www.omg.org/spec/UML/2.5.1/ 6 8 Metamodell Syntax (1) ● A metamodel is a model of a model. ● Linguistics: – ● “the way in which linguistic elements (such as words) are put In UML, a metamodel is a model used to model together to form constituents (such as phrases or clauses)” itself. – “the part of grammar dealing with this” – It can is used to model itself as well as other ● See: https://www.merriam-webster.com/dictionary/syntax models and metamodels. ● Programming languages: – For example, the MOF model is a metamodel. – “The syntax of a programming language describes the proper form of its programs […].” ● See: Alfred V. Aho, Monica S. Lam, Ravi Sethi, Jeffrey D. Ullman. Compilers: Principles, Techniques, & Tools. 2nd ed. Addison Wesley, 2006. 9 11 Metaclass Syntax (2) ● A metaclass is a class in an object oriented programming language ● Abstract syntax: a description of the structure whose instances are classes. of language elements that is independent of – Python: ● PEP 3115 – Metaclasses in Python 3000 https://www.python.org/dev/peps/pep-3115/ any particular representation. ● Python 3.9.2 documentation – Data model – Metaclasses https://docs.python.org/3/reference/datamodel.html#metaclasses ● Concrete syntax: a mapping of the abstract – Groovy: syntax to a particular (machine) representation. ● The Groovy programming language – Runtime and compile-time metaprogramming http://groovy-lang.org/metaprogramming.html ● groovy.lang.MetaClass http://docs.groovy-lang.org/latest/html/api/groovy/lang/MetaClass.html – UML: classes in a metamodel are called metaclasses (examples of UML metaclesses include Element, Classifier, …). 10 12 Syntax (3) Semantics (1) ● Abstract syntax: ● Concrete syntax: ● Definition (programming languages): – Infix notation: – “The syntax of a programming language describes operator ● (1 + 2) * 3 the proper form of its programs, while the semantics of the language defines what its programs mean; – Prefix notation: that is, what each program does when it executes.” ● arg1 arg2 (* (+ 1 2) 3) ● See: Alfred V. Aho, Monica S. Lam, Ravi Sethi, Jeffrey D. – Postfix notation: Ullman. Compilers: Principles, Techniques, & Tools. 2nd ed. Addison Wesley, 2006. ● ((1 2 +) 3 *) 13 15 Syntax (4) Semantics (2) ● The abstract syntax of UML is specified using a ● The following sentence demonstrates the UML model called the UML metamodel. difference between syntax and semantics: – „Colorless green ideas sleep furiously.” ● See: Noam Chomsky. Syntactic Structures. Mouton & Co., 1957. ● The sentence is grammatically (syntactically) correct, however, it is meaningless. 14 16 Domain-specific languages Meta Object Facility (MOF) (2) ● Domain-specific language (DSL): a computer ● MOF is a domain-specific language for defining language that's targeted to a particular kind of metamodels. problem, rather than a general purpose – The MOF model is used to model itself as well as language that's aimed at any kind of software other models (e.g., UML and CWM). problem. – Can be used to model arbitrary metadata (for – Examples: BibTeX/LaTeX, CSS, DOT (Graphviz), example, software configuration or requirements Gradle DSL, Make, PlantUML, SQL, … metadata). – See: Martin Fowler. DomainSpecificLanguage. https://martinfowler.com/bliki/DomainSpecificLangu age.html 17 19 Meta Object Facility (MOF) (1) Meta Object Facility (MOF) (3) ● The Meta Object Facility (MOF) provides an open ● UML metamodel: and platform-independent metadata management – A UML model that specifies the abstract syntax of framework and associated set of metadata services UML. to enable the development and interoperability of model and metadata driven systems. – This metamodel uses constructs from a constrained subset of UML that is identified in the MOF – Examples of systems that use MOF include modeling specification and used for constructing metamodels. and development tools, data warehouse systems, metadata repositories, etc. ● See: OMG Meta Object Facility (MOF) Core Specification, Version 2.5.1 18 20 The Four-Layer Metamodel Layered Metamodel Architecture Hierarchy (UML 2.4.1) ● ● When dealing with defining languages there are Meta-metamodel (M3): – The primary responsibility of this layer is to define the language for specifying a metamodel. generally three layers that always have to be – A meta-metamodel is typically more compact than a metamodel that it describes. – It is generally desirable that related metamodels and meta-metamodels share common design taken into account: philosophies and constructs. ● Metamodel (M2): – The language specification, or the metamodel. – A metamodel is an instance of a meta-metamodel, meaning that every element of the metamodel is an instance of an element in the meta-metamodel. – The user specification, or the model. – The primary responsibility of the metamodel layer is to define a language for specifying models. ● Model (M1): – Objects of the model. – A model is an instance of a metamodel. – The primary responsibility of the model layer is to define languages that describe semantic domains, i.e., to allow users to model a wide variety of different problem domains, such as software, business processes, and requirements. ● Run-time instances (M0): – Contains the run-time instances of model elements defined in a model. 21 23 Layered Metamodel Architecture Layered Metamodel Architecture ● Metamodeling: ● What is a metamodel in one case can be a model in another case, and this is what happens with UML and MOF. metamodel Class Association – Both UML and MOF are language specifications (metamodels) from which users can define their own «instanceOf» models. «instanceOf» «instanceOf» – From the perspective of MOF, however, UML is viewed as a user (i.e., the members of the OMG that have car model Person Car * developed the language) specification that is based on MOF as a language specification (metamodel). 22 24 The Four-Layer Metamodel Abstract and Concrete Syntax Hierarchy (UML 2.4.1) M3 (MOF) Class ● Example: {subsets owner} + annotatedElement Element + owningElement «instanceOf» * 0..1 «instanceOf» «instanceOf» M2 (UML) classifier Abstract Attribute Class Instance syntax «instanceOf» «instanceOf»
Load more

Recommended publications
  • Using the UML for Architectural Description?
    Using the UML for Architectural Description? Rich Hilliard Integrated Systems and Internet Solutions, Inc. Concord, MA USA [email protected] Abstract. There is much interest in using the Unified Modeling Lan- guage (UML) for architectural description { those techniques by which architects sketch, capture, model, document and analyze architectural knowledge and decisions about software-intensive systems. IEEE P1471, the Recommended Practice for Architectural Description, represents an emerging consensus for specifying the content of an architectural descrip- tion for a software-intensive system. Like the UML, IEEE P1471 does not prescribe a particular architectural method or life cycle, but may be used within a variety of such processes. In this paper, I provide an overview of IEEE P1471, describe its conceptual framework, and investigate the issues of applying the UML to meet the requirements of IEEE P1471. Keywords: IEEE P1471, architectural description, multiple views, view- points, Unified Modeling Language 1 Introduction The Unified Modeling Language (UML) is rapidly maturing into the de facto standard for modeling of software-intensive systems. Standardized by the Object Management Group (OMG) in November 1997, it is being adopted by many organizations, and being supported by numerous tool vendors. At present, there is much interest in using the UML for architectural descrip- tion: the techniques by which architects sketch, capture, model, document and analyze architectural knowledge and decisions about software-intensive systems. Such techniques enable architects to record what they are doing, modify or ma- nipulate candidate architectures, reuse portions of existing architectures, and communicate architectural information to others. These descriptions may the be used to analyze and reason about the architecture { possibly with automated support.
    [Show full text]
  • The Guide to Succeeding with Use Cases
    USE-CASE 2.0 The Guide to Succeeding with Use Cases Ivar Jacobson Ian Spence Kurt Bittner December 2011 USE-CASE 2.0 The Definitive Guide About this Guide 3 How to read this Guide 3 What is Use-Case 2.0? 4 First Principles 5 Principle 1: Keep it simple by telling stories 5 Principle 2: Understand the big picture 5 Principle 3: Focus on value 7 Principle 4: Build the system in slices 8 Principle 5: Deliver the system in increments 10 Principle 6: Adapt to meet the team’s needs 11 Use-Case 2.0 Content 13 Things to Work With 13 Work Products 18 Things to do 23 Using Use-Case 2.0 30 Use-Case 2.0: Applicable for all types of system 30 Use-Case 2.0: Handling all types of requirement 31 Use-Case 2.0: Applicable for all development approaches 31 Use-Case 2.0: Scaling to meet your needs – scaling in, scaling out and scaling up 39 Conclusion 40 Appendix 1: Work Products 41 Supporting Information 42 Test Case 44 Use-Case Model 46 Use-Case Narrative 47 Use-Case Realization 49 Glossary of Terms 51 Acknowledgements 52 General 52 People 52 Bibliography 53 About the Authors 54 USE-CASE 2.0 The Definitive Guide Page 2 © 2005-2011 IvAr JacobSon InternationAl SA. All rights reserved. About this Guide This guide describes how to apply use cases in an agile and scalable fashion. It builds on the current state of the art to present an evolution of the use-case technique that we call Use-Case 2.0.
    [Show full text]
  • OMG Systems Modeling Language (OMG Sysml™) Tutorial 25 June 2007
    OMG Systems Modeling Language (OMG SysML™) Tutorial 25 June 2007 Sanford Friedenthal Alan Moore Rick Steiner (emails included in references at end) Copyright © 2006, 2007 by Object Management Group. Published and used by INCOSE and affiliated societies with permission. Status • Specification status – Adopted by OMG in May ’06 – Finalization Task Force Report in March ’07 – Available Specification v1.0 expected June ‘07 – Revision task force chartered for SysML v1.1 in March ‘07 • This tutorial is based on the OMG SysML adopted specification (ad-06-03-01) and changes proposed by the Finalization Task Force (ptc/07-03-03) • This tutorial, the specifications, papers, and vendor info can be found on the OMG SysML Website at http://www.omgsysml.org/ 7/26/2007 Copyright © 2006,2007 by Object Management Group. 2 Objectives & Intended Audience At the end of this tutorial, you should have an awareness of: • Benefits of model driven approaches for systems engineering • SysML diagrams and language concepts • How to apply SysML as part of a model based SE process • Basic considerations for transitioning to SysML This course is not intended to make you a systems modeler! You must use the language. Intended Audience: • Practicing Systems Engineers interested in system modeling • Software Engineers who want to better understand how to integrate software and system models • Familiarity with UML is not required, but it helps 7/26/2007 Copyright © 2006,2007 by Object Management Group. 3 Topics • Motivation & Background • Diagram Overview and Language Concepts • SysML Modeling as Part of SE Process – Structured Analysis – Distiller Example – OOSEM – Enhanced Security System Example • SysML in a Standards Framework • Transitioning to SysML • Summary 7/26/2007 Copyright © 2006,2007 by Object Management Group.
    [Show full text]
  • UML Tutorial: Part 1 -- Class Diagrams
    UML Tutorial: Part 1 -- Class Diagrams. Robert C. Martin My next several columns will be a running tutorial of UML. The 1.0 version of UML was released on the 13th of January, 1997. The 1.1 release should be out before the end of the year. This col- umn will track the progress of UML and present the issues that the three amigos (Grady Booch, Jim Rumbaugh, and Ivar Jacobson) are dealing with. Introduction UML stands for Unified Modeling Language. It represents a unification of the concepts and nota- tions presented by the three amigos in their respective books1. The goal is for UML to become a common language for creating models of object oriented computer software. In its current form UML is comprised of two major components: a Meta-model and a notation. In the future, some form of method or process may also be added to; or associated with, UML. The Meta-model UML is unique in that it has a standard data representation. This representation is called the meta- model. The meta-model is a description of UML in UML. It describes the objects, attributes, and relationships necessary to represent the concepts of UML within a software application. This provides CASE manufacturers with a standard and unambiguous way to represent UML models. Hopefully it will allow for easy transport of UML models between tools. It may also make it easier to write ancillary tools for browsing, summarizing, and modifying UML models. A deeper discussion of the metamodel is beyond the scope of this column. Interested readers can learn more about it by downloading the UML documents from the rational web site2.
    [Show full text]
  • Pivotpoint-Sparx Partnership Promotes Model-Based Systems
    PivotPoint-Sparx Partnership Promotes Model-Based Systems Engineering with SysML PivotPoint Technology and Sparx Systems today announced a technology partnership that will combine their complementary strengths in SysML training and tools for systems engineers. PivotPoint announced that its “SysML Distilled™ with Enterprise Architect™” workshop is immediately available, and will use Sparx’s new MDG Technology for SysML™ product. Fallbrook, California (PRWEB) - October 9, 2006 -- PivotPoint Technology and Sparx Systems today announced a technology partnership to promote model-based systems engineering with the Systems Modeling Language (SysML). SysML is the new domain-specific modeling language for systems engineering applications that was adopted by the Object Management Group as OMG SysML™ in July 2006, and is attracting users among systems engineers worldwide. Under the agreement, PivotPoint will be Sparx’s primary partner for training and consulting services that use Sparx’s new SysML product (MDG Technology for SysML™), which was released last week. PivotPoint showed its readiness to partner by announcing the immediate availability of a new “SysML Distilled™ with Enterprise Architect™” workshop, which combines both SysML language and tool training. SysML extends the Unified Modeling Language (UML), the industry standard for specifying software-intensive systems, so that it can also specify hardware, processes, personnel, and facilities. Systems engineers who want to follow a model-based systems engineering process gain at least two important advantages in using SysML. First, SysML is a smaller language than UML 2.0 since it has fewer diagrams and constructs, so it is easier for engineers to learn and apply. Second, SysML adds to the semantic expressiveness of UML with two new diagrams for defining requirements and parametric constraints, which systems engineers need to fully specify complex systems.
    [Show full text]
  • 03-01-06 BPDM RFP.Pdf
    Business Process Definition Metamodel RFP Object Management Group First Needham Place 250 First Avenue, Suite 100 Needham, MA 02494 Telephone: +1-781-444-0404 Facsimile: +1-781-444-0320 Business Process Definition Metamodel Request For Proposal OMG Document: bei/2003-01-06 Letters of Intent due: June 16, 2003 Submissions due: August 18, 2003 Objective of this RFP This Request For Proposals solicits submissions that specify a business process definition metamodel, which is platform independent with respect to specific business process definition languages. This metamodel will define an abstract language for specification of executable business processes that execute within an enterprise (with or without human involvement); and may collaborate between otherwise- independent business processes executing in different business units or enterprises. The specification developed in response to this RFP is expected to achieve the following: • A common metamodel to unify the diverse business process definition graphical and textual notations that exist in the industry • A metamodel that complements existing UML metamodels so that business processes specifications can be part of complete system specifications to assure consistency and completeness bei/2003-01-06, January 31, 2003 1 Business Process Definition Metamodel RFP • The ability to integrate process models for workflow management processes, automated business processes, and collaborations between business units. • Support for the specification of choreography, describing the collaboration
    [Show full text]
  • Unifying Modeling and Programming with ALF
    SOFTENG 2016 : The Second International Conference on Advances and Trends in Software Engineering Unifying Modeling and Programming with ALF Thomas Buchmann and Alexander Rimer University of Bayreuth Chair of Applied Computer Science I Bayreuth, Germany email: fthomas.buchmann, [email protected] Abstract—Model-driven software engineering has become more The Eclipse Modeling Framework (EMF) [5] has been and more popular during the last decade. While modeling the established as an extensible platform for the development of static structure of a software system is almost state-of-the art MDSE applications. It is based on the Ecore meta-model, nowadays, programming is still required to supply behavior, i.e., which is compatible with the Object Management Group method bodies. Unified Modeling Language (UML) class dia- (OMG) Meta Object Facility (MOF) specification [6]. Ideally, grams constitute the standard in structural modeling. Behavioral software engineers operate only on the level of models such modeling, on the other hand, may be achieved graphically with a set of UML diagrams or with textual languages. Unfortunately, that there is no need to inspect or edit the actual source code, not all UML diagrams come with a precisely defined execution which is generated from the models automatically. However, semantics and thus, code generation is hindered. In this paper, an practical experiences have shown that language-specific adap- implementation of the Action Language for Foundational UML tations to the generated source code are frequently necessary. (Alf) standard is presented, which allows for textual modeling In EMF, for instance, only structure is modeled by means of of software systems.
    [Show full text]
  • Plantuml Language Reference Guide (Version 1.2021.2)
    Drawing UML with PlantUML PlantUML Language Reference Guide (Version 1.2021.2) PlantUML is a component that allows to quickly write : • Sequence diagram • Usecase diagram • Class diagram • Object diagram • Activity diagram • Component diagram • Deployment diagram • State diagram • Timing diagram The following non-UML diagrams are also supported: • JSON Data • YAML Data • Network diagram (nwdiag) • Wireframe graphical interface • Archimate diagram • Specification and Description Language (SDL) • Ditaa diagram • Gantt diagram • MindMap diagram • Work Breakdown Structure diagram • Mathematic with AsciiMath or JLaTeXMath notation • Entity Relationship diagram Diagrams are defined using a simple and intuitive language. 1 SEQUENCE DIAGRAM 1 Sequence Diagram 1.1 Basic examples The sequence -> is used to draw a message between two participants. Participants do not have to be explicitly declared. To have a dotted arrow, you use --> It is also possible to use <- and <--. That does not change the drawing, but may improve readability. Note that this is only true for sequence diagrams, rules are different for the other diagrams. @startuml Alice -> Bob: Authentication Request Bob --> Alice: Authentication Response Alice -> Bob: Another authentication Request Alice <-- Bob: Another authentication Response @enduml 1.2 Declaring participant If the keyword participant is used to declare a participant, more control on that participant is possible. The order of declaration will be the (default) order of display. Using these other keywords to declare participants
    [Show full text]
  • Sysml Distilled: a Brief Guide to the Systems Modeling Language
    ptg11539604 Praise for SysML Distilled “In keeping with the outstanding tradition of Addison-Wesley’s techni- cal publications, Lenny Delligatti’s SysML Distilled does not disappoint. Lenny has done a masterful job of capturing the spirit of OMG SysML as a practical, standards-based modeling language to help systems engi- neers address growing system complexity. This book is loaded with matter-of-fact insights, starting with basic MBSE concepts to distin- guishing the subtle differences between use cases and scenarios to illu- mination on namespaces and SysML packages, and even speaks to some of the more esoteric SysML semantics such as token flows.” — Jeff Estefan, Principal Engineer, NASA’s Jet Propulsion Laboratory “The power of a modeling language, such as SysML, is that it facilitates communication not only within systems engineering but across disci- plines and across the development life cycle. Many languages have the ptg11539604 potential to increase communication, but without an effective guide, they can fall short of that objective. In SysML Distilled, Lenny Delligatti combines just the right amount of technology with a common-sense approach to utilizing SysML toward achieving that communication. Having worked in systems and software engineering across many do- mains for the last 30 years, and having taught computer languages, UML, and SysML to many organizations and within the college setting, I find Lenny’s book an invaluable resource. He presents the concepts clearly and provides useful and pragmatic examples to get you off the ground quickly and enables you to be an effective modeler.” — Thomas W. Fargnoli, Lead Member of the Engineering Staff, Lockheed Martin “This book provides an excellent introduction to SysML.
    [Show full text]
  • VPUML Data Sheet
    Datasheet Visual Paradigm for UML 7.0 Model-Code-Deploy Platform Boost Productivity with Innovative and Intuitive Technologies – From Requirements to Code Datasheet Visual Paradigm for UML 7.0 What VP-UML Provides? UML Modeling Business Process Modeling Visualize, design, communicate and Visualize, understand, analyze and document UML 2.2 diagrams with improve business process with BPMN, intuitive and sophisticated visual Process Map, Data Flow Diagram and modeling environment. Organization Chart. Database Modeling Requirement Modeling Design, generate, reverse and synchronize Capture, organize, manage and realize database with sophisticated ERD. requirements with SysML Requirement Generate professional documentation and Diagram. Build or customize your own Java Object-Relational Mapping layer requirement types. (Hibernate). Mind Mapping Diagramming Toolset Brainstorm, outline, share and discuss Create and maintain business and concepts and idea with mind mapping engineering diagrams with Visual tool. Mind Mapping diagram nodes can Paradigm cutting edge visual modeling link to any BPMN or UML elements to toolset such as resource-centric interface, keep the traceability. mouse gesture, sweeper, magnet, styles and layer. Page 2 of 6 Datasheet Visual Paradigm for UML 7.0 What VP-UML Provides? Modeling Toolset Documentation Generation Beyond diagramming there are various Design and generate professional toolsets to improve the quality of visual documentation in PDF, MS Word 2007 modeling. Nicknamer helps maintain and HTML formats. Keeping database, single element with multiple names for program and technical specification multi-national team. Visual Diff shows up-to-date with minimal effort. differences between diagrams and revisions visually. Animating UML diagram with Animacian. Team Collaboration Interoperability & Integration Modeling collaboratively and Export, import and merge with XML, simultaneously with VP Teamwork XMI, MS Excel formats.
    [Show full text]
  • 7 Best Free Flowchart Tools for Windows
    2018. 6. 1. Pocket: 7 Best Free Flowchart Tools for Windows 7 Best Free Flowchart Tools for Windows By Joel Lee, www.makeuseof.com 6월 20일, 2017 Flowcharts aren’t just for engineers, programmers, and managers. Everyone can benet from learning how to make owcharts, most notably as a way to streamline your work and life, but even to break free from bad habits. The only problem is, what’s the best way to make a owchart? Plenty of top-notch owcharting apps exist, but they can get pricey. Microsoft Visio, the most popular option, is $300 (standalone) or $13 per month (on top of Oce 365). ConceptDraw Pro is $200. Edraw Max is $180. MyDraw is $70. Is it really necessary to spend so much on a owcharting tool? No! There are plenty of free options that are more than good enough, especially for non-business uses. You can either learn to create stunning owcharts in Microsoft Word How to Create Stunning Flowcharts With Microsoft Word How to Create Stunning Flowcharts With Microsoft Word Used with imagination, owcharts can simplify both your work or life. Why not try out a few owcharts with one of the easiest tools on hand – Microsoft Word. Read More if you already have it or use one of the following free Windows apps. Web-based apps have been intentionally excluded. 1. Dia Dia is a free and full-featured owchart app. It’s also entirely open source under the GPLv2 license, which is great if you adhere to open source philosophy. It’s powerful, extensible, and easy to use.
    [Show full text]
  • A Study on Process Description Method for DFM Using Ontology
    Invited Paper A Study on Process Description Method for DFM Using Ontology K. Hiekata1 and H. Yamato2 1Department of Systems Innovation, Graduate School of Engineering, The University of Tokyo, 5-1-5, Kashiwanoha, Kashiwa-city, Chiba 277-8563, Japan 2Department of Human and Engineered Environmental Studies, Graduate School of Frontier Sciences, The University of Tokyo, 5-1-5, Kashiwanoha, Kashiwa-city, Chiba 277-8563, Japan [email protected], [email protected] Abstract A method to describe process and knowledge based on RDF which is an ontology description language and IDEF0 which is a formal process description format is proposed. Once knowledge of experienced engineers is embedded into the system the knowledge will be lost in the future. A production process is described in a proposed format similar to BOM and the process can be retrieved as a flow diagram to make the engineers to understand the product and process. Proposed method is applied to a simple production process of common sub-assembly of ships for evaluation. Keywords: Production process, DFM, Ontology, Computer system 1 INTRODUCTION (Unified Resource Identifier) is assigned to all the objects, There are many research and computer program for and metadata is defined for all objects using the URI. supporting optimization of production process in Metadata is defined as a statement with subject, shipyards. And knowledge of experienced engineers is predicate and object. The statement is called triple in embedded into the system. Once the knowledge is RDF. Two kinds of elements, Literal or Resource, can be embedded into computer system, the knowledge is not a component of a statement.
    [Show full text]