I am constantly helping other work more productively in systems and software engineering. This is another example that I will focus on more in the future.
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. ...
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...
I have read tens of thousands of pages on these subjects. I will be touching on this subject a great deal in my channel, UML Operator . We tend to use "Features" and "Capabilities" a lot, but don't necessarily understand what they mean. I see this in scope documents, and it is sometimes clear that folks are confused or confusing. I once saw on Quora, A capability is the ability to do something , normally it is provided by the infrastructure of the software system and makes features possible. The author was not using it in the sense of a high level possible goal to be achieved using the system, but rather as an enabler that makes features and high level possible goals capable of being accomplished through their existence. In other words I am not using the term here as a collection of features that might be used to achieve something. That is another meaning of the term. As for feature, a feature is something that the system does that is visible to the user an...
Comments
Post a Comment