Getting Started
This section shows the application of a DICE Profile at DPIM (Architectural) level for annotating UML diagrams with quality parameters. First, it is worth to recall that the modelling phase is done using Papyrus. Since there exists extensive documentation on how to use this tool to create profiled UML models, we will not provide details on the usage of this specific tool.
We use an example of a real system for illustrating how to import the DICE profile and annotate the UML diagrams. In particular, we describe the POSIDONIA Operations, a customizable Integrated Port Operations Management System. It optimizes the operational maritime activities related to the vessel flow within the service area of the port, integrating all the involved stakeholders and all the relevant information systems. The system constantly monitories and receives information from different sensors (GPS, temperature, radio) and boats; and processes the messages accordingly.
Next figure shows the UML activity diagram detailing all the steps of the POSIDONIA Operations. The diagram is divided in four phases. Each phase has a certain execution time (hostDemand annotation, value=$parse), which describes the expected average time of execution (statQ=mean), the time unit (unit=ms) and how the time is determined (assumption, source=assm).
The arrival of new messages from sensors and boats is represented by the annotation arrivalRate of the initial state NMEAstream. The parameters value, unit, statQ and source are equivalents to the parameters of the hostDemand annotation. The initial node is marked as open for indicating that the messages arrives in streaming or real-time.
Finally, the last figure shows the UML deployment diagram. It details the deployment of all the logical components into the hardware resources. The annotation poolSize indicates the number of computational cores available on the server (value=$aisParser).
