Engineering Method

Introduction
Characteristics of the Engineering Method
Project Approach

The Method

Problem Selection
Preliminary Ideas
Refinment and Selection
Feasibility Study
Request for Design
Requirement Analysis
User and Client Requirements
Establish the Level of Design
Determine the Performance Requirements
Specifications Document
Conceptual Design
System Study
System Design
End Product Visualization Document
Refinment of the System Design
System Design Documents
Assessment and Specification Update
Detailed Design
Design Development
Detailed Design Documents
Design Assessment
FREEZE the Design
Implementation
Troubleshooting
Testing and Evaluation
Design and Implementation Testing
Operational Testing
Testing and Evaluation Results
Documentation
The Product Report

References
© Natkeeran Ledchumikanthan




Problem Selection

For an employee engineer the problem selection involves the identification of a need relevant to the company. Most likely she/he will be assigned a project. For a student or a hobbyist the problem selection is a more open phase. She/he would have to identify a worthy need or interest.

Preliminary Ideas

Students, hobbyists, professionals, and companies hunt for good ideas. Hunting for and evaluating ideas is a talent. Initially, the ideas are explored in breadth. Intuition, experience, and expert opinion are the guides in the exploration. During this phase, try not to be too judgmental or being too out in the fringe. The result of this phase may include a list of possible project ideas, sketches of product ideas, and collected project articles. The following are sources for project ideas.

  • Magazines
  • Internet Sites (Think Cycle, TEEDOR)
  • Technology Forecast Lists (GW Forcasts, BT List)
  • Patents: (identify an area where cluster of activity is taking place     and select a project from that area)
  • Patents: (select a project that is "not quite technically or     commercially successful" and correct by invention)
  • Brainstorming
  • Consultants
  • Own Ideas (How can I improve a situation? Would that not be     neat to do?)

    Refinement and Evaluation

    Not all ideas are worth pursuing. Ideas need to be considered in the particular engineering context.

    Consider the available resources, time, and expertise.
    Consider "needs", interests, or market demands.
    Consult with potential users and clients if possible.
    Consider your personal requirements and motivations.
    Consult with experts if possible.
    Research on vague ideas.

    After careful consideration narrow down the project domain to three to five projects. Then, prioritize the project selections. Select the most promising project. When selecting the project explicitly state the reasons: "needs", commerce or amusement. Also, select a project that is challenging and manageable. Select a project that is practical, within the range of your knowledge, experience, and resources.

    Feasibility Study

    Assessment of Need and Interests:
    The product must have a need, market demand, or interests that will provide an acceptable net benefit for the costs employed to engineer the product. To assess the need and market demand, personally interview potential clients and users, conduct market research if possible, seek expert opinion and use your personal experience; then decide.

    If the project lacks sufficient demand or resources, or if the designer is not motivated, then the project needs to be modified or abandoned.

    Survey Existing Systems and State of the Art:
    Usually, there will exist products similar to the product that you select to engineer. Research and study the existing systems and the state of the art systems similar to the one that you are proposing. The challenge is to out compete, offer an alternative product, or find a niche market for your product thorough engineering. Use your experience and consult expert opinion to decide whether you can engineer to create a superior or niche or unique product. If not modify or abandon the project now.

    Preliminary technical feasibility:
    Is the product producible?
    There are obvious impossible ideas or projects such as perpetual machines and automobiles from scratch.

    Decision
    If feasibility study indicates that product in its entire scope is technically feasible, has a market demand, and if you assess that you can deliver within budget and on time, then write the Request for Design. . Otherwise modify the project and reevaluate it, select another project, or start all over again.

    Request for Design

    In the Request for Design define the product that you are proposing to design. Illustrate the need, market demand, or the interest for the product. Detail the objectives of the project. Illustrate how you are suited to design the product. Also, note the risks involved in undertaking the project.

    If your supervisor rejects the Request for Design, then you will have to modify the project, select another project, or start all over again.

    At the end of the Problem Selection phase you must have a product idea that has a demand, doable, and that you are excited about.