Tool Support Sample Clauses

Tool Support. In this section we give a brief introduction to the functionality of the tool Reqaid. This requirements tool is an application that has been developed and used in the project Aletheia [8]. Moreover, it is currently successfully used in the EU project Smart Products [9]. The IoT-A consortium decided to use Reqaid as a tool for documenting the requirements, as it supports the specifically defined requirements process. In particular Reqaid supports the following functions: • Version Control: Requirements and use cases can be changed as often as desired by persons of the project through the whole project cycle. Reqaid has an automatic version control to ensure that no data loss occurs after modifications. • Access Rights: Access rights ensure which user groups can view or change certain information such as use cases and requirements.
View Source
Tool Support. ADLs provide a formal description of the system, thus they can be manipulated and reasoned about in an automated fashion by software tools. This tool support determines the usefulness of an ADL to a large extent. • Active Specification: An active specification reduces possible design options.
View Source
Tool Support. Active Specification: The EAST-ADL tooling actively supports the user during specification, e.g. the tool prevents syntactically incorrect connections between components. • Multiple Views: EAST-ADL provides possibilities for multiple views on different levels of abstraction. However, it is left up to the user to ensure the consistency between the different views. • Analysis: EAST-ADL supports validation techniques such as simulation, rapid control prototyping (RCP) and hardware/software in the loop and safety analysis. Simulation requires execution of the plant model and the system model, which are supported. • Refinement: EAST-ADL provides five levels of abstraction: Vehicle Layer, Analysis Level, Design Level, Implementation Level and Operational Level. The refinement between the first three levels is explicitly supported by the current EAST-ADL tools. • Implementation Generation: Currently there is no automated transformation from EAST- ADL to an implementation language such as AUTOSAR. • Dynamism: At the moment there is no support for property-preserving refactorings of models.
View Source
Tool Support. We created a few case studies to explore the usefulness of our ideas and realised that tool support is crucial for even medium-sized projects. However, we didn’t want to pursue tool development (or the extension of the existing tool) without a solid theoretical foundation. We have now reached a point where the theory is mature enough to start building tool support. We considered using the existing requirements plug-in as a starting point, but eventually abandoned the idea. There were technical and methodological Figure 4.1: Screenshot of the ProR Requirements Plug-In for Rodin
View Source

Related to Tool Support

  • Technical Support State Street will provide technical support to assist the Fund in using the System and the Data Access Services. The total amount of technical support provided by State Street shall not exceed 10 resource days per year. State Street shall provide such additional technical support as is expressly set forth in the fee schedule in effect from time to time between the parties (the “Fee Schedule”). Technical support, including during installation and testing, is subject to the fees and other terms set forth in the Fee Schedule.

  • Telephone Support The Fund Designated Persons may contact State Street’s HORIZONR Help Desk and Fund Assistance Center between the hours of 8 a.m. and 6 p.m. (Eastern time) on all business days for the purpose of obtaining answers to questions about the use of the System, or to report apparent problems with the System. From time to time, the Fund shall provide to State Street a list of persons who shall be permitted to contact State Street for assistance (such persons being referred to as the “Fund Designated Persons”).

  • Technical Support Services 2.1 The technical support services (the "Services"): Party A agrees to provide to Party B the relevant services requested by Party B, which are specified in Exhibit 1 attached hereto ("Exhibit 1").

  • Operational Support 2.1 Party A agrees, according to the operational needs of Party B, to act as the guarantor of Party B in the contracts, agreements, or transactions entered into between Party B and third parties, in order to fully guarantee the performance by Party B of such contracts, agreements, and transactions. 2.2 Party A agrees, according to the operational needs Party B, to recommend directors and senior management to Party B and Party B agrees to appoint such personnel recommended by Party A to be its directors and senior management. The relevant personnel recommended by Party A pursuant to this Article shall meet the qualification requirements for directors and senior management under applicable laws. 2.3 To ensure the performance of this Agreement, Party A agrees to provide to Party B cooperative policy advice and guidance, which is consistent with the daily operation and financial management and the employment policy of Party B.

  • Acceptance Testing At the time of installation of a LIS trunk group, and at no additional charge, acceptance tests will be performed to ensure that the service is operational and meets the applicable technical parameters.