From a method viewpoint, it is a good idea to have a dedicate “top level concept” for process maps. This shall apply for value-streams, organizational processes and system processes. It nicely fits with the existing “Top level Maps” available in HOPEX on Capabilities, Systems and Information. We are currently looking at introducing such a feature. On your side, what additional value would you see by adding this feature? Antoine
... View more
Hi, >We are thinking of using the Application Service object and adding a stereotype "API". > Well, this a hack when using HOPEX without the SOIA module. The "Application Service" concept aims at representing an internal component of an application. In moderm application architectures, this could be a servlet, a java class or a .NET Class, considered from a functional viewpoint, without their technical details. In mainframe application architectures, an "Application Service" would be the functional view of a batch program or a COBOL program. As, by definition, an API is the external part of an application, "Application Service" is not the appropritate candidate. During the last decade, HOPEX has integrated a new set of concepts aiming at representing APIs. These are the Exchange Contact/Exchange concepts along with their exposure withi applications structures: service points and request points. They provide a flow based approach for APIs. This approach also fits with the flow based approach taken by BPMN and HOPEX. Following that route, it is even possible to produce swagger like documentation, directly from HOPEX models (see attached document). However, there is a challenge in transitionning from traditionnal application architecture thinking to modern modular architecture principles. MEGA is providing a training along with the SOAI module to gather those principles. We warmly recommand that you follow it.
... View more