Joule
  • Welcome to Joule's Docs
  • Why Joule?
    • Joule capabilities
  • What is Joule?
    • Key features
    • The tech stack
  • Use case enablement
    • Use case building framework
  • Concepts
    • Core concepts
    • Low code development
    • Unified execution engine
    • Batch and stream processing
    • Continuous metrics
    • Key Joule data types
      • StreamEvent object
      • Contextual data
      • GeoNode
  • Tutorials
    • Getting started
    • Build your first use case
    • Stream sliding window quote analytics
    • Advanced tutorials
      • Custom missing value processor
      • Stateless Bollinger band analytics
      • IoT device control
  • FAQ
  • Glossary
  • Components
    • Pipelines
      • Use case anatomy
      • Data priming
        • Types of import
      • Processing unit
      • Group by
      • Emit computed events
      • Telemetry auditing
    • Processors
      • Common attributes
      • Filters
        • By type
        • By expression
        • Send on delta
        • Remove attributes
        • Drop all events
      • Enrichment
        • Key concepts
          • Anatomy of enrichment DSL
          • Banking example
        • Metrics
        • Dynamic contextual data
          • Caching architecture
        • Static contextual data
      • Transformation
        • Field Tokeniser
        • Obfuscation
          • Encryption
          • Masking
          • Bucketing
          • Redaction
      • Triggers
        • Change Data Capture
        • Business rules
      • Stream join
        • Inner stream joins
        • Outer stream joins
        • Join attributes & policy
      • Event tap
        • Anatomy of a Tap
        • SQL Queries
    • Analytics
      • Analytic tools
        • User defined analytics
          • Streaming analytics example
          • User defined analytics
          • User defined scripts
          • User defined functions
            • Average function library
        • Window analytics
          • Tumbling window
          • Sliding window
          • Aggregate functions
        • Analytic functions
          • Stateful
            • Exponential moving average
            • Rolling Sum
          • Stateless
            • Normalisation
              • Absolute max
              • Min max
              • Standardisation
              • Mean
              • Log
              • Z-Score
            • Scaling
              • Unit scale
              • Robust Scale
            • Statistics
              • Statistic summaries
              • Weighted moving average
              • Simple moving average
              • Count
            • General
              • Euclidean
        • Advanced analytics
          • Geospatial
            • Entity geo tracker
            • Geofence occupancy trigger
            • Geo search
            • IP address resolver
            • Reverse geocoding
            • Spatial Index
          • HyperLogLog
          • Distinct counter
      • ML inferencing
        • Feature engineering
          • Scripting
          • Scaling
          • Transform
        • Online predictive analytics
        • Model audit
        • Model management
      • Metrics engine
        • Create metrics
        • Apply metrics
        • Manage metrics
        • Priming metrics
    • Contextual data
      • Architecture
      • Configuration
      • MinIO S3
      • Apache Geode
    • Connectors
      • Sources
        • Kafka
          • Ingestion
        • RabbitMQ
          • Further RabbitMQ configurations
        • MQTT
          • Topic wildcards
          • Session management
          • Last Will and Testament
        • Rest endpoints
        • MinIO S3
        • File watcher
      • Sinks
        • Kafka
        • RabbitMQ
          • Further configurations
        • MQTT
          • Persistent messaging
          • Last Will and Testament
        • SQL databases
        • InfluxDB
        • MongoDB
        • Geode
        • WebSocket endpoint
        • MinIO S3
        • File transport
        • Slack
        • Email
      • Serialisers
        • Serialisation
          • Custom transform example
          • Formatters
        • Deserialisers
          • Custom parsing example
    • Observability
      • Enabling JMX for Joule
      • Meters
      • Metrics API
  • DEVELOPER GUIDES
    • Setting up developer environment
      • Environment setup
      • Build and deploy
      • Install Joule
        • Install Docker demo environment
        • Install with Docker
        • Install from source
        • Install Joule examples
    • Joulectl CLI
    • API Endpoints
      • Mangement API
        • Use case
        • Pipelines
        • Data connectors
        • Contextual data
      • Data access API
        • Query
        • Upload
        • WebSocket
      • SQL support
    • Builder SDK
      • Connector API
        • Sources
          • StreamEventParser API
        • Sinks
          • CustomTransformer API
      • Processor API
      • Analytics API
        • Create custom metrics
        • Define analytics
        • Windows API
        • SQL queries
      • Transformation API
        • Obfuscation API
        • FieldTokenizer API
      • File processing
      • Data types
        • StreamEvent
        • ReferenceDataObject
        • GeoNode
    • System configuration
      • System properties
  • Deployment strategies
    • Deployment Overview
    • Single Node
    • Cluster
    • GuardianDB
    • Packaging
      • Containers
      • Bare metal
  • Product updates
    • Public Roadmap
    • Release Notes
      • v1.2.0 Join Streams with stateful analytics
      • v1.1.0 Streaming analytics enhancements
      • v1.0.4 Predictive stream processing
      • v1.0.3 Contextual SQL based metrics
    • Change history
Powered by GitBook
On this page
  • What will we learn in this article?
  • What steps do we take for an impactful use case?
  • Understand the system
  • Identify the actors
  • Define actor goals
  • Map the scenario
  • Validate and refine
  • Example: Online appointment scheduling
  • Actors
  • Basic flow
  • Alternate flow
  • Outcome
  • Template: User story
  • Example Stories
  • Additional resources

Was this helpful?

  1. Use case enablement

Use case building framework

Build impactful use cases

What will we learn in this article?

In this guide, we will learn how to create effective use cases that bridge the gap between user needs and system functionality. We will walk through the steps of building a use case, provide a real-world example and offer a simple user story template to help you get started.

By the end, we will have the tools and confidence to create use cases that drive real business impact.

With this use case in our hands, we will be focused when transferring it to the Joule DSL and have a successful project delivery.

What steps do we take for an impactful use case?

Understand the system

To build a strong use case, we start by defining the system we are working with. Whether it’s software, a product or a service:

  1. What does it do for our users?

  2. What goals does it help to achieve?

  3. What are the key features and functions?

Represent everything visually using a graphing tool, on paper or a board

Identify the actors

Actors are anyone or anything interacting with our system. This can include:

  1. External stakeholders such as end users (i.e., customers, employees).

  2. Secondary systems or tools with dependencies to the target improvement area.

  3. Internal stakeholders, your colleagues.

We should clearly define their behaviours and roles in the process.

Define actor goals

Next, we focus on what the actors want to achieve. This step shifts the perspective from what the system can do to why users need it. Listing each goal ensures we understand the breadth of user interactions and outcomes.

Map the scenario

Now, we outline the step-by-step flow of interaction between the actor and the system:

  1. Basic flow What happens when everything works as intended.

  2. Alternate flows What happens if there are errors, misuse or exceptions.

These flows give us a clear picture of how the system operates in real-world situations.

Validate and refine

We compile all the flows to create a full use case. If we’re working with complex systems, we focus on the most common interactions or critical scenarios. Testing these scenarios can help us refine the use case and improve its usability.

Example: Online appointment scheduling

Actors

  1. Customer.

  2. Scheduling System.

Basic flow

  1. The customer selects a service and checks availability.

  2. The system displays available slots.

  3. The customer chooses a time and provides contact details.

  4. The system confirms the booking and sends a notification.

Alternate flow

If the customer enters incomplete contact information, the system prompts them to complete the form before proceeding.

Outcome

The customer successfully schedules an appointment or receives actionable guidance to correct errors.

Template: User story

We can use this simple structure to write user stories as part of our use case to add more context and tell the story:

“As a [persona], I [want to], [so that].”

Example Stories

  1. As a customer, I want to view available appointment times, so that I can book a slot that fits my schedule.

  2. As a system admin, I want to track booking patterns, so that I can optimize resource allocation.

Additional resources

PreviousUse case enablementNextConcepts

Last updated 6 months ago

Was this helpful?

.

design process.

Visualisation of .

Use case framework
Double diamond
use cases using the C4 model
Use case diagram