Sparx EA Inspector

By Tim Ackroyd on

In this episode, we will focus on "Inspector". In Sparx Systems Enterprise Architect (EA), the Inspector is a panel that provides detailed information and properties of selected elements within a model. It allows users to view and modify various attributes, relationships, and other details associated with elements such as classes, objects, use cases, actors, etc.

Over the past couple of years, I have been in projects where project teams are using a Wiki to drive their projects. First off, I am not against this by any means. After all, wikis started as Knowledge-Management platforms and what is more important to project delivery than access to knowledge, right?

However, and OMG!, if you cannot effectively manage knowledge, how useful is your Wiki? Thus to my point about seeing the most atrocious uses of Wiki and then wondering why the company has so much trouble with delivery and/or managing their architecture. What I see is more like "fire and forget"...literally!

Too many people forget that "data" is "knowledge" and while wikis were great in the '90s and early 2000's, there are now much better and more effective ways of exposing "knowledge" (data, intelligence).

While the above clip is on something as simple in Sparx EA as a modeling (UML, CASE) platform, such as a tool to parse the data under your model elements, Sparx is a modeling tool over SQL technology. Whether you have one project file locally on your PC, or dozens of Sparx Projects over many Cloud SQL instances, the important thing to understand is what you can do with that "Data" (intelligence).

Now just imagine inspecting your model and project data in a data architecture such as Azure Data Lake Storage using Databricks notebooks and other data science tooling (AI, ML) while applying advanced analytics techniques.

Comments

Post a Comment

Popular posts from this blog

Sparx EA and Open Collaboration

By Tim Ackroyd on
I get asked, quite often, "Is there a way to integrate Sparx Enterprise Architect (EA) with other tooling?" My answer is always, "Yes". There are multiple approaches, from very simple to more advanced. I have helped several shops do this over the years, and may do videos on this in the future. Integrating Sparx with Azure DevOps and other Cloud platforms, as well as other Tooling, is very possible and beneficial for managing delivery, such as requirements, problem solving, design, and development... all in a unified way.  The integration can allow companies/shops to seamlessly synchronize between Sparx EA's modeling environment and platforms, such as Azure DevOps'. Remember that one of the biggest benefits of Sparx EA over other modeling platforms, is that Sparx is based on Data-First implementation and supports open integration. Years ago, something call Open Services for Lifecycle Collaboration (OSLC) came out and Sparx was one of the first to embrace it. ...
Read more

BPMN Diagram versus Sequence Diagram

By Tim Ackroyd on
I am getting some great questions in our  UML Operator Channel , as we are publishing  a series on Business Process Modeling Notation (BPMN) . Modelers see the term "Sequence" in BPMN and get a little confused...probably my fault 😏. When using BPMN, just understand the difference between Unified Modeling Language (UML) and BPMN (an extension of UML) and things should fall into place. So now let's talk about BPMN vs UML Sequence Diagrams... BPMN Diagram versus Sequence Diagram BPMN diagrams and sequence diagrams are both types of visual representations used in the field of business process modeling and software engineering, respectively. While they share some similarities, they serve different purposes and focus on different aspects of a system or process. BPMN Diagram: Purpose: BPMN (Business Process Model and Notation) is used for modeling and documenting business processes. It provides a standardized way to r...
Read more

MDA vs MDD

By Tim Ackroyd on
This post kicks of a new series on UML Operator Channel  UML Operator Channel around systems and software delivery, titled "Model-Driven Anything". Subscribe, turn on notifications, follow, and most importantly...Contribute 😎 IMPORTANT NOTE: Never start a software development effort without Requirements!!! or Scope!!! However, sometimes software starts out as a means of developing scope and requirements! So what are we talking about? Model-Driven Architecture (MDA) and Model-Driven Development (MDD) are both approaches within the realm of software development that emphasize the use of models as primary artifacts in the software engineering process. However, they have distinct focuses and methodologies. Here are the key differences between the two: Model-Driven Architecture (MDA) Origin and Standardization: Origin: MDA is a software design approach proposed by the Object Management Group (OMG). Standardization: It is a well-defined framework with standardized guidelines and...
Read more