As an Architect, why should I start with Labnaf?

I could use ArchiMate as long as

  • I had to deal only with simple or isolated architecture projects
  • Architecture outcomes, usefulness and costs were not much scrutinized nor understood

Today I need to switch from ArchiMate to Labnaf

  • I need enterprise visualization and continuous collaboration with a single language from idea to software in production
  • I need to enable re-use, reduce costs, optimize quality, optimize consistency, manage complexity and enable a focus on growth
  • I need a prefab vehicle to coordinate IT and business stakeholder efforts towards meaningful transformations and optimized business outcomes

In particular, my needs are:

Enterprise Visibility, Navigation and Portfolio Management

  • A scalable language for Application Portfolio Management (APM) that can manage complexity and separates levels of detail
  • Identify redundant, complex, critical, expensive, obsolete etc. applications, technologies and processes using automatic imports and automatic calculations
  • In the same way, BPM, information architecture and technology architecture modeling as part of the same scalable language
  • Model clouds (application and technology as a service), IoT and ecosystems

Content Optimization

  • Automatically import information periodically or on demand
  • Define initial value calculations when I create new elements
  • Define periodical value calculations. Ideally define these calculations using the same modeling language.
  • Generate diagrams automatically
    • to reduce time and costs,
    • and to get complete and consistent diagrams that are not dependent on the author.

Dashboards, Charts and Reports  (Periodically or On Demand)

  • Provide summary and C-level views using predefined and extendable charts and dashboards
  • Define tabular report templates (for Excel generation). Ideally define these templates using the same modeling language.
  • Provide detailed reports, including consolidated matrices, using Excel report generation
  • Generate principles and standards documents and re-use those in my RFPs
  • Generate solution architecture documents based on controlled model content

Goal-driven Target Capabilities Definition and Roadmapping

  • Institute demand and project planning that is aligned to strategy and to target capabilities roadmaps
  • Manage teams, assign domains and projects to individuals (all as models)
  • Automate model validation and automatically route model errors to assigned individuals

A transformation process expressed as a flow of viewpoints

  • Where each type of view (viewpoint) answers some defined and meaningful questions.
  • So we understand
    1. Why we need such views
    2. Who (role) provides input
    3. Who uses the output
    4. Which language constructs are used in each type of view

Embedded Governance

  • Define my own set of mandatory views along with their dependencies
  • Calculate architecture documentation completeness and present results in predefined dashboards
  • Govern strategy and architecture delivery using predefined charts and dashboards specific to each stage in the transformation process
  • Automated information distribution to business and IT stakeholders

Automatic Task Scheduling (e.g. nightly)

  • Data import
  • Calculation
  • Diagram generation
  • Excel generation
  • Word, PDF and RTF generation
  • HTML generation
  • Model validation and error report distribution
  • Backups…

Framework Tailoring (Language, metamodel, viewpoints and their dependencies, toolboxes, diagram types…)

  • A SDLC (DEV, TEST, PROD) environment to quickly customize my language, metamodel, toolboxes and diagram types in a few clicks
  • Straight through metamodel customization, because my metamodel evolves quickly, especially in the beginning
    • A practical metamodel that makes sense (derived from transformation process and systems semantics from the language itself)
    • Ease metamodel evolution and readability.
    • Metamodel expressed using the end user language (metamodel and documentation are now the same thing)
    • Change metamodel in two clicks
    • Automatically identify invalid connectors in existing model
    • Run a language transformer tool to adapt invalid connectors

More language transformation capabilities to

  • Import models from other tools and languages
  • Adapt element types, connector types, diagram types, tagged values, tag grouping, default tag grouping status and default element sub-diagram types in my existing or imported models

Unified Standards

  • Spare years and millions by re-using standards and best practices that are already unified into one single actionable transformation solution (1 language, 1 metamodel, 1 process, 1 repository and 1 tool)