Welcome to a new episode of your favorite podcast. The topic of today is to capture and import the vast amounts of existing content in your organization, and how to integrate this into your repository. The import is one of the four major steps of an architecture tool implementation that we discussed in Episode 3. Why bringing in existing content? Concerns: age of content, correctness, type of storage (project vs. Enterprise Baseline), integration into dev method/SDLC, document naming/versioning Size of import: number of models and complexity drive effort Content format: how to map the information to models, objects, attributes Create catalog of to-be-imported content (> Notion) Five phases of import: preparation, initial import, create new model, normalization, quality assurance Preparation: catalog, database setup, filter/permission considerations, tool mapping (Visio), tracking and reporting Initial import: detailed look at what to import; automatically or manually import, use catalog for tracking, issues when importing Create new models: BPMN Collaboration example, merge between different databases Normalization: where does content go into structure (subprocesses, catalog models, etc.), object consolidation, adapting models to "correct" layout/standards (such as object naming) QA: modeler QA vs. central QA, semantic checks, macros, automated workflows; release and publish, communication Please reach out to us by either sending an email to [email protected] or leaving us a voice message by clicking here. The full show notes, including graphics, further links, credits, and transcript, are available at whatsyourbaseline.com/episode7.

Ask this episode

“What did the council decide on item 42?” — answered with the speaker and the moment.

Transcript

Related