Coverage in Requirements Modeling Sample Clauses

Coverage in Requirements Modeling. BepiColombo_Models_v5.0 [RD9] is the final Event-B project in the first conducted pilot (see 2.1) and covers approximately 18% of mainly functional requirements. Detailed numbers below are showing the coverage of requirements with respect to their modeling status: • 38 requirements (about 7.79%) have the status “fully modeled”, • 48 requirements (about 9.84%) have the status “partially modeled”, and • 402 requirements (about 82.38%) have the status “ignored”. Even though this is only a small percentage of the original requirements, the resulting models are quite complex. Despite this, our experience suggests that the required modeling efforts are not very alarming. The only really time-consuming activity in the pilot development is proofs - a considerable amount of time is needed for producing a proof, even when it is needed only to reuse an existing proof. Hence our interest has moved during the project from quantitative goals such as requirements coverage to qualitative goals such as better understanding of the Event-B proof methodology. Let us still pay attention to “ignored” requirements. The set of “ignored” requirements is too heterogeneous to have a simple content-based characterization. However, it can be observed that a vast majority of the “ignored” requirements is formed by requirements that do not directly concern telemetry/telecommand handling. The position of telemetry/telecommand handling as an inevitable part of many space software projects partially explains why the modeling effort in first pilot of WP3 has so far almost solely concentrated on requirements that directly concern telemetry/telecommand handling. The emphasis on telemetry/telecommand handling has also the following pragmatic motivation: among the requirements that do not directly concern telemetry/telecommand handling, certain requirements specify somewhat massive collections of data structures to be handled in the instrument ASW modules of the OBSW. Sufficient modeling of the handling of all such structures would almost inevitably take a very long time. There is still no good estimate for how long it would take to create an Event-B project that in some useful way would at least partially model every functional requirement and would also be complete with respect to proofs without strikingly compromising the collection of properties concerned in proofs.
Sample 1
AutoNDA by SimpleDocs

Related to Coverage in Requirements Modeling

  • 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.

  • Margin Requirements 9.1. The Client shall provide and maintain the Initial Margin and/or Hedged Margin in such limits as the Company, at its sole discretion, may determine at any time under the Contract Specifications for each type of CFD.

  • 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.

  • Basic Requirements To be eligible for PayPal’s Seller Protection program, all of the following basic requirements must be met, as well as any applicable additional requirements: • The primary address for your PayPal account must be in the United States. • The item must be a physical, tangible good that can be shipped, except for items subject to the Intangible Goods Additional Requirements. Transactions involving items that you deliver in person in connection with payment made in your physical store, may also be eligible for PayPal’s Seller Protection program so long as the buyer paid for the transaction in person by using a PayPal goods and services QR code. • You must ship the item to the shipping address on the Transaction Details page in your PayPal account for the transaction. If you originally ship the item to the recipient’s shipping address on the Transaction Details page but the item is later redirected to a different address, you will not be eligible for PayPal’s Seller Protection program. We therefore recommend not using a shipping service that is arranged by the buyer, so that you will be able to provide valid proof of shipping and delivery. • The shipping requirement does not apply to eligible transactions involving items that you deliver in person; provided, however, that you agree to provide us with alternative evidence of delivery or such additional documentation or information relating to the transaction that we may request. • You must respond to PayPal’s requests for documentation and other information in a timely manner as requested in our email correspondence with you or in our correspondence with you through the Resolution Center. If you do not respond to PayPal’s request for documentation and other information in the time requested, you may not be eligible for PayPal’s Seller Protection program. • If the sale involves pre-ordered or made-to-order goods, you must ship within the timeframe you specified in the listing. Otherwise, it is recommended that you ship all items within 7 days after receipt of payment. • You provide us with valid proof of shipment or delivery. • The payment must be marked “eligible” or “partially eligible” in the case of Unauthorized Transaction claims, or “eligible” in the case of Item Not Received claims, for PayPal’s Seller Protection program on the Transaction Details page. • In the case of an Unauthorized Transaction claim, you must provide valid proof of shipment or proof of delivery that demonstrates that the item was shipped or provided to the buyer no later than two days after PayPal notified you of the dispute or reversal. For example, if PayPal notifies you of an Unauthorized Transaction claim on September 1, the valid proof of shipment must indicate that the item was shipped to the buyer no later than September 3 to be eligible for PayPal’s Seller Protection program. PayPal determines, in its sole discretion, whether your claim is eligible for PayPal’s Seller Protection program. PayPal will make a decision, in its sole discretion, based on the eligibility requirements, any information or documentation provided during the resolution process, or any other information PayPal deems relevant and appropriate under the circumstances. Item Not Received additional requirements To be eligible for PayPal’s Seller Protection program for a buyer’s Item Not Received claim, you must meet both the basic requirements and the additional requirements listed below: • Where a buyer files a chargeback with the issuer for a card-funded transaction, the payment must be marked “eligible” for PayPal’s Seller Protection on the Transaction Details page. • You must provide proof of delivery as described below.

  • Posting Requirements Seller shall post the Development Security in accordance with the following terms and conditions:

  • Testing Requirements 12.1. Workplaces -

  • 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.

  • W-9 Requirement Alongside a signed copy of this Agreement, Grantee will provide Florida Housing with a properly completed Internal Revenue Service (“IRS”) Form W-9. The purpose of the W-9 form is to document the SS# or FEIN# per the IRS. Note: W-9s submitted for any other entity name other than the Grantee’s will not be accepted.

  • Application Requirements This application shall contain, as a minimum, a sketch showing the location of proposed facilities; a description, sketch, manufacturer’s brochure, etc. of the proposed facilities; and a description of the operation proposed. (11-28-90) 101. -- 199. (RESERVED)‌ 200. OPERATIONAL AGREEMENT.‌‌

  • Accounting Requirements CONTRACTOR shall comply with all applicable COUNTY, State, and Federal accounting laws, rules and regulations. CONTRACTOR shall establish and maintain accounting systems and financial records that accurately account for and reflect all Federal funds received, including all matching funds from the State, COUNTY and any other local or private organizations. CONTRACTOR’s records shall reflect the expenditure and accounting of said funds in accordance with all applicable State laws and procedures for expending and accounting for all funds and receivables, as well as meet the financial management standards in 45 CFR Part 92 and in the Office of Management and Budget 2 CFR Part 200 “Uniform Administrative Requirements, Cost Principles, and Audit Requirements for Federal Awards.”

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