Scenario Refinement Sample Clauses

Scenario Refinement. The purpose of a scenario is to facilitate agreement between eDIANA architects and developers with stakeholders. Scenarios are refined from high level scenarios representing generic interactions between users or other system actors with the eDIANA platform. High level scenarios must start by identifying initiating actors and by defining the basic sequence of interaction with the eDIANA platform. Scenarios must be created properly from early phases. Hence, actor identification and interaction storyboards must be as complete as possible. It must be noted that an actor is someone or something that interacts with the system. This means that in addition to users, administrators, etc. external systems providing or requiring information from the eDIANA platform must be identified as actors. On the other hand, to properly identify useful scenarios, the following questions should be answered: • What functionality does each actor expect from the eDIANA platform? • Do the actors need to be informed about the events occurring in the systems? • What information the actors need to supply/receive to/from the system? When refining scenarios, it is useful to split the interactions with the system in logical sequences of events. This may allow assigning detailed scenarios to specific parts of the eDIANA platform or to specific components. In the same way, optional or conditional paths within a sequence of events can be divided into separated detailed scenarios. In general the criteria should be to assign detailed scenarios coming from task T2.5 to other task of the eDIANA project dealing with concrete eDIANA aspects.
Sample 1
AutoNDA by SimpleDocs

Related to Scenario Refinement

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Fabrication Making up data or results and recording or reporting them.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Generating Facility The Interconnection Customer’s device for the production of electricity identified in the Interconnection Request, but shall not include the Interconnection Customer’s Interconnection Facilities.

  • Compaction 11.1 Concrete shall be thoroughly compacted and fully worked around the reinforcement, around embedded fixtures and into corners of the formwork. 11.2 Concrete shall be compacted using mechanical vibrators complying with IS 2505, IS 2506, IS 2514 and IS:4656. Over vibration and under vibration of concrete are harm full and shall be avoided. Vibration of very wet mixes shall also be avoided. Whenever vibration has to be applied externally, the design of formwork and the disposition of vibrators shall receive special consideration to ensure efficient compaction and to avoid surface blemishes.

  • Storage The ordering agency is responsible for storage if the contractor delivers within the time required and the agency cannot accept delivery.

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

  • Infrastructure Infrastructure serves as the foundation and building blocks of an integrated IT solution. It is the hardware which supports Application Services (C.3.2) and IT Management Services (C.3.3); the software and services which enable that hardware to function; and the hardware, software, and services which allow for secure communication and interoperability between all business and application service components. Infrastructure services facilitate the development and maintenance of critical IT infrastructures required to support Federal government business operations. This section includes the technical framework components that make up integrated IT solutions. One or any combination of these components may be used to deliver IT solutions intended to perform a wide array of functions which allow agencies to deliver services to their customers (or users), whether internal or external, in an efficient and effective manner. Infrastructure includes hardware, software, licensing, technical support, and warranty services from third party sources, as well as technological refreshment and enhancements for that hardware and software. This section is aligned with the FEA/DoDEA Technical Reference Model (TRM) which describes these components using a vocabulary that is common throughout the entire Federal government. A detailed review of the TRM is provided in Section J, Attachment 5. Infrastructure includes complete life cycle support for all hardware, software, and services represented above, including planning, analysis, research and development, design, development, integration and testing, implementation, operations and maintenance, information assurance, and final disposition of these components. The services also include administration and help desk functions necessary to support the IT infrastructure (e.g., desktop support, network administration). Infrastructure components of an integrated IT solution can be categorized as follows:

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Dewatering (a) Where the whole of a site is so affected by surface water following a period of rain that all productive work is suspended by agreement of the Parties, then dewatering shall proceed as above with Employees so engaged being paid at penalty rates as is the case for safety rectification work. This work is typically performed by Employees engaged within CW1, CW2 or CW3 classifications. When other Employees are undertaking productive work in an area or areas not so affected then dewatering will only attract single time rates. (b) Where a part of a site is affected by surface water following a period of rain, thus rendering some areas unsafe for productive work, consistent with the Employer’s obligations under the OH&S Act, appropriate Employees shall assist in the tidying up of their own work site or area if it is so affected. Where required, appropriate Employees will be provided with the appropriate PPE. Such work to be paid at single time rates. Productive work will continue in areas not so affected. (c) To avoid any confusion any ‘dewatering’ time which prevents an Employee from being engaged in their normal productive work is not included in any calculation for the purposes of determining whether an Employee is entitled to go home due to wet weather (refer clauses 32.4 and 32.5)

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