In conjunction with the Software Engineering Conference 2018 in Ulm, March 6, 2018
The number of students continuously increases and presents ever greater challenges for instructors in software engineering. In courses with a huge number of students, it is particularly difficult to motivate students to actively participate. At the same time, practice-oriented and project-related training is becoming increasingly important, but project courses in cooperation with industry are often associated with high costs.
Digital teaching, online courses and new teaching concepts complement the curriculum. They offer a wide range of possibilities for modern and attractive teaching, but pose methodical, technical and organizational challenges for instructors.
Continue reading “Call for Papers: 1st Workshop on Innovative Software Engineering Education (ISEE 2018)”
In conjunction with Software Engineering 2018
Ulm, March 6, 2018
Scope of the workshop
In order to develop and deliver high-quality products to their customers, software companies have to adopt state-of-the-art software development processes. To face this challenge, companies are applying innovative methods, approaches and techniques like agile methods, DevOps, Continuous Delivery, test automation, infrastructure as code or container-based virtualization.
Continue reading “Call for Papers: 3rd Workshop on Continuous Software Engineering (CSE 2018)”
A friend’s post alerted me to the potential overreach of copyright and commercial law when it comes to the human body. The particular post was about tattoo artists who tried to make money of sport professionals who had integrated the tattoos into their professional persona: The company who had bought the tattoo artists’ designs claims that the copyright to the art extends to the performances of professionals showing the art. Hence they wanted money for any performance, here as part of the professionals appearing in video games.
It is easy to extend this to high-tech. The consequences could be dire, if the enhanced human body would become subject to overreaching intellectual property rights held by companies. Imagine a pacemaker for your heart that has only been licensed to you and you lack the necessary data and rights to make it work over time. I’m sure some company will come up with a pacemaker that needs to get a license key every year or so from the company’s license server. Would the company let the person die, if he or she fails to pay the annual license fee? In case you wonder whether anyone would accept such a pacemaker into their heart (pun intended): Just imagine being poor enough to not be able to pay for the medical procedure. Or imagine requiring a particularly innovative pacemaker function that only this one manufacturer offers and you can’t pay for the perpetual license.
If this seems far-fetched, you should note that this is already happening in other contexts. For example, John Deere, a leading manufacturer of tractors and other farming equipment is only leasing its tractors and the software to farmers. John Deere argues that farmers don’t own the tractor and its data any longer, John Deere remains the owner. As a consequence, all data from the farmers’ tractors is planned to end up in John Deere data centers and farmers who don’t keep paying might be cut of their equipment and its data.
The Internet and interconnectedness is making it happen. It is indeed time to clarify ownership and limits of ownership, in particular when it comes to the human body and its rights. Indeed an interesting time for lawyers (and everyone else).
I recently participated in an NII Shonan workshop on open source ecosystems. As a follow-up, we are preparing a book of articles. I’m contributing a chapter on “license clearance in software product governance”. Obviously, open source plays an important role. Please find abstract and paper below.
Abstract: Almost all software products today include open source components. However, the obligations that open source licenses put on their users can be difficult or undesirable to comply with   . As a consequence, software vendors and related companies need to govern the process by which open source components are included in their products  . A key process of such open source governance is license clearance, that is, the process by which a company decides whether a particular component’s license is acceptable for use in its products   . In this article, we discuss this process, review the challenges it poses to software vendors and provide unanswered research questions that result from it.
Read the full paper as HTML or as a PDF. The final reference will be announced once the book has been published.
About two years back, I bought a Seagate Backup Plus Slim 2 TB external 2.5 inch harddrive. I love it! So much so, that I tried buying a second one a couple of months ago. From the get go, that second copy behaved weirdly, The disk was slow and seemed to operate in intermittent sprints only. I finally got out a benchmarking tool and the the tests bore out that something was wrong, when compared with my original (older) copy. The original one is displayed to the left, the new one to the right.
Continue reading “Tech troubles of @Seagate Backup Plus Slim”
When talking with companies about the use of open source, sooner or later we end up discussing the problem of license compliance. This is perhaps the most prominent aspect of open source governance for companies getting started with using open source. It can be surprisingly difficult to coherently explain the cause and effect chains that create the potentially high costs of not properly governing your open source engagement!
So here then is my take at teasing it apart.
Continue reading “Costs of no or poor open source governance”