2
\$\begingroup\$

This question is not directly about design but meaning of a concept used in electronics design. Basically, I cannot find the clear explanation regarding the following use of "specification" and "drafting":

What is meant by "hardware specification" and "drafting hardware specification". Is this something done before circuit/hardware design of after design? Could you give concrete example which can clearly show what these mean?

\$\endgroup\$
1
  • \$\begingroup\$ "Drafting" by itself can also mean the process or department that a hardware design is handed off to to be laid out and routed, in order to generate the various artifacts needed to fabricate a printed wiring board (PWB) and build the PCB. \$\endgroup\$
    – SteveSh
    Nov 7 '20 at 1:44
2
\$\begingroup\$

A specification -- for any technical device or part thereof -- is a document that describes what it does do, or what it should do.

Note that in some situations a specification for a part will be called a "requirements document". They're not exact synonyms: if it's built and you're selling it, you'll almost never call the document that describes it the "requirements", while if you're in a really formal process where the whole document gets written first and then design starts, it'll most likely be called "requirements". But within those extremes, there's a lot of overlap.

Depending on the design process used, the specifications may be written before the board is designed (i.e., the "pure" waterfall model), or the specification may be written as the board is designed (i.e., the "spiral" model, aka "agile"), or they may be written only after everything has been made to work and someone wants to sell it (i.e. the "make sure your resume is current" model).

Even in pure waterfall models, the board won't exactly match the specification -- when you're designing a board to specification you generally try to exceed specification in every way, so that when you fall short of your own self-imposed mark you still exceed the customer's required specification.

Specifications can be formal, informal, loose or tight. In general, a specification specifies all the important parameters of the part. For a circuit board these may include:

  1. What the board actually does (this is a good one to include).
  2. The physical envelope ("space claim") that the board fills, and perhaps cannot grow beyond.
  3. It's weight
  4. The mounting features of the board
  5. The connectors on the board, and possibly their locations
  6. The power supplies needed by the board, and usually the current draw from each
  7. The expected inputs and desired outputs.
  8. Aspects of the environment in which it is expected to work, and survive (i.e., temperature, humidity, vibration levels, shock, vacuum if it's a space application, radiation, etc.)
  9. Electromagnetic compatibility specifications, both susceptibility and what it can or cannot generate.
  10. Etc.

"Drafting" is just another word for composing a document, usually leaning toward the initial phases, and possibly the work you need to do to make sure all the details are correct. So if you're "drafting a specification" you're running around making sure that you're asking for something that's both possible and that will make you happy when you're getting it.

Depending on whether the document is going to be internal or part of a contract, you may be trying to dot every 'i' and cross every 't', or you may just jot something down on a napkin -- but usually if you're "drafting" it, you'll be writing it as if it really matters that it be adhered to, and depended upon.

\$\endgroup\$
5
  • \$\begingroup\$ Sorry I try to make it clear for myself. So if a designer designs a circuit board and gives it to another person who is responsible for "drafting hardware specification", will he need to draw the board in CAD and write a document about the details of the board? I am confused whether this "drafting hardware specification" done after the design or before? \$\endgroup\$
    – pnatk
    Nov 7 '20 at 0:17
  • \$\begingroup\$ I edited. Boards are expensive enough to design that you should go into it with some sort of specification stated, even if it's a prototype effort, and even if you are the only "customer". It keeps you from doing stupid things like making a board that's 1/8" bigger than will fit in that nice pretty case that you bought, or that lasts for ten minutes on the batteries you planned on using. \$\endgroup\$
    – TimWescott
    Nov 7 '20 at 0:25
  • 1
    \$\begingroup\$ But that doesn't mean that board designs are always launched with well-enough articulated specifications -- it just means that on a well run project, specifications, however informal, are known and understood ahead if time. \$\endgroup\$
    – TimWescott
    Nov 7 '20 at 0:26
  • 1
    \$\begingroup\$ As used in this context, a "requirements document" is the same as a "specification (document)". My industry tends to use the requirements vernacular. \$\endgroup\$
    – SteveSh
    Nov 7 '20 at 1:46
  • \$\begingroup\$ @SteveSh: I like that comment enough I'm going to add it to my answer. Thanks! \$\endgroup\$
    – TimWescott
    Nov 7 '20 at 17:36

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.