Iterations. 2.2 Prior to the start of each Iteration, the Parties shall agree an Iteration Backlog which shall include:
Iterations. The iterative process described in the preceding paragraph may be repeated up to three (3) times for any given deficiency and/or requested modification. If, after three iterations, the parties cannot agree upon the modifications to the relevant deliverables, then either party may immediately terminate any affected SOW.
Iterations. The iterative process described in the preceding paragraph may be repeated up to three
Iterations. The development of the Deliverables shall take place in Iterations, cf. clause 5.2 of the Contract: An Iteration shall typically include the following phases, cf. clause 4.3 of Appendix 1: Analysis and design Development Execution of Agile Demonstrations Evaluation and planning of the next Iteration Advising the Customer In accordance with clause 3.2.4 of the Contract, the Supplier shall regularly advise the Customer on how best to ensure the suitability of the Deliverables in relation to the Customer's Business Objectives and Needs. The Supplier's advice shall thus ensure that the Project continuously results in deliverables with a business value for the Customer. In this context, the Supplier shall primarily advise the Customer on: The Agile Method applied. The Customer's description of the requirements in the Prioritised Requirements List, including their classification as Mandatory and Other Requirements. The Customer's prioritisation of Requirements, also in the individual Iteration, including the possible consequences and risks associated with the Customer's prioritisation. Issues of relevance to the combination of Mandatory and Other Requirements in the Prioritised Requirements List, including correlations and any Dependencies between the individual requirements. The Customer's prioritisation of requirements and activities in the individual Iterations as well as participation in the planning thereof. The combination of Mandatory and Other Requirements in the individual Iterations. The consequences and risks associated with the Customer's choices, including in relation to the fulfilment of the Customer's Business Objectives and Needs in subsequent Iterations and in relation to the Customer's license agreements, cf. Appendix 16. Matching of expectations with the Customer with respect to the Customer's expected time for submission of regular feedback and clarifications in the individual Iterations. Determination of acceptance criteria. Configuration of IT environment, cf. clause 4 of the Contract. New technologies or solutions which may affect the way in which the Customer's needs are met. Any changes to the requirements for the Customer's IT environment, if such changes should be necessary during the Project. [The list of issues requiring advice to the Customer may usefully be supplemented and adjusted as required for the individual Project. The above issues should be included at least.] Where the Supplier assists the Customer in relation to e.g. (i) ...
Iterations. We describe the subroutine ΠAA-it, which is executed in each iteration of our 𝐷-AA protocol. M − M M − M M − Honest parties first distribute their values via ΠoBC, similarly to [20]. To ensure validity, the parties discard the outliers out of the values received. In the pure asynchronous unidimensional setting (where 𝑡𝑠 = 𝑡𝑎 = 𝑡), discarding the lowest 𝑡 and the highest 𝑡 values received in each iteration is enough [1, 4, 13]: there is at least one value remaining, and any corrupted value remaining is in the range of honest values. Then, the parties compute the new values by taking the average between the lowest and the highest values remaining. The multidimensional case generalizes this approach: if a party obtains a set of value-sender pairs of size at least 𝑛 𝑡 via ΠoBC in some iteration, then at least 𝑡 of the values in are honest. Hence, one can obtain a safe area by computing the convex hull of each subset of 𝑡 values, and then by intersecting these convex hulls, as shown in Figure 2. This intersection is guaranteed to be included in the convex hull of the honest values in . We formally define the safe area [26] below.
Iterations. 1. GVMS HAS CONFIRMED THAT IT HAS TESTED THE SOFTWARE AND HAS NO COMMERCIAL SUBSCRIPTION PAYING CUSTOMERS USING THE SERVICES. 2. THE REVENUE MODEL FOR GVMS IS FRANCHISE FEE AND THE CUSTOMER SUBSCRIPTIONS AND THE CASH FLOW IS EXPECTED OVER MEDIUM TERM FROM ITS REVENUE. 3. SOLUTIONNET WILL PROVIDE THE TECHNICAL SUPPORT FOR THE PERIOD OF 1 YEAR AS PART OF THE CONTRACT.
