Non-Regulated Deviance from Standards at MetroEngineers

Author(s):  
Sarah Langer ◽  
Ronny Gey ◽  
Diana Karadzhova-Beyer ◽  
Andrea Fried

With the case study MetroEngineers, Sarah Langer, Ronny Gey, Diana Karadzhova-Beyer, and Andrea Fried highlight organizational deviance from standards in the software development of a service engineering company for rail vehicles called MetroEngineers. Despite the initial intention to develop software according to European standards, the case study explains the reasons why the software developers deviate from standards nonetheless. First, software development at MetroEngineers is provided for a Chinese market which is hardly regulated through standards. Deviations from standards are therefore hardly sanctioned, but even MetroEngineers itself has not established an adequate internal sanctioning system for standard deviations. Second, MetroEngineers’ software developers lack allocative and authoritative resources for standard enactment and a lively internal discourse on the importance of standard-compliant development involving middle management and the customer. This means that software developers are ambitiously trying to develop in accordance with European standards, but ultimately fail to overcome the various contradictions that arise in standard enactment. This chapter represents one of the two manipulation-oriented types of organizational deviance introduced in the book.

2019 ◽  
Vol 30 (4) ◽  
pp. 41-80
Author(s):  
VenuGopal Balijepally ◽  
Sridhar Nerur

Software development is a problem-solving activity, where ideas are combined in complex ways to create a software product that embodies new knowledge. In this endeavor, software developers constantly look for actionable knowledge to help solve the problem at hand. While knowledge management efforts in the software development domain traditionally involved technical initiatives such as knowledge repositories, experience factories, and lessons-to-learn databases, there is a growing appreciation in the software community of the role of developers' personal knowledge networks in software development. However, research is scarce on the nature of these networks, the knowledge resources accessed from these networks, and the differences, if any, between developers of different experience levels. This research seeks to fill this void. Based on a case study in a software development organization, this research explores the nature of knowledge networks of developers from a social capital perspective. Specifically, it examines the structural and relational dimensions of developers' knowledge networks, identifies the specific actionable knowledge resources accessed from these networks, and explores how entry-level and more experienced developers differ along these dimensions. The findings from the qualitative analysis, backed by limited quantitative analysis of the case study data underpin the discussion, implications for practice and future research directions.


2022 ◽  
pp. 1297-1341
Author(s):  
VenuGopal Balijepally ◽  
Sridhar Nerur

Software development is a problem-solving activity, where ideas are combined in complex ways to create a software product that embodies new knowledge. In this endeavor, software developers constantly look for actionable knowledge to help solve the problem at hand. While knowledge management efforts in the software development domain traditionally involved technical initiatives such as knowledge repositories, experience factories, and lessons-to-learn databases, there is a growing appreciation in the software community of the role of developers' personal knowledge networks in software development. However, research is scarce on the nature of these networks, the knowledge resources accessed from these networks, and the differences, if any, between developers of different experience levels. This research seeks to fill this void. Based on a case study in a software development organization, this research explores the nature of knowledge networks of developers from a social capital perspective. Specifically, it examines the structural and relational dimensions of developers' knowledge networks, identifies the specific actionable knowledge resources accessed from these networks, and explores how entry-level and more experienced developers differ along these dimensions. The findings from the qualitative analysis, backed by limited quantitative analysis of the case study data underpin the discussion, implications for practice and future research directions.


2014 ◽  
Vol 5 (3) ◽  
pp. 56-74 ◽  
Author(s):  
Mehrez Essafi ◽  
Henda Ben Ghezala

This work suggests a multilevel support to software developers, who often lack knowledge and skills on how to proceed to develop secure software. In fact, developing software with such quality is a hard and complex task that involves many additional security-dedicated activities which are usually omitted in traditional software development lifecycles or integrated but not efficiently and appropriately deployed in some others. To federate all these software security-assurance activities in a structured way and provide the required guidelines for choosing and using them in a flexible development process, authors used meta-modeling techniques and dynamic process execution that consider developer's affinities and product's states. The proposed approach formalizes existing secure software development processes, allows integration of new ones, prevents ad-hoc executions and is supported by a tool to facilitate its deployment. A case study is given here to exemplify the proposed approach application and to illustrate some of its advantages.


2020 ◽  
Vol 9 (5) ◽  
pp. 2030-2037
Author(s):  
Vahid Bakhtiary ◽  
Taghi Javdani Gandomani ◽  
Afshin Salajegheh

Over recent years, software teams and companies have made attempts to achieve higher productivity and efficiency and get more success in the competitive market by employing proper software methods and practices. Test-driven development (TDD) is one of these practices. The literature review shows that this practice can lead to the improvement of the software development process. Existing empirical studies on TDD report different conclusions about its effects on quality and productivity. The present study tried to briefly report the results from a comparative multiple-case study of two software development projects where the effect of TDD within an industrial environment. Method: We conducted an experiment in an industrial case with 18 professionals. We measured TDD effectiveness in terms of team productivity and code quality. We also measured mood metric and cyclomatic complexity to compare our results with the literature. We have found that the test cases written for a TDD task have higher defect detection ability than test cases written for an incremental NON-TDD development task. Additionally, discovering bugs and fixing them became easier. The results obtained showed the TDD developers develop software code with a higher quality rate, and it results in increasing team productivity than NON_TDD developers.


Author(s):  
Do Vu Phuong Anh

This research presents the results of applying the theory of competence framework to evaluate the current competence of middle management in enterprises, in the case study of DOJI Gemstone Jewelry Group (DOJI Group). By using in-depth interviews and survey through questionnaires, the research results show that the middle management level at DOJI Group has satisfied relatively well the most competencies of the professional competence group, executive management competence as well as personal development competence. However, some of the competencies that need to be further improved include time management, training and leadership competence, innovation and learning competence. The solutions given are for reference by DOJI Group and other private enterprises in Vietnam in the assessment and development of middle management level.


2014 ◽  
Vol 2014 ◽  
pp. 1-9 ◽  
Author(s):  
Ali M. Alakeel

Program assertions have been recognized as a supporting tool during software development, testing, and maintenance. Therefore, software developers place assertions within their code in positions that are considered to be error prone or that have the potential to lead to a software crash or failure. Similar to any other software, programs with assertions must be maintained. Depending on the type of modification applied to the modified program, assertions also might have to undergo some modifications. New assertions may also be introduced in the new version of the program, while some assertions can be kept the same. This paper presents a novel approach for test case prioritization during regression testing of programs that have assertions using fuzzy logic. The main objective of this approach is to prioritize the test cases according to their estimated potential in violating a given program assertion. To develop the proposed approach, we utilize fuzzy logic techniques to estimate the effectiveness of a given test case in violating an assertion based on the history of the test cases in previous testing operations. We have conducted a case study in which the proposed approach is applied to various programs, and the results are promising compared to untreated and randomly ordered test cases.


Sign in / Sign up

Export Citation Format

Share Document