marcleclair / mini-cap-anymemo Goto Github PK

#9

[SP:3]
[Priority: Medium]
[Risk: Medium Value: High]

Task 1: Add the mockup for the dialog box (30 mins)
Task 2: Modify the dialogue box (commits are directly tagging this US with #91) (5h)
Task 3: Update the notification box in order to lead the user to the app when they click the notification box. (commits are directly tagging this US with #91) (2h)
Task 4: Acceptance test (See below)

Acceptance test:
Preconditions:
The app is launched and on the opening page.
There is at least one deck of card available.
The deck of the card should not be empty.

• if users in step 9.3 choose the current day, the user will receive a notification within 5min
• if users in step 9.4 choose the "add number of days" radio button, the textbox for the number of days is generated.

[SP:3]
[Priority: Low]
[Risk: Low Value: Medium]

This is a task for US 18 (#101)

• Add a column to the database that will hold the string that represents the tag

[SP: 5]
[Priority: 2]
[Risk: High value, medium risk]

Tasks:

1. Back-end (5h)
2. Front-end (5h)

20h

Fix Regex Expression to accept all links

Enables a daily study mode which lets users choose a certain of number of cards to go through every day.

[SP: 21]
[Priority: High]
[Risk: High value, High risk]

Divided into 3 US, which are #71 #63 #50

Preconditions: The app is launched and on the opening page (Recent)

• if users in the step 9.3 choose the current day, the user will receive a notification within 5min

[SP: 2]
[Priority: Medium]
[Risk: High value, low risk]

With all the new hints we've added, the class is slowly reaching 2000 LOC. There's a lot of code in there that can be condensed / eliminated.

This is a task for US 21 (#104)

• Set a flag date to determine when a card has been read (ie. answer has been seen by user)
• This allows pushing any unfinished cards to the another day by showing a dialog box before a user starts working out (See US21 for mockup of the dialog box #104 )

[SP: 3]
[Priority: medium]
[Risk: low, Value: high]
Task1: Implementation for the statistic #112
Task2: test #113
Task3: acceptance #124
Mockup:

[SP: 5]
[Priority: high]
[Risk: Medium, Value: High]

Task 1: Set a flag in the DB for cards that have been done in a workout (#105)
Task 2: Create a Dialog fragment appearing before a workout if there are incomplete cards from past day(s) (#108)
Task 3: Create unit tests for newly added methods (#111)
Task4 : Acceptance test (#123)

[SP: 3]
[Priority: Medium]
[Risk: High value, low risk]
Tasks:
#46
#47
Acceptance Test: #43

2h

This is a task for US 18 (#101)

• Add a button in the more dropdown menu of DBs that will allow the user to tag it
• Add a button in the misc tab that will take the user to the tag list

[SP: 3]
[Priority: 2]
[Risk: High value, medium risk]

Tasks:

Back-end (5h)
Front-end (5h)

Preconditions: The app is launched and on the opening page (Recent)

Case1:

Case2:

#8

[SP: 8]
[Priority: High]
[Risk: High value, high risk]
20h

• Unit test

Create a dialogue box containing the following:
Task1: #49 (Mel)

• Submit button to add the deck to workout mode
• Calendar to allow the user to chose a start date
• Field to let the user chose the number of days they want to study all their cards

The submit button will:

• Change the learningDate column in Cards

Task2: Notification #72 --(Wei)
Diagram is in the Wiki: https://github.com/MarcLeclair/Mini-Cap-AnyMemo/wiki/Diagrams
Acceptance Test: #43

[SP: 2]
[Priority: 1 ]
[Risk: Low risk, high value]

Task:

1. Test and document the black-box test cases

This task is for US 21 (#104)

• Newly added method for the reschedule dialog box functionality are to be tested

[SP: 3]
[Priority: 2]
[Risk: high risk, high value]

Task 1: Setting up Jenkins + Slave Server story (2h)

Enables shuffling for cards in the active deck

[SP: 0]
[Priority: 1]
[Risk: Low value, Low risk]

This task is for US 21 (#104)

• Create a Dialog Fragment Launcher for showing the "Incomplete workout" dialog
• Create an xml layout for the incomplete workout dialog (view mockup #104)
• Display this dialog box right before a study session if there are incomplete cards from the day(s) before
• If the user decides to skip the cards -> reset the card's date to 1/1/1 (flag for finished card)
• If the user decides to "ask tomorrow" -> reset the card's date to yesterday
• If the user decides to reschedule the cards (could be today) -> reset the card's date to today/future date depending on the day they picked

15h

#8

Adding a hint button to the front end such that the drop down doesn't need to be used every time a hint is requested. Improve usability and how intuitive the app is.

[SP: 2]
[Priority: 1]
[Risk: Low value, low risk]

Acceptance test:

Preconditions: The app is launched and on the opening page (Recent)

US5.2: As a user I can get a multiple choice question for the hint

Preconditions: Steps 5.1.1 to 5.1.4 have been done.

US5.3: As a user I can display a picture for the hint

Preconditions: Steps 5.1.1 to 5.1.4 have been done.

Case1:

Case2:

*The step 5.1.5 can be done multiple times for the letter hint and multiple choice hint

Functionality users utilize to have multiplayer match with another person using the AnyMemo app.

[SP:21]
[Priority: High]
[Risk: High Value: High]

US 15.1:As a user, I can see a new tab for the game.
Task1: Create new tab to lead to multiplayer activity (#115)
Task 2: Create server connection (#116)
Task 3: Create client connection (#117)

US15.2:
As a user, I can connect my game to another client.
Task 4: Make sure those two interact and client can update server and so can the server update the client (#118)
Task 5: Create game room fragment (#119)
Task 6: Compare both phones DB (#120)

Minor fixes that will be implemented in order to improve the user experience.

[SP: 2]
[Priority: 1]
[Risk: Low value, low risk]

Precondition: User wants to display the answer by showing one random letter at a time

[SP: 5]
[Priority: High]
[Risk: High value, High risk]

Unit tests:

• Add to Favourites
• Letter Hint
• Multiple Choice Questions Hint
• Card
• Setting

Espresso tests:

• Letter Hint
• Multiple Choice Questions Hint
• Picture Hint
• Spelling Test Hint
• Add to Workout Mode Dialogue Box

Bug overview:
When trying to view the card list from a chosen database, the app crashes and closes down.

Steps to reproduce the bug:

1. Go to the list of databases tab (2nd tab from the left).
2. Select a quiz.
3. Choose Card List.

Expected result:
Being able to see the list of cards that the database contains.

Actual result :
The app crashes and closes before being able to see the list of cards.

[SP: 0.5]
[Priority: 1]
[Risk: Low risk, high value ]

Tasks:

1. Explain issues we encountered while trying to setup the environment to run the app (1h)
2. Explain what steps were followed to do the setup (1h)

[SP:3]
[Priority: Low]
[Risk: Medium Value: Medium]

[SP: 5]
[Priority: 1]
[Risk: High value, low risk]

Tasks:

1. Class Diagram (1h)
2. Architecture Diagram (2h)
3. Layered / domain diagram (1h)

#8

[SP: 2]
[Priority: High]
[Risk: High value, Low risk]

Time: 5h
#103

[SP: 5]
[Priority: low]
[Risk: low, Value: medium]

The user can create Custom Tag folders, inside that "Tags" folder, and they're able to add databases to said folder.

-By long holding the database, an option menu will pop out
-The user clicks on add tag
-The app will ask him to add a tag name
-The app will create a tags folder in wish a folder is created with the desired name, and the chosen database will be cloned into that new folder.

Preconditions: The app is launched and on the opening page (Recent)

Case1:

Case2:

Grading Scheme | Grade on 25

Planning

• Done enough work? 2
• Story points, Risk, Priority 2
• Task breakdown 2
• Assigned to individuals 1
• Plan for next release 1

Arch and Design

• Overall arch and layers/Domain and class diagram 2
• Mockups, etc 1
• Using best practices for framework 1

Code

• Change logs describe evolution with references 2
• Code review 2
• Coding style enforced 1
• Quality of code in key classes 3

Testing/Validation

• All stories tested (basic tests) 1
• Quality of tests 3
• Continuous integration 1

14h

20h

Enables a spell check mode on the cards to compare with card answer. In other words, the user should be able to use spell check mode to enter the text for answer he thinks is right ( For example Question Card displays: Head --> User will have a field to enter his answer "La Tete").

[SP: 5]
[Priority: Low]
[Risk: Low value, Low risk]

• Add UI for user to choose the option.
• Add user input box
• Create backend logic to verify input vs. card answer
• Connect front end and back end
• Create Espresso test for UI

Preconditions: The app is launched and on the opening page (Recent)

Case1:

Case2:

Case3:

#9

[SP: 8]
[Priority: High]
[Risk: High value, high risk]
Tasks: #48
Acceptance Test: #43

time: 2h
#103

[SP: 8]
[Priority: 1]
[Risk: High value, low risk]

Tasks:

1. display a random letter (20h)
2. display a picture (10h)
3. give a multiple choice question (20h)
4. fornt-end (10h)

US5.1: As a user I can display a random letter for the hint

Preconditions: The app is launched and on the opening page (Recent)

US5.2: As a user I can get a multiple choice question for the hint

Preconditions: Steps 5.1.1 to 5.1.4 have been done.

US5.3: As a user I can display a picture for the hint

Preconditions: Steps 5.1.1 to 5.1.4 have been done.

Case1:

Case2:

10h

#8

For both question and answer

[SP: 2]
[Priority: medium]
[Risk: Low Value: Medium ]

Preconditions: The app is launched and on the opening page (Recent)

Case1:

Case2:

Case3: