|Generative AI in Sparx Systems Prolaborate||Nizam Mohamed||This session will introduce the new AI capabilities in Sparx Prolaborate Platform that will help an Enterprise Architecture team maximize its efficiency. Join this session to see how the AI-powered tools available in Prolaborate may assist architects in obtaining insights and identifying patterns from complicated Enterprise Architecture Models.|
The session will demonstrate the capabilities of the platform to
Obtain Insights from Model by using Natural language
Use the power of the trained Generative AI assistant to interpret complex models and diagrams to provide all required responses
Generate Elaborate documentation for your Architecture models using plethora of intelligence in the Generative AI world
Architecture Content Generation and validation to ensure the information in your Architecture landscape is accurate
|PLENARY – Increasing your EA ROME (Return on Modelling Effort)||Jackie Mitchell||An interactive session to explore the real world difficulties in getting our organisations to embrace EA. Discovering practical ways to break down barriers to EA adoption and sharing solutions to increase our modeling productivity!|
|Tools and Techniques|
|Analiza to zalezy – Document generation (PL)||Wojtek Giers||Pl|
Czy pracujesz z klientem, który nie ma dostępu do EA lub nie chce go mieć? Czy Twój klient używa tylko Worda do prowadzenia analizy? Jeśli tak masz to na pewno chciałbyś pracować w EA i umieć generować dokumenty tekstowe na podstawie repozytorium. Podczas występienia pokaże jak z użyciem funkcji generowania dokumentacji i tworzenia szablonów, stworzyć dokument SRS w EA. Oczywiście będę używał jedynie podstawowych funkcji EA. W trakcie warsztatu pokaże nieco teorii i dużo praktyki. Zapraszam.
Are you working with a client who doesn’t have or doesn’t want access to EA? Does your client only use Word to create their analysis? If so, you would definitely like to work in EA and be able to generate text documents based on the repository. During the presentation, I will show how to create an SRS document in EA using the documentation generation and template creation functions. Of course, I will only use basic EA features. During the workshop, i will show some theory and a lot of practice
|EA without diagrams||Ian Mitchell||EA is a visual modelling tool, but that doesn’t mean we need to use diagrams for everything.|
In this session Ian will explore how we can replace large numbers of diagrams with simple spreadsheets views, and what this means for the kinds of data which EA can contain, and the kinds of users who might now want to use EA.
|Model Maturity Model Integration – Live!||Peter Lieber||Related to the CMMI (Capability Maturity Model Integration) we defined the MMMI (Model Maturity Model Integration). The goal of the MMMI is to constantly develop the value of models within organisations over different levels. |
The 5 levels of maturity are – once clearly defined – a step-by-step process.
Level 0: No Model
Level 1: My, myself and I
Level 2: Collaboration
Level 3: Advanced Collaboration and Publication,
Level 4: Regulation and Optimization.
What is needed to develop from one level to the next and what benefit does it bring? In this training session, we discuss conditions and goals to development can take place within the organisation. One of the most important pieces: How to develop the value acknowledgement that models are creating.
We look at this 5M-development process not only from the organization’s perspective but will also reflect your role as enterprise architect and modelling expert, acting in an ecosystem.
|A model driven approach to designing and managing changes in the IT Architecture||Habte Woldu||Today organizations face a challenge of running many projects that span across various IT Applications and components. As teams become more agile, understanding and managing the changes in the IT Architecture landscape becomes a challenge.|
In this presentation we’ll present :
The key challenges of managing changes in IT Architecture
The concept of organization of Enterprise Architect repository to manage changes and model versioning across different teams, components and projects
The Model driven approach to integrate IT Architecture design and implementation processes, where models are the single source of executable specifications like Swagger, OpenAPI, JSON Schema, Avro Schema, etc. that feed the implementation process for various platforms and architectures.
|Using perspectives in EA||Jacek Woynarowski||A practical application and demonstration of principles discussed in Global Summit|
|Modeling SIL (system integration lab) for missile against missile system using Enterprise Architect||Avishai Lebenzon||It is not a secret that in many cases there is one high motivated person who is determinate about the Necessity of EA and tries to push the organization to work with the tool, but others are not always at the same state of mind. |
Pandatech group had took part in missile against missiles weapon development program. The program included two parts:
First project – development of the system itself.
Second project – labs development for the system integration and testing.
Our part was to design the system integration lab (SIL). The SIL components were based on the system components. Unfortunately, the system components were not yet designed.
Initially, modelling was not considered due to tight schedules.
It would have seemed unnecessary to plan a laboratory construction project using models.
Due to the tight schedule, system engineering teams just wanted to fulfil the prototype and finish the proof of concept based on lean documents.
The presentation will share some of the design process issues based on real examples and will go over some methodology issues.
|Cyber Security – threat modelling||Bob Hruska||Cyber Threats stem from 4 problem areas: the complexity of systems as IoT presents to us, the vulnerability of systems due to software inconsistencies, the know-how of attackers and the tools to do so. The sticking point becomes apparent in the development process of systems. But here, security considerations follow most often at the end of the process, which also leads to insufficient documentation.|
Threat Modeling+: The methodology to develop secure systems, in compliance with standards and regulation. Insufficient documentation contradicts industry-specific standards and norms. In the future, the Cyber Resilience Act will mandate such an approach for all digital systems.
The approach of “Cybersecurity by Design” with its implementation in Threat Modeling has existed for some time. The aim here is to identify potential threats in the system model based on a threat model. The AIT Austrian Institute of Technology has further developed this modeling method with artificial intelligence and industry-specific threat catalogs under the name “ThreatGet”.
|KSI ZUS in EA – working with big EA models||Kalina Mielke||1. How to work with IT system-monsters|
Drawbacks of keeping detailed documentation in EA for such a big system.
Need for specific tools.
2. Why relational database and why postgresql.
3. Adding tables to EA db model and how to query them in EA (in postgresql)
4. What about adding db triggers to EA model (postgresql)
to put some data automated way?
5. Comparing EA models
Special repository for EA models.
|Using EA and Prolaborate for System integration||Jan de Liefde||The realization or renovations of large infrastructure systems are longyear projects where we have to deal with different operational-, technical-, integration- and management challenges.|
This presentation shows how we can use the combination of Enterprise Architect and Prolaborate to tackle these challenges and offer different projectroles (project/technical management, system and domain engineers, contractmanagement, Stakeholder management, etc.) role related information and visualizations based on a consistent set of data stored in the model.
The combination of Enterprise Architect and Prolaborate supports multi-disciplinaire projecteams to have an integrated view on Issues, decisions, changes, risks, changing schedules in combination with requirements, interfaces and different levels design.
|Creating a Digital Twin Enterprise knowledge management systems – methodologies implemented in EA||Roman Kazička||Sharing experiences of using EA and:|
– Supporting all stakeholders, especially decision makers:
– Right Information for Right Role In right time.
– Communication, Understanding, Trust, Cooperation.
In practical examples based on Sparxsystem ecosystems – EA, Procloud Server, PROLABORATE, Lemontree, EaDocx, plus Atlassian Confluence.