Objects should be generic, with roles

Today, we have object types:

• Element
• Server
• Client
• Process
• Asset
• Lambda

It seems that a Server, Client, and Lambda are all specializations of Process or Asset, and really represent the "role" of each; role is really determined by the specific use - a server is the sink for a dataflow, the source is a client. But when describing an object, until the dataflows are determined, why force users to know ahead of time which one they need? Also, a client or server may be a server or a client, based on other data flows...

An alternative suggestion: create a generic "node" (Asset may be the right object already available), and allow assignment of properties that are generic. If roles are needed, assigning a role may add attributes specific to the role(s) added at runtime.
This approach helps with constructing models based on less-than-perfect knowledge of the system.

Start by reviewing how the existing Element, Server, Client, Process, Asset, and Lambda object types are defined and used. The work is complete when objects can be created generically and roles can be assigned at runtime with any role-specific attributes they require.