Method overview Sample Clauses

Method overview. When describing a past event using the formal model, the event is broken down by looking at individual impacted systems separately, which is seen in Figure 3.4. The three main steps of the method can also be seen in Figure 3.4 and consists of: Step 1 – Identify impacted systems, Step 2 – Describe Dependency Impacts and Step 3 – Describe System Impacts. Steps 2 and 3 are both about characterisation of impacts. The general purpose of the description is to enable the subsequent assessment of general patterns that can be of interest especially for incident management (as this is the context of the CascEff project). The choice of characteristics has been highly influenced by previous research on dependencies and cascading effects (x.x. XxXxxxxxx et al., 2007; Xxxxxxx et al., 2001; Xxxxxx et al., 2009; Xxxxxxxxx and Xxxxxxxx, 2006; Xxxxxx-Xxxxxx and Xxxxxxxxx, 2012); see Chapter 2 for additional details). In addition, the choice of characteristics has also been based on communication with other CascEff partners to get their view on which characteristics that can be of relevance for the project. Each step of the method is described in detail in Sections 3.3.6-3.3.8. Note that steps 1-3 are typically performed using an iterative approach rather than a linear one. This means that when an impacted system has been identified (Step 1) this is followed by describing Dependency and System Impacts for this system before returning to Step 1 and identifying additional impacted systems. 3.3.6 Step 1 Identify impacted systems‌ 3.3.1 for an explanation of why this is done. In order to identify an impacted system, an explicit statement of an effect or a potential effect needs to be made in the written material. One example of a statement referring to an impacted system is that “the loss of power and communications led to missed orders and enquiries [for business and industry]” as was the case in the UK floods in 2007 (Pitt review, 2008). Furthermore, an explicit statement about the existence of a dependency between two systems, but where this dependency has not caused an impact from an originating system to a dependent system, would also be included as an impacted system here. Typically, such dependencies are only mentioned in the written accounts when it was close to having caused an impact, i.e. a “near miss”, but did not due to the presence of some favourable conditions. When having identified an impacted system it is categorised in one of the system categories presented in...
AutoNDA by SimpleDocs
Method overview. Figure 6 depicts the analysis-aided architecture evaluation and design method (hereafter called ADM), which is based on ATAM. The process of moving from requirement scenarios to design decisions is based on the following notions: • Prioritized High-Level Scenarios: A subset of high-level scenario is selected from requirements analysis models. They help to define dependent and independent non-functional parameters. • Analysis Reasoning Frameworks: One framework is defined for each kind of analysis method (e.g., schedulability analysis, performance analysis, reliability analysis). They consist of UML profiles (e.g. XXXXX) and rules to annotate analysis models. Analysis reasoning frameworks also includes rules to make design decisions grouped into analytical advices.

Related to Method overview

  • Method of Billing Consultant may submit invoices to the City for approval on a progress basis, but no more often than two times a month. Said invoice shall be based on the total of all Consultant’s services which have been completed to City’s sole satisfaction. City shall pay Consultant’s invoice within forty-five (45) days from the date City receives said invoice. Each invoice shall describe in detail, the services performed, the date of performance, and the associated time for completion. Any additional services approved and performed pursuant to this Agreement shall be designated as “Additional Services” and shall identify the number of the authorized change order, where applicable, on all invoices.

  • Method of Computation To determine the Adviser’s liability with respect to the Excess Amount, each month the Fund Operating Expenses for the Fund shall be annualized as of the last day of the month. If the annualized Fund Operating Expenses for any month exceeds the Operating Expense Limit of the Fund, the Adviser shall first waive or reduce its investment advisory fee for such month by an amount sufficient to reduce the annualized Fund Operating Expenses to an amount no higher than the Operating Expense Limit. If the amount of the waived or reduced investment advisory fee for any such month is insufficient to pay the Excess Amount, the Adviser shall also remit to the Fund an amount that, together with the waived or reduced investment advisory fee, is sufficient to pay such Excess Amount.

  • Method of Calculation All calculations under this Section 4 shall be made to the nearest one hundredth of a share.

  • Method of Measurement All linear and area measurements under this Agreement are measured on the horizontal plane, unless specified otherwise in an attached Schedule.

  • Program Overview Microsoft extends to eligible partners the opportunity to participate in the Program referenced above subject to these Program Terms & Conditions (“Program Terms”). Each entity participating in the Program is hereinafter referred to as a “Participant.” Participation in the Program is voluntary. The Program is governed by the Program Terms, which incorporate by reference the Microsoft Partner Network Agreement (as in effect between Microsoft and Participant, the “MPN Agreement”). Capitalized terms used but not defined in these Program Terms have the meanings assigned to them in the MPN Agreement. These Program Terms are subject to local requirements and may vary by jurisdiction, and Participant retains sole discretion to set pricing for sales of applicable products.

  • Method of Allocation The Employer must specify in its Adoption Agreement the manner of allocating each annual Employer contribution to this Trust.

  • Method of Service A Notice may be given by: (i) being personally delivered on a Party; (ii) being left at the Party’s current address for service; (iii) being sent to the Party’s current address for service by pre-paid ordinary mail; or (iv) being sent by facsimile transmission to the Party’s current facsimile number for service provided that a copy of the notice is then delivered by one of the means described above.

  • Method of Accounting The Company will use the method of accounting previously determined by the Members for financial reporting and tax purposes.

  • Overview (a) The Employer is committed to maintaining a stable and skilled workforce, recognising its contribution to the operation of the Employer. As such, full time direct and ongoing employment is a guiding principle of this Agreement. (b) The Employer will take all measures to achieve employment security for the direct permanent employees of the Employer. The Parties agree upon the measures in this Clause to protect and enhance the employment security, health and safety, terms and conditions of employment and career development of the employees. (c) The employer agrees that it is highly important to ensure that work is performed effectively, efficiently and without undue pressure or bullying, and in a way that promotes OHS and EO principles and practices in the workplace and appropriate representation of employees should they so request. The employer will ensure that its employment practices are consistent with the above principles and practices.

  • Method of Adjustment Calculation Agent Adjustment; notwithstanding anything in the 2002 Definitions to the contrary, the Calculation Agent may make an adjustment pursuant to Calculation Agent Adjustment to any one or more of the Base Amount, the Forward Price and any other variable relevant to the settlement or payment terms of the Transaction.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!