The engr132 from kyan-cmt

Filename convention examples

GuiNameIntro_ewidlosk

GuiName_ewidlosk

citations_sec005_team18

add textbox with the programmer name in each of the team member GUI's
in text citations for pictures
left justified apa citations for citations page
the simulations should do 'something'
- all user inputs should be working
- if you haven't worked out the math for your simulation, plot something simple as a placeholder
add this header to each of your .m files

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% % ENGR 13200 Spring 2014 % Programmer(s) and Purdue Email Address(es): % 1. Name, [email protected] % % Other Contributor(s) and Purdue Email Address(es): % 1. Name [email protected] % % Section #: Team #: % Assignment: nanoHUB Project % % Academic Integrity Statement: % I/We have not used source code obtained from % any other unauthorized source, either modified % or unmodified. Neither have I/we provided access % to my/our code to another. The project I/we am/are % submitting is my/our own original work. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
convert all citations in APA - do your own citations and bring it to the next meeting
begin thinking about the executive summary (due M9)

everyone verify your tag names in the .fig, .m AND the document, make sure they are the same
- cross reference against other peoples tags
change the button the main page to something that briefly describes your gui
add a tool tip (the mouse over text, configurable in guide) that is 1 sentence that describes your gui
once you're done, click through every part of your gui, starting from the main, and verify that every navigation button is working

do all code navigation (next, prev, exit, etc. see M5_NavMap_sec005_team18.ppt)
all elements that are used (anything besides static labels) must have tag names
all tags for elements need to be stored in the FileTagInventory_sec005_team18.docx
- must have filenames and name of coder