Application components cooperate through named information flows and one shared data object In the Application Cooperation viewpoint every arrow names the information one component passes to another, so a missing arrow is a missing integration and two arrows carrying the same data mark a duplicated system.
Application components cooperate through named information flows and one shared data object
An ArchiMate 3.2 Application Cooperation viewpoint with two lanes of flat hairline cards. The front office lane holds the Connections portal, the CRM and the Billing engine. The back office lane holds the Meter data service, the Asset register and the GIS. Blue arrows carry named information up to the front office: meter reads, asset data and the network map. On the centre line a Connection application data object is written by the portal and read by the Asset register, shown by quieter neutral arrows. A legend names the two element types, application component and data object. From the ArchiMate 3.2 Specification, The Open Group.
Front office: faces the customer
Back office: runs the estate
Meter reads
Asset data
Network map
Writes
Reads
Connections portal Customer connection requests Channel for new connections CRM Tracks customer contacts System of engagement Billing engine Use of system charges Bills the metered demand Meter data service Collects half hourly reads Source of metered volumes Asset register Master record of plant Source of truth for assets GIS Network geography and maps Where the assets sit Connection application Shared by front and back office Data object Application component Data object Derived from the ArchiMate 3.2 Specification, The Open Group
