Terminology User requirements Sample Clauses

Terminology User requirements. In PRECIOUS, the user requirements refer to the ways in which the end user may wish to interact with the service and to the system tools that may help them to achieve their behavioural change goals. The precise requirements of each user will depend on the individual; therefore PRECIOUS should allow users to select preferred options where possible. The virtual individual model will also play an important role in delivering a personalised service to the user. The PRECIOUS user requirements are listed in Table 5. In computer science, the terms ‘usage scenario’ and ‘use case’ are often used synonymously, which can cause confusion. In PRECIOUS, the following definitions are used to distinguish between these terms: Scenario-based design is a group of techniques that describe the use of a future system (user requirements) at an early stage of the development process. Rather than detailing the functional system requirements, usage scenarios are stories that describe how individuals will use the system to accomplish particular goals or tasks [6]. Usage scenario ‘story’ format: This section describes the characteristics of the user, for example age/life stage, employment status, marital status, health status, financial position, attitudes towards technology and social influences. This section of the usage scenario provides examples of how the user could optimise their use of the technology on a day-to-day basis to improve their health. For example “Xxxx is gradually gaining weight but finds it difficult to schedule exercise around a busy working day and often eats convenience foods that are low in fibre and high in fat. The technology builds motivation by advising Xxxx that even small changes are beneficial and throughout the day a message system reminds Xxxx to take a break and go for a walk to buy lunch. Using his GPS location the technology is able to recommend nearby vendors and a range of healthy and affordable options”. Examples such as these allow the development team to visualise the use of the technology and design practical solutions. In contrast to a usage scenario, a use case describes sequences of actions that a system or sub-system must perform during its interaction with the external user(s) [7]. The combined application of usage scenarios and use cases has previously been described in the European Commission FP6-funded project MINAml: 4.1: System architecture and design specification), these usage scenarios, and their corresponding user requirements,...
AutoNDA by SimpleDocs

Related to Terminology User requirements

  • Customer Requirements Customer will be required to maintain complex passwords for their User accounts where applicable. For any such passwords LightEdge will provide a secure URL that any User can access to change passwords. All User passwords are set to a ninety (90) day password expiration schedule by default. LightEdge is not responsible for unexpected use of Services whether by ex-employees, compromised User passwords or any other misuse of Customer accounts. Customer shall be responsible for all costs incurred by such unexpected use of Service. Customer shall be fully responsible for providing to LightEdge at Customer’s own expense and in a timely manner the following: - All security for its Services and systems used or accessible in connection with Service; - Cooperative testing of all Customer-provided hardware, software, and Services for compatibility with Service; - Designating an Authorized Contact(s) to be the point of contact to interface with LightEdge Technical Support; - All cabling necessary to support Service; and - Physical and remote management access to any and all Servers onto which Service is installed.

  • Training Requirements Grantee shall: A. Authorize and require staff (including volunteers) to attend training, conferences, and meetings as directed by DSHS; B. Appropriately budget funds in order to meet training requirements in a timely manner, and ensure that staff and volunteers are trained as specified in the training requirements listed at xxxxx://xxx.xxxx.xxxxx.xxx/hivstd/training/ and as otherwise specified by DSHS. Grantee shall document that these training requirements are met; and C. Ensure that staff hired for HIV and syphilis testing are trained to perform blood draws within three (3) months of employment.

  • CONTRACT WORK HOURS AND SAFETY STANDARDS As per the Contract Work Hours and Safety Standards Act (40 U.S.C. 3701-3708), where applicable, all Customer Purchase Orders in excess of ,000 that involve the employment of mechanics or laborers must include a provision for compliance with 40 U.S.C. 3702 and 3704, as supplemented by Department of Labor regulations (29 CFR Part 5). Under 40 U.S.C. 3702 of the Act, each contractor must be required to compute the wages of every mechanic and laborer on the basis of a standard work week of 40 hours. Work in excess of the standard work week is permissible provided that the worker is compensated at a rate of not less than one and a half times the basic rate of pay for all hours worked in excess of 40 hours in the work week. The requirements of 40 U.S.C. 3704 are applicable to construction work and provide that no laborer or mechanic must be required to work in surroundings or under working conditions which are unsanitary, hazardous or dangerous. These requirements do not apply to the purchases of supplies or materials or articles ordinarily available on the open market, or contracts for transportation or transmission of intelligence.

  • Specifications and Standards a) All articles supplied shall strictly conform to the specifications, trademark laid down in the bidding document and wherever articles have been required according to ISI/ ISO/ other applicable specifications/ certifications/ standards, those articles should conform strictly to those specifications/ certifications/ standards. The supply shall be of best quality and description. The decision of the competent authority/ purchase committee whether the articles supplied conforms to the specifications shall be final and binding on the supplier/ selected bidder.

  • Specific Requirements compensation insurance with statutory limits required by South Dakota law. Coverage B-Employer’s Liability coverage of not less than $500,000 each accident, $500,000 disease-policy limit, and $500,000 disease-each employee.

  • Human and Financial Resources to Implement Safeguards Requirements The Borrower shall make available necessary budgetary and human resources to fully implement the EMP and the RP.

  • Regulatory Requirements Each Party’s obligations under this Agreement shall be subject to its receipt of any required approval or certificate from one or more Governmental Authorities in the form and substance satisfactory to the applying Party, or the Party making any required filings with, or providing notice to, such Governmental Authorities, and the expiration of any time period associated therewith. Each Party shall in good faith seek and use its Reasonable Efforts to obtain such other approvals. Nothing in this Agreement shall require Developer to take any action that could result in its inability to obtain, or its loss of, status or exemption under the Federal Power Act or the Public Utility Holding Company Act of 2005 or the Public Utility Regulatory Policies Act of 1978, as amended.

  • Contract Work Hours and Safety Standards Act The following clauses apply to any Federal-aid construction contract in an amount in excess of $100,000 and subject to the overtime provisions of the Contract Work Hours and Safety Standards Act. These clauses shall be inserted in addition to the clauses required by 29 CFR 5.5(a) or 29 CFR 4.6. As used in this paragraph, the terms laborers and mechanics include watchmen and guards.

  • 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.

  • System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.

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