In the world of software development for an operational environment, change is inevitable. How one deals with that change, from a developer’s point of view, can have a monumental effect on acceptance and use of software in an operational environment. In critical software, it’s essential that the change be managed in a way that ensures user buy in. In today’s environment with additional requirements for software security, change to both the development of new software and the modification and change of critical legacy software is inevitable and essential to continued operations and survival.
This talk will deal with 2 distinct ways to roll out software change and the pros and cons of each, with real world examples from the NASA flight critical software experience of the speaker. With a perspective of both the user and developer, this talk is intended to add perspective to the decision making process for both management and the developers that have to deal with those decisions.
0 Comments