Soren Sabet Sarvestany

        The following outlines my current design process, developed as a response to my engineering design experiences during my first two years of University.

 

Step 1: Identifying the Opportunity

            I don't believe in problems, I believe in opportunities. My study of psychology and the science of achievement have led me to the conclusion that the mental attitude in which one approaches a challenge largely determine the outcome, regardless of how much technical skill or resources are available to address that challenge. In engineering, this challenge is usually presented to me by others (professors, employers, clients, etc) , and phrased as a design 'problem', but I immediately begin thinking about it as an opportunity. 

 

Step 2: Preliminary Research 

 

          Experience has taught me not to make assumptions about things I know nothing about. My next step, after identifying the opportunity, is to do preliminary research on both the technical and non-technical aspects of the opportunity. This involves interacting with stakeholders and searching for reference designs.

 

Step 3: Identify Key Outcome(s) 

 

         It is important to identify early on what is actually necessary to solve the problem at hand, and to reduce complexity as much as possible. For example, in my robot design course, my team and I were caught up trying to design a robot that could do everything, when in reality all we needed to do was simply get a ball to a gameboard. I believe this philosophy can be carried over to any engineering project. There is usually one key outcome that is necessary, and the sooner that outcome is identified, the smoother the project will go. No time will be wasted on steps that don't bring the project closer to the key outcome. Once that outcome can demonstratebly be achieved, then other features can be added. 

 

Step 4: Functional Decomposition

        Most engineering projects are too complex to solve at once. I like to use functional decomposition to break down the project into manageable parts, working backwards from the key outcome to where I am now. Furthermore, once I have broken down the project, it is easier to prioritize functions and dedicate time and resources appropriately. 

 

Step 5: Conceptual Designs for Each Function

 

          Several conceptual designs are generated for each function. Conceptual designs are ranked with consideration to requirements, metrics, constraints, and criteria, and the simplest and most promising ideas are chosne for the next stage. This is the stage where I first begin prototyping conceptual solutions, to see if they are feasable and if I have the technical knowledge and experience required. 

 

Step 6: Converge to a Preliminary Solution 

 

         The conceptual designs for each function are combined to form the preliminary solution. The first prototype of the design is created, and is tested to see if it performs as required. Notes are taken on design performance. This first solution is modified such that it meets all requirements and constraints.  

 

Step 7: Iterate, Prototype, Test

         Within the available time and resource constraints, the design is improved, prototyped, and tested as much as possible. Testing the solution is the most important step, because that is the only way to be certain that the design will do what it was meant to do. The design is iterated upon with consideration to the criteria presented by the stakeholders. 

 

Step 8: Deliver the Design, Reflect

 

         The final design is built/created and delivered to the relevant party. Once the project is complete, I reflect on the project to identify the lessons I learned, the mistakes I made, and what I would do differently next time.