Fuzzy classification context for the responsive and formal design process

Author(s):  
Solomon Gebreyohannes ◽  
William Edmonson ◽  
Albert Esterline ◽  
Abdollah Homaifar ◽  
Nadew Kibret
Author(s):  
Solomon Gebreyohannes ◽  
William Edmonson ◽  
Albert Esterline ◽  
Jules Chenou
Keyword(s):  

1994 ◽  
Vol 03 (02) ◽  
pp. 129-153 ◽  
Author(s):  
GEORGE TOYE ◽  
MARK R. CUTKOSKY ◽  
LARRY J. LEIFER ◽  
J. MARTY TENENBAUM ◽  
JAY GLICKSMAN

The SHARE project seeks to apply information technologies in helping design teams gather, organize, re-access, and communicate both informal and formal design information to establish a "shared understanding" of the design and design process. This paper presents the visions of SHARE, along with the research and strategies undertaken to build an infrastructure toward its realization. A preliminary prototype environment is being used by designers working on a variety of industry sponsored design projects. This testbed continues to inform and guide the development of NoteMail, MovieMail, and Xshare, as well as other components of the next generation SHARE environment that will help distributed design teams work together more effectively on the Internet.


2000 ◽  
Vol 1701 (1) ◽  
pp. 116-120 ◽  
Author(s):  
Douglas W. Harwood ◽  
Timothy R. Neuman ◽  
Joel P. Leisch

Six papers in this Record were presented at a conference session during the January 1994 TRB annual meeting. They address various aspects of the relationships among design speed, operating speed, and design consistency. All six papers are examined to show the interrelationships of design speed, operating speed, and design consistency; what changes are needed in the current design process and current design policies; how the concept of design consistency can produce better designs; and what research is needed to develop these concepts further. The improvements involve three key principles. First, design speeds must not be arbitrary but must be selected realistically based on projected operating speeds. Second, if lower design speed is used, all aspects of the roadway and its environment must be consistent with the lower speed. Third, large differences in operating speed between successive roadway elements represent design inconsistencies that can lead to safety problems. These principles can be used to develop a design process that leads to safer, more efficient, and more consistent designs. The TRB Committees on Operational Effects of Geometrics (A3A08) and on Geometric Design (A2A02) jointly sponsored the January 1994 conference session to call attention to the many unresolved issues about the roles of design speed, operating speed, and design consistency in creating highway designs that operate efficiently and safely and meet the needs of drivers. Originally, two alternative topics were considered: relationship of design speed and operating speed and the role of formal design consistency criteria in creating good highway designs. These topics were so interrelated that it was difficult to address one without the other. A key insight from the papers was that in a consistent design the design speed selected for use in determining the geometrics of the facility is similar to the operating speed of the completed facility. To call attention to the central role of several speed-related parameters in creating consistent designs, the session was titled “Speed.” Key points of the papers are summarized, generalizing the principles and philosophy for creating consistent designs, and suggesting directions for research to develop the ideas into practical design policies that highway engineers can apply.


2012 ◽  
Vol 232 ◽  
pp. 823-827
Author(s):  
Frederic Danesi ◽  
Nicolas Gardan ◽  
Elvis Kwassi

This article focuses on the optimization of a design process, in the context of automotive subcontracting opportunity. This optimization is guided by the underlying manufacturing process and by the industrial knowledge. We first show that the actual design studies are biased by the final goal (a formal design) and do not take into account early industrial needs (a draft design to draw up an estimate). We then demonstrate how an automaker subcontractor optimizes the early design process thanks to industrial knowledge.


2015 ◽  
Vol 7 (4) ◽  
pp. 1
Author(s):  
Paul James

<p>This is a research paper focused on assessing the design project manager behaviour and the raised managerial design issues relating to a formal design review in a metro project start-up. Very little research has been conducted in this area and the paper exposes weak aspects of the design review process previously unexplored in today’s metro construction environments.</p><p>In order to consider more implicitly the questions and issues raised, this empirical groundwork utilised an interpretive perspective. The scope for this research was the design mechanisms/processes associated with a large single package – a TBM Segment Design. The population for this study was made up of a number of individuals (12) engineers/Managers located at site, and a total of 9 Engineers/Managers were determined as the resultant sample frame.</p><p>The outcomes consisted of six (6) themes, namely: Mismanagement Issues; Management Interference; Technical Issues; Contractor Design managers Issues; Documentation Issues; Communication Issues, raised from an initial question; these were further developed into four (4) final themes relating to an assessment of the managerial implications.</p><p>The paper gives a clear insight into the practical issues surrounding a metro design review and the development of appropriate managerial strategies that can be implemented. The paper also addresses some of the implications for continuing design review developments. The paper suggests that projects of this kind may benefit from an Integrated Collaborative Design approach through integrating construction expertise with the design process at the detail design phase.</p>


Author(s):  
Robert Knobel ◽  
Mark Chen ◽  
Lynann Clapham

In 2011, Queen’s Engineering began rollout of its "Engineering Design and Practice Sequence (EDPS)". The EDPS is a "professional spine" sequence of courses over four years, meant to address and incorporate into all of its engineering programs the majority of the 12 Graduate attributes required by the Canadian Engineering Accreditation Board (CEAB). In year 1, the first EDPS course – Engineering Practice I - introduces students to engineering design and problem solving, but with little formal instruction in the design process and engineering tools. Formal instruction in these aspects comes in second year, in Engineering Design and Practice II (course number APSC200). Finally, in third and fourth year, students undertake significant design projects in their discipline. The second-year version of the professional spine, APSC200, is a one-term course taken by all students. This begins with a 6-week Faculty-wide course module, followed by a 6-week program-specific module. In the first Faculty-wide segment, students learn the design process – problem definition and scope, idea generation and broadening tools, decision-making tools, economic analysis, stakeholders, risk, and safety. Students are exposed to the necessity of formal design techniques via a zero-level "P0" project, and taught these techniques during a more extensive P1 project. The second 6 weeks of APSC200 involves a discipline-specific project (P2) in which the student teams practice the skills introduced in the earlier portion of the course while working through a design project chosen to emphasize the skills of their program. This paper focusses on the development and implementation of the P2 project for students in the Queen’s Engineering Physics program. The goal of this project is to introduce discipline-specific tools and techniques, to excite students in their chosen engineering discipline, and to put into practice the formal design techniques introduced earlier. The P2 project developed for Engineering Physics was entitled a "Compact Environmental Monitoring Station". The premise was that the Ontario Ministry of the Environment (MOE) issued an RFP for small, cheap sensor devices that could be provided to every Ontario household, and set up to "crowdsource" environmental data for the MOE. Student teams were required to research and justify which environmental parameters would be appropriate for their monitoring device, decide on parameters to monitor, design the device, and build a working prototype of the device. The device specifications required the use of an Arduino-based platform, interfacing the chosen sensor(s) to a laptop computer using MatLab. Since only some students were familiar with Arduinos and MatLab, two "just in time" workshops were delivered on these topics, using a "flipped lab" approach. For the prototype design and build, students had only 4 weeks and a budget of $100. Arduino boards and some basic sensors were supplied, with students able to source and purchase other components within their budget. The prototype-build provided the students with a valuable hands-on experience and also helped them to fully appreciate unexpected practical design constraints. Given the short timeframe (4-weeks) for the design and build, prototypes were very impressive, with many including solar power or rechargeable batteries, Bluetooth connectivity, 3-D printed packaging, IPhone or Android apps, as well as calibration functions. This paper will summarize the development of this Engineering Physics P2 module, and will report on the first year of offering it in its current format.  


Author(s):  
Daisie Boettner ◽  
Lynn K. Byers ◽  
Bobby G. Crawford ◽  
Gunnar Tamm ◽  
John Rogers ◽  
...  

As a result of recent curriculum revisions, the mechanical engineering faculty at the United States Military Academy teaches the formal design process “just in time” for students to apply the process to their capstone design projects. The design process consists of several phases and incorporates many engineering tools. During the initial offering of the course, Mechanical Engineering Design, instructors assigned students to capstone design teams early in the course. As the instructor taught the design process, team members applied the concepts to their capstone project. Based on instructors’ and students’ feedback, faculty revised the course structure to teach the design process in the context of a simple, in-class design project (design a portable illumination device) during the first half-semester. All in-class exercises were collaborative, hands-on experiences based on the project. To reinforce topics introduced in class and ensure all students develop a firm foundation in the design process, a separate common customer need (a device to store a West Point class ring) was the focus of all individual homework. Each student developed a design, built a prototype, and wrote an individual design report. Subsequent to formal design process instruction, students formed capstone teams and began their one and one-half semester capstone design projects. Results indicate that students more thoroughly understood the design process and its associated engineering tools allowing capstone teams to progress more efficiently through conceptual design; order parts, build prototypes, and test prototypes much earlier than the previous year; and enjoy a successful capstone experience.


Sign in / Sign up

Export Citation Format

Share Document