Publish EA Model Online: Engaging Stakeholders with Prolaborate

Publishing an EA model online is about making your architecture content accessible, understandable, and engaging for a broad audience over the web. Traditionally, sharing Enterprise Architect models meant generating static documents or HTML reports and sending them out. This approach is cumbersome and quickly leads to outdated information. Enter Prolaborate – Sparx Systems’ web platform – which offers a dynamic solution to publish EA models online and keep them continuously up-to-date. In this article, we’ll explore how using Prolaborate to publish your EA models can transform stakeholder engagement and why it’s a game-changer for organizations looking to socialize their architecture.

Features  Case Studies

The Pain of Traditional Model Publishing 

If you’ve managed enterprise models before, you know the pain points. You might export diagrams to PDF for a presentation, or write lengthy Word documents to explain the model to non-technical stakeholders. Perhaps you’ve used EA’s HTML report generator to put a model on an intranet. These methods work in the short term but have significant drawbacks:

Static Snapshots: The moment you export a document or HTML, it starts to become stale. Models evolve rapidly, and keeping external artifacts in sync with the live EA repository can be a full-time job. As Sparx’s documentation notes, while you can publish models via documents, the result is “a decoupled export from the live repository” – meaning any changes after export are not reflected.

Limited Interactivity: A PDF or HTML export is read-only and offers little interactivity. Stakeholders can’t query the data or navigate freely; they are limited to whatever was laid out in the document. The richness of the EA model (its traceability, alternate views, etc.) is lost.

Distribution Challenges: Ensuring everyone has the latest copy is difficult. Large documents might sit in email attachments or shared drives where they’re easily overlooked or versions proliferate.

Access Barriers: If someone wants deeper information, they often need to ask an EA specialist for a custom report or, worse, get access to the EA tool itself, which has a learning curve. 

Given these issues, it’s clear why simply publishing a model once is not enough. What teams need is a living publication – a source that is always current and interactive. That’s exactly what “publishing your content” via Prolaborate aims to achieve. 

Prolaborate: Turning Your EA Model into a Live Web Portal 

Prolaborate allows you to publish EA models online in a way that overcomes the above challenges. Instead of static files, it provides a web portal where the content of your EA repository is accessible in real time. When you use Prolaborate, you’re essentially deploying your model to a web app where authorized users can explore it as needed. 

Here’s how Prolaborate addresses the traditional pain points: 

• Always Up-to-Date: Because Prolaborate connects directly to the EA repository (via Sparx’s Pro Cloud Server), it serves live data. If an architect updates the model, a stakeholder browsing the Prolaborate site will see that update instantly. You effectively “share your models by giving people browser-based views through Prolaborate” and these views are as current as the source. No more version confusion or manually regenerating documents; the single source of truth is the model itself, now viewable online. 
• Interactive Navigation: Prolaborate isn’t a flat export – it’s an interactive application. Users can click through packages, open diagrams, drill down into element details, follow relationships, and even perform searches or queries. This mimics much of the power of Enterprise Architect but in a simplified, read-friendly manner. For example, a stakeholder can start at a high-level diagram of business processes, click on a particular process to see the detailed BPMN diagram, and then click on an element to see its properties or linked requirements. This level of self-service exploration is impossible with static documents. It engages stakeholders because they can ask their own questions of the model and get answers immediately, simply by navigating. 
• Custom Views for Target Audiences: When publishing your EA content online, one size does not fit all. Prolaborate allows you to create tailored pages and dashboards that present key information for specific audiences. For instance, you might have a “Project Dashboard” page that shows, via charts and lists, the status of requirements, key milestones, and etc., These pages are essentially curated selections of model content arranged in a narrative or report-style format. Sparx Systems introduced a feature called “Pages” in Prolaborate that “allows you to structure and display key diagrams and element details in a document-like format”. This means you can design a web page that feels like a live report – combining diagrams, and model data – which is perfect for publishing to executives or clients. They get a friendly overview (like a report) but it’s not static; if they refresh next time after some changes, they might see updated charts or new elements automatically included. Prolaborate essentially lets you publish the model in context, not just as raw model dumps. 
• No EA Installation or Training Needed: A major barrier to model communication has been the requirement for stakeholders to learn a complex modeling tool. With Prolaborate, to share your EA model online, you simply send a web link. There’s no installation, and the interface is designed for clarity. The key highlight of Prolaborate is that it gives people web-based views for an “easy way to publish the content” of your models. Stakeholders can zoom into diagrams, read element descriptions, and even use graphical viewers – all without any technical setup. This dramatically broadens your reach: anyone comfortable with a web browser can consume the model content. 
• Stakeholder Engagement and Feedback: Publishing is not just about pushing information; it’s also about gathering in feedback. Prolaborate includes features to capture stakeholder input directly on the model. For example, suppose you’ve published the EA model of a proposed system architecture. Business stakeholders browsing it can highlight a concern by dropping a comment right on the relevant component. This feedback loop is immediate and tied to the context (much better than an email saying “see page 5 of the PDF, I have a concern”). By lowering the bar for providing feedback – just type your comment next to the diagram – Prolaborate encourages engagement. Stakeholders feel heard and involved because their input goes straight into the model discussion rather than a side channel. 
• Regulatory and Contractual Documentation: It’s worth noting that publishing models online via Prolaborate doesn’t mean you never produce documents. There will still be cases (regulatory submissions, contractual deliverables) where a physical document is required. Enterprise Architect itself has robust document generation for those scenarios. However, what Prolaborate does is handle the day-to-day communication. It ensures everyone is working off the live model for their understanding, reducing the number of ad-hoc documents needed. When you do generate a formal document, it can be from the latest model without worrying that people have been reviewing an out-of-date version in the interim. Prolaborate thus complements EA’s document publishing by acting as a continuously updated publication medium.  

Making Your Model Easy to Access 

Publishing your EA model online with Prolaborate not only benefits internal stakeholders but can also improve the discoverability of architecture knowledge within your organization. When architecture information is locked in siloed documents or in the heads of a few experts, it’s effectively invisible. By publishing it online via Prolaborate you allow team members to search and find what they need. Prolaborate’s search function helps users quickly locate specific parts of the model (e.g., “CRM data model” or “Order Management Use Case Diagram”). It turns your EA repository into a knowledge base that people actually use. 

Publishing the model is broadcasting the enterprise architecture or solution architecture of your enterprise. It shows transparency – anyone with access can see how things are structured. 

Security and Access Control 

Of course, when publishing anything online, security is paramount. Prolaborate includes robust security measures to ensure you publish safely: 

User Authentication: Only authorized users can access the model content. Prolaborate supports integration with enterprise identity systems (like Azure AD, Okta, etc.), so you can manage access via single sign-on and existing user accounts. 

Granular Permissions: You can control exactly what each user or group can see and do. For example, you might allow a partner company’s user to view a specific package in the model and nothing else. Or allow certain internal users to comment but not edit. This granular control means you are publishing only what’s appropriate for each audience, mitigating the risk of exposing sensitive information. 

Read-Only vs. Edit: By default, most stakeholders accessing via Prolaborate will be in a read/comment mode. Only designated modelers or admins can make structural changes. Even if you open your model broadly for viewing, you maintain governance over who can actually modify the source. 

HTTPS and Encryption: Prolaborate is typically deployed using HTTPS for secure data transfer. And because it works with Pro Cloud Server, it benefits from Sparx’s secure API calls. Your model data isn’t open to the internet at large; it’s delivered securely to authenticated sessions. 

Transforming Stakeholder Engagement 

Let’s consider the impact of having your EA model published online in a live portal: 

Stakeholders become Self-Sufficient: A project manager can check the latest process flow or requirements in Prolaborate without having to email the architect. A developer can quickly find an entity relationship in the data model while coding. This self-service reduces bottlenecks and interruptions for the modeling team. 

Architecture Becomes Part of Daily Conversation: When the architecture is one click away (and even integrated into tools like Confluence or Jira as mentioned earlier), it naturally becomes referenced more often. People will include Prolaborate links in meeting notes or chat discussions. This means architectural considerations stay front-and-center during project execution, leading to fewer misalignments. 

Feedback Loop Shortens: If a stakeholder spots an issue or has a suggestion, they can immediately annotate the live model. Contrast this with waiting for the next document release or meeting – the loop could be weeks shorter thanks to instant online access. 

Showcasing and Buy-In: From an architecture team, publishing the model online is also a way to showcase your architecture work to leadership in an interactive format. Instead of static slides in a quarterly review, you could invite executives to view a Prolaborate dashboard that visualizes how the architecture is evolving. The visual dashboards and live reports can demonstrate progress (or highlight issues) in a compelling way, helping you get buy-in for architecture initiatives. Sparx Prolaborate supports creating such dashboards and charts that draw from model data (e.g., number of applications by department, or compliance status of components), turning raw model data into business-relevant information. 

Conclusion 

Publishing an EA model online using Sparx Systems Prolaborate is a smart strategy for any organization aiming to maximize the value of its enterprise architecture. It moves your model from a closed environment to an open platform (within the bounds of security) where it can inform, guide, and involve all stakeholders. The result is a living architecture repository: always current, easily accessible, and richly interactive. 

In summary, if you want to publish your EA model online in a way that truly engages people, Sparx Prolaborate is the tool to do it. It combines the rigour of Enterprise Architect with the accessibility of the web.