Graphic User Interface Requirement Clause Samples

Graphic User Interface Requirement. The client and server software for the EDMS will be built using current Microsoft 32 bit development environments. The client PCs in the Registrar of Deeds, UCC, Assessor, Treasurer, and public workstations are required to run either Windows 95 or Windows NT. Workstations that only access the EDMS through ______________________________________________________________________________ Oklahoma County 4-1 EDMS System Technical Proposal - June 16, 1997 the Intranet or Internet can be Windows 3.1 running 16 bit Netscape Web software.
View Source
Graphic User Interface Requirement. The proposed software must be implemented utilizing the County's standard Microsoft Windows environment All operations performed by users will be accessible through an industry standard graphic user interface (GUI). The interface should provide a flexible, menu-driven environment. A detailed description of the proposed system's user interface will be provided, and shall explicitly state how this interface is used to invoke system functions. The County requires the GUI have the same 'look and feel' within all software modules or functional screens provided in the Proposed software. 'Look and feel' refers to the physical arrangement of menu bars and buttons, the grouping of menu commands under each main menu selection, and commonality in the syntax used for identical or similar operations in different software modules (e.g., a menu button for printing is labeled and arranged the same way for print operations in all software modules).
View Source

Related to Graphic User Interface Requirement

  • Interface Requirements 2.4.5.1 The NID shall be equal to or better than all of the requirements for NIDs set forth in the applicable industry standard technical references.

  • Software Requirements 7 Developer shall prepare the Project Schedule using Oracle’s Primavera P6.

  • Program Requirements The parties shall comply with the Disadvantaged Business Enterprise Program requirements established in 49 CFR Part 26.

  • CONTRACT COMPLIANCE REQUIREMENT The HUB requirement on this Contract is 0%. The student engagement requirement of this Contract is 0 hours. The Career Education requirement for this Contract is 0 hours. Failure to achieve these requirements may result in the application of some or all of the sanctions set forth in Administrative Policy 3.10, which is hereby incorporated by reference.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.