Blog · Custom Engineering Notes
Managing Hardware and Software Versions
Version management is unglamorous and it is the difference between a diagnosable field problem and an unfixable one.
Overview
- If you cannot say what firmware is on a unit in the field, you cannot reproduce its behaviour.
- Baseline hardware and software together as a released configuration with a name.
- Keep the ability to roll back; a one-way update is a risk accepted knowingly or not.
- Record what changed at each release in the operator's language, not only in the engineering log.
Related pages
- Scenario CustomizationView
- Platform and Payload CustomizationView
- Production StrengthView
- Intelligent Payloads and AccessoriesView
More in this area
- Writing a Customization Requirements DocumentRead
- Prototype vs Production ConfigurationRead
- Common Interface Issues in Integration ProjectsRead
- Why Payload Power Budget MattersRead
- Why Acceptance Criteria Come FirstRead
- Managing Requirement ChangesRead
- Preparing for Field TestingRead
- Managing Hardware and Software VersionsThis page
- What Makes Up a Custom Project CostRead
- Planning from Pilot to Volume DeliveryRead