Available Documentation Clause Samples
The 'Available Documentation' clause defines the obligation to provide or make accessible relevant documents related to the subject matter of the agreement. Typically, this clause specifies which documents must be shared, such as technical manuals, compliance certificates, or records necessary for due diligence, and may outline the format or timeframe for delivery. Its core practical function is to ensure that all parties have access to essential information, thereby promoting transparency and enabling informed decision-making or compliance with contractual requirements.
Available Documentation. Pre-studies (states of the art, proposals, discussions). • Proposals for Mathematical Extensions for Event-B [3] • Mathematical Extension in Event-B through the Rodin Theory Component [4] • Generic Parser's Design Alternatives [5] • Theoretical Description of Structured Types [6] • Technical details (specifications). • Mathematical_Extensions wiki page [7] • Constrained Dynamic Lexer wiki page [8] • Constrained Dynamic Parser wiki page [1] • Theory plug-in wiki page [9] • Records Extension Documentation on wiki [10] • Teaching materials (tutorials). • User's guides. • Theory Plug-in User Manual [11]
Available Documentation. 8.4.1. Flow plug-in
Available Documentation. See the references below. The validation document is being prepared and will probably be made available in spring 2011.
Available Documentation. The internals of the relevance filter plug-in and the process of fine tuning are documented in ▇. ▇▇▇▇▇'▇ Master thesis.[6] • A rigorous specification of Event-B's logic (for Rodin developers) and a reference document containing the definitions of built-in symbols (for Rodin developers and users) can be found in "The logic of Event-B" report.[10] • The specification of the Improved ▇▇ ▇▇▇▇▇ Generation [14] is available from the Rodin Wiki.
Available Documentation. The following pages give useful information about the Rodin platform releases: • Release notes[23] . • Bugs[24] . • Feature requests[25] .
Available Documentation. SVN Team-based development documentation[5] • Decomposition plug-in user guide [6] • Event Model decomposition for shared variable approach [7] • Decomposition tool for Event-B [8]
Available Documentation. The following pages give useful information about UML-B: • Lectures[1] . • Tutorials[1] . • Worked Examples[1] . UML-B State-machine Animation Plug-in: • General information[2] • Tutorial[3]
Available Documentation. Papers describing previous work: • ▇. ▇▇▇▇▇▇▇▇, ▇. ▇▇▇▇▇▇, ▇. ▇▇▇▇▇▇▇▇, ▇. ▇▇▇▇▇▇. Automatic Testing from Formal Specifications. In Proc. of TAP'07, pp. 95-113, LNCS 4454, Springer, 2007. • ▇. ▇▇▇▇▇▇▇▇▇, ▇. ▇▇▇▇▇▇▇, ▇. ▇▇▇▇, ▇. ▇▇▇▇▇▇▇▇, ▇. ▇▇▇▇▇▇▇▇▇▇▇, ▇. ▇▇▇▇▇▇, ▇. ▇▇▇▇▇▇▇▇▇▇▇▇▇▇. Applying Model Checking to Generate Model-Based Integration Tests from Choreography Models. In Proc. of TestCom/FATES 2009, pp. 179-194, IEEE Computer Society, 2009. • ▇. ▇▇▇▇▇▇▇▇▇, ▇. ▇▇▇▇▇. Functional Search-based Testing from State Machines. In Proc. of ICST 2008, pp. 525-528, IEEE Computer Society, 2008. • ▇. ▇▇▇▇▇▇▇▇▇, ▇. ▇▇▇▇▇▇▇▇▇▇. Improving Testing of Enterprise Systems by Model-Based Testing on Graphical User Interfaces. In Proc. of the Satellite Workshops of ECBS'10. pp. 352-357, IEEE Computer Society, 2010. See also: DEPLOY Deliverable D53 (August 2010).
Available Documentation. There are two major sources of information about ProR on the internet: • ProR at the Eclipse Foundation [31] • ProR Documentation for end users and plugin developers [32]
Available Documentation. We have updated the documentation[11], including the Tasking Event-B Overview[12], and Tutorial [13] materials.