Recommendations about requirement properties Sample Clauses

Recommendations about requirement properties. The focus here is to predict properties of requirements such as priority. For that matter, we will use the information available (i.e., the requirement per se plus the values assigned to its properties) in past and current projects about similar requirements to the one we want to recommend the requirement properties.
Sample 1
AutoNDA by SimpleDocs
Recommendations about requirement properties. The state-of-the-art has lead us to identify several approaches that could be used for this task. One approach is based on matching the requirement at hand (i.e., the requirement for which we want to predict the property) with similar requirements that have already been defined in past or ongoing projects, reducing this task to a similarity and relatedness detection case where approaches presented in points A.3 and A.4 of this section can be used: one based on a hybrid recommender combining collaborative and content-based techniques (possibly improved with similarity NLP techniques, and one based on topic modelling. Alternatively, the recommendation of each requirement property can be seen as a classification task with n classes where machine learning approaches can be used to assign a value to the specific property of a requirement (with a similar approach of that used in (Xxxxxxxxxx 2011)).
Sample 1

Related to Recommendations about requirement properties

  • Developer Operating Requirements (a) Developer must comply with all applicable NYISO tariffs and procedures, as amended from time to time.

  • Initial Forecasts/Trunking Requirements Because Verizon’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom CSTC decides to market its services, Verizon will be largely dependent on CSTC to provide accurate trunk forecasts for both inbound (from Verizon) and outbound (to Verizon) traffic. Verizon will, as an initial matter, provide the same number of trunks to terminate Reciprocal Compensation Traffic to CSTC as CSTC provides to terminate Reciprocal Compensation Traffic to Verizon. At Verizon’s discretion, when CSTC expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, Verizon will provide the number of trunks CSTC suggests; provided, however, that in all cases Verizon’s provision of the forecasted number of trunks to CSTC is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and CSTC’s previous forecasts have proven to be reliable and accurate.

  • EDD Independent Subrecipient Reporting Requirements Effective January 1, 2001, the County of Orange is required to file in accordance with subdivision (a) of Section 6041A of the Internal Revenue Code for services received from a “service provider” to whom the County pays $600 or more or with whom the County enters into a contract for $600 or more within a single calendar year. The purpose of this reporting requirement is to increase child support collection by helping to locate parents who are delinquent in their child support obligations. The term “service provider” is defined in California Unemployment Insurance Code Section 1088.8, Subparagraph B.2 as “an individual who is not an employee of the service recipient for California purposes and who received compensation or executes a contract for services performed for that service recipient within or without the State.” The term is further defined by the California Employment Development Department to refer specifically to independent Subrecipients. An independent Subrecipient is defined as “an individual who is not an employee of the ... government entity for California purposes and who receives compensation or executes a contract for services performed for that ... government entity either in or outside of California.” The reporting requirement does not apply to corporations, general partnerships, limited liability partnerships, and limited liability companies. Additional information on this reporting requirement can be found at the California Employment Development Department web site located at xxxx://xxx.xxx.xx.xxx/Employer_Services.htm

  • Project Requirements Failure to comply with the following requirements will result in a suspension of all other operations:

  • Operating Requirements Any operating and technical requirements that may be applicable due to Regional Transmission Organization, Independent System Operator, control area, or the Connecting Transmission Owner’s requirements, including those set forth in the Small Generator Interconnection Agreement. Operating Requirements shall include Applicable Reliability Standards.

  • Forecasting Requirements 19.5.1 The Parties shall exchange technical descriptions and forecasts of their Interconnection and traffic requirements in sufficient detail necessary to establish the Interconnections necessary for traffic completion to and from all Customers in their respective designated service areas.

  • Training Requirements Grantee shall:

  • Trunk Forecasting Requirements 14.2.1 Initial trunk forecast requirements. At least ninety (90) days before initiating interconnection in a LATA, Alltel shall provide Verizon a two (2)-year traffic forecast that complies with the Verizon Interconnection Trunking Forecast Guide, as revised from time to time. This initial traffic forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Interconnection Trunk groups in the LATA over the next eight (8) quarters.

  • Staffing Requirements Licensee will be in full compliance with the main studio staff requirements as specified by the FCC.

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

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