Design Process in General

PROBLEM IDENTIFICATION

Problem identification is the first step in the engineering design process. As engineers if we can't effectively identify a problem, how can we expect to solve it. Accurate problem identification entails communicating with the client to be sure that we understand what the client is asking for. Better to spend a few extra hours in this phase, than waste a few days or possibly months in another. Usual forms of problem identification are meetings with clients or surveys and studies. Another common form of problem identification can be from the shortcomings of an existing design.

RESEARCH PHASE

As engineers we have a vast amount of knowledge in our respective fields; yet, there are many specific fields that we do not know about. This is where the research phase comes in. In this phase we can acquire the knowledge that we lack. There are many ways of doing this. The most common method is speaking with an expert. Less direct research methods include studying literature and reviewing previous or similar product documentation.

REQUIREMENTS SPECIFICATION

Imagine a basketball game without hoops; it would just be a bunch of professional athletes running around. Nothing would ever get accomplished without baskets, or more specifically, goals. Engineering is no different and the requirements specification phase is an engineer's chance to set the project goals. To be more specific, this is the part of the design process where the terms of success are determined. Some of the things defined at this time would be an approximate time-line and working budget.

CONCEPT GENERATION

This is the part of the design process where engineers really begin to shine. The point of concept generation is to come up with as many solutions as possible. The only restraints for ideas at this time are the project requirements. Once all the options are on the table, the project team will begin to narrow them down in preparation for the design phase.

DESIGN PHASE

Once the overall concept has been narrowed down to one or two main concepts, the design phase begins. It is here that the details begin to take shape. Packaging and pricing concerns will start to arise as preparation begins for the prototype phase. Blueprints or schematics are drawn and 3D models may be implemented to aid in better visualization of what will actually be built.

PROTOTYPING AND CONSTRUCTION PHASE

This is the time when the hammers and nails come out. Using the models and diagrams created in the design phase, actual devices are built. Typically any product created at this time will be crude representations of the final product. One of the best things about a prototype is that changes can be made without affecting the customer. One difficulty of this phase is that design flaws often make their appearance here. It is not uncommon to have a product completely redesigned after finding serious flaws in a prototype.

SYSTEM INTEGRATION

Once a working design has been constructed, it will move onto the system integration phase. System integration is the phase where a design most closely emulates its ultimate application. For example, a prototype steering wheel may be mounted on a bracket and tested in a lab for the prototyping phase. That same steering wheel would be used on an actual vehicle for the system integration phase. This is so designers can see how the product will interact with other systems.

TESTING

Having been successfully integrated with other system components, the testing phase is reserved for working out the last few issues. Areas addressed at this point are reliability and extreme environment operation. Many companies have huge facilities devoted to this phase of the design process. McConnell Douglas has a gigantic wind-tunnel for testing aircraft design. General Motors has miles of paved and dirt roadways to privately test new vehicles. With facilities like the ones previously mentioned it is not hard to see how important testing is to the design process. It is cheaper to fix a design in the testing phase, than to recall a faulty final product later.

DELIVERY

After a solid and fully functional design completed, the design is delivered to someone else such as another company for manufacturing. Depending on where the product is going, differing levels of documentation will be included with the delivery. If it is going directly to a client, a user manual is almost always included. If the design as a whole is being passed along, schematics and testing data will be delivered.

MAINTENANCE

Although it is the final phase, it is no less important than any other step. The roles associated with this step can vary from one company to another. For a highly complicated or unique product, the actual design team may be responsible for repairs. In other cases they may just be needed for troubleshooting . A common form of maintenance for the computer industry is software updates and device drivers.