What does it mean to use a method? Towards a practice theory for software engineering

Dittrich, Yvonne

doi:10.1016/j.infsof.2015.07.001

Cited by 29 publications

(30 citation statements)

References 34 publications

(54 reference statements)

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Cambridge and Longman dictionaries define approach, method, and technique similarly as the following -a [special/planned/particular] way of doing something‖; however, practice is defined as -the act of doing something regularly or repeatedly‖ [29,30]. In this SLR, we define approach, method, and technique as a technical and formalized approach to facilitate and support continuous practices [31]. For simplicity purpose, the approaches, methods, techniques, algorithms, and frameworks, along with the tools to support them, that are developed and reported in the literature for this purpose, are classified as approach rather than practice.…”

Section: A Research Questionsmentioning

confidence: 99%

“…For simplicity purpose, the approaches, methods, techniques, algorithms, and frameworks, along with the tools to support them, that are developed and reported in the literature for this purpose, are classified as approach rather than practice. On the other hand, software practice is a social practice [32] and is defined as shared norms and regulated rules and activities, which can be supported and improved by an approach [31,33].…”

Section: A Research Questionsmentioning

confidence: 99%

See 1 more Smart Citation

Continuous Integration, Delivery and Deployment: A Systematic Review on Approaches, Tools, Challenges and Practices

2017

View full text Add to dashboard Cite

Context: Continuous practices, i.e., continuous integration, delivery, and deployment, are the software development industry practices that enable organizations to frequently and reliably release new features and products. With the increasing interest in and literature on continuous practices, it is important to systematically review and synthesize the approaches, tools, challenges, and practices reported for adopting and implementing continuous practices.Objective: This research aimed at systematically reviewing the state of the art of continuous practices to classify approaches and tools, identify challenges and practices in this regard, and identify the gaps for future research. Method:We used systematic literature review (SLR) method for reviewing the peer-reviewed papers on continuous practices published between 2004 and 1st June 2016. We applied thematic analysis method for analysing the data extracted from reviewing 69 papers selected using predefined criteria. Results:We have identified thirty approaches and associated tools, which facilitate the implementation of continuous practices in the following ways: (1) -reducing build and test time in continuous integration (CI)‖; (2) -increasing visibility and awareness on build and test results in CI‖; (3) -supporting (semi-) automated continuous testing‖; (4) -detecting violations, flaws and faults in CI‖; (5) -addressing security and scalability issues in deployment pipeline‖, and (6) -improving dependability and reliability of deployment process‖. We have also determined a list of critical factors such as -testing (effort and time)‖, -team awareness and transparency‖, -good design principles‖, -customer‖, -highly skilled and motivated team‖, -application domain‖, and -appropriate infrastructure‖ that should be carefully considered when introducing continuous practices in a given organization. The majority of the reviewed papers were validation (34.7%) and evaluation (36.2%) research types. This review also reveals that continuous practices have been successfully applied to both greenfield and maintenance projects. Conclusion:Continuous practices have become an important area of software engineering research and practice. Whilst the reported approaches, tools, and practices are addressing a wide range of challenges, there are several challenges and gaps which require future research work for: improving the capturing and reporting of contextual information in the studies reporting different aspects of continuous practices; gaining a deep understanding of how software-intensive systems should be (re-) architected to support continuous practices; addressing the lack of knowledge and tools for engineering processes of designing and running secure deployment pipelines.

show abstract

Section: A Research Questionsmentioning

confidence: 99%

Section: A Research Questionsmentioning

confidence: 99%

Continuous Integration, Delivery and Deployment: A Systematic Review on Approaches, Tools, Challenges and Practices

2017

View full text Add to dashboard Cite

show abstract

“…Hence, systems developers have to understand the working situation of others, become savvy politicians who can handle project uncertainty and conflict, be familiar with different domains of industry and work with people having different educational backgrounds and experiences (Andersen, 1990). The computer science field itself is beginning to acknowledge the importance of these social and practice‐related aspects of SE (Päivärinta & Smolander, ; Dittrich, ).…”

Section: Developing a Canonical Body Of Isd Knowledgementioning

confidence: 99%

Distilling a body of knowledge for information systems development

Hassan

Mathiassen

2017

Information Systems Journal

View full text Add to dashboard Cite

Abstract. As a contribution towards consolidating the information systems (IS) field, we offer a systematic method for distilling a canonical body of knowledge (BOK) for information systems development (ISD), an area that historically accounts for as much as half of all IS research. Based on an integrative synthesis of the literature, we present a map of the most significant ISD research, uncover gaps in its canons and suggest fruitful lines of inquiry for new research. Our review combines citation analysis, which identifies the field's evidence of cumulative tradition, with computer-aided textual analysis, a hermeneutically guided method that organizes the fragmented corpus of ISD literature into coherent knowledge areas. From a pool of over 6500 articles published in the IS Senior Scholars' Basket of Journals, we find 940 IS citation classics, and from that list, 466 ISD articles that offer canonical ISD knowledge distinctive to IS and complementary to other disciplines such as software engineering and project management. From this study, we offer two contributions: (1) a justification for an ISDBOK grounded in the theory of practice and professionalism, and (2) a canonical map of disciplinary ISD knowledge with areas that have demonstrated cumulative tradition and others that require the attention of IS scholars.

show abstract

“…Various methods and processes are at the heart of software engineering [1]. In practical software design, parts of systems are specified using visual models.…”

Section: Introductionmentioning

confidence: 99%

Comparison of Selected Modeling Notations for Process, Decision and System Modeling

Kluza

Wiśniewski

Jobczyk

et al. 2017

Proceedings of the 2017 Federated Conference on Computer Science and Information Systems

View full text Add to dashboard Cite

Abstract-System specifications can be modeled using various types of notations and diagrams regarding applications of the particular model. In this paper, we present an overview of the existing solutions, focusing on UML, BPMN and DMN models and the diagrams provided by these notations. We perform a comparison of these approaches and provide examples of representing system requirements in these notations.

show abstract

What does it mean to use a method? Towards a practice theory for software engineering

Cited by 29 publications

References 34 publications

Continuous Integration, Delivery and Deployment: A Systematic Review on Approaches, Tools, Challenges and Practices

Continuous Integration, Delivery and Deployment: A Systematic Review on Approaches, Tools, Challenges and Practices

Distilling a body of knowledge for information systems development

Comparison of Selected Modeling Notations for Process, Decision and System Modeling

Contact Info

Product

Resources

About