You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 7, 2021. It is now read-only.
For a lattice design project, i.e., covering the evolution from a:
design concept -> CDR -> PDR -> etc.
given the multitude of lattice files that will be generated during this activity – and exchanged between individuals & groups, i.e., the End Users – a well thought out naming convention at the outset, is as important as e.g. ditto for the parameters for a control system for such a system:
<system> -> <sub-system> -> <sub-sub-system> -> etc.
Hence, for a Straw Man proposal for Functional Specs – i.e., What vs. How/Design Specs – I suggest:
For a lattice design project, i.e., covering the evolution from a:
given the multitude of lattice files that will be generated during this activity – and exchanged between individuals & groups, i.e., the End Users – a well thought out naming convention at the outset, is as important as e.g. ditto for the parameters for a control system for such a system:
Hence, for a Straw Man proposal for Functional Specs – i.e., What vs. How/Design Specs – I suggest:
.
The text was updated successfully, but these errors were encountered: