...
- Contemporary software ensures longer-term support.
- Contemporary operating system also ensures easier deployment on new hardware.
- Successfully recreating this interrelated system, and properly documenting it, ensures complete understanding of system, enabling correcting problems or improving the system more quickly and with less risk.
2) Clarify "system down" procedures for likely scenarios for current set-up (and
...
later for new system)
- Ensures appropriate response by Testing Center staff and IT support.
- Characterize "pain points" working around different types of failures to help calibrate levels of urgency.
- Examples: What happens if failure persists for 1/2 day? A week? etc.
- Helps us all invest in activities we wished we did before a failure.
- For example, Physics IT has made images of each of the 3 computers. What else might be done?
Approach and considerations
The current system generally works well so serves as a good model, so focus on recreated it.
...
- Tracking work to be done and why, by whom, by when, who reviews/ vets work, etc.
Review what is known
- Includes reviewing what has already been done and what is being done or considered.
Alan, Nick and other Testing Center staff clearly know a lot the most regarding not only the necessary desired results of the system, who how the technical functions of the system meet those objectives, and all related workflows.
Physics IT has made efforts to characterize "what is" from a technical and work-flow perspective:
Testing Center staff and Physics IT staff have done some work, and we continue to try to improve what we have and what can be done: