From 6e600d30adbe59557cd2478fb0ed0861c03f0faf Mon Sep 17 00:00:00 2001 From: marcinzelent Date: Sat, 18 Feb 2017 23:13:33 +0100 Subject: Removed faulty diagrams. --- EventMaker/Design/AddEventFDUC.txt | 16 + EventMaker/Design/AddingEvent.sequencediagram | 1 - .../Design/AddingEvent.sequencediagram.layout | 1 - EventMaker/Design/AddingEventFDUC.txt | 16 - EventMaker/Design/Design.modelproj | 20 +- EventMaker/Design/EditEventFDUC.txt | 16 + EventMaker/Design/EditingEventFDUC.txt | 16 - EventMaker/Design/ModelDefinition/Design.uml | 18 + EventMaker/Design/RemoveEventFDUC.txt | 13 + EventMaker/Design/RemovingEvent.sequencediagram | 582 --------------------- .../Design/RemovingEvent.sequencediagram.layout | 224 -------- EventMaker/Design/RemovingEventFDUC.txt | 13 - 12 files changed, 66 insertions(+), 870 deletions(-) create mode 100644 EventMaker/Design/AddEventFDUC.txt delete mode 100644 EventMaker/Design/AddingEvent.sequencediagram delete mode 100644 EventMaker/Design/AddingEvent.sequencediagram.layout delete mode 100644 EventMaker/Design/AddingEventFDUC.txt create mode 100644 EventMaker/Design/EditEventFDUC.txt delete mode 100644 EventMaker/Design/EditingEventFDUC.txt create mode 100644 EventMaker/Design/RemoveEventFDUC.txt delete mode 100644 EventMaker/Design/RemovingEvent.sequencediagram delete mode 100644 EventMaker/Design/RemovingEvent.sequencediagram.layout delete mode 100644 EventMaker/Design/RemovingEventFDUC.txt diff --git a/EventMaker/Design/AddEventFDUC.txt b/EventMaker/Design/AddEventFDUC.txt new file mode 100644 index 0000000..f91da65 --- /dev/null +++ b/EventMaker/Design/AddEventFDUC.txt @@ -0,0 +1,16 @@ +Use case name: Add event +Scope: EventMaker +Level: Adding new event to the list +Primary Actor: User +Stakeholders and Interests: Teachers, adding events functionality +Preconditions: App started successfuly +Success Guarantee: New event on the list +Main Success Scenario: User opens app, presses add button, fills all fields on the page for creating new event and saves the event. +Extensions: +A. User opens app, presses add button but then he changes mind and presses the back button to return to the main page. +B. If user tries to add event with empty field show him error message and don't add the event. +C. The name of event can't be longer than 20 characters. +Special Requirements: UWP app, serialization to JSON +Technology and Data Variations List: None +Frequency of Occurence: Based on the will of the user +Miscellaneous: None \ No newline at end of file diff --git a/EventMaker/Design/AddingEvent.sequencediagram b/EventMaker/Design/AddingEvent.sequencediagram deleted file mode 100644 index 19a76f1..0000000 --- a/EventMaker/Design/AddingEvent.sequencediagram +++ /dev/null @@ -1 +0,0 @@ - \ No newline at end of file diff --git a/EventMaker/Design/AddingEvent.sequencediagram.layout b/EventMaker/Design/AddingEvent.sequencediagram.layout deleted file mode 100644 index 5f28270..0000000 --- a/EventMaker/Design/AddingEvent.sequencediagram.layout +++ /dev/null @@ -1 +0,0 @@ - \ No newline at end of file diff --git a/EventMaker/Design/AddingEventFDUC.txt b/EventMaker/Design/AddingEventFDUC.txt deleted file mode 100644 index 402ade8..0000000 --- a/EventMaker/Design/AddingEventFDUC.txt +++ /dev/null @@ -1,16 +0,0 @@ -Use case name: Adding event -Scope: EventMaker -Level: Adding new event to the list -Primary Actor: User -Stakeholders and Interests: Teachers, adding events functionality -Preconditions: App started successfuly -Success Guarantee: New event on the list -Main Success Scenario: User opens app, presses add button, fills all fields on the page for creating new event and saves the event. -Extensions: -A. User opens app, presses add button but then he changes mind and presses the back button to return to the main page. -B. If user tries to add event with empty field show him error message and don't add the event. -C. The name of event can't be longer than 20 characters. -Special Requirements: UWP app, serialization to JSON -Technology and Data Variations List: None -Frequency of Occurence: Based on the will of the user -Miscellaneous: None \ No newline at end of file diff --git a/EventMaker/Design/Design.modelproj b/EventMaker/Design/Design.modelproj index 91b7a5f..58f7eb4 100644 --- a/EventMaker/Design/Design.modelproj +++ b/EventMaker/Design/Design.modelproj @@ -22,24 +22,10 @@ - + Content - - Content - AddingEvent.sequencediagram - - - Content - - - Content - - - Content - RemovingEvent.sequencediagram - - + Content @@ -56,7 +42,7 @@ Content DomainModel.classdiagram - + Content diff --git a/EventMaker/Design/EditEventFDUC.txt b/EventMaker/Design/EditEventFDUC.txt new file mode 100644 index 0000000..daa5441 --- /dev/null +++ b/EventMaker/Design/EditEventFDUC.txt @@ -0,0 +1,16 @@ +Use case name: Edit event +Scope: EventMaker +Level: Editing existing events +Primary Actor: User +Stakeholders and Interests: Marcin Zelent, extra functionality +Preconditions: App started successfuly, there is at least one event on the list +Success Guarantee: Previously created event's information changed +Main Success Scenario: User opens app, presses edit button on the chosen event, changes information on the edit page and saves the event. +Extensions: +A. User opens app, presses edit button on the chosen event but then he changes mind and presses the back button to return to the main page. +B. If user tries to save event with empty field show him error message and don't update the event. +C. The name of event can't be longer than 20 characters. +Special Requirements: UWP app, serialization to JSON +Technology and Data Variations List: None +Frequency of Occurence: Based on the will of the user +Miscellaneous: None \ No newline at end of file diff --git a/EventMaker/Design/EditingEventFDUC.txt b/EventMaker/Design/EditingEventFDUC.txt deleted file mode 100644 index 81f8439..0000000 --- a/EventMaker/Design/EditingEventFDUC.txt +++ /dev/null @@ -1,16 +0,0 @@ -Use case name: Editing event -Scope: EventMaker -Level: Editing existing events -Primary Actor: User -Stakeholders and Interests: Marcin Zelent, extra functionality -Preconditions: App started successfuly, there is at least one event on the list -Success Guarantee: Previously created event's information changed -Main Success Scenario: User opens app, presses edit button on the chosen event, changes information on the edit page and saves the event. -Extensions: -A. User opens app, presses edit button on the chosen event but then he changes mind and presses the back button to return to the main page. -B. If user tries to save event with empty field show him error message and don't update the event. -C. The name of event can't be longer than 20 characters. -Special Requirements: UWP app, serialization to JSON -Technology and Data Variations List: None -Frequency of Occurence: Based on the will of the user -Miscellaneous: None \ No newline at end of file diff --git a/EventMaker/Design/ModelDefinition/Design.uml b/EventMaker/Design/ModelDefinition/Design.uml index 32c7fe5..431f120 100644 --- a/EventMaker/Design/ModelDefinition/Design.uml +++ b/EventMaker/Design/ModelDefinition/Design.uml @@ -655,6 +655,24 @@ Id="3b814457-889b-410e-aad3-6a62b7007f73" name="ExecutionEvent" /> + + + + + + + - - - - - - - - - - - - - - - - - - - - - - Databinding to SelectedEventIndex - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \ No newline at end of file diff --git a/EventMaker/Design/RemovingEvent.sequencediagram.layout b/EventMaker/Design/RemovingEvent.sequencediagram.layout deleted file mode 100644 index eacd91a..0000000 --- a/EventMaker/Design/RemovingEvent.sequencediagram.layout +++ /dev/null @@ -1,224 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \ No newline at end of file diff --git a/EventMaker/Design/RemovingEventFDUC.txt b/EventMaker/Design/RemovingEventFDUC.txt deleted file mode 100644 index 1201c3c..0000000 --- a/EventMaker/Design/RemovingEventFDUC.txt +++ /dev/null @@ -1,13 +0,0 @@ -Use case name: Removing event -Scope: EventMaker -Level: Remove event from the list -Primary Actor: User -Stakeholders and Interests: Teachers, removing events functionality -Preconditions: App started successfuly, there is at least one event on the list -Success Guarantee: Removed event not present on the list -Main Success Scenario: User opens app and presses remove button on the chosen event. -Extensions: None -Special Requirements: UWP app, serialization to JSON -Technology and Data Variations List: None -Frequency of Occurence: Based on the will of the user -Miscellaneous: None \ No newline at end of file -- cgit v1.2.3