@DMiddleton wrote: Hello, the System Used object allows a modeler to show that some sort of "System" is used or needed by the process. Yes you can connect the actual resources to the System Used BUT when modeling (especially a new process) you may not know what actual System, Application or other resource is that will be used. In that case the System Used can be named and helps show that some sort of system is required to perform that process. Hope that helps. Good day D and thanks for sharing. Please let me comment something additional. I will appreciate your insights about it. For me, who's used to model through direct relationships between main objects, it’s been hard to find real value in the usage of System Used as a type of object, instead of as a type of relationship. Worts yet because the representation of System Used is not uniform across key diagram types. For example, let’s consider an Organizational Process Diagram and an Application Usage Viewpoint Diagram. At the Application Usage Viewpoint Diagram, System Used is represented as a line, resembling a type of direct relationship between the two main objects. While at the Organizational Process Diagram, System Used is represented as a rounded box, with actual Applications (and Resources) listed below the box, depicting the true nature of System Used as an object type and container. Wouldn’t it be cleaner to model System Used as a type or relationship between Processes and Applications? What modeling value am I not seeing with the current definition, and polymorphism characteristic of System Used? Thanks again.
... View more
