diff --git a/Use-Case-Specification:-Price-Alarm-List.md b/Use-Case-Specification:-Price-Alarm-List.md
new file mode 100644
index 0000000..15fef3c
--- /dev/null
+++ b/Use-Case-Specification:-Price-Alarm-List.md
@@ -0,0 +1,28 @@
+# Use-Case Specification: Price Alarm List
+## 1. Use-Case: Price Alarm List
+### 1.1 Brief Description
+This use case shows the flow for accessing the price alarm list and removing single price alarms.
+
+## 2. Flow of Events
+### Activity Diagram
+![activity diagram]()<br>
+[Cucumber Test File](https://github.com/Mueller-Patrick/Betterzon/blob/master/CucumberTests/src/test/resource/priceAlarms.feature)
+
+### 2.1 Accessing the price alarm list
+When the user is on the landing page and logged in, he can click the profile icon in the top right corner of the page. This will open a popup containing a brief summary of his profile like username etc and also a link to the price alarm list page. When he clicks on this link, he will be redirected to the price alarm list page. This page will contain a list of price alarms (if there already are any). The list will contain a maximum of 20 alarms per page, with an option to switch to page 2...n. The user can select the sorting order by himself.
+
+### 2.2 Removing a price alarm
+Next to each price alarm item in the list, there will be a "remove" button. If the user clicks this button, he will be prompted to confirm the removal. If he proceeds, the price alarm will be deleted.
+
+## 3. Special Requirements
+N/A
+
+## 4. Preconditions
+### 4.1 The user has to be logged in to set see the list of his price alarms
+Obviously, an anonymous user is not able to set a price alarm and is therefore also not able to get a list of price alarms he already set.
+
+## 5. Postconditions
+N/A
+
+## 6. Function Points
+[tbd]
\ No newline at end of file