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.
Tuesday, 24 November 2009
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.
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.
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.
Monday, 2 November 2009
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.
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.
Monday, 26 October 2009
User Interface Design - completed
The UI Design is finally completed after much delay.
The reasons for the delay are numerous but mostly down to using Interface Builder in designing only the UI and not in the implementation of the project. This resulted in specific elements not responding to cosmetic changes within Interface Builder and therefore not suitable for UI Design.
I then had to mockup my design which meant further delay to having to find similar elements in mockup form similar to those within Interface Builder.
During the mockup design I had a thought of where to display the configurable parts of the application which I primarily had within the application itself but which I thought would be more suitably located within Apple's own 'Settings' application on the iPhone device as there are very few preferences that can be changed by the end-user.
Due to the change in the location of the Options screen there was also limited use in including a tab bar at the bottom of the three Options, Help and About screens to navigate to each of those pages easily. Therefore the mockup designs for the remaining two pages needed to be altered to reflect this design update.
These changes and the additional time to annotate the new design contributed to the delay of the User Interface Design.
The reasons for the delay are numerous but mostly down to using Interface Builder in designing only the UI and not in the implementation of the project. This resulted in specific elements not responding to cosmetic changes within Interface Builder and therefore not suitable for UI Design.
I then had to mockup my design which meant further delay to having to find similar elements in mockup form similar to those within Interface Builder.
During the mockup design I had a thought of where to display the configurable parts of the application which I primarily had within the application itself but which I thought would be more suitably located within Apple's own 'Settings' application on the iPhone device as there are very few preferences that can be changed by the end-user.
Due to the change in the location of the Options screen there was also limited use in including a tab bar at the bottom of the three Options, Help and About screens to navigate to each of those pages easily. Therefore the mockup designs for the remaining two pages needed to be altered to reflect this design update.
These changes and the additional time to annotate the new design contributed to the delay of the User Interface Design.
Wednesday, 21 October 2009
User Interface Design - progress
I have managed to create most of the windows for the design within Interface Builder. However I have discovered that some elements, such as tables, are not possible to edit from Interface Builder but by through code in Xcode.
This has affected my design of the Options window as I am unable to list any of the custom preferences/settings I wish to include. Other elements such as the 'Back button' cannot be placed on the Navigation bar and the library Apple provides for Tab Bar icons is not very extensive.
In the case of the above difficulties I may need to procure an alternative route in designing the User Interface.
This has affected my design of the Options window as I am unable to list any of the custom preferences/settings I wish to include. Other elements such as the 'Back button' cannot be placed on the Navigation bar and the library Apple provides for Tab Bar icons is not very extensive.
In the case of the above difficulties I may need to procure an alternative route in designing the User Interface.
Subscribe to:
Posts (Atom)