What is the difference between revision and version

It is a major release of the software An intermediate software update that typically addresses bugs in the original release but is not seen as a major release of the software Purpose To help modify the original and introduce new features and functionality To fix bugs and issues that were present in the original release Changes Small, minute Bigger Image Courtesy: georgiestclair.

Comments How can you say, in your comparison table for Revision definition: "It is a major release of the software", yet the changes are "Small, minute"? Visa-versa for Version. The entire table makes no sense. Thanks for nicely explaining. Your name. Plain text. This question is for testing whether or not you are a human visitor and to prevent automated spam submissions.

To help modify the original and introduce new features and functionality. The lifecycle schema for parts can contain revision as a property as well as reference to document including document revision. In order to manage differences between part and lifecycle, companies are using interchangeability model. Usually, unique part number is identifying part until both parts can be mixed in the same bin location.

As soon as next design or other change will make a change, new part number will be assigned to the part. It means the functional and physical properties are equivalent in performance, reliability and maintainability.

Based on that, two parts can be used without requiring special procedures such as selecting for fit or performance and without altering the part itself or any other part. In addition to Part Number, lifecycle status can be applied to the part to identify the level of maturity. Typical examples of lifecycle statuses are — pre-release, production, last time buy, obsolete and some others.

Management part lifecycle is completely different document versions and revisions. These are separate processes. The alignment between them can be set by assignment of specific document revision to be related to design of a specific Part Part Number. In case part lifecycle managed by another system e. Create a free Team What is Teams? Collectives on Stack Overflow.

Learn more. Asked 11 years, 4 months ago. Active 2 years ago. Viewed 16k times. Improve this question. Mark Mark 1, 5 5 gold badges 13 13 silver badges 26 26 bronze badges. Add a comment. Active Oldest Votes. Versions are commonly used for computer program files to identify. For example, a version "1. While you have a very good feel for how many releases are represented in going from revision "AA" to "AD", you'd have little idea whether there were a few releases, or several hundred, between versions "1.

The reason that we need an alias is that competing data management processes may create their own variation identifiers. A PLM system can provide a sequential revision "overlay" to the software developer's seemingly-arbitrary, and generally non-sequential, version. And, given the wider role for revisions in the IPC standards, we would propose that you cannot have a version without also specifying an associated revision.

Except in specialized cases, there's little general support for using the term "variation". Iteration describes the unique combination of an item's particular revision at a specific lifecycle phase.

Based on the context, we believe that the more appropriate term would be "variation":. When a repair part within an item is changed so that it is no longer interchangeable with its previous version, it shall be assigned a new PIN. The CAGE Code, drawing format size letter, and drawing revision letter are not considered part of the drawing number.

MIL-HDBKA, interestingly, seems there was no need to actually define the term "revision", though its meaning is presumed by context:.