______ 
| ___ \
| |_/ /
| ___ \
| |_/ /
\____/ 
       
       

  ____  
 |  _ \ 
 | |_) |
 |  _ < 
 |_| \_\
        

    ##   
   #  #  
   #     
 #####   
   #     
   #     
   #     
         

 _____ 
/  ___|
\ `--. 
 `--. \
/\__/ /
\____/ 
       
       

 ___   
(  _`\ 
| |_) )
| ,__/'
| |    
(_)    
       
       

IMPORTANT: enter the case-INsensitive alphabetic (no numbers) code AND WRITE SOME SHORT summary of changes (below) if you are saving changes. (not required for previewing changes). Wiki-spamming is not tolerated, will be removed, so it does NOT even show up in history. Spammers go away now.


Visit Preferences to set your user name
Summary of change:
Diagrams should go on subpages. Please give a descriptions, link a small preview image, and also link the diagram file (until we get something working with CVS). The page name should reflect the diagram name. Something like ''!MembersPage/RichardBarrington/QTune/DesignDiagrams/LoadConfigUsecase''. What tool is recommended? * [http://www.acknowledge.co.uk/download/togetherj.html TogetherJ] ? Um... No. Together Edition for Eclipse is $4000 USD?! Is there another product you were thinking of? Some more affordable choices... * [http://www.gnome.org/projects/dia/ Dia] * [http://qse.ifs.tuwien.ac.at/~auer/umlet/index.html UMLet] seems simple enough, but not collaborative. * [http://argouml.tigris.org/ ArgoUML] * [http://www.eclipse.org/downloads/index.php Eclipse 3.0.1] with... ** [http://www.omondo.com/ Ormondo] free version ** [http://www.visual-paradigm.com/productinfovpumlce.php Visual Paradigm for UML] free version (probably too restricted) ---- '''Use cases''' ''Hardware setup'' * MembersPage/RichardBarrington/QTune/DesignDiagrams/LoadConfigUsecase * MembersPage/RichardBarrington/QTune/DesignDiagrams/SaveConfigUsecase * MembersPage/RichardBarrington/QTune/DesignDiagrams/LoadFirmwareUsecase * MembersPage/RichardBarrington/QTune/DesignDiagrams/SetupBoardInputsUsecase * MembersPage/RichardBarrington/QTune/DesignDiagrams/SetupBoardOutputsUsecase ''Engine tuning'' * MembersPage/RichardBarrington/QTune/DesignDiagrams/SetupEngineConstantsUsecase * MembersPage/RichardBarrington/QTune/DesignDiagrams/TuneVEUsecase * MembersPage/RichardBarrington/QTune/DesignDiagrams/TuneIgnitionUsecase * MembersPage/RichardBarrington/QTune/DesignDiagrams/TuneIdleUsecase * MembersPage/RichardBarrington/QTune/DesignDiagrams/TuneBoostUsecase ''Application'' * MembersPage/RichardBarrington/QTune/DesignDiagrams/FirstRunUsecase * MembersPage/RichardBarrington/QTune/DesignDiagrams/ConfigureApplicationUsecase * MembersPage/RichardBarrington/QTune/DesignDiagrams/ExitApplicationUsecase ---- '''Class diagrams''' Hmm. Thinking outloud here.... A !CommandPattern for talking between GUI and !SerialPort. A controller should probably be between them though. This is mostly to make undo easier, and also so we can manage the commands as the system changes. !SerialPort can then worry about any wrapping/error detection/etc. TDB ---- '''Sequence diagrams''' TDB ---- '''Object diagrams''' TDB ---- '''Statechart diagrams''' TDB ---- Back to MembersPage/RichardBarrington/QTune
Optional: Add document to category:
Wiki formatting: * is Bullet list ** Bullet list subentry ... '''Bold''', ---- is horizontal ruler, <code> preformatted text... </code> See wiki editing HELP for tables and other formatting tips and tricks.