Engineering design project : series 1

This book is a compilation of engineering design projects which illustrates a detail explanation on the design process including all tools and methods involved in each design stage. The presented projects have been selected to prepare engineering students with the adequate knowledge and skills required in organizing product based project, formulating problems, generating and evaluating alternatives, preparing technical documentation and considering the sustainable and economic constraints for the product development and realization stage using the integration of various disciplines in mechanical and manufacturing engineering. This book is generally suitable as a reference to project-oriented problem-based learning (POPBL) activities at engineering institutions

Engineering design project : series 2

This book is a compilation of engineering design projects which illustrates a detail explanation on the design process including all tools and methods involved in each design stage. The presented projects have been selected to prepare engineering students with the adequate knowledge and skills required in organizing product based project, formulating problems, generating and evaluating alternatives, preparing technical documentation and considering the sustainable and economic constraints for the product development and realization stage using the integration of various disciplines in mechanical and manufacturing engineering. This book is generally suitable as a reference to project-oriented problem-based learning (POPBL) activities at engineering institutions

Metalinguistic Proposals

This paper sets out the felicity conditions for metalinguistic proposals, a type of directive illocutionary act. It discusses the relevance of metalinguistic proposals and other metalinguistic directives for understanding both small- and large-scale linguistic engineering projects, essentially contested concepts, metalinguistic provocations, and the methodology of ordinary language philosophy. Metalinguistic proposals are compared with other types of linguistic interventions, including metalinguistic negotiation, conceptual engineering, lexical warfare, and ameliorative projects

We Don't Need Another Hero? The Impact of "Heroes" on Software Development

A software project has "Hero Developers" when 80% of contributions are delivered by 20% of the developers. Are such heroes a good idea? Are too many heroes bad for software quality? Is it better to have more/less heroes for different kinds of projects? To answer these questions, we studied 661 open source projects from Public open source software (OSS) Github and 171 projects from an Enterprise Github. We find that hero projects are very common. In fact, as projects grow in size, nearly all project become hero projects. These findings motivated us to look more closely at the effects of heroes on software development. Analysis shows that the frequency to close issues and bugs are not significantly affected by the presence of project type (Public or Enterprise). Similarly, the time needed to resolve an issue/bug/enhancement is not affected by heroes or project type. This is a surprising result since, before looking at the data, we expected that increasing heroes on a project will slow down howfast that project reacts to change. However, we do find a statistically significant association between heroes, project types, and enhancement resolution rates. Heroes do not affect enhancement resolution rates in Public projects. However, in Enterprise projects, the more heroes increase the rate at which project complete enhancements. In summary, our empirical results call for a revision of a long-held truism in software engineering. Software heroes are far more common and valuable than suggested by the literature, particularly for medium to large Enterprise developments. Organizations should reflect on better ways to find and retain more of these heroesComment: 8 pages + 1 references, Accepted to International conference on Software Engineering - Software Engineering in Practice, 201

Development of a Rooftop Collaborative Experimental Space through Experiential Learning Projects

The Solar, Water, Energy, and Thermal Laboratory (SWEAT Lab) is a rooftop experimental space at the University of Texas at Austin built by graduate and undergraduate students in the Cockrell School of Engineering. The project was funded by the Texas State Energy Conservation Office and the University’s Green Fee Grant, a competitive grant program funded by UT Austin tuition fees to support sustainability-related projects and initiatives on campus. The SWEAT Lab is an on-going experiential learning facility that enables engineering education by deploying energy and water-related projects. To date, the lab contains a full weather station tracking weather data, a rainwater harvesting system and rooftop garden. This project presented many opportunities for students to learn first hand about unique engineering challenges. The lab is located on the roof of the 10 story Engineering Teaching Center (ETC) building, so students had to design and build systems with constraints such as weight limitations and wind resistance. Students also gained experience working with building facilities and management for structural additions, power, and internet connection for instruments. With the Bird’s eye view of UT Austin campus, this unique laboratory offers a new perspective and dimension to applied student research projects at UT Austin.Cockrell School of Engineerin

ADAPTS: An Intelligent Sustainable Conceptual Framework for Engineering Projects

This paper presents a conceptual framework for the optimization of environmental sustainability in engineering projects, both for products and industrial facilities or processes. The main objective of this work is to propose a conceptual framework to help researchers to approach optimization under the criteria of sustainability of engineering projects, making use of current Machine Learning techniques. For the development of this conceptual framework, a bibliographic search has been carried out on the Web of Science. From the selected documents and through a hermeneutic procedure the texts have been analyzed and the conceptual framework has been carried out. A graphic representation pyramid shape is shown to clearly define the variables of the proposed conceptual framework and their relationships. The conceptual framework consists of 5 dimensions; its acronym is ADAPTS. In the base are: (1) the Application to which it is intended, (2) the available DAta, (3) the APproach under which it is operated, and (4) the machine learning Tool used. At the top of the pyramid, (5) the necessary Sensing. A study case is proposed to show its applicability. This work is part of a broader line of research, in terms of optimization under sustainability criteria.Telefónica Chair “Intelligence in Networks” of the University of Seville (Spain

Management of multi-method engineering design research: a case study

There is a need for a research management methodology that will utilise research methods on an individual basis and when combined in a multi-method approach. An agreed methodology would enable rapid progress in achieving agreement on the main issues within engineering design research. Researchers at the University of Glasgow have developed a conceptual management methodology, testing it on three engineering design research projects. This paper describes the methodology and presents results indicating its ability to enable rigorous triangulation of research results obtained via different methods and across different research projects forming the basis of an effective management tool

The suitability of PRINCE2 for engineering infrastructure

The view that PRINCE2 was not suitable for application to infrastructure was identified in a study done for a separate purpose, namely, to examine project governance and methodology, which is not reported in this paper. It was asserted by several participants in interviews conducted with a sample of experienced practitioners across a range of industries and disciplines. This paper follows up on those comments by conducting an examination of PRINCE2 from an engineering infrastructure perspective to investigate the validity of this assertion. It takes a deductive, definitional approach to determine if there are any features in it that would cause difficulty for engineering infrastructure use. Seventeen features were examined, and 15 were found to have difficulty in application to the project management of engineering infrastructure. The remaining two found inconsistencies that were unlikely to cause too much difficulty. The features causing difficulty include non-generic terminology for the terms project, lifecycle and stage, using a product rather than a project-based process, use of an iterative product delivery process unsuited to predictive projects, use of a delivery process for all project phases, assumption of a board governance model with inappropriate accountabilities, lack of clarity around the use of the project plan, and absence of a lifecycle appropriate for engineering infrastructure, with PRINCE2 effectively self-declaring its need for a higher-level project lifecycle/ methodology from somewhere else. The paper concludes that PRINCE2 is quite poorly suited to managing engineering infrastructure projects and identifies that some of the reasons for this are likely to also cause difficulty for many ICT projects as well