This document discusses software updates and the importance of minimizing downtime when applying them. It notes that software will need changes over time to fix faults or add features. While the system is unavailable during updates, high availability is important. The document suggests designing systems that can apply updates with little or no downtime by allowing new software versions to run alongside old ones or replacing only specific parts of an application. It also stresses testing compatibility and fault tolerance when planning for updatable systems.

1. Software Update [11]

2. maybe your are sw engineering…

3. designing the architecture

4. there will be faults in the software…
need to change at some point in the future!

5. to add features or treat a fault

6. The system is unavailable while it is being
stopped and restarted to install new
software

7. Availability

8. The system and its applications must not
stop operating, not even to install new sw

9. a system needs before deploying the first
time to minimize the time spent installing
new software

10. how to do it after deploying the first time?
you need to add the capability to make change
capability

11. slightly better situation is that the new
software can overlap with the old version
OLD NEW

12. Sometimes you can replace only specific
parts of an application
: Create as small an update as your tools and what needs to be patched allow

13. Different levels of the system may needing
different capability to support the updates
Application
Firmware

14. new capabilities sometimes means
changed interfaces
: to support interactions with other systems that have not been updated.
: usually means treating the next version’s special attributes
as no-ops and ignoring them

15. Updating a running system…
: usually to initiate the application of the update
: repetitive to the operators

16. You already have FAULT TOLERANT MINDSET
make enough Capability
check your System( firmware / application )
check Compatible

17. Your system must be changed later
So, reduce planned downtime

18. THANK YOU!