Example diagram Clause Samples

The "Example diagram" clause provides a visual representation to clarify the structure, process, or relationship described in the agreement. Typically, this clause includes a diagram or schematic that illustrates how certain elements of the contract interact, such as workflow steps, organizational hierarchies, or data flows. By offering a visual aid, the clause helps parties better understand complex provisions, reducing ambiguity and supporting clearer communication.
Example diagram. Figure 14 shows the addition of a mitigation in the diagram. This mitigation addresses the vulnerability concerning input validation. Implementing the mitigation can therefore be expected to reduce the conditional likelihood of the leads-to relation to which the vulnerability is attached, although likelihood values are not shown in the diagram.
View SourceView Similar (2)
Example diagram. Figure 6 shows the start of a CORAS diagram, where assets has been inserted on the right-hand side. Only a single asset is included, although there could have been more. If so, we would insert them above or below the one already there.
View SourceView Similar (2)
Example diagram. Figure 10 shows the addition of threat scenarios in the diagram. Initiates relations have also been added from the threat, as well as leads-to relations from one threat scenario to another. Both relation types are represented by an arrow with an open arrowhead. Notice that the square brackets are meant for likelihood assessments. As we are only concerned with identification of risk model elements and their relations here, these have been left empty.
View SourceView Similar (2)
Example diagram. Figure 9 illustrates the addition of threats on the left-hand side of the diagram. Again, the example includes a single threat, although more could have been added above or below.
View SourceView Similar (2)
Example diagram. Figure 12 shows the addition of incidents in the diagram. In this particular example, there is only a single incident. We have also added an incoming leads-to relation to the incident, as well as an In addition to connecting the incident to the rest of the model, we have also added another vulnerability on the incoming leads-to relation to the incident. This means that all leads-to relations have an attached vulnerability. Although this is not a requirement, it may be a good idea to support the identification of indicators in the next step.
View SourceView Similar (2)
Example diagram. Figure 11 shows the addition of indicators in the diagram. Two indicators have been added. The first is attached to a threat scenario, meaning that it will be used as input for assessing the likelihood of the threat scenario. The other is attached to a vulnerability attached to a leads-to relation, meaning that it will be used as input for assessing the conditional likelihood of the relation.
View SourceView Similar (2)
Example diagram. Figure 9 shows the addition of vulnerabilities in the diagram. In this example, vulnerabilities have only been attached to leads-to relations from threat scenarios, but they could also have been attached to initiates relations from a threat.
View SourceView Similar (2)

Related to Example diagram

  • Product Description The lead products covered by this Settlement Agreement are limited to following Amazon Identification Number (ASIN) B07CYPCHM3, with the description, "60-40 Tin Lead Rosin Core Solder Wire with 2% Flux for Electrical Soldering and DIY, 2 Sizes, Include 0.6mm & 0.8mm, 2pcs (0.6mm&0.8mm Solder Wire)," which was offered for sale by the Settling Entity on ▇▇▇▇▇▇.▇▇▇, hereinafter the “Product” or “Products.”

  • SAMPLE (If applicable and the project has specifications, insert the specifications into this section.)

  • Program Changes Contractor agrees to inform the County of any alteration in program or service delivery at least thirty (30) days prior to the implementation of the change, or as soon as reasonably feasible.

  • Examples (A) The taxpayer has received a statutory notice of deficiency, under I.R.C. §6212, which entitles the taxpayer to seek Tax Court review of a proposed tax deficiency. This is not a delinquent tax because it is not a final tax liability. Should the taxpayer seek Tax Court review, this will not be a final tax liability until the taxpayer has exercised all judicial appeal rights. (B) The IRS has filed a notice of Federal tax lien with respect to an assessed tax liability, and the taxpayer has been issued a notice under I.R.C. §6320 entitling the taxpayer to request a hearing with the IRS Office of Appeals contesting the lien filing, and to further appeal to the Tax Court if the IRS determines to sustain the lien filing. In the course of the hearing, the taxpayer is entitled to contest the underlying tax liability because the taxpayer has had no prior opportunity to contest the liability. This is not a delinquent tax because it is not a final tax liability. Should the taxpayer seek tax court review, this will not be a final tax liability until the taxpayer has exercised all judicial appeal rights. (C) The taxpayer has entered into an installment agreement pursuant to I.R.C. §6159. The taxpayer is making timely payments and is in full compliance with the agreement terms. The taxpayer is not delinquent because the taxpayer is not currently required to make full payment. (D) The taxpayer has filed for bankruptcy protection. The taxpayer is not delinquent because enforced collection action is stayed under 11 U.S.C. §362 (the Bankruptcy Code).

  • Contract Schedule The information set forth in the Contract Schedule is true and correct.