Course Number and Title
M.E. 0304-730 I.S.E 0303-735
Design Project Management
Total Credits = 4
Fifth year standing in an engineering discipline and permission of instructor. Graduate and dual degree students taking this course are expected to complete this course immediately prior to MSD I and MSD II, to meet their graduate capstone requirement. ME students are expected to complete Cornerstone Design and the majority of their co-op requirements prior to enrolling in this course. ISE students are expected to complete the majority of their co-op requirements, and Engineering Management prior to enrolling in this course.
Course Description: This course focuses on preparing students to take on a leadership role in design project teams. Topics include product development processes, management of design project teams, developing a business case for design projects, understanding customer needs and translating them into engineering specifications, tools for developing design concepts, tools for assessing the feasibility of design concepts, conducting engineering tradeoffs and analysis to synthesize a preliminary design. Students use the concepts and tools discussed throughout the course in a team-based environment to develop project readiness packages for subsequent use by senior design teams. Class 4, Credit 4.
Recommended TextProduct Design and Development by Karl T. Ulrich and Steven D. Eppinger, 3rd edition or 4th edition are both acceptable., McGraw-Hill / Irwin Publishers, ISBN 0 07 247146 8
RIT Mechanical Engineering Program Outcomes
MEPO 1. Engage in the mechanical engineering profession.
MEPO 2. Design a system or a component to meet a set of customer specifications and constraints, as well as to define and write the requirements of the design.
MEPO 3. Identify, formulate, and solve mechanical engineering problems.
MEPO 4. Use the techniques, skills, and modern engineering tools necessary for engineering practice; and be able to apply mathematics, science, and engineering principles to mechanical engineering.
MEPO 5. Understand the impact of engineering solutions in a global and societal context, the professional and ethical responsibilities associated with the practice of engineering, and contemporary issues facing mechanical engineers.
MEPO 6. Design and conduct experiments, as well as analyze and interpret data.
MEPO 7. Participate in multi-disciplinary teams.
MEPO 8. Communicate effectively by written, verbal, and graphical means.
MEPO 9. Engage in life-long learning and recognize its importance.
Course Learning Objectives
A student who successfully fulfills the course requirements will have demonstrated the following:
Level 1: Knowledge
DPM 1.1 Learn about various Engineering Design Methods and Processes.
DPM 1.2 Learn about various tools used in engineering design processes.
DPM 1.3 Have a basic understanding of the concepts and tools of engineering design project management.
Level 3: Application
DPM 3.1 Use methods of Needs Assessment to translate customer needs (with measures of effectiveness) into engineering specifications.
DPM 3.2 Use methods of Concept Development to propose a functional architecture for the product Platform or Technology Roadmap.
DPM 3.3 Use the concept of Set Based Concurrent Engineering to develop a technology roadmap for product developmemt.
Level 4: Analysis
DPM 4.1 Conduct an engineering analysis to identify appropriate measures of performance for each engineering specification.
DPM 4.2 Conduct an interface analysis to identify the relationships needed between engineering design teams.
Level 5: Synthesis
DPM 5.1 Use an engineering design process to develop project readiness packages for one or more subsequent senior design teams.
Mapping Course Learning Objectives to Program Outcomes
Each learning objective of the course should support one or more program outcomes for the overall program of study within the department. The table below illustrates how each course learning objectives contributes to each program outcome either 1=slightly, 2=moderately, or 3=significantly.
|Mapping||MEPO 1||MEPO 2||MEPO 3||MEPO 4||MEPO 5||MEPO 6||MEPO 7||MEPO 8||MEPO 9|
PART 0 - Benchmarking and Background Research for each roadmap
- Identify fundamental engineering concepts that are relevant to your project. Includes releveant coursework, governing equations and models, theories, etc. You need to understand the context of your project before you can begin planning for future work.
- Identify benchmarks - Your first benchmark will be past senior design projects related to the technology / application field. Other benchmarks may be internal to RIT or may be commercially available products.
PART I - Customer Needs Assessment for each roadmap
- Identify stakeholder groups - customers, users, sponsors, students, etc. Each stakeholder group should be represented by one or more individual stakeholder representatives. For example "Engineering faculty" may be a stakeholder group, while "Edward Hensel" may be one individual representative of that group.
- Gather raw data from stakeholders - through a combination of interviews, focus group, use cases, contextual observations, etc. as appropriate to the stakeholder group and project family.
- Organize the raw data (focused on WHY the customers need the product/process) using affinity diagrams, and VALIDATE the raw data back with the stakeholders. Typically, you will prepare one affinity diagram per stakeholder group.
- Consolidate the raw data from various stakeholders. Combine the information gained from each stakeholder group into a single comprehensive view of the "market", with a single affinity diagram.
- Interpret the raw data, through creation of an objective tree - to end up with a hierarchical representation of the combined needs of various stakeholders. Again, the objective tree should be validated back with the stakeholders to verify that the team has captured WHAT the customer needs. The team needs to be able to explain to the stakeholders that the objective tree may be a superset of their individual needs, and should explore conflicts between various stakeholder demands.
- Identify and quantify constraints (IP, Ethical, budget, time, codes, standards, etc)
- Prepare a Voice of the Customer for the primary and secondary objective tree level.
- Prepare a revised project mission statement for the roadmap. A good mission should have clearly articulated objectives, resources constraints, and timeline. Validate the mission statement with your stakeholders.
PART II of DPM -- System Architecture Concept for each roadmap
- Identify the critical functions that the product / process must perform. This is focused on WHAT the product / process must do. There should be a fair amount of time spent on system architecture at this point. The goal of the functional analysis is to define the parallel development paths of a project family. In some cases, those paths may be well defined. In others, not yet. Ultimately, each function should results in one or more senior design teams.
- Begin to develop the VOE engineering performance specifications for each function., with units of measure. may or may not set target values during dpm.
- Correlate the VOC to the VOE. Fill in the main house of house 1. Fill in the table mapping common to MSD1. Show that they are basically the same information.
PART III of DPM -- Defining individuals projects within each roadmap
For each function, (At this point, each DPM team member or sub-team will lead one function)
- Begin to discuss tradeoffs between the functions. Identify critical interfaces between functions. show either Roof of HOQ or trade-off matrix.
- define a mission statement for each function
- Conduct a preliminary brainstorming session on means to accomplish each function
- Create a preliminary function-means matrix (HOW vs HOW-TO) or ( HOW vs MEANS)
- Specify which functions must interface with one another (Identify which relationships have to exist between functions, but defer the definition of the interface details to MSD1, 2)
- Propose a timeline for investigation of each function in parallel with one another.
- assemble the parallel (functional) timelines into a roadmap for the family
- prepare a Project Readiness Package for the first trip-segment of the roadmap. Show that the engineering spec and VOC for each individual project are inherited from the parent roadmap -- the individual projects do not stand on their own. The goal is for each roadmap team to produce multiple PRPS, but only one web site. The PRPs will only be word docs. Most information should flow from the roadmap into the PRPs.
The class meets for three two-hour lecture/studio sessions each week. Significant class time is provided for students to collaborate with one another and to meet with faculty members and guides during the quarter.
Contribution of Course to Meeting Professional Component
College Level Mathematics and Basic Sciences = 0 credits
Engineering Topics = 4 credits (1 engineering science, 3 design)
General Education = 0 credits
Prepared By: Edward Hensel Date: September, 2007 Revised: September, 2011 (Elizabeth DeBartolo)