A Model-Driven Software Construction Approach for Cyber-Physical Systems

Total Page:16

File Type:pdf, Size:1020Kb

A Model-Driven Software Construction Approach for Cyber-Physical Systems Faculty for Computer Science, Electrical Engineering and Mathematics A Model-driven Software Construction Approach for Cyber-physical Systems Uwe Pohlmann Dissertation submitted in partial fulfillment of the requirements for the degree of Doktor der Naturwissenschaften (Dr. rer. nat.) Referee: Prof. Dr. Matthias Tichy Prof. Dr. Gregor Engels Paderborn, April 17, 2018 ISBN 978-3-00-059657-5 Abstract Systems and software engineers realize innovative functionality in cyber-physical systems by connecting previously independent systems. The development of these systems becomes more challenging because the systems’ complexity, the amount of the safety-critical software, the heterogeneity of the underlying platforms, and the connectivity of the systems increase steadily. However, existing model-driven approaches do not cover the different engineers’ concerns efficiently during the different development tasks. Many of these approaches have a focus on the formal design and the verification of safety and real-time properties. Though, the question how to retain the systems’ safety during following construction tasks remains open. This thesis focuses on the construction tasks: physical system integration validation, resource allocation, and the implementation. It presents a highly automated end-to-end model- driven approach for the development of interacting cyber-physical systems that are realized on heterogeneous, distributed platforms. The approach covers the validation of the system integration via model-in-the-loop simulation, constraint-driven software to hardware allocation, and generative software construction. Consequently, the approach retains the system’s safety with respect to systematic errors through different development tasks. It enables engineers to detect and avoid design and implementation flaws. Thereby, it improves the reliability of systems during their operation. It enables an effective and efficient seamless development. This thesis evaluates the approach by providing an integrated development environment and conducting several case studies from the automotive and automation domain. The evaluation shows the effective and in comparison to state of the art approaches more efficient application of: (1) the model-in-the-loop simulation in the context of virtual prototypes, (2) the allocation constraint specification and the automated allocation planning, and (3) the generation of executables for heterogeneous, distributed embedded platforms. III Zusammenfassung Systemingenieure und Softwaretechniker realisieren innovative Funktionen von cyber- physischen Systemen durch die Vernetzung von vormals unabhängigen Systemen. Die Entwicklung dieser Systeme wird schwieriger, weil die Systemkomplexität, die Menge an sicherheitskritischer Software, die Heterogenität der verwendeten Plattformen und der Vernetzungsgrad stetig ansteigen. Jedoch bedienen existierende modellgetriebene Entwicklungsansätze die verschiedenen Bedürfnisse der beteiligten Ingenieure während der verschiedenen Entwicklungsaufgaben nicht effizient genug. Existierende Ansätze fokussieren sich typischerweise auf den formalen Entwurf und die Verifizierung von Sicherheits- und Echtzeiteigenschaften. Sie beantworten jedoch nicht die Frage wie die Systemsicherheit während der folgenden Konstruktionsschritte beibehalten werden kann. In dieser Dissertation fokussiere ich mich auf die Konstruktionsschritte Validierung der Systemintegration, Zuordnung von Systemressourcen und auf die Implementierung. Ich stelle einen durchgängig modellgetriebenen Entwicklungsansatz für interagierende cyber-physische Systeme vor, welche durch heterogene, verteilte Software- und Hardwareplattformen gekennzeichnet sind. Der Ansatz beinhaltet Verfahren für die Systemintegrationsvalidierung mittels „Model-in-the- Loop“ Simulation, die automatische Softwareverteilung, welche durch Entwurfsanforderungen stark beschränkt ist, und die generative Softwarekonstruktion. Dementsprechend stellt der Ansatz die Systemsicherheit in Bezug auf systematische Fehler während der verschiedenen Entwicklungsaufgaben sicher. Er ermöglicht Ingenieuren und Technikern Entwurfs- und Implementierungsfehler frühzeitig zu entdecken und im Folgenden systematisch zu vermeiden. Hierdurch verbessert der Ansatz die Zuverlässigkeit der Systeme während ihres Betriebs. Er ermöglicht eine effektive und effiziente, durchgängige Entwicklung. Zur Anwendung und Evaluierung des Ansatzes stelle ich eine integrierte Entwicklungsumgebung zur Verfügung und führe verschiedene Fallstudien aus der Automobil- und der Automatisierungsdomäne durch. Die Evaluierung zeigt die effektive und im Vergleich zum Stand der Technik effizientere Anwendung von (1) der „Model-in-the-Loop“ Simulation im Kontext eines virtuellen Prototyps, (2) der Spezifikation von Allokationsbeschränkungen und der automatisierten Allokationsplanung und (3) der Generierung von ausführbaren Programmen für heterogene, verteilte, vernetzte eingebettete Plattformen. V Danksagung Ich möchte mich an dieser Stelle bei meinen Freunden, Kollegen und bei meiner Familie bedanken, ohne die diese Arbeit nicht möglich gewesen wäre. Insbesondere das angenehme Arbeits- und Forschungsklima des Heinz Nixdorf Instituts, des Fraunhofer-Instituts IEM und des s-labs, welches durch die vielen Kollegen geprägt wird, die vielen gemeinsamen Stunden und die anregenden Diskussionen, haben mir immer geholfen. Ich möchte mich bei meinen Betreuern Wilhelm Schäfer und Matthias Tichy bedanken. Durch die vielen Anregungen, Rückmeldungen und Diskussionen konnte ich meine Forschung vorantreiben und in dieser Arbeit darstellen. Neben dem fachlichen Rat waren die persönlichen Ratschläge sehr inspirierend. Gregor Engels danke ich für die Übernahme des weiteren schriftlichen Gutachtens. Ich möchte den weiteren Mitgliedern meiner Promotionskommission, Eric Bodden, Matthias Meyer und Stefan Sauer, danken. Meine Arbeit hat von der interdisziplinären Arbeit im Forschungsprojekt ENTIME profitiert. Hier möchte ich den bisher nicht erwähnten Projektmitarbeitern Farisoroosh Abrishamchian, Harald Annacker, Frank Bauer, Daniel Kruse, Sarah Flottmeier, Viktor Just, Thomas Schierbaum, Heinrich Teichrieb und Felix Oestersötebier danken. Dies gilt auch für die Mitarbeiter im Forschungsprojekt it’s OWL – Intelligente Vernetzung, in dem ich mitarbeiten durfte. Namentlich gilt der Dank Peer Adelt, Johannes Ax, Lars Dürkop, Volker Geneiß, Thorsten Jungeblut, Jan Jatzkowski, Uwe Mönks, Konstantin Nußbaum, Henning Trsek, Jens Otto und Lukasz Wisniewski. Weiterhin möchte ich meinen Kollegen Stefan Dziwok, Christopher Gerking, Christian Heinzemann und David Schubert aus der MechatronicUML Entwicklungsgruppe danken mit denen ich viele Konzepte detailliert entwickelt, diskutiert und verbessert habe. Dank gilt auch meinen Bürokollegen Stefan Dziwok, Christian Bremer und Sven Merschjohann und den weiteren aktuellen und ehemaligen Kollegen der Fachgruppe Softwaretechnik. Diese sind namentlich Anas Anis, Matthias Becker, Steffen Becker, Manuel Benz, Christian Brenner, Christian Brink, Eric Bodden, Andreas Peter Dann, Nicola Danielzik, Tobias Eckardt, Markus Fockel, Jens Frieben, Johannes Geismann, Faezeh Ghassemi, Joel Greenyer, Jutta Haupt, Stefan Henkler, Ben Hermann, Jörg Holtmann, Thorsten Koch, Stefan Krüger, Sebastian Lehrig, Renate Löffler, Jürgen Maniera, Ahmet Mehic, Sven Merschjohann, Matthias Meyer, Vera Meyer, Lisa Nguyen, Faruk Pasic, Goran Piskachev, Marie Christin Platenius, Claudia Priesterjahn, Jan Rieke, David Schmelter, Philipp Schubert, Johannes Späth, Lars Stockmann, Christian Stritzke, Julian Suck, Oliver Sudmann, Dietrich Travkin, Markus von Detten und Benedict Wohlers. Die Integration von Studenten in Forschungsaktivitäten ist mir sehr wichtig. Deshalb wäre diese Arbeit in der vorliegenden Form nicht möglich gewesen ohne die Mitarbeit der Studenten Jan Bobolz, Melanie Bruns, Ingo Budde, Mike Czech, Andreas Peter Dann, Johannes Geismann, Marcus Hüwe, Arthur Krieger, Jan-Niclas Strüwer, Sebastian Thiele, Mario Rose, Rebekka Wohlrab und Boris Wolf. Zum Schluss möchte ich mich bei meiner Familie für ihre Unterstützung bedanken. Dank gilt meinen Brüdern Martin und Andreas, wie auch meiner Mutter Mathilde und meinem Vater Dietrich. Besonderer Dank gilt meiner Freundin Anna für ihre Mithilfe und Unterstützung. VII Contents Titlepage I Abstract III Zusammenfassung V Danksagung VII 1 Introduction 1 1.1 Problem Statement . 2 1.1.1 Simulation of Cyber-physical Systems . 2 1.1.2 Specifying Constraints for Allocation Planning . 3 1.1.3 Constructing Software for Distributed Cyber-Physical Systems . 4 1.2 Contribution . 4 1.2.1 Model-in-the-Loop Simulation . 5 1.2.2 Allocation Engineering . 6 1.2.3 Software Construction . 6 1.3 Running Example: Cooperative Overtaking System Using Car-2-X Communication 6 1.4 Thesis Structure . 7 2 MechatronicUML 11 2.1 Development Process . 11 2.2 Modeling Views . 12 2.2.1 Real-Time Coordination Protocol . 12 2.2.2 Real-Time Statechart . 14 2.2.3 Action Language . 15 2.2.4 Component Model . 16 2.2.5 Component Instance Configuration . 17 3 Model-in-the-Loop Simulation 19 3.1 Modelica . 23 3.1.1 Modeling System’s Structures . 23 3.1.2 Modeling the State-based Behavior . 24 3.1.3 Model-in-the-Loop (MiL) Simulation of Modelica Models . 27 3.2 Process for Model-in-the-Loop Simulation of MechatronicUML . 27 3.3 Real-Time Coordination Modelica Library . 30 3.3.1 Synchronization Connectors and Ports . 30 3.3.2 Message-Based Communication . 32 3.3.3 Clocks, Invariants, and Clock Constraints . 34 3.3.4 Formal Syntax and Semantics
Recommended publications
  • Curriculum Vitae
    Vancouver, BC Canada +1.604.551.7988 KipWarner [email protected] Senior Software Engineer / Co-chairman OPMLWG 07 August 2021 *** WARNING: MANGLED TEXT COPY. DOWNLOAD PDF: www.thevertigo.com/getcv.php?fix Education 2007 Artificial Intelligence, BSc (Cognitive Systems: Computational Intelligence & Design) Department of Computer Science, University of British Columbia 2005 Associate of General Science Kwantlen Polytechnic University Professional Experience Jul 2015 - Cartesian Theatre, Vancouver, British Columbia Present Senior Software Engineer Techniques: Artificial intelligence, asymmetric cryptography, build automation, continuous integration testing, digital signal processing, machine learning, MapReduce, REST architecture, SIMD, and UNIX server daemon. Technologies: AltiVec / POWER Vector Media Extension; Apport; Assembly; AVX, Autopkgtest; Avahi / Apple’s Bonjour; Bash; C++17; CppUnit; cwrap (nss_wrapper); DBus; debhelper; GCC; GDB; Git; GNU Autotools; GNU/Linux; init.d; libav / FFmpeg; lsbinit; M4; OpenBMC; OpenSSL; Pistache; pkg-config; PortAudio; PostgreSQL; PPA; Python; QEMU; quilt; sbuild / pbuilder; setuptools; SQLite; STL; strace; systemd; Swagger; Umbrello; and Valgrind. Standards: Debian Configuration Management Specification; Debian Database Application Policy; Debian Policy Manual; Debian Python Policy; DEP-8; Filesystem Hierarchy Standard; freedesktop.org; GNU Coding Standards; IEEE 754; JSON; LSB; OpenAPI Specification; POSIX; RFC 4180; RSA; SQL; UNIX System V; UML; UPnP; and Zeroconf. Hardware: Ported to 64-bit PC
    [Show full text]
  • Indicators for Missing Maintainership in Collaborative Open Source Projects
    TECHNISCHE UNIVERSITÄT CAROLO-WILHELMINA ZU BRAUNSCHWEIG Studienarbeit Indicators for Missing Maintainership in Collaborative Open Source Projects Andre Klapper February 04, 2013 Institute of Software Engineering and Automotive Informatics Prof. Dr.-Ing. Ina Schaefer Supervisor: Michael Dukaczewski Affidavit Hereby I, Andre Klapper, declare that I wrote the present thesis without any assis- tance from third parties and without any sources than those indicated in the thesis itself. Braunschweig / Prague, February 04, 2013 Abstract The thesis provides an attempt to use freely accessible metadata in order to identify missing maintainership in free and open source software projects by querying various data sources and rating the gathered information. GNOME and Apache are used as case studies. License This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0) license. Keywords Maintenance, Activity, Open Source, Free Software, Metrics, Metadata, DOAP Contents List of Tablesx 1 Introduction1 1.1 Problem and Motivation.........................1 1.2 Objective.................................2 1.3 Outline...................................3 2 Theoretical Background4 2.1 Reasons for Inactivity..........................4 2.2 Problems Caused by Inactivity......................4 2.3 Ways to Pass Maintainership.......................5 3 Data Sources in Projects7 3.1 Identification and Accessibility......................7 3.2 Potential Sources and their Exploitability................7 3.2.1 Code Repositories.........................8 3.2.2 Mailing Lists...........................9 3.2.3 IRC Chat.............................9 3.2.4 Wikis............................... 10 3.2.5 Issue Tracking Systems...................... 11 3.2.6 Forums............................... 12 3.2.7 Releases.............................. 12 3.2.8 Patch Review........................... 13 3.2.9 Social Media............................ 13 3.2.10 Other Sources..........................
    [Show full text]
  • Pipenightdreams Osgcal-Doc Mumudvb Mpg123-Alsa Tbb
    pipenightdreams osgcal-doc mumudvb mpg123-alsa tbb-examples libgammu4-dbg gcc-4.1-doc snort-rules-default davical cutmp3 libevolution5.0-cil aspell-am python-gobject-doc openoffice.org-l10n-mn libc6-xen xserver-xorg trophy-data t38modem pioneers-console libnb-platform10-java libgtkglext1-ruby libboost-wave1.39-dev drgenius bfbtester libchromexvmcpro1 isdnutils-xtools ubuntuone-client openoffice.org2-math openoffice.org-l10n-lt lsb-cxx-ia32 kdeartwork-emoticons-kde4 wmpuzzle trafshow python-plplot lx-gdb link-monitor-applet libscm-dev liblog-agent-logger-perl libccrtp-doc libclass-throwable-perl kde-i18n-csb jack-jconv hamradio-menus coinor-libvol-doc msx-emulator bitbake nabi language-pack-gnome-zh libpaperg popularity-contest xracer-tools xfont-nexus opendrim-lmp-baseserver libvorbisfile-ruby liblinebreak-doc libgfcui-2.0-0c2a-dbg libblacs-mpi-dev dict-freedict-spa-eng blender-ogrexml aspell-da x11-apps openoffice.org-l10n-lv openoffice.org-l10n-nl pnmtopng libodbcinstq1 libhsqldb-java-doc libmono-addins-gui0.2-cil sg3-utils linux-backports-modules-alsa-2.6.31-19-generic yorick-yeti-gsl python-pymssql plasma-widget-cpuload mcpp gpsim-lcd cl-csv libhtml-clean-perl asterisk-dbg apt-dater-dbg libgnome-mag1-dev language-pack-gnome-yo python-crypto svn-autoreleasedeb sugar-terminal-activity mii-diag maria-doc libplexus-component-api-java-doc libhugs-hgl-bundled libchipcard-libgwenhywfar47-plugins libghc6-random-dev freefem3d ezmlm cakephp-scripts aspell-ar ara-byte not+sparc openoffice.org-l10n-nn linux-backports-modules-karmic-generic-pae
    [Show full text]
  • GNOME Annual Report 2008
    1 Table of Contents Foreword Letter from the Executive Director 4 A year in review GNOME in 2008 8 GNOME Mobile 16 Events and Community initiatives Interview with Willie Walker 20 GNOME around the world 24 GNOME Foundation Foundation Finances 30 List of all 2008 donors 33 2 Letter from Stormy Peters Stormy Peters is the GNOME Foundation Executive Director and has great experience in the industry and with the open source culture. Hello GNOME Lovers! seek them out and to invite them to come play. (Actually, I felt welcome from day -1, GNOME's goal is to bring free and open as I met a bunch of guys on the plane who source computing to everyone regardless of turned out to also be going to GUADEC. I ability. I consider myself extremely lucky to spent my first day in Copenhagen walking have joined the project as executive director around with some guys from Red Hat and of the GNOME Foundation. It's a pleasure Eazel trying to stay awake through jetlag. I and a privilege to work with thousands of pe- remember Havoc Pennington saying we just ople dedicated to making free had to stay awake until dinner software available for everyone The spirit and time.) on desktops and mobile plat- dedication of the forms. I don't think it's an GNOME community to One of the most common exaggeration to say that their goals of creating questions I get asked is GNOME technology is chan- a free and open source why did you take this job? ging the world for many from software ..
    [Show full text]
  • Omnet++ Installation Guide Version 4.6 Copyright © 2014 András Varga and Opensim Ltd
    OMNeT++ Installation Guide Version 4.6 Copyright © 2014 András Varga and OpenSim Ltd. Table of Contents 1. General Information ........................................................................................... 1 2. Windows ............................................................................................................. 2 3. Mac OS X ........................................................................................................... 6 4. Linux ................................................................................................................ 12 5. Ubuntu ............................................................................................................. 18 6. Fedora 18 ......................................................................................................... 22 7. Red Hat ............................................................................................................ 24 8. OpenSUSE ....................................................................................................... 26 9. Generic Unix .................................................................................................... 28 10. Build Options ................................................................................................. 35 iii Chapter 1. General Information 1.1. Introduction This document describes how to install OMNeT++ on various platforms. One chapter is dedicated to each operating system. 1.2. Supported Platforms OMNeT++ has been tested and is supported on the
    [Show full text]
  • CSE 303 Lecture 13A
    CSE 303 Lecture 13a Debugging C programs reading: Programming in C Ch. 13 slides created by Marty Stepp http://www.cs.washington.edu/303/ 1 gdb • gdb : GNU debugger. Helps you step through C programs. absolutely essential for fixing crashes and bad pointer code your program must have been compiled with the -g flag • usage: $ gdb program GNU gdb Fedora (6.8-23.fc9) Copyright (C) 2008 Free Software Foundation, Inc... (gdb) run parameters ... • redirecting input: $ gdb program (gdb) run parameters < inputfile 2 gdb commands command description run or r parameters run the program break or b place sets a breakpoint at the given place: - a function's name - a line number - a source file : line number print or p expression prints the given value / variable step or s advances by one line of code ("step into") next or n advances by one line of code ("step over") finish runs until end of function ("step out") continue or c resumes running program backtrace or bt display current function call stack quit or q exits gdb 3 A gdb session $ gdb intstack GNU gdb 5.2.1 Copyright 2002 Free Software Foundation, Inc. (gdb) b 34 Breakpoint 1 at 0x4010ea: file intstack.c, line 34. (gdb) r Starting program: /home/user/intstack Breakpoint 1, main () at intstack.c:34 34 Node* oldFront = stack; (gdb) p stack $1 = (Node *) 0x4619c0 (gdb) n 35 printf("%d\n", stack->data); (gdb) n 36 stack = stack->next; (gdb) n 37 free(oldFront); (gdb) p stack $4 = (Node *) 0x462856 (gdb) p oldFront $2 = (Node *) 0x4619c0 (gdb) p *oldFront $3 = {data = 10, next = 0x462856} (gdb) c Continuing.
    [Show full text]
  • GUADEC Schedule.Pdf
    1 Contents About the event ......................................................................................................................... 5 Map of the location............................................................................................................................................................. 5 Welcome to GUADEC!................................................................................................................. 6 The G !ME !pen Des"top Da#............................................................................................... $ Main t%ac" sche&ule................................................................................................................... ' We&nes&a# ('th )ul#.......................................................................................................................................................... ' Thurs&a# 29th )ul#............................................................................................................................................................... * +ri&a# ,-th )ul#.................................................................................................................................................................... 10 Abst%acts..................................................................................................................................... 1( G OME, the /eb. an& +ree&om................................................................................................................................
    [Show full text]
  • L'écosystème Du Libre
    L’écosystème du Libre: interactions entre projets amonts, distributions et utilisateurs - l’exemple de Debian et Ubuntu Lucas Nussbaum Rencontres Mondiales du Logiciel Libre 2009 Thème Développement Lucas Nussbaum L’écosystème du Libre 1 / 23 Le Logiciel Libre aujourd’hui Lucas Nussbaum L’écosystème du Libre 2 / 23 Le Logiciel Libre aujourd’hui Ubuntu Lucas Nussbaum L’écosystème du Libre 2 / 23 Objectifs de cette présentation Présenter les différents acteurs du développement de logiciels libres Expliquer les interactions entre ces acteurs En particulier : interactions autour de/entre Debian et Ubuntu Lucas Nussbaum L’écosystème du Libre 3 / 23 Les Utilisateurs Objectif : utiliser les logiciels pour produire quelque chose Besoins : Logiciels faciles d’accès et à utiliser Logiciels correspondant à leurs besoins Logiciels fonctionnant correctement Utilité pour la communauté : Remontée de problèmes ou de besoins supplémentaires Vie de la communauté : Support d’autres utilisateurs Buzz ... Lucas Nussbaum L’écosystème du Libre 4 / 23 Les distributions Tentent de fournir aux utilisateurs tous les logiciels correspondant à leurs besoins Standardisent : La manière d’accéder aux logiciels (paquets) La qualité des logiciels La manière de remonter des problèmes Principales tâches : Uniformisation de logiciels d’origines diverses Intégration Gestion de branches "stables" Lucas Nussbaum L’écosystème du Libre 5 / 23 Les projets amonts Développent réellement les logiciels Objectif : meilleur logiciel possible Dans sa branche de développement Grande diversité
    [Show full text]
  • ANNUAL REPORT 2010-2011 Table of Contents
    ANNUAL REPORT 2010-2011 Table of contents Foreword Letter from the GNOME Foundation Executive Director 4 GNOME 3 A review of the GNOME 3 Platform 5 The way to GNOME 3 and the future 7 Words about GNOME 3 8 Two years in review International events 9 Hackfests 11 Interview with the Thank You pants winners 13 GNOME Outreach Program for Women 15 Google Summer of Code 19 GNOME User Groups 21 Foundation development GNOME Foundation financial overview 22 GNOME Advisory Board 23 Friends of GNOME donors 25 3 Letter from the GNOME Foundation Executive Director The publication date of this biannual report is roughly one year from when I started as Executive Director of the GNOME Foundation. Most of the period it covers is before I joined, and a discussion of the accomplishments of this period needs a big acknowledgement and thank you to the folks that drove the organization during this time. In fact, it's because of the amazing work that you'll read about in this report that I knew it was the right decision to come and work for GNOME. During the first part of this time, Stormy Peters held the role of Executive Director and worked hard to steer the Foundation. I personally have learned a great deal from her and I think the organization benefited greatly from her dedication and hard work! The second­most significant period of time represented in this report was the ten month period after Stormy left the GNOME Foundation but before I was hired. During this time, all of the affairs and activities of the GNOME community and Foundation were steered by volunteers.
    [Show full text]
  • Herramientas Computacionales En Linux
    Herramientas Computacionales en Linux Antonio Carrillo Ledesma y Karla Ivonne González Rosas Facultad de Ciencias, UNAM http://academicos.fciencias.unam.mx/antoniocarrillo Una copia de este trabajo se puede descargar de la página: http://132.248.182.159/acl/hcl/ http://132.248.182.159/acl/Textos/ Con…namiento 2020, Versión 1.0 1 1El presente trabajo está licenciado bajo un esquema Creative Commons Atribución CompartirIgual (CC-BY-SA) 4.0 Internacional. Los textos que compo- nen el presente trabajo se publican bajo formas de licenciamiento que permiten la copia, la redistribución y la realización de obras derivadas siempre y cuando éstas se distribuyan bajo las mismas licencias libres y se cite la fuente. ¡Copiaeste libro! ... Compartir no es delito. Herramientas Computacionales en Linux Índice 1 Introducción 5 2 Sistemas Operativos 12 2.1 Windows .............................. 14 2.2 Mac OS .............................. 15 2.3 Android .............................. 17 2.4 Linux ............................... 20 2.5 Chrome OS y las Chromebook .................. 27 2.6 Otros ................................ 30 3 Trabajando con Debian GNU/Linux y sus Derivados 32 3.1 Sistema de Archivos y Estructura de Directorios ........ 32 3.2 Trabajando en Línea de Comandos ............... 37 3.3 Cómo buscar archivos ....................... 59 3.4 Monitorear el Desempeño .................... 66 3.5 Compresores y Descompresores de Archivos .......... 69 3.6 Copiar Archivos entre Equipos .................. 75 3.7 Interprete de Órdenes de Consola BASH ............ 78 3.8 Desde la Nube ........................... 86 4 Otras Herramientas en Línea de Comandos 91 4.1 Prompt de la Línea de Comandos ................ 91 4.2 Historia de Comados ....................... 96 4.3 Alias a Comandos ......................... 97 4.4 Ayuda de Comandos y Tipo de Archivos ...........
    [Show full text]
  • El Cómputo En Los Cursos De La Facultad De Ciencias, UNAM
    El Cómputo en los Cursos de la Facultad de Ciencias, UNAM Antonio Carrillo Ledesma y Karla Ivonne González Rosas Facultad de Ciencias, UNAM http://academicos.fciencias.unam.mx/antoniocarrillo Una copia de este trabajo se puede descargar de la página: https://sites.google.com/ciencias.unam.mx/acl/en-desarrollo Con…namiento 2020-2021, Versión 1.0 1 1El presente trabajo está licenciado bajo un esquema Creative Commons Atribución CompartirIgual (CC-BY-SA) 4.0 Internacional. Los textos que compo- nen el presente trabajo se publican bajo formas de licenciamiento que permiten la copia, la redistribución y la realización de obras derivadas siempre y cuando éstas se distribuyan bajo las mismas licencias libres y se cite la fuente. ¡Copiaeste libro! ... Compartir no es delito. El Cómputo en los Cursos de la Facultad de Ciencias, UNAM Índice 1 Introducción 7 1.1 Software Propietario y Libre ................... 7 1.1.1 Software Propietario ................... 8 1.1.2 Software Libre ....................... 9 1.2 El Cómputo en las Carreras de Ciencias ............ 11 1.2.1 Algunos Cursos que Usan Cómputo ........... 14 1.3 Paquetes de Cómputo de Uso Común .............. 17 1.3.1 Sistemas Operativos ................... 21 1.3.2 Paquetes de Cálculo Numérico .............. 21 1.3.3 Paquetes de Cálculo Simbólico .............. 22 1.3.4 Paquetes Estadísticos ................... 23 1.3.5 Paquetes O…máticos ................... 24 1.3.6 Lenguajes de Programación y Entornos de Desarrollo . 24 1.3.7 Otros Programas de Cómputo .............. 24 1.4 Sobre los Ejemplos de este Trabajo ............... 25 1.5 Agradecimientos .......................... 25 2 Sistemas Operativos 26 2.1 Windows .............................
    [Show full text]
  • Developer Switch Dreams Crafting the GNOME DX
    Developer Switch Dreams Crafting the GNOME DX Christian Hergert ([email protected]) GNOME is so much more than a desktop What is GNOME? ● Compositor (Mutter, Shell ● !ro"ect with stron# desi#n ethic ($%, Hi# ● 'ile Manager (Nautilus, Sushi ● Hardware ()stractions (*luetooth, Network, Disk, Media, !ower, +nput ● Graphics ,oolkits (Gtk+, Clutter, St ● Lan#uage Enablement (GO)"ect, !ython, JavaScript, 1ala, !erl, Mono What is GNOME? (Continued ● Content Storage and E2ctraction (Tracker, Gom ● !ersonal Data Management (E-D-S, Calendar, Notes, Tasks, ,odo ● (pplication Suite (Evolution, Gnumeric, GIMP, Gedit ● We) *rowser (Epiphan/, We)4itGtk) ● +!C (D3*us/kd)us, G1ariant, Gsettin#s ● Media 'ramework (GStreamer, pulseaudio, rygel ● ,ranslations (damned lies, #translator) ● (rtwork (backgrounds, icono#raph/ What is GNOME? (Continued ● Security (!olic/4it, lock screen, li)secret, seahorse, sand)o2in# ● Communications (Telepathy, 6arstream, empathy ● System Setup/Con7# (+nitial Setup, Control Center) ● 'ile 'ormats (li)2ml8, documents, "son, markdown, (SN9:, desktop ● Standards (wmspec, trash, mime, icons, thum)nail, sounds, recent 7les ● Documentation (yelp/mallard, #tk-doc, #uides5turorials What is GNOME? (Continued ● Developer Tools (#lade, #it#, #li), devhelp, #edit, an"uta, Nemiver, *uilder, *o2es, #he2, s/spro6, terminal, #tk-doc, yelp, d36eet, lookin# #lass, #parted, meld, mempro6, vala) GNOME is a massive achievement *ut there is an elephant in the GN$5room +t;s reall/ hard to contri)ute to 'ree So6tware So + did some research on wh/
    [Show full text]