Reply To: Application Development and Support Standard


How does this standard relate to the Virtual Classroom standard or any other Standards and SLAs that will involve application administration, acquisition, and/or development?

Is there a size of application and/or level of application exposure that triggers formal adherence to a Development Life Cycle? Are there specific templates or forms required?

I know the standard says that development philosophies are excluded from the scope, but the outlined process indicates a level of linear formality commonly associated with waterfall development rather than agile approaches. that’s not to say that agile methods should not follow the same lifecycle, it’s more a question of what level of formality is expected.

Under Operation and Maintenance, I agree that at least two-weeks’ notice is preferable when outages are involved. However, there should also be a process for handling an Emergency Request for Change. Perhaps Change Management should be referenced.

Disposition or disposal: end user input is always good. How does this provision apply in the case of product end of life or end of support?

Is there a central repository for the minimum artifacts related to the Application Development Lifecycle? Is there an audit process? How will departments be able to proactively tell if their artifacts are meeting the standard?

Under upgrades, large systems are used continuously, which makes this provision unattainable: “Upgrade or refresh hardware and software during breaks in the semester or business cycle, or when anĀ Application is offline so end-users are not negatively impacted.” Change management processes and minimal disruption principles are encouraged in those instances.

An emergency request for change process should apply here, too.