Hi guys...
here's what i have find out about design document .....
first 2 things i think we had it....the storyboard i did for each presentation...
so Q is ....any update on storyboard i should do?!
another Q is....anything else we could add...???
so far i will be doing the web research of social networking
Design Document!--------
1. Intro
2. Storyboard- documents all the technology and design for our project- 10 pg?!
-------------storyboard
-------------technology report on each page --- write it next to graph....?!
3. A flow chart of the navigational pathway- 2 page will do!?
4. resource
5. content review
system design
user interface design
non-functionali requirements like performance..
languages ..etc
6. Research/reflection on social networking...6-8 pages?!!----BIG DEAL FOR ME AND JUAN
7. prototype- could be a non working one...just a tour ....use html...flash....director...anything....BIG FOR ZUN
8. evaluation and testing methodologies
testing and evluation procedures
and how they will be implemented..
9. Conclusion
I guess its a pretty nice plan...Normally the design docs, min is 40 pages...
is 20 pages enough though???....thats a lot!
we got really good mark for the project plan! NICE 9/10!!!....its sad its only 10 %
Subscribe to:
Post Comments (Atom)
2 comments:
it looks like a good plan... it depends on juan on what topics he would cover for content... so i guess we dont worry on page numbers and concentrate on content topics... If u want to create a flash video for a demo based on the sketches we did, that would be great... thanks jo... -zun
Hi,
Looks like a good start to the structure, I would suggest:
- Adding in a requirements section between Intro and Storyboard
- This includes *who are your users*
- Something like a few personas may help this
- What are the goals of the users
- Have a quick look back at the interaction design lectures (http://www.itee.uq.edu.au/~comp3503/), there are a lot of techniques which could be used here
- The point of this section is to clearly identify what the system has to accomplish
- Research section may be better off straight after the requirements section
- This would be like saying "based on the requirements we found, we researched these different things"
- Then, reflection can go after evaluation / testing, so you can reflect on what you found during the evaluation (in academic writing this is often called discussion)
- Research should include the current system, what does it do well, what could be done better.
- Again, having a look back at the interaction design slides might make this easier (http://www.itee.uq.edu.au/~comp3503/)
So my suggestion for structure would be
Title page / executive summary
Table of contents
1. Intro
2. User requirements
3. Research
4. Design
4.1 Storyboard
4.2 Flowchart
4.3 Resources
4.4 Content Review
5. Prototype/Implementation
6. Evaluation
7. Reflection/Discussion
8. Conclusion
References
Appendacies
Hope that helps, gimme a yell if you need any more information.
cheers
Dekker
Post a Comment