Wednesday, 17 February 2010

Implementation - completed

All errors have now been resolved and coding is completed. However, I am unable to commence testing until an oddity in the application presenting a white screen on startup, and nothing more, is resolved.

There are a few features that have been looked over in this implementation of the project. This includes the gamekit multiplayer aspect of the game which I feel I can't include until the code implemented so far is seen to be meeting specifications.

Further documents are in the process of being updated for the draft deadline tomorrow which include; the project plan - which needs to be updated with the latest entries, the test plan - which is not complete but need to be updated to include a user feedback form, and the project document which needs to be reviewed before submission.

Friday, 15 January 2010

Implementation - progress

Made significant progress by getting the file reading operations to work!

The process within Xcode and Objective-C 2.0 is to incorporate the files to be read from into the project within Xcode, usually within the 'Resources' folder. You then assign a string with the full path of the file to be read by applying a method onto the project's bundle object. It is then possible to read from the file.

A few problems associated with file reading and data management remain. Such as, assigning attribute names to an array of string objects and arranging the card objects into a 'random' order.

Next on the agenda is performing research into the implementation of the GameKit framework and then implementing the multiplayer aspect into the game.

Friday, 8 January 2010

Implementation - progress

After coming back from the winter break I have cleared all occurring errors from the implementation. Some errors were caused by incorporating cyclic links within different class files which I therefore decided was not necessary for the implementation nor required by the specification. Further errors included improper definition of an array.

With these errors resolved I am ready to move onto incorporating the file reading capabilities of the program in order to read in data corresponding to each individual card.

Tuesday, 24 November 2009

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.

Monday, 23 November 2009

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.

Friday, 20 November 2009

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.

Thursday, 19 November 2009

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.