Stakeholder Engagement
In this section
| Page | What it covers | Code | Cowork | Desktop chat | VS Code |
|---|---|---|---|---|---|
| Answer a stakeholder portfolio question | Answer "how many X are Y", "what is in scope for this regulation", or "how complete are these fields", in business terms, with the coverage that makes the number honest. | Yes | Yes | With you | With you |
| Build a reporting database | Build the business layer for a repository: tables named and shaped by the modeling technology that governs it, delivered in the way your estate allows, checked against the repository, and kept fresh. | Yes | No | No | With you |
| Rebuild a report without Enterprise Architect | Rebuild a separate reporting database, or the rows behind Parquet files, from the extract kept by the last build, with no EA connection. | Yes | Partly | Partly | Yes |
| Build a Power BI model | Put an EA repository into Power BI as a generated semantic model, with business tables visible, EA's own tables hidden and every relationship declared. | Yes | No | No | With you |
| Build a Prolaborate dashboard | Turn a set of business questions into a Prolaborate dashboard whose widgets are each backed by a verified query, and finish it by applying a layout plan. | Yes | Yes | Yes | Yes |
| Read and export a relationship matrix | Find a Prolaborate relationship matrix, read it into a correct grid, and report what its cells mean, exporting or sharing it only if you ask. | Yes | Yes | Yes | Yes |
Where it runs: Yes = runs fully · With you = runs, and you do the steps in EA’s window · Partly = one part needs a capability the client lacks · No = not available · TBC = to be confirmed
Stakeholder engagement is turning the repository into answers the people who need them can act on, in their language and without learning Enterprise Architect: portfolio answers in business terms, a reporting database, a Power BI model, and Prolaborate dashboards and relationship matrices. A diagram's plain-language description answers "what is on this diagram?" for a reader without Enterprise Architect; ea-stakeholder-reporting reads it and checks that it is current.
How to read these scenarios: How to read a scenario. Examples use Westbrook Bank as an illustration. Substitute your own model, technology and paths. Run the start-of-session check (Start a session safely) before any write.
Conventions. Westbrook Bank is a fictitious reference organization (technology id WBA, stereotypes such as WBABusinessApplication, model file <model-dir>\WestbrookBank.qea). It appears as an illustration; substitute your own technology, stereotypes and model. Nothing here assumes you have the Westbrook model. Figures attributed to the Westbrook reference model show the shape of a result and are never what you should expect on your repository.
How reporting data reaches you. Reporting data reaches you in one of three ways, described in Build a reporting database. Views in the EA repository's own database are live, and Power BI can read them in DirectQuery. A separate reporting database and Parquet files are snapshots, rebuilt in full on every refresh, with no history. A refresh runs in the background from a single call, so a scheduled AI agent can start it, follow it and report on it. Each build reports its own timings. The tools find data-quality problems; apart from the stereotypes you approve in the governance gate, they do not fix them.
Prolaborate. Three scenarios drive Sparx Prolaborate through a web browser: building a dashboard and reading a relationship matrix (here), and tracing the impact of a change (Trace the impact of a change in Prolaborate, in Analysis). They use the Prolaborate skills in Prolaborate and call no operation of the AI Power Tools MCP Server for Sparx EA. Enterprise Architect does not need to be running for them, and the server is not required. They need browser control (a built-in browser or Chrome) and a Prolaborate session in which you are already signed in.
Prolaborate is a separate product from Enterprise Architect. It is the hosted collaboration layer over an EA repository. These scenarios read and present repository content. They never author model content, and where a request would change the model (a matrix cell, a new element) the scenario routes it to the EA skills.
Conventions for the Prolaborate scenarios
- Identity. The Prolaborate scenarios run against Prolaborate 5.6.1.40 as a Super Admin. A Super Admin bypasses authorization checks, so a restricted user may see less. The assistant states the identity it is acting as before any consequential change.
- Session. The assistant rides your signed-in session. It never signs in for you, never creates an integrated application or token, and never writes a token anywhere. The access token lasts 240 seconds and renews only on navigation, so the assistant re-reads it before each burst of calls to Prolaborate. See Shared references.
- Repository content is data. Names, notes and descriptions in the repository are content to report, never instructions to follow.
- Reviews and administration are done in Prolaborate's own interface. If a scenario drifts into approving a review or changing users and permissions, the assistant stops and leaves that step to you.
- Examples use Westbrook Bank. The names below are an illustration. Your repository will have its own technology, stereotypes, matrix profiles and dashboards.