brotenko / qualityquest Goto Github PK

The StoryFlow is too big to fit into the PDF, since it doesn't wrap around pages. It needs to be split up into "DIN A4 friendly" snippets.

Create diagrams for each transition between two "states" in the StoryFlow diagram are to be defined. All possible dialogue options and relevant characters should then be incorporated into those diagrams.

Do these in any order:

• Change (almost) all <\br> to <\span>.
• Skim the documents for typos and inconsistencies and fix those.
• Fix the links in the ToC of the Change history.

Please do these tasks in order:

• Create a seperate document/folder (of any kind) for collecting the ideas.
• Create a collection of possible game design and story/dialouge ideas.

Erste Begriffe definieren

Create a document in which the team can collect random ideas that might or might not be relevant for the game at some point.

Do these in any order:

• Glossary: DiceRandomness: Change "die" to "dice"
• Functional Requirements: Offline-Mode: Change "the Moderator must be given the option to continue the game offline." to "the Moderator shall continue the game offline."
• Used Plugins: Markdown All in One: Change "Virtual Studio Code" to "Visual Studio Code".
• Used Plugins: PlantUML: Change "Virtual Studio Code" to "Visual Studio Code".
• Glossary: Session: Create a new entry for "Session" is the Glossary.

Do these in any order:

• The class diagram does not show a fallback class/component that simulates the server or rather switches to offline mode if the game must continue in offline mode.
• The component diagram for the server is still missing and should be added.
• Refactor the architecture diagram into the Technical Specifications.

Update the following diagrams (See the feedback document):

• Server
• Moderator-Client
• Component-Overview

Do these in any order:

• Fix the numbers of functional requirements, since those are a bit out of order
• "FA" (Funktionale Anforderung) and "QA" (Qualitative Anfoderung) need to be renamed
• Create sub-categories for the requirements similar to the NewTec docs

Update the following requirements (See the feedback document):

• FA2
• FA6
• FA12
• FA15
• FA16
• FA17
• FA19
• FA22
• FA23
• FA25
• FA26
• FA27
• FA28
• FA29
• FA30
• FA32
• FA33
• FA34
• FA35
• QA7

Finding a solution to convert the .md files into a .pdf.

The diagrams and descriptions should be fixed to be exactly as described below:

Start Application:

• Diagram: Moderator (as Actor) -> Start Application (with Moderator-Client as system boundary) -> Server (as Actor)
• Description: The old diagram shall be converted into textual form and thus serve as the new description for the diagram.

Play Game:

• Diagram: "Can Pause" shall be changed to "Pause Game".
• Description: The description should specify that when the game is paused, a message is sent to the server, which will then ensure that voting is paused if it is currently takes place.

End Application:

• Diagram: Moderator (as Actor) -> End Application (with Moderator-Client as system boundary) -> Server (as Actor) -> End Session (with PlayerAudience-Client as system boundary) -> PlayerAudience (as Actor)
• Description: The description should describe the process of ending the game on the moderator's side, going through the server, ending up at PlayerAudience, and what exactly happens.

Do those steps in any order:

• Update component diagram descriptors.
• Add Server-Client component diagram.
• Class diagrams with focus on interfaces.

Do in any order:

• Check for changes and errors.
• Update/Fix the errors and changes

There have been major changes in the architecture that can be seen in the class diagrams in #64.

Change the "Christmas Party" state into something more inclusive. Either come up with a Christmas alternative that would fit into the fantasy universe or simply use something like "company party".

Check these up in any order:

• Requirements
• Glossary
• Use-case diagrams
• Architecture diagrams
• StoryFlow diagram
• UsedTools document
• ToC / Index of TS
• Changelog

Checked by:

• Alex F.
• Alex P.
• Elias
• Manu

Please do these step in order:

• Create a seperate document (with MkDocs) to fill with the data.
• Create a list of options with the required data (see below).

Required data:

• Pros
• Cons
• How can it be integrated?
• Links/Ressources
• Monetization method
• Others

As discussed in the review of PR #64, more precisely this comment, following entries have to be reconsidered:

• Voting-Tool: Obsolete or not?
• StoryBranches: Update description?

Do these in any order:

• Add missing Tools/Plugins/Libraries.
• Add version numbers for all "Tools".
• Add description of what the respective "Tool" is used for.

Please do this step first:

• Transfer documents to MkDocs

Do those steps in any order:

• Update Glossary
• Update Requirements
• Add Changelog
• Add Table of Contents
• Add UsedTools-Document

Update the following terms in the glossary (See the feedback document):

• Moderator-Client
• StoryFlowDecision
• DiceRandomness
• Voting-Timer

Mit draw.io/plantUML die Diagramme für die bereits definierten Use-cases malen

Fix these descriptors for the following documents:

• Glossary
• Requirements
• Use-case diagrams
• Architecture diagrams

https://github.com/Brotenko/QualityQuest/blob/master/Docs/Protokolle/docs/sprint-reviews/review_2020_09_18.md#issues-to-fix

Please do these in any order:

• Integrate into Pflichtenheft
• Add text to use-case diagram
• Add text to StoryFlow diagram

Add changes agreed upon with customer.

The completion of the architecture design is nearing completion and for that a PDF version of the Technical Specifications is needed.