Other modelling formalisms Sample Clauses

Other modelling formalisms. Aside from the UML-based family of modelling formalisms, other SESAMO modelling formalisms are associated with specific toolsets. For example, The BDMP (Boolean logic Driven Markov Processes) formalism was adapted from the dependability area to the security domain in order to model attack scenarios, and is supported by the KB3 modelling software platform of consortium partner EDF to let security analysts build and analyze security-oriented BDMP models. Similarly, the ASCE tool of SESAMO partner Xxxxxxx uses its own formalism for modelling security informed safety cases. The SCYTHER tool uses a specialized modelling language, the Security Protocol Description Language, which can characterize security protocols and verify security claims. The IMACT tool of partner XxxXX is another example of the use of a specialized modelling formalism to implement a model-based engineering approach in the avionics domain of SESAMO. As illustrated in Figure 16, the IMACT tool implements a classic model-based engineering approach with a specialized modelling language capable of representing the elements of the Integrated Modular Architecture (IMA) – including the SESAMO partitioning building blocks. While creating the model, the user resolves ambiguities and makes trade-offs as appropriate on the basis of analyses run on the models (this is where the SESAMO analytic techniques are applicable). Code generation can follow, much as in the AUTOSAR approach in the automotive domain. For further information on the IMACT workflow and technical details see Appendix A. All of these specialized modelling formalisms co-exist within the SESAMO modelling environment, and are likely to be in use simultaneously within modelling initiatives, supported by different parts of the SESAMO toolchain. The degree of interoperability between those different tools will be determined by the possibility of property and semantics preserving M2M transformations between the formalisms used by the tools. This has been possible for those in the UML family, despite the use of different profiles and despite their different commercial providers. It has also been possible when modelling tools come from the same overall family. For example, modelling tools that come from the SysML based AVATAR family and are in use within the consortium (see ProVerif [18] and UPPAAL [11] within the railway use case) have been successfully provided with automatic transformations from the original AVATAR models (and TTOOL [12] inco...
Sample 1
AutoNDA by SimpleDocs

Related to Other modelling formalisms

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

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

  • Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.

  • Timeline Contractor must perform the Services and deliver the Deliverables according to the following timeline:

  • Design XXX XXX XXXXX Plan and Aligned Budget

  • Logging The ISP will require the maintenance of network and application logs as part of BNY Mellon’s security information and event management processes. Logs are retained in accordance with law applicable to BNY Mellon’s provision of the services as well as BNY Mellon’s applicable policies. BNY Mellon uses various tools in conjunction with such logs, which may include behavioral analytics, security monitoring case management, network traffic monitoring and analysis, IP address management and full packet capture.

  • Timelines a) Timelines may be extended by mutual consent of the parties. b) Working days shall be defined as Monday through Friday excluding statutory holidays. c) Disputes that arise during non-instructional days (Summer Months, Christmas Break, and March Break) will have timelines automatically extended. d) Local grievance timelines will be held in abeyance while the dispute is in the CDRP, in the event that the matter is referred back locally.

  • Scaling “Scaling,” as used herein, involves:

  • Work Scheduling Except at the request of an affected employee, no employee shall have the number of hours they are normally scheduled to work reduced as the result of the use of non-permanent employees such as, but not limited to: seasonal, intermittent, student interns, interns, interim, established term, or temporary employees, due to the performance of such employee’s duties by the nonpermanent employee.

  • Training Program It is agreed that there shall be an Apprenticeship Training Program, the provisions of which are set forth in Exhibit "D", which is attached hereto and forms part of this Agreement.

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