Free and open source software development of IT systems

IT system development, integration, deployment, and administration benefit significantly from free and open source software (FOSS) tools and services. Affordability has been a compelling reason for adopting FOSS in computing curricula and equipping computing labs with support infrastructure. Using FOSS systems and services, however, is just the first step in taking advantage of how FOSS development principles and practices can impact student learning in IT degree programs. Above all, FOSS development of IT systems requires changes to how students, instructors, and other contributors work collaboratively and openly and get involved and invested in project activities. In this paper I examine the challenges to engage students in FOSS development projects proposed by real clients. A six-week course project revealed problems with adopting FOSS development and collaboration across different activities and roles that student team members have assumed. Despite these problems, students have showed a genuine and strong interest in gaining more practice with FOSS development. FOSS development teaching was further refined in two other courses to learn about adequate teaching strategies and the competencies that students achieve when they participate in FOSS development of IT systems

Using wikis for effective peer assessment

In 2009, Curtin University began offering a Bachelor of Education (Primary) program fully online apart from practicum school placements. At Curtin, the Bachelor of Education course has the same structure and units regardless of whether it is taught on campus, regionally or online. The units match in content and assessment and all use Blackboard as the Learning Management System (LMS). For online students, the LMS is the sole source of unit information, documentation submission of assessments and interactions between the students, the teachers and the content and considerable thought has been given to assisting student development in the use of technology and optimising the likelihood of active engagement. Contrary to initial expectations, not all students were technologically sophisticated. Indeed many students were tentative—frightened that they would break something—and generally nervous about learning technologies. To engage students in the learning process, the decision was made to incorporate a wiki, TypeWithMe, into the group assignment. It was hoped that the wiki would benefit students in their group work and the peer assessments aspect of one of their assessments. The results indicated that even though students had concerns regarding their technological ability, they reported that TypeWithMe was easy to use and assisted in both their group work and peer assessment

How organisation of architecture documentation affects architectural knowledge retrieval

A common approach to software architecture documentation in industry projects is the use of file-based documents. This approach offers a single-dimensional arrangement of the architectural knowledge. Knowledge retrieval from file-based architecture documentation is efficient if the organisation of knowledge supports the needs of the readers; otherwise it can be difficult. In this paper, we compare the organisation and retrieval of architectural knowledge in a file-based documentation approach and an ontology-based documentation approach. The ontology-based approach offers a multi-dimensional organisation of architectural knowledge by means of a software ontology and semantic wiki, whereas file-based documentation typically uses hierarchical organisation by directory structure and table of content. We conducted case studies in two companies to study the efficiency and effectiveness of retrieving architectural knowledge from the different organisations of knowledge. We found that the use of better knowledge organisation correlates with the efficiency and effectiveness of AK retrieval. Professionals who used the knowledge organisation found this beneficial

A mapping study on documentation in Continuous Software Development

Context: With an increase in Agile, Lean, and DevOps software methodologies over the last years (collectively referred to as Continuous Software Development (CSD)), we have observed that documentation is often poor. Objective: This work aims at collecting studies on documentation challenges, documentation practices, and tools that can support documentation in CSD. Method: A systematic mapping study was conducted to identify and analyze research on documentation in CSD, covering publications between 2001 and 2019. Results: A total of 63 studies were selected. We found 40 studies related to documentation practices and challenges, and 23 studies related to tools used in CSD. The challenges include: informal documentation is hard to understand, documentation is considered as waste, productivity is measured by working software only, documentation is out-of-sync with the software and there is a short-term focus. The practices include: non-written and informal communication, the usage of development artifacts for documentation, and the use of architecture frameworks. We also made an inventory of numerous tools that can be used for documentation purposes in CSD. Overall, we recommend the usage of executable documentation, modern tools and technologies to retrieve information and transform it into documentation, and the practice of minimal documentation upfront combined with detailed design for knowledge transfer afterwards. Conclusion: It is of paramount importance to increase the quantity and quality of documentation in CSD. While this remains challenging, practitioners will benefit from applying the identified practices and tools in order to mitigate the stated challenges

Minimalism Heuristics Revisited : Developing a Practical Review Tool

Purpose: This article looks at existing minimalism literature and the application of minimalism heuristics. It proposes a revised set of minimalism heuristics to be used at different phases of the minimalist documentation process. The goal is to offer a practical tool for technical communication professionals. Method: The revised heuristics are a combination of a literature review, the best practices of technical communication, and a company pilot study where the heuristics were tested. Results: The article offers a revised list of minimalism heuristics, to be used as part of the minimalist documentation process to ensure documentation quality. Conclusion: The technical communication field is charting new ground in the era of responsive design and mobile platforms.In this new landscape, the principles of minimalism have much to offer. The proposed minimalism heuristics comprise one strategy of applying minimalism for better documentation quality.©2021 Society for Technical Communication.fi=vertaisarvioitu|en=peerReviewed

Software knowledge management using wikis : a plugin for weakly typed pages

Tese de mestrado integrado. Engenharia Informática e Computação. Faculdade de Engenharia. Universidade do Porto. 201

Using GitHub in Large Software Engineering Classes: An Exploratory Case Study

GitHub has been recently used in Software Engineering (SE) classes to facilitate col- laboration in student team projects. The underlying tenet is that the technical and social feature of GitHub can help students to communicate and collaborate more effectively as a team as well as help teachers to evaluate individual student contribution more objectively. To shed more light on this, in this case study, we explore the benefits and drawbacks of using GitHub in SE classes. Our study is conducted in a software engineering class of 91 students divided into 18 teams. Our research method includes an entry and an exit surveys and a qualitative analysis of students’ commit behavior throughout the period of the project. Our findings show that a) enforcing GitHub in SE classes can be an effective approach for enhancing students’ skills in configuration management and version control, and b) despite the steep learning curve, most teams managed to optimize their commit behavior over time. In terms of student evaluation, our analysis exposed the risks of using GitHub for individual effort assessment. The work in this paper provides several valuable insights for researchers and makes several recommendations for practitioners (teachers) about integrating GitHub in SE classes

A systematic review of knowledge sharing challenges and practices in global software development

Abstract not availableMansooreh Zahedia, Mojtaba Shahinb, Muhammad Ali Baba