chartletv0.21.0chartlet.casoon.de

← All examples

Course booking: system context

A course booking system as one box, the learners and trainers who use it and the three external systems it calls — the context template of the MCP diagram starter. No boundary and nothing inside the system: the diagram answers who uses it and what it relies on, with the main path from the learner to the payment provider. Illustrative values.

Course booking: system context

examples/booking-context.json
{
  "schemaVersion": 1,
  "type": "architecture",
  "title": "Course booking: system context",
  "height": 480,
  "architecture": {
    "components": [
      {
        "id": "learner",
        "label": "Learner",
        "sublabel": "books and attends courses",
        "kind": "person"
      },
      {
        "id": "trainer",
        "label": "Trainer",
        "sublabel": "runs courses",
        "kind": "person"
      },
      {
        "id": "booking",
        "label": "Course booking",
        "sublabel": "the system in scope"
      },
      {
        "id": "payment",
        "label": "Payment provider",
        "sublabel": "external system",
        "kind": "external"
      },
      {
        "id": "mail",
        "label": "E-mail service",
        "sublabel": "external system",
        "kind": "external"
      },
      {
        "id": "directory",
        "label": "Staff directory",
        "sublabel": "external system",
        "kind": "external"
      }
    ],
    "connections": [
      {
        "from": "learner",
        "to": "booking",
        "label": "books a course"
      },
      {
        "from": "trainer",
        "to": "booking",
        "label": "plans dates"
      },
      {
        "from": "booking",
        "to": "payment",
        "label": "takes payment"
      },
      {
        "from": "booking",
        "to": "mail",
        "label": "sends confirmations"
      },
      {
        "from": "booking",
        "to": "directory",
        "label": "looks up trainers"
      }
    ],
    "mainPath": [
      "learner",
      "booking",
      "payment"
    ]
  }
}
Focus
Course booking: system context
Course booking: system contextArchitecture diagram with 6 components and 5 connections. Main path: Learner → Course booking → Payment provider. Most connected: Course booking (5 connections). Nothing leads into Learner and Trainer. Nothing leads out of Payment provider, E-mail service and Staff directory. Learner (person): connects to Course booking (books a course). Trainer (person): connects to Course booking (plans dates). Course booking (service): connects to Payment provider (takes payment), E-mail service (sends confirmations) and Staff directory (looks up trainers). Payment provider (external system): no outgoing connection. E-mail service (external system): no outgoing connection. Staff directory (external system): no outgoing connection.Learner → Course booking: books a courseTrainer → Course booking: plans datesCourse booking → Payment provider: takes paymentCourse booking → E-mail service: sends confirmationsCourse booking → Staff directory: looks up trainersbooks a courseplans datestakes paymentsends confirmationslooks up trainersLearner – books and attends coursesLearnerbooks and attends coursesTrainer – runs coursesTrainerruns coursesCourse booking – the system in scopeCourse bookingthe system in scopePayment provider – external systemPayment providerexternal systemE-mail service – external systemE-mail serviceexternal systemStaff directory – external systemStaff directoryexternal system
Show chart data
Data for Course booking: system context
ComponentKindConnects to
LearnerpersonCourse booking (books a course)
TrainerpersonCourse booking (plans dates)
Course bookingservicePayment provider (takes payment), E-mail service (sends confirmations), Staff directory (looks up trainers)
Payment providerexternal system
E-mail serviceexternal system
Staff directoryexternal system
  • System context
  • Show who uses a system and what it depends on