|
We visited Appwork yesterday, a FAU-student-created start-up and provider of JDownloader, a desktop application for downloading files. We use it, mostly for downloading research talks and other instructional material. Appwork’s offices are located in downtown Fürth, in a beautiful loft, see photo impressions below. Sadly, I lost the main lounge photo, but still, you can guess what a fabulous work place it is!
Continue reading Impressions from a Visit to FAU Start-up Appwork Abstract: The aim of this master thesis is to demonstrate the way the software requirements are built on the example of a case written in the form of Harvard Business Case. “The importance of complete, consistent and well documented software requirements is difficult to overstate” (early 1986). There is no bigger risk to a software project than incomplete, misunderstood, or under-emphasized software requirements. However, it is not always clear how to work out requirements. This case was written based on a real software project and gives an overview of the process how the requirements are discovered, documented, validated and managed. It also illustrates the methodologies and techniques used by requirements engineer, and defines the key players. The case ends with an open question – how can the process of working out requirements could be improved or reinforced? Along with the case, this work contains structured summary of major concepts with the theoretical materials the case was based on. The discussion guide provided in the final part of this thesis is the instruction how this case should be presented to the auditory. Keywords: Requirements analysis, business case PDFs: Master Thesis Reference: Maria Arcus. Business Case: How to work out Requirements? Master Thesis, Friedrich-Alexander-Universität Erlangen-Nürnberg: 2013. Abstract: It is well known that open source software brought changes to the software development domain. It changed the paradigm from payed developers working in offices to people developing geographically separated, including basements, garages, etc. Even the innovation factor of organizations changed to open innovation, intensively including customers or consumers. This work pretends to further analyze the changes Open Source brought along concerning to alliances. It intends to determine the ways or channels through which Single–Vendor Commercial Open Source firms meet partners in order to set a formal cooperation. To distinguish channels, the researcher first examined a set of interview transcripts. Based on the transcripts analysis, certain channels are identified. To validate the use of those channels, interviews with Open–Source based companies are accomplished. During the interview process, some other channels are identified. Results obtained from this study contribute to the understanding how Open Source modified the approaches companies use to get to know partners. Keywords: Open source software, software industry, commercial open source, single-vendor open source, strategic alliances, business partners PDFs: Master Thesis, Work Description Reference: Cecilia La Fuente. Why and How to Forge Open Source Alliances. Master Thesis, Friedrich Alexander-Universität Erlangen-Nürnberg: 2013. Abstract: Free Seas Ahoy! is a social networking site with open source development for sailors, boaters and anyone who are interested in exchanging nautical experiences and information. It is a social networking site on the verge to lead the market of sailors and nautical industry niche, which incorporate a trip management tool with which to plan, organize and record a great variety of information concerning sailing trips. On the other hand it provides social interaction and information exchange about the sailing related information and experiences. [...] Reference: Muzdat Juma. Free Seas Ahoy! Business Case. Master Thesis, Friedrich-Alexander-Universität Erlangen-Nürnberg: 2013. Die FAU hat sich erfolgreich eine Rahmenpromotionsordnung gegeben, welche die Promotionsordnungen der einzelnen Fakultäten angleicht und damit den Gesamtprozess vereinfacht sowie die Qualitätskriterien vereinheitlicht und transparenter macht. Lesen Sie mehr in der Pressemitteilung. Abstract: Software plays a significant role in the context of modern enterprises. CRM, ERP, Billing and Accounting systems are some of the examples of the information system components which have become inseparable parts of daily operations in almost every enterprise. An organization’s specific needs and requirements for information systems are evolving into dozens of software engineering projects that need to be managed. Pursuing the aim to optimize these projects’ outcomes in terms of quality, costs and time, customers and software development teams face a dilemma of choice – which software engineering process model to use? I previously described why it is difficult being an external Ph.D. student. One of the aspects is that you have to convince me that you can prevail, even though I have much less opportunity to advise you than I’d have with a “wissenschaftlicher Mitarbeiter” (TA/RA position funding Ph.D. studies) that I employ. So, if you are thinking about approaching me to become your advisor, I recommend you go through the following mental exercise first: To layout the work that motivates you as a combination of research question, possible hypotheses, research approach and employed methods, and expected results. You should be able to write this up as a 100-200 word abstract. Here are two examples (I wrote this blog post on a whim, so please don’t hold me to the quality of these examples): Continue reading A Note to and Exercise for Prospective External Ph.D. Students Abstract: Is the development of Free/Libre/Open Source Software (FLOSS) still like roughly 20 years ago, when a Finnish student wrote the basis of a nowadays successful operating systems in his spare time at home? Or is FLOSS becoming mainstream in the perception of companies? How much of the work on FLOSS is done during working hours? Continue reading OSR Group Thesis: An Analysis of Work Rhythms in Open Source Abstract: This is a master thesis for the program International Information Systems. In this thesis work the situation of a software company and its product is analyzed. The situation is written in form of a Harvard Business Case with a lucid narrative. The case will be taught in Product management course in the university. Although the specific situation of one company was evaluated, thousands of firms with strongly customer-focused product development face similar challenge. The problem arises when listening to customers’ requests poses threats to product innovation and hence its market position. The main questions are if firms should disrupt their customers and what are the effects of disruptive and sustaining innovations on the firm’s business. Along with the main case, there are teaching note and class discussion guide, so that the teacher had more material to discuss the case with students. The thesis work is licensed CC-BY-3.0. Continue reading OSR Group Thesis: Should Firms Disrupt Their Customers? Nailing your Thesis (NYT) is our research lab course, where we teach what science is, how to perform research, and how to publish it. Below, please find the overview course syllabus. Continue reading Course Syllabus of Nailing your Thesis (NYT) |
Audi AG
BearingPoint GmbH
Capgemini Service SAS
DATEV eG
Develop Group GmbH
Elektrobit Corp.
GfK SE
Google, Inc.
QuinScape GmbH
RedHat, Inc.
Robert Bosch GmbH
Siemens AG
SUSE Linux GmbH
Univention GmbH
WeWebU Software AG
Open Source Business Foundation
Open Source Business Alliance |
|
Copyright © 2013 Open Source Research Group - All Rights Reserved |
|
