Task Contributions and Progress Sample Clauses

Task Contributions and Progress beyond the State-of-the-art‌ As noted in the previous subsections, dynamic representations found in current literature are not always capable of effectively describing the dynamic view of software systems. Modelling the dynamic view of a system and designing a representation that allows developers to describe it are two quite important contributions of this task. Additionally, the design of a unified view of software projects represented using an aggregated ontology is another meaningful contribution that effectively illustrates the expected outcome of WP3. As part of working on these directions, we had to achieve significant progress beyond the current state-of-the-art. In specific, the work on this task includes the following main contributions: • The design of a dynamic ontology that is used to represent the dynamic view of a software project. This ontology covers the possible action-flow representations as long as they are compatible with the RESTful paradigm. • The development of a dynamic representation that is oriented towards the main concepts of the RESTful paradigm. This representation is designed in the form of storyboards, i.e. system scenarios described in the form of diagrams. As part of this contribution, we can also distinguish the following progress points: o Upon analysing the current state-of-the-art on dynamic representations, we claim that this new diagram type is required since no other representation, either graphical or textual, can describe the dynamic view of RESTful services effectively. Current UML diagram types and textual representations are oriented towards the Object Oriented paradigm; thus, they cannot describe the resources of a RESTful service, or the actions and the properties on these resources, without compromising their semantics or introducing verbosity. o Since current graphical editors are not capable of handling the creation and editing of storyboards, we design and implement a new tool to sufficiently meet this requirement. Our tool allows designing storyboards based on a robust non-verbose meta-model, since it is based on the well-known Eclipse IDE. Additionally, the main prerequisites for the S-CASE tools are also met, as our tool is open-source and cross-platform, while it allows coupling with components supporting the XMI representations of Eclipse. • The design of an aggregated ontology of software projects. This contribution is actually a central element of S-CASE since it focuses on the main scope of this w...