Die Open-Source-Softwareentwicklung als Best-Practice-Beispiel eines erfolgreichen Dienstleistungsnetzwerkes

2003 ◽  
pp. 613-639 ◽  
Author(s):  
Dodo zu Knyphausen-Aufseß ◽  
Leona Achtenhagen ◽  
Jörg Müller-Lietzkow
Keyword(s):  
Author(s):  
Philip M. Uys

<span>This paper analyses the change and innovation strategies that Charles Sturt University (CSU) used from 2007 to 2009 during the implementation and mainstreaming of an open source learning management system (LMS), Sakai, named locally as </span><em>CSU Interact</em><span>. CSU was in January 2008 the first Australian University to implement an open source learning management system institution wide. The unique characteristics of implementing change and innovation in higher education are discussed as well as CSU's change model, which comprises eight dimensions that can occur in any order and also in parallel, and is based on the work of Kotter, Cohen and Synnot. Two key strategies have emerged to support change, namely the building of learning communities and the sharing of best practice in implementing educational technology. Other findings were that the change was largely driven from the bottom up and with top management support and through the writer's role, from middle management in terms of top down strategies. Technological innovations in the context of an open source learning management system have wider, external implications than the local institution given the free flow of information and intellectual property within the community.</span>


2021 ◽  
Vol 58 (2) ◽  
pp. 271-287 ◽  
Author(s):  
Thomas Wilmer

ZusammenfassungDer folgende Artikel bietet einen Überblick über die häufigsten Anwendungsprobleme beim Einsatz und der Integration von freier und Open Source Software in der Praxis. Ein Schwerpunkt liegt dabei auf den Herausforderungen für Softwarehersteller, welche freie Software in ihre Produkte integrieren und vertreiben. Hingewiesen wird auf die unterschiedlichen freien Lizenzarten, Best Practice-Lösungsmöglichkeiten und Compliancefragen sowie die Grenzen der Auslegung der Lizenzen.


2021 ◽  
Author(s):  
Daniel Huppmann ◽  
Matthew Gidden

&lt;p&gt;&lt;strong&gt;Background: Transparency, reproducibility and reusability of scientific analysis&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;Researchers are now widely expected to share the data and source code of their work&amp;#160;to foster transparency, reproducibility and reusability.&lt;br&gt;Alas, the quality of data documentation and scientific software scripts&amp;#160;can vary substantially. In many instances, metadata and information on the provenance of data&amp;#160;are missing or incomplete, and source code often does not include a clear list of dependencies&amp;#160;(including version information) or systems requirements.&amp;#160;Finally, the source code does not include sufficient inline documentation&amp;#160;to be easily understood.&amp;#160;As a consequence, even though the data and related scripts may be released&amp;#160;under an open-source license, analysis too often cannot be reproduced or adapted&amp;#160;with reasonable effort by other researchers.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;The pyam package&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;This talk presents the open-source Python package &lt;strong&gt;pyam&lt;/strong&gt; for energy system scenario analysis&amp;#160;and visualization. The aim of pyam is not to provide any ground-breaking new methods&amp;#160;or analysis routines. Instead, it provides a reliable, well-tested interface&lt;br&gt;similar in feel &amp; style to the widely used &lt;strong&gt;pandas&lt;/strong&gt;&amp;#160;package,&amp;#160;but geared for data formats and applications often used in energy systems analysis&lt;br&gt;and integrated assessment modelling.&lt;/p&gt;&lt;p&gt;By using pyam for their scenario input data processing and analysis workflows,&amp;#160;researchers can reduce standard tasks like unit conversion and data validation&amp;#160;from a 5-minute effort to 30 seconds - and have the knowledge that their scripts&amp;#160;won't break if pandas or another dependency change their APIs,&amp;#160;because the pyam community will work to ensure forward-compatibility and continuity.&amp;#160;As another side benefit, the pyam package will raise meaningful errors when input data doesn't make sense,&amp;#160;whereas own ad-hoc scripts may fail silently or - even worse - return non-sensical values.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Spatial, temporal and sectoral aggregation &amp; downscaling features&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;To highlight the applicability of the pyam package for the EGU community&amp;#160;and energy &amp; climate modellers at large,&amp;#160;this talk will focus on the features for spatial, temporal and sectoral aggregation&amp;#160;and downscaling. The package include several often-used methods like weighting by&amp;#160;proxy variables or deriving indicators based on minimum or maximum values of timeseries data.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Building a community&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;The pyam package follows best-practice of version control, continuous-integration&amp;#160;and scientific-software documentation. This facilitates building on the package by&amp;#160;other researchers. The community uses several tools for communication and discussion, including a Slack channel, an email list and a Github repository for issues &amp; pull requests. And of course, we appreciate contributions by colleagues&amp;#160;to extend the scope of features and methods based on their own use cases and requirements!&lt;/p&gt;&lt;p&gt;&lt;strong&gt;More information&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;ReadTheDocs: https://pyam-iamc.readthedocs.io/&lt;br&gt;GitHub repo: https://github.com/iamconsortium/pyam&lt;/p&gt;


2012 ◽  
Vol 7 (2) ◽  
pp. 118
Author(s):  
Putu Wuri Handayani ◽  
Ultary Hariyaty

Penelitian ini bertujuan untuk menganalisis perbandingan fungsionalitas open source software ERP dalam pengembangan modul pembelajaran untuk proses bisnis penjualan, distribusi serta pengadaan. Penelitian ini membandingkan tiga OSS ERP yaitu Compiere 3.3 Community Edition, Openbravo 3.0 Community Edition, dan xTuple 3.6 PostBooks Edition. Kebutuhan functional masing-masing modul diturunkan dari proses bisnis best practice ERP. Hasil penelitian adalah suatu aplikasi yang direkomendasikan untuk mendukung kegiatan pembelajaran ERP di tingkat universitas dan daftar kebutuhan fungsionalitas yang dibutuhkan untuk modul pembelajaran, seperti modul penjualan dan distribusi serta modul pengadaan dengan menggunakan aplikasi yang direkomendasikan sebelumnya. This study aims to analyze the comparison of the functionality of open source ERP software in the development of learning modules for the business processes of sales, distribution and procurement. This study compared three OSS ERP that are Compiere Community Edition 3.3, Openbravo Community Edition 3.0, and 3.6 xTuple PostBooks Edition. Functional needs of each module is derived from best practice business processes ERP. Hasil penelitian adalah suatu aplikasi yang direkomendasikan untuk mendukung kegiatan pembelajaran ERP di tingkat universitas dan daftar kebutuhan fungsionalitas yang dibutuhkan untuk modul pembelajaran, seperti modul penjualan dan distribusi serta modul pengadaan dengan menggunakan aplikasi yang direkomendasikan sebelumnya.


2021 ◽  
Vol 17 (11) ◽  
pp. e1009481
Author(s):  
Haley Hunter-Zinck ◽  
Alexandre Fioravante de Siqueira ◽  
Váleri N. Vásquez ◽  
Richard Barnes ◽  
Ciera C. Martinez

Functional, usable, and maintainable open-source software is increasingly essential to scientific research, but there is a large variation in formal training for software development and maintainability. Here, we propose 10 “rules” centered on 2 best practice components: clean code and testing. These 2 areas are relatively straightforward and provide substantial utility relative to the learning investment. Adopting clean code practices helps to standardize and organize software code in order to enhance readability and reduce cognitive load for both the initial developer and subsequent contributors; this allows developers to concentrate on core functionality and reduce errors. Clean coding styles make software code more amenable to testing, including unit tests that work best with modular and consistent software code. Unit tests interrogate specific and isolated coding behavior to reduce coding errors and ensure intended functionality, especially as code increases in complexity; unit tests also implicitly provide example usages of code. Other forms of testing are geared to discover erroneous behavior arising from unexpected inputs or emerging from the interaction of complex codebases. Although conforming to coding styles and designing tests can add time to the software development project in the short term, these foundational tools can help to improve the correctness, quality, usability, and maintainability of open-source scientific software code. They also advance the principal point of scientific research: producing accurate results in a reproducible way. In addition to suggesting several tips for getting started with clean code and testing practices, we recommend numerous tools for the popular open-source scientific software languages Python, R, and Julia.


Author(s):  
M. Pscheidt ◽  
Th.P. van der Weide

The study is motivated by the context encountered in a development aid project with the aim to develop and implement an academic registration and information system (ARIS) for Mozambican universities. The ideas and findings presented here are based on a theoretical literature review in order to build a theoretical model of best practice in the context of North-South collaborations.


Author(s):  
ANDRÉ MARQUES PEREIRA ◽  
RAFAEL QUEIROZ GONÇALVES ◽  
CHRISTIANE GRESSE VON WANGENHEIM ◽  
LUIGI BUGLIONE

Software projects often fail, because they are not adequately managed. The establishment of effective and efficient project management practices still remains a key challenge to software organizations. Striving to address these needs, "best practice" models, such as, the Capability Maturity Model Integration (CMMI) or the Project Management Body of Knowledge (PMBOK), are being developed to assist organizations in improving project management. Although not required, software tools can help implement the project management process in practice. In order to provide comprehensive, low-cost tool support for project management, specifically, for small and medium enterprises (SMEs), in this paper we compare the most popular free/open-source web-based project management tools with respect to their compliance to PMBOK and CMMI for Development (CMMI-DEV). The results of this research can be used by organizations to make decisions on tool adoptions as well as a basis for evolving software tools in alignment with best practices models.


Atmosphere ◽  
2019 ◽  
Vol 10 (1) ◽  
pp. 17 ◽  
Author(s):  
Arsenios E. Chatzimichailidis ◽  
Christos D. Argyropoulos ◽  
Marc J. Assael ◽  
Konstantinos E. Kakosimos

Air pollution is probably the single largest environment risk to health and urban streets are the localized, relevant hotspots. Numerous studies reviewed the state-of-the-art models, proposed best-practice guidelines and explored, using various software, how different approaches (e.g., Reynolds-averaged Navier–Stokes (RANS), large eddy simulations (LES)) inter-compare. Open source tools are continuously attracting interest but lack of similar, extensive and comprehensive investigations. At the same time, their configuration varies significantly among the related studies leading to non-reproducible results. Therefore, the typical quasi-2D street canyon geometry was selected to employ the well-known open-source software OpenFOAM and to investigate and validate the main parameters affecting LES transient simulation of a pollutant dispersion. In brief, domain height slightly affected street level concentration but source height had a major impact. All sub-grid scale models predicted the velocity profiles adequately, but the k-equation SGS model best-resolved pollutant dispersion. Finally, an easily reproducible LES configuration is proposed that provided a satisfactory compromise between computational demands and accuracy.


2020 ◽  
Vol 25 (6) ◽  
pp. 5137-5192 ◽  
Author(s):  
Alexander Trautsch ◽  
Steffen Herbold ◽  
Jens Grabowski

Abstract Automated static analysis tools (ASATs) have become a major part of the software development workflow. Acting on the generated warnings, i.e., changing the code indicated in the warning, should be part of, at latest, the code review phase. Despite this being a best practice in software development, there is still a lack of empirical research regarding the usage of ASATs in the wild. In this work, we want to study ASAT warning trends in software via the example of PMD as an ASAT and its usage in open source projects. We analyzed the commit history of 54 projects (with 112,266 commits in total), taking into account 193 PMD rules and 61 PMD releases. We investigate trends of ASAT warnings over up to 17 years for the selected study subjects regarding changes of warning types, short and long term impact of ASAT use, and changes in warning severities. We found that large global changes in ASAT warnings are mostly due to coding style changes regarding braces and naming conventions. We also found that, surprisingly, the influence of the presence of PMD in the build process of the project on warning removal trends for the number of warnings per lines of code is small and not statistically significant. Regardless, if we consider defect density as a proxy for external quality, we see a positive effect if PMD is present in the build configuration of our study subjects.


Sign in / Sign up

Export Citation Format

Share Document