Software

softwareWould you build or purchase a house that does not have a Blueprint? It is not uncommon for enterprises to build or buy Software Applications without first having a discussion about the underlying information that the Software Applications are intended to address. As numerous Applications are introduced into an enterprise’s environment, there may be numerous dissimilar databases, multiple data models, or no data models at all.

When individuals use these Software Applications, they perform the work within that specific Software Application’s ‘bubble’. This is how the ‘Silo-Effect’ takes shape in a given environment (select the ‘CBL Taxonomy’ item on the website Methodology page for an explanation of the ‘Silo-Effect’). Data Stewards and Data Architects can manage this process by establishing a Common Business Language Taxonomy (Figure 1) and a Decision Support Data Model (Figure 2) that reflects the language of the business across Organizational Units.

 

insurance

Figure 1. Common Business Language Taxonomy example

insurance-case

Figure 2. Insurance Case Management Data Model example

THE GITS METHODOLOGY EXPEDITES SOFTWARE IMPLEMENTATIONS & MITIGATES THE SILO-EFFECT
GITS can provide you with resources and training/training materials to show you how to use the Common Business Language Taxonomy (Figure 1) and its associated Taxonomy narrative to develop the Decision Support Data Model (Figure 2). The Decision Support Data Model can then be used to as a ‘Blueprint’ for developing or purchasing software.

GITS can provide you with resources and training/training materials to show you the role of Data Governance, which includes conducting ‘Handshakes’ with the End Users to ascertain the needs of the business. We can train your Data Stewards on how to develop the Common Business Language Taxonomy Pallet that will be sustainable regardless of the Software Implementation. Once the Common Business Language Taxonomy Palette is agreed upon, Data Governance can execute another ‘Handshake’ with Data Architecture to develop a Decision Support Data Model. This approach is more expeditious than the Business Requirements/Technical Specification narratives that are normally developed within the Software Development Life Cycle.

The Common Business Language Taxonomy Pallets and the Decision Support Data Models can be maintained whether Software Applications are developed in-house or purchased off the shelf. In fact, they can be used collectively to perform Gap Analysis activities to ensure that the End User needs have been met by candidate Software solutions. It is not uncommon for the software landscape to change as corporations extended geographical boundaries or mergers take place. As the software landscape changes, the Taxonomy Pallets and Data Models will ensure that your enterprise’s Common Business Language is used consistently.