| LCG purposes | Recognises a stakeholder with no concern |
|---|
| LCG purposes | Recognises a concern raised by no stakeholder |
|---|
| LCG purposes | Recognises a concern no viewpoint frames |
|---|
| LCG purposes | Recognises a viewpoint framing no concern |
|---|
| LCG purposes | Recognises a solution stated as a concern |
|---|
| LCG purposes | Recognises an architecture principle with no rationale or implications |
|---|
| LCG purposes | Recognises colliding architecture principles with no precedence |
|---|
| LCG purposes | Recognises a technology choice filed as a principle |
|---|
| LCG purposes | Recognises an architecture principle with no owner |
|---|
| LCG purposes | Recognises an architecture principle contradicting the data strategy |
|---|
| LCG purposes | Recognises a missing architecture stakeholder |
|---|
| LCG purposes | Recognises a viewpoint with no model kinds |
|---|
| LCG purposes | Resolves colliding architecture principles for their owners |
|---|
| LCG purposes | Rewrites a solution as the concern behind it |
|---|
| LCG purposes | Explains stakeholders, concerns and viewpoints |
|---|
| LCG purposes | Explains the architecture principle template |
|---|
| LCG purposes | Explains the alignment of architecture with the data strategy |
|---|
| LCG purposes | Recognises overlapping subject areas |
|---|
| LCG purposes | Recognises an entity in two subject areas |
|---|
| LCG purposes | Recognises a subject area with no system of record |
|---|
| LCG purposes | Recognises a subject area with two systems of record |
|---|
| LCG purposes | Recognises an application-named subject area |
|---|
| LCG purposes | Recognises an enterprise term with no entity |
|---|
| LCG purposes | Recognises a subject area with no owning domain |
|---|
| LCG purposes | Recognises a system of record not creating its data |
|---|
| LCG purposes | Recognises a subject-area definition defining nothing |
|---|
| LCG purposes | Recognises an enterprise entity with no glossary term |
|---|
| LCG purposes | Recognises a reporting store as system of record |
|---|
| LCG purposes | Recognises a wrong business-area alignment |
|---|
| LCG purposes | Redistributes an application-named subject area |
|---|
| LCG purposes | Explains the enterprise data model and its subject areas |
|---|
| LCG purposes | Explains the system of record |
|---|
| LCG purposes | Explains the BIAN service landscape |
|---|
| LCG purposes | Explains definitions distinguishing a concept |
|---|
| LCG purposes | Recognises an entity created in two applications |
|---|
| LCG purposes | Recognises an entity read with no creator |
|---|
| LCG purposes | Recognises an update outside the system of record |
|---|
| LCG purposes | Recognises a creator outside the system of record |
|---|
| LCG purposes | Recognises a data flow with no consumer |
|---|
| LCG purposes | Recognises a data flow into the system of record |
|---|
| LCG purposes | Recognises a deletion not reaching the copies |
|---|
| LCG purposes | Recognises a flow of data its source does not hold |
|---|
| LCG purposes | Recognises an unknown application in the matrix |
|---|
| LCG purposes | Recognises a broken data value chain |
|---|
| LCG purposes | Recognises a data flow with no frequency or pattern |
|---|
| LCG purposes | Recognises a circular data flow |
|---|
| LCG purposes | Raises a double creation as a business decision |
|---|
| LCG purposes | Explains reading a CRUD matrix by entity |
|---|
| LCG purposes | Explains data flows and the data value chain |
|---|
| LCG purposes | Recognises a decision with no alternatives |
|---|
| LCG purposes | Recognises a decision with only positive consequences |
|---|
| LCG purposes | Recognises a silent reversal of a decision |
|---|
| LCG purposes | Recognises a principle violated without exception |
|---|
| LCG purposes | Recognises a placement contradicting the system of record |
|---|
| LCG purposes | Recognises an accepted decision with open questions |
|---|
| LCG purposes | Recognises a decision record with no context |
|---|
| LCG purposes | Recognises a placement citing a superseded decision |
|---|
| LCG purposes | Recognises a placement with no decision |
|---|
| LCG purposes | Recognises a subject area with no target placement |
|---|
| LCG purposes | Recognises an accepted decision with no decider |
|---|
| LCG purposes | Recognises a decision outside its options |
|---|
| LCG purposes | Links a reversing decision to the one it reverses |
|---|
| LCG purposes | Explains architecture decision records |
|---|
| LCG purposes | Explains principle exceptions |
|---|
| LCG purposes | Explains the traceability of target placements |
|---|
| LCG purposes | Recognises a forward dependency in a roadmap |
|---|
| LCG purposes | Recognises a transition state with no exit criteria |
|---|
| LCG purposes | Recognises a work package realising nothing |
|---|
| LCG purposes | Recognises a target element no package reaches |
|---|
| LCG purposes | Recognises decommissioning before the consumers move |
|---|
| LCG purposes | Recognises parallel changes to one system of record |
|---|
| LCG purposes | Recognises a work package with no owner |
|---|
| LCG purposes | Recognises transition states out of order |
|---|
| LCG purposes | Recognises a package realising a superseded decision |
|---|
| LCG purposes | Recognises an unmeasurable exit criterion |
|---|
| LCG purposes | Recognises a dependency on an unknown package |
|---|
| LCG purposes | Resequences decommissioning after the consumers move |
|---|
| LCG purposes | Explains transition architectures and work packages |
|---|
| LCG purposes | Explains roadmap dependency and decommissioning order |
|---|
| LCG purposes | Explains the business drivers of data architecture |
|---|
| LCG purposes | Explains the enterprise architecture domains |
|---|
| LCG purposes | Explains enterprise architecture frameworks |
|---|
| LCG purposes | Explains data architecture tools |
|---|
| LCG purposes | Explains lifecycle projections |
|---|
| LCG purposes | Explains clear architecture diagrams |
|---|
| LCG purposes | Explains data architecture readiness and risk assessment |
|---|
| LCG purposes | Explains organisational change for data architecture |
|---|
| LCG purposes | Explains data architecture governance and metrics |
|---|
| LCG purposes | Recognises a record class named after a system |
|---|
| LCG purposes | Recognises overlapping record classes |
|---|
| LCG purposes | Recognises a record type in no class |
|---|
| LCG purposes | Recognises a record class with no owner |
|---|
| LCG purposes | Recognises a record class mixing different retention |
|---|
| LCG purposes | Recognises records in a system their class does not list |
|---|
| LCG purposes | Recognises a record class defined by format |
|---|
| LCG purposes | Recognises a record type placed in two classes |
|---|
| LCG purposes | Reclassifies records by business activity |
|---|
| LCG purposes | Splits a record class by retention |
|---|
| LCG purposes | Places every record type in exactly one class |
|---|
| LCG purposes | Explains records classification by business activity |
|---|
| LCG purposes | Explains the records inventory |
|---|
| LCG purposes | Explains retention as a property of a record class |
|---|
| LCG purposes | Recognises a retention period with no trigger |
|---|
| LCG purposes | Recognises a retention trigger no system records |
|---|
| LCG purposes | Recognises conflicting retention periods with no precedence |
|---|
| LCG purposes | Recognises a retention basis not covering the class |
|---|
| LCG purposes | Recognises disposition with no legal-hold check |
|---|
| LCG purposes | Recognises permanent retention with no reason |
|---|
| LCG purposes | Recognises a retention trigger contradicting its basis |
|---|
| LCG purposes | Recognises disposition with no approver |
|---|
| LCG purposes | Names the trigger event a retention provision sets |
|---|
| LCG purposes | Sources a retention trigger to a recorded date |
|---|
| LCG purposes | Resolves conflicting retention periods |
|---|
| LCG purposes | Cites retention periods only from the provisions given |
|---|
| LCG purposes | Explains retention trigger events |
|---|
| LCG purposes | Explains where retention trigger dates come from |
|---|
| LCG purposes | Explains retention regimes for bank records |
|---|
| LCG purposes | Explains disposition authorisation |
|---|
| LCG purposes | Recognises a mandatory metadata element its capturer cannot know |
|---|
| LCG purposes | Recognises a retention trigger missing from the metadata |
|---|
| LCG purposes | Recognises free text where a vocabulary is needed |
|---|
| LCG purposes | Recognises duplicate metadata elements |
|---|
| LCG purposes | Recognises personal data in a widely visible metadata element |
|---|
| LCG purposes | Recognises a metadata element with no definition |
|---|
| LCG purposes | Recognises records with no link to their class |
|---|
| LCG purposes | Recognises a standard metadata element used against its meaning |
|---|
| LCG purposes | Adds the metadata element a retention trigger needs |
|---|
| LCG purposes | Sets a metadata element where its capturer can know it |
|---|
| LCG purposes | Uses standard metadata elements for their meaning |
|---|
| LCG purposes | Explains records metadata |
|---|
| LCG purposes | Explains how metadata is obtained at capture |
|---|
| LCG purposes | Explains personal data in metadata |
|---|
| LCG purposes | Explains Dublin Core elements |
|---|
| LCG purposes | Recognises disposition suspended in one system only |
|---|
| LCG purposes | Recognises a legal hold with no release |
|---|
| LCG purposes | Recognises a hold scoped by system only |
|---|
| LCG purposes | Recognises hold custodians not notified |
|---|
| LCG purposes | Recognises collection with no chain of custody |
|---|
| LCG purposes | Recognises a hold with no applied date |
|---|
| LCG purposes | Recognises imminent deletion of data under hold |
|---|
| LCG purposes | Recognises a hold with no matter or decision-maker |
|---|
| LCG purposes | Suspends every disposition path in a hold's scope |
|---|
| LCG purposes | Stops an imminent deletion of held data as urgent |
|---|
| LCG purposes | Explains preservation under a legal hold |
|---|
| LCG purposes | Explains the legal hold process |
|---|
| LCG purposes | Explains chain of custody for digital evidence |
|---|
| LCG purposes | Recognises a record editable after declaration |
|---|
| LCG purposes | Recognises views of restricted records not logged |
|---|
| LCG purposes | Recognises disposition without evidence |
|---|
| LCG purposes | Recognises record versions overwritten |
|---|
| LCG purposes | Recognises a repository with no declaration point |
|---|
| LCG purposes | Recognises repository access not by class |
|---|
| LCG purposes | Locks declared records and links their corrections |
|---|
| LCG purposes | Records disposition with a certificate |
|---|
| LCG purposes | Proposes a preservation format only where retention needs it |
|---|
| LCG purposes | Explains the characteristics of records |
|---|
| LCG purposes | Explains the audit trail of a records repository |
|---|
| LCG purposes | Explains long-term digital preservation |
|---|
| LCG purposes | Explains the drivers of document and content management |
|---|
| LCG purposes | Explains the content lifecycle and content types |
|---|
| LCG purposes | Explains vital records and business continuity |
|---|
| LCG purposes | Explains the Generally Accepted Recordkeeping Principles |
|---|
| LCG purposes | Explains content architecture: taxonomies, ontologies and search |
|---|
| LCG purposes | Explains publishing and delivering content |
|---|
| LCG purposes | Explains auditing records management |
|---|
| LCG purposes | Explains DCM tools |
|---|
| LCG purposes | Explains information governance for content |
|---|
| LCG purposes | Recognises an orphan strategy goal |
|---|
| LCG purposes | Recognises an invented business objective |
|---|
| LCG purposes | Recognises an unmeasurable strategy goal |
|---|
| LCG purposes | Recognises an activity stated as a strategy goal |
|---|
| LCG purposes | Recognises a strategy goal with no owner |
|---|
| LCG purposes | Recognises a strategy goal no initiative serves |
|---|
| LCG purposes | Recognises an initiative serving no goal |
|---|
| LCG purposes | Recognises an initiative ending after its goal |
|---|
| LCG purposes | Recognises a data principle forbidding nothing |
|---|
| LCG purposes | Recognises a data principle with no owner |
|---|
| LCG purposes | Recognises a data principle with no rationale or implications |
|---|
| LCG purposes | Recognises colliding data principles with no precedence |
|---|
| LCG purposes | Recognises a standard or technology choice filed as a principle |
|---|
| LCG purposes | Recognises duplicate data principles |
|---|
| LCG purposes | Recognises a data principle contradicting a strategy goal |
|---|
| LCG purposes | Recognises a scope gap in the data strategy |
|---|
| LCG purposes | Recognises a proposed object presented as agreed |
|---|
| LCG purposes | Rewrites an activity goal as a measurable outcome |
|---|
| LCG purposes | Rewrites a value statement as a principle forbidding something |
|---|
| LCG purposes | Resolves colliding principles by narrowing or precedence |
|---|
| LCG purposes | Explains the evaluate-direct-monitor model of data governance |
|---|
| LCG purposes | Explains measurable outcome goals |
|---|
| LCG purposes | Explains the structure of a data principle |
|---|
| LCG purposes | Explains traceability from initiatives to goals to business objectives |
|---|
| LCG purposes | Explains the kinds of rules binding an organisation's data and where they are published |
|---|
| LCG purposes | Judges a business term definition by genus and differentia |
|---|
| LCG purposes | Recognises a data domain with no owner |
|---|
| LCG purposes | Recognises a data domain with two owners |
|---|
| LCG purposes | Recognises a business term owned by two domains |
|---|
| LCG purposes | Recognises a business term owned by no domain |
|---|
| LCG purposes | Recognises a custodian as a domain owner |
|---|
| LCG purposes | Recognises a decision type with no or two deciders |
|---|
| LCG purposes | Recognises a decision type with no escalation path |
|---|
| LCG purposes | Recognises an escalation going down or round |
|---|
| LCG purposes | Recognises an escalation to a body unable to decide it |
|---|
| LCG purposes | Recognises a RACI row with no or several accountable roles |
|---|
| LCG purposes | Recognises a RACI row contradicting the decision rights |
|---|
| LCG purposes | Recognises accountability without authority |
|---|
| LCG purposes | Recognises a vacant role held accountable |
|---|
| LCG purposes | Recognises approval and implementation in one person |
|---|
| LCG purposes | Recognises a governance body with no mandate |
|---|
| LCG purposes | Recognises a governance body missing the owners it decides about |
|---|
| LCG purposes | Recognises a governance body with no reporting line |
|---|
| LCG purposes | Recognises a decision type in two bodies' mandates |
|---|
| LCG purposes | Recognises a steward with nothing to steward |
|---|
| LCG purposes | Moves accountability to the role with authority |
|---|
| LCG purposes | Explains data governance roles and bodies |
|---|
| LCG purposes | Explains decision rights and the escalation ladder |
|---|
| LCG purposes | Explains the single-accountable rule of a RACI |
|---|
| LCG purposes | Explains the authority behind accountability |
|---|
| LCG purposes | Explains segregation of duties |
|---|
| LCG purposes | Explains data domains and term ownership |
|---|
| LCG purposes | Recognises a policy written as a procedure |
|---|
| LCG purposes | Recognises a policy with no scope |
|---|
| LCG purposes | Recognises a policy implementing no principle |
|---|
| LCG purposes | Recognises a policy with no standard |
|---|
| LCG purposes | Recognises a policy with no owner or review date |
|---|
| LCG purposes | Recognises a policy with no exception route |
|---|
| LCG purposes | Recognises an exception authority contradicting the decision rights |
|---|
| LCG purposes | Recognises a standard serving no policy |
|---|
| LCG purposes | Recognises a recommendation written as a standard |
|---|
| LCG purposes | Recognises a standard with no verification |
|---|
| LCG purposes | Recognises a standard naming a tool |
|---|
| LCG purposes | Recognises a procedure meeting no standard |
|---|
| LCG purposes | Recognises a procedure unable to meet its standard |
|---|
| LCG purposes | Recognises conflicting data policies |
|---|
| LCG purposes | Recognises conflicting data standards |
|---|
| LCG purposes | Recognises a policy exception with no expiry |
|---|
| LCG purposes | Recognises a policy exception granted without authority |
|---|
| LCG purposes | Recognises a policy approved outside the operating model |
|---|
| LCG purposes | Recognises a stale data policy |
|---|
| LCG purposes | Separates procedure steps from a policy |
|---|
| LCG purposes | Rewrites a recommendation as a verifiable requirement |
|---|
| LCG purposes | Explains policies, standards and procedures as distinct instruments |
|---|
| LCG purposes | Explains the verbal forms of requirements |
|---|
| LCG purposes | Explains how compliance with a standard is verified |
|---|
| LCG purposes | Explains policy exceptions and their lifecycle |
|---|
| LCG purposes | Explains conflicts between policies with overlapping scope |
|---|
| LCG purposes | Recognises a regulatory principle with no control |
|---|
| LCG purposes | Recognises a regulatory principle dropped without reason |
|---|
| LCG purposes | Recognises a control with no evidence |
|---|
| LCG purposes | Recognises control evidence owned by nobody |
|---|
| LCG purposes | Recognises stale control evidence |
|---|
| LCG purposes | Recognises a control tested for design only |
|---|
| LCG purposes | Recognises a control mapped to a principle it cannot address |
|---|
| LCG purposes | Recognises a manual step outside the control matrix |
|---|
| LCG purposes | Recognises a control operating no internal standard |
|---|
| LCG purposes | Recognises a control owner without authority over the process |
|---|
| LCG purposes | Recognises a control in self-review |
|---|
| LCG purposes | Recognises a control slower than the report it protects |
|---|
| LCG purposes | Recognises automation evidenced by a manual artefact |
|---|
| LCG purposes | Recognises a control covering part of the report's population |
|---|
| LCG purposes | Recognises a reference to a principle outside the scope |
|---|
| LCG purposes | Designs a control over a manual adjustment |
|---|
| LCG purposes | Explains design and operating effectiveness of controls |
|---|
| LCG purposes | Explains control evidence and its currency |
|---|
| LCG purposes | Explains manual steps in report production as a control risk |
|---|
| LCG purposes | Explains the attributes of a control |
|---|
| LCG purposes | Recognises a governance issue with no owner |
|---|
| LCG purposes | Recognises an issue owner without the decision right |
|---|
| LCG purposes | Recognises an unrouted governance issue |
|---|
| LCG purposes | Recognises an issue escalated past the level with authority |
|---|
| LCG purposes | Recognises an issue routed below the level with authority |
|---|
| LCG purposes | Recognises a decision with no decider recorded |
|---|
| LCG purposes | Recognises a decision taken without the decision right |
|---|
| LCG purposes | Recognises an issue closed with no decision |
|---|
| LCG purposes | Recognises an issue closed with no verification |
|---|
| LCG purposes | Recognises duplicate governance issues |
|---|
| LCG purposes | Recognises a decision against a policy with no exception |
|---|
| LCG purposes | Recognises an issue severity with no impact |
|---|
| LCG purposes | Recognises a complaint logged as an issue |
|---|
| LCG purposes | Recognises a decision not written back to its deliverable |
|---|
| LCG purposes | Recognises a definition dispute citing no terms |
|---|
| LCG purposes | Routes a governance issue to the decider of its decision type |
|---|
| LCG purposes | Raises a decision for its owner instead of taking it |
|---|
| LCG purposes | Explains routing governance issues to the lowest level with authority |
|---|
| LCG purposes | Explains the governance issue lifecycle |
|---|
| LCG purposes | Recognises an activity count presented as an outcome |
|---|
| LCG purposes | Recognises a governance metric with no target |
|---|
| LCG purposes | Recognises a governance metric with no owner |
|---|
| LCG purposes | Recognises a governance metric with no source |
|---|
| LCG purposes | Recognises a metric target with no rationale |
|---|
| LCG purposes | Recognises a metric measuring no goal |
|---|
| LCG purposes | Recognises a strategy goal no metric measures |
|---|
| LCG purposes | Recognises a metric whose direction cannot be read |
|---|
| LCG purposes | Recognises a metric source unable to produce it |
|---|
| LCG purposes | Recognises a metric target inconsistent with its goal |
|---|
| LCG purposes | Recognises an impossible metric reading |
|---|
| LCG purposes | Recognises duplicate governance metrics |
|---|
| LCG purposes | Replaces an activity metric with an outcome metric |
|---|
| LCG purposes | Replaces an unreadable metric direction with readable metrics |
|---|
| LCG purposes | Explains outcome, control and activity metrics |
|---|
| LCG purposes | Explains metric direction |
|---|
| LCG purposes | Explains the definition of a measure and its population |
|---|
| LCG purposes | Explains targets and their rationale |
|---|
| LCG purposes | Explains the business drivers and goals of data governance |
|---|
| LCG purposes | Explains the data-centric organisation and its governance bodies |
|---|
| LCG purposes | Explains centralised, replicated and federated operating models |
|---|
| LCG purposes | Explains the types of data stewards |
|---|
| LCG purposes | Explains data asset valuation |
|---|
| LCG purposes | Explains data governance readiness assessment |
|---|
| LCG purposes | Explains the organisational touch points of data governance |
|---|
| LCG purposes | Explains change management for data governance |
|---|
| LCG purposes | Explains the business glossary as a governance tool |
|---|
| LCG purposes | Explains coordination with architecture groups |
|---|
| LCG purposes | Explains data governance tools |
|---|
| LCG purposes | Explains embedding data governance in the organisation's culture |
|---|
| LCG purposes | Recognises a modelling scope with no boundary |
|---|
| LCG purposes | Recognises a modelling standard named but not chosen |
|---|
| LCG purposes | Recognises a model layer planned with no notation |
|---|
| LCG purposes | Recognises model inputs the plan does not locate |
|---|
| LCG purposes | Recognises a model review planned by its modeller |
|---|
| LCG purposes | Recognises a model with no repository or baseline |
|---|
| LCG purposes | Plans the deliverables of a modelling assignment |
|---|
| LCG purposes | Chooses a modelling scheme and notation for an audience and purpose |
|---|
| LCG purposes | Sets the modelling standards a project follows |
|---|
| LCG purposes | Selects the tools and repository for a modelling project |
|---|
| LCG purposes | Recognises an incomplete data model scorecard |
|---|
| LCG purposes | Recognises a scorecard score with no evidence |
|---|
| LCG purposes | Recognises a model reviewed by its modeller |
|---|
| LCG purposes | Recognises a review decision contradicting its total |
|---|
| LCG purposes | Recognises a review finding with no owner or action |
|---|
| LCG purposes | Recognises a scorecard score contradicting the validator |
|---|
| LCG purposes | Recognises a review of a version other than the one released |
|---|
| LCG purposes | Recognises a data requirement making several claims |
|---|
| LCG purposes | Recognises a data requirement prescribing a design solution |
|---|
| LCG purposes | Recognises a statement outside the scope of data requirements |
|---|
| LCG purposes | Scores a data model against the Data Model Scorecard |
|---|
| LCG purposes | Recognises an ambiguous business term in a data requirement |
|---|
| LCG purposes | Recognises untestable wording in a data requirement |
|---|
| LCG purposes | Recognises an unverifiable data requirement |
|---|
| LCG purposes | Recognises a reference with several possible referents |
|---|
| LCG purposes | Recognises a data requirement without a named subject |
|---|
| LCG purposes | Recognises a measure stated without unit or basis |
|---|
| LCG purposes | Recognises a data requirement silent on current versus past values |
|---|
| LCG purposes | Recognises an inferred structure presented as declared |
|---|
| LCG purposes | Recognises reverse-engineered objects not marked as-is |
|---|
| LCG purposes | Recognises a dead database object carried into the model |
|---|
| LCG purposes | Recognises a guessed meaning written as a definition |
|---|
| LCG purposes | Recognises a reverse-engineering source with no environment or date |
|---|
| LCG purposes | Recognises a physical workaround lifted into the logical model |
|---|
| LCG purposes | Recognises an absolute statement with its exception unasked |
|---|
| LCG purposes | Recognises a mandatory attribute without its moment of obligation |
|---|
| LCG purposes | Recognises a business rule left inside another statement |
|---|
| LCG purposes | Reverse-engineers a logical model from a database schema |
|---|
| LCG purposes | Recognises content filed under the wrong requirement |
|---|
| LCG purposes | Recognises an unsourced data requirement |
|---|
| LCG purposes | Recognises a missing or meaningless requirement priority |
|---|
| LCG purposes | Recognises a missing or wrong requirement type |
|---|
| LCG purposes | Recognises a status contradicting the requirement's content |
|---|
| LCG purposes | Recognises a guess recorded as fact |
|---|
| LCG purposes | Recognises a missing rationale for a non-obvious requirement |
|---|
| LCG purposes | Recognises a model change with no reason |
|---|
| LCG purposes | Recognises a model change with no impact analysis |
|---|
| LCG purposes | Recognises a breaking model change released as a minor version |
|---|
| LCG purposes | Recognises a change to a deployed structure with no migration |
|---|
| LCG purposes | Recognises a released model version with no baseline |
|---|
| LCG purposes | Recognises a model change released without approval |
|---|
| LCG purposes | Recognises duplicate data requirements |
|---|
| LCG purposes | Recognises paraphrased data requirements |
|---|
| LCG purposes | Recognises conflicting data requirements |
|---|
| LCG purposes | Releases a model change as a new model version |
|---|
| LCG purposes | Recognises inconsistent terminology across the register |
|---|
| LCG purposes | Recognises a requirements register with unbounded scope |
|---|
| LCG purposes | Recognises a requirements register describing no events |
|---|
| LCG purposes | Recognises an uncovered identity requirement |
|---|
| LCG purposes | Recognises an uncovered volume or retention requirement |
|---|
| LCG purposes | Recognises an uncovered sensitivity or access requirement |
|---|
| LCG purposes | Recognises an uncovered lineage requirement |
|---|
| LCG purposes | Recognises undecided history requirements across the register |
|---|
| LCG purposes | Recognises a requirements register serving no stated question |
|---|
| LCG purposes | Recognises a missing or wrong requirement trace |
|---|
| LCG purposes | Recognises unstable requirement identifiers |
|---|
| LCG purposes | Retires a superseded register entry instead of deleting it |
|---|
| LCG purposes | Explains singular and unambiguous requirement statements |
|---|
| LCG purposes | Distinguishes a business requirement from a design solution |
|---|
| LCG purposes | Explains the data requirement types of the register |
|---|
| LCG purposes | Explains requirement attributes and traceability |
|---|
| LCG purposes | Explains current value, history and point-in-time reproducibility |
|---|
| LCG purposes | Explains the identity of a business thing |
|---|
| LCG purposes | Explains the non-functional data concerns |
|---|
| LCG purposes | Explains the scope, events and questions a data register must state |
|---|
| LCG purposes | Explains referential and logical ambiguity in natural-language statements |
|---|
| LCG purposes | Explains persistent identifiers |
|---|
| LCG purposes | Explains verifiable requirement statements |
|---|
| LCG purposes | Explains consistency within a requirements register |
|---|
| LCG purposes | Explains intensional definition by superordinate concept and delimiting characteristics |
|---|
| LCG purposes | Explains generic and partitive concept relations |
|---|
| LCG purposes | Recognises a constraint claimed by a rule and missing from the schema |
|---|
| LCG purposes | Recognises a declared constraint the target platform does not enforce |
|---|
| LCG purposes | Explains SBVR fact types and rule statements |
|---|
| LCG purposes | Explains Witt's classification of business rules |
|---|
| LCG purposes | Explains rule enforcement mechanisms and platform enforcement |
|---|
| LCG purposes | Recognises an ambiguous node label |
|---|
| LCG purposes | Recognises a node with an unclear boundary and no scope note |
|---|
| LCG purposes | Recognises overlapping sibling nodes without reciprocal scope notes |
|---|
| LCG purposes | Recognises a meaning change without a history note |
|---|
| LCG purposes | Recognises a node without warrant |
|---|
| LCG purposes | Recognises inconsistent node label forms |
|---|
| LCG purposes | Recognises an abbreviation, jargon or system name as a node label |
|---|
| LCG purposes | Recognises a compound node combining two characteristics |
|---|
| LCG purposes | Recognises siblings divided by mixed characteristics |
|---|
| LCG purposes | Recognises a synonym kept as a separate node |
|---|
| LCG purposes | Recognises a link failing the all-and-some test |
|---|
| LCG purposes | Recognises an instance placed as a concept node |
|---|
| LCG purposes | Recognises a part-of link in a kind-of hierarchy |
|---|
| LCG purposes | Recognises an unjustified polyhierarchy |
|---|
| LCG purposes | Recognises an associative relationship shown as a hierarchy |
|---|
| LCG purposes | Recognises non-reciprocal hierarchy links |
|---|
| LCG purposes | Recognises uneven levels of specificity among siblings |
|---|
| LCG purposes | Recognises a home-grown copy of an existing vocabulary |
|---|
| LCG purposes | Deleted or reused node (taxonomy) |
|---|
| LCG purposes | Recognises a structural error in a taxonomy hierarchy |
|---|
| LCG purposes | Models a role as an association to the party playing it |
|---|
| LCG purposes | Derives the broader concept from the head of a definition |
|---|
| LCG purposes | Recognises a taxonomy node deleted while data still refers to it |
|---|
| LCG purposes | Recognises a node code reused for a different concept |
|---|
| LCG purposes | Explains hierarchical relations and the all-and-some test |
|---|
| LCG purposes | Explains scope notes and history notes |
|---|
| LCG purposes | Explains warrant for vocabulary terms |
|---|
| LCG purposes | Explains label form conventions for vocabularies |
|---|
| LCG purposes | Explains characteristics of division and node labels |
|---|
| LCG purposes | Explains equivalence relations and preferred terms |
|---|
| LCG purposes | Explains associative relations |
|---|
| LCG purposes | Explains reuse of external vocabularies |
|---|
| LCG purposes | Recognises an insertion anomaly in a logical data model |
|---|
| LCG purposes | Recognises an update anomaly in a logical data model |
|---|
| LCG purposes | Recognises a deletion anomaly in a logical data model |
|---|
| LCG purposes | Recognises a repeating group in an entity |
|---|
| LCG purposes | Recognises an attribute holding several facts |
|---|
| LCG purposes | Recognises an attribute with several meanings |
|---|
| LCG purposes | Recognises attributes held as name-value rows |
|---|
| LCG purposes | Recognises a partial dependency on a composite key |
|---|
| LCG purposes | Recognises a transitive dependency between non-key attributes |
|---|
| LCG purposes | Recognises a stored derivable attribute |
|---|
| LCG purposes | Recognises a non-superkey determinant in a 3NF entity |
|---|
| LCG purposes | Recognises independent multi-valued facts in one entity |
|---|
| LCG purposes | Recognises a join dependency kept in one entity |
|---|
| LCG purposes | Recognises a lossy decomposition |
|---|
| LCG purposes | Recognises a functional dependency lost in a decomposition |
|---|
| LCG purposes | Recognises attributes inapplicable to some instances |
|---|
| LCG purposes | Recognises an unstable or meaningful primary key |
|---|
| LCG purposes | Recognises an entity identified only by a system-assigned key |
|---|
| LCG purposes | Recognises undeclared subtype constraints |
|---|
| LCG purposes | Recognises independently changing histories in one entity |
|---|
| LCG purposes | Recognises an unresolved many-to-many relationship |
|---|
| LCG purposes | Recognises a polymorphic association |
|---|
| LCG purposes | Recognises a connection trap |
|---|
| LCG purposes | Recognises a fan trap |
|---|
| LCG purposes | Recognises a chasm trap |
|---|
| LCG purposes | Recognises a redundant relationship |
|---|
| LCG purposes | Recognises overlapping entities |
|---|
| LCG purposes | Recognises one entity split by value into several |
|---|
| LCG purposes | Recognises a relationship contradicting its data rule |
|---|
| LCG purposes | Recognises a constraint implied by neither keys nor domains |
|---|
| LCG purposes | Traces a logical-model anomaly to its structural cause |
|---|
| LCG purposes | Records the functional dependencies of an entity |
|---|
| LCG purposes | Decomposes an entity along a functional dependency without loss |
|---|
| LCG purposes | Resolves a many-to-many relationship into an associative entity |
|---|
| LCG purposes | Replaces a repeating group with a dependent entity |
|---|
| LCG purposes | Introduces subtypes for attributes applying to only some instances |
|---|
| LCG purposes | Explains functional dependency |
|---|
| LCG purposes | Explains candidate key and prime attribute |
|---|
| LCG purposes | Explains the insertion, update and deletion anomalies |
|---|
| LCG purposes | Explains first normal form |
|---|
| LCG purposes | Explains second normal form |
|---|
| LCG purposes | Explains third normal form |
|---|
| LCG purposes | Explains Boyce-Codd normal form |
|---|
| LCG purposes | Explains multivalued dependency and fourth normal form |
|---|
| LCG purposes | Explains join dependency and fifth normal form |
|---|
| LCG purposes | Explains sixth normal form for temporal data |
|---|
| LCG purposes | Explains domain-key normal form |
|---|
| LCG purposes | Explains attribute domains |
|---|
| LCG purposes | Explains lossless-join decomposition |
|---|
| LCG purposes | Explains dependency preservation |
|---|
| LCG purposes | Explains derived data and point-in-time snapshots |
|---|
| LCG purposes | Explains supertype and subtype constraints |
|---|
| LCG purposes | Explains relationship cardinality and optionality |
|---|
| LCG purposes | Explains natural keys, surrogate keys and key stability |
|---|
| LCG purposes | Explains the connection, fan and chasm traps |
|---|
| LCG purposes | Explains an entity type as the realisation of one business concept |
|---|
| LCG purposes | Expresses a logical model as a UML class diagram |
|---|
| LCG purposes | Models data as fact types in a fact-based scheme |
|---|
| LCG purposes | Maps an application model onto a canonical model |
|---|
| LCG purposes | Recognises an unmanaged duplicate column |
|---|
| LCG purposes | Recognises logical entities merged into one table |
|---|
| LCG purposes | Recognises a stored derived or summary value |
|---|
| LCG purposes | Recognises a lossy or unconstrained vertical split |
|---|
| LCG purposes | Recognises an entity split into clone tables by value |
|---|
| LCG purposes | Recognises rolled-up subtypes losing conditional constraints |
|---|
| LCG purposes | Recognises rolled-down subtypes losing supertype constraints |
|---|
| LCG purposes | Recognises a hierarchy encoded redundantly |
|---|
| LCG purposes | Recognises content held outside the database by reference |
|---|
10109 more in the RDF.