A Student-Centered Learning Approach to Design for Manufacturability: Meeting the Needs of an Often- Forgotten Customer

A hands-on learning module was implemented at Marquette University in 2012 to teach biomedical engineering students about basic manufacturing processes, lean manufacturing principles, and design for manufacturability. It incorporates active and student-centered learning as part of in-class assembly line simulations. Since then, it has evolved from three class periods to five. The module begins with two classroom presentations on manufacturing operations and electronics design, assembly, and testing. Students then participate in an in-class assembly line simulation exercise where they build and test an actual product per written work instructions. They reflect on this experience and suggest design and process changes to improve the assembly line process and quality, save time, and reduce cost and waste. At the end of the module students implement their suggested design and process improvements and repeat the exercise to determine the impact of their improvements. They learn of the importance of Design for Manufacturability, well-written work instructions, process design, and designing a product not only for the end user, but also for the assemblers and inspectors. Details of the module, and its implementation and assessment are presented along with student feedback and faculty observations

An open source collaboration infrastructure for Calibre

The study of Free and Open Source (Libre) software and the benefits provided by its processes and products to collaborative software development has been somewhat ad hoc. Each project wishing to use tools and techniques drawn from Libre software conducts its own research, thus duplicating effort, consequently there is a lack of established community practice on which new projects can draw. Long-standing intuitive theories of Libre development lack empirical validation. The long-term goal is to provide a resource to guide the evolution of Libre-software projects, from inception to maturity. The CALIBRE project is a co-ordination action aiming to address these issues through its research, its wider educational goals, and with an open invitation to the community to contribute. To succeed, the CALIBRE project needs an effective technological infrastructure which must support internal and external collaboration, communication and contribution to the project. The requirements of CALIBRE are similar to those of a Libre software project; this suggests that adopting a SourceForge-style environment which will be incrementally enhanced with further specialised tools as the requirements become better understood will be a sensible strategy

An artefact repository to support distributed software engineering

The Open Source Component Artefact Repository (OSCAR) system is a component of the GENESIS platform designed to non-invasively inter-operate with work-flow management systems, development tools and existing repository systems to support a distributed software engineering team working collaboratively. Every artefact possesses a collection of associated meta-data, both standard and domain-specific presented as an XML document. Within OSCAR, artefacts are made aware of changes to related artefacts using notifications, allowing them to modify their own meta-data actively in contrast to other software repositories where users must perform all and any modifications, however trivial. This recording of events, including user interactions provides a complete picture of an artefact's life from creation to (eventual) retirement with the intention of supporting collaboration both amongst the members of the software engineering team and agents acting on their behalf

A Hands-On, Active Learning Approach to Increasing Manufacturing Knowledge in Engineering Students

This paper describes a new learning module implemented as part of the senior capstone design course at Marquette University to teach engineering students about basic manufacturing processes, lean manufacturing principles, and design for manufacturability. The module includes several examples of active and student centered learning as part of an in-class assembly line simulation exercise. Students reflected on this experience, and suggested process improvements to save time, reduce cost and waste, and improve the assembly line process. They learned of the importance of manufacturing documentation, process design, and design for assembly. At the end of the module, students understood the importance of designing a product not only for the end user, but also for the assemblers and inspectors. Details of the module design and implementation will be presented along with comments from students

Supporting collaboration within the eScience community

Collaboration is a core activity at the heart of large-scale co- operative scientific experimentation. In order to support the emergence of Grid-based scientific collaboration, new models of e-Science working methods are needed. Scientific collaboration involves production and manipulation of various artefacts. Based on work done in the software engineering field, this paper proposes models and tools which will support the representation and production of such artefacts. It is necessary to provide facilities to classify, organise, acquire, process, share, and reuse artefacts generated during collaborative working. The concept of a "design space" will be used to organise scientific design and the composition of experiments, and methods such as self-organising maps will be used to support the reuse of existing artefacts. It is proposed that this work can be carried out and evaluated in the UK e-Science community, using an "industry as laboratory" approach to the research, building on the knowledge, expertise, and experience of those directly involved in e-Science

Active artefact management for distributed software engineering

We describe a software artefact repository that provides its contents with some awareness of their own creation. "Active" artefacts are distinguished from their passive counterparts by their enriched meta-data model which reflects the work-flow process that created them, the actors responsible, the actions taken to change the artefact, and various other pieces of organisational knowledge. This enriched view of an artefact is intended to support re-use of both software and the expertise gained when creating the software. Unlike other organisational knowledge systems, the meta-data is intrinsically part of the artefact and may be populated automatically from sources including existing data-format specific information, user supplied data and records of communication. Such a system is of increased importance in the world of "virtual teams" where transmission of vital organisational knowledge, at best difficult, is further constrained by the lack of direct contact between engineers and differing development cultures

An evaluation framework to drive future evolution of a research prototype

The Open Source Component Artefact Repository (OSCAR) requires evaluation to confirm its suitability as a development environment for distributed software engineers. The evaluation will take note of several factors including usability of OSCAR as a stand-alone system, scalability and maintainability of the system and novel features not provided by existing artefact management systems. Additionally, the evaluation design attempts to address some of the omissions (due to time constraints) from the industrial partner evaluations. This evaluation is intended to be a prelude to the evaluation of the awareness support being added to OSCAR; thus establishing a baseline to which the effects of awareness support may be compared

Communication and conflict issues in collaborative software research projects

The Open Source Component Artefact Repository (OS- CAR) was developed under the auspices of the GENESIS project to store data produced during the software development process. Significant problems were encountered during the course of the project in both the development itself and management of the project. The reasons for and potential solutions to these problems are examined with the intention of developing a set of guidelines to enable participants in other collaborative projects to avoid these pitfalls. We wish to make it clear that we attach no opprobrium to any of the participants in the GENESIS project as many of the issues we outline below have solutions only visible with hindsight. Instead, we seek to provide a fair-minded critique of our role and the mistakes we made in a fairly typical two-year EU research project, and to provide a set of recommendations for other similar projects, in order that they can (attempt to) avoid suffering similarly

Open-source artefact management

This paper presents the GENESIS project, which aims to develop an open-source, light-weight, process-aware (and process-neutral) workflow management system. In particukar OSCAR, the artefact repository, is discussed. The requirements of a system for artefact management and storage are described, and the concept of active artefacts is explained. The software engineering methods which will be used in the project are described and some examples of the open-source tooles which may be used are described

The experience of OSCAR

Evolutionary development of a large software component by a small team within a larger research project has many problems in common with industrial software development as well as giving rise to its own unique problems. We reflect on these problems based on our experience developing OSCAR within the GENESIS project. Key issues are identified and possible ways to overcome or ameliorate these problems are suggested