Theme 9: System Navigation Sample Clauses

Theme 9: System Navigation. This refers to general navigation aspects of the system. The test environment for the usability tests was xxxxx://xx0.xxx.xxxx.xx/ Table 19 - Case Study 1 External Testing System Navigation Theme Details Registration All testers reported that finding where to register was unclear and most spent one minute locating it at ‘login’. Suggest adding ‘login/register’ title to this function. Keep it in the same place on the screen. Tabs and breadcrumbs Font is far too small. Think about people with visual disabilities. Dashboard navigation Dashboard features were lauded but finding the dashboard was not intuitive, and most testers found it a bit confusing. What happens when you shut down one of the boxes on dashboard? How can you bring it back? Supply guidance / instructions. Submitting a blog Not clear what happens after blog is submitted. Email depositor to notify events, e.g. when blog submission is live. Export and basket features Very nice and good but location-wise they are too low; they seem like footers and not important information. Promote these features.
AutoNDA by SimpleDocs
Theme 9: System Navigation. This refers to general navigation aspects of the system. Table 25 - Case Study 2 External Testing System Navigation Theme Details Registration The log-in process makes you think you are logged in as a guest. No suggestions made Registration Registration task was not very easy to complete (link is hidden). His experience in computer systems helped him carry out the task assigned. He expects that this task will be much harder for a novel user. No suggestions made Dashboard navigation Sorting, organizing, browsing the information do not facilitate the navigation. No suggestions made Navigation Very easy to navigate. The user especially liked the provision of external links found in a post on the right sidebar. The interface was intuitive. No suggestions made The above section highlighted the issues identified during the test as well as included further suggestions coming from the testers. All of the participants followed the same set of tasks and were given the same questions to answer, which enabled a collation of the results. The overall impression of the testers about the system was positive. Many features of the system were praised by the testers. They were satisfied with the way the content was organised, accuracy of author names and dates, and the availability of citation information. The general view of the system was positive. However, the evaluation has been fruitful in identifying bugs and collecting suggestions for further improvements. All the suggestions were reported in this section and brought to the attention of the development team. Some of the prominent suggestions included various uses of date for changing the presentation order of weblog posts from chronological to reversed chronological and including faceted search by date. Most of the bugs and observations did not suggest a need for a major redesign or changes in the system.
Theme 9: System Navigation. This refers to general navigation aspects of the system. The test environment for the usability tests was xxxx://xx0.xxx.xxxx.xx/ Table 42 - Case Study 4 External Testing System Navigation Theme Details Registration Registration was an easy task. “Register” option could be more visible and distinct. Registration process After the message that the user received an email with a link to verify his account, a link to register appears again. The message gives the impression that you can login immediately. Wrong encoding to the Greek notification letter for the account verification. Register/login url is not https. The message should be clearer that you should see the email in order to proceed. Email text: “about 3 days” is not precise, maybe “about” should be removed. Check if username is the same with the password, inform the user if the password is weak/safe. Tabs Tabs help in navigation: you can see where you are and the adjacent options. Add border-radius to tabs. Bigger tabs and bigger font- size. Tabs Links open in same window. Links (from Files and Export as) to open in a new tab. Tabs Keywords and references usually was zero. If they are zero values, then make the tab inactive. Export As Element not prominent. Could be in a more visible position. It can be in another Tab because “Export” is important in the preservation concept. Maybe move the element above its current position. Fonts Fonts are not easy to read. Available languages text is too small. Green colour of the fonts makes them unreadable in combination with the green background in the top of the page. Bigger font-size in the footer. Maybe a background colour instead of the white background. Tab position Reference links (right sidebar) Do not obscure post content overlap with the content of the post. with the design. Drop down menus Drop-down menu (any field) show more options in case of the Greek language than in English. Add more options in English.
Theme 9: System Navigation. This refers to general navigation aspects of the system. The test environment for the usability tests was xxxxx://xx0.xxx.xxxx.xx/ Table 48 – Case Study 5 & 6 External Testing System Navigation Theme Details Registration Participants are not immediately sure if the “sign up” button is what we mean with “registration process” but other than this there was no problem. One user liked the option not to have to register to use the software. No further suggestions made. Navigation to account The word “dashboard” was not immediately clear to participants, in terms of what we meant. Also not that clicking on the user name brought you to the dashboard. One user was not able to figure out how to add widgets, but in the end he was able to figure it out on his own. Additional Comments: “Funny behaviour, not predictable which widget will jump where”. Supply guidance on dashboard functions and its benefits. Navigation with ‘time slider’ Some participants were unable to use the timeline slider to open a blog post. Either the link (accessed by hovering over the bullet point in the timeline slider) was not “alive”, or the No further suggestions made. participant could not access the actual post through the link that appeared when hovering over the bullet point in the timeline slider. This was true for several other blog pages that we attempted to access. Dashboard navigation User had a few difficulties returning to the dashboard once user began the searches. Supply guidance on how to get to the dashboard/account. Submitting a blog All participants completed this Hints or examples for the extra task successfully, but there information when submitting a was still some confusion in the blog are needed. interface. For example: AS: “What's the difference between referred and not referred? Why do I get to another screen which does nothing else but to ask me to press another button. The Topic List is not very intuitive and does not cover everything. The license type is not intuitive. I think you have to explain, why it's important to have restricted or private access.” The usability tests from August 2013 highlight confusion around navigation, especially in relation to the dashboard and around various back scenarios (back from the search, back to the dashboard). The feedback shows issues with clarifying the benefits of some features (for e. g. why purchase restricted content, what is the license copy for, how to use the dashboard). The searching still seems to be problematic with...

Related to Theme 9: System Navigation

  • Sites 11.1 To enable Digital Origin to fulfill its obligations under any Contract: 11.1.1 the Client shall permit or procure permission for Digital Origin and any other person(s) authorised by Digital Origin to have reasonable access to the Client’s Sites, Equipment and/or Leased Equipment and any other relevant telephone system and other equipment and shall provide such reasonable assistance as Digital Origin requests. 11.1.2 Digital Origin will normally carry out work by appointment and during Normal Working Hours but may request the Client to (and the Client shall) provide access at other times. In the event that the Client cancels, reschedules or misses any pre-arranged appointment, it shall be liable to Digital Origin for any costs and expenses which Digital Origin incurs as a result of such cancellation, rescheduling and/or missed appointment. 11.2 At the Client’s request, Digital Origin may agree (at its sole discretion) to work outside Normal Working Hours and the Client shall pay Digital Origin’s reasonable charges for complying with such a request. 11.3 The Client warrants, represents and undertakes that it has adequate health and safety provisions in place at its Sites. 11.4 The Client shall procure all consents, licences and permissions necessary from landlords or other third parties for the carrying out of preparation work, installation of Equipment and/or Leased Equipment and for the provision, use and operation of the Equipment and/or Leased Equipment and/or Services at the Sites (save to the extent Digital Origin has agreed in writing to do it). 11.5 In the event that the Client is not able to procure the necessary consent to provide the Services within ninety days of the Connection Date Digital Origin will be able to terminate the Contract forthwith by giving the Client written notice without any liability. If the Client has not managed to procure the necessary consents and Digital Origin has commenced work the Client shall, on request by Digital Origin, refund to Digital Origin the cost of all such work (including, without limitation, staff costs and equipment costs) of an amount no less than £500 as Early Termination Charges. 11.6 The Client shall provide Digital Origin with the site and building plans (to include full details of all internal cabling runs) of the Sites and provide Digital Origin with full details of all other services in the vicinity of the proposed works. 11.7 The Client is responsible for making the Site good after any work undertaken by Digital Origin at a Site, including without limitation replacing and re-siting items and for re-decorating. 11.8 If the Client is moving a Site, Digital Origin must be informed as soon as is reasonably practicable so that suitable arrangements can be made to transfer the Client’s Services and Equipment and/or Leased Equipment. Unless otherwise requested, Digital Origin, in addition to moving the Service and Equipment and/or Leased Equipment, will also endeavour (but cannot guarantee that it will be able, for example where the Client moves to a different exchange) to retain the Client’s relevant existing telephone number(s). If Digital Origin can transfer the Client’s existing number(s) to the new Site the existing Contract will continue under the same terms and conditions. If Digital Origin cannot transfer the Client’s existing number(s) to the new Site, installation of a new line will be required at the new Site, or if the Client requires any additional new lines, this will attract new line connection charges and a new Contract. 11.9 If the new installation or moving Site involves the visit of an engineer to facilitate the new installation the Client will be responsible for the costs incurred by Digital Origin for the appointment together with an administration fee in respect of any additional works required to be undertaken by Digital Origin to complete the transfer of the Services and Equipment and/or Leased Equipment. 11.10 If the Client moves Sites and leaves the Equipment and/or Leased Equipment for the new owner/tenant the Client is required to inform them that the Service will be discontinued if Digital Origin is not contacted by the new owner/tenant within 72 hours for the purpose of entering into a new contract with Digital Origin for such services and subject in any event to the agreement of such a contract. 11.11 If at the new Site the Client receives services from an alternative supplier the Client is responsible for any contractual agreement the Client has with them and any liabilities the Client may incur for terminating such agreement.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.

  • Network Maintenance and Management 38.1 The Parties will work cooperatively to implement this Agreement. The Parties will exchange appropriate information (for example, maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the government, escalation processes, etc.) to achieve this desired result. 38.2 Each Party will administer its network to ensure acceptable service levels to all users of its network services. Service levels are generally considered acceptable only when End Users are able to establish connections with little or no delay encountered in the network. Each Party will provide a twenty four (24)-hour contact number for Network Traffic Management issues to the other’s surveillance management center. 38.3 Each Party maintains the right to implement protective network traffic management controls, such as “cancel to”, “call gapping” or seven (7)-digit and ten (10)-digit code gaps, to selectively cancel the completion of traffic over its network, including traffic destined for the other Party’s network, when required to protect the public-switched network from congestion as a result of occurrences such as facility failures, switch congestion or failure or focused overload. Each Party shall immediately notify the other Party of any protective control action planned or executed. 38.4 Where the capability exists, originating or terminating traffic reroutes may be implemented by either Party to temporarily relieve network congestion due to facility failures or abnormal calling patterns. Reroutes shall not be used to circumvent normal trunk servicing. Expansive controls shall be used only when mutually agreed to by the Parties. 38.5 The Parties shall cooperate and share pre-planning information regarding cross-network call-ins expected to generate large or focused temporary increases in call volumes to prevent or mitigate the impact of these events on the public-switched network, including any disruption or loss of service to the other Party’s End Users. Facsimile (FAX) numbers must be exchanged by the Parties to facilitate event notifications for planned mass calling events. 38.6 Neither Party shall use any Interconnection Service provided under this Agreement or any other service related thereto or used in combination therewith in any manner that interferes with or impairs service over any facilities of AT&T-21STATE, its affiliated companies or other connecting telecommunications carriers, prevents any carrier from using its Telecommunications Service, impairs the quality or the privacy of Telecommunications Service to other carriers or to either Party’s End Users, causes hazards to either Party’s personnel or the public, damage to either Party’s or any connecting carrier’s facilities or equipment, including any malfunction of ordering or billing systems or equipment. Upon such occurrence either Party may discontinue or refuse service, but only for so long as the other Party is violating this provision. Upon any such violation, either Party shall provide the other Party notice of the violation at the earliest practicable time. 38.7 AT&T TENNESSEE hereby commits to provide Disaster Recovery to CLEC according to the plan below. 38.7.1 AT&T TENNESSEE Disaster Recovery Plan 38.7.2 In the unlikely event of a disaster occurring that affects AT&T TENNESSEE’s long-term ability to deliver traffic to a CLEC, general procedures have been developed by AT&T TENNESSEE to hasten the recovery process in accordance with the Telecommunications Service Priority (TSP) Program established by the FCC to identify and prioritize telecommunication services that support national security or emergency preparedness (NS/EP) missions. A description of the TSP Program as it may be amended from time to time is available on AT&T TENNESSEE’s Wholesale – Southeast Region Web site. Since each location is different and could be affected by an assortment of potential problems, a detailed recovery plan is impractical. However, in the process of reviewing recovery activities for specific locations, some basic procedures emerge that appear to be common in most cases. 38.7.3 These general procedures should apply to any disaster that affects the delivery of traffic for an extended time period. Each CLEC will be given the same consideration during an outage, and service will be restored as quickly as possible. AT&T TENNESSEE reserves the right to make changes to these procedures as improvements become available or as business conditions dictate. 38.7.4 This plan will cover the basic recovery procedures that would apply to every CLEC.

  • Programming Processor is not responsible for programming or reprogramming of fuel dispensers.

  • Infrastructure Infrastructure serves as the foundation and building blocks of an integrated IT solution. It is the hardware which supports Application Services (C.3.2) and IT Management Services (C.3.3); the software and services which enable that hardware to function; and the hardware, software, and services which allow for secure communication and interoperability between all business and application service components. Infrastructure services facilitate the development and maintenance of critical IT infrastructures required to support Federal government business operations. This section includes the technical framework components that make up integrated IT solutions. One or any combination of these components may be used to deliver IT solutions intended to perform a wide array of functions which allow agencies to deliver services to their customers (or users), whether internal or external, in an efficient and effective manner. Infrastructure includes hardware, software, licensing, technical support, and warranty services from third party sources, as well as technological refreshment and enhancements for that hardware and software. This section is aligned with the FEA/DoDEA Technical Reference Model (TRM) which describes these components using a vocabulary that is common throughout the entire Federal government. A detailed review of the TRM is provided in Section J, Attachment 5. Infrastructure includes complete life cycle support for all hardware, software, and services represented above, including planning, analysis, research and development, design, development, integration and testing, implementation, operations and maintenance, information assurance, and final disposition of these components. The services also include administration and help desk functions necessary to support the IT infrastructure (e.g., desktop support, network administration). Infrastructure components of an integrated IT solution can be categorized as follows:

  • Site Lands or areas indicated in the Contract Documents as being furnished by the Owner upon which the Work is to be performed, including rights-of-way and easements for access thereto, and such other lands furnished by the Owner that are designated for the use of the Contractor. Also referred to as Project Site, Job Site and Premises.

  • Internet Connection Certain Solutions may require an active and stable connection to the Internet in order to function. It is therefore your responsibility to ensure that you have at all times an active and stable Internet connection.

  • Moonlighting Employment as a physician in a professional capacity outside of what is outlined in this Agreement, whether temporary special medical activity (“TSMA”) or external moonlighting, must be approved in writing, in advance, by the Departmental Chair, Program Director and Director of Graduate Medical Education (or designee). Even if approved, professional and general liability insurance as outlined in Section 5.4 is not provided to Trainee engaged in external moonlighting. Trainee acknowledges he or she has the responsibility to obtain insurance for such engagement. TSMA and external moonlighting must be included and reported as part of Trainee's hours spent on clinical experience and education. Trainee shall not be required to engage in any outside work.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!