Principle: Apply expertise from other fields

  • Description
  • Diagram Context
  • <b>Statement</b><br/>A model <i>represent</i> a complex entity, i.e. an "organization".  This process of representing potentially touches upon concepts in semiotics, communication theory, and mathematics, while the science of organization has been addressed in cybernetics, systems thinking, and biology. Physically, the modelling tool is first and foremost a <i>database.</i> Any insights fro these fields should be embraced, not rejected.<br/><b>Impacts on Modeling</b><br/>Widen the boundaries of what it is "to model".  For example:<br/><ul>
    <li>Insofar a modeling tool is primarily a software application, then at very minimum, think in terms of human computer interaction (HCI) and user experience (UX) - "users" here being both modelers and end-user consumers.</li><li>As a database, what are the key principles and techniques for database administration, including information storage, irretrievability, and information lifecycle?</li><li>The model, insofar as it is - or creates - business\technical communication artefacts, then what information design techniques are required?</li></ul>
    <b>Wider Business Impacts</b><br/>The model must have some business purpose and that purpose is only realizable by adapting and deploying competencies and knowledge that goes beyond "business modeling". This also provides an opportunity for genuine collaboration and co-creation with the model's end users and stakeholders.<br/><br/>