396 research outputs found
Environments to support collaborative software engineering
With increasing globalisation of software production, widespread use of
software components, and the need to maintain software systems over long
periods of time, there has been a recognition that better support
for collaborative working is needed by software engineers.
In this paper, two approaches to developing
improved system support for collaborative software engineering are
described: GENESIS and OPHELIA.
As both projects are moving towards industrial trials and eventual publicreleases of their systems, this exercise of comparing and
contrasting our approaches has provided the basis for future
collaboration between our projects particularly in carrying out
comparative studies of our approaches in practical use
Taxing Collaborative Software Engineering
The engineering of complex software systems is often the result of a highly
collaborative effort. However, collaboration within a multinational enterprise
has an overlooked legal implication when developers collaborate across national
borders: It is taxable. In this short article, we discuss the unsolved problem
of taxing collaborative software engineering across borders. We (1) introduce
the reader to the basic principle of international taxation, (2) identify three
main challenges for taxing collaborative software engineering, and (3) estimate
the industrial significance of cross-border collaboration in modern software
engineering by measuring cross-border code reviews at a multinational software
company.Comment: 7 pages, 3 figure
Historical awareness support and its evaluation in collaborative software engineering
The types of awareness relevant to collaborative soft-
ware engineering are identified and an additional type,
"historical awareness" is proposed. This new type of
awareness is the knowledge of how software artefacts re-
sulting from collaboration have evolved in the course of
their development.
The types of awareness that different software engineer-
ing environment architectures can support are discussed. A
way to add awareness support to our existing OSCAR sys-
tem, a component of the GENESIS software engineering
platform, is proposed. Finally ways of instrumenting and
evaluating the awareness support offered by the modified
system are outlined
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
Tool Enhancement For Collaborative Software Engineering Education
Software development can be done by people have different background in various environments. Recent researches indicate that collaborative software development is important for student. Individual expected to work together become teamwork. The teamwork expected to understand collaborative software development include methods and tools in project development. Student with lack experience and communication skill is major problem in the collaborative software development. Teamwork skills are important in collaborative software development. Discussion and assessment component is a method to develop teamwork skill. This study performed develop collaborative tool that can support collaborative work of student. Apply assessment component in the collaborative tool to assess individual and team work. In testing and evaluation phase, the result indicates that the collaborative tool can be used to support collaborative work of student and to evaluate individual and team work skill
OntoMaven: Maven-based Ontology Development and Management of Distributed Ontology Repositories
In collaborative agile ontology development projects support for modular
reuse of ontologies from large existing remote repositories, ontology project
life cycle management, and transitive dependency management are important
needs. The Apache Maven approach has proven its success in distributed
collaborative Software Engineering by its widespread adoption. The contribution
of this paper is a new design artifact called OntoMaven. OntoMaven adopts the
Maven-based development methodology and adapts its concepts to knowledge
engineering for Maven-based ontology development and management of ontology
artifacts in distributed ontology repositories.Comment: Pre-print submission to 9th International Workshop on Semantic Web
Enabled Software Engineering (SWESE2013). Berlin, Germany, December 2-5, 201
Environments to Support Collaborative Software Engineering
With increasing globalisation of software production, widespread use of software components, and the need to maintain software systems over long periods of time, there has been a recognition that better support for collaborative working is needed by software engineers. In this paper,
two approaches to developing improved system support for collaborative software engineering are described: GENESIS
and OPHELIA. As both project are moving towards industrial trials and eventual public releases of their systems, this exercise of comparing and contrasting our approaches has provided the basis for future collaboration between our projects particularly in carrying out comparative studies of our approaches in practical use
The Impact of Dynamics of Collaborative Software Engineering on Introverts: A Study Protocol
Background: Collaboration among software engineers through face-to-face
discussions in teams has been promoted since the adoption of agile methods.
However, these discussions might demote the contribution of software engineers
who are introverts, possibly leading to sub-optimal solutions and creating work
environments that benefit extroverts. Objective: We aim to evaluate whether
providing software engineers with time to work individually and reason about a
collective problem is a setting that makes introverts more comfortable to
interact and contribute more, ultimately leading to better solutions. Method:
We plan to conduct a between-subjects study, with teams in a control group that
design a software architecture in a team discussion meeting and teams in a
treatment group in which subjects work individually before engaging in a
meeting. We will assess and compare the amount of contribution of introverts,
their subjective experiences, and the designed solutions. Limitations: As
extroverts will be present in both groups, we will not be able to conclude that
better solutions are solely due to the increased participation of introverts.
The analyses of their subjective experience and amount of contributions might
provide evidence to suggest the reasons for observed differences.Comment: 5 page
- …