This session will delve into the step-by-step information gathering process and technical analysis that goes in to crafting an enterprise data model. Taxonology is where taxonomy modeling theory meets technology - and the sparks fly!

1. Taxonology
An Object-Oriented Approach to Taxonomy Design Gene Stakhov

2. Source: Frederic Fortier, Eugene Stakhov

3. Enterprise Data:
Ecosystems and Taxonomies

4. Enterprise Data:
Information Governance
Source: Information Governance Reference Model (IGRM)
http://www.edrm.net

5. Data Silo Epidemic

6. “The hierarchical classification of entities of interest
of an enterprise, organization or administration,
used to classify documents, digital assets and other
information”
-Wikipedia (Corporate Taxonomy)

7. Taxonomy

8. Object-Oriented Programming

10. Objects and Classes
• Objects are derived from classes
• Classes contain properties
• Classes can have one or more
subclasses

11. Objects and Classes
• Objects are derived from classes
• Classes contain properties
• Classes can have one or more
subclasses
{encapsulation,
instantiation,
inheritance,
specialization,
polymorphism,
canonicalization};
Taxonology:=

12. First Name: Eugene
Nickname: Gene
Last Name: Stakhov
Eye Color: Grey
Hair Color: {system: undefined error}
TIN: 123-45-6789
… …
Object: Properties:

13. Example
Loan Document
metadata security

14. Example
Loan Document
Loan Base Class
inheritance
metadata security
Loan Subclass 1 Loan Subclass 2
lifecycle
: abstract class

15. Sample Taxonomy

16. Design Styles
• Content-Centric
• Organizational
• Functional

17. Content-Centric Design

18. Organizational Design

19. Functional Design

20. Getting Started
Requirements Workshops
•Document characteristics (volume,
format, input)
•Organizational structure
•Process
•Security
•Retention
•Reporting

21. Getting Started
Tools and Techniques
• Questionnaire/Worksheet
• “Procs not docs”
• What are the documents that
start the process (i.e., input)?
• Who produces these documents?
• Data Dictionary and Glossary
• Document Matrix

22. Common Pitfalls
• Lean/Flexible
• Not all metadata is equal
• Used to search?
• Used for records/lifecycle
governance?
• Used for reporting?
• Used for workflow/process?
• Look for rigidity
• High-level properties can be data
typed liberally

23. Citizen Developers
“A citizen developer is a user who creates new
business applications for consumption by others
using development and runtime environments
sanctioned by corporate IT … today, end users
can build departmental, enterprise and even
public applications using shared services, fourth-
generation language (4GL)-style development
platforms and cloud computing services”
Source: Gartner, Citizen Developer Model

24. Eugene Stakhov, CRM, CDIA+
• Email: president@armanyc.org
• Phone: (909) CRM-GENE
Senior Solution Architect, IG
enChoice, Inc.
President
ARMA Metro NYC Chapter
crmgene @gstakhov