Legacy Software

	All members agree to promote and practice good programming standards. Where applicable, all software will be developed using industry standard Best Practice methods.
	Code will be commented, indented and laid out in a logical, readable manner.
	Full source code, with code comments, should be included with all systems and unless otherwise agreed with the Client should be considered as part of the deliverables to the Client.
	If the security backup is lodged with the Consortium, then as a minimum, the full source, complete with code comments, an overview description of the application functionality and configuration together with a set of example or test data and design level access authority to all parts of the supplied systems should be included in the lodged package. Regular updates to the lodged package should be provided to ensure that the security backup copy, and access to it, is maintained at a reasonably current status.
	Where the security backup and support is to be provided by the Client, then a package as defined above for the Consortium should be provided to the Client and the necessary authority provided to agreed members of the Client staff or his representatives
	Irrespective of whether the security backup is maintained by the Client or by the Consortium, the Consortium member responsible for the development and any ongoing support will maintain a security backup package similar to that defined above for the Consortium for the duration of any support contract arranged with the Client and in any event for a minimum time of six months form system handover.
	Members agree not to knowingly compete with other members who already have established a working relationship with the Client concerned but will, where mutually agreeable, be available to support other members with the Clients requirements or otherwise offer assistance as requested by the incumbent member.
	Where the Consortium holds a security backup then in the event of its use being required the Consortium will on request make it available to the original member who developed the system and any other party elected by that developer, or within the terms agreed between the Client and the original developer, to the Client; Where such terms exist then these terms should be lodged with the security backup held by the Consortium.
	Where a member is no longer able to, or no longer wishes to support a Clients application, for example through ill health or retirement, then the Client may call upon the Consortium to arrange for support. The Consortium will use its best endeavours to supply a member to support the Clients needs. Where the Consortium holds a security backup it will be made available to the member to assist with this support. The Client will then be responsible for contracting with and paying the member for any such services.
	Unless otherwise agreed with the Client, all software is to be wholly developed in-house by the member contracted by the Client, or by other members of the Consortium who are experienced personnel. To maintain control over the quality and consistency of the application the software development will not be sub-contracted to third parties (either within the UK or overseas). Similarly, trainees will not be used to develop deliverables.
	Wherever possible, Clients are to be fully involved in the development process. Regular updates are to be sent to them and they should be encouraged to provide feedback and to talk to our designers and programmers.
	Naming of variables, forms, tables, etc. will follow a logical and clear structure. As an example, the Leszynski/Reddick convention may be used such that tables to start with 'tbl', integers to start with 'int' (unless modified by a prefix for Scope or Lifetime). Punctuation marks and spaces are to be prohibited from such names.
	Databases will be designed according to the relational model and will where appropriate be normalised to the Third Normal Form.
	All variables will be explicitly declared. declarations will occur at the top of the relevant procedure.
	All procedures will include error processing and where appropriate error-logging routines.
	The use of Macros should where practical be avoided; all processing will thus be undertaken using the appropriate application code, Transact-SQL code, SQL stored procedures, queries or views.
	All software will be Year 2000 compliant and will be checked for viruses prior to delivery.
	All applications will undergo quality checking and testing by the Developer prior to delivery.
	In the event that any bugs or code errors in the application code caused by the Developer being discovered subsequent to delivery, then they will be corrected free of charge by the Developer during the warrantee period and during any subsequent support contract. The Developer will use his best endeavours to effect such corrections in a prompt and efficient manner.