Presentation is loading. Please wait.

Presentation is loading. Please wait.

Session 7 Page 11 ECE361 Engineering Practice Brainstorming, Trades, Evaluation, and Conceptual Capture.

Similar presentations


Presentation on theme: "Session 7 Page 11 ECE361 Engineering Practice Brainstorming, Trades, Evaluation, and Conceptual Capture."— Presentation transcript:

1 Session 7 Page 11 ECE361 Engineering Practice Brainstorming, Trades, Evaluation, and Conceptual Capture

2 Session 7 Page 22 Trades and Conceptual Design

3 Session 7 Page 33 Design Process Assures Design will meet Requirements Requirements Specification BrainstormingTrades Preliminary Design Requirements vs. Capabilities Detailed Design Review ImplementationTestingReporting Stage 1 Stage 1 – Problem Definition & Potential Solutions Stage 2 Stage 2 – Design Stage 3 Stage 3 – Verification Deliver = $$$ This process is part of what we call Systems Engineering

4 Session 7 Page 44 Conceptual Design The PDS establishes what the system must do functionally, but the implementation details need to be established The conceptual design process is where this takes place through the Generation of alternative solutions and the Evaluation of alternatives to choose the “best” solution This process leads to …

5 Session 7 Page 55 Preliminary Design Never carry out preliminary design without reference to the PDS and the chosen strategy –Strategy – Your general approach to solving the problem (e.g. win by multiple trips) –Design – the creation to achieve the strategy –Concept of Operation – the specific plan of action for achieving the strategy with your design Outlining the functions allows for design of solutions for those functions –The interaction between the various functions must be considered together with the constraints imposed by those functions –Functions often translate to subsystems

6 Session 7 Page 66 Conceptual Capture Process Identify strategy Document process for each function in PDS –Generate multiple approaches for each function –Evaluate each approach and decide on single approach for each function Capture preliminary design for each solution –Each individual approach should be low-risk –Document each part of the solution carefully –Include sketches, diagrams, code, etc. Complete conceptual capture for total system –Think about integrating individual function solutions Assign functions to team members (prelim)

7 Session 7 Page 77 Conceptual Capture Report Informal report format, focus is on conveying design concepts, not on writing lengthy report –Include brief introduction and summary sections –Try to clearly indicate strategy and main points of concept of operation List all functions performed by system and capture preliminary design for each –Description of function and current best solution, along with list of alternatives –Include sketches and diagrams, neatly hand drawn is fine –Some action view is necessary where appropriate Each team member should prepare their portion of the report, and label it as such

8 Session 7 Page 88 Team Minute How is my team functioning? Ask these questions: –Do I know the names of all of my team members? [ y=2, n=0 ] –When we meet, are all members present and participating? [ y=2, n=0 ] –Do I feel like my ideas are valued in the team discussions? [ y=2, n=0 ] –Do I know my team’s main idea for the design? [ y=2, n=0 ] If your score is below 4, come see me

9 Session 7 Page 99 Team Activity Consider all system functions Generate multiple approaches for each function Evaluate ideas for each function and decide on single approach function Submit minutes of team deliberations Complete conceptual capture for total system Submit as a team report at the next class Capture Preliminary Design!

10 Session 7 Page 1010 ECE 361 Assignments TEAM ASSIGNMENT - Prepare Conceptual Capture Report describing team’s conceptual design Due at end of next class, one per team, hard copy


Download ppt "Session 7 Page 11 ECE361 Engineering Practice Brainstorming, Trades, Evaluation, and Conceptual Capture."

Similar presentations


Ads by Google