diff --git a/docs/Software Development/04-Software Application Specifications/10-Event-Driven Architecture.md b/docs/Software Development/04-Software Application Specifications/10-Event-Driven Architecture.md
new file mode 100644
index 0000000..e490d7c
--- /dev/null
+++ b/docs/Software Development/04-Software Application Specifications/10-Event-Driven Architecture.md	
@@ -0,0 +1,35 @@
+# Event-Driven Architecture
+
+
+In this section, we'll cover the concept of events in our software system and provide an example using the Cloud Event specification.
+
+## Understanding Event-Driven Architecture
+
+
+Event-driven architecture is a powerful approach that revolves around events as triggers in a system. Events can come from user actions, internal processes, or external inputs. By using event-driven architecture, we can create systems that are flexible, scalable, and responsive to changes.
+
+## Utilizing the Cloud Event Specification
+
+The Cloud Event specification is a common standard for describing event data in a consistent format. It provides a set of attributes that define important properties of an event, allowing easy sharing and processing of events across different systems and services.
+
+### Example Cloud Event
+
+Here's an example of a Cloud Event in JSON format:
+
+```json
+{
+  "id":"4b9240e7-73c4-4ef1-9c9d-82dca9b506a1",
+  "specversion":"1.0",
+  "datacontenttype":"application/json",
+  "time":"2023-06-13T15:37:00Z",
+  "subject":"example_subject",
+  "source":"/my-service",
+  "userid":"c24f8303-9e10-4f0d-88cd-25e29c3c68af",
+  "data":{
+    "message":"Hello World"
+  }
+}
+```
+
+Within this example, we present a Cloud Event featuring attributes such as specversion, type, id, source, time,userid, and data. These attributes provide crucial information regarding the event, including its type, unique identifier, source, timestamp, and payload data.
+