Skip to content

Strategic design approach using semantics and best practice

Cyber Security, Enterprise Architecture and Evidence Based Practice

  • Home
  • About me
  • Useful Links
  • Video clips

Category: IEEE1471

Using controlled vocabularies and semantics to improve Enterprise Architecture repositories – principle 5

April 21, 2011February 21, 2016 by Tolosa, posted in Content Authoring, Controlled Vocabulary, Evidence, Evidence Based Enterprise Architecture, Frameworks, Glossary, IEEE1471, Semantic

One of the recommendations of IEEE 1471 (the standard for describing the architecture of a software-intensive system) is to establish a conceptual framework and vocabulary for talking about architectural issues of systems. To provide a definition of what controlled vocabularies are and why they should be used i refer to Wikipedia and the following quote:

In organizations, controlled vocabularies may be introduced to improve technical communication. The use of controlled vocabulary ensures that everyone is using the same word to mean the same thing. This consistency of terms is one of the most important concepts in technical writing and knowledge management, where effort is expended to use the same word throughout a document or organization instead of slightly different ones to refer to the same thing.

Both enterprise architecture and evidence based activities benefit greatly from a controlled vocabulary. By creating and agreeing on a controlled set of terms, and the meaning behind the terms, helps readers understand commonality and relationships across document sets that support projects, processes, policies and strategies etc. and therefore a greater understanding of what the document is trying to say.

Where evidence is used to support enterprise artefacts and documentation the use of controlled vocabulary helps ensure that the evidence is understood and bears meaning to the hypotheses and recommendations it is supporting.

Tagged Content Authoring, Decision Making, Evidence Based Enterprise Architecture, Information Management, ValueLeave a comment

Recent Posts

  • Business and Threat Assessments
  • Drivers, Goals, Objectives, Constraints and Concerns
  • Preparation for a cyber security strategy
  • A cyber security strategy, use case by use case.
  • The naked business…

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Categories

  • CERT (2)
  • Cyber Defence (7)
    • Cyber Defence Ontology (4)
    • Vulnerability Management (1)
  • Cyber Security (3)
  • Cyber Security Ontology (1)
  • Cyber Security Strategy (3)
  • Enterprise Architecture (41)
    • Architectural Statement of Work (1)
    • Business Strategy (10)
    • Enterprise Architecture Ontology (4)
    • Enterprise Architecture Repository (4)
    • Evidence Based Enterprise Architecture (30)
      • EBEA (6)
    • IEEE1471 (1)
    • TOGAF (3)
  • Enterprise Ontology (3)
  • Evidence (19)
    • Evidence Ontology (9)
  • Frameworks (6)
  • Information Management (7)
    • Content Authoring (1)
    • Controlled Vocabulary (2)
    • DITA (1)
    • Docbook (1)
    • Glossary (1)
  • Metadata (1)
  • Ontology (4)
    • OWL (2)
  • Principles (3)
  • Research (4)
  • RISK (1)
  • SABSA (1)
  • Semantic (5)
    • RDF (2)
  • Service Management (3)
    • ITIL (1)
    • ITIL Ontology (2)
  • strategy (1)
  • Threat (3)
    • Threat Actor (2)
  • Uncategorized (2)
  • Value (3)
    • Value Assurance (2)
  • XML (1)
    • XML Authoring (1)

Blogroll

  • Enterprise Irregulars
  • evidence soup
  • Mike the Architect
  • Simplicable blog
  • WordPress.org

Meta

  • Register
  • Log in
  • Entries feed
  • Comments feed
  • WordPress.com
Website Powered by WordPress.com.
Cancel

 
Loading Comments...
Comment
    ×
    Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
    To find out more, including how to control cookies, see here: Cookie Policy