LMS Use Cases Sample Clauses

LMS Use Cases. Inside the LMS, there are two users: the teachers and the students. The core integration of BEACONING with the LMS is to use the LMS students to play BEACONING games and use the grading they get for assessment. To achieve this, a few conditions need to be met: • The Student needs to be registered in the BEACONING. The registration of a student in the BEACONING ecosystem must be done by a teacher. • The LMS needs a Token to access the Analytics of the student, stored in the BEACONING ecosystem. To get it, the LMS needs to use the BEACONING Token of the current user. • The Student needs to have games available. A teacher needs to deploy games for the student to play. As noted in the points above, the teacher takes a primary role in this simple approach to integrate the LMS. Although he could do all these actions from the BEACONING’s Teacher UI, these should also be available in the LMS. In the next sub-sections, more detail about each user role and use cases will be detailed.
Sample 1
AutoNDA by SimpleDocs

Related to LMS Use Cases

  • Technical Objections to Grievances It is the intent of both Parties of this Agreement that no grievance shall be defeated merely because of a technical error, other than time limitations in processing the grievance through the grievance procedure. To this end, an arbitration board shall have the power to allow all necessary amendments to the grievance and the power to waive formal procedural irregularities in the processing of a grievance, in order to determine the real matter in dispute and to render a decision according to equitable principles and the justice of the case.

  • Required Procurement Procedures for Obtaining Goods and Services The Grantee shall provide maximum open competition when procuring goods and services related to the grant-assisted project in accordance with Section 287.057, Florida Statutes.

  • Technical Objections No grievance shall be defeated merely because of a technical error, other than time limitations in the processing of the grievance through the grievance procedure. To this end, an arbitrator shall have the power to waive formal procedural irregularities in the processing of the grievance in order to determine the real matter in dispute.

  • Procurement of Goods Part A: General Goods shall be procured in accordance with the provisions of Section I of the “Guidelines for Procurement under IBRD Loans and XXX Credits” published by the Bank in January 1995 and revised in January and August 1996, September 1997 and January 1999 (the Guidelines) and the following provisions of Section I of this Schedule. Part B: International Competitive Bidding

  • Technical Objections to Grievance No grievance will be defeated or denied by any minor technical objection.

  • Procurement of Goods and Services (a) If the HSP is subject to the procurement provisions of the BPSAA, the HSP will abide by all directives and guidelines issued by the Management Board of Cabinet that are applicable to the HSP pursuant to the BPSAA.

  • GEOGRAPHIC AREA AND SECTOR SPECIFIC ALLOWANCES, CONDITIONS AND EXCEPTIONS The following allowances and conditions shall apply where relevant: Where the company does work which falls under the following headings, the company agrees to pay and observe the relevant respective conditions and/or exceptions set out below in each case.

  • Business Use Coverage is provided if the BUSINESS USE surcharge has been paid as specified on YOUR DECLARATION PAGE. Eligibility is limited to the following: cars, trucks and vans used for route sales, inspections, maintenance, repair, landscaping, carrying tools to a job site and eligible vehicles owned by religious / charitable organizations.

  • Technical Standards Applicable to a Wind Generating Plant i. Low Voltage Ride-Through (LVRT) Capability A wind generating plant shall be able to remain online during voltage disturbances up to the time periods and associated voltage levels set forth in the standard below. The LVRT standard provides for a transition period standard and a post-transition period standard.

  • Objections to New Subprocessors (a) If Customer has a legitimate reason under Data Protection Law to object to the new Subprocessors’ processing of Personal Data, Customer may terminate the Agreement (limited to the Cloud Service for which the new Subprocessor is intended to be used) on written notice to SAP. Such termination shall take effect at the time determined by the Customer which shall be no later than thirty days from the date of SAP’s notice to Customer informing Customer of the new Subprocessor. If Customer does not terminate within this thirty day period, Customer is deemed to have accepted the new Subprocessor.

Time is Money Join Law Insider Premium to draft better contracts faster.