Proof of Sprint Meetings - SD-Group-11/ml-frontend GitHub Wiki
02/04/2021
Accomplished:
- Learnt Basic HTML and CSS.
Impediments:
- None
Plan to complete:
- Login.html complete
05/04/2021
Accomplished:
- Login.html complete
Impediments:
- None
Plan to complete:
-Registration.html and home.html
06/04/2021
Accomplished:
- Registration.html and home.html
Impediments:
-None
Plan to complete:
- Login.css
07/04/2021
Accomplished:
- Login.css
Impediments:
- None
Plan to complete:
- Registration.css and home.css
08/04/2021
Accomplished:
- Registration.css and home.css
Impediments:
- Implementing comprehensive css with home.css
Plan to complete:
- All javascript files
09/04/2021
Accomplished:
- Registration, LandingPage and Login .js
Impediments
- None
Plan:
-make documentation page
10/04/2021
Accomplished:
-Made documentation.html. documentation.css, documentaion.js
Impediments
-Bad variable naming caused big bug trying to apply lineargradient for background
Plan to complete:
Button to go back to home page
11/04/2021
Accomplished:
-Added back buttons to documentation page
-Editted css in some pages and made it better (made buttons line)
Impediments
- It took a long time to make the buttons line up and not be in the wrong spot
Yaseen:
02/04/2021
Accomplished:
-
Learnt Basic HTML.
-
Learnt Syntax.
-
Find documentation on HTML,CSS and Javascript.
Impediments:
- None
Plan to complete:
- Login.html complete
05/04/2021
Accomplished:
- Login.html complete
Impediments:
- None
Plan to complete:
-Registration.html and Landing page.html
06/04/2021
Accomplished:
- Registration.html and Landing page .html
Impediments:
- Wifi- went down which slowed down productivity
Plan to complete:
- Login css
07/04/2021
Accomplished:
- Login.css
Impediments:
- None
Plan to complete:
- Registration.css and LandingPage.css
08/04/2021
Accomplished:
- Registration.css and LandingPage.css
Impediments:
- Implementing comprehensive css
Plan to complete:
- All javascript files
09/04/2021
Accomplished:
- Registration, LandingPage and Login .js
Impediments
- None
Gryphon:
02/04/2021
Accomplished:
-learnt the basics of web dev including:
-Html
-CSS
- linking an html document to a JavaScript CSS file.
Impediments:
-None
Plan to Complete :
-Work on Login with Yaseen and zahraa
05/04/2021
Accomplished:
- Login.html complete
Impediments:
- None
Plan to complete:
- Work on the Registration.html and Landing page.html with Yaseen and Zahraa
06/04/2021
Accomplished:
- Registration.html and Landing page .html completed
Impediments:
-Difficulty with working collaboratively due to connectivity issues.
Plan to complete:
- Work on the CSS for the login page with Yaseen and Zahraa
07/04/2021
Accomplished:
- Login.css completed
Impediments:
- None
Plan to complete:
- work on the CSS files for the Registration and LandingPages
08/04/2021
Accomplished:
- Registration.css and LandingPage.css completed
Impediments:
- experience some issues with getting the layout of the landing page correct.
Plan to complete:
- create JavaScript files for the login registration and landing pages
09/04/2021
Accomplished:
- JavaScript for the Registration, Landing Page and Login pages complete
Impediments:
- None
Plan to complete:
-learn how to use travis ci for continuous implementation of JavaScript files
Fatima:
02/04/2021
Accomplished:
- Learned the basic idea of the Naive Bayes Model covered in class.
Impediments:
Plan to complete:
- Find resources online about the Naive Bayes Model.
05/04/2021
Accomplished:
- made summaries of the Naive Bayes theory
Impediments:
Plan to complete:
- Research how to implement the Naive Bayes model.
06/04/2021
Accomplished:
- Summarize research on implementation of the Naive bayes model.
Impediments:
Plan to complete:
- Compile document.
07/04/2021
Accomplished:
- Summaries compiled into word document
Impediments:
- Referencing
Plan to complete:
- Make sure document is properly referenced
08/04/2021
Accomplished:
- Research document mostly complete
Impediments:
Plan to complete:
- Look for anything that might be important to add and compile
09/04/2021
Accomplished:
- Document completed
Impediments
Back-end Research
Friday 2nd:
Ziyaad:
What’s been done?
The task of Research for backend was received
What problems were there?
I was quite unsure of the implementations that we were going to research
What is going to be done?
We are going to get a very basic understanding of how the backend is going to be structured
Jeremy:
What’s been done?
We have been assigned to researching the backend structure of our platform
What problems were there?
Nothing from my side
What’s going to be done?
I am initiating the research to see what options are available.
Monday 5th:
Ziyaad:
What’s been done?
I have gained a basic understanding of the solutions to our problem
What problems were there?
Nothing this far
What’s going to be done?
Continuing the research for more understanding
Jeremy
What’s been done?
I have completed a slight amount of work
What problems were there?
I misunderstood certain natures of our platform and what solutions were needed.
What’s going to be done?
I am going to gain a better understanding of the nature of our platform
Tuesday 6th
Ziyaad
What’s been done?
Minimal work was done yesterday
What problems were there?
I was consumed with other work
What’s going to be done?
Continuation of research
Jeremy
What’s been done?
I have gained an understanding of how our project is working
What problems were there?
Nothing for now
What’s going to be done?
I am going going onto research the existing solutions.
Wednesday 7th
Ziyaad
What’s been done?
I have looked into different database management systems
What problems were there?
I am not too certain as to how to implement these solutions
What’s going to be done?
Finding the implementation of these solutions
Jeremy
What’s been done?
I have looked into different languages for databases
What problems were there?
It is quite complex
What’s going to be done?
Learning how to use these languages and queries properly
Thursday 8th
Ziyaad
What’s been done?
I have looked into frameworks that’ll be suitable.
What problems were there?
Finding frameworks that work best for all our needs are hard to come across.
What’s going to be done?
Continuation of finding a framework
Jeremy
What’s been done?
I now understand how the databases/DBMS and queries operate and how we’d use them
What problems were there?
No much to report
What’s going to be done?
Collaborating with Ziyaad to combine our knowledge base.
Friday 9th
Ziyaad
What’s been done?
Found out the implementation and use of Django
What problems were there?
Nothing
What’s going to be done?
Concluding the research
Jeremy
What’s been done?
Joined forces with Ziyaad to put all our information together
What problems were there?
It took a while to explain our points to each other
What’s going to be done?
Finalizing our document
Monday 12th
Ziyaad
What’s been done?
The document has been finalized
What problems were there?
It took quite some time to compile it all
What’s going to be done?
Submit the work
Jeremy
What’s been done?
Completed the tasks
What problems were there?
Nothing much
What’s going to be done?
Submitting our tasks
Michael:
Friday, 2nd April 2021
Since the client suggested the software be a desktop application, Talion and I being responsible for researching frameworks we will use, I looked into python desktop frameworks that could potentially be used for creating the frontend such as PyQt, Tkinter, Kivy and more, it was difficult to make full comparisons between frameworks and how they might relate to our desired application. The next step would be to find which would be most ideal, if applicable.
Monday, 5th April 2021 Upon more research, the most viable frameworks for creating python GUIs relevant to our machine learning application would be PyQt and Tkinter, however, we decided against creating the frontend using python since it is limited in creating beautiful, modern frontend GUIs. It was challenging to try to find ways to make it possible to use python alone for the full stack. Next I will look into ways to integrate python with another language for GUIs.
Tuesday, 6th April 2021 Since the suggested platform was for a desktop application, I looked into frameworks that could be used to integrate python as the backend with another language that could be used for the frontend, specifically for desktop applications. The main frameworks considered were Eel and Electron, which allow the integration for a desktop application, rendered in the browser and designed using HTML, CSS and Javascript. The impediments were to understand how Eel could be used since its documentation is limited and not as popular compared to Electron. Electron seemed to be the better option.
Wednesday, 7th April 2021 We decided to look into python web frameworks since creating a web application instead of a desktop application is more viable, these included django, Flask, CherryPy, Pyramid, Grok, TurboGears and Web2Py. The obstacles faced were trying to learn how web frameworks work and how they can be used and understanding the terminology. On thursday I continued to do research into it. Thursday, 8th April 2021 Yesterday I got a better understanding of Django , I had no impediments.Today I will do a comparison between Django and Flask web frameworks. Friday, 9th April 2021 Yesterday I found that Django will be better suited for the application than Flask since it is faster to release features once you’ve gained an understanding of the implementation and also due to its versatility and scalability. I struggled to find clear, concise comparisons between the two for the roles they would play within the application. Today I will investigate REST APIs and Django’s REST API and understand how it can be implemented.
Meeting Minutes
Introduction The following is the minutes recorded of the meetings conducted during the first sprint of members with the following roles Product Owner - Mr. Jiahao Huo Scrum Master - Michael De Carvalho (1852684) Scrum Development Team Jeremy Crouch (1598024) Talion Naidoo (1448771) Ureeshah Moodley (1600076) Yaseen Haffejee (1827555) Ziyaad Ballim (1828251) Fatima Daya (1620146) Phoenix Krinsky (2233063) Zahraa (2115850)
Backlog Refinement Meeting and Sprint Planning Meeting (08/04/2021) During the first meeting with the product owner, we conducted both the sprint backlog and sprint planning meeting with the goal of forming the product backlog as well as committing the top priority PBIs to the first sprint and breaking each user story into tasks. Backlog Refinement Meeting: During the backlog refinement meeting several possible PBIs were mentioned, such as: Create a login, Registration and home page. Implement Linear Regression model to train data Implement Naive Bayes model to train data Create graphical model visualisations for the user to be able to interpret their data Allow users to adjust hyper parameters of the training models in order to influence factors such as learning rates. Create tutorials or instructive help buttons to guide the user to understand how the software works Save their models to a directory as well as load their models from that directory. Due to the nature of the project, however, upon refinement it was decided that special types of user stories based on research, named Spikes, would be the main priority in order to first understand the problem domain in order to implement the software solution, these include researching the frameworks that would be used, basic machine learning models and their implementations as well as a basic frontend such as login and registration and so the above bulleted features would not be as important for this sprint.
Sprint Planning Meeting: Now that the main product backlog had been refined and the main areas of importance defined, the PBIs could be committed to the first Sprint. The user stories that were constructed include: Decide on a framework Research backend implementation Login frontend Registration frontend Home page frontend Since the main items had been committed to the sprint, they could now be broken up into tasks in the following way: Decide a framework Deciding a framework was broken down into the following tasks Researching potential frameworks that would be used for python applications Choose the framework Backend Research Backend was broken down into the following tasks: Research different databases Refine options for the managements system Naive Bayes Model Research The following tasks were constructed: Research existing code implementations Research the theoretical model
Registration Was broken down into the following tasks: Make the User interface of the registration page Once registration button is pressed, the user should be moved to the login page
Login Was broken down into the following tasks: Make the User interface of the Login page Once login button is pressed, the user should be moved to the home page
Home Page Was broken down into the following tasks: Make the User interface of the home page Create the layout and elements of the home page