6,440 research outputs found

    Web-based support for managing large collections of software artefacts

    Get PDF
    There has been a long history of CASE tool development, with an underlying software repository at the heart of most systems. Usually such tools, even the more recently web-based systems, are focused on supporting individual projects within an enterprise or across a number of distributed sites. Little support for maintaining large heterogeneous collections of software artefacts across a number of projects has been developed. Within the GENESIS project, this has been a key consideration in the development of the Open Source Component Artefact Repository (OSCAR). Its most recent extensions are explicitly addressing the provision of cross project global views of large software collections as well as historical views of individual artefacts within a collection. The long-term benefits of such support can only be realised if OSCAR is widely adopted and various steps to facilitate this are described

    D2.4 Guidance and assessment tutorial: Inquiry Guidance and Assessment Tutorial

    Get PDF
    The weSPOT project aims at propagating scientific inquiry as the approach for science learning and teaching in combination with today’s curricula and teaching practices. It lowers the threshold for linking everyday life with science teaching in schools by technology. weSPOT supports the meaningful contextualization of scientific concepts by relating them to personal curiosity, experiences, and reasoning. weSPOT addresses several challenges in the area of science learning and technology support for building personal conceptual knowledge. The project focuses on inquiry-based learning with a theoretically sound and technology supported personal inquiry approach. The project is focused on three main development aspects: (a) define a reference model for inquiry-based learning skills, (b) create a diagnostic instrument for measuring inquiry skills, and (c) implement a working environment that allows the easy linking of inquiry activities with school curricula and legacy systems. The foreseen weSPOT Toolkit gives smart support for personal scientific inquiry to address a lack of scientific inquiry skills in an age group of 12-25. The current deliverable, D2.4, outlines the inquiry guidance and assessment tutorial, to support teachers in their quest for scientific inquiry. The inquiry guidance tutorial includes several items that will introduce the weSPOT IBL model to the teachers, provide them with examples of how to use it in practice, describe the available tools and show them how they work. This diagnostic tutorial is focused on the diagnostic instrument which will look at the entire inquiry life cycle which may start with the formulation of a research question and may end with the valorisation of the results and it will cover the four different complexities of inquiry, from confirmation inquiry to open, self-directed inquiry. The second part of the deliverable focuses on the diagnostic framework describing the adopted approach. The weSPOT diagnostic instrument for inquiry skills and competences aimed at a) to establish a European baseline of the current level of inquiry skills in the target group and b) to demonstrate the potential of the weSPOT-technology for STEM-learning in general.weSPOT Project IST (FP7/2007-2013) under grant agreement N° 318499

    Support for collaborative component-based software engineering

    Get PDF
    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

    An investigation into computer support for cooperative work in software engineering groups

    Get PDF
    The research of this thesis relates to Computer Supported Cooperative Work (CSCW) in the context of software engineering, and in particular software engineering education. Whilst research into group working has tended to be directed towards CSCW, very little research has been undertaken on group working within software engineering. Linked with CSCW is groupware, which is the class of tools that supports and augments groupwork. This thesis represents an attempt to contribute to the understanding of the groupware needs of software engineers, and to identify and trial groupware that supports software engineering activities. An infrastructure has been developed providing virtual environments, for use by both collocated and geographically distributed software engineering students, to support their groupwork. This infrastructure comprises of synchronous and asynchronous groupware, in the form of desktop video conferencing, and a shared information workspace. This shared workspace has been tailored from the groupware tool, Basic Support for Cooperative Work (BSCW).Within this thesis, hypotheses have been formulated as to the student use of these virtual environments. These hypotheses concentrate on the areas of: organisation and coordination of tasks, the level of cooperation that occurs within the phases of the software lifecycle, the usage of the functions within a shared workspace, and what importance is placed on the role of synchronous communication within software engineering student groupwork. Through a series of case studies it was possible to determine the outcome of these hypotheses using various data collection methods. These methods include questionnaires, focus group meetings, observations, and automatic monitoring of workspace activities. The outcomes of this thesis are that the hypotheses regarding organisation and coordination, and, the role of synchronous communication within software engineering, have been proved. Whilst the determination of the level of cooperation during the phases of the software lifecycle has not been proved, the use of functions within the shared workspace has been partly proved

    Evaluating groupware support for software engineering students

    Get PDF
    Software engineering tasks, during both development and maintenance, typically involve teamwork using computers. Team members rarely work on isolated computers. An underlying assumption of our research is that software engineering teams will work more effectively if adequately supported by network-based groupware technology. Experience of working with groupware and evaluating groupware systems will also give software engineering students a direct appreciation of the requirements of engineering such systems. This research is investigating the provision of such network-based support for software engineering students and the impact these tools have on their groupwork. We will first describe our experiences gained through the introduction of an asynchronous virtual environment ­ SEGWorld to support groupwork during the Software Engineering Group (SEG) project undertaken by all second year undergraduates within the Department of Computer Science. Secondly we will describe our Computer Supported Cooperative Work (CSCW) module which has been introduced into the students' final year of study as a direct result of our experience with SEG, and in particular its role within Software Engineering. Within this CSCW module the students have had the opportunity to evaluate various groupware tools. This has enabled them to take a retrospective view of their experience of SEGWorld and its underlying system, BSCW, one year on. We report our findings for SEG in the form of a discussion of the hypotheses we formulated on how the SEGs would use SEGWorld, and present an initial qualitative assessment of student feedback from the CSCW module

    Business Process Management Education in Academia: Status, challenges, and Recommendations

    Get PDF
    In response to the growing proliferation of Business Process Management (BPM) in industry and the demand this creates for BPM expertise, universities across the globe are at various stages of incorporating knowledge and skills in their teaching offerings. However, there are still only a handful of institutions that offer specialized education in BPM in a systematic and in-depth manner. This article is based on a global educators’ panel discussion held at the 2009 European Conference on Information Systems in Verona, Italy. The article presents the BPM programs of five universities from Australia, Europe, Africa, and North America, describing the BPM content covered, program and course structures, and challenges and lessons learned. The article also provides a comparative content analysis of BPM education programs illustrating a heterogeneous view of BPM. The examples presented demonstrate how different courses and programs can be developed to meet the educational goals of a university department, program, or school. This article contributes insights on how best to continuously sustain and reshape BPM education to ensure it remains dynamic, responsive, and sustainable in light of the evolving and ever-changing marketplace demands for BPM expertise
    • …
    corecore