The Effects of Software Process Evolution to Technical Debt—Perceptions from Three Large Software Projects

2016 ◽  
pp. 305-327
Author(s):  
Jesse Yli-Huumo ◽  
Andrey Maglyas ◽  
Kari Smolander
Keyword(s):  
Software Process ◽  
Technical Debt ◽  
Software Projects ◽  
Large Software

Using Stack Overflow to Assess Technical Debt Identification on Software Projects

2020 ◽  
Author(s):  
Eliakim Gama ◽  
Sávio Freire ◽  
Manoel Mendonça ◽  
Rodrigo O. Spínola ◽  
Matheus Paixao ◽  
...  
Keyword(s):  
Technical Debt ◽  
Software Projects ◽  
Stack Overflow

APPLYING EXPERT JUDGMENT TO IMPROVE AN INDIVIDUAL'S ABILITY TO PREDICT SOFTWARE DEVELOPMENT EFFORT

2012 ◽  
Vol 22 (04) ◽  
pp. 467-483 ◽  
Author(s):  
CUAUHTÉMOC LÓPEZ-MARTÍN ◽  
ALAIN ABRAN
Keyword(s):  
Software Development ◽  
Software Process ◽  
Development Effort ◽  
Academic Environment ◽  
Academic Institutions ◽  
Graduate Courses ◽  
Software Projects ◽  
Personal Software Process ◽  
Software Development Effort ◽  
Effort Prediction

Expert-based effort prediction in software projects can be taught, beginning with the practices learned in an academic environment in courses designed to encourage them. However, the length of such courses is a major concern for both industry and academia. Industry has to work without its employees while they are taking such a course, and academic institutions find it hard to fit the course into an already tight schedule. In this research, the set of Personal Software Process (PSP) practices is reordered and the practices are distributed among fewer assignments, in an attempt to address these concerns. This study involved 148 practitioners taking graduate courses who developed 1,036 software course assignments. The hypothesis on which it is based is the following: When the activities in the original PSP set are reordered into fewer assignments, the result is expert-based effort prediction that is statistically significantly better.

Web-based issue tracking for large software projects

1998 ◽  
Vol 2 (5) ◽  
pp. 25-33 ◽  
Author(s):  
J.R. Callahan ◽  
R.R. Khatsuriya ◽  
R. Hefner
Keyword(s):  
Software Projects ◽  
Web Based ◽  
Large Software

scholarly journals A Taste of the Software Industry Perception of Technical Debt and its Management in Brazil

2019 ◽  
Vol 7 ◽  
pp. 1 ◽  
Author(s):  
Victor Machado Silva ◽  
Helvio Jeronimo Junior ◽  
Guilherme Horta Travassos
Keyword(s):  
Software Engineering ◽  
Small Group ◽  
Software Industry ◽  
Internal Quality ◽  
Primary Study ◽  
Communication Tool ◽  
Technical Debt ◽  
Software Projects ◽  
Considerable Fraction

Technical debt (TD) is receiving more and more attention to software engineering. Although it was initially used as a communication tool for technical and non-technical stakeholders, nowadays this concept supports the improvement of the software’s internal quality. Despite the increasing number of studies regarding TD and its management, only a few are concerned with the industry. Therefore, this primary study aims to characterize TD and its management under the perspective of Brazilian software organizations using their practitioners as proxies. A survey was performed with 62 practitioners, representing around 12 organizations and 30 software projects. The analysis of 40 valid questionnaires indicates that TD is still unknown to a considerable fraction of the participants, and only a small group of organizations adopt TD management activities in their projects. The survey package is available and can be used to support further investigations on TD management in software organizations.

A programming environment for large software projects

1994 ◽  
Vol 5 (4) ◽  
pp. 275-278
Author(s):  
I. V. Mashechkin ◽  
E. O. Orlova
Keyword(s):  
Programming Environment ◽  
Software Projects ◽  
Large Software

Managing Software Projects with Team Software Process (TSP)

2013 ◽  
pp. 84-117
Author(s):  
Salmiza Saul Hamid ◽  
Mohd Hairul Nizam Md Nasir ◽  
Shamsul Sahibuddin ◽  
Mustaffa Kamal Mohd Nor
Keyword(s):  
Project Management ◽  
Software Development ◽  
Management Practices ◽  
Software Process ◽  
Development Project ◽  
Software Projects ◽  
Engineering Teams ◽  
Software Development Project ◽  
Software Failure ◽  
Team Software Process

Despite the widespread use of sound project management practices and process improvement models over the last several years, the failure of software projects remains a challenge to organisations. As part of the attempt to address software industry challenges, several models, frameworks, and methods have been developed that are intended to improve software processes to produce quality software on time, under budget, and in accordance with previously stipulated functionalities. One of the most widely practised methods is the Team Software Process (TSP). The TSP was designed to provide an operational framework for establishing an effective team environment and guiding engineering teams in their work. This chapter provides an overview of the TSP and its associated structures and processes. It also highlights how the TSP operational framework can assist project manager and software development team to deliver successful projects by controlling and minimizing the most common software failure factors. Comparative analysis between the TSP and conventional project management has also been presented. Additionally, the results of TSP implementation in industrial settings are highlighted with particular reference to scheduling, quality, and productivity. The last section indicates additional advantages of TSP and comments on the future of TSP in the global software development project.

Software Project Managers under the Team Software Process

2012 ◽  
pp. 115-126
Author(s):  
Marcos Ruano-Mayoral ◽  
Ricardo Colomo-Palacios ◽  
Ángel García-Crespo ◽  
Juan Miguel Gómez-Berbís
Keyword(s):  
Software Development ◽  
Software Process ◽  
Development Project ◽  
Project Managers ◽  
Project Manager ◽  
Software Project ◽  
Software Projects ◽  
Software Development Project ◽  
Team Software Process ◽  
Definition Of

Despite the clear relevance of the Information and Communications Technologies (ICT) market in world economics and the evident lack of success of software projects, organizations devote little effort to the development and maturity of the software project manager profession. This work analyzes the figure of project manager from the perspective of the Team Software Process (TSP), and it considers the required skills, attitudes and knowledge for a software development project. The basis for the study is the analysis of relevant references from the literature for their subsequent categorization into different competency concepts. The results of the analysis are compared with the contributions which the Guide to the SWEBOK® and the PMBOK® Guide models provide of the profiles of the project manager. The results indicate that the literature relating to the Team Software Process is focused on the definitions of skills and attitudes, and to a lesser extent on knowledge components. The lack of the definition of the components which comprise competency constitutes a challenge for software development organizations that use TSP, whose project managers should confront the task with full capacities, and without the help of established and recognized competencies. The current work attempts to establish the competencies for project managers identified in the literature, in the environment of the use of TSP for software development, using a study based on content analysis.

Using Genetic Algorithms to Search for Key Stakeholders in Large-Scale Software Projects

2013 ◽  
pp. 118-134 ◽  
Author(s):  
Soo Ling Lim ◽  
Mark Harman ◽  
Angelo Susi
Keyword(s):  
Genetic Algorithms ◽  
Real World ◽  
Large Scale ◽  
Requirements Elicitation ◽  
Software Project ◽  
Software System ◽  
Software Projects ◽  
Key Stakeholders ◽  
Large Software ◽  
Stakeholder Needs

Large software projects have many stakeholders. In order for the resulting software system and architecture to be aligned with the enterprise and stakeholder needs, key stakeholders must be adequately consulted and involved in the project. This work proposes the use of genetic algorithms to identify key stakeholders and their actual influence in requirements elicitation, given the stakeholders’ requirements and the actual set of requirements implemented in the project. The proposed method is applied to a large real-world software project. Results show that search is able to identify key stakeholders accurately. Results also indicate that many different good solutions exist. This implies that a stakeholder has the potential to play a key role in requirements elicitation, depending on which other stakeholders are already involved. This work demonstrates the true complexity of requirements elicitation – all stakeholders should be consulted, but not all of them should be treated as key stakeholders, even if they appear to be significant based on their role in the domain.

Sign in / Sign up

Export Citation Format

Share Document