Recent changes to Meetings

Meetings modified by Uwe Eisele

Uwe Eisele — Sun, 20 Oct 2013 12:29:55 -0000

--- v12
+++ v13
@@ -1 +1 @@
-Page has been migrated to Redmine (http://www.jak-swproject.eu/projects/jak-software-project/wiki/Meetings).
+Page has been migrated to Redmine ().

Meetings modified by Uwe Eisele

Uwe Eisele — Sun, 20 Oct 2013 12:29:23 -0000

--- v11
+++ v12
@@ -1,216 +1 @@
-This page contains the minutes of our meetings.
-Points which should be discussed can be added here too.
-
-Next Meeting at Fr, 18.10.2013 2:00 PM at Room 2/301
-
-# Points to be discussed in the next meeting
-
-# Meeting at Fr, 18.10.2013 2:00 PM
->##### Debriefing of JAK meeting and discussion of results
-
->##### Deciding whats the content of the specification
-* Introduction
-* Initial situation and objectives
-* User Stories
-* Requirements (high-level)
-* Deliverables
-* Architecture (high-level)
-    * interfaces and functions
-    * components and structure
-    * behavior
-    * data models
-* Common infrustructure aspects (e.g. Server, language, ...)
-* Security aspects
-
->##### Roles / Who works on what
-
->##### Whats next?
-
-# Meeting with the JAK people
->##### Progress
-* Presentation of what we planing to do
-Web    
-    * Discuss roles and find german words
-    * Discuss rights (which role is allowed to do what)
-    * Wording
-    * Attributes of domain elements
-    * Current situation of event management
-    * Discussing infrastructure
-    * New Requirements
-App
-    * Discuss features of smartphone app
-
->##### Roles
-* Member -> Mitglied
-* Volunteer -> Aktives Mitglied
-* Group Manager -> Arbeitsgruppenleiter
-* Dissemmination -> Pressearbeit
-
-The defined rights of the roles are correct.
-(Maybe it would be good to have a flexible rights management, e.g. define role of service in configuration file)
-
->##### Security
-* Prices/costs can only be seen by admins and planers
-
->##### Notifications
-* The newsletter has to be sended weakly (day should be configurable)
-* Its required by some processes to notify members
-
->##### Locations (new)
-* Role: Admin, Planer
-* Its necessary to manage locations
-
->##### Pre-sale (new)
-* We should offer a possibility to sell tickets (no payment)
-* Pre-sale for some events
-* Order button for events with active pre-sale
-* Sumerization of all events with pre-sale on one page
-* Pre-Sale should be stoped automaticaly x days befor the event (x -> configurable)
-* Sold tickets must be stored in database
-* View on admin page with sold tickets
-* Send eMail to person when ticket has been sold (member choosable)
-* Set hints for an event pre-sale (e.g. Karten nur an Abendkasse)
-* Capturing of ticket stores
-* Capture number of tickets which are handled by stores
-
->##### Google Calendar connected to Event Management
-* Dates of events must automatically inserted to the calendar of the local authority
-
->##### Infrastructure
-* High-Performance Server
-* Can use what ever we want
--> Java is possible
--> For development the current system will be cloned
--> We get ssh access to this server
-
->##### Event creation process
-* Planer creates a new event
-    * in the beginning only date must be fixed
-    * planer can klick on "Pling finished" button if all required fields are field
-    * Status is logged with extra free text field
-* System sends a email to all disseminators when a planer fisishes planing
-* Disseminator starts work on event (inserting text/pictures)
-    * Press button "Publish" when finished to publish the event on public site
-    * Maybe offer possibility to "Publish on ..."
-
->##### Events
-* Should be possible to change events after publishing
-* More than one band at one event
-* Files must be added to events and bands
-* When a events is published, all attached files must be stored on the filesystem
-* Its possible to have more than one event per day (we dont have to care about volunteer conflicts)
-* Reminder for hotel booking of band members
-* track actual sold tickets
-
->##### Event attributes
-* Date, time, location
-* Total number of standing and seating (imported from location, but changable)
-* An event can be marked as a highlight (a highlight is displayed on the main page)
-* Information about hotel for band members?
-    * Is hotel required for band members? 
-    * Has hotel been booked? 
-    * Whats the name of the hotel?
-    * Whats the complete prices of the hotel?
-* Start of pre-sale (if no start date is specified, then there is no pre-sale)
-* Ticket prices
-    * Pre-sale price (Vorverkauf)
-    * Normal price (Abendkasse)
-    * Discount for members in euro (Ermäßigung für Mitglieder)
-* Information about Tickes
-    * Are tickets sold out? (Manual input)
-    * Tickets only available at the event? (automatically displayed x (current 3) days bevore the event)
-* Pictures of event (also linked to the band)
-* Documents
-* Actual number of guests
-
->##### Group Manager
-* Every group manager has one group
-* Group manager is responsilbe for the member management
-* group manager can assign volunteers to his group
-* a volunteer can be a member of different groups
-* a volunteer which has been assigned to a group gets a email
-
->##### Members/Volunteers
-* a volunteer which gets assigned to a event gets a email
-* a volunteer can cancel the work request by an link in the email (in this case the group manager gets informed by email) -> its better that volunteer accepts work (state agreed/open/canlce)
-* Its possible to assigne volunteers to more events at the same time (volunteers have to manually cancle)
-* If volunteer who is assigned to an event gets inactive, the group manager gets informed
-* Its not possible to delete members -> members can only marked as resigned (for historical tracking)
-
->##### Bands
-* Store Url of Band-Website
-* Store multiple links to Band articles/videos
-* attach documents/pictures
-
->#### Band Attributes
-* Name of the band
-* Short description
-* Long description (max 1000 characters)
-* Members with instruments (only text)
-* URLs (Band Website, Videos, Facebook, ...)
-* Contacts (phone, mobil, email)
-* Contact person
-* Addess
-* Bank details (IBAN number, bank code (BLZ) and account number) (Only Admin and Planer)
-* Gage (only admin and planer)
-* Picturs (with metainformation, Where was the photo taken?, Copyright)
-* Free text for additional information
-
->##### Gallery
-* No sepatate image galery
-* An event is an image folder -> show images per event and band
-* Show images on events and band site
-* Images can be assigned to event and/or band
-* Uploaded pictures must be automatically resized (size configurable)
-
->##### Pictures
-* Sore metainformation for pictures
-* copyright message must automatically displayed when image is shown
-
-# Lecture 15.10.2013
-* Every student should sumerize what he did and what he want to do on wiki page
-* JAK Meeting today at 6 PM
-    * Stiftstrasse 32, Weinstadt-Beutelsbach
-    * Hartmunt Lenz (founder / CEO)
-    * Boris Poplutz (technical)
-    * Lutz Weber (event organizer)
-    * Ursula Vollmer (disseminatio)
-
-# Meeting Tu, 15.10.2013 11:30
-
->##### Common repository and ticket management
-We decided to have a common source code and ticket management.
-Our sourcecode repository is hosted on sourceforce (https://sourceforge.net/p/swproject).
-The Ticketmanagement is done with Redmine on (http://jak-swproject.eu).
-
->##### Ticket managemant and time tracking
-Its important to track time. This can be done with our Redmine Ticket Management System.
-Everybode should log all his work on the website. 
-
->##### Structure on SVN
-How we organize our source? Where we do store what?
--> Every Project has a root directory with trunk/branch/tag subdirectories
-Uwe creates the initial SVN structure.
-Commiting is only allowed with the related ticket number.
-
->##### When shall we meet (How we handle Scrum)?
-* Tuesday after the Software Design lecture
-* Saturday 11 AM via Skype
-Our Sprints take 2 weeks.
-
->##### Spokes-persons of Web-Group and Scrum Master
-App: Stefan
-Web: Uwe
-Scrum Master changes evrey week (order of mailing list)
-
->##### Experiences
-Jo: node.js
-
->##### Preffered Software 
-Language: Java
-Database MySQL
-Server: Tomcat
-UML Tool: UML Lab
-
-Server: Ask Mr Keller for a Server (fund money for cloud instance)
-Set up contiouse integration -> we need server
+Page has been migrated to Redmine (http://www.jak-swproject.eu/projects/jak-software-project/wiki/Meetings).

Meetings modified by Uwe Eisele

Uwe Eisele — Sun, 20 Oct 2013 11:41:22 -0000

--- v10
+++ v11
@@ -62,16 +62,16 @@

 >##### Pre-sale (new)
 * We should offer a possibility to sell tickets (no payment)
-* Pre-sale for events with active presale flag
+* Pre-sale for some events
 * Order button for events with active pre-sale
 * Sumerization of all events with pre-sale on one page
 * Pre-Sale should be stoped automaticaly x days befor the event (x -> configurable)
 * Sold tickets must be stored in database
 * View on admin page with sold tickets
 * Send eMail to person when ticket has been sold (member choosable)
-* Set hints for an event presale (e.g. Karten nur an Abendkasse)
+* Set hints for an event pre-sale (e.g. Karten nur an Abendkasse)
 * Capturing of ticket stores
-* Capture number of tickets which are handles by stores
+* Capture number of tickets which are handled by stores

 >##### Google Calendar connected to Event Management
 * Dates of events must automatically inserted to the calendar of the local authority
@@ -103,17 +103,25 @@
 * track actual sold tickets

 >##### Event attributes
-* Datum, Uhrzeit, Location
-* Anzahl gesamt Sitz- oder Stehplätze (aus der Location)
-* Ein Event kann ein Highlight sein! (es können mehrere sein!)
-* Braucht Buchung von Hotel und ob Hotels gebucht mit Angabe vom Hotelnamen (mit Preis bei der Buchung)
-* Ab WANN der Vorverkauf stattfindet! (Wenn Leer, dann gibt‘s keinen!)
-* Eintrittspreise (VVK, Abendkasse, Ermäßigung ausgezahlt am)
-* Info ob ausverkauft
-* Info ob Tickets nur noch an der Abendkasse! (das ist derzeit 3 Tage vor der Veranstaltung!)
-* Und auch im nachhinein:
-    * Bilder vom Event (verlinkt mit der Band)
-    * Anzahl der Gäste...
+* Date, time, location
+* Total number of standing and seating (imported from location, but changable)
+* An event can be marked as a highlight (a highlight is displayed on the main page)
+* Information about hotel for band members?
+    * Is hotel required for band members? 
+    * Has hotel been booked? 
+    * Whats the name of the hotel?
+    * Whats the complete prices of the hotel?
+* Start of pre-sale (if no start date is specified, then there is no pre-sale)
+* Ticket prices
+    * Pre-sale price (Vorverkauf)
+    * Normal price (Abendkasse)
+    * Discount for members in euro (Ermäßigung für Mitglieder)
+* Information about Tickes
+    * Are tickets sold out? (Manual input)
+    * Tickets only available at the event? (automatically displayed x (current 3) days bevore the event)
+* Pictures of event (also linked to the band)
+* Documents
+* Actual number of guests

 >##### Group Manager
 * Every group manager has one group
@@ -135,18 +143,18 @@
 * attach documents/pictures

 >#### Band Attributes
-* Bandnamen
-* Kurzinfo
-* Bandmitglieder mit deren Instrumente (textuelle)
-* Bandbeschreibung, max. 1000 Zeichen
-* (mehrere) URLs: Bandhomepage, evtl. Videos, Links zu Facebook
-* Kontakt: Telefonnummer (fest), und Mobil, Email
-* Ansprechpartner: Telefonnummer (fest), Mobil, Email
-* Adressdaten
-* Bankverbindung (!) (IBAN Nummer, bzw. BLZ und Kontonummer)
-* Verweis auf die Bilder (mit Metainformationen, woher kommt das Bild, Rechte/Copyright etc.)
-* Gage (nur sichtbar für Planer und Admin)
-* Freitext für Infos
+* Name of the band
+* Short description
+* Long description (max 1000 characters)
+* Members with instruments (only text)
+* URLs (Band Website, Videos, Facebook, ...)
+* Contacts (phone, mobil, email)
+* Contact person
+* Addess
+* Bank details (IBAN number, bank code (BLZ) and account number) (Only Admin and Planer)
+* Gage (only admin and planer)
+* Picturs (with metainformation, Where was the photo taken?, Copyright)
+* Free text for additional information

 >##### Gallery
 * No sepatate image galery

Meetings modified by Uwe Eisele

Uwe Eisele — Fri, 18 Oct 2013 14:01:25 -0000

--- v9
+++ v10
@@ -124,7 +124,7 @@

 >##### Members/Volunteers
 * a volunteer which gets assigned to a event gets a email
-* a volunteer can cancel the work request by an link in the email (in this case the group manager gets informed by email)
+* a volunteer can cancel the work request by an link in the email (in this case the group manager gets informed by email) -> its better that volunteer accepts work (state agreed/open/canlce)
 * Its possible to assigne volunteers to more events at the same time (volunteers have to manually cancle)
 * If volunteer who is assigned to an event gets inactive, the group manager gets informed
 * Its not possible to delete members -> members can only marked as resigned (for historical tracking)

Meetings modified by Uwe Eisele

Uwe Eisele — Thu, 17 Oct 2013 21:50:05 -0000

--- v8
+++ v9
@@ -5,54 +5,204 @@

 # Points to be discussed in the next meeting

+# Meeting at Fr, 18.10.2013 2:00 PM
+>##### Debriefing of JAK meeting and discussion of results
+
+>##### Deciding whats the content of the specification
+* Introduction
+* Initial situation and objectives
+* User Stories
+* Requirements (high-level)
+* Deliverables
+* Architecture (high-level)
+    * interfaces and functions
+    * components and structure
+    * behavior
+    * data models
+* Common infrustructure aspects (e.g. Server, language, ...)
+* Security aspects
+
+>##### Roles / Who works on what
+
+>##### Whats next?
+
+# Meeting with the JAK people
+>##### Progress
+* Presentation of what we planing to do
+Web    
+    * Discuss roles and find german words
+    * Discuss rights (which role is allowed to do what)
+    * Wording
+    * Attributes of domain elements
+    * Current situation of event management
+    * Discussing infrastructure
+    * New Requirements
+App
+    * Discuss features of smartphone app
+
+>##### Roles
+* Member -> Mitglied
+* Volunteer -> Aktives Mitglied
+* Group Manager -> Arbeitsgruppenleiter
+* Dissemmination -> Pressearbeit
+
+The defined rights of the roles are correct.
+(Maybe it would be good to have a flexible rights management, e.g. define role of service in configuration file)
+
+>##### Security
+* Prices/costs can only be seen by admins and planers
+
+>##### Notifications
+* The newsletter has to be sended weakly (day should be configurable)
+* Its required by some processes to notify members
+
+>##### Locations (new)
+* Role: Admin, Planer
+* Its necessary to manage locations
+
+>##### Pre-sale (new)
+* We should offer a possibility to sell tickets (no payment)
+* Pre-sale for events with active presale flag
+* Order button for events with active pre-sale
+* Sumerization of all events with pre-sale on one page
+* Pre-Sale should be stoped automaticaly x days befor the event (x -> configurable)
+* Sold tickets must be stored in database
+* View on admin page with sold tickets
+* Send eMail to person when ticket has been sold (member choosable)
+* Set hints for an event presale (e.g. Karten nur an Abendkasse)
+* Capturing of ticket stores
+* Capture number of tickets which are handles by stores
+
+>##### Google Calendar connected to Event Management
+* Dates of events must automatically inserted to the calendar of the local authority
+
+>##### Infrastructure
+* High-Performance Server
+* Can use what ever we want
+-> Java is possible
+-> For development the current system will be cloned
+-> We get ssh access to this server
+
+>##### Event creation process
+* Planer creates a new event
+    * in the beginning only date must be fixed
+    * planer can klick on "Pling finished" button if all required fields are field
+    * Status is logged with extra free text field
+* System sends a email to all disseminators when a planer fisishes planing
+* Disseminator starts work on event (inserting text/pictures)
+    * Press button "Publish" when finished to publish the event on public site
+    * Maybe offer possibility to "Publish on ..."
+
+>##### Events
+* Should be possible to change events after publishing
+* More than one band at one event
+* Files must be added to events and bands
+* When a events is published, all attached files must be stored on the filesystem
+* Its possible to have more than one event per day (we dont have to care about volunteer conflicts)
+* Reminder for hotel booking of band members
+* track actual sold tickets
+
+>##### Event attributes
+* Datum, Uhrzeit, Location
+* Anzahl gesamt Sitz- oder Stehplätze (aus der Location)
+* Ein Event kann ein Highlight sein! (es können mehrere sein!)
+* Braucht Buchung von Hotel und ob Hotels gebucht mit Angabe vom Hotelnamen (mit Preis bei der Buchung)
+* Ab WANN der Vorverkauf stattfindet! (Wenn Leer, dann gibt‘s keinen!)
+* Eintrittspreise (VVK, Abendkasse, Ermäßigung ausgezahlt am)
+* Info ob ausverkauft
+* Info ob Tickets nur noch an der Abendkasse! (das ist derzeit 3 Tage vor der Veranstaltung!)
+* Und auch im nachhinein:
+    * Bilder vom Event (verlinkt mit der Band)
+    * Anzahl der Gäste...
+
+>##### Group Manager
+* Every group manager has one group
+* Group manager is responsilbe for the member management
+* group manager can assign volunteers to his group
+* a volunteer can be a member of different groups
+* a volunteer which has been assigned to a group gets a email
+
+>##### Members/Volunteers
+* a volunteer which gets assigned to a event gets a email
+* a volunteer can cancel the work request by an link in the email (in this case the group manager gets informed by email)
+* Its possible to assigne volunteers to more events at the same time (volunteers have to manually cancle)
+* If volunteer who is assigned to an event gets inactive, the group manager gets informed
+* Its not possible to delete members -> members can only marked as resigned (for historical tracking)
+
+>##### Bands
+* Store Url of Band-Website
+* Store multiple links to Band articles/videos
+* attach documents/pictures
+
+>#### Band Attributes
+* Bandnamen
+* Kurzinfo
+* Bandmitglieder mit deren Instrumente (textuelle)
+* Bandbeschreibung, max. 1000 Zeichen
+* (mehrere) URLs: Bandhomepage, evtl. Videos, Links zu Facebook
+* Kontakt: Telefonnummer (fest), und Mobil, Email
+* Ansprechpartner: Telefonnummer (fest), Mobil, Email
+* Adressdaten
+* Bankverbindung (!) (IBAN Nummer, bzw. BLZ und Kontonummer)
+* Verweis auf die Bilder (mit Metainformationen, woher kommt das Bild, Rechte/Copyright etc.)
+* Gage (nur sichtbar für Planer und Admin)
+* Freitext für Infos
+
+>##### Gallery
+* No sepatate image galery
+* An event is an image folder -> show images per event and band
+* Show images on events and band site
+* Images can be assigned to event and/or band
+* Uploaded pictures must be automatically resized (size configurable)
+
+>##### Pictures
+* Sore metainformation for pictures
+* copyright message must automatically displayed when image is shown
+
+# Lecture 15.10.2013
+* Every student should sumerize what he did and what he want to do on wiki page
+* JAK Meeting today at 6 PM
+    * Stiftstrasse 32, Weinstadt-Beutelsbach
+    * Hartmunt Lenz (founder / CEO)
+    * Boris Poplutz (technical)
+    * Lutz Weber (event organizer)
+    * Ursula Vollmer (disseminatio)
+
 # Meeting Tu, 15.10.2013 11:30

->##### Comman repository and ticket management
-Do it together
+>##### Common repository and ticket management
+We decided to have a common source code and ticket management.
+Our sourcecode repository is hosted on sourceforce (https://sourceforge.net/p/swproject).
+The Ticketmanagement is done with Redmine on (http://jak-swproject.eu).

 >##### Ticket managemant and time tracking
-Ticket with Redmine http://www.jak-swproject.eu/
+Its important to track time. This can be done with our Redmine Ticket Management System.
+Everybode should log all his work on the website. 
+
+>##### Structure on SVN
+How we organize our source? Where we do store what?
+-> Every Project has a root directory with trunk/branch/tag subdirectories
+Uwe creates the initial SVN structure.
+Commiting is only allowed with the related ticket number.

 >##### When shall we meet (How we handle Scrum)?
-Tu after Sw Design
-Sa 11 AM Skype
-Sprint 2 weeks
-User Stories in Bakclock
-
->##### Structure on SVN
-How we organize our source? Where we store what?
-Uwe creates SVN structure
-Add ticket number to commit
+* Tuesday after the Software Design lecture
+* Saturday 11 AM via Skype
+Our Sprints take 2 weeks.

 >##### Spokes-persons of Web-Group and Scrum Master
 App: Stefan
 Web: Uwe
 Scrum Master changes evrey week (order of mailing list)

-
 >##### Experiences
 Jo: node.js

->##### Review of requirements and use cases
-
->##### Questions to JAK
-* Infrastructure
-
->##### How shall we proceed? What do we need?
+>##### Preffered Software 
 Language: Java
 Database MySQL
-
+Server: Tomcat
 UML Tool: UML Lab

 Server: Ask Mr Keller for a Server (fund money for cloud instance)
-Set up contiouse integration: 
-
-
-# Lecture 15.10.2013
-* Every student should sumerize what he did and what he want to do on wiki page
-* JAK: Stiftstrasse 32, Weinstadt-Beutelsbach
-
-* Hartmunt Lenz (founder / CEO)
-* Boris Poplutz (technical)
-* Lutz Weber (event organizer)
-* Ursula Vollmer (disseminatio)
+Set up contiouse integration -> we need server

Meetings modified by Uwe Eisele

Uwe Eisele — Tue, 15 Oct 2013 13:53:35 -0000

--- v7
+++ v8
@@ -1,5 +1,7 @@
 This page contains the minutes of our meetings.
 Points which should be discussed can be added here too.
+
+Next Meeting at Fr, 18.10.2013 2:00 PM at Room 2/301

 # Points to be discussed in the next meeting

Meetings modified by Uwe Eisele

Uwe Eisele — Tue, 15 Oct 2013 12:16:35 -0000

--- v6
+++ v7
@@ -29,6 +29,7 @@

 >##### Experiences
+Jo: node.js

 >##### Review of requirements and use cases

@@ -43,3 +44,13 @@

 Server: Ask Mr Keller for a Server (fund money for cloud instance)
 Set up contiouse integration: 
+
+
+# Lecture 15.10.2013
+* Every student should sumerize what he did and what he want to do on wiki page
+* JAK: Stiftstrasse 32, Weinstadt-Beutelsbach
+
+* Hartmunt Lenz (founder / CEO)
+* Boris Poplutz (technical)
+* Lutz Weber (event organizer)
+* Ursula Vollmer (disseminatio)

Meetings modified by Uwe Eisele

Uwe Eisele — Tue, 15 Oct 2013 10:59:51 -0000

--- v5
+++ v6
@@ -14,6 +14,8 @@
 >##### When shall we meet (How we handle Scrum)?
 Tu after Sw Design
 Sa 11 AM Skype
+Sprint 2 weeks
+User Stories in Bakclock

 >##### Structure on SVN
 How we organize our source? Where we store what?
@@ -37,5 +39,7 @@
 Language: Java
 Database MySQL

+UML Tool: UML Lab
+
 Server: Ask Mr Keller for a Server (fund money for cloud instance)
 Set up contiouse integration:

Meetings modified by Uwe Eisele

Uwe Eisele — Tue, 15 Oct 2013 10:30:30 -0000

--- v4
+++ v5
@@ -6,20 +6,36 @@
 # Meeting Tu, 15.10.2013 11:30

 >##### Comman repository and ticket management
+Do it together

 >##### Ticket managemant and time tracking
+Ticket with Redmine http://www.jak-swproject.eu/

 >##### When shall we meet (How we handle Scrum)?
+Tu after Sw Design
+Sa 11 AM Skype

 >##### Structure on SVN
 How we organize our source? Where we store what?
+Uwe creates SVN structure
+Add ticket number to commit

 >##### Spokes-persons of Web-Group and Scrum Master
+App: Stefan
+Web: Uwe
+Scrum Master changes evrey week (order of mailing list)
+

 >##### Experiences

 >##### Review of requirements and use cases

 >##### Questions to JAK
+* Infrastructure

 >##### How shall we proceed? What do we need?
+Language: Java
+Database MySQL
+
+Server: Ask Mr Keller for a Server (fund money for cloud instance)
+Set up contiouse integration:

Meetings modified by Uwe Eisele

Uwe Eisele — Tue, 15 Oct 2013 07:06:39 -0000

--- v3
+++ v4
@@ -4,8 +4,6 @@
 # Points to be discussed in the next meeting

 # Meeting Tu, 15.10.2013 11:30
-
-## Organisatoric

 >##### Comman repository and ticket management

@@ -16,11 +14,9 @@
 >##### Structure on SVN
 How we organize our source? Where we store what?

->##### Experiences
-
 >##### Spokes-persons of Web-Group and Scrum Master

-## Development
+>##### Experiences

 >##### Review of requirements and use cases