A continuous process of technical architecture modernization can help you prepare for any operating system’s inevitable demise.
With the retirement of Windows 10, as described in part 1 of this series, users of the operating system to control test and measurement systems have a choice to make. In part 2, we looked at what steps you can take if you want to continue using Windows 10, and in part 3, we looked steps you plan to upgrade to Windows 11.[1]
One factor that shouldn’t present a major issue is the user interface. According to Noman Hussain, vice president of software and strategic business analysis at Pickering Interfaces, “The transition from Windows 10 to Windows 11 is relatively seamless for experienced users. The core file system remains familiar—for example, the System32 and SysWOW64 folders, as well as Program Files and Program Files (x86) folders, follow the same structure” (Figure 1.)
When asked if operators used to Windows 10 will find difficulty with the switch to Windows 11, Toby Marsden, head of go-to-market strategy and strategic alliances at Keysight Technologies, said, “No, in reality, it is the reverse—that older technology platforms need more specific training; most organizations and users use more modern operating systems. Any specific skills around Windows 10 are dying out.” Added Steve Summers, director and security lead for aerospace and defense at Emerson Test and Measurement, “The user experience is very similar moving to Windows 11. There is a little disruption as operators see the new toolbar for the first time,” but they adjust quickly. And according to Hussain, “From an operator’s perspective…the learning curve is minimal, and day-to-day tasks can be carried out much as before. The main frustration we hear from users is that Windows updates sometimes change the look and placement of icons, which can be disruptive, but is generally a minor inconvenience rather than a training issue.”
Planning for the next operating system
Ultimately, Microsoft will withdraw support for Windows 11, which debuted October 4, 2021, although no end date has been set as of now. (The current version, 25H2, is set to end October 12, 2027, but will presumably be replaced by Windows 11 version 27H2.)
An ongoing effort is the optimal approach for upgrading to any new operating system or other software while planning ahead for any required revalidation process. Marsden described technical architecture modernization as a continuous process to keep systems updated and operating effectively and said that Keysight can help with testing to ensure systems do not regress and continue to perform well. He acknowledged that some customers still rely on legacy technical architectures to run critical business processes, but he added that “most customers are looking for modern, flexible architectures, as legacy systems can result in the business bending to the system’s functionality rather than enabling new operational efficiencies to be achieved.”
According to Summers, “Teams that plan for validation take a professional approach to software design, including building unit tests and other testing routines, so that updates can be validated more quickly.” His company recommends that engineers follow professional software-design processes when developing new systems, but he acknowledged that many existing test systems do not have the necessary tools implemented. Summers added, “Customers who have followed our advice to design code validation as part of their development process are in a good position for these revalidations; those who have not adopted this approach are facing a more manual validation process.” He recommended, “Update your development process now to incorporate best code practices—CI/CD [continuous integration/continuous deployment], unit test, etc. This takes more time up front but makes ongoing re-validation much faster and easier in the future.”
According to Hussain, “We always design with long-term support in mind. Our driver packages cover multiple generations of Windows, and we test them across different OS versions so you can move when you’re ready. My advice is to plan migration early and involve us in that process — it makes the whole thing smoother and saves a lot of headaches down the line.”
When asked about the inevitable end of Windows 11, Keysight’s Marsden said, “Don’t panic!” He advised a thorough evaluation to ensure that that operating-system migration won’t impact key business processes, but he cautioned that failure to address migration will ultimately lead to higher costs and lower business-efficiency gains. “Business continuity needs to be assessed around key workflows, application functionality, and performance,” Marsden noted, adding that any existing system should be thoroughly tested before migrating to a new Windows version.
Said Hussain at Pickering, “Our advice is to plan ahead rather than react at the last moment. Customers should build a migration strategy that considers both short-term needs and long-term continuity, including hardware readiness, software compatibility, and regulatory requirements.” He concluded, “Change is inevitable. Plan for it now to avoid future hiccups.”
Related EE World content
Contending with Windows 10’s retirement: part 3
Contending with Windows 10’s retirement: part 2
Contending with Windows 10’s retirement: part 1
How modularity benefits test systems
What is an instrument driver and why do I need one?
Tech Toolbox: Test & Measurement
Tech Support Challenges and IoT
Designing The Computational Architecture Of The Future
Leave a Reply
You must be logged in to post a comment.