CS221 Week 7

[:en] Prior to the weekly tutorial, the group received feedback on the submitted Test Spec. Much of it referred to QA matters. Besides that the major concern was discord between the Test Spec and the UI Documents, which was amended by Aaron updating the UI Documents. After the weekly tutorial, the group had a particularly long (2-3 hrs) in which we chiefly discussed the Design Spec. I was assigned to help Nathan with composing Component Diagrams for the document.

On Friday we first compiled a list of all public Methods that are necessary in the design, and the Classes which initialise and access these methods. Nathan formed that list into a draft of component diagram using Adobe Photoshop, which I then formalised into proper UML using draw.io. This took around an hour.

The same day, the group had a review meeting for the Design Spec, presenting the work we had done. Following that meeting, my next task was to continue the progress that Bartosz had made on Sequence Diagrams for the Design Spec. Initially I was to modify the existing sequence diagram to reflect the changes made to the Use Cases in the UI Doc, but we decided the original diagrams were satisfactory. So, I made an additional diagram demonstrating the process of pausing/unpausing in the program. After that, I wrote short summaries describing each of the sequence diagrams we had made. Including time taken to further familiarise myself with the code, I spent approx 3hrs on this task.

On Tuesday, the group held the QA Review meeting for the Design Spec. I attended, and spent additional time after the meeting proofreading the doc and helping to configure the LaTeX file. Time spent: approx 3 hrs.

Total time spent this week: ~10 hours. [:de]After the weekly tutorial, the group had a particularly long (2-3 hrs) in which we chiefly discussed the Design Spec. I was assigned to help Nathan with composing Component Diagrams for the document.

On Friday we first compiled a list of all public Methods that are necessary in the design, and the Classes which initialise and access these methods. Nathan formed that list into a draft of component diagram using Adobe Photoshop, which I then formalised into proper UML using draw.io.

The same day, the group had a review meeting for the Design Spec, presenting the work we had done. Following that meeting, my next task was to continue the progress that Bartosz had made on Sequence Diagrams for the Design Spec.[:]

CS221 Week 6

[:en]Having submitted the Test Specification last week, Nathan and I have started to transition to new roles on the project. The element of principal concern is the Design Specification, a full draft of which we need to have ready for the next tutorial meeting.

Following the tutorial meeting of Wed 3rd we had our usual informal meeting. From this, I was assigned the task of writing the Introduction section of the Design Spec. I first thoroughly read the SE.QA.05 document to get an understanding of the contents and purpose of the Design Spec. During the weekend I spent a couple of hours writing an Introduction draft. After that I had a short (20 min)meeting with some group members where I showed my work, and we further discussed the Group’s plan for the Design Spec.

It will likely be another week before we recieve feedback on the Test Spec, so I expect to be assigned further tasks related to the Design Spec following the next tutorial meeting. Approximately 3.5 hours spent working this week. [:de]Having submitted the Test Specification last week, Nathan and I have started to transition to new roles on the project. The element of principal concern is the Design Specification, a full draft of which we need to have ready for the next tutorial meeting.

Following the tutorial meeting of Wed 3rd we had our usual informal meeting. From this, I was assigned the task of writing the Introduction section of the Design Spec. I first thoroughly read the SE.QA.05 document to get an understanding of the contents and purpose of the Design Spec. During the weekend I spent a couple of hours writing a draft for the Introduction section.[:]

CS221 Week 5

[:en]This week the group met for ~1 hour to discuss and give feedback on the Test Specification. A few days later the Test Spec group met with the JavaFX group to note areas in which the Test Spec disagreed with the current JavaFX build, which also took ~1 hour. I spent approx ~3 hours implementing the changes discussed in these two previous meetings. On Tuesday I spent a further hour tweaking some aspects fo the document, and then later in the day I participated in the Quality Assurance Review meeting for the Test Spec document. In total this week around 7 hours were spent working on the project.[:de]This week the group met for approximately an hour to discuss and give feedback on the Test Specification.[:]

CS221 Week 4

[:en]This week the group met to review the User Interface Presentation document and the Use Cases document. I pointed out a few details that needed addressing, and noticed that the UI Presentation needed to be updated to compy with SE.QA.02.

I did a small amount of work on the Test Specification this week. Formalised last week’s drafted tests, and ensured the Test Procedures table had a coherent Test Reference system. ~2 hours spent.[:de]This the group met to review the User Interface Presentation document and the Use Cases document. I pointed out a few details that needed addressing, and noticed that the UI Presentation needed to be updated to compy with SE.QA.02.

I did a small amount of work on the Test Specification this week. Formalised last week’s drafted tests, and ensured the Test Procedures table had a coherent Test Reference system.[:]

CS221 Week 3

[:en]This week, I wrote the introduction for the Test Spec. I first read SE.QA.02 to find out what should be included in the introduction, and how it should be structured. After that, I spent a few hours drafting an intro into the test spec .tex file. I also added a subsection detailing how the Test Spec should be used. Lastly I wrote drafts for 10 or so possible tests that could be added to the Test Spec. ~2 hours spent. [:de]This week, I wrote the introduction for the Test Spec. I first read SE.QA.02 to find out what should be included in the introduction, and how it should be structured. After that, I spent a few hours drafting an intro into the test spec .tex file.[:]

CS221 Week 2

[:en]During the second tutorial meeting, sub-groups assigned to tasks presented what they’d worked on so far.

Nathan screenshared our first draft Test Spec with the group. Laurence advised that the questions we had concerning our task be taken to Chris Price. On Thursday I met with Nathan and Aaron, we discussed what aspects of UI would need to be written into the Test Spec.

We were tasked for the following week to continue working on the Test Spec. Feedback from Chris Price caused us to rethink the structure of the Test Spec, in that tests should be written to naturally follow on from each other. Following this, I began work on the Test Spec as a LaTeX document (first refamiliarising myself with LaTeX). Next I rewrote the existing draft to reflect Chris’ feedback (which caused it to be more specific and repeatable), and then transferred the new draft to the LaTeX document.

I spent some time writing more tests into the Test Spec Doc, ensuring where possible that the Input, Output and Pass Criteria sections are specific. Last, I successfully uploaded a .tex file and a readme to the /docs folder on the group’s GitLab. ~4 hrs spent

Time spent: most of a single working day.

[:de]During the second tutorial meeting, sub-groups assigned to tasks presented what they’d worked on so far.

Nathan screenshared our first draft Test Spec with the group. Laurence advised that the questions we had concerning our task be taken to Chris Price.

We were tasked for the following week to continue working on the Test Spec.

[:]

CS221 Week 1

[:en]Prior to the 24th Jan group meeting tutorial, I read through the Requirements Spec. During the meeting Laurence introduced the group project and discussed the nature of the weekly group meetings. The group volunteered for various tasks to report on by the next group meeting and I, along with Nathan, was tasked to start work on the Testing Specification.

I read through SE-QA-06, and then the following Tuesday met with Nathan. Following that we individually wrote out some System Tests pertaining to different FR’s, which I then compiled into a Word Document containing a first draft of the Test Spec. We noted a few questions we had concerning the tests we’d written, to be brought up in the next group meeting. Time spent: ~half a working day.[:de]Prior to the 24th Jan group meeting tutorial, I read through the Requirements Spec. During the meeting Laurence introduced the group project and discussed the nature of the weekly group meetings. The group volunteered for various tasks to report on by the next group meeting and I, along with Nathan, was tasked to start work on the Testing Specification.

I read through SE-QA-06, and then the following Tuesday met with Nathan. Following that we individually sketched out some tests pertaining to different FR’s, which I then compiled into a first draft of the Test Spec.[:]