Requirements Traceability Clause Samples

POPULAR SAMPLE Copied 1 times
Requirements Traceability. With the translation of semiformal requirements into a formal modal there is the challenge of traceability between requirements in Problem Frames and their implementation in Event-B. Some of the requirements in Problem Frames might be modelled as invariants, some might be guards of an event or actions. Some of them might not only occur at a specific point (such as an event) but could be spread over a whole model. A requirement in Problem Frames describes how a domain should be influenced under certain conditions by the machine which makes the mentioned possibility of spreaded require- ments in the Event-B model more likely. There is methodogical work to do to solve this problem. However, ordered and structured requirements at different levels of ab- straction in a semiformal notation instead of completely informal require- ments are helpful to achieve traceablity.
View Source
Requirements Traceability. The Contractor shall create and maintain a Requirements Traceability Matrix or equivalent through the end of this contract that shall be comprised of: the requirements from Attachment 4 - Requirements Matrix and documentation of any changes and/or gaps identified during the requirements verification process a cross-reference for each requirement to use cases, design/specification documents and test cases The Contractor shall not proceed with the development of the solution until the Requirements Verification and Fit-Gap Analysis is complete and accepted in writing by the State. A number of applications will be required for the operation of the data repository; some of the functions that they perform may be combined. The Contractor shall be wholly responsible for the design and/or configuration of the application. The Contractor shall create and deliver to the State the design/configuration documentation that includes the following as a minimum: Acquisition: receiving and verifying files transmitted by courts to the acquisition server and returning an acknowledgement of receipt or an error message Validation and cleansing: unpacking (or parsing) data and performing error testing that goes beyond the schema‐based validation that will occur at the court prior to the transmission of the file, and correcting known errors in the information. Transformation, loading, and updating: validated information will be loaded into the repository databases and subset databases in batches, and updates to cases will replace previous submissions Quality control: reports must be run against the repository data periodically to identify potential problems, e.g., old cases that have not been updated for a significant period of time, duplicate or contradictory information about cases, unattached index entries, and inconsistent or invalid codes or other information Archiving: after the end of the fiscal year in which a case was closed, and following a reasonable time period to run end‐of‐year reports, key parts of the case may be moved to an archival database Restoring from archives: on occasion a closed case will be reopened and the court will resubmit it – the archived case must be marked as reactivated or the case must be removed from the archive Expunction: when a defendant’s record is expunged or a case is sealed, identifying data will be obscured to ensure that the information cannot be retrieved, but statistical information will remain for reporting court activity Purging: a...
View Source
Requirements Traceability. ‌ Techniques and tools for linking requirements and formal models to support requirements traceability are a key part of requirements validation. A proto- type Rodin plug-in has been developed for linking structured requirements documents with Event-B models. The plug-in was originally developed by Systerel and continued development is by Düsseldorf and Systerel. The tool is based on the taxonomy approach proposed by Abrial for structuring re- quirements and provides support to manage links between requirements and Event-B models. Some experiences with applying this tool are outlined in Chapter 10. Chapter 9 also outlines an approach to requirements traceabil- ity that is based on the KAOS approach to requirements engineering. The problem frame approach developed by Bosch will play an important role in requirements traceability for their formal development process. A particular issue that is emerging is the need for integrated tool support for managing Problem Frames and links between requirements and models. Linking safety analysis techniques with requirements engineering is im- portant for safety-critical applications. This is especially important for Siemens Transportation Systems. Initial proposals for linking safety analysis with re- quirements validation and Event-B modelling are outlined in Chapter 12.
View Source
Requirements Traceability. All too often, the requirements are used to build the model without establish- ing explicit traceability, even though traceability has become established as a key subject of requirements engineering research [GF94]. Traceability allows us, amongst other things, to verify that the model fulfills the requirements and to verify that not more than what was requested got modelled. It also allows us to perform an impact analysis for change requests and provides a foundation for building variants of a system. Traceability is difficult, as a link across different languages is required: requirements are typically articulated in natural language, while the model typically uses a more formal notation. So far, B models are often inspired by their requirements, rather than derived. [Hal09] shows how one can arrive at good models, even when working with low-quality requirements. Even though the resulting model captures the customer’s wishes, systematic traceability is difficult. In Chapter 9, we present two approaches to more thorough traceability. We try to bring natural language requirements and B models together using various constructs like LTL formulae and UML-B elements. Further, we present an approach for structuring requirements inspired by mathematics.
View Source
Requirements Traceability. System requirements must be traceable to operational and other requirements, where identified by the government.
View Source

Related to Requirements Traceability

  • Traceability 11.1 Under the terms of this Agreement, Supplier shall have and operate a process to ensure that all Products, sub-assemblies and the components contained therein supplied to the Buyer are completely Traceable back to manufacturer by batch or lot or date code. 11.2 Further Supplier hereby agrees, unless directed otherwise by the Buyer, to procure components through franchised distributors or direct component Suppliers. Supplier agrees to indemnify and hold the Buyer harmless from and against all costs and expenses for the removal, repair or replacement and reinstallation of counterfeit components incorporated into a Product sold by Supplier to the Buyer where the counterfeit component was procured by Supplier from a person or entity other than a franchised distributor or direct component Supplier or other person or entity pre-approved by the Buyer in writing.

  • System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.

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

  • Specific Requirements compensation insurance with statutory limits required by South Dakota law. Coverage B-Employer’s Liability coverage of not less than $500,000 each accident, $500,000 disease-policy limit, and $500,000 disease-each employee.

  • Match Requirements There is no match required on the part of the Grantee under this Agreement.