Visual Version History: Difference between revisions
Jump to navigation
Jump to search
(→About) |
(→About) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
AKA visual change log. | AKA visual change log. | ||
A visual version history is the recording of snapshots of a design during the design process, which shows the evolution of a design. It is created by taking screenshots, and embedding small images above a part library corresponding to that design. | A visual version history is the recording of snapshots of a design during the design process, which shows the evolution of a design. It is created by taking screenshots, and embedding small images above a part library corresponding to that design. | ||
'''A visual version history is particularly useful in coordinating large scale open hardware collaboration by allowing for immediate inspection of designs.''' Other value includes that it: | |||
#Provides an immediate assessment of development status, without having to download files | #Provides an immediate assessment of development status, without having to download files | ||
| Line 8: | Line 10: | ||
#Gives insight into design decisions | #Gives insight into design decisions | ||
#Provides insight to the level of completion and overall progress on a design | #Provides insight to the level of completion and overall progress on a design | ||
Insert the newest addition to the visual history at the top so it is readily visible upon first sight. | |||
=Working Doc= | =Working Doc= | ||
| Line 16: | Line 20: | ||
=Links= | =Links= | ||
*This work is derived from [[Incentive Challenge Judging Criteria]] | *This work is derived from [[Incentive Challenge Judging Criteria]] | ||
*[[Annotated_Visual_History]] | |||
Latest revision as of 18:19, 24 June 2021
About
AKA visual change log.
A visual version history is the recording of snapshots of a design during the design process, which shows the evolution of a design. It is created by taking screenshots, and embedding small images above a part library corresponding to that design.
A visual version history is particularly useful in coordinating large scale open hardware collaboration by allowing for immediate inspection of designs. Other value includes that it:
- Provides an immediate assessment of development status, without having to download files
- Shows the order of design, which gives insight into future modification
- Gives insight into design decisions
- Provides insight to the level of completion and overall progress on a design
Insert the newest addition to the visual history at the top so it is readily visible upon first sight.
Working Doc
Links
- This work is derived from Incentive Challenge Judging Criteria
- Annotated_Visual_History