1. Progress Reports

2. Schedule http://web.eng.fiu.edu/~arellano/4011/schedule.ht m http://web.eng.fiu.edu/~arellano/4011/schedule.ht m

3. Contents Title Page Abstract I. Project Progress This section is at the heart of the progress report. It describes in explicit numerical and engineering detail the state of the project that exists at the time of the report. It describes: II. A report showing the effort of each participant (number of hours) and any other pertinent management information

4. Contents A Word 2007 tutorial on reports:  Formatting  References  Table of contents  List of Figures  List of Tables Is available at:  http://web.eng.fiu.edu/~ARELLANO/4010/f2007/proposal/p roposal.ppt http://web.eng.fiu.edu/~ARELLANO/4010/f2007/proposal/p roposal.ppt

5. Title Page Double click on the white area of this slide to open the Word page that contains the Title Page. Copy the entire Title Page and paste it into a new Word 2007 document. My example does not have any formatting. Please use some creativity here

6. ABSTRACT An ABSTRACT can be the most difficult part of the research report to write because in it you must:  introduce your subject matter,  tell what was done,  and present selected results,  all in one short (about 50 to 250 words) paragraph. The most common type of ABSTRACT is the informative abstract. A good way to develop an informative abstract is to devote a sentence or two to each of the major parts of the report.

7. I.Project Progress This section is at the heart of the progress report. It describes in explicit numerical and engineering detail the state of the project that exists at the time of the report. It describes: A. Description of the work done since the last report. B. The design approach being implemented in the prototype. C. The functionality and performance expected to be provided by the prototype compared to that predicted in the Proposal. D. Critical components acquired or in process of being acquired in preparation for implementation.

8. I.Project Progress E. Test procedures being developed and required to measure and evaluate system performance provided by the prototype. F. Results of any tests and measurements on sub systems already performed that are critical to the successful development of the prototype. G. Critical technical problems that may have been encountered and how they are being managed. H. A clear numerical analysis and evaluation of the projects cost/time line that will be in effect from the time of issuance of the report to the end of the term. Comparison of this cost/time with the estimates in the Proposal

9. I.Project Progress I. An updated Gantt/cost/task chart for the completion of the project. J. An updated current block diagram of the system being developed.

10. Set The base Line Updating The Project Status

12. Double Click on the affected tasks and change the changes in estimated and actual time per Resource

13. Updating The Project Status The task bar changes colour to reflect status (Red / Blue – Not Started) (Purple – Started) (Grey – Progress completed) The task name changes colour to reflect status (Red – Not Started) (Purple – Started) (Green – Completed)

14. Updating The Project Status If the task is completed enter 0 in Estimate

15. Updating The Project Status We reduced 20 hours but because of the weekend it appears to be a longer time

16. Updating The Project Status You can find the whole OWB presentation at:  http://web.eng.fiu.edu/~ARELLANO/4010/F2007/Openwork bench.ppt http://web.eng.fiu.edu/~ARELLANO/4010/F2007/Openwork bench.ppt

17. II.Individual Contribution A report showing the effort of each participant (number of hours) and any other pertinent management information

18. Log Books Very important, show your mentor your individual Log Books and ask for feedback about the way to keep them.