Claremont Controls

HORNET SOFTWARE Business Resource Management
Quality Registration
ISO 9001:1994 and TickIT logo
In 1995 Claremont Controls Ltd. achieved ISO 9001:1994 registration for the design, development and provision of Hornet Software and associated services. Our quality systems also achieved the necessary standard to be registered under TickIT.

Back one level
ISO 9001:1994

Is the Quality System Standard - a set of requirements for quality assurance in design, development, production, installation and servicing. It identifies the 20 key elements that are the foundation for quality.

Back one level
TickIT

Is designed to improve market confidence in third party quality system certification and makes active use of IS0 9001 for software developers in a rational disciplined approach for any company involved in software development. Case study evidence has shown it to have been effective. An important part of TickIT has been to stimulate software system developers to think about what quality really is in the context of software development.

Back one level
Year 2000 Conformity

All Hornet products were designed to conform to any requirements brought about by the roll over of dates in the year 2000 since their inception in the early 1980's. The British Standards Institute committee BDD/1/-/3 defines conformity as requiring that neither performance not functionality is affected by dates prior to, during and after the year 2000.

The definition details four specific aspects that must be addressed, all of which are included in all Hornet software:

  1. No value for current date will cause any interruption in operation.

    Hornet software does use and check against the current computer system date and applies this for use in date marking reports etc. Users must ensure that their system clocks after 1 Jan 2000 have been re-set correctly where necessary (consult your computer systems documentation). Dates after 1 Jan 2000 will not adversely affect Hornet software.

  2. Date based functionality must behave consistently for dates prior to, during and after the year 2000.

    This is true for all Hornet software.

  3. In all interfaces and data storage, the century in any date must be specified either explicitly or by unambiguous algorithms or inferencing rules.

    Hornet uses a generic inferencing for resolving ambiguous century dates; for example year dates of less than 70 are deemed to be years after the millenium threshold. All projects based date values are stored and processed in Hornet by a method independant of and unaffected by the millenium date change.

  4. Year 2000 must be recognised as a leap year.

    This is true for all Hornet software.

Jump to top of this page