Duplicate of e-mail

Hey Guys,

Right I'll detail all the work for each team task by task so each of you knows what we need to get done... Remember final date for getting it to me to compile will be the 21st Dec (Next Friday).

To aid each other any work we have accumulated up load to the blog, Im gonna just upload my whole folder of work onto my Uni web space with a link to it on the blog so you can download the whole folder for access to any of the work. I reckon it'll be useful if we all do something similar, Stu's idea with modding the documents online using Google docs is a good one. Check it out if you haven't seen it already.

When you e-mail me the work make sure all documents are in .doc format, Any UML diagrams send them in both .jpeg format and the original .argo (or what ever it is) format in case I need to change any names of class to ensure were all consistent.

I found the following articles on writing technical documents online...

http://www.sussex.ac.uk/engineering/1-3-11-2.html

Theres some useful points on using headings, cross-referencing and such.

In terms of referencing other articles we may come across, I'm not sure what style the uni likes to use and it changes from subject area to subject area but I reckon if we all use the Harvard referencing style then if it does need to be changed it wont be as hard...

http://www.cs.bham.ac.uk/~pxc/refs/index.html

As a side note, we have to submit some user interface designs as part of the document (HCI Usability a spec section), So I've assigned different UI's to each team to do and I guess we can then do a vote of the pro's and cons(Posted on the blog) of each to come to a final conclusion. I think paper sketches are fine for this section...


Tasks...
Si & Jimbo

• Write up the Domain Requirements we did expanding on the points and how they will affect the overall design
• Write up the UML Use Case Diagram (the documentation for each and the Sequence diagrams for the most important use cases)
• For the HCI Side of things if both of you could individually do two designs for the Simulation System i.e. (the main GUI any file dialog boxes) stuff like that then post them on the blog so we can all comment on them and decide which one is best to be used.

Stu, Dan, Will

• (Stu) - Write up the Non-Functional requirements, again expanding on any points and try and figure out any metrics or measurable value that we can analyse to see how well we meet up to the requirements after we've implemented it. I was thinking along the lines of (Time In Seconds it takes for the software to load up for the speed and efficiency requirement) Or something along those lines.
• (Stu) - Write up and document the UML Class Diagram for the Simulation System.
• (Stu) - HCI Designs for the In Car System and for the Monitoring System
  
• (Dan) - Write up the Functional Requirements for the In Car System again expanding on points we came up with in the meeting...
• (Dan) - Write up the UML Class Diagram for the In Car System documenting where required...
• (Dan) - HCI Designs for the In Car System and the Monitoring Centre
• (Will) - Write up the Functional Requirements for the Monitoring Centre (same as above for other details)
• (Will) - Write up the UML Class Diagram for the Monitoring Centre with any Documentation that needs to be included.
• (Will) - HCI designs for the In Car System and the Simulation Monitoring Centre.

I hope I haven't missed anything... If anyone notices anything missing just wazz an e-mail or post a blog entry... Other than that have an ace Christmas & I'll see you in the new year for the meeting with Jon on the 11th @ 11am (Think it's posted on the Google calender for those who have a memory like mine!)

Dan