scholarly journals Open Source Engineering Processes

2013 ◽  
Vol 55 (5) ◽  
Author(s):  
Wolfgang Mauerer ◽  
Michael C. Jaeger

AbstractSoftware engineering in open source projects faces similar challenges as in traditional software development (coordination of and cooperation between contributors, change and release management, quality assurance, …), but often uses different means of solving them. This leads to some salient distinctions between both worlds, especially with respect to communication and how technical issues are addressed. The variations within open source software (OSS) communities are considerable, and many different approaches are currently in use, ranging from informal conventions to highly systematic, formally specified and rigidly applied processes. We discuss the archetypal best practises in the field, illustrate them by presenting example projects, and provide a comparison to traditional approaches.

Author(s):  
Stefan Dietze

This chapter discusses typical collaborative requirements definition processes as they are performed in open source software development (OSSD) projects. In the beginning, some important aspects of the entire OSSD approach are introduced in order to enable an understanding of the subsequent description of the feedback-based requirements definition processes. Since the OSSD model seems to represent a successful way of dealing with the significant distribution and heterogeneity of its actors, some opportunities to adapt this approach also in other (software) industries are discussed. Nevertheless the entire OSSD model still exhibits several improvement opportunities that also are addressed in this chapter. In order to overcome possible weaknesses, several approaches to improve the described requirements definition approach are introduced. These improvements help to assure a higher level of efficiency and quality assurance for both processes and the developed artifacts, and furthermore also enable the consideration and acceptance of this approach in other domains and industries.


Author(s):  
Stefan Dietze

This chapter discusses typical collaborative requirements definition processes as they are performed in open source software development (OSSD) projects. In the beginning, some important aspects of the entire OSSD approach are introduced in order to enable an understanding of the subsequent description of the feedback-based requirements definition processes. Since the OSSD model seems to represent a successful way of dealing with the significant distribution and heterogeneity of its actors, some opportunities to adapt this approach also in other (software) industries are discussed. Nevertheless the entire OSSD model still exhibits several improvement opportunities that also are addressed in this chapter. In order to overcome possible weaknesses, several approaches to improve the described requirements definition approach are introduced. These improvements help to assure a higher level of efficiency and quality assurance for both processes and the developed artifacts, and furthermore also enable the consideration and acceptance of this approach in other domains and industries.


Author(s):  
Sofiane Sahraoui

Open source software (OSS) development has been a trend parallel to that of agile software development, which is the highly iterative development model following conventional software engineering principles. Striking similarities exist between the two development processes as they seem to follow the same generic phases of software development. Both modes of development have less emphasis on planning and design and a more prominent role for implementation during the software engineering process. This chapter expounds on this connection by adopting an agile perspective on OSS development to emphasize the similarities and dissimilarities between the two models. An attempt is first made to show how OSS development fits into the generic agile development framework. Then, the chapter demonstrates how the development process of Mozilla and Apache as two of the most famous OSS projects can be recast within this framework. The similarity discussed and illustrated between agile and OSS development modes is rather limited to the mechanics of the development processes and do not include the philosophies and motivations behind development.


Author(s):  
Walt Scacchi

This paper examines what is known about the role of open source software development within the world of game mods and modding practices. Game modding has become a leading method for developing games by customizing or creating Open Source Software extensions to game software in general, and particularly to proprietary closed source software games. What, why, and how OSS and closed source software come together within an application system is the subject for this study. Observational and qualitative is used to highlight current practices and issues that can be associated with software engineering and game studies foundations with multiple examples of different game mods and modding practices are identified throughout this study.


Electronics ◽  
2021 ◽  
Vol 10 (13) ◽  
pp. 1523
Author(s):  
Javier Conde ◽  
Sonsoles López-Pernas ◽  
Alejandro Pozo ◽  
Andres Munoz-Arcentales ◽  
Gabriel Huecas ◽  
...  

Although many courses in computer science and software engineering require students to work on practical assignments, these are usually toy projects that do not come close to real professional developments. As such, recent graduates often fail to meet industry expectations when they first enter the workforce. In view of the gap between graduates’ skills and industry expectations, several institutions have resorted to integrating open-source software development as part of their programs. In this pilot study, we report on the results of the contributions of eleven students to the FIWARE open-source project as part of their final year project. Our findings suggest that both teachers and students have a positive perception towards contributing to the FIWARE open-source initiative and that students increased their knowledge of technologies valued by the industry. We also found that this kind of project requires an additional initial effort for the students as well as for the instructor to monitor their progress. Consequently, it is important that the instructors have previous experience in FIWARE, as many of the students need help during the process.


Sign in / Sign up

Export Citation Format

Share Document