Non-Functional Requirements

Additional Notes

The Non-Functional Requirements are a living document and will need to be customised and added to by the Project Manager for each procurement.

For projects not being managed by IT Services these are provided as-is, and should be adopted and adapted by the Project Manager running the procurement exercise.

Support in the use, and evaluation of, these requirements is only provided where the project is being run by IT Services.

After each procurement, a lessons learnt should be undertaken to assess their robustness, based on clarifications sought / quality of responses.  The Enterprise Architecture Team should be informed of the recommendations from the lessons learnt, so that these documents can be updated to benefit other users.

Procurement Tips

It is essential that UCD Procurement are informed as early as possible when you are considered undertaking a procurement so there are no unexpected delays or blocks. You should advise UCD Procurement of provisional timelines and indicative solution costs. 

UCD Procurement will typically provide you a recently relevant tender that you use as the basis for tender.

Look to see what over tenderers in this space has recently been published (through both UCD Procurement, and directly yourself through eTenders, and through contacts in other institutions/organisations.