Software tools for project management: focus on collaborative management

Today, projects involve members from different geographical areas more than any other time in history. Thus, adequate Collaborative Project Management Software (CollabPMS) solutions are needed to enable individuals and organizations to manage, communicate and work together across time and space barriers. This article describes a set of managerial and collaborative functionalities that a CollabPMS should provide to support the complexities of a distributed project effectively. Out of hundreds software packages available in the market, four were selected, ProjectLibre, Redmine, Microsoft Project 2013 and Clarizen, to assess if they have the described functionalities. Clarizen can be considered the best software for managing distributed projects, because it provides, by default, all the managerial functions and the collaborative features that support the coordinated collaboration level. ProjectLibre was the software that less stood out in this evaluation, although it provides the majority of the outlined managerial functionalities it doesn't support any level of collaboration.info:eu-repo/semantics/publishedVersio

The use of software tools for project management: focus on collaborative management

Dissertação de mestrado em Engenharia IndustrialToday, projects involve members from different geographical areas more than any other time in history. Thus, adequate Collaborative Project Management Software (CollabPMS) solutions are needed to enable individuals and organizations to manage, communicate and work together across time and space barriers. This dissertation describes a set of managerial and collaborative functionalities that a CollabPMS should provide to support the complexities of a distributed project effectively. Out of hundreds of software packages available in the market, four were selected, ProjectLibre, Redmine, Microsoft Project Professional 2013 and Clarizen, to assess whether they had or not functionalities that we described. Clarizen can be considered the best software for managing distributed projects, because it provides, by default, all the required managerial functionalities and the collaborative features that support the coordinated collaboration level. ProjectLibre was the software that less stood out in this evaluation, because although it provides the majority of the outlined managerial functionalities it doesn’t support any level of collaboration.Hoje, os projetos envolvem membros de diferentes áreas geográficas mais do que em qualquer outro momento da história. Assim sendo, são necessárias soluções adequadas de software colaborativo de gestão de projectos para permitir que indivíduos e organizações giram, comuniquem e trabalhem em conjunto ultrapassando as barreiras do tempo e do espaço. Esta dissertação descreve um conjunto de funcionalidades de gestão e de colaboração que um software colaborativo de gestão de projectos deve ter para apoiar as complexidades de um projeto distribuído de forma eficaz. Das centenas de pacotes de software disponíveis no mercado, quatro foram selecionados, ProjectLibre, Redmine, Microsoft Project Profissional 2013 e Clarizen, para avaliar se eles tinham ou não as funcionalidades que descrevemos. Clarizen pode ser considerado o melhor software para gerir projetos distribuídos, porque fornece, por defeito, todas as funcionalidades de gestão requeridas e todas as funções de colaboração que suportam o nível de colaboração coordenado. ProjectLibre foi o software que menos se destacou nesta avaliação, porque, embora forneça a maioria das funcionalidades de gestão delineadas, não suporta qualquer nível de colaboração

Support for collaborative component-based software engineering

Collaborative system composition during design has been poorly supported by traditional CASE tools (which have usually concentrated on supporting individual projects) and almost exclusively focused on static composition. Little support for maintaining large distributed collections of heterogeneous software components across a number of projects has been developed. The CoDEEDS project addresses the collaborative determination, elaboration, and evolution of design spaces that describe both static and dynamic compositions of software components from sources such as component libraries, software service directories, and reuse repositories. The GENESIS project has focussed, in the development of OSCAR, on the creation and maintenance of large software artefact repositories. The most recent extensions are explicitly addressing the provision of cross-project global views of large software collections and historical views of individual artefacts within a collection. The long-term benefits of such support can only be realised if OSCAR and CoDEEDS are widely adopted and steps to facilitate this are described. This book continues to provide a forum, which a recent book, Software Evolution with UML and XML, started, where expert insights are presented on the subject. In that book, initial efforts were made to link together three current phenomena: software evolution, UML, and XML. In this book, focus will be on the practical side of linking them, that is, how UML and XML and their related methods/tools can assist software evolution in practice. Considering that nowadays software starts evolving before it is delivered, an apparent feature for software evolution is that it happens over all stages and over all aspects. Therefore, all possible techniques should be explored. This book explores techniques based on UML/XML and a combination of them with other techniques (i.e., over all techniques from theory to tools). Software evolution happens at all stages. Chapters in this book describe that software evolution issues present at stages of software architecturing, modeling/specifying, assessing, coding, validating, design recovering, program understanding, and reusing. Software evolution happens in all aspects. Chapters in this book illustrate that software evolution issues are involved in Web application, embedded system, software repository, component-based development, object model, development environment, software metrics, UML use case diagram, system model, Legacy system, safety critical system, user interface, software reuse, evolution management, and variability modeling. Software evolution needs to be facilitated with all possible techniques. Chapters in this book demonstrate techniques, such as formal methods, program transformation, empirical study, tool development, standardisation, visualisation, to control system changes to meet organisational and business objectives in a cost-effective way. On the journey of the grand challenge posed by software evolution, the journey that we have to make, the contributory authors of this book have already made further advances

DesignWorld : a tool for team collaboration in high band virtual environments

Current software tools for documenting and developing models of buildings focus on supporting a single user who is a specialist in the specific software used within their own discipline. Extensions to these tools for use by teams maintain the single discipline view and focus on version and file management. There is a perceived need in industry to have tools that specifically support collaboration among individuals from multiple disciplines with both a graphical representation of the design and a persistent data model. This project involves the development of a prototype of such a software tool. We have identified multi-user 3D virtual worlds as an appropriate software base for the development of a collaborative design tool. These worlds are inherently multi-user and therefore directly support collaboration through a sense of awareness of others in the virtual world, their location within the world, and provide various channels for direct and indirect communication. Such software platforms also provide a 3D building and modelling environment that can be adapted to the needs of the building and construction industry. DesignWorld is a prototype system for collaborative design developed by augmenting the Second Life (SL) commercial software platform1 with a collection web-based tools for communication and design. Agents manage communication between the 3D virtual world and the web-based tools. In addition, agents maintain a persistent external model of designs in the 3D world which can be augmented with data such as relationships, disciplines and versions not usually associated with 3D virtual worlds but required in design scenarios

Planning and implementation of effective collaboration in construction projects

The 21st century is now seen as the time for the construction industry to embrace new ways of working if it is to continue to be competitive and meet the needs of its ever demanding clients. Collaborative working is considered by many to be essential if design and construction teams are to consider the whole lifecycle of the construction product. Much of the recent work on collaborative working has focused on the delivery of technological solutions with a focus on web (extranets), CAD (visualisation), and knowledge management technologies. However, it is now recognised that good collaboration does not result from the implementation of information technology solutions alone. The organisational and people issues, which are not readily solved by pure technical systems, need to be resolved. However, approaches that exclusively focus on organisational and people issues will not reap the benefits derived from the use of technology, especially in the context of distributed teams which are the norm in construction. Work currently being undertaken at Loughborough University aims to bring together the benefits enabled by the technology, with the organisational, and its people issues to provide a framework enabling high level strategic decisions to be made to implement effective collaboration. This paper reports on the initial stages of the project: the background to the project, the methodology used, and findings from the literature survey and the requirements capture survey conducted as part of the project

A design recording framework to facilitate knowledge sharing in collaborative software engineering

This paper describes an environment that allows a development team to share knowledge about software artefacts by recording decisions and rationales as well as supporting the team in formulating and maintaining design constraints. It explores the use of multi-dimensional design spaces for capturing various issues arising during development and presenting this meta-information using a network of views. It describes a framework to underlie the collaborative environment and shows the supporting architecture and its implementation. It addresses how the artefacts and their meta-information are captured in a non-invasive way and shows how an artefact repository is embedded to store and manage the artefacts

DATUM in Action

This collaborative research data management planning project (hereafter the RDMP project) sought to help a collaborative group of researchers working on an EU FP7 staff exchange project (hereafter the EU project) to define and implement good research data management practice by developing an appropriate DMP and supporting systems and evaluating their initial implementation. The aim was to "improve practice on the ground" through more effective and appropriate systems, tools/solutions and guidance in managing research data. The EU project (MATSIQEL - (Models for Ageing and Technological Solutions For Improving and Enhancing the Quality of Life), funded under the Marie Curie International Research Staff Exchange Scheme, is accumulating expertise for the mathematical and computer modelling of ageing processes with the aim of developing models which can be implemented in technological solutions (e.g. monitors, telecare, recreational games) for improving and enhancing quality of life.1 Marie Curie projects do not fund research per se, so the EU project has no resources to fund commercial tools for research data management. Lead by Professor Maia Angelova, School of Computing, Engineering and Information Sciences (SCEIS) at Northumbria University, it comprises six work packages involving researchers at Northumbria and in Australia, Bulgaria, Germany, Mexico and South Africa. The RDMP project focused on one of its work packages (WP4 Technological Solutions and Implementation) with some reference to another work package lead by the same person at Northumbria University (WP5 Quality of Life). The RDMP project‟s innovation was less about the choice of platform/system, as it began with existing standard office technology, and more about how this can be effectively deployed in a collaborative scenario to provide a fit-for-purpose solution with useful and usable support and guidance. It built on the success of the Datum for Health project by taking it a stage further, moving from a solely health discipline to an interdisciplinary context of health, social care and mathematical/computer modelling, and from a Postgraduate Research Student context to an academic researcher context, with potential to reach beyond the University boundaries. In addition, since the EU project is re-using data from elsewhere as well as creating its own data; a wide range of RDM issues were addressed. The RDMP project assessed the transferability of the DATUM materials and the tailored DATUM DMP

Characterization and Classification of Collaborative Tools

Traditionally, collaboration has been a means for organizations to do their work. However, the context in which they do this work is changing, especially in regards to where the work is done, how the work is organized, who does the work, and with this the characteristics of collaboration. Software development is no exception; it is itself a collaborative effort that is likewise affected by these changes. In the context of both open source software development projects and communities and organizations that develop corporate products, more and more developers need to communicate and liaise with colleagues in geographically distant places about the software product they are conceiving, designing, building, testing, debugging, deploying and maintaining. Thus, work teams face sizeable collaborative challenges, for which they have need of tools that they can use to communicate and coordinate their Work efficiently

Collaborative yet independent: Information practices in the physical sciences

In many ways, the physical sciences are at the forefront of using digital tools and methods to work with information and data. However, the fields and disciplines that make up the physical sciences are by no means uniform, and physical scientists find, use, and disseminate information in a variety of ways. This report examines information practices in the physical sciences across seven cases, and demonstrates the richly varied ways in which physical scientists work, collaborate, and share information and data. This report details seven case studies in the physical sciences. For each case, qualitative interviews and focus groups were used to understand the domain. Quantitative data gathered from a survey of participants highlights different information strategies employed across the cases, and identifies important software used for research. Finally, conclusions from across the cases are drawn, and recommendations are made. This report is the third in a series commissioned by the Research Information Network (RIN), each looking at information practices in a specific domain (life sciences, humanities, and physical sciences). The aim is to understand how researchers within a range of disciplines find and use information, and in particular how that has changed with the introduction of new technologies