Queensland University of Technology   Brisbane Australia Skip bannerSkip to content A university for the real world - Information Technology Services
QUT Home TILS Home
Staff Directory Contact us
ITS Home About ITS Assistance Services Governance

Systems Development Framework

Governance
Project Management
IT Service Management
Web Governance Linked to another ITS website.
Systems Development
  * When to use this Framework
  Types of development life cycles
  "Not so soft" projects
  SDF Phases
  Project Documentation
  Appendices
  Checklists
Additional resources
Quality Management
- - - - -
Change Management
Continuous Improvement Program
- - - - -
Policies & Standards
Commitees, Groups and Working Parties
Forms
- - - - -

[Print-friendly version]

When should this framework be used

All system development and implementation activities, regardless of whether they are a registered AMP project or not, should follow a systematic planning and development process. Routine support work such as system enhancements or modifications to existing systems and services should also proceed within a controlled process.

The Systems Development Framework provides a guideline to the standard steps inherent in a controlled development process. This does not mean that it should be rigidly followed through all phases for all development activities – this must be an informed judgement. However, appropriate consideration of the process should be a part of all system development work and a conscious decision made as to how the activity should best proceed based on the effort required and the level of complexity.

For many systems development and implementation activities, particularly AMP projects, it will be required to reference the use of the Systems Development Framework within the Quality Management Section of the Project Plan and state the level of adherence to the framework. For particular situations or activities where it may not be suitable, adequate justification or reasoning for not following the framework should be included in the Project Plan as well as a description of what alternative method has been used to ensure an appropriately managed and controlled process.

For the purpose of this document general reference is made to “projects” and the various phases that are carried out however it should not be seen to be restricted solely to formal projects. A range of various activities occur across the University for which this framework may provide guidance. Examples include:

  • Large software development projects
  • Small software enhancements or modifications
  • Package acquisition and implementation
  • General maintenance and support activities for existing systems
  • Upgrades and enhancements to existing systems
  • Server upgrades
  • Web site development
  • Internet tools implementation and support.

All of these activities whether they come under the banner of “projects”, “services” , “systems” or “tasks” can benefit from a well-planned and structured process.