scholarly journals Insights into the Prevalence of Software Project Defects

2014 ◽  
Vol 2014 ◽  
pp. 1-5
Author(s):  
Javier Alfonso-Cendón ◽  
Manuel Castejón Limas ◽  
Joaquín B. Ordieres Meré ◽  
Juan Pavón
Keyword(s):  
Software Development ◽  
Clustering Algorithm ◽  
Control Strategies ◽  
Likelihood Ratio Statistic ◽  
Software Project ◽  
Software Defects ◽  
Software Projects ◽  
Development Lifecycle ◽  
Definition Of ◽  
Effort Distribution

This paper analyses the effect of the effort distribution along the software development lifecycle on the prevalence of software defects. This analysis is based on data that was collected by the International Software Benchmarking Standards Group (ISBSG) on the development of 4,106 software projects. Data mining techniques have been applied to gain a better understanding of the behaviour of the project activities and to identify a link between the effort distribution and the prevalence of software defects. This analysis has been complemented with the use of a hierarchical clustering algorithm with a dissimilarity based on the likelihood ratio statistic, for exploratory purposes. As a result, different behaviours have been identified for this collection of software development projects, allowing for the definition of risk control strategies to diminish the number and impact of the software defects. It is expected that the use of similar estimations might greatly improve the awareness of project managers on the risks at hand.

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.

scholarly journals On Effort Distribution in Software Project Development for Academic Domain

2020 ◽  
Vol 9 (3) ◽  
pp. 1755-1761
Keyword(s):  
Software Development ◽  
Computer Science ◽  
Distribution Data ◽  
Development Effort ◽  
Software Project ◽  
Effort Estimation ◽  
Software Projects ◽  
Computer Science Courses ◽  
Almost All ◽  
Effort Distribution

Effort distribution in software engineering is a well-known term used to measure cost and effort estimation for each and every phase or activity in software development. Effort distribution is taken in consideration in almost all IT companies while developing software. But it is mostly not considered or overlooked in developing academic software projects by students of computer science courses. The paper presents with results of an experimentation on phase effort distribution data of 84 software academic projects of post graduate final year students of computer science. The phase effort distribution provided by students were collected, analyzed and compared with COCOMO II model which provides effort distribution required in software development. Finally, this paper also discusses and provides recommendation about the use and importance of effort distribution in academic software projects development.

Toward Agile Interactive Software Development Process Models for Crowd Source Projects

2014 ◽  
pp. 117-131
Author(s):  
Izzat Alsmadi ◽  
Saqib Saeed
Keyword(s):  
Software Development ◽  
Process Models ◽  
Agile Development ◽  
Software Project ◽  
Interactive Software ◽  
Crowd Sourcing ◽  
Software Projects ◽  
The Public ◽  
Development Models ◽  
High Level

Typical traditional software development models are initially designed for company-style software project teams. They also assume a typical software project that has somewhat clear goals, scope, budget, and plan. Even Agile development models that are very flexible in considering previous project parameters assume somewhat stable team and project structures. However, in recent years, the authors have noticed expansion in software projects that are developed in a very illusive flexible team, scope, budget, and plan structures. Examples of such projects are those projects offered in open competition (also called crowd sourcing) structure for software developers to be part of. In typical open competition projects, initial, high level project ideas are submitted to the public through the Internet. The project initiators give their initial requirements, constraints, and conditions for successful products or submissions. Teams can be organized before or through the competition. Submission and evaluation of deliverables from teams are subjected to project initiator evaluation along with evaluation teams organized through the open competition host. This chapter investigates all traditional project characteristics. The authors elaborate on all those elements that should be modified to fit the open competition agile structure. They use several case studies to demonstrate management issues related to managing software projects in open competitions.

scholarly journals Software development: do good manners matter?

2015 ◽  
Author(s):  
Giuseppe Destefanis ◽  
Marco Ortu ◽  
Steve Counsell ◽  
Michele Marchesi ◽  
Roberto Tonelli
Keyword(s):  
Software Development ◽  
Open Source Software ◽  
Development Process ◽  
Communication Process ◽  
Software Project ◽  
Software Development Process ◽  
Key Factors ◽  
Software Projects ◽  
Complex Process ◽  
Time Required

A successful software project is the result of a complex process involving, above all, people. Developers are the key factors for the success of a software development process, not merely as executors of tasks, but as protagonists and core of the whole development process. This paper investigates social aspects among developers working on software projects developed with the support of Agile tools. We studied 22 open source software projects developed using the Agile board of the JIRA repository. All comments committed by developers involved in the projects were analyzed and we explored whether the politeness of comments affected the number of developers involved and the time required to fix any given issue. Our results showed that the level of politeness in the communication process among developers does have an effect on the time required to fix issues and, in the majority of the analysed projects, it had a positive correlation with attractiveness of the project to both active and potential developers. The more polite developers were, the less time it took to fix an issue. In the majority of the analysed cases, the more developers wanted to be part of a project, the more they were willing to continue working on the project over time.

scholarly journals Software development: do good manners matter?

2015 ◽  
Author(s):  
Giuseppe Destefanis ◽  
Marco Ortu ◽  
Steve Counsell ◽  
Michele Marchesi ◽  
Roberto Tonelli
Keyword(s):  
Software Development ◽  
Open Source Software ◽  
Development Process ◽  
Communication Process ◽  
Software Project ◽  
Software Development Process ◽  
Key Factors ◽  
Software Projects ◽  
Complex Process ◽  
Time Required

A successful software project is the result of a complex process involving, above all, people. Developers are the key factors for the success of a software development process, not merely as executors of tasks, but as protagonists and core of the whole development process. This paper investigates social aspects among developers working on software projects developed with the support of Agile tools. We studied 22 open source software projects developed using the Agile board of the JIRA repository. All comments committed by developers involved in the projects were analyzed and we explored whether the politeness of comments affected the number of developers involved and the time required to fix any given issue. Our results showed that the level of politeness in the communication process among developers does have an effect on the time required to fix issues and, in the majority of the analysed projects, it had a positive correlation with attractiveness of the project to both active and potential developers. The more polite developers were, the less time it took to fix an issue. In the majority of the analysed cases, the more developers wanted to be part of a project, the more they were willing to continue working on the project over time.

scholarly journals Juego lúdico GetKanban Game para apoyar el proceso de enseñanza aprendizaje de la disciplina de gestión de proyectos de software en los estudiantes de TIC`S

2020 ◽  
Vol 6 (3) ◽  
pp. 27-34
Author(s):  
E.J. Robles Gómez ◽  
J.A. Flores Lara ◽  
J.C. Ontiveros Neri
Keyword(s):  
Project Management ◽  
Software Engineering ◽  
Software Development ◽  
Systems Engineering ◽  
Educational Institution ◽  
Development Projects ◽  
Software Project ◽  
Software Projects ◽  
Teaching Learning ◽  
On Time Delivery

El juego getKanban es una herramienta para enseñar la metodología Kanban y SCRUM de una manera divertida. Facilita la enseñanza de la gestión de proyectos de software a través de un juego de mesa, donde los jugadores aprenden a formular estrategias de gestión de proyectos y las implementan para elaborar proyectos de calidad en tiempo y forma. El presente artículo muestra los resultados de la implementación del juego en una institución educativa de nivel superior, con alumnos de Ingeniería en Sistemas Computacionales de octavo semestre. Se puede apreciar que al utilizar este juego ayuda de manera efectiva a la enseñanza de Kanban y SCRUM, para la gestión de proyectos de software. Por lo cual se recomienda poder implementar este tipo de juegos como estrategia didáctica para la enseñanza/aprendizaje de Ingeniería de Software aplicada a la Gestión de Proyectos de Desarrollo de Software. The game Kanban is a tool to teach the methodology in a fun way. It facilitates the teaching of software project management through where players learn to formulate strategies and implement them to develop quality projects on time Delivery. This article shows the results of the implementation of the game in an educational institution of higher level, with students of Computer Systems Engineering eighth semester. It can be seen that by using this game it helps in an effective way to teach Kanban for the management of software projects. Therefore, it is recommended to be able to implement this type of games as a didactic strategy for the teaching / learning of Software Engineering applied to the Management of Software Development Projects

scholarly journals Identification-Method Research for Open-Source Software Ecosystems

Symmetry ◽  
2019 ◽  
Vol 11 (2) ◽  
pp. 182 ◽  
Author(s):  
Zhifang Liao ◽  
Ningwei Wang ◽  
Shengzong Liu ◽  
Yan Zhang ◽  
Hui Liu ◽  
...  
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
Clustering Algorithm ◽  
Research Area ◽  
Software Project ◽  
Software Projects ◽  
Virtual Collaboration ◽  
Software Ecosystem ◽  
Software Ecosystems ◽  
Core Project

In recent years, open-source software (OSS) development has grown, with many developers around the world working on different OSS projects. A variety of open-source software ecosystems have emerged, for instance, GitHub, StackOverflow, and SourceForge. One of the most typical social-programming and code-hosting sites, GitHub, has amassed numerous open-source-software projects and developers in the same virtual collaboration platform. Since GitHub itself is a large open-source community, it hosts a collection of software projects that are developed together and coevolve. The great challenge here is how to identify the relationship between these projects, i.e., project relevance. Software-ecosystem identification is the basis of other studies in the ecosystem. Therefore, how to extract useful information in GitHub and identify software ecosystems is particularly important, and it is also a research area in symmetry. In this paper, a Topic-based Project Knowledge Metrics Framework (TPKMF) is proposed. By collecting the multisource dataset of an open-source ecosystem, project-relevance analysis of the open-source software is carried out on the basis of software-ecosystem identification. Then, we used our Spectral Clustering algorithm based on Core Project (CP-SC) to identify software-ecosystem projects and further identify software ecosystems. We verified that most software ecosystems usually contain a core software project, and most other projects are associated with it. Furthermore, we analyzed the characteristics of the ecosystem, and we also found that interactive information has greater impact on project relevance. Finally, we summarize the Topic-based Project Knowledge Metrics Framework.

A Framework for Risk Management in AI System Development Projects

2019 ◽  
pp. 1-20
Author(s):  
Kitti Photikitti ◽  
Kitikorn Dowpiset ◽  
Jirapun Daengdej
Keyword(s):  
Artificial Intelligence ◽  
Risk Management ◽  
Project Management ◽  
Software Development ◽  
System Development ◽  
Systems Development ◽  
Development Projects ◽  
Software Project ◽  
Software Projects ◽  
Very High

It has been well-known that the chance of successfully delivering a software project within an allocated time and budget is very low. Most of the researches in this area have concluded that “user's requirements” of the systems is one of the most difficult risks to deal with in this case. Interestingly, until today, regardless of amount of effort put into this area, the possibility of project failure is still very high. The issue with requirement can be significantly increased when developing an artificial intelligence (AI) system, where one would like the systems to autonomously behave. This is because we are not only dealing with user's requirements, but we must also be able to deal with “system's behavior” that, in many cases, do not even exist during software development. This chapter discusses a preliminary work on a framework for risk management for AI systems development projects. The goal of this framework is to help project management in minimizing risk that can lead AI software projects to fail due to the inability to finish the projects on time and within budget.

Developing a Glossary for Software Projects

2018 ◽  
pp. 7399-7410 ◽  
Author(s):  
Tamer Abdou ◽  
Pankaj Kamthan ◽  
Nazlie Shahmir
Keyword(s):  
Information Technology ◽  
Software Development ◽  
Effective Communication ◽  
Software Project ◽  
Application Domain ◽  
Software Projects ◽  
Development Methodology ◽  
Software Development Methodology

The success of a software project depends intrinsically on effective communication among stakeholders. The purpose of a glossary is to ensure that the knowledge of the domain underlying a software project be communicated properly to all the stakeholders of that project. This chapter provides the context, the rationale, and the means for developing a glossary for software projects. In doing so, it proposes a process for developing a glossary. This process is independent of any particular application domain, software development methodology, and information technology. The approaches for representing and presenting a glossary, for the consumption of humans as well as that of machines, are discussed.

eXtreme Programming, Agile Methodologies, Software Project Management, Customer Role, Rigorous Testing

2022 ◽  
pp. 163-182
Author(s):  
Kamalendu Pal
Keyword(s):  
Project Management ◽  
Software Development ◽  
Extreme Programming ◽  
Acceptance Testing ◽  
Software Project ◽  
Software Project Management ◽  
Software Projects ◽  
Agile Methodologies ◽  
Rigorous Testing ◽  
Software Development Methodologies

Agile software development methodologies are attracting attention from academics and practitioners for planning and managing software projects. The eXtreme Programming (XP) challenges conformist wisdom regarding software system development processes and practices as agile methodologies. To work efficiently in the current software development practice, characterized by requirements fuzziness, XP moves away from document-centric operations into people-centric management. In the XP-based software project, the customers play an essential role, having multiple responsibilities such as driving the project, gathering requirements (‘user stories'), and exercising quality control (or acceptance testing). Besides, the customers must liaise with external project stakeholders (e.g., funding authorities, end-users) while maintaining the development team's trust and the wider business. The success of such software project management practices relies on the quality result of each stage of development obtained through rigorous testing. This chapter describes three characteristics of XP project management: customer role, software testing feedback, and learning.

Sign in / Sign up

Export Citation Format

Share Document