Sample Prompts for the Inventory Builder

Explore sample prompts to enhance your experience with the inventory builder.

Using well-crafted prompts significantly improves the analysis of enterprise architecture diagrams and images, enabling the inventory builder to accurately extract relevant architectural elements for each fact sheet type.

Find below some examples of best practice prompts for different fact sheet types.

Application

  • Identify applications in the diagram by their visual representation and extract their names and relationships. [Describe the visual representations - e.g., blue boxes, turquoise boxes, grey blocks].
  • Analyze colored boxes in the diagram: [specify colors] boxes represent applications. Extract their names and any parent-child relationships.
  • Extract all application components from the diagram, noting their integration points and platform relationships. Distinguish them from other elements like IT components.

Business Capability

  • Identify business capabilities and their hierarchical structure in the diagram. Note relationships to supporting applications and organizations.
  • Extract business capability elements and organize them by their tier level and parent-child relationships.

Interface

  • Identify interfaces represented by arrows/lines between applications. Name interfaces using the format: [SourceSystem][TargetSystem][DataObjectOrPurpose]_[InterfaceType].
  • Extract all connection lines representing interfaces between systems. Determine provider (start of line) and consumer (end of line/arrow) relationships.
  • Identify interface elements with their associated data objects. Note data flow directions, with the line origin indicating the provider and the arrow end indicating the consumer.

Data Object

  • Extract data objects mentioned on or near interface arrows. Link each data object to its respective interface and identify parent-child relationships between data objects.
  • Identify hierarchical data structures in the diagram. Extract parent data objects (e.g., 'Products') and their child elements (e.g., 'Product_Id', 'Product_Name').
  • Analyze small text labels near interfaces that represent data objects being transferred between systems. Connect these to the appropriate interfaces.

IT Component

  • Identify IT components that make up infrastructure elements, such as hardware or microservices. Distinguish them from applications and note their technical relationships.
  • Extract IT components with their product specifications and identify which applications they support or belong to.
  • Identify technical components that underpin applications (e.g., 'Microsoft SharePoint 2019' supporting SharePoint applications). Note platform affiliations.

Business Context

  • Identify business processes in the diagram, noting hierarchical relationships and process flows. Extract sub-processes that belong to larger business functions.
  • Identify business context elements arranged in tiers, noting parent-child relationships between processes, value streams, and products.

Organization

  • Identify organizational units represented in the diagram (e.g., as dotted squares or specific shapes). Note their relationships to applications and other elements.
  • Extract organizational structures showing reporting lines, departments, and their relationships to business capabilities or applications.

Platform

  • Identify platform elements that host multiple applications. Note which applications belong to each platform and any associated IT components.
  • Extract platform components that serve as foundations for multiple applications, noting dependencies.

Initiative

  • Identify initiative elements in the grey boxes and extract their names, objectives, and related organizational units.
  • Extract initiative components and their relationships to business capabilities, objectives, and organizational units they impact.

Objective

  • Extract business objectives from the diagram and identify their relationships to initiatives and business contexts.
  • Identify objective elements and how they align with business capabilities and initiatives in the architecture.