Status: This project page is a collection of general information, not related to a special project of mine.
This page describes my standard way of creating hardware version numbers. For small projects, things might be handled different, because there is some amount of administrative overhead caused by this procedure. However, for larger electronics projects, this document serves as a reference for me.
Contents
Part numbers
Project code
For a new project, a unique project code consisting of two capital letters XY and entered into the project code listing at PartNumberDesignators.
Parts
For each hardware part to be developed for the project, or elements of a part that may need to be referenced specifically in the project's lifecycle, a part number is assigned. This is constructed as XY-TNN with T being the type designator letter (as given in this Wiki's project part template), and NN a number counting parts of this type in this project.
Revisions
A revision number is added to the part number to uniquely designate a specific version of the part. This is added to the part number as XY-TNN.RR with RR being the revision number. Revision 01 is assigned to the first revision already in development stage. Further revision numbers are incrementally assigned. Assignment of the next revision number takes place once the current revision has been published as stable.
Development, test and release cycle
Design changes after release
If after release of a part revision changes to the design are neccessary, an Engineering Change Order (ECO) is created. An ECO number is assigned to each Engineering Change Order in the format ECO-XY-TNN.RR-MMM, where MMM is the count of ECOs in this project, starting at 1. An ECO registry is kept in the project Wiki for each project that has published ECOs. An ECO template is available in the projects Wiki.
THIS DATA IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS DATA, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
All product and brand names mentioned on there pages and in the source code are registered names and/or trademarks of the respective owner and are mentioned for identification purposes only.
For a full copyright notice, please see this link. For imprint and contact information, please see http://www.thiemo.net/.