title: Loose coupling among objects within oracle schema
body: <p>I am building an information service that manages Suppliers.
  The suppliers are used by our billing system, tender system and sales system. 
  Though 60% of the attributes of supplier are unique to each system, there are still 40% attributes of Supplier that are shared across the systems. </p>
  
  <p>My objective is to build a flexible system, so that change to one individual system's data, should not impact other systems. For example, if i need to make certain tables offline for upgrading them, it should not impact rest of the systems that need supplier information. 
  What is the best way of achieving this? Should all the different context specific attributes live in one schema, but deployed on different table spaces? 
  Also, the read and update may happen more for one set of attributes than the other. How should i logically represent them via one model, but deploy them in such a fashion that they can evolve independently? </p>
  
  <p>Thank you. </p>