Benefits of TSPi in a software project under a small settings enviroment

This article presents a case study about the TSPi benefits in a software project under a Small Settings environment. An adapted process based on the TSPi was defined. The pilot project had a schedule and budget restricted. The process began collecting historical projects data in order to get a measure repository. The project was launched defining the following goals: increase the productivity, reduce the test time and improve the product quality. Finally, the results were analysed and the goals were verified.

Configuración de un entorno de trabajo para el desarrollo de software ágil con integración continua

Hoy en día, existen numerosos sistemas (financieros, fabricación industrial, infraestructura de servicios básicos, etc.) que son dependientes del software. Según la definición de Ingeniería del Software realizada por I. Sommerville, “la Ingeniería del Software es una disciplina de la ingeniería que comprende todos los aspectos de la producción de software desde las etapas iniciales de la especificación del sistema, hasta el mantenimiento de éste después de que se utiliza.” “La ingeniería del software no sólo comprende los procesos técnicos del desarrollo de software, sino también actividades tales como la gestión de proyectos de software y el desarrollo de herramientas, métodos y teorías de apoyo a la producción de software.” Los modelos de proceso de desarrollo software determinan una serie de pautas para poder desarrollar con éxito un proyecto de desarrollo software. Desde que surgieran estos modelos de proceso, se investigado en nuevas maneras de poder gestionar un proyecto y producir software de calidad. En primer lugar surgieron las metodologías pesadas o tradicionales, pero con el avance del tiempo y la tecnología, surgieron unas nuevas llamadas metodologías ágiles. En el marco de las metodologías ágiles cabe destacar una determinada práctica, la integración continua. Esta práctica surgió de la mano de Martin Fowler, con el objetivo de facilitar el trabajo en grupo y automatizar las tareas de integración. La integración continua se basa en la construcción automática de proyectos con una frecuencia alta, promoviendo la detección de errores en un momento temprano para poder dar prioridad a corregir dichos errores. Sin embargo, una de las claves del éxito en el desarrollo de cualquier proyecto software consiste en utilizar un entorno de trabajo que facilite, sistematice y ayude a aplicar un proceso de desarrollo de una forma eficiente. Este Proyecto Fin de Grado (PFG) tiene por objetivo el análisis de distintas herramientas para configurar un entorno de trabajo que permita desarrollar proyectos aplicando metodologías ágiles e integración continua de una forma fácil y eficiente. Una vez analizadas dichas herramientas, se ha propuesto y configurado un entorno de trabajo para su puesta en marcha y uso. Una característica a destacar de este PFG es que las herramientas analizadas comparten una cualidad común y de alto valor, son herramientas open-source. El entorno de trabajo propuesto en este PFG presenta una arquitectura cliente-servidor, dado que la mayoría de proyectos software se desarrollan en equipo, de tal forma que el servidor proporciona a los distintos clientes/desarrolladores acceso al conjunto de herramientas que constituyen el entorno de trabajo. La parte servidora del entorno propuesto proporciona soporte a la integración continua mediante herramientas de control de versiones, de gestión de historias de usuario, de análisis de métricas de software, y de automatización de la construcción de software. La configuración del cliente únicamente requiere de un entorno de desarrollo integrado (IDE) que soporte el lenguaje de programación Java y conexión con el servidor. ABSTRACT Nowadays, numerous systems (financial, industrial production, basic services infrastructure, etc.) depend on software. According to the Software Engineering definition made by I.Sommerville, “Software engineering is an engineering discipline that is concerned with all aspects of software production from the early stages of system specification through to maintaining the system after it has gone into use.” “Software engineering is not just concerned with the technical processes of software development. It also includes activities such as software project management and the development of tools, methods, and theories to support software production.” Software development process models determine a set of guidelines to successfully develop a software development project. Since these process models emerged, new ways of managing a project and producing software with quality have been investigated. First, the so-called heavy or traditional methodologies appeared, but with the time and the technological improvements, new methodologies emerged: the so-called agile methodologies. Agile methodologies promote, among other practices, continuous integration. This practice was coined by Martin Fowler and aims to make teamwork easier as well as automate integration tasks. Nevertheless, one of the keys to success in software projects is to use a framework that facilitates, systematize, and help to deploy a development process in an efficient way. This Final Degree Project (FDP) aims to analyze different tools to configure a framework that enables to develop projects by applying agile methodologies and continuous integration in an easy and efficient way. Once tools are analyzed, a framework has been proposed and configured. One of the main features of this FDP is that the tools under analysis share a common and high-valued characteristic: they are open-source. The proposed framework presents a client-server architecture, as most of the projects are developed by a team. In this way, the server provides access the clients/developers to the tools that comprise the framework. The server provides continuous integration through a set of tools for control management, user stories management, software quality management, and software construction automatization. The client configuration only requires a Java integrated development environment and network connection to the server.

Fuel consumption study. Urban traffic control system (UTCS) software support project. Final report.

Federal Energy Administration, Office of Transportation Policy and Research, Washington, D.C.

Action research to explore perceptions of risk in project management

Uses research in a major UK company on the introduction of an electronic document management system to explore perceptions of, and attitudes to, risk. Phenomenological methods were used; with subsequent dialogue transcripts evaluated with Winmax dialogue software, using an adapted theoretical framework based upon an analysis of the literature. The paper identifies a number of factors, and builds a framework, that should support a greater understanding of risk assessment and project management by the academic community and practitioners.

National whoppercropper - risk management discussion support software

It is a paradox that in a country with one of the most variable climates in the world, cropping decisions are sometimes made with limited consideration of production and resource management risks. There are significant opportunities for improved performance based on targeted information regarding risks resulting from decision options. WhopperCropper is a tool to help agricultural advisors and farmers capture these benefits and use it to add value to their intuition and experience. WhopperCropper allows probability analysis of the effects of a range of selectable crop inputs and existing resources on yield and economic outcomes. Inputs can include agronomic inputs (e.g crop type, N fertiliser rate), resources (e.g soil water at sowing), and seasonal climate forecast (SOI phase). WhopperCropper has been successfully developed and refined as a discussion-support process for decision makers and their advisers in the northern grains region of Australia. The next phase of the project will build on the current project by extending its application nationally and enhancing the resource management aspects. A commercial partner, with over 800 advisor clients nationally, will participate in the project.

A Small Settings Case Study using TSPi in a Software Project

This article introduces a small setting case study about the benefits of using TSPi in a software project. An adapted process from the current process based on the TSPi was defined. The pilot project had schedule and budget constraints. The process began by gathering historical data from previous projects in order to get a measurement repository. The project was launched with the following goals: increase the productivity, reduce the test time and improve the product quality. Finally, the results were analysed and the goals were verified.

Specifics in Applying Agile Software Methodologies in Portal Solutions

Agile methodologies are becoming more popular in the software development process nowadays. The iterative development lifecycle, openness to frequent changes, tight cooperation with the client and among the software engineers are turning into more and more effective practices and respond to a higher extend to the current business needs. It is natural to raise the question which methodology is the most suitable for use when starting and managing a project. This depends on many factors—product characteristics, technologies used, client’s and developer’s experience, project type. A systematic analysis of the most common problems appearing when developing a particular type of projects—public portal solutions, is proposed. In the case at hand a very close interaction with various types of end users is observed. This is a prerequisite for permanent changes during the development and support cycles, which makes them ideal candidates for using an agile methodology. We will compare the ways in which each methodology addresses the specific problems arising and will finish with ranking them according to their relevance. This might help the project manager in choosing one or a combination of the methodologies.

Social Network Structure as a Critical Success Condition for Open Source Software Project Communities

In recent years, a surprising new phenomenon has emerged in which globally-distributed online communities collaborate to create useful and sophisticated computer software. These open source software groups are comprised of generally unaffiliated individuals and organizations who work in a seemingly chaotic fashion and who participate on a voluntary basis without direct financial incentive. The purpose of this research is to investigate the relationship between the social network structure of these intriguing groups and their level of output and activity, where social network structure is defined as 1) closure or connectedness within the group, 2) bridging ties which extend outside of the group, and 3) leader centrality within the group. Based on well-tested theories of social capital and centrality in teams, propositions were formulated which suggest that social network structures associated with successful open source software project communities will exhibit high levels of bridging and moderate levels of closure and leader centrality. The research setting was the SourceForge hosting organization and a study population of 143 project communities was identified. Independent variables included measures of closure and leader centrality defined over conversational ties, along with measures of bridging defined over membership ties. Dependent variables included source code commits and software releases for community output, and software downloads and project site page views for community activity. A cross-sectional study design was used and archival data were extracted and aggregated for the two-year period following the first release of project software. The resulting compiled variables were analyzed using multiple linear and quadratic regressions, controlling for group size and conversational volume. Contrary to theory-based expectations, the surprising results showed that successful project groups exhibited low levels of closure and that the levels of bridging and leader centrality were not important factors of success. These findings suggest that the creation and use of open source software may represent a fundamentally new socio-technical development process which disrupts the team paradigm and which triggers the need for building new theories of collaborative development. These new theories could point towards the broader application of open source methods for the creation of knowledge-based products other than software.

Advances in an emergency management software for the Canary Islands

[EN]Capaware is a free software platform to develop 3D multilayer geographical applications. The project has been developed by the Technological Institute of the Canary Islands and the University of Las Palmas de Gran Canaria during the last years.

Iowa DOT Project Management Peer Exchange, 2016

This project supported the planning and conduct of a two-day Iowa Department of Transportation–hosted peer exchange for state agencies that have implemented some or all of the suggested strategies outlined in the Second Strategic Highway Research Program–sponsored project R10, Project Management Strategies for Complex Projects. Presentations were made by participating states, and several opportunities were provided for directed discussion. General themes emerging from the presentations and discussions were identified as follows: To implement improvements in project management processes, agency leadership needs to decide that a new approach to project management is worth pursuing and then dedicate resources to developing a project management plan. The change to formalized project management and five-dimensional project management (5DPM) requires a culture shift in agencies from segmented “silo” processes to collaborative, cooperative processes that make communication and collaboration high priorities. Agencies need trained project managers who are empowered to execute the project management plan, as well as properly trained functional staff. Project management can be centralized or decentralized with equal effect. After an agency’s project management plan and structure are developed, software tools and other resources should be implemented to support the plan and structure. All projects will benefit from enhanced project management, but the project management plan should specify appropriate approaches for several project levels as defined by factors in addition to dollar value. Project management should be included in an agency’s project development manual.

Entrepreneurship in project management systems: proposal of a model and preliminary empirical evidence

This study analyzes the manifestation of the dimensions of Entrepreneurial Orientation (EO) and Project Management Systems (PMS). We used a qualitative approach to conduct exploratory research through a study in literature and a pilot case in a software company. Data was collected from semi structured interviews, documents, and records on file, then triangulated and treated with content analysis. The model proposed for the relationship between the types of PMS (ad hoc, Classic PM, innovation, entrepreneurship/intrapreneurship) and the dimensions of EO (innovativeness, risk-taking, proactiveness, competitive aggressiveness, and autonomy), was partially corroborated by empirical studies. New studies are suggested to validate the applicability and setup of the model.

Final report : a software diagnostic tool for evaluating distress mechanisms in bridges exposed to aggressive environments

Durability issues of reinforced concrete construction cost millions of dollars in repair or demolition. Identification of the causes of degradation and a prediction of service life based on experience, judgement and local knowledge has limitations in addressing all the associated issues. The objective of this CRC CI research project is to develop a tool that will assist in the interpretation of the symptoms of degradation of concrete structures, estimate residual capacity and recommend cost effective solutions. This report is a documentation of the research undertaken in connection with this project. The primary focus of this research is centred on the case studies provided by Queensland Department of Main Roads (QDMR) and Brisbane City Council (BCC). These organisations are endowed with the responsibility of managing a huge volume of bridge infrastructure in the state of Queensland, Australia. The main issue to be addressed in managing these structures is the deterioration of bridge stock leading to a reduction in service life. Other issues such as political backlash, public inconvenience, approach land acquisitions are crucial but are not within the scope of this project. It is to be noted that deterioration is accentuated by aggressive environments such as salt water, acidic or sodic soils. Carse, 2005, has noted that the road authorities need to invest their first dollars in understanding their local concretes and optimising the durability performance of structures and then look at potential remedial strategies.

Decision - Support Software Tool Handbook

The road and transport industry in Australia and overseas has come a long way to understanding the impact of road traffic noise on the urban environment. Most road authorities now have guidelines to help assess and manage the impact of road traffic noise on noise-sensitive areas and development. While several economic studies across Australia and overseas have tried to value the impact of noise on property prices, decision-makers investing in road traffic noise management strategies have relatively limited historic data and case studies to go on. The perceived success of a noise management strategy currently relies largely on community expectations at a given time, and is not necessarily based on the analysis of the costs and benefits, or the long-term viability and value to the community of the proposed treatment options. With changing trends in urban design, it is essential that the 'whole-of-life' costs and benefits of noise ameliorative treatment options and strategies be identified and made available for decisionmakers in future investment considerations. For this reason, CRC for Construction Innovation Australia funded a research project, Noise Management in Urban Environments to help decision-makers with future road traffic noise management investment decisions. RMIT University and the Queensland Department of Main Roads (QDMR) have conducted the research work, in collaboration with the Queensland Department of Public Works, ARUP Pty Ltd, and the Queensland University of Technology. The research has formed the basis for the development of a decision-support software tool, and helped collate technical and costing data for known noise amelioration treatment options. We intend that the decision support software tool (DST) should help an investment decision-maker to be better informed of suitable noise ameliorative treatment options on a project-by-project basis and identify likely costs and benefits associated with each of those options. This handbook has been prepared as a procedural guide for conducting a comparative assessment of noise ameliorative options. The handbook outlines the methodology and assumptions adopted in the decision-support framework for the investment decision-maker and user of the DST. The DST has been developed to provide an integrated user-friendly interface between road traffic noise modelling software, the relevant assessment criteria and the options analysis process. A user guide for the DST is incorporated in this handbook.

Project diagnostics : assessing the condition of projects and identifying poor health combing forces

In many cases, construction projects do not achieve the objectives that the project participants set for them. If participants could better understand how their project is performing overall, at various stages of its delivery, then the opportunities to achieve project success would almost certainly be greater. This paper documents a method of assessing the status of a project, at a point in its design or construction phase, or after completion. The status is assessed in terms of up to seven (7) key success factors. Any evidence of less than adequate performance in these performance areas is scrutinised to seek out the root causes of why this situation is happening. Using these identified root causes of under performance, general suggestions can then be made as to how to return the project to good health. A software package that assists in assessing the status of the project has been developed. The package is currently being calibrated before commercial release.