OBJECTIVE

Given the Specifications Document, how does an engineer generate solutions? The process is neither automatic nor unguided. Engineering does not take place in a vacuum. An engineer is assigned or undertakes a project that lies within his/her expertise, resources, time and social domain. The engineering solution should lie within the domain. The task of the engineer is to imagine, draw, adapt, copy, modify, improve and synthesize in order to actualize a solution.

System Study

The purpose of the study is to explore, identify and establish key system concepts.

The system can be decomposed at high levels (The Core Design, Component Systems, Input and Output Peripherals, Housing, Interconnections and Interfaces) and analyzed.

The design of existing systems and state of the art should be studied. Suitable design components that can be adopted legally, easily, and cost effectively to meet the system needs should be noted.

Research (colleges, experts, Internet, books, and journals) should be conducted if necessary.

System Design

Various design possibilities should be generated, considered and evaluated. The decisions made at this stage will shape the overall design a great deal. If the workability of certain concepts are in doubt, more research should be conducted. Again, expert opinion can assist wielding out fringe concepts and in assessing the degree of difficulty in developing certain components. Also, consider the economic and produciability factors of the system design. Research, experience, and expert opinion should help in deciding upon a suitable system design. At the end of this phase the concepts that are to be utilized must be firmly established, and the system design completed.

End Product Visualization Document

After the system design the engineer must have a clear vision as to what product she/he will deliver. Imagine that the product is complete, and it functions according to the concepts that were developed. Then, create drawings, scenarios, and other documents visualizing the product in use and being a success. This process helps in reviewing the objectives and concepts, and motivates the designer.

Refinement of the System Design

Hardware Description

system level design (core design, and component designs)

block diagrams

select the hardware platform

power supply requirements

Software Description

high level flow chart

identify languages

sketch screen shots

Interconnection and interfacing

internal connections

identify other systems with which the system must interact

mock up interfaces

Casing

draw the physical appearance of the system

System Design Documents
The system design documents are the refined hardware and software descriptions, and the interconnection and interfacing and casing designs.

System Design Assessment and Specifications Update

Assess whether the system meets the specifications. Add further details to the specifications. Due to the ill-defined nature of engineering problems it is likely that specifications may need to be altered. Communicate the new specifications to the client and forge an agreement.

The End Product Visualization Document and the Specifications Document together define the Operational Definition of Success for the client, user, and the engineer.

If the specifications cannot be met, or a new agreement cannot be met, then modify the system design or the original specifications.