DOCSLIB.ORG

Caracterizaç ˜Ao De Um Processo De Software Para Projetos De Software Livre

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Caracterizaç ˜Ao De Um Processo De Software Para Projetos De Software Livre Caracterizac¸ao˜ de um Processo de Software para Projetos de Software Livre Christian Robottom Reis [email protected] Orientac¸ao:˜ Profa. Dra. Renata Pontin de Mattos Fortes [email protected] Dissertac¸ao˜ apresentada ao Instituto de Cienciasˆ Matematicas´ e de Computac¸ao˜ da Universidade de Sao˜ Paulo para a obtenc¸ao˜ do t´ıtulo de Mestre em Cienciasˆ da Computac¸ao˜ e Matematica´ Computacional. Sao˜ Carlos, Sao˜ Paulo Fevereiro de 2003 ii Resumo Software Livre e´ software fornecido com codigo´ fonte, e que pode ser livremente usado, modifica- do e redistribu´ıdo. Projetos de Software Livre sao˜ organizac¸oes˜ virtuais formadas por indiv´ıduos que trabalham juntos no desenvolvimento de um software livre espec´ıfico. Estes indiv´ıduos trabalham geo- graficamente dispersos, utilizando ferramentas simples para coordenar e comunicar seu trabalho atraves´ da Internet. Este trabalho analisa esses projetos do ponto de vista de seu processo de software; em outras pala- vras, analisa as atividades que realizam para produzir, gerenciar e garantir a qualidade do seu software. Na parte inicial do trabalho e´ feita uma extensa revisao˜ bibliografica,´ comentando os principais traba- lhos na area,´ e sao˜ detalhadas as caracter´ısticas principais dos projetos de software livre. O conteudo´ principal deste trabalho resulta de dois anos de participac¸ao˜ ativa na comunidade, e de um levantamento realizado atraves´ de questionario,´ detalhando mais de quinhentos projetos diferentes. Sao˜ apresenta- das treze hipoteses´ experimentais, e os resultados do questionario´ sao˜ discutidos no contexto destas hipoteses.´ Dos projetos avaliados nesse levantamento, algumas caracter´ısticas comuns foram avaliadas. As equipes da grande maioria dos projetos sao˜ pequenas, tendo menos de cinco participantes. Alem´ disso, existe uma distribuic¸ao˜ equilibrada entre algumas formas de organizac¸ao˜ descritas na literatura, incluin- do o ‘ditador benevolente’ de Eric S. Raymond e o ‘comite’ˆ exemplificado pelo projeto Apache. Dentre um conjunto de dom´ınios de aplicac¸ao˜ determinados, os projetos de software livre se concentram nas areas´ de engenharia e desenvolvimento de software, redes e seguranc¸a, e aplicac¸oes˜ multim´ıdia. Com relac¸ao˜ as` atividades do processo de software, pode-se dizer que a maioria dos projetos tem requisitos fundamentalmente definidos pelos seus autores, e que a base de usuarios´ de grande parte dos softwares e´ composta dos seus desenvolvedores e da comunidade de software livre. Uma parcela signifi- cativa dos projetos baseia-se em outros softwares pre-existentes,´ e em padroes˜ publicados previamente. Pouca enfaseˆ e´ dada a` usabilidade, assim como as` atividades de garantia de qualidade convencionais. Surpreendentemente, tambem´ recebem pouca atenc¸ao˜ as atividades de revisao˜ de codigo´ e teste sis- tematico.´ Entre as ferramentas que os projetos utilizam, se destacam as listas de discussao˜ e os sistemas de controle de versao.˜ Foi estabelecida uma correlac¸ao˜ entre a dimensao˜ da equipe do projeto e as atividades de engenharia de software que realiza, mas nao˜ se confirmou um v´ınculo entre estas atividades e a idade do projeto. Foram tambem´ estabelecidas relac¸oes˜ entre o numero´ de linhas de codigo´ do software do projeto e a sua idade, tamanho e dom´ınio de aplicac¸ao.˜ Estes resultados sao˜ exibidos neste trabalho, e estarao˜ publicamente dispon´ıveis no site Web do projeto. O trabalho conclui descrevendo partes essenciais do processo de software em projetos de software livre, e oferecendo sugestoes˜ para trabalhos posteriores. Palavras-Chave: Software Livre, Open Source, Processo de Software, Ciclo de Vida, Modelo de Pro- cesso de Software, Engenharia de Software, Desenvolvimento de Software Descentralizado. iii iv Abstract Free Software (or Open Source) is software provided with source code that may be freely used, modified and redistributed. Free Software Projects are virtual communities of developers that work on a specific free software product. These developers work geographically dispersed, using simple tools to communicate and coordinate their actions over the Internet. This work analyzes these projects with respect to their software process; in other words, the activiti- es they do to produce, manage and ensure the quality of their software. In the initial sections, I perform a large review of related work in this field, and provide an overview of the main characteristics of free software projects. The main contents of this dissertation is based on two years of participation in free software projects, and on a survey based on a questionnaire that describes over five hundred different free software projects. I present thirteen initial hypothesis, using them as a framework to analyze the results of the survey. Among the projects evaluated in this survey, some common aspects were observed. For instance, most projects have a small team, with less than five developers. I also found a balanced distribution of leadership systems described in other works, including Eric Raymond’s ‘benevolent dictator’ and the committee exemplified by the Apache project. The domains in which these projects tend to concentrate are software engineering and development, networks and security, and multimedia applications. Concerning the software process activities, most projects have their functional requirements esta- blished by their authors: the user base for most of the projects includes the development team and the free software community. A large proportion of the projects surveyed are based on pre-existing soft- ware, or on previously published standards. Little emphasis is placed on usability and conventional forms of quality assurance. Remarkably, this lack of emphasis on conventional process includes activi- ties like review and testing. Among the tools used by the projects, mailing lists and versioning systems such as CVS come out ahead by a strong margin. A correlation was identified between the size of the project’s team and the software engineering activities that it realizes, but I could not establish a link between the age of the project and these activities. Other correlations were established between the size of the project’s codebase (in terms of lines of code) and its age, size and application domain. The dissertation concludes describing essential parts of the software process in free software projects, and offering suggestions for future work. Keywords: Free Software, Open Source, Software Process, Software Lifecycle, Software Process Mo- del, Software Engineering, Distributed Software Development. v vi CONTEUDO´ CONTEUDO´ Conteudo´ 1 Introduc¸ao˜ 1 1.1 Motivac¸ao˜ ......................................... 2 1.2 Problema de Pesquisa ................................... 2 1.3 Organizac¸ao˜ da Dissertac¸ao˜ ................................ 3 1.4 Convenc¸oes˜ de Formato .................................. 3 2 Processo de Software 5 2.1 Definic¸ao˜ ......................................... 5 2.2 Atividades Essenciais ................................... 6 2.3 Atividades Auxiliares ................................... 7 2.4 Garantia de Qualidade de Software ............................ 8 2.5 Modelos de Processo de Software ............................ 9 3 Software Livre e Open Source 11 3.1 Propriedade Intelectual .................................. 11 3.2 Licenc¸as de Software ................................... 12 3.2.1 Graus de Restric¸ao˜ em Licenc¸as de Software .................. 13 3.2.2 Licenc¸as de Software Livre ............................ 13 3.3 Software Livre e Open Source .............................. 14 3.3.1 Open Source ................................... 16 3.4 Historico´ ......................................... 16 3.4.1 GNU e a Free Software Foundation ....................... 16 3.4.2 O nucleo´ Linux .................................. 17 3.4.3 Outros pacotes de software livre ......................... 17 3.4.4 As distribuic¸oes˜ Linux .............................. 18 3.4.5 Projetos de Software Livre ............................ 20 vii CONTEUDO´ CONTEUDO´ 4 Projetos de Software Livre 21 4.1 Definic¸ao˜ ......................................... 21 4.2 Organizac¸oes˜ Alternativas ................................ 22 4.3 Aspectos de um Projeto de Software Livre ........................ 23 4.3.1 Software ..................................... 23 4.3.2 Comunidade ................................... 24 4.3.3 Comunicac¸ao˜ escrita ............................... 25 4.3.4 Gerenciaˆ do Codigo-fonte´ ............................ 26 4.3.5 Apoio ao Processo de Desenvolvimento ..................... 30 4.3.6 Servic¸os de Hospedagem de Projetos ...................... 32 4.4 Exemplos de Projetos de Software Livre ......................... 33 4.4.1 Nucleo´ de Sistema Operacional: Linux ..................... 33 4.4.2 Servidor Web: Apache .............................. 34 4.4.3 Navegador Web: Mozilla ............................. 34 5 Trabalhos Relacionados 37 5.1 Literatura Essencial .................................... 37 5.1.1 A Catedral e o Bazar de Eric Raymond ..................... 37 5.1.2 Desenvolvimento Distribu´ıdo: Herbsleb e Grinter ................ 39 5.1.3 A avaliac¸ao˜ emp´ırica de Sandeep Krishnamurthy ................ 39 5.1.4 Detratores Iniciais ................................ 40 5.2 Estudos sobre Projetos Espec´ıficos ............................ 41 5.2.1 O Servidor Apache ................................ 41 5.2.2 O Nucleo´ Linux .................................. 42 5.2.3 O Projeto Mozilla ................................
Load more

Recommended publications
  • Engineering at Johns Hopkins University! We Look Forward to Meeting You When You Arrive on Campus for Orientation
    Eng in eering 1 01 2019-2020 p rogr am p lanni ng gui de for fi rst-y ear e ngi neering s tudents Welcome to the Whiting School of Engineering at Johns Hopkins University! We look forward to meeting you when you arrive on campus for orientation. In the meantime, we have prepared the First-Year Academic Guide and Engineering 101 to get you started. The Academic Guide includes information for all first-year students at Hopkins, while Engineering 101 is directed specifically to engineering students. Engineering 101 contains information about all of the majors in the School of Engineering, including recommended first semester class schedules. You’ll also find out about some opportunities to join student groups. We hope that these materials help you learn about the Hopkins community and the options available to you. Again, welcome to Hopkins and we’ll see you in August! Linda Moulton, Denise Shipley, Lashell Silver, Eric Simmons, Janet Weise, and Betty Zee Johns Hopkins University Whiting School of Engineering Office of Academic Affairs—Engineering Advising Wyman Park Building Suite N125 3400 N. Charles Street Baltimore, MD 21218-2681 410-516-7395 [email protected] https://engineering.jhu.edu/advising/ Nondiscrimination Statement The Johns Hopkins University is committed to equal opportunity and providing a safe and non- discriminatory educational and working environment for its students, trainees, faculty, staff, post-doctoral fellows, residents, and other members of the University community. To that end, the university seeks to provide community members with an environment that is free from discrimination and harassment on the basis of sex, gender, marital status, pregnancy, race, color, ethnicity, national origin, age, disability, religion, sexual orientation, gender identity or expression, veteran status or other legally protected characteristic.
    [Show full text]
  • Mailman CLI Documentation Release 1
    Mailman CLI Documentation Release 1 Rajeev S September 26, 2014 Contents 1 mailman.client 3 1.1 Requirements...............................................3 1.2 Project details..............................................3 1.3 Documentation..............................................3 1.4 Acknowledgements...........................................3 1.5 Table of Contents.............................................4 i ii Mailman CLI Documentation, Release 1 This package is called mailman.client. Contents 1 Mailman CLI Documentation, Release 1 2 Contents CHAPTER 1 mailman.client The mailman.client library provides official Python bindings for the GNU Mailman 3 REST API. Note that the test suite current requires that a Mailman 3 server be running. It should be running using a dummy or throw-away database, as this will make changes to the running system. TBD: mock the real Mailman engine so that it is not necessary in order to run these tests. 1.1 Requirements mailman.client requires Python 2.6 or newer. 1.2 Project details You may download the latest version of the package from the Python Cheese Shop or from Launchpad. You can also install it via easy_install or pip.: % sudo easy_install mailman.client % sudo pip install mailman.client See the Launchpad project page for access to the Bazaar branch, bug report, etc. 1.3 Documentation A simple guide to using the library is available within this package, in the form of doctests. The manual is also available online in the Cheeseshop at: http://package.python.org/mailman.client 1.4 Acknowledgements Many thanks to Florian Fuchs for his contribution of an initial REST client. 3 Mailman CLI Documentation, Release 1 1.5 Table of Contents 1.5.1 Mailman REST client >>> import os >>> import time >>> import smtplib >>> import subprocess >>> from mock import patch This is the official Python bindings for the GNU Mailman REST API.
    [Show full text]
  • Usenet News HOWTO
    Usenet News HOWTO Shuvam Misra (usenet at starcomsoftware dot com) Revision History Revision 2.1 2002−08−20 Revised by: sm New sections on Security and Software History, lots of other small additions and cleanup Revision 2.0 2002−07−30 Revised by: sm Rewritten by new authors at Starcom Software Revision 1.4 1995−11−29 Revised by: vs Original document; authored by Vince Skahan. Usenet News HOWTO Table of Contents 1. What is the Usenet?........................................................................................................................................1 1.1. Discussion groups.............................................................................................................................1 1.2. How it works, loosely speaking........................................................................................................1 1.3. About sizes, volumes, and so on.......................................................................................................2 2. Principles of Operation...................................................................................................................................4 2.1. Newsgroups and articles...................................................................................................................4 2.2. Of readers and servers.......................................................................................................................6 2.3. Newsfeeds.........................................................................................................................................6
    [Show full text]
  • Ubuntu Server Guide Ubuntu Server Guide Copyright © 2010 Canonical Ltd
    Ubuntu Server Guide Ubuntu Server Guide Copyright © 2010 Canonical Ltd. and members of the Ubuntu Documentation Project3 Abstract Welcome to the Ubuntu Server Guide! It contains information on how to install and configure various server applications on your Ubuntu system to fit your needs. It is a step-by-step, task-oriented guide for configuring and customizing your system. Credits and License This document is maintained by the Ubuntu documentation team (https://wiki.ubuntu.com/DocumentationTeam). For a list of contributors, see the contributors page1 This document is made available under the Creative Commons ShareAlike 2.5 License (CC-BY-SA). You are free to modify, extend, and improve the Ubuntu documentation source code under the terms of this license. All derivative works must be released under this license. This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE AS DESCRIBED IN THE DISCLAIMER. A copy of the license is available here: Creative Commons ShareAlike License2. 3 https://launchpad.net/~ubuntu-core-doc 1 ../../libs/C/contributors.xml 2 /usr/share/ubuntu-docs/libs/C/ccbysa.xml Table of Contents 1. Introduction ........................................................................................................................... 1 1. Support .......................................................................................................................... 2 2. Installation ............................................................................................................................
    [Show full text]
  • (GNU Mailman) Mailing Lists
    Usability and efficiency improvements of the (GNU Mailman) mailing lists Rudy Borgstede ([email protected]) System and Network Engineering University of Amsterdam July 5, 2008 Versions Version Date Changes 0.0.1 18 May 2008 First setup of the report 0.0.2 9 June 2008 Release Candidate 1 of the project proposal 0.1.1 17 June 2008 A rewrite of the document because of the change of project result. The project will deliver an advice rather then a product like a patch or add-on for GNU Mailman. This means that the report becomes an consultancy report instead of a project proposal. 1.0.0 30 June 2008 Final version 1 of the report. 1.0.1 1 July 2008 A spelling check of the report. 1.0.2 5 July 2008 Extending the conclusion en future work chapters. Participants Name Contact Information University of Amsterdam Rudy Borgstede (Student) [email protected] Cees de Laat (Supervisor) [email protected] NLnet Michiel Leenaars (Supervisor) [email protected] Abstract This report is the result of a research project of four weeks at the NLnet Foundation1 in Amster- dam. The NLnet Foundation is a foundation who financially supports the open-source community and their projects. The purpose of the project is to improve the usability and the administration of the mailing lists (of the foundation) and giving a more clear view on mailing list server software to anyone who is interested in using mailing list server software or developing new mail or mail- ing list server software. The report describes the research of the usability of several open-source mailing list server software for scalable environments with several well known mail servers.
    [Show full text]
  • Werkstatt Open Source / Freie Software, Jahrestagung Der LEAH 20.08.2019 - Kurzscript
    Werkstatt Open Source / Freie Software, Jahrestagung der LEAH 20.08.2019 - Kurzscript Ablauf Werkstatt - Begrüßung, Vorstellung der Referenten, Kurz-Vorstellung der Teilnehmern, Erwartungen - Einstieg mit Kurzvideo “Die neugierige Bäckerin”: https://www.youtube.com/watch?v=wHo755bxByI - Impulsvortrag “Philosophische Sicht auf Software - Die Freie Software-Bewegung”. Was hat das mit Demokratie zu tun? / Richard Stallman / GNU/Linux - Zwei Übungen: 1) Softwareprogramme aussuchen, Lizenz ermitteln, Frei oder proprietär? 2) Teilnehmer mit Android-Smartphone: freien App-Katalog F-Droid finden, herunterladen, installieren. Dann damit weitere freie Apps installieren, z. B.: Zapp - für das öffentlich-rechtliche Fernsehen und Mediatheken Transportr - Zugriff auf Fahrpläne von öffentlichen Verkehrsmitteln weltweit - Konkrete Freie/OpenSource-Programme als Ersatz von proprietären Programmen (s. S. 3 / Flipchart) Ergänzungen zum Blatt zum Mitnehmen (nächste Seite), die sich durch Fragen oder Anregungen ergeben haben: - Bäckerei-Video: Privatsphären-Paradox: Psychologie: weil die Nachteile nicht sofort greifbar sind (und auch durch geschicktes Design nicht ins Bewusstsein gerückt werden) und sich außerdem in der Zukunft befinden, werden diese Nachteile viel weniger stark gewichtet als der sofortige Nutzen. Also wird die App installiert, obwohl man im realen Leben mit dem mangelnden Datenschutz nicht einverstanden wäre. - Warum wird proprietäre Software in sensiblen behördlichen Bereichen einsetzt, obwohl das offensichtliche Nachteile hat? -> ARD-Doku “Das Microsoft-Dilemma”, 2018, 45 min (gibt es online) - Sicherheit: “Wenn bei freier Software jeder mitmischen kann, wie kann das dann sicher sein?” -> Es gibt einen gemeinschaftlichen und öffentlichen Review-Prozess, wenn Code-Änderungen in den Hauptzweig der Software übernommen werden sollen. Alle Änderugen sind lückenlos nachvollziehbar. Durch diesen Entwicklungsprozess werden Sicherheitslücken schnell erkannt und behoben; Hintertüren werden erst gar nicht eingebaut.
    [Show full text]
  • Set up Mail Server Documentation 1.0
    Set Up Mail Server Documentation 1.0 Nosy 2014 01 23 Contents 1 1 1.1......................................................1 1.2......................................................2 2 11 3 13 3.1...................................................... 13 3.2...................................................... 13 3.3...................................................... 13 4 15 5 17 5.1...................................................... 17 5.2...................................................... 17 5.3...................................................... 17 5.4...................................................... 18 6 19 6.1...................................................... 19 6.2...................................................... 28 6.3...................................................... 32 6.4 Webmail................................................. 36 6.5...................................................... 37 6.6...................................................... 38 7 39 7.1...................................................... 39 7.2 SQL.................................................... 41 8 43 8.1...................................................... 43 8.2 strategy.................................................. 43 8.3...................................................... 44 8.4...................................................... 45 8.5...................................................... 45 8.6 Telnet................................................... 46 8.7 Can postfix receive?..........................................
    [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]
  • OSS Alphabetical List and Software Identification
    Annex: OSS Alphabetical list and Software identification Software Short description Page A2ps a2ps formats files for printing on a PostScript printer. 149 AbiWord Open source word processor. 122 AIDE Advanced Intrusion Detection Environment. Free replacement for Tripwire(tm). It does the same 53 things are Tripwire(tm) and more. Alliance Complete set of CAD tools for the specification, design and validation of digital VLSI circuits. 114 Amanda Backup utility. 134 Apache Free HTTP (Web) server which is used by over 50% of all web servers worldwide. 106 Balsa Balsa is the official GNOME mail client. 96 Bash The Bourne Again Shell. It's compatible with the Unix `sh' and offers many extensions found in 147 `csh' and `ksh'. Bayonne Multi-line voice telephony server. 58 Bind BIND "Berkeley Internet Name Daemon", and is the Internet de-facto standard program for 95 turning host names into IP addresses. Bison General-purpose parser generator. 77 BSD operating FreeBSD is an advanced BSD UNIX operating system. 144 systems C Library The GNU C library is used as the C library in the GNU system and most newer systems with the 68 Linux kernel. CAPA Computer Aided Personal Approach. Network system for learning, teaching, assessment and 131 administration. CVS A version control system keeps a history of the changes made to a set of files. 78 DDD DDD is a graphical front-end for GDB and other command-line debuggers. 79 Diald Diald is an intelligent link management tool originally named for its ability to control dial-on- 50 demand network connections. Dosemu DOSEMU stands for DOS Emulation, and is a linux application that enables the Linux OS to run 138 many DOS programs - including some Electric Sophisticated electrical CAD system that can handle many forms of circuit design.
    [Show full text]
  • An Overview of the Trilinos Project
    An Overview of the Trilinos Project MICHAEL A. HEROUX, ANDREW G. SALINGER, ROSCOE A. BARTLETT, HEIDI K. THORNQUIST, VICKI E. HOWLE, RAY S. TUMINARO, ROBERT J. HOEKSTRA, JAMES M. WILLENBRING, JONATHAN J. HU, and ALAN WILLIAMS TAMARA G. KOLDA, Sandia National Laboratories RICHARD B. LEHOUCQ, and KEVIN R. LONG, KENDALL S. STANLEY ROGER P. PAWLOWSKI, Oberlin College ERIC T. PHIPPS, The Trilinos Project is an effort to facilitate the design, development, integration, and ongoing support of mathematical software libraries within an object-oriented framework for the solution of large-scale, complex multiphysics engineering and scientific problems. Trilinos addresses two fun- damental issues of developing software for these problems: (i) providing a streamlined process and set of tools for development of new algorithmic implementations and (ii) promoting interoperability of independently developed software. Trilinos uses a two-level software structure designed around collections of packages.ATrilinos package is an integral unit usually developed by a small team of experts in a particular algorithms area such as algebraic preconditioners, nonlinear solvers, etc. Packages exist underneath the Trili- nos top level, which provides a common look-and-feel, including configuration, documentation, licensing, and bug-tracking. Here we present the overall Trilinos design, describing our use of abstract interfaces and default concrete implementations. We discuss the services that Trilinos provides to a prospective package Sandia is a multiprogram laboratory operated by Sandia Corporation, a Lockheed Martin Company, for the United States Department of Energy under Contract DE-AC04-94AL85000. Authors’ addresses: M. A. Heroux, R. A. Bartlett, R. J. Hoekstra, R. B. Lehoucq, R. P.
    [Show full text]
  • IP Addresses: Ipv4 and Ipv6
    Parallels® Plesk Panel Copyright Notice Parallels Holdings, Ltd. c/o Parallels International GmbH Vordergasse 59 CH-Schaffhausen Switzerland Phone: +41-526320-411 Fax: +41-52672-2010 Copyright © 1999-2011 Parallels Holdings, Ltd. and its affiliates. All rights reserved. This product is protected by United States and international copyright laws. The product’s underlying technology, patents, and trademarks are listed at http://www.parallels.com/trademarks. Microsoft, Windows, Windows Server, Windows NT, Windows Vista, and MS-DOS are registered trademarks of Microsoft Corporation. Linux is a registered trademark of Linus Torvalds. Mac is a registered trademark of Apple, Inc. All other marks and names mentioned herein may be trademarks of their respective owners. Contents Preface 8 Typographical Conventions ........................................................................................................... 8 Feedback ....................................................................................................................................... 9 Operating Inside Parallels Containers 10 What's New in Parallels Panel 12 Panel 10.4 ................................................................................................................................... 12 Panel 10.3 ................................................................................................................................... 15 Panel 10.2 ..................................................................................................................................
    [Show full text]