Not sure, but normally the specific contract and associated Statement of Work (SOW) define the particular requirements for each stage, and they reference the circuit performance requirements for the initial breadboards, then the Design Standards for prototypes and pre-production builds. This may be the user's own requirements in the form of a design document called out on the BOM. Then when you move up to the production builds all of the normal standards are defined on the assembly drawings, and the "exceptions" are defined per the requirements documents, which would take precedence over the industry standards. But I don't think there is any standard that defines the different stages of how any or all products are developed, as that varies too much from company to company and product to product.
So, for example, your initial design contract and statement of work for a garage door opener might have deliverables in the form of a list of circuit performance requirements. It would stipulate that a schematic would be produced that would define an electrical circuit that would open a particular PN garage door control receiver operating on a Bluetooth frequency of xx ghz, with a desired bandwidth, a certain battery voltage, certain levels of reliability for the crystal oscillator, etc. The initial contract produces no hardware, just a design concept and a proposed schematic and BOM and possibly the proposed enclosure drawing, perhaps even an initial board layout.
Once that is approved, a second phase of the contract, or a new contract for working prototypes is approved, and a new P.O. is cut. This would be to build the working prototypes, and the user would specify within that SOW the selection of materials for the PWB, the PWB drawing, the prototype assembly drawings, and reference build requirements such as all soldering must meet IPC-A-610F level 2, what little traceability and configuration controls are needed, etc. And so on and so forth.

But on the other hand, the user may have one design house perform the design and development, then switch to a medium-volume CEM to build prototypes and low-rate initial production. There can be all kinds of variations on a theme here, so I don't think there is any standard that describes guidelines for each stage of development. 
But there might be.
dean

-----Original Message-----
From: Ioan Tempea [mailto:[log in to unmask]] 
Sent: Thursday, April 21, 2016 8:45 AM
To: Stadem, Richard D.; TechNet E-Mail Forum
Subject: RE: MIL/space product nomenclature

Hi Dean,

Requirements, what makes them different from each other, which stages are mandatory for particular types of hardware and which may be waivered, etc.

Thanks,

Ioan Tempea

-----Message d'origine-----
De : Stadem, Richard D. [mailto:[log in to unmask]] Envoyé : Thursday, April 21, 2016 9:42 AM À : TechNet E-Mail Forum; Ioan Tempea Objet : RE: MIL/space product nomenclature

I am not sure just what you are asking. Are you looking for a document that details the requirements for each stage?

-----Original Message-----
From: TechNet [mailto:[log in to unmask]] On Behalf Of Ioan Tempea
Sent: Thursday, April 21, 2016 8:28 AM
To: [log in to unmask]
Subject: [TN] MIL/space product nomenclature

Dear Technos,

Is there a document that explains the particularities of each stage in the manufacturing of MIL/space hardware? I mean Bread Board, QM, DM, EM, Flight, and so on, what do they actually want to say?

Thanks,

Ioan Tempea, P. Eng.
Manufacturing Engineer, Satellite Systems

[cid:[log in to unmask]]

MacDonald, Dettwiler and Associates Corporation, 21025 Trans-Canada Highway, Ste-Anne-de-Bellevue, QC, Canada H9X 3R2
Tel: +1-514-457-2150 x3556
www.mdacorporation.com<http://www.mdacorporation.com/>

This e-mail, and any attachments, are intended solely for the use of the intended recipient(s) and may contain legally privileged, proprietary and/or confidential information. Any use, disclosure, dissemination, distribution or copying of this e-mail and any attachments for any purposes that have not been specifically authorized by the sender is strictly prohibited. If you are not the intended recipient, please immediately notify the sender by reply e-mail and permanently delete all copies and attachments. This email is for informational purposes only and shall not be interpreted to authorize or conclude a binding agreement between MDA and any other party unless this email contains or is accompanied by an express written confirmation of MDA's intention to enter into a binding agreement, such confirmation shall only be provided by an authorized representative of MDA.


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please contact helpdesk at x2960 or [log in to unmask] ______________________________________________________________________

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please contact helpdesk at x2960 or [log in to unmask] 
______________________________________________________________________