From use cases to prototype cases Sample Clauses

From use cases to prototype cases. In order to connect possible end results to tangible outcomes which would also be accessible to non-technical audiences, early in the project, the PHENICX consortium defined very concrete use cases which connected the scientific objectives of the different partners to actual end user situations. This gave us a firm grip on the many objectives and enabled us to focus on the end user even before we had tangible results to show. Furthermore, it bundled different objectives defined in the WPs into possible user scenarios. For the next step – the delivering of the first prototype – it was necessary to transform these use cases as defined in Deliverable 2.2 into prototype moments that included different aspects of the existing use cases. In making a planning of what functionality should be available in which demonstrator, several considerations were taken into account:  Maturity of functionality (technology that already is past a ‘preliminary’ phase is most straightforward to implement in a concrete prototype);  Fit of functionality into an intended integrated use context for the prototype (for example, the first M18 prototype presented in this deliverable will most strongly focus on post-(live) concert experiences);  Controversy of functionality following from focus group feedback so far, calling for early concretisation and mock-ups of plans, so potential users can verify their original stances and give early feedback (for example, functionality involving social data and personalisation was deemed controversial). These considerations led to the following overall planning: Use case M18 / 0.6 /D7.1 M21 / v0.8 M23 / v0.9 M24 / v1.0 / D7.2 M25 / v1.1 M29 / v1.2 / D7.3 M34 / v2.0 / D7.4 Digital program notes (uc 1) v1.0 v1.1 v2.0 v3.0 Virtual concert guide (uc 2) v1.0 v1.1 v2.0 v3.0 Overseeing the music (uc 3) v1.0 v1.1 v2.0 v3.0 Focusing attention (uc 4) v1.0 v1.1 v2.0 v3.0 Comparing performances (uc 5) v1.0 v1.1 v2.0 v3.0 Capturing the moment (uc 6) v1.0 v1.1 v2.0 v3.0 Sharing the magic (uc 7) v1.0 v2.0 v3.0 Becoming the maestro (uc 8) v1.0 v1.1 v2.0 v3.0 Ediitorial support (uc 9) v1.0 v2.0 v3.0 As can be seen, besides the planned milestones for deliverable prototypes and the final prototype, 3 extra intermediate releases have been added, giving opportunity for extra tests in real life situations and further possibilities to adapt and react to collected user feedback and connected research outcomes in an agile way.
AutoNDA by SimpleDocs

Related to From use cases to prototype cases

  • Required Procurement Procedures for Obtaining Goods and Services The Grantee shall provide maximum open competition when procuring goods and services related to the grant-assisted project in accordance with Section 287.057, Florida Statutes.

  • Interconnection Facilities Engineering Procurement and Construction Interconnection Facilities, Network Upgrades, and Distribution Upgrades shall be studied, designed, and constructed pursuant to Good Utility Practice. Such studies, design and construction shall be based on the assumed accuracy and completeness of all technical information received by the Participating TO and the CAISO from the Interconnection Customer associated with interconnecting the Large Generating Facility.

  • Technical Standards Applicable to a Wind Generating Plant i. Low Voltage Ride-Through (LVRT) Capability A wind generating plant shall be able to remain online during voltage disturbances up to the time periods and associated voltage levels set forth in the standard below. The LVRT standard provides for a transition period standard and a post-transition period standard.

  • Construction Progress Schedule A schedule indicating proposed activity sequences and durations, milestone dates for receipt and approval of pertinent information, preparation, submittal, and processing of Shop Drawings and Samples, delivery of materials or equipment requiring long-lead time procurement, and proposed date(s) of Material Completion and Occupancy and Final Completion. The schedule will be developed to represent the sixteen or seventeen CSI Specification Divisions. It shall have a minimum number of activities as required to adequately represent to Owner the complete scope of work and define the Project’s critical path and associated activities. If the Project is to be phased, then each individual Phase should be identified from start through completion of the overall Project and should be individually scheduled and described, including any Owner’s occupancy requirements and showing portions of the Project having occupancy priority. The format of the schedule will have dependencies indicated on a monthly grid identifying milestone dates such as construction start, phase construction, structural top out, dry-in, rough-in completion, metal stud and drywall completion, equipment installation, systems operational, Material Completion and Occupancy Date, final inspection dates, Punchlist, and Final Completion date.

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Procurement of Goods and Services (a) If the HSP is subject to the procurement provisions of the BPSAA, the HSP will abide by all directives and guidelines issued by the Management Board of Cabinet that are applicable to the HSP pursuant to the BPSAA.

  • Authorized User Overview and Mini-Bid Process Project Based IT Consulting Services Contracts enable Authorized Users to use a competitive Mini-bid Process to acquire Services on an as-needed basis, for qualified IT Projects. Project Based IT Consulting Services may include, but will not be limited to projects requiring: analysis, data classification, design, development, testing, quality assurance, security and associated training for Information Technology based applications. See section 1.3 Out of Scope Work for a listing of projects expressly excluded from the scope of this Contract. An Authorized User Agreement for Project Based IT Consulting Services will be governed first by the terms and conditions specified in the OGS Centralized Contract and second by terms and conditions added to the Authorized User Statement of Work. Additional terms and conditions shall not conflict with or modify the terms and conditions of the OGS Centralized Contract. NYS Executive Agencies must adhere to all internal processes and approvals including, as required, approval from NYS Office of Information Technology Services. Other Authorized Users must adhere to their own internal processes and approvals. In accordance with Appendix B, section 28, Modification of Contract Terms, an Authorized User may add additional required terms and conditions to this Mini-Bid and resultant Authorized User Agreement only if such terms and conditions (1) are more favorable to the Authorized User and (2) do not conflict with or supersede the OGS Centralized Contract terms and conditions. Examples of additional terms and conditions include: • Expedited delivery timeframe; • Additional incentives, such as discount for expedited payment/Procurement Card use; and • Any additional requirements imposed by the funding source or Federal law.

  • Construction Sequencing In general, the sequence of the proposed dates of Initial Operation of Interconnection Customers seeking interconnection to the Transmission System will determine the sequence of construction of Network Upgrades.

  • Changes to Project Should the Subgrantee wish to make changes to the outcomes, Scope of Work, equipment to be purchased, key personnel, expenditures or deliverables, the Subgrantee must request permission to revise the project. This is done by submitting a Change Request. Changes within a budget category that are more than ten percent (10%) of the award or that move funds from one budget category to another require submission of a Change Request. Approval must be obtained from the Division before the changes are implemented in the project. Approval will be granted for changes that are consistent with the intent of the approved application or prior Change Requests. Changes to the project must be requested using the Change Request in the DOS Grants System at xxxxxxxxx.xxx.

  • Construction Change Directives 7.3.1 A Construction Change Directive is written order prepared by the Architect and signed by the Owner and Architect, directing a change in the Work and stating a proposed basis for adjustment, if any, in the Contract Sum, or Contract Time, or both. The Owner may by Construction Change Directive, without invalidating the Contract, order changes in the Work within the general scope of the Contract consisting of additions, deletions or other revisions, the Contract Sum and Contract Time being adjusting accordingly.

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