Current Tool Landscape Sample Clauses

Current Tool Landscape. ‌ The ASCENS tool landscape reflects the ASCENS approach to the software development lifecycle, illustrated on Figure 1 and described in detail in joint deliverable JD3.2. Following the ASCENS approach to the software development lifecycle, we roughly classify the tools into design tools and runtime tools. This distinction is not strict – especially the difference between monitoring a faithful simulation at design time and monitoring a real execution at runtime can be small – but it is useful to provide a presentation structure. Feedback Design Runtime Deployment Figure 1: ASCENS Ensemble Software Development Life Cycle On the design cycle side, our tool support starts with the early stage formal modeling tools. These tools are the jSAM stochastic model checker (Section 2.1) for the modeling approaches that rely on process algebras and the Xxxxx Daemon Wrapper (Section 2.2) for the modeling approaches that rely on rewriting logic – three tools that rely on Xxxxx, MAIA (Section 2.5), MESSI (Section 2.3) and MISSCEL (Section 2.4), have also been developed. The SimSOTA tool (Section 2.6) can evaluate the behavior of complex feedback driven adaptation mechanisms using simulation. The FACPL frame- work (Section 2.7) can be used to capture policies that regulate interaction and adaptation of SCEL components. The KnowLang Toolset (Section 2.8) serves to describe knowledge models which are then compiled into a binary knowledge base, to be used for subsequent knowledge reasoning tasks. Where applicable, we continue with tools for transition from modeling to programming. These include the BIP compiler (Section 2.9) for the approaches that rely on correctness by construction. For manual implementation, we provide frameworks that reify the formal modeling concepts, specif- ically jRESP (Section 3.2) and jDEECo (Section 3.3) – as explained in other deliverables, the two frameworks follow different strategies in mapping the SCEL language entities into implementation constructs. Because the manual implementation approaches do not guarantee preserving the correspondence between the model and the code, we also examine methods and tools to verify whether code complies to models. For C code, we have developed the GMC model checker (Section 2.10), for Java code, we have integrated the JPF model checker in jDEECo (Section 3.3). On the runtime cycle side, our tool support has to consider the differences between ensembles and more ordinary applications. The fact that ordinary ap...