scholarly journals Towards an Anatomy of Software Craftsmanship

2022 ◽  
Vol 31 (1) ◽  
pp. 1-49
Author(s):  
Anders Sundelin ◽  
Javier Gonzalez-huerta ◽  
Krzysztof Wnuk ◽  
Tony Gorschek

Context: The concept of software craftsmanship has early roots in computing, and in 2009, the Manifesto for Software Craftsmanship was formulated as a reaction to how the Agile methods were practiced and taught. But software craftsmanship has seldom been studied from a software engineering perspective. Objective: The objective of this article is to systematize an anatomy of software craftsmanship through literature studies and a longitudinal case study. Method: We performed a snowballing literature review based on an initial set of nine papers, resulting in 18 papers and 11 books. We also performed a case study following seven years of software development of a product for the financial market, eliciting qualitative, and quantitative results. We used thematic coding to synthesize the results into categories. Results: The resulting anatomy is centered around four themes, containing 17 principles and 47 hierarchical practices connected to the principles. We present the identified practices based on the experiences gathered from the case study, triangulating with the literature results. Conclusion: We provide our systematically derived anatomy of software craftsmanship with the goal of inspiring more research into the principles and practices of software craftsmanship and how these relate to other principles within software engineering in general.

Author(s):  
Zaidoun Alzoabi

The term Agile Method of software development was coined in the 2001.This approach is characterized with creativity, flexibility, adaptability, responsiveness, and human-centricity. Researchers have suggested that the complex, uncertain, and ever-changing environment is pushing developers to adopt agile methods rather than traditional software development. Agile methodologist claim that their Agile methods is the answer for the software engineering chaotic situation, in which projects are exceeding their time and budget limits, requirements are not fulfilled, and consequently ending up with unsatisfied customers. In this chapter we will explain agile methodology, its general characteristics, and quick description of the famous agile methods known in the industry and research.


Author(s):  
Lessandra Da Silva e Silva ◽  
Ocirema Maria Juca Farias ◽  
Douglas De Souza Campos ◽  
Bruno Pereira Gonçalves ◽  
Rilmar Pereira Gomes ◽  
...  

This research aimed to present a brightness control system through the Arduino prototype that will adjust the brightness in the workplace according to the Brazilian norms according to the activities performed and through the literature review point its advantages and benefits to the company. To this end, the following research methodologies were adopted: case study, literature review, quantitative and qualitative analysis. Where illuminance samples were collected in a work environment where they are outside the standard of NBR 8995-1, a fact that has been negatively influencing workers performance and company results, a high level of energy consumption was also detected energy. Thus, based on the literature review on the subject, and the results obtained in the inspection of the illuminance of the work environment, it was possible to present a prototype on the Arduino platform that solved the problem of lighting in the work environment, regarding the quantitative results of the work. Research has proven that with the installation of the prototype in the workplace the energy reduction can vary from 7% to 20% in addition to the reduction of occupational disease costs, and the qualitative results show numerous benefits of adequate lighting in the workplace. minus three spheres: physical; cognitive and operational.


Author(s):  
Gordon Deline ◽  
Fuhua Lin ◽  
Dunwei Wen ◽  
Dragan Gaševic ◽  
Kinshuk N/A

This article presents a case study of ontology-driven development of intelligent educational systems. Following a review of literature related to ontology development, ontology-driven software development, and traditional software engineering, we developed an ontology-driven software development methodology appropriate for intelligent ontology-driven systems which have ontologies as key execution components, such as e-Advisor, and which is biased toward an integration of incremental and iterative ontology development and downstream Model Driven Architecture for development of software components.


Author(s):  
Zaidoun Alzoabi

The term Agile Method of software development was coined in the 2001.This approach is characterized with creativity, flexibility, adaptability, responsiveness, and human-centricity. Researchers have suggested that the complex, uncertain, and ever-changing environment is pushing developers to adopt agile methods rather than traditional software development. Agile methodologist claim that their Agile methods is the answer for the software engineering chaotic situation, in which projects are exceeding their time and budget limits, requirements are not fulfilled, and consequently ending up with unsatisfied customers. In this chapter we will explain agile methodology, its general characteristics, and quick description of the famous agile methods known in the industry and research.


Author(s):  
Abbas Moshref Razavi ◽  
Rodina Ahmad

The first part of this chapter presents the results of a systematic literature review on Agile Software Development (ASD) challenges as are reported in implementation and adoption cases. The data only considers the concrete evidences of surfaced problems mainly according to work experience and case study articles. The results are analyzed so that types, nature and intensity of the problems are determined and, compared to each other, within three major classifications of “large organizations”, “distributed settings” and “both large and distributed environments”. The analysis reveals that, in ASD, common organizational and managerial issues have been replaced by communication and collaboration problems. The second part uses the results of the part one as a frame of analysis to render more interpretations e.g. signifying that non-agility preconceptions are the root of a majority of problematic projects. Besides, mediating between agile projects and traditional forms of management, and, economic governance are two major rival approaches that are emerging in response to these challenges.


Author(s):  
Aline Bos ◽  
Charlene Harrington

We analyzed what happens to a nursing home chain when private equity takes over, with regard to strategy, financial performance, and resident well-being. We conducted a longitudinal (2000-2012) case study of a large nursing home chain that triangulated qualitative and quantitative data from 5 different data sources. Results show that private equity owners continued and reinforced several strategies that were already put in place before the takeover, including a focus on keeping staffing levels low; the new owners added restructuring, rebranding, and investment strategies such as establishing new companies, where the nursing home chain served as an essential “launch customer.”


Sign in / Sign up

Export Citation Format

Share Document