We have a short meeting about the intergration week where we plan what should we focus on and when we need to finish it. We have also planned we will be having a group meeting everyday at noon to make sure everyone knows what they are doing.
Have the flashcard classses done. JavaDoc and comments added as well.
We had a generalgroup meeting that the project manager and QA manager follow up on what we have done and what needs to be done.
continue drawing sequence diagram.
I drawed the sequence diagram using draw.io website.
In this meeting, we had disscuss about who work on which part of the document.
In this meeting, we had look through the User Interface Documentation feedback. We had also disscuss about the design specification. I need continue to work on the sequence diagram. More spike work needed to be done for the design specification standards.
I spent some time understanding how a sequence diagram should be from Visual Paradigm, etc. Image below is a draft of the sequence diagram base on the welsh vocabulary app.
In this meeting, the testing team have presented a draft of the testing specification. Feedback was given during the presentation. They need to change the format of their document in order to meet the documentation standards. Functional requirements should be also added into the test table. The test table should be no more than 50 test, but if test that needed to add into the test table, repetition test can be taken out. There are couple more things that need to be change as well.
For the design team where I am in it, more spike work need to be done. For example, UML Diagram, Sequence Diagram, documentation, etc.
In this meeting, we have talk about the class design which Konstancja will draw the UML diagram and I will draw the sequence diagram. Kassy did not attend this meeting, but she is doing the document and adding some other posiible test. We also reviewed the final version of the User Interface design and there is a small change where the changing language button need to be. The current button is blocking two row of the words.
This meeting is to review the User Interface. Taavi presented an initial development version of the Use Case document. Mariusz presented teh initial development version of the User Interface presentation with some animation of the program. Although the program is working, but there will be a further change for the code which will have a better software architecture and data structure.
Have a small progression on the design specification standards. Ubderstanding the format of the documentation for Design Specification Standards. Writing what is the introduction, scope and the objective of design specification.
I cloned the respository from git lab which created by Mariusz and packages are created according to the project requirements. I also wrote a Readme.md on how to clone and get it work on local machine so everyone can look through the project.
Successfully read JSON file using simple google Json. Fixed error that I should be using String instead of Json Object.
In this meeting, there is some spike work done on the User Interface and the class design. We have all agreed that Mariusz is the project leader, Taavi is the deputy project leader, Sophie is the QA manager, Kassy is the Deputy QA manager. Separate meeting from the tutorial will be conducted on Mon at 10:00 in the morning and Wednesday at 13:00. For the class design, there is an ongoing discussion on how the words are stored and sorted. We have also choose to have one singular Word object for both language variants. Concerning matters will be discussed in the next unofficial meeting which will be on Monday. There is a roadblock for testing currently due to the incomplete User Interface.
This is the first group meeting outside the schedule. All of us meet at the Think Tank area and start discussing about the design of the User Interface, class design, improving testing file after use cases are finalised to reference each use case, less general on the test but make more test cases and be more specific on each test case, when should we have meeting, etc.
For the User Interface, Mariusz suggested all of us give some idea and if we have spare time, design the UI as well which we will get a variation of choices. We will choose the most agreed design for futher implementation. We also agreed that we will use just only one class for the word instead of English class, Welsh Class. There will be a futher change if there is some problem when implementating it to the program.
Trying to get read the JSON file. There are multiple way to read and write a JSON file such as json-simple, Gson, Jackson, etc.
We all has agree that we will have meeting at 13:00 at Wednesday in the Think Tank, Llandinam area. Meeting time is going to be rush since Sophie, Martynas, Mariusz and I are going to the GitLab workshop at 14:00. The rest of the team will continue discuss and we will follow up what we have missed.
In this meeting, Taavi has presented the draft of the User Interface. Kassy and I presented the Design Specification Standards. There is nothing much we could present which we do not have enough information. Kassy and Martynas presented Test Procedure Standards as well. Project manager, Bernie suggest that we could add something that is more specific to the test. Since three of the members unable to attend to the tutorial due to personal problem, Sophie will plan to have a group meeting which everyone needs to be there to brainstorm some ideas and suggestion.
Different ideas were shared and discussed which we agreed to use binary tree data structure for the storing and searching the list of words. The first draft of the UML diagram was created and will discuss what we are missing for the class in the next tutorial. I and my team had also created a google doc for the Outline Structure document which is not fully complete where we do not have enough and full details of the User Interface for the moment.
Understanding what are the objectives and requirements is important. I have read the SE.QA.05 - Design Specification Standards and the SE.QA.09 - Java Coding Standards. I acknowledge that for the objectives of SE.QA.05, it is to aid the production of a design specification which is a complete and accurate translation of the client's requirements.
I and my team member had decided to meet on the 6th of February at 12:00 in the library - Hugh Owen to discuss what algorithm, data structures, class, etc. need to be used. For the SE.QA.09, we have decided to use google docs which all of us who are working on the document can edit the same document and we could get a better scope for it.
Our group decided to use Discord for group communications. I have volunteered for the role of SE.QA.05 - Design Specification Standards and start to draft class designs and conduct spike work on main elements such as reading JSON files, deciding which data structure we should use for storing, searching in the list of words. On the other hand, I have also volunteered for the role of SE.QA.09 - Java Coding Standards which it covers the standards to which Java source code must be produced.