Research Context and Main Question Sample Clauses

Research Context and Main Question. The work of this thesis is categorized under the computer science fields of formal verifica- tion and coordination systems. In fact, this thesis introduces a formal verification framework for coordination systems in particular and for component-based systems in general. Let us introduce these fields briefly. A system that consists of a set of independent computing components and a coordinating subsystem is called a component based system. Coordination is defined as the study of the dynamic topologies of interactions among concurrent programs, processes and components of a system, with the goal of finding solutions to the problem of managing these interac- tions [12]. To be more precise about the coordination systems, we need to model or express the coordination strategies using some kind of modeling formalism or language. There exist many coordination models and languages in the literature [120]. In this thesis we concentrate on the coordination language Reo, that is, an exogenous coordination language which can specify coordination of a set of components through networks of channels or compositional connectors built out of primitive ones [13]. The main goal of verification methods is trying to ascertain that an actual system or pro- gram satisfies its requirements. In formal verification one tries to achieve the aim of veri- fication by describing the system using a mathematical model, expressing the requirements as properties of this model and by showing through rigorous mathematical reasoning that the model of the system indeed has the required properties [50, 110]. There are two main methods for formal verification: deductive verification (theorem proving) and model checking. In de-
AutoNDA by SimpleDocs

Related to Research Context and Main Question

  • Research Questions The study addresses the following questions.

  • Research Use The Requester agrees that if access is approved, (1) the PI named in the DAR and (2) those named in the “Senior/Key Person Profile” section of the DAR, including the Information Technology Director and any trainee, employee, or contractor1 working on the proposed research project under the direct oversight of these individuals, shall become Approved Users of the requested dataset(s). Research use will occur solely in connection with the approved research project described in the DAR, which includes a 1-2 paragraph description of the proposed research (i.e., a Research Use Statement). Investigators interested in using Cloud Computing for data storage and analysis must request permission to use Cloud Computing in the DAR and identify the Cloud Service Provider (CSP) or providers and/or Private Cloud System (PCS) that they propose to use. They must also submit a Cloud Computing Use Statement as part of the DAR that describes the type of service and how it will be used to carry out the proposed research as described in the Research Use Statement. If the Approved Users plan to collaborate with investigators outside the Requester, the investigators at each external site must submit an independent DAR using the same project title and Research Use Statement, and if using the cloud, Cloud Computing Use Statement. New uses of these data outside those described in the DAR will require submission of a new DAR; modifications to the research project will require submission of an amendment to this application (e.g., adding or deleting Requester Collaborators from the Requester, adding datasets to an approved project). Access to the requested dataset(s) is granted for a period of one (1) year, with the option to renew access or close-out a project at the end of that year. Submitting Investigator(s), or their collaborators, who provided the data or samples used to generate controlled-access datasets subject to the NIH GDS Policy and who have Institutional Review Board (IRB) approval and who meet any other study specific terms of access, are exempt from the limitation on the scope of the research use as defined in the DAR.

  • JOINT WORK PRODUCT This Agreement is the joint work product of H-GAC and the Contractor. This Agreement has been negotiated by H-GAC and the Contractor and their respective counsel and shall be fairly interpreted in accordance with its terms and, in the event of any ambiguities, no inferences shall be drawn against any party.

  • Joint Inventions For Subject Inventions conceived or first actually reduced to practice under this Agreement that are joint Subject Inventions made by CONTRACTOR and USER, each Party shall have the option to elect and retain title to its undivided rights in such joint Subject Inventions.

  • DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK Firms and/or individuals that assisted in the development or drafting of the specifications, requirements, statements of work, or solicitation documents contained herein are excluded from competing for this solicitation. This shall not be applicable to firms and/or individuals providing responses to a publicly posted Request for Information (RFI) associated with a solicitation.

  • Use of Technology Participants are subject to all existing laws (federal and state) and University regulations and policies on use of technology, including not only those laws and regulations that are specific to computers and networks, but also those that may apply generally to personal conduct such as:  UC Electronic Communications Policy: xxxx://xxxxxx.xxxx.xxx/doc/7000470/ElectronicCommunications  UCLA E-mail Policy and Guidelines: xxxx://xxx.xxxxxxxxxxxxx.xxxx.xxx/app/Default.aspx?&id=455  IT Services Acceptable Use Policy: xxxx://xxx.xxx.xxxx.xxx/policies/aupdetail.html  The UC Policy on Copyright Ownership: xxxx://xxxxxxxxx.xxxxxxxxxxxxxxxxxxxxxx.xxx/resources/copyright-ownership.html  Bruin OnLine Service Level Agreement: xxxx://xxx.xxx.xxxx.xxx/policies/BOL_SLA.pdf Any violation may result in technology related privileges being restricted or revoked and may also result in The University undertaking disciplinary or civil action. If the violation constitutes a criminal offense, appropriate legal action may be taken.

  • AREAS OF COLLABORATION The School will collaborate under Xxxx Innovation Mission to establish, operate and support ATL in India within the school premises with financial support from NITI Aayog.

  • Collaboration We believe joint effort toward common goals achieves trust and produces greater impact for L.A. County’s youngest children and their families.

  • Product Information EPIZYME recognizes that by reason of, inter alia, EISAI’s status as an exclusive licensee in the EISAI Territory under this Agreement, EISAI has an interest in EPIZYME’s retention in confidence of certain information of EPIZYME. Accordingly, until the end of all Royalty Term(s) in the EISAI Territory, EPIZYME shall keep confidential, and not publish or otherwise disclose, and not use for any purpose other than to fulfill EPIZYME’s obligations, or exercise EPIZYME’s rights, hereunder any EPIZYME Know-How Controlled by EPIZYME or EPIZYME Collaboration Know-How, in each case that are primarily applicable to EZH2 or EZH2 Compounds (the “Product Information”), except to the extent (a) the Product Information is in the public domain through no fault of EPIZYME, (b) such disclosure or use is expressly permitted under Section 9.3, or (c) such disclosure or use is otherwise expressly permitted by the terms and conditions of this Agreement. For purposes of Section 9.3, each Party shall be deemed to be both the Disclosing Party and the Receiving Party with respect to Product Information. For clarification, the disclosure by EPIZYME to EISAI of Product Information shall not cause such Product Information to cease to be subject to the provisions of this Section 9.2 with respect to the use and disclosure of such Confidential Information by EPIZYME. In the event this Agreement is terminated pursuant to Article 12, this Section 9.2 shall have no continuing force or effect, but the Product Information, to the extent disclosed by EPIZYME to EISAI hereunder, shall continue to be Confidential Information of EPIZYME, subject to the terms of Sections 9.1 and 9.3 for purposes of the surviving provisions of this Agreement. Each Party shall be responsible for compliance by its Affiliates, and its and its Affiliates’ respective officers, directors, employees and agents, with the provisions of Section 9.1 and this Section 9.2.

  • Notice of Technological Change (a) For the purpose of technological change, the Employer agrees to provide the Union with as much notice as possible, but in any event not less than sixty (60) days notice of a technological change.

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