openreq-live Sample Clauses

openreq-live. 6.2.1.1 Overview Name openreq-live Partner TU Graz Dependencies None Base path / Port 9001 Technology Maven Table 33. Group Decision Engine – MS openreq-live
Sample 1
AutoNDA by SimpleDocs
openreq-live. OpenReq Live is developed following a “minimal viable product” approach where the feedback of the OpenReq partners and other user communities accessed during OpenReq studies is directly considered when prioritizing the functionalities of future releases. The idea of following a “minimal viable product” approach was generated out of discussions with the advisory board in a plenary meeting of OpenReq in December 2017 in Vienna. A major focus of the User Interface (UI) design is to follow a responsive design style [7] which allows the application of OpenReq functionalities also in mobile environments. OpenReq Live is based upon the latest web-technologies and will run on a Spring Boot application including the Thymeleaf as well as the Bootstrap framework. A major goal of “OpenReq Live” is to show OpenReq functionalities in an integrated fashion which goes beyond the application in the individual OpenReq trials. We want to emphasize that the UI elements presented in this deliverable represent a showcase of OpenReq which can serve as a reference design for the trial scenarios that are based on individual UI elements, for example, the Siemens trial UI is based on a Doors integration. Similar as the “minimal viable products” also the designs included in this deliverable will be improved repeatedly depending on the feedback from trial partners, usability studies, and the feedback of OpenReq communities and users engaged in the integration of OpenReq functionalities in the “Open Call”. OpenReq Live will also serve as a basis for different user studies [8] planned in the context of work package 4 (Group Decision Support – see deliverable D4.1 [5]). In OpenReq Live, requirements can be assigned (via drag & drop) to specific releases, which are described by a name as well as the release date (the created releases are sorted by their release dates). Requirements not yet assigned to a specific release are available in a dedicated section “unassigned requirements” on top of the page. The following screenshot (Figure 6) illustrates a planned release #4 of the OpenReq Live which is part of the whole OpenReq Live release plan. Figure 6: Fragment of the Release Plan for the OpenReq prototype. Figure 6 shows all requirements assigned to release “Release #4” which is due to April, 28th 2018. Requirements are described by a name, a descriptive text as well as a status. Further information of requirements is a popularity value of Twitter7 (shown below the Twitter bir
Sample 1

Related to openreq-live

  • 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 CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Destination CSU-Pueblo scholarship This articulation transfer agreement replaces all previous agreements between CCA and CSU-Pueblo in Bachelor of Science in Physics (Secondary Education Emphasis). This agreement will be reviewed annually and revised (if necessary) as mutually agreed.

  • Signaling Link Transport 9.2.1 Signaling Link Transport is a set of two or four dedicated 56 kbps transmission paths between Global Connection-designated Signaling Points of Interconnection that provide appropriate physical diversity.

  • Problem Solving Employees and supervisors are encouraged to attempt to resolve on an informal basis, at the earliest opportunity, a problem that could lead to a grievance. If the matter is not resolved by informal discussion, or a problem-solving meeting does not occur, it may be settled in accordance with the grievance procedure. Unless mutually agreed between the Employer and the Union problem-solving discussions shall not extend the deadlines for filing a grievance. The Union Xxxxxxx or in their absence, the Local Union President, or Area Xxxxxxx, or Chief Xxxxxxx, either with the employee or alone, shall present to the appropriate supervisor a written request for a meeting. If the supervisor agrees to a problem- solving meeting, this meeting shall be held within fourteen (14) calendar days of receipt of the request. The supervisor, employee, Union Xxxxxxx, and up to one (1) other management person shall attempt to resolve the problem through direct and forthright communication. If another member of management is present that person will not be hearing the grievance at Step Two, should it progress to that Step. The employee, the Union Xxxxxxx or in their absence, the Local Union President, or Area Xxxxxxx, or Chief Xxxxxxx, may participate in problem-solving activities on paid time, in accordance with Article 31, Union Rights, Section 1H.

  • Data Storage Where required by applicable law, Student Data shall be stored within the United States. Upon request of the LEA, Provider will provide a list of the locations where Student Data is stored.

  • Dewatering 4.7.1 Where a part of a site is affected by surface water following a period of rain, thus rendering some areas unsafe for productive work, consistent with the Employer’s obligations under the OH&S Act, all non- trades employees shall assist in ‘dewatering’ their own work site or area if it is so affected. Such work to be paid at single time rates. Productive work will continue in areas not so affected.

  • TOOL STORAGE 1. A company shall provide on all construction jobs in towns and cities, and elsewhere where reasonably necessary and practicable (or if requested buy the employee), a suitable and secure waterproof lock-up solely for the purpose of storing employees’ tools, and on multi-storey and major projects the company shall provide, where possible, a suitable lock-up for employees’ tools within a reasonable distance of the work area of large groups of employees.

  • Network Access TENANT may find it necessary to purchase a network interface card, wireless PC card or other hardware in order to connect to the internet service. LANDLORD is not responsible for the purchase of these items and LANDLORD cannot guarantee compatibility with any device TENANT may have. The computer and network card must have software installed that supports the Internet Protocol commonly referred to as TCP/IP. Any conflicts between the software compatibility of the network and the TENANT’S computer operating system or any other feature will be the responsibility of the TENANT to resolve. LANDLORD will not be responsible for software issues related to the user’s personal computer.

  • Web Hosting If Customer submits a Service Order(s) for web hosting services, the following terms shall also apply:

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