Test Plan - progress

I have completed the logical testing aspect of the Test Plan. I have created test data to test the main comparison method that calculates and decides which card wins the round. I have also detailed expected outputs for Round and Game events.

I have not detailed a plan for testing the acceptance side of the testing as of yet. But this is currently the next item on the agenda. This will detail exactly what the acceptance testing will achieve and what is required to perform the testing. The plan will also include a rough draft of the user questionnaire that will be completed after testing to provide feedback for the project.

Test Plan - started

Today I worked on the Test Plan in school, mainly due to not being able to bring a working copy of my project in. While working to resolve this issue, I have decided to complete a test plan foremost.

The test plan has made me think about how specific data will be accessed by each device and as a result, updating my pseudocode portion via an iterative process.

Implementation - started

I have started churning out code for the implementation side of the project. My approach is to start outlining the interface including links and view transitions primarily, then flesh it out with more fundamental code.

So far when trying to compile, the usual errors are produced which I am in the process of working out. Hopefully the process will go according to schedule dispute early signs of error.

Design - completed

At long last the Design work has come together and can now be considered complete. It was difficult finding an ending point for this part of the development process as more and more components of the program needed to be documented in pseudocode. I believe the Design work I have completed will be sufficient to write the program and if parts are lacking they can be updated in an iterative manner.

Design - started & progress

I have started working on the main Design of my project. I have decided to detail the design of the project using pseudocode. I have chosen this method due to the nature of the application in being event-driven based. Pseudocode allows for various routines to be written for each event seperately and for subroutines to be seperately detailed from the main routine which fits the nature of the project.

I am currently designing the main game functionality and the use of the 'Resume Game' function. I have realised for it to be possible to resume a stranded game, the host and client devices must have a local instance of the data being shared between them.