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




Requirement Analysis

User and Client Requirements

A distinction is made between the client (the company, the supervisor, or instructor) and the actual user. The user's wishes and the client's requirements are not necessarily the same. Generally, the engineer is constrained by the client's requirements and she/he strives to meet the user's needs, particularly in terms of safety.

User and client needs were considered during the problem selection. At this stage more details and analysis are sought. Thus, identify, collect, organize, clarify, and prioritize the client and user requirements. What are the methods to establish the client and user requirements?

  • Personal interviews
  • Questionnaires
  • Market research
  • Use case scenarios
  • Analysis of user's requirements of similar products
  • Literature review

    Establish the Level of Design

    From the Request for Design the level at which the solution may lie should become apparent. Neigel Cross illustrates the importance of establishing the level of design by noting the classic problem 'to design a doorknob' (pg77). If the designer designs a door with a doorknob, the client who sells doorknobs would have no use for the door. If the designer finds a solution which does not need a doorknob, the client has no interest at all. If the designer designs "latch mechanisms" and no doorknob, again the client is not served. Thus, determining and agreeing on the level and scope of the design is an important step in the Engineering Method.

    Determine the Performance Requirements
    The information provided by clients and user are usually not in the technical language. Convert the user and client requirements into technical form; be precise as possible.

  • Functional requirements - What is the system supposed to do?
  • Non-functional requirements or Constraints (i.e: use certain     hardware, physical look, human factors )
  • Operational requirements

    As noted before, engineering problems are ill defined. Thus, in order to clarify the user and client requirements the engineer may need to consider particular solutions. However, I defer considering solutions until the next phase-conceptual design.

    Specifications Document

    Review the objectives of the project. State and justify the established level of design. Also, list quantifiable performance requirements which when delivered would deem the product a success.

    A more detailed and more comprehensive technical description (perhaps consisting of block diagrams, flow charts, sketches, graphics, power supplies, housing, interface mock-ups) of what you are going to achieve will be provided after the conceptual design. Further note that the conceptual design phase may take place parallel to requirement analysis.

    The Specification Document is the operational definition of success. Thus, communicate the specifications with the client and reach an agreement.