Below is the tasks completed throughout the work day:

Make sure the git is ready for submission. (Completed 12:30 am)

Update the config reference file. (Completed 1.45pm)

Ensure all the documents are up to Qa standard. (Completed 4:14pm)

Worked all day. Below is the tasks throughout the day and their completion time:

Finished updating the issues on GitLab (11:10 am).

Made templates for the system tests and modular tests. (1:30pm)

Ran all current JUnit tests. (2:30pm)

Created a modular test doc for today 30/04/20. (4:03pm)

Worked all day. Below is the notes taken through out the day and the timestamps:

Finished updating issues on Git – 10:26 am.

Git Repository looks good. Added folders into dev that correspond with every day we had a meeting. This should have been updated throughout the project

Added files into the weekly dev folders from old uploads to the git. (2:34pm)

Worked all day. Below is the notes taken throughout the day along with time stamps:

Finished updating issues on the Gitlab 11am.

Decomposition Description:

1. Added cell classes, WordType and TestResults to the significant classes.
2. Updated class mapping.

(Finished 1:30 pm)

Created a txt file to record software builds and tests failed. (Finished 2:20 pm)

Reviewed the test spec document. Everything is in line with QA 06. All the changes are what Chris requested. the only thing I need to clarify with das82 is what is meant by repeatable tests. (Finished 3:10pm)

Reviewed new code:

1. Class/variable names fine.
2. All words in American English.
3. Indentation correct.
4. Layout correct i.e Variables/constructor/methods all in correct order.
5. Some java docs missing.
6. Still need to fix package name.

Below is the notes taken through out the day along with time stamps when the tasks were completed.

Finished adding to do list as issues on the git lab at 10:27am.

When checking the code against the QA a few things I noticed:

1. Packages must start with uk.ac.aber.cs221.group03.
2. Each file should have a simple header giving the filename, a copyright message, and the version and date. (This will be completed with the java docs).

Apart from that everything seems inline with the QA standards. Really clean work. (Code check finished 11:45).

According to the QA 10 doc the test report does not need an introduction. Instead I have created the layout of the report along with the tables of the system tests and module tests (Finished 11:17 am).

Leaving the java docs until the changes made last time are checked/corrected.

Looked through UI spec and mock up. Everything is according to QA.04. (2:30 pm)

Prepping work for integration week. Going through java docs to see what needs changing. Had a meeting on the code and what will need changing next week.

Looking at java docs -1 hour

Going through QA. 10 to see the testing report requirements – 2 hours

Meeting about the code – 1 hour

This week as there was very little work for the QA manager, I was assigned with helping the architecture team create java docs.

Writing java doc comments and generating the java docs – 4 hours

With the UK in quarantine all meetings moved online. The formal review for the design document was done this week, as well as an informal meeting to show members not on the architecture team how the code functions.

Formal review of design document – 2 hours

Architecture meeting – 1 hour 30 mins

Downloaded code and set up Intellij ready to edit java docs – 1 hour

This week I followed up on QA feedback from the test document review. I also created issues on the Gitlab according to the rest of Chris’ review. I went through the updates Merlin made to the UI use case document and PowerPoint. I again compared this to the feedback we got from our Project Manager. Lastly, I ensured I was ready for the design specification review.

Updating Repository – 1 hour

Checking UI Documents – 2 hour

Creating issues – 1 hour

Going over design specification lecutures and QA . documents – 1 hour

This week was a slow week as no review of documents were needed. I followed up on the previous review of the testing document from Chris. I also prepared for the design document review for next week.

Created a config reference document for the repository – 1 hour

Prepared for the design document review – 2 hour

This week was the group needed a full test document sheet ready to be forwarded to Chris, so we organised a formal testing document review. This was done on the 26/02/20. After the review took place, Halvor took charge in showing us how to use the Gitlab repository. I then focused on looking at the other SE.QA docs in preparation for the design document.

Formal testing document review – 2 hour

Gitlab repository session – 1 hour

Preparation for the design document review – 2 hour

This week the formal review of the UI Document was due. The review was conducted on the 19/2/20 and minutes were taken by me to report the errors and what the document was lacking. Also during this time two members of our group were still not signed up to gitlab so I followed up on that. Lastly I looked over SE.QA.06 – Test Procedure Standards as that will be the next document due for review.

Formal review of UI document – 2 hours

Revising SE.QA.06 and SE.QA.07 – 2 hours

This week I was assigned the tasks of attending the git lab practical and preparing for the formal review of the UI document:

Git lab practical – 2 hour

Formal review prep – 2 hour

I have been assigned the task of QA manager for the project. As there is no work currently finished and waiting to be processed by QA, I have spent time going through all the QA documents to prepare.

3 Hours – Going through all the documents and taking note of what I am looking for when assessing a piece of work. I have especially focused on SE.QA.04 (the user interface document) as this is the first section of the project that will be reviewed.

1.5 hours – Creating main blog to hold all individual blogs and creating my personal blog.

1 hour – Looking through and taking notes of SE QA.01, SE QA.02 and SE QA.03.

During the meeting I was assigned the task of starting a group blog and coordinating everyone’s individual blogs. As this was a small task, I was also assigned to read through SE.QA.01 – Quality Assurance Plan, SE.QA.02 – General Documentation Standards and SE.QA.03 – Project Management Standards.