OpenReq Interfaces Sample Clauses

OpenReq Interfaces. The following table describes user studies and related data collected for analysis purposes which are used to develop the OpenReq platforms and algorithms and publish corresponding research results. The usage of this data for the purposes of documenting OpenReq results in the OpenReq knowledge base is described thereafter. WP Task Study description Task 6.1 Design OpenReq user interface approach Evaluation of the OpenReq User Interfaces by means of Usability Studies. These studies will be conducted with students at TU Graz, User-Communities of the trial partners and within the scope of questionnaires and prototype evaluations and supported by anonymous communities and micro worker platforms. Resulting Data: Anonymous user feedback on usability questionnaires such as SUS. Task 6.2 Continuous integration No user studies and data collection are planned in this context. Task 6.3 Development of the OpenReq integrated version and API No user studies and data collection are planned in this context. Task 6.4 Integration of OpenReq in issue trackers & collaboration tools No user studies and data collection are planned in this context. Task 6.5 OpenReq cloud platform and services No user studies and data collection are planned in this context. Task 6.6 Integration of OpenReq in requirements tools No user studies and data collection are planned in this context (usability studies are covered in Task 7.3). Task 6.7 Open-Call technical supervision No user studies and data collection are planned in this context. Scientific publications representing outcomes of the mentioned user studies and beyond are stored in the OpenReq knowledge base and are publicly accessible. The accessibility of deliverables (related to WP6) will follow the policy defined in the OpenReq proposal. Technical reports will be publicly accessible except that partners define a different policy (which is the exception of the rule). Source Code will be made publicly accessible always taking into account the policy defined in the OpenReq proposal. Running prototypes hosted in Engineering premises and potentially containing data from knowledge base will not be publicly available. All such data will be hosted only in Engineering data center located in Europe, and will not be accessible from outside, unless otherwise agreed with the consortium. All data stored in the Virtual Machine used to host OpenREQ cloud services will be protected by Engineering corporate firewalls and will be backed up with daily incre...
View SourceView Similar (2)
OpenReq Interfaces. The OpenReq Interfaces will provide open, unified interfaces for easily integrating OpenReq into external tools in form of connectors (see Figure 1). Examples for
View Source

Related to OpenReq Interfaces

  • Interfaces GTE provides the CLECs with choices for access to OSS pre-ordering, ordering, maintenance and repair systems. Availability of the interfaces is fundamental to the CLEC being able to effectively do business with GTE. Additionally, in many instances, CLEC personnel must work with the service personnel of GTE. Measurements in this category assess the availability to the CLECs of systems and personnel at GTE work centers.

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central ▇▇▇▇▇▇ Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • Network Interface Device 2.7.1 The NID is defined as any means of interconnection of the customer’s premises wiring to BellSouth’s distribution plant, such as a cross-connect device used for that purpose. The NID is a single line termination device or that portion of a multiple line termination device required to terminate a single line or circuit at the premises. The NID features two (2) independent ▇▇▇▇▇▇▇▇ or divisions that separate the service provider’s network from the customer’s premises wiring. Each chamber or division contains the appropriate connection points or posts to which the service provider and the customer each make their connections. The NID provides a protective ground connection and is capable of terminating cables such as twisted pair cable. 2.7.2 BellSouth shall permit NewPhone to connect NewPhone’s Loop facilities to the customer’s premises wiring through the BellSouth NID or at any other technically feasible point.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If WCS chooses to subtend a Verizon access Tandem, WCS’s NPA/NXX must be assigned by WCS 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 WCS 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 WCS’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office WCS 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 WCS’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.