Successful implementation of Enterprise Architect - 28.05.2016
written by Avishay Leibenson, CEO of Panda Tech
Implementation of Stage A in the Enterprise Architect implementation project in a large security organization in Israel:
A few months ago we began implementing SPARX Enterprise Architect implementation project in a large security organization. The work began after a long process of examination by the managers of the organization, whether they are going on and proceed and what is required of them in order to succeed. There were moments of crisis in the process and points in which we already thought it would not work because processes of change in organizations are processes that require leadership and initiative from opinion leaders in the organization and a strong desire to bring about change.
Panda-Tech's vision is Same Tools - Same Language, meaning that we strive for a development organization to work with the same tools throughout the development process, creating a common language among all the people involved in the development of the project. The main problem is that projects experience a lack of synchronization between the various entities, and there is an ongoing preoccupation with writing documents in various formats, especially frustration of not meeting customer goals. Our method is based on the simple idea - the whole project is implemented through visual models. In other words, no more documents in complicated formats, but real engineering work with one tool for all-and-all.
From the moment of starting it was decided on four main models developed in this organization:
Operational Modeling - This is a visual model by which the operational system is designed. In other words, there is no reference to the technological side of the system, but to the operating side of the system, how the system will be used in the future, what the interfaces will be between the various functionaries and what entities will be managed. This is a stage that represents agreement with the customer and explains how the system will integrate at the operational level.
System Modeling - This is a visual model that represents system engineering and derives from the operational model. The model includes the system requirements, the system architecture and its various components, the system interfaces and processes, and the system data model. This model is not a technical model but rather a solution to engineering and system design. Here the system is practically planned.
Technological Modeling - This is a visual model that describes the technical operation of the system and how it works at the technical level. This model is derived from the previous model - the system model.
Modeling tests - This is a visual model that is already being implemented in the engineering modeling phase, since the design of the tests and the test environments is carried out at an early stage. At this stage, we must decide what the system's test requirements are, what the required test equipment is, what the simulators and emulators are, what the required testing environments are. It is also necessary to plan where each requirement will be examined, in what manner and by what method of proof. All this is done using the testing model, which is an important and essential part of the modeling process.
The four building blocks set together constitute a holistic approach defined by the OMG (Object Management Group) called MBSE.
The meaning of the name is Model Base System Engineering, is system-based engineering models. The leading idea - a series of linked models instead of a series of documents that have nothing to do with management.
"The current project takes only a few months but already has clear results for the customer," said the chief system engineer during a systematic survey conducted by several project managers in the organization.
"My feeling is that you type fewer texts using the Panda Tech solution, we are less busy with formats and documents and a lot of time is saved as a result, we are now doing a lot more engineering and design, A large part of the document is no longer relevant, and whoever goes back would fix the document, in a Panda Tech solution, everything is linked, so once you change one thing, you see its context and update accordingly. "
We are proud to be a significant part of leading change in organizations. We are aware of the complexity of the processes and the complexity of implementation, but the alternative is clear and has been tried for too many years. Our mission is to transfer as many organizations as possible from a series of unrelated documents to the ability to manage a series of connected visual models on a single, manageable technological infrastructure.