Hey Guys,
Just adding the final additions to the report. Anything that's not java doced I think it's to late now, i'll go through and quickly add author tags but thats about it.
Would any one be able to assist me in the printing of the report? We all know the benefits of multiprocessing =P
Dan
Friday, 25 April 2008
Monday, 21 April 2008
Email 21/04/08
Hey Guys,
Here's the feedback from the report, we've got to push really hard to get it all finished. Or close as possible!
* Use the titles given to you in the Guide to the final report. E.g., section 2 should be titled "Testing". This makes it easier for the grader to give you a good grade.
* "it's" versus "its"
* sometimes you don't write proper sentences. E.g., "...as a car enters campus, the decision". Should be two separate sentences here.
* 1.1: this scenario (and screenshots) is ok but could be better. The writing is poor in places. Also, you don't show any alternative scenarios. You have demonstrated to the reader that you have implemented the basic functionalities. However, you have not provided any evidence that you have gone beyond the basic spec. Think about the coolest part of your system, and show the screenshots for that. Also, you don't mention any functionality that you cannot provide. If some cool functionalities could not be implemented, for whatever reason, mention them. You won't get marked down for not covering everything.
* If space is an issue, I suggest focusing section 1 more on 1.1 and 1.2 than 1.3. The simulation part is not as "exciting" and some of the stuff you have there now could be cut if necessary.
* Implementation section. This section doesn't read well. The point of this section is not to give a lot of details of the implementation or to repeat the Design Report. You will get good marks here by being self-reflective -- that is, discussing how your eventual design differed from or extended the one in the design report. You may need a high-level class diagram to show the overall system architecture so that you can discuss such things, but giving detailed class diagrams and method descriptions doesn't really add anything. Again, try to be self-reflective as much as possible: what proved challenging and why? What would you do differently if you could do it again? Where was your design not sufficient and why? etc. Reread the guide and try to answer the questions posed there. I know there are 2 pages reserved at the end for reflection but those 2 pages will concern more process issues. This section is really about how well you designed the problem in advance and if there were any surprises that forced changes to the design.
* I don't think you mention the design patterns at all in the implementation section. It would be good to do so -- especially, whether you found them to be useful/effective or not.
* usability section looks good
Dan
Thursday, 17 April 2008
Email 17/04/08
Hey Guys,
Just working through the stuff required for the usability section and I've come up with the following plan,
- Introduction to section, brief paragraph explaining the success and failure of certain features, (I'll just say that Speech recognition was a pipe dream etc...)
Then following that I've come up with the following section heading structure for which each section needs to be a maximum of 2 pages (1 of which will be a massive table),
ICS (I'll do this section)
Comment on incomplete features
Usability study for the user interface
Monitoring Centre (Jimbo doing this section?)
Comment on incomplete features
Usability study for the user interface
Simulation Engine(Si doing this section)
Comment on incomplete features
Usability study for the user interface
Ok for the usability study i've dug up the following shiz, It's basically the same as the heuristic evaluation we did for MySpace and Facebook, I've found "Nielsen's 10 heuristics" which are at... http://info.comp.lancs.ac.uk/year2/notes/csc252/slides.html under slides 16-17 it's called evaluation.ppt. What i'll do is insert the 10 heuristics in the appendix, so the table structure wants to look something like this,
Heuristic ID | Description (I.e. if it was violated or not and why) | Improvements that can be made.
This should only take like 2 hours max, and atleast that way we've got 1 extra section of the report finished, also if you wanna include screen shot's of specific examples that mite be cool. Anyhooo just e-mail me it over when done and i'll sthick it into the report.
Dan
Just working through the stuff required for the usability section and I've come up with the following plan,
- Introduction to section, brief paragraph explaining the success and failure of certain features, (I'll just say that Speech recognition was a pipe dream etc...)
Then following that I've come up with the following section heading structure for which each section needs to be a maximum of 2 pages (1 of which will be a massive table),
ICS (I'll do this section)
Comment on incomplete features
Usability study for the user interface
Monitoring Centre (Jimbo doing this section?)
Comment on incomplete features
Usability study for the user interface
Simulation Engine(Si doing this section)
Comment on incomplete features
Usability study for the user interface
Ok for the usability study i've dug up the following shiz, It's basically the same as the heuristic evaluation we did for MySpace and Facebook, I've found "Nielsen's 10 heuristics" which are at... http://info.comp.lancs.ac.uk/year2/notes/csc252/slides.html under slides 16-17 it's called evaluation.ppt. What i'll do is insert the 10 heuristics in the appendix, so the table structure wants to look something like this,
Heuristic ID | Description (I.e. if it was violated or not and why) | Improvements that can be made.
This should only take like 2 hours max, and atleast that way we've got 1 extra section of the report finished, also if you wanna include screen shot's of specific examples that mite be cool. Anyhooo just e-mail me it over when done and i'll sthick it into the report.
Dan
Tuesday, 15 April 2008
Email 15/04/08
Hey Guys,
Right were finally at that stage where we can start polishing off this project for good =!!!!!!! I've uploaded a working version of the system to the svn. To get it running start your self an instance of the monitoring centre (either running locally or online) Then boot up the simulation engine and hit run. You should see an explosion of ICS windows and whaaabam it's all up and going...
What does this mean in terms of finishing?! Well we have the following to do....
1) Full description of the product - Pretty much finished, we need Will and Jimbo to send in their bits for it and tweak the other bits (Tutor hasn't given any info yet)
2) Testing - If we each write up the testing section for the system we each developed, so individually if we go back to the Design report and take a couple of the test cases relevant to the system we each implemented. (2 Pages for each system) Then write them up in tabular format. Then as a group we'll all write the integration testing section.
3) Usability - Again if we each take the system we developed for this section and write up 2 pages (for each system) each on the usability of the system, refer to the final project report guide for this section. It's basically how usable the UI is in relation to usability guide lines
4) Evaluation - This is an evaluation done on the experience we gained, will be a bit tricky to write. But I think i've come up with an idea. If we each write say 200 words on, A) What we gained from the project. B) What we found most difficult C) What you would do differently if you could do it again D) What extra features you would add if you had more time.
5) Appendices - JAVA DOC!! ARGHGHG make sure over the next week you all javadoc the relevant files that you've coded in the author section and comment all methods you've done. I'll generate the javadoc for it when i've been through and check each file is authored correctly
Were very very nearly finished now. Jon asked if we could have also of this done by friday (There isn't much just tweaking code and around 5/7 pages of writing, screen shots that kinda stuff) That leaves us with a week to polish off the report, tweak it and revise for the first exam which is on the 28th?!?!?!
E-mail me if your in any doubt, also make sure you get in contact with your partner who you deved the system with so you know who's going to write up what.... If you could send the stuff for submission to the report from just one e-mail address i.e. 1 person from the monitoring centre dev team send the compiled stuff, etc...
WEEEE CAN DOOO THIS!! IT"S all nearly over!!!!
Dan
Right were finally at that stage where we can start polishing off this project for good =!!!!!!! I've uploaded a working version of the system to the svn. To get it running start your self an instance of the monitoring centre (either running locally or online) Then boot up the simulation engine and hit run. You should see an explosion of ICS windows and whaaabam it's all up and going...
What does this mean in terms of finishing?! Well we have the following to do....
1) Full description of the product - Pretty much finished, we need Will and Jimbo to send in their bits for it and tweak the other bits (Tutor hasn't given any info yet)
2) Testing - If we each write up the testing section for the system we each developed, so individually if we go back to the Design report and take a couple of the test cases relevant to the system we each implemented. (2 Pages for each system) Then write them up in tabular format. Then as a group we'll all write the integration testing section.
3) Usability - Again if we each take the system we developed for this section and write up 2 pages (for each system) each on the usability of the system, refer to the final project report guide for this section. It's basically how usable the UI is in relation to usability guide lines
4) Evaluation - This is an evaluation done on the experience we gained, will be a bit tricky to write. But I think i've come up with an idea. If we each write say 200 words on, A) What we gained from the project. B) What we found most difficult C) What you would do differently if you could do it again D) What extra features you would add if you had more time.
5) Appendices - JAVA DOC!! ARGHGHG make sure over the next week you all javadoc the relevant files that you've coded in the author section and comment all methods you've done. I'll generate the javadoc for it when i've been through and check each file is authored correctly
Were very very nearly finished now. Jon asked if we could have also of this done by friday (There isn't much just tweaking code and around 5/7 pages of writing, screen shots that kinda stuff) That leaves us with a week to polish off the report, tweak it and revise for the first exam which is on the 28th?!?!?!
E-mail me if your in any doubt, also make sure you get in contact with your partner who you deved the system with so you know who's going to write up what.... If you could send the stuff for submission to the report from just one e-mail address i.e. 1 person from the monitoring centre dev team send the compiled stuff, etc...
WEEEE CAN DOOO THIS!! IT"S all nearly over!!!!
Dan
Subscribe to:
Posts (Atom)