DOCSLIB.ORG

[Scale=0.250]Images/Logoidl Forge : Concept Et Utilisation [Scale

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
[Scale=0.250]Images/Logoidl Forge : Concept Et Utilisation [Scale Le concept Les fonctionnalit´es Les produits disponibles Les forges utilis´ees Forge : Concept et utilisation [email protected] INRA-MIA 9 d´ecembre 2011 1 [email protected] INRA MIA BioSP / PEPI - Ecole´ IDL 2011 Le concept Les fonctionnalit´es Les produits disponibles Les forges utilis´ees Pr´eambule principales sources de ce topo projet-plume.org/ressource/faq-forge FusionForge User guide portail fusionforge 2 [email protected] INRA MIA BioSP / PEPI - Ecole´ IDL 2011 Le concept Les fonctionnalit´es Exemples Les produits disponibles D´efinition Les forges utilis´ees 3 [email protected] INRA MIA BioSP / PEPI - Ecole´ IDL 2011 Le concept Les fonctionnalit´es Exemples Les produits disponibles D´efinition Les forges utilis´ees 4 [email protected] INRA MIA BioSP / PEPI - Ecole´ IDL 2011 Le concept Les fonctionnalit´es Exemples Les produits disponibles D´efinition Les forges utilis´ees 5 [email protected] INRA MIA BioSP / PEPI - Ecole´ IDL 2011 Le concept Les fonctionnalit´es Exemples Les produits disponibles D´efinition Les forges utilis´ees 6 [email protected] INRA MIA BioSP / PEPI - Ecole´ IDL 2011 Le concept Les fonctionnalit´es Exemples Les produits disponibles D´efinition Les forges utilis´ees 7 [email protected] INRA MIA BioSP / PEPI - Ecole´ IDL 2011 qui permet ´egalement aux diff´erentes communaut´es d'utilisateurs des logiciels d'acc´eder aux sources, aux executables, aux documentations et informations diverses qui offre un espace d'´echange entre utilisateurs et concepteurs d'un projet informatique il s'appui sur une interface Web Le concept Les fonctionnalit´es Exemples Les produits disponibles D´efinition Les forges utilis´ees D´efinition Une forge est un outil collaboratif qui permet `aplusieurs d´eveloppeurs de participer ensemble au d´eveloppement de logiciels, 8 [email protected] INRA MIA BioSP / PEPI - Ecole´ IDL 2011 qui offre un espace d'´echange entre utilisateurs et concepteurs d'un projet informatique il s'appui sur une interface Web Le concept Les fonctionnalit´es Exemples Les produits disponibles D´efinition Les forges utilis´ees D´efinition Une forge est un outil collaboratif qui permet `aplusieurs d´eveloppeurs de participer ensemble au d´eveloppement de logiciels, qui permet ´egalement aux diff´erentes communaut´es d'utilisateurs des logiciels d'acc´eder aux sources, aux executables, aux documentations et informations diverses 8 [email protected] INRA MIA BioSP / PEPI - Ecole´ IDL 2011 il s'appui sur une interface Web Le concept Les fonctionnalit´es Exemples Les produits disponibles D´efinition Les forges utilis´ees D´efinition Une forge est un outil collaboratif qui permet `aplusieurs d´eveloppeurs de participer ensemble au d´eveloppement de logiciels, qui permet ´egalement aux diff´erentes communaut´es d'utilisateurs des logiciels d'acc´eder aux sources, aux executables, aux documentations et informations diverses qui offre un espace d'´echange entre utilisateurs et concepteurs d'un projet informatique 8 [email protected] INRA MIA BioSP / PEPI - Ecole´ IDL 2011 Le concept Les fonctionnalit´es Exemples Les produits disponibles D´efinition Les forges utilis´ees D´efinition Une forge est un outil collaboratif qui permet `aplusieurs d´eveloppeurs de participer ensemble au d´eveloppement de logiciels, qui permet ´egalement aux diff´erentes communaut´es d'utilisateurs des logiciels d'acc´eder aux sources, aux executables, aux documentations et informations diverses qui offre un espace d'´echange entre utilisateurs et concepteurs d'un projet informatique il s'appui sur une interface Web 8 [email protected] INRA MIA BioSP / PEPI - Ecole´ IDL 2011 pas d'aide `al'analyse fonctionnelle et la sp´ecification pas de gantt ou autre Quoique ... Une forge peut offrir quelques indicateurs Activit´es, Suivis des bugs, des demandes de fonctionnalit´es ... Le concept Les fonctionnalit´es Exemples Les produits disponibles D´efinition Les forges utilis´ees D´efinition Une forge n'est pas un outil de management de projet pas fait pour le recueil des besoins 9 [email protected] INRA MIA BioSP / PEPI - Ecole´ IDL 2011 pas de gantt ou autre Quoique ... Une forge peut offrir quelques indicateurs Activit´es, Suivis des bugs, des demandes de fonctionnalit´es ... Le concept Les fonctionnalit´es Exemples Les produits disponibles D´efinition Les forges utilis´ees D´efinition Une forge n'est pas un outil de management de projet pas fait pour le recueil des besoins pas d'aide `al'analyse fonctionnelle et la sp´ecification 9 [email protected] INRA MIA BioSP / PEPI - Ecole´ IDL 2011 Quoique ... Une forge peut offrir quelques indicateurs Activit´es, Suivis des bugs, des demandes de fonctionnalit´es ... Le concept Les fonctionnalit´es Exemples Les produits disponibles D´efinition Les forges utilis´ees D´efinition Une forge n'est pas un outil de management de projet pas fait pour le recueil des besoins pas d'aide `al'analyse fonctionnelle et la sp´ecification pas de gantt ou autre 9 [email protected] INRA MIA BioSP / PEPI - Ecole´ IDL 2011 Une forge peut offrir quelques indicateurs Activit´es, Suivis des bugs, des demandes de fonctionnalit´es ... Le concept Les fonctionnalit´es Exemples Les produits disponibles D´efinition Les forges utilis´ees D´efinition Une forge n'est pas un outil de management de projet pas fait pour le recueil des besoins pas d'aide `al'analyse fonctionnelle et la sp´ecification pas de gantt ou autre Quoique ... 9 [email protected] INRA MIA BioSP / PEPI - Ecole´ IDL 2011 Une forge peut offrir quelques indicateurs Activit´es, Suivis des bugs, des demandes de fonctionnalit´es ... Le concept Les fonctionnalit´es Exemples Les produits disponibles D´efinition Les forges utilis´ees D´efinition Une forge n'est pas un outil de management de projet pas fait pour le recueil des besoins pas d'aide `al'analyse fonctionnelle et la sp´ecification pas de gantt ou autre Quoique ... 9 [email protected] INRA MIA BioSP / PEPI - Ecole´ IDL 2011 Le concept Les fonctionnalit´es Exemples Les produits disponibles D´efinition Les forges utilis´ees D´efinition Une forge n'est pas un outil de management de projet pas fait pour le recueil des besoins pas d'aide `al'analyse fonctionnelle et la sp´ecification pas de gantt ou autre Quoique ... Une forge peut offrir quelques indicateurs Activit´es, Suivis des bugs, des demandes de fonctionnalit´es ... 9 [email protected] INRA MIA BioSP / PEPI - Ecole´ IDL 2011 Le concept Les fonctionnalit´es pour le projet Les produits disponibles pour l'utilisateur Les forges utilis´ees 10 [email protected] INRA MIA BioSP / PEPI - Ecole´ IDL 2011 Le concept Les fonctionnalit´es pour le projet Les produits disponibles pour l'utilisateur Les forges utilis´ees 11 [email protected] INRA MIA BioSP / PEPI - Ecole´ IDL 2011 Administration du projet : choix fonctionnels choix des outils : syst`eme de gestion de version, mails-lists, wiki, forums ... r^ole des membres du projet : admin, junior or senior developper, doc writer activit´e historique statistiques Le concept Les fonctionnalit´es pour le projet Les produits disponibles pour l'utilisateur Les forges utilis´ees Gestion de projet Administration du projet : informations factuelles cr´eation et description du projet, objectifs, licence, visibilit´e,mode de partage, ... organisation en cat´egories d´efinition des groupes de d´eveloppeurs (r^oles) 12 [email protected] INRA MIA BioSP / PEPI - Ecole´ IDL 2011 activit´e historique statistiques Le concept Les fonctionnalit´es pour le projet Les produits disponibles pour l'utilisateur Les forges utilis´ees Gestion de projet Administration du projet : informations factuelles cr´eation et description du projet, objectifs, licence, visibilit´e,mode de partage, ... organisation en cat´egories d´efinition des groupes de d´eveloppeurs (r^oles) Administration du projet : choix fonctionnels choix des outils : syst`eme de gestion de version, mails-lists, wiki, forums ... r^ole des membres du projet : admin, junior or senior developper, doc writer 12 [email protected] INRA MIA BioSP / PEPI - Ecole´ IDL 2011 Le concept Les fonctionnalit´es pour le projet Les produits disponibles pour l'utilisateur Les forges utilis´ees Gestion de projet Administration du projet : informations factuelles cr´eation et description du projet, objectifs, licence, visibilit´e,mode de partage, ... organisation en cat´egories d´efinition des groupes de d´eveloppeurs (r^oles) Administration du projet : choix fonctionnels choix des outils : syst`eme de gestion de version, mails-lists, wiki, forums ... r^ole des membres du projet : admin, junior or senior developper, doc writer activit´e historique statistiques 12 [email protected] INRA MIA BioSP / PEPI - Ecole´ IDL 2011 Le concept Les fonctionnalit´es pour le projet Les produits disponibles pour l'utilisateur Les forges utilis´ees 13 [email protected] INRA MIA BioSP / PEPI - Ecole´ IDL 2011 Le concept Les fonctionnalit´es pour le projet Les produits disponibles pour l'utilisateur Les forges utilis´ees 14 [email protected] INRA MIA BioSP / PEPI - Ecole´ IDL 2011 Le concept Les fonctionnalit´es pour le projet Les produits disponibles pour l'utilisateur Les forges utilis´ees Gestion du code source CVS, SVN, Git, ... aide `ala configuration des clients Source Code Management visualisation du code avec ViewVC (SVN) 15 [email protected] INRA MIA BioSP / PEPI - Ecole´ IDL 2011 Le concept Les fonctionnalit´es pour le projet Les produits disponibles pour l'utilisateur Les forges utilis´ees 16 [email protected] INRA MIA BioSP / PEPI - Ecole´ IDL 2011 Le concept Les fonctionnalit´es pour le projet Les produits disponibles pour l'utilisateur Les forges utilis´ees trackers collecteurs de retours d'informations et de demandes Syst`eme g´en´erique qui permet de collecter et de redistribuer les diff´erents retours des utilisateurs vers les d´eveloppeurs pour les prendre en charge.
Load more

Recommended publications
  • Gestión De Proyectos Software
    Proyecto Fin de Carrera AITForge: Gestión de Proyectos Software Autor: Antonio Domingo Lagares Alfaro Titulación: Ingeniero de Telecomunicación (Plan 98) Especialidad: Telemática Año: 2005 Tutor: Antonio Estepa Alonso AITForge: Gestión de Proyectos Software Índice de contenido 1 Prefacio..................................................................................................................6 2 Portales de Desarrollo Colaborativo......................................................................7 2.1 Introducción a los Entornos Colaborativos....................................................8 2.1.1 Hosting de Proyectos de Software Libre (FOSPHost)...........................9 2.1.2 ¿Software Libre y Software de Fuentes Abiertas?...............................10 2.1.3 Prácticas deseables en Software Libre................................................11 2.1.4 El nacimiento de una nueva filosofía de trabajo...................................13 2.1.5 Objetivos de los sistemas libres de FOSPHost....................................14 2.1.6 Principales características de los sistemas FOSPHost........................16 Características intrínsecas..........................................................................16 Características de utilidad...........................................................................17 Características de usabilidad......................................................................18 Características contextuales.......................................................................19 2.1.7
    [Show full text]
  • Free Software Needs Free Tools
    Free Software Needs Free Tools Benjamin Mako Hill [email protected] June 6, 2010 Over the last decade, free software developers have been repeatedly tempted by devel- opment tools that offer the ability to build free software more efficiently or powerfully. The only cost, we are told, is that the tools themselves are nonfree or run as network services with code we cannot see, copy, or run ourselves. In their decisions to use these tools and services – services such as BitKeeper, SourceForge, Google Code and GitHub – free software developers have made “ends-justify-the-means” decisions that trade away the freedom of both their developer communities and their users. These decisions to embrace nonfree and private development tools undermine our credibility in advocating for soft- ware freedom and compromise our freedom, and that of our users, in ways that we should reject. In 2002, Linus Torvalds announced that the kernel Linux would move to the “Bit- Keeper” distributed version control system (DVCS). While the decision generated much alarm and debate, BitKeeper allowed kernel developers to work in a distributed fashion in a way that, at the time, was unsupported by free software tools – some Linux developers decided that benefits were worth the trade-off in developers’ freedom. Three years later the skeptics were vindicated when BitKeeper’s owner, Larry McVoy, revoked several core kernel developers’ gratis licenses to BitKeeper after Andrew Tridgell attempted to write a free replacement for BitKeeper. Kernel developers were forced to write their own free software replacement: the project now known as Git. Of course, free software’s relationships to nonfree development tools is much larger than BitKeeper.
    [Show full text]
  • This Book Doesn't Tell You How to Write Faster Code, Or How to Write Code with Fewer Memory Leaks, Or Even How to Debug Code at All
    Practical Development Environments By Matthew B. Doar ............................................... Publisher: O'Reilly Pub Date: September 2005 ISBN: 0-596-00796-5 Pages: 328 Table of Contents | Index This book doesn't tell you how to write faster code, or how to write code with fewer memory leaks, or even how to debug code at all. What it does tell you is how to build your product in better ways, how to keep track of the code that you write, and how to track the bugs in your code. Plus some more things you'll wish you had known before starting a project. Practical Development Environments is a guide, a collection of advice about real development environments for small to medium-sized projects and groups. Each of the chapters considers a different kind of tool - tools for tracking versions of files, build tools, testing tools, bug-tracking tools, tools for creating documentation, and tools for creating packaged releases. Each chapter discusses what you should look for in that kind of tool and what to avoid, and also describes some good ideas, bad ideas, and annoying experiences for each area. Specific instances of each type of tool are described in enough detail so that you can decide which ones you want to investigate further. Developers want to write code, not maintain makefiles. Writers want to write content instead of manage templates. IT provides machines, but doesn't have time to maintain all the different tools. Managers want the product to move smoothly from development to release, and are interested in tools to help this happen more often.
    [Show full text]
  • Introducting Innovations in Open Source Projects
    Introducing Innovations into Open Source Projects Dissertation zur Erlangung des Grades eines Doktors der Naturwissenschaften (Dr. rer. nat.) am Fachbereich Mathematik und Informatik der Freien Universität Berlin von Sinan Christopher Özbek Berlin August 2010 2 Gutachter: Professor Dr. Lutz Prechelt, Freie Universität Berlin Professor Kevin Crowston, Syracuse University Datum der Disputation: 17.12.2010 4 Abstract This thesis presents a qualitative study using Grounded Theory Methodology on the question of how to change development processes in Open Source projects. The mailing list communication of thirteen medium-sized Open Source projects over the year 2007 was analyzed to answer this question. It resulted in eight main concepts revolving around the introduction of innovation, i.e. new processes, services, and tools, into the projects including topics such as the migration to new systems, the question on where to host services, how radical Open Source projects can change their ways, and how compliance to processes and conventions is enforced. These are complemented with (1) the result of five case studies in which innovation introductions were conducted with Open Source projects, and with (2) a theoretical comparison of the results of this thesis to four theories and scientific perspectives from the organizational and social sciences such as Path Dependence, the Garbage Can model, Social-Network analysis, and Actor-Network theory. The results show that innovation introduction is a multifaceted phenomenon, of which this thesis discusses the most salient conceptual aspects. The thesis concludes with practical advice for innovators and specialized hints for the most popular innovations. 5 6 Acknowledgements I want to thank the following individuals for contributing to the completion of this thesis: • Lutz Prechelt for advising me over these long five years.
    [Show full text]
  • Increase in Efficiency of Free Software Projects Through Information
    Increase in efficiency of free software projects through information management Robert Schuster Working group Software Engineering Freie Universität Berlin 2005-05-17 Abstract Free and Open Source Software is an enduring undertaking. How- ever this does not mean that this development model has no flaws. This paper will present a problem of the F/OSS development pro- cess that results from insufficient care for information management. I will outline the factors that lead to this problem and propose a light- weight process enhancement to cope with it. This enhancement will 1 introduce a role named “mediator” - a person whose task it is to make it easier for new developers to enter the project and support the knowledge transfer between developers. The role is then imple- mented in the project GNU Classpath and evaluated by it's develop- ers with the help of a survey. The key aspects of mediation are sum- marized and abstracted in form of a short manual which is targetted for use by any F/OSS project. Contents 1 Introduction 3 1.1 Disambiguation . 4 1.2 Categories and conditions of F/OSS projects . 5 1.2.1 Categories . 5 1.2.2 Environment and conditions . 8 1.2.3 Definition of success . 11 2 Introducing mediation 13 2.1 Which difficulties exist? . 13 2.2 The idea of mediation . 13 2.3 Selected tasks . 14 2.4 Project properties supporting the success of the mediation role . 15 2.5 Related works . 16 3 Implementing the mediator 18 3.1 Introduction to GNU Classpath . 18 3.2 Why GNU Classpath has been chosen for exemplifying me- diation .
    [Show full text]
  • Software Studies: a Lexicon, Edited by Matthew Fuller, 2008
    fuller_jkt.qxd 4/11/08 7:13 AM Page 1 ••••••••••••••••••••••••••••••••••••• •••• •••••••••••••••••••••••••••••••••• S •••••••••••••••••••••••••••••••••••••new media/cultural studies ••••software studies •••••••••••••••••••••••••••••••••• ••••••••••••••••••••••••••••••••••••• •••• •••••••••••••••••••••••••••••••••• O ••••••••••••••••••••••••••••••••••••• •••• •••••••••••••••••••••••••••••••••• ••••••••••••••••••••••••••••••••••••• •••• •••••••••••••••••••••••••••••••••• F software studies\ a lexicon ••••••••••••••••••••••••••••••••••••• •••• •••••••••••••••••••••••••••••••••• ••••••••••••••••••••••••••••••••••••• •••• •••••••••••••••••••••••••••••••••• T edited by matthew fuller Matthew Fuller is David Gee Reader in ••••••••••••••••••••••••••••••••••••• •••• •••••••••••••••••••••••••••••••••• This collection of short expository, critical, Digital Media at the Centre for Cultural ••••••••••••••••••••••••••••••••••••• •••• •••••••••••••••••••••••••••••••••• W and speculative texts offers a field guide Studies, Goldsmiths College, University of to the cultural, political, social, and aes- London. He is the author of Media ••••••••••••••••••••••••••••••••••••• •••• •••••••••••••••••••••••••••••••••• thetic impact of software. Computing and Ecologies: Materialist Energies in Art and A digital media are essential to the way we Technoculture (MIT Press, 2005) and ••••••••••••••••••••••••••••••••••••• •••• •••••••••••••••••••••••••••••••••• work and live, and much has been said Behind the Blip: Essays on the Culture of •••••••••••••••••••••••••••••••••••••
    [Show full text]
  • The Lcg Savannah Software Development Portal
    THE LCG SAVANNAH SOFTWARE DEVELOPMENT PORTAL Y. Perrin, D. Feichtinger#1, F. Orellana#2, CERN, Geneva, Switzerland, M. Roy, FSF France Abstract A web portal has been developed, in the context of ORGANIZATION AND the LCG/SPI project, in order to coordinate workflow FUNCTIONALITY and manage information in large software projects. It is LCG Savannah is organized in projects which are a development of the GNU Savannah package and grouped according to their type as entered at offers a range of services to every hosted project: Bug / registration time. All projects of the same type inherit a support / patch trackers, a simple task planning system, number of common characteristics and default values news threads, and a download area for software with, of course, the possibility to define new types and releases. Features and functionality can be fine-tuned to override the defaults for any given project. on a per project basis and the system displays content LCG Savannah should be seen as a development and grants permissions according to the user's status front-end for every project it hosts. It provides, in a (project member, other Savannah user, or visitor). A fully configurable and integrated way, the main highly configurable notification system is able to functions required by any significant software channel tracker submissions to developers in charge of development project. These include bug and support specific project modules. request tracking, task management, automatic The portal is based on the GNU Savannah package notification of people concerned, access to CVS which is now developed as 'Savane' with the support of repository, download area, news and mailing lists.
    [Show full text]
  • (RES) Architecture Study
    Reuse Enablement System (RES) Architecture Study Prepared by: NASA Earth Science Data Systems – Software Reuse Working Group July 23, 2007 Updated February 14, 2008 Earth Science Data Systems Software Reuse Working Group Editor: James Marshall (Innovim / NASA Goddard Space Flight Center) Contributing Working Group Members: Angelo Bertolli (Innovim / NASA Goddard Space Flight Center) Nancy Casey (Science Systems and Applications, Inc. / NASA Goddard Space Flight Center) Bradford Castalia (University of Arizona) Victor Delnore * (NASA Langley Research Center) Robert R. Downs (Columbia University / NASA Socioeconomic Data and Applications Center) Ryan Gerard (Innovim / NASA Goddard Space Flight Center) Mary Hunter (Innovim / NASA Goddard Space Flight Center) Shahin Samadi (Innovim / NASA Goddard Space Flight Center) Mark Sherman (SGT Inc. / NASA Goddard Space Flight Center) Ross Swick (National Snow and Ice Data Center, University of Colorado – Boulder) Curt Tilmes (NASA Goddard Space Flight Center) Robert Wolfe * (NASA Goddard Space Flight Center) * Co-chair Working Group Participants: Nadine Alameh (MobiLaps LLC) Howard Burrows (Autonomous Undersea Systems Institute / National Science Digital Library) Yonsook Enloe (SGT Inc. / NASA Goddard Space Flight Center) Stefan Falke (Washington University in St. Louis) Michael Folk (National Center for Supercomputing Applications) Emily Greene (Raytheon Company) Tommy Jasmin (University of Wisconsin-Madison, Space Science and Engineering Center) Steve Olding (Everware / NASA Goddard Space Flight Center) Bill Teng (Science Systems and Applications, Inc. / NASA Goddard Space Flight Center) Fred Watson (California State University, Monterey Bay) Acknowledgements: Michael Chyatte (Computer Science Corporation / NASA Goddard Space Flight Center) – SourceMotel site running GForge Thomas Clune (NASA Goddard Space Flight Center) – SourceMotel site running GForge Kathy Fontaine (NASA Goddard Space Flight Center) – Earth Science Data System Working Group Coordinator Gene Major (Science Systems and Applications, Inc.
    [Show full text]
  • PDF File (440K Characters)
    GNU Rush – a restricted user shell version 2.1, 1 July 2019 Sergey Poznyakoff Published by the Free Software Foundation, 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Copyright c 2008-2019 Sergey Poznyakoff Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sec- tions, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled “GNU Free Documentation License”. i Short Contents 1 Introduction .......................................... 1 2 Operation............................................ 3 3 Quick Start .......................................... 5 4 Configuration File ..................................... 7 5 Default Configuration ................................. 37 6 Usage Tips .......................................... 39 7 Test Mode .......................................... 45 8 Option Summary ..................................... 47 9 The rushwho utility. .................................. 49 10 The rushlast utility. ................................. 53 11 Accounting Database.................................. 55 12 How to Report a Bug ................................. 57 A Time and Date Formats ............................... 59 B GNU Free Documentation License ....................... 63 Concept Index ........................................... 73 iii Table of Contents 1 Introduction ....................................
    [Show full text]
  • User-Driven Development for Bespoke Software
    User-Driven Development for Bespoke Software Tryggvi Björgvinsson Dissertation submitted in partial fulfillment of a Philosophiae Doctor degree in Software Engineering Supervisor Dr. Helgi Þorbergsson, University of Iceland Doctoral Committee Dr. Helgi Þorbergsson, University of Iceland Dr. Helmut Neukirchen, University of Iceland Dr. Mathias Klang, University of Gothenburg Opponents Dr. Pekka Abrahamsson, Free University of Bozen-Bolzano Dr. Finn Kensing, University of Copenhagen Faculty of Industrial Engineering, Mechanical Engineering and Computer Science School of Engineering and Natural Sciences University of Iceland Reykjavik, January 2013 User-Driven Development for Bespoke Software Dissertation submitted in partial fulfillment of a Philosophiae Doctor degree in Software Engineering Copyright 2013 Tryggvi Björgvinsson This work is licensed under the Creative Commons Attribution-ShareAlike 3.0 Unported License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/3.0/. Faculty of Industrial Engineering, Mechanical Engineering and Computer Science School of Engineering and Natural Sciences University of Iceland Hjarðarhagi 2--6 107 Reykjavík Iceland Telephone: 525 4700 Bibliographic information: Tryggvi Björgvinsson, 2013, User-Driven Development for Bespoke Software, PhD dissertation, Faculty of Industrial Engineering, Mechanical Engineering and Computer Science, University of Iceland. ISBN 978-9935-9069-6-0 Printing: Háskólaprent Reykjavik, Iceland, January 2013 To my mother, Björk Tryggvadóttir, and father, Björgvin Magnússon. Without your support I would never have gotten this far. Abstract Software engineering as a discipline has for the last few decades tried to tackle the problem of software project failures. A software engineer's arsenal consists of various methods and tech- niques applicable to the plethora of different software projects.
    [Show full text]
  • Increasing the Efficiency of Free Software Projects Through
    Increasing the efficiency of free software projects through information management Robert Schuster Advisor: Christopher Oezbek, Prof. Dr. Lutz Prechelt, Working group Software Engineering Freie Universität Berlin 2005-09-06 Abstract Free and Open Source Software is a permanent undertaking. However this does not mean that this development model has no flaws. This paper will present a problem of the F/OSS development process that results from insufficient care for information management. It will outline the factors that lead to this problem and proposes a light-weight process enhancement to cope with it. This enhancement will introduce a role named “mediator” - a person whose task it is to make it easier for new developers to enter the project and support the knowledge transfer between developers. The role is then implemented in the project GNU Classpath and evalu- ated by it's developers with the help of a survey. The key aspects of mediation are summarized and abstracted in form of a short manual which is targetted to be used by any F/OSS project. 1 Contents 1 Introduction 4 1.1 Free Software or Open Source . 5 1.2 Categories and conditions of F/OSS projects . 5 1.2.1 Categories . 5 1.2.2 Environment and conditions . 7 1.2.3 Definition of success . 9 2 Introducing mediation 11 2.1 Which difficulties exist? . 11 2.2 The idea of mediation . 12 2.3 Goals and tasks of the mediator . 12 2.3.1 Guidelines for the daily work . 13 2.4 Project properties supporting the success of the mediation role .
    [Show full text]
  • Integracija Softverskih Razvojnih Okruženja Sa On-Line Repozitorijumima Programskog Koda
    Univerzitet u Novom Sadu Tehnički fakultet “Mihajlo Pupin” Zrenjanin Integracija softverskih razvojnih okruženja sa on-line repozitorijumima programskog koda Integration of software development environments with on-line code repositories MASTER RAD Predmetni nastavnik: Student: Prof.dr. Ljubica Kazi Dragana Ljubinković MIT 12/2017 Smer: Informacione tehnologije - master Zrenjanin, 2018. Univerzitet u Novom Sadu Tehnički fakultet „Mihajlo Pupin” Zrenjanin Ključna dokumentacijska informacija Redni broj: RBR Identifikacioni broj: IBR Tip dokumentacije: Monografska dokumentacija TD Tip zapisa: Tekstualni štampani dokument TZ Vrsta rada: (dipl.mag.dokt.): Master rad VR Ime i prezime autora: Ljubinković Dragana AU Mentor (titular, ime, prezime, zvanje): Doc. dr Ljubica Kazi MN Naslov rada: Integracija softverskih razvojnih okruženja sa on- NS line repozitorijumima programskog koda Jezik publikacije: Srpski JZ Jezik izvoda: Srpski/Engleski JI Zemlja publikovanja: Republika Srbija ZP Uže geografsko područje: Zrenjanin, Vojvodina UGP Godina: 2019. GO Izdavač: Autorski reprint IZ Mesto i adresa: Tehnički fakultet “Mihajlo Pupin”, Đure MS Đakovića bb, Zrenjanin Fizički opis rada: Broj poglavlja 6/ Strana 70/ Slika FO 30/ Listinga 2/ Naučna oblast: Informacione tehnologije – master OB Naučna disciplina: Distribuirani informacioni sistemi ND Predmetna odrednica, ključne reči: Biblioteka Tehničkog fakulteta PO „Mihajlo Pupin“ Zrenjanin UDK Čuva se: ČU Važna napomena: VN Izvod: U ovom radu teorijski je prikazan način rada IZ online repozitorijuma koda. U odeljku stručnog istraživanja prikazane su opšte osobine repozitorijuma koda, načini instalacije, zašto se koriste, kao i definicije srodnih termina koji se koriste. U praktičnom delu rada prikazani su konkretni primeri rada određenih repozitoijuma koda, način upotrebe i njihove glavne karakteristike. Posebno je analiziran aspekt integracije alata za razvoj softvera sa on-line repozitorijumima koda.
    [Show full text]