Project Plan - L6mps/LasaLaraAP GitHub Wiki
Project Roles
-
Ants-Oskar Mäesalu
Team leader, back-end, Android architecture
-
Mattias Nurk
Front-end, design
-
Kaspar Kesli
Back-end, front-end and back-end link-up
-
Joosep Heinmets
Front-end, tester
Communication Means
-
The team
Meetings, Facebook conversations, phone conversations, Skype
-
The client
E-mail, weekly meetings (Thursday at 16? - needs to be specified), Skype
-
The coordinator
Weekly meetings (Monday at 09:00)
Work Process
-
The customer will understand what we are building thanks to regular meetings where we elaborate on what we’ve done in the past week and show him the results of our work, e.g. screen designs, working prototype etc.
-
Whether our solution proposal is accepted by the customer is determined through critical thinking in the planning phase and regular demonstration of our work directly to the customer.
-
The accepted solution will be built with guidance from our course lecturer Üllar Lindmaa and client Thomas Narbeshuber.
-
Oskar as our team leader will assign the tasks requiring completion.
-
The front-end will be implemented by Mattias and Joosep, the back-end by Oskar and Kaspar
-
The code review and test writing will be done by Joosep who will then verify if our product acts like we have intended.
-
The product will be validated when meeting the customer.
-
-
We consider something ready to be published to the customer for review when we have coded and tested the software part in question.
-
We gather feedback from the customer through weekly meetings where we listen to his remarks and write down his comments.
-
A task is “DONE”, when it has been developed and tested. However, this is subject to change as a task may be reopened in following iterations.
Scope
Iteration 1
-
Functional Requirements (Oskar, 3h)
-
Non-Functional Requirements (Joosep, 5h)
-
Project Plan (Everyone, 10h)
- Work Process (Mattias, 5h)
-
Collaboration Infrastructure - VCS (Kaspar, 2h)
-
Collaboration Infrastructure - Wiki (Kaspar, 2h)
-
Collaboration Infrastructure - Issue Tracker (Kaspar, 2h)
Iteration 2
Front-end
-
Views
-
Book selection (Mattias, 15h)
- Overall progress bar
-
Chapter selection (Mattias, 8h)
- Book progress bar
-
Back-end
-
Android app architecture (Oskar, 8h)
-
Content
-
Structure (Oskar, 8h)
-
Books
-
Chapters
-
Questions
-
-
Web requests (Oskar, 8h)
-
Retrieval
-
Proposal
-
-
Storage with SQLite (Oskar, 12h)
-
Books
-
Chapters
-
Questions
-
-
Back-end & front-end linking (Kaspar)
- Android activities
- Android fragments
Iteration 3
Front-end
-
Views
-
Question screen (Mattias, 40h)
-
Chapter progress bar
-
Question view
-
Answer view
-
“Did you know the answer?” buttons
-
-
Settings screen (Mattias, 10h)
-
Reset Progress
-
Page View option
-
Switch Question/Answer
-
Scramble Question Order
-
Propose Question
-
-
Content update
-
Back-end
-
Optimisation (Oskar, 15h)
-
Web requests
-
Internal storage
-
-
Settings (Oskar, 10h)
-
User progress storage
Iteration 4
Front-end
-
Views
-
Sign-up
-
Login
-
Content update
-
Back-end
-
Content
- User structure
-
Functionality
- Sign-up
-
Login