RAPID PROTOTYPING ON THE EXAMPLE OF SOFTWARE DEVELOPMENT IN AUTOMOTIVE INDUSTRY - The Importance of their Provision for Software Projects at the Correct Time

Author(s):  
CUAUHTÉMOC LÓPEZ-MARTÍN ◽  
ALAIN ABRAN

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.


Author(s):  
Sebastian Baltes

AbstractAnalyzing and understanding software developers’ work habits and resulting needs is an essential prerequisite to improve software development practice. In our research, we utilize different qualitative and quantitative research methods to empirically investigate three underexplored aspects of software development: First, we analyze how software developers use sketches and diagrams in their daily work and derive requirements for better tool support. Then, we explore to what degree developers copy code from the popular online platform Stack Overflow without adhering to license requirements and motivate why this behavior may lead to legal issues for affected open source software projects. Finally, we describe a novel theory of software development expertise and identify factors fostering or hindering the formation of such expertise. Besides, we report on methodological implications of our research and present the open dataset SOTorrent, which supports researchers in analyzing the origin, evolution, and usage of content on Stack Overflow. The common goal for all studies we conducted was to better understand software developers’ work practices. Our findings support researchers and practitioners in making data-informed decisions when developing new tools or improving processes related to either the specific work habits we studied or expertise development in general.


2020 ◽  
Vol 110 (04) ◽  
pp. 226-230
Author(s):  
Andreas Selmaier ◽  
Benedikt Martens ◽  
Martin Sjarov ◽  
Marlene Kuhn ◽  
Meike Herbert ◽  
...  

Digitalisierungsprojekte sind Softwareprojekte. Sequenzielle Planungsmethoden, wie sie im konventionellen Projektmanagement überwiegend Anwendung finden, eignen sich nur bedingt für diesen Projekttyp, da die anwendungsspezifischen Anforderungen sowie die Abhängigkeiten der Anlagen und IT-Systeme untereinander zu einem erheblichen Anstieg der Gesamtkomplexität führen. In diesem Beitrag wird daher ein Ansatz zur systematischen Auswahl geeigneter Projektmanagementmethoden für Digitalisierungsprojekte vorgestellt, welcher die traditionelle Projektplanung im Produktionsumfeld um iterative Vorgehensweisen aus der Software- entwicklung ergänzt.   Digitalization projects are software projects. Less suitable for such projects are sequential planning methods often used in conventional project management, as application-specific requirements and interdependencies of facilities and IT systems considerably increase overall complexity. Therefore, this paper presents an approach for the systematic selection of suitable management methods for digitalization projects, which adds iterative procedures from software development to traditional project planning in the production environment.


Author(s):  
Izzat Alsmadi ◽  
Saqib Saeed

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.


2013 ◽  
pp. 84-117
Author(s):  
Salmiza Saul Hamid ◽  
Mohd Hairul Nizam Md Nasir ◽  
Shamsul Sahibuddin ◽  
Mustaffa Kamal Mohd Nor

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.


Author(s):  
Marcos Ruano-Mayoral ◽  
Ricardo Colomo-Palacios ◽  
Ángel García-Crespo ◽  
Juan Miguel Gómez-Berbís

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.


Author(s):  
Valerio Fernandes del Maschi ◽  
Luciano S. Souza ◽  
Mauro de Mesquita Spínola ◽  
Wilson Vendramel ◽  
Ivanir Costa ◽  
...  

The quality in software projects is related the deliveries that are adjusted to the use, and that they take care of to the objectives. In this way, Brazilian organizations of software development, especially the small and medium ones, need to demonstrate to future customers whom an initial understand of the business problem has enough. This chapter has as objective to demonstrate methodology, strategy, main phases and procedures adopted beyond the gotten ones of a small organization of development of software in the implantation of a Customized Software Engineering Process and of a Tool of Support to the Process in the period of 2004 to 2006 on the basis of rational unified process (RUP) and in the Microsoft solutions framework (MSF).


2015 ◽  
pp. 1722-1743
Author(s):  
Liguo Yu

Scheduling and staffing are important management activities in software projects. In closed-source software development, the relationships among development effort, time, and staffing have been well established and validated: the development effort determines the development time and the best number of developers that should be allocated to the project. However, there has been no similar research reported in open-source projects. In this chapter, the authors study the development effort, development time, and staffing in an open-source project, the Linux kernel project. Specifically, they investigate the power law relations among development effort, development time, and the number of active developers in the Linux kernel project. The authors find the power law relations differ from one branch to another branch in the Linux kernel project, which suggests different kinds of management and development styles might exist in different branches of the Linux kernel project. The empirical knowledge of software development effort obtained in this study could help project management and cost control in both open-source communities and closed-source industries.


2015 ◽  
Vol 6 (4) ◽  
pp. 39-68 ◽  
Author(s):  
Maryam Hassani Saadi ◽  
Vahid Khatibi Bardsiri ◽  
Fahimeh Ziaaddini

One of the major activities in effective and efficient production of software projects is the precise estimation of software development effort. Estimation of the effort in primary steps of software development is one of the most important challenges in managing software projects. Some reasons for these challenges such as: discordant software projects, the complexity of the manufacturing process, special role of human and high level of obscure and unusual features of software projects can be noted. Predicting the necessary efforts to develop software using meta-heuristic optimization algorithms has made significant progressions in this field. These algorithms have the potent to be used in estimation of the effort of the software. The necessity to increase estimation precision urged the authors to survey the efficiency of some meta-heuristic optimization algorithms and their effects on the software projects. To do so, in this paper, they investigated the effect of combining various optimization algorithms such as genetic algorithm, particle swarm optimization algorithm and ant colony algorithm on different models such as COCOMO, estimation based on analogy, machine learning methods and standard estimation models. These models have employed various data sets to evaluate the results such as COCOMO, Desharnais, NASA, Kemerer, CF, DPS, ISBSG and Koten & Gary. The results of this survey can be used by researchers as a primary reference.


Sign in / Sign up

Export Citation Format

Share Document