scholarly journals Measuring The Impact of Socio-Technical Congruence in a Different Types of Software Life Cycle

2017 ◽  
Vol 9 (1-3) ◽  
Author(s):  
W.A.W.M. Sobri ◽  
S.S.M. Fauzi ◽  
M.H.N.M. Nasir ◽  
R. Ahmad ◽  
A.J. Suali

Measuring developer coordination is a fundamental challenge and complex task in software development organizations. One way used to conceptualize and measure developer coordination is known as 'Socio-Technical Congruence (STC)', which is fit between the coordination requirements established by the dependencies among tasks and the actual coordination activities carried out by the developers. However, STC has not been widely accepted as a broad theory. This is for the reason that, STC is relatively new, and there are many fundamental questions that need to be addressed and understood. This research intend to construct a model of the relationship between STC and project performance in the different types of software development lifecycle. The model constructed can be used to provide additional evidence to the body of knowledge, which will further strengthen the STC theory. Therefore, we outline research questions, the proposed method used to conduct the research, potential contributions and the expected results of the research.

Author(s):  
Naresh E. ◽  
Vijaya Kumar B.P.

The article tries to shed some light on the impact of human psychology on the effective use of pair programming in the modern Software development lifecycle such as SCRUM, Extreme Programming which are in turn used on heterogeneous software projects. This article also tries to identify that if the authors try to pair people keeping their psychology in mind that pair can come up with code with fewer defects, with efficient code, if the paper tries to pair people randomly without any planning or thinking might create a pair which let aside create inefficient code and lead to be unproductive nature, and even it will create a negative impact on the project and the team. This article introduces a few novel approaches in framing the pairs in pair programming's like known and unknown pairs, coder and reviewer pair and coder and tester pair. Applying the described approaches, an industry can improve the quality of the delivered product and improve the efficiency of software engineers.


2020 ◽  
Author(s):  
CRS Kumar

In the game of Golf, a player is challenged to take the minimum strokes to complete a round of 18 holes under varying playing conditions. Players use different clubs depending on their skill levels to achieve the desired distance while taking shots at the golf ball from the start (tee off) to the hole (pin). Unlike other games which have a standardized playing area, the terrain in a golf course comprises of various natural and manmade features viz. fairways, bunkers, trees, water bodies etc, which increase the difficulty level of the game and keep the players challenged.The game of golf has a fascinating similarity to a software development life cycle. If the holes on a golf course are considered akin to milestones in a development project then most of the Software Engineering models focus on software development in groups. Thus, we propose SOLF i.e Software Development Lifecycle model based on Golf, as a SDLC ideal for individuals or a small group of 2-3 developers. The proposed model is easy to comprehend, flexible and optimally adjustable in a dynamic environment.SOLF divides the project into 18 stages wherein each stage of the project will have 3 to 6 tasks which are required to be completed within a fixed timeline. The stages are managed by creating checklists at the start akin to the pre-shot routines in golf and the customer feedback is received on reaching each of the milestones similar to applause in the game of golf. Terrain of the golf course is reflected as risk list which are varying for each of the stages.SOLF achieves 10x speedup in software development and research projects as it creates an environment of challenges and drives the developer towards self excellence. It also inculcates a spirit of competition and sportsmanship by challenging the developers on various 'terrains' of development.


2012 ◽  
Vol 6 (1) ◽  
pp. 389-407 ◽  
Author(s):  
Maxine E. Sprague ◽  
Jim Parsons

In this paper, the authors discuss creativity and the impact it might have on teaching and learning. The authors believe that imaginative play, at all ages, helps all people (children especially) create healthy environments and spaces that expand their learning. The authors contend that teaching for imagination—which asks little more than creating and trusting an ecological space that engenders it—seldom is considered a priority. Given the emphasis on creativity in the real world and the virtual digital world, the authors believe it is important to add to the body of knowledge through continued research in this field.


2021 ◽  
Author(s):  
Mayank Gokarna

DevOps is the combination of cultural mindset, practices, and tools that increases a team's ability to release applications and services at high velocity. The development and operations teams always have a conflict around the scope of responsibility. With these differences the quality and speed of delivery across software Development Life Cycle is negatively impacted. DevOps is about removing the barriers between two traditionally delimited teams, development and operations. With DevOps, these two teams work together to optimize both the productivity of developers and the reliability of operations. They strive to communicate frequently, increase efficiencies, and improve the quality of services they provide. They take full ownership for their services, often beyond where their stated roles or titles have traditionally been scoped. Transitioning to DevOps requires a change in culture and mindset first. It is quite difficult to persuade a whole company to change its culture at once. This paper aims to bring different phases of software development lifecycle into DevOps implementation strategy and presents a comprehensive collection of leading tools used across Software Development life Cycle to automate and integrate different stages of software delivery. This paper also highlights on DevOps practices which span across different phases of the Software Development Lifecycle and how those can be implemented with different tools available.


2021 ◽  
Vol 123 (13) ◽  
pp. 547-560
Author(s):  
Antonio Montero-Navarro ◽  
Thais González-Torres ◽  
José-Luis Rodríguez-Sánchez ◽  
Rocio Gallego-Losada

PurposeThis paper aims at providing an overview and synthesis of the existing body of knowledge about greenwashing. Special attention is paid to the articles directly linked with agriculture, food industry and food retail.Design/methodology/approachA bibliometric analysis was performed over 351 documents extracted from the WoS database, using SciMAT and VOSviewer software programs.FindingsThree periods in the academic literature about greenwashing can be distinguished: ground-setting (2003–2010), trail-blazing (2011–2015) and remarkable growth (2016–2020). Along this evolution, a body of knowledge which stemmed from the literature about CSR has achieved a major development, deploying different research lines such as stakeholders' management, marketing and communication and audit. A specific analysis of the academic literature about greenwashing in agriculture, food industry and food retail has been carried out, showing a need for further development.Social implicationsThe development of scientific knowledge about greenwashing puts this social claim on the spotlight of business management studies, helping to fight greenwashing and, this way, to reduce the environmental impact of corporate activities. Studying greenwashing will help to reduce its frequency and, therefore, heal the planet.Originality/valueSome previous studies have provided systematic reviews of the literature using different approaches, but they did not untangle the intellectual structure and the evolution of the body of research about greenwashing. This article originally provides a thorough analysis of these aspects, as well as a closer look at the impact of greenwashing practices in the academic literature regarding agriculture, food industry and food retail.


2014 ◽  
pp. 999-1013
Author(s):  
Alessandra Bagnato ◽  
Fabio Raiteri ◽  
Christian Jung ◽  
Frank Elberzhager

Security inspections are increasingly important for bringing security-relevant aspects into software systems, particularly during the early stages of development. Nowadays, such inspections often do not focus specifically on security. With regard to security, the well-known and approved benefits of inspections are not exploited to their full potential. This book chapter focuses on the Security Goal Indicator Tree application for eliminating existing shortcomings, the training that led to their creation in an industrial project environment, their usage, and their reuse by a team in industry. SGITs are a new approach for modeling and checking security-relevant aspects throughout the entire software development lifecycle. This book chapter describes the modeling of such security goal based trees as part of requirements engineering using the GOAT tool dedicated plug-in and the retrieval of these models during the various phases of the software development lifecycle in a project by means of Software Vulnerability Repository Services (SVRS) created in the European project SHIELDS (SHIELDS - Detecting known security vulnerabilities from within design and development tools).


Sign in / Sign up

Export Citation Format

Share Document