Figure L.16 - Implement using Pluggable Components

<font color="#e0121d"><b>Using this model for Process Analysis</b></font><br/><font color="#29313b">When using these entity definitions in process or use case analysis, the most useful entities will be </font><br/><ul>
<li><font color="#29313b">Geographic Address</font></li><li><font color="#29313b">Geographic sub address</font></li><li><font color="#29313b">Postal Delivery Address</font></li><li><font color="#29313b">Geographic Site & Role</font></li><li><font color="#29313b">and the concrete example Geographic Locations (Street, Property, Country, State …)</font></li></ul>
<font color="#29313b"><br/></font><font color="#29313b">If a generic term for “where?” is required and the answer could be an Address a defined Site or a Location, then the term Place should be used.</font><br/><font color="#29313b">In common language the Geographic / Local prefix is usually not used as it is assumed that it is clear from the context. During process analysis it is probably worthwhile to explicitly note this information. </font><br/><font color="#29313b">It will also be useful to note whether an address is a Postal Address or not.</font><br/><font color="#29313b">If more detailed entities are referenced, then they should be defined and related back to the entities in this model. e.g. “a Council Area is a type of Administrative Area that …”</font><br/><font color="#e0121d"><b>Model Implementation Using Components</b></font><br/><font color="#29313b">This model should not be implemented as a monolithic component, but in such a way that functionality can be plugged in as required.</font><br/><font color="#29313b">This is shown conceptually in fig 16</font><br/><font color="#29313b"><br/></font><font color="#29313b">Note that a Service Provider may need to have multiple standard sets plugged in at the one time.</font><br/>