Documenting Big Data Architectures can entail re-use of classical notations for software architecture description augmented with appropriate notations aimed at isolating and identifying the data-intensive nature of Big Data applications. In this vein, the DICE ecosystem offers a plethora of ready-to-use tools and notations to address a variety of quality issues (performance, reliability, correctness, privacy-by-design, etc.). In order to make profit of these tools, the user has to use the explicit notation we have defined to support their scenario. The notation in question entails building-specific UML diagrams enriched with specific profiles, that is, the standard UML mechanism to design domain-specific extensions --- in our case, the mechanism in question was used to define stereotypes and tagged values inside the DICE Profiles and specific to model data-intensive constructs, features, and characteristics. The DICE profiles tailor the UML meta-model to the domain of DIAs. For example, the generic concept of Class can become more specific, i.e., to have more semantics, by mapping it to one or many concrete Big Data notions and technical characteristics, such as compute and storage nodes (from a more abstract perspective) or Storm Nimbus nodes. Besides the power of expression, the consistency of the models behind the DICE profile remains guaranteed thanks to the meta-models and their relations we defined using the UML standard.
|June 19, 2023 (Monday)||09:30 AM - 04:30 PM|
|July 3, 2023 (Monday)||09:30 AM - 04:30 PM|
|July 17, 2023 (Monday)||09:30 AM - 04:30 PM|
|July 31, 2023 (Monday)||09:30 AM - 04:30 PM|
|August 14, 2023 (Monday)||09:30 AM - 04:30 PM|
|August 28, 2023 (Monday)||09:30 AM - 04:30 PM|
Let us know how we can help you.