|
|
 |
|
|
 |
Jump directly to
|
|
Important Dates to Remember
|
| Midterm Exam(Opened book & notes) |
Posted by October 11 (Wednesday) 7:00 PM at Canvas
Due by October 13 (Friday) Noon or earlier by uploading your solution to Canvas
|
| Project Proposal Deadline |
October 18 (Wednesday) |
| Project Progress Report Due |
Optional but highly recommended. November 8 (Wednesday) |
| 1-page Summary due for
your group's Project Presentation |
December 4 (Monday) Noon, in Word (.docx) format |
| Project Presentations |
In-class presentation & via Zoom, December 6 (Wednesday) 7:10-9:30 |
| Project Final Report and Project Presentation Due |
December 6 (Wednesday) 7:10 PM or earlier, upload to Canvas.
Project Final Report (in a PDF format) and Project Presentation (in Powerpoint .pptx)
|
| Final Exam(Opened book & notes) |
Posted by December 7 (Thusday) 7:00 PM at Canvas
Due by December 9 (Saturday) Noon or earlier by uploading your solution to Canvas
|
|
| |
-
Requirement of this class is to conduct a group project on a
water quality modeling/management/planning problem and
give a formal presentation.
The project
will be a group effort, ideally two students per group, but
the students/group ratio will be depending on the class size.
Suggested list of topics will be further discussed in the first class.
Previous projects would also give you some idea on selecting your
group's project topic.
Project topic can be one of
various water quality modeling/management/planning topics
deal with surface, river & stream, lake & reservoir, subsurface
and groundwater, and estuary water quality issue.
Idea is that by conducting this group project research as a "seed" reseach closely
related to your areas, you can
- Really understand class topics by actually using them, and
- Develop this project further into your own dissertation/thesis/project research.
Each group is required to submit a full written
Group Final Project Report
(in a PDF file format, no hardcopy
report), and project presentation (in Powerpoint, .pptx)
by uploading to Canvas.
CEE 756/856 Course Timeline
You are always welcome to have
an advisory Zoom meeting in regard
to your project idea/problem -- help is in your reach.
Keep in mind that your project will be managed as if I'm your client
who awarded the project to your group solely based on the merit,
meaningfulness, and doability of the project proposal that
your group had submitted.
That means that by the time you submit the progress status report,
I can even fire(!) your group from the project depending on
your group's adherence to proposed schedule and interim
performance -- please be serious.
Finally, remember that the ability to accomplish a thorough, technically-sound,
and quality project is what distinguishes you from the
undergraduates and distinguishes engineers from others.
I'd expect nothing short of a fantastic project from each
group and will not accept any sloppy, unstructured and
perfunctory project.
|
| |
-
Each group is required to submit
one-page written proposal
of the project.
A project proposal should include following core components based on
your group's preliminary research and literature review.
Be succinct and concise.
Project proposal reviews will be returned within days with
comments/suggestions.
- Title of the project
- Project Group name (Yes, a nickname for your group) and group member names
- Project Conceptualization (Why)
- Projected audience of your project report (Who)
- Project Objectives (What)
- Study site or topic/Source of data (Where/When/What types of data)
- Proposed procedures and methodologies for the project (How)
- Expected deliverables at the end of your project (What)
- (realistic) Timeframe -- use a Gantt Chart format if possible
If you have a difficulty to decide/select a project topic
by October 9 (Friday), please
contact me for consultation and for some brainstorming.
Also, an optional project progress report
is highly recommended for your project.
In the progress report, reiterate objectives and clearly
mark on the Gantt Chart the levels of progress that you
made since the project starting date -- will help you to quickly identify
what has to be done toward your project completion.
- Title of the project
- Project Group name and group member names
- Project Objectives
- a Gantt Chart with progress milestones marked
(either Completed or On-progress or Delayed)
CEE 756/856 Course Timeline
|
|
Group Project Presentation
|
| |
-
Project presentations are scheduled in the last class of the semester.
Each project group would have about 20-30 min. for its
presentation (depending on the number of project teams).
All group members will participate in
the presentation; i.e., a multi-speaker setting.
Thus, please prepare accordingly for your presentation
strategy rather than improvising at the very last minute on
who will present what.
Each group shall prepare a PowerPoint presentation for
the final project presentation.
For presentation tips, here's a dear old WEF paper
(Haworth and Reardon, Proceedings in 65 th Annual Conference
and Exposition, Water Environment Federation, September, 1992)
that you may find quite helpful and still valid.
-
Final presentation will be evaluated based on instructor's
and students' peer evaluation score composites
including effectiveness and conciseness of the presentation.
In the begining of yopur presentation,
clearly indicate each member's task/role and contribution to your
project.
|
One-page Summary for Your Project Presentation
|
-
Don't forget to submit one-page summary of your
presentation to Dr. Yoon
in a Microsoft Word file format, .docx
(use the Word template listed below).
These summaries will be put together into a class project
presentation proceedings and will be distributed before
class project presentation day
via Canvas posting.
Each one-page project presentation summary should contain;
- Group name and group member names,
- Title of your project,
- Three Keywords best describing your project, and
- Abstract (300 words max.).
When you're e-mailing your one-page summary, please name the file as
'xxx_wqmd_fa2023_presentation_summary.docx' where
'xxx' is your project group name. For
example, an one-page project summary
filename from a project groupt "AquaHeads" would be
AquaHeads_wqmd_fa2023_presentation_summary.docx
|
|
Final Report Core Elements
|
| |
-
Final Project Report is also
due on the Poject Presentation day.
A written project report, single file in a PDF format
(uploaded to Canvas, no hardcopy report)
should include following core components;
- Title of your project
(in the Cover page)
Title should be concise and self-explanatory. Be specific.
Vehemently avoid any ambiguous or run-on title. 15 words maximum.
- Course name, current Semester and Year,
Group name, group member names and ODU IDs
(in the Cover page)
In the same cover page
- Abstract
(in the second page - Abstract and Keywords)
In the second page.
Should include a brief and succint
statement of the problem, objective, method(s),
and final conclusion. 300 words maximum. If you can't
summarize your project within 300 words, chances are that
probably you're not quite sure what you did.
- Keywords
(in the second page - Abstract and Keywords)
Right below the Abstract section. Five keywords maximum.
Use following format;
KEYWORDS: Bacteria Source Tracing (BST); Fecal coliforms; Total Maximum Daily Load (TMDL)
- Table of Contents
(in the third page)
Include correct page numbers for each section. Also list
Appendices for data used in the project and model
output (if you used one).
Also list each member's responsibility for section(s) applicable.
- Introduction/Background of your project topic
(Introduction section)
- Clearly disclose your problem conceptualization
with a solid rationale.
You should be able to show your genuine
interest in your project topic why you choose it.
Avoid such problem conceptualization that was
defined retrospectively to fit your methodology/technique.
- Literature review on similar studies done previously (if there's any)
Were there any previous study/investigation conducted
on the same or similar problem? If there were,
what methods were used? (i.e., mathematical? experimental, etc.?)
List all such references at the Reference section in your report using
proper formats. (
see below for the format guideline)
- Provide detailed background information
of your study site/data. Make it sure to
include maps of study site with its source.
- Project Objectives . (What do you
want to solve/test/prove? Why?)
(Objectives section)
- Use bullets or numbers to list your objectives.
Get to the point and stop beating around the bushes.
- Bottomline is that you should know exactly
what do you want to solve/test/analyze in your
project, regardless of the scale of problem.
(i.e., proper and correct problem conceptualization)
Without knowing it, a project would become
either a never-ending organizational disaster
that will fizzle without a fruition
or a mere technical charade with no substance.
- Source of data
(Data section)
What types of data did you get from Where/When
for your project? Describe about your data in detail.
Why do you think that particular data source is
adequate and valid?
Why not others? Make it sure to disclose the source of data used
in your project in a utmost detail.
- Procedures and methodologies
used in your project.
(Methodology section)
Must clearly state assumptions and
limitations of
each procedure/method used to accomlish your project Objectives.
- Your interpretation and conclusion
(Discussion and Conclusion section)
- By far, the most important part of your report, of course.
- Make it sure to reiterate the original
Objective of the project in your
conclusion. Keep in mind that
the readers usually do not remember what the original
Objectives were -- talk to the reader, not to yourself.
- Also, always express your concludion in form
of recommendations for possible future actions. Finding
right or wrong is one thing. But good project
should also be able to suggest a way to correct/obviate
the current problem or improve from what you started from.
- References
(References section)
Include only ones that were actually cited in your report.
Internet website/webpage are not citable
in References section and should not used "as is" references -- find the correct
reference/source that the webpage is based on, and refer them
instead. One exception is the website/webpage address where
you may have obtained your sample data from. (usually government sites)
Use correct formats (
see below for the format guideline)
- Appendices
(Appendices section)
Data for the study, Model output,
Correspondences, Map, Folded figures,
Drawings, etc.
The project report
grading will be based on the problem conceptualization,
assumption and limitation, correctness of the procedures,
thoroughness of analysis
and the clarity.
|
| |
-
In regard to the project report format, following guidelines should rigorously
be used;
- No smaler than 11-point San Serif font (i.e., Times
Roman or similar font) with 1.5 line spacing, justified on a Letter-size,
8.5"x11" (21.5 x 28 cm) layout with at least 1-inch margins at top, bottom, and sides.
- Each page in main boday of the report should be numbered in the bottom,
aligned right using group name and numeral
combination. (i.e., AquaHeads 1, AquaHeads 2, and so forth)
- Use correct spelling, punctuation, grammar, and syntax. Spelling and hyphenation
of compound words follow the unabridged Webster's Third New International Dictionary.
- Numbered Figures and Tables should be placed in the text body,
not in separate pages or Appendix. Legend for figures should
be placed at the bottom of figures
whereas legend for tables at the top of tables.
- Summary/Conclusion section should be a single
paragraph (150 words or fewer) stating the nature of
the problem and summarizing its important conclusions.
If you can't summarize within 150 words or less, then
it would be very unlikely that
you understand what you did in the project.
- There is no page limit for the Final report.
However, keep in mind that a good report
is always succint and to the point. Verbose,
bloated and disorganized reports usually
incur more confusion than what is already presented
in the problem itself.
- "I" is boring. Avoid starting sentences
using terms such as "I" or "My." Also avoid
gender-specific words such as "he," "she," "his,"
and "her." Use words such as "The
group," "Authors," "Discussers," and "Researchers" instead.
Remember, accute opinionedness and incompetency are always
mutually inclusive.
- For reference(s) if you used any in your main body of
the report (i.e., not in References section, but in Introduction,
Data, Methodology, Discussion and Conclusion sections),
use complete and accurate reference format.
Omissions, discrepancies in the spelling of names, errors
in titles, and incorrect dates must be avoided.
(think why you put references in your report in the first place)
Do not put references in footnote nor 'numbered' reference index.
For multiple authors, use following format;
| single author |
(Alerich, 1997) |
| two authors |
(Marks and Bormann, 1985) |
| more than two authors |
(Megahan et al., 1996) |
| multiple references -- start from recent one |
(Alerich, 1999; Megahan et al., 1996; Marks and Bormann, 1985) |
| the same author with multiple references
-- start from recent one |
(Alerich, 1998;1997a;1997b;1995) |
|
* et al. (=et alii) -- don't forget to put a 'period' and in italic.
- For listing reference(s) in the
References section which should be
at the end of your report, use ASCE standard format
shown at the bottom of this page. Omissions, discrepancies in the
spelling of names, errors in titles, and incorrect dates must be avoided.
In case that if there's more than one authors for a reference,
the proper convention is;
Last_name(1), Initials(1), Initials(2), Last_name(2), Initials(3), Last_name(3),
. . . and Initials(n), Last_name(n), (Year), Title, Source, Vol.(No.):page-page.
where 1=first author, 2=second author, and so forth to 'n'th author.
| single author |
Alerich, J.K. |
| two authors |
Marks, W.L. and M.S. Bormann |
| three authors or more more |
Megahan, D.D., Bormann, M.S. and J.K. Alerich |
|
See more Reference format examples below.
- Materials from Internet webpages are not
regarded as legitimate references.
If you'd like to refer material(s) that you found
in Internet, identify the original
source and author(s) information, then refer it instead of
merely listing URI(s) or webpage address(es).
Else do not use them (=URI) in your References.
- For reference(s) if you used any for your discussion/comment, use complete and
accurate references. Omissions, discrepancies in the spelling of names, errors
in titles, and incorrect dates must be avoided. For listing reference(s) and
citing(s) for your discussion, use following standard formats;
- Examples
- Abstract
- Hartle, R. E., and J. M. Grebowsky, (1990), Upward Ion Flow in the
Nightside Ionosphere of Venus (abstract), Eos Transactions of AGU, 71:1431.
- Book
- Crosby, D.G., (1998), Environmental Toxicology and Chemistry,
Oxford University Press, New York, New York, ISBN 0-19-51171301.
- Book Chapter
-
Yoon, J. (2007) Chapter I. Introduction, Application of GIS Technologies in Port Facilities and Operations
Management, Wright, N.T. and J. Yoon, Ed., ASCE Technical White Paper, ASCE Ports and Harbors Committee/COPRI Committee, GIS
Subcommittee, American Society of Civil Engineers, Reston, Virginia, ISBN: 0784408696.
- Journal Article
-
Park, K. and J. Yoon, (2015), Monitoring for Spatiotemporal Estuarine
Chlorophyll using MODIS and In-situ Characteristics, Journal of
Environmental Engineering (JEE), American Society of Civil Engineers
(ASCE), J. Environ. Eng. , 10.1061/(ASCE)EE.1943-7870.0000928 , 0401500
- Proceedings and Conference Papers
-
Yoon. J and A. Shahvari, (2011), Dispersive Tidal Plume Modeling of Brine Discharge from
Reverse Osmosis (RO) Desalination System, OS33C-1692,
Particle Dynamics and Sedimentary Processes in Estuarine
and Coastal Environments I, American Geophysical Union (AGU)
Fall 2011 meeting, San Fransico, December, 2011.
- Report
-
Yoon, J., (2008), Calibration of a Three-Dimensional, Numerical Hydrodynamic Model
of the Mattaponi Tidal Estuary, Virginia, City of Newport News, Waterworks, 117 pp.
|
|
Examples of Previous Project Topics
|
| |
- Retrospective Evaluation and Study of a Best Management Practice Pond
- Reconstruction of Radionuclide
Concentrations Along The Techa River
- Dynamics of NOM filtration by Oysters in Chesapeake
Bay - Quantitative Analysis
- Assessment of Phosphorus Concentration in Elizabeth River
- Establishing relationship between Fe, Mn and DO
in Lake Prince (LP) and Western Branch Reservoir (WBR)
- Feasibility Study of the Reclamation of
Process Water at Anheuser Busch for Non-
Potable Uses
- The Impact of Storm Surges of Water
Quality for Coastal North Carolina
- Mapping Radioactive Contamination
Plumes at Hanford Site Tank Farms Using
Spectral-ray Gamma Logging
- The Effects on Manganese Levels in Lake
Meade as a result of the Sludge Lagoon
Discharge
- Conceptualization of Largrangian model for
Tributary WLA management
- Comparative Study of Best Management Practice (BMP) Design
- Relationship between Fecal Coliform Levels and Streamflow in the Potomac River
- The Effects of the Shipbuilding Industry on the Local Environment
- Prediction of Temperature Stratification in the James River Following Discharge of Secondary
Cooling Water from the Surry Atomic Power Plant
- Elimination of Toxicity at Outfall 16
- Study on Turbidity using Stream Water Quality Model QUAL2E, Pea Hill Arm of Lake Gaston
- Which is the pollutant - HRSD or the James River
- Molybdenum Total Maximum Daily Load Recommendations for the Middle Humboldt River, Nevada
- Hydrologic and Water Quality Modeling of the Mattaponi River and King William Reservoir Project
- PCB Transport and Fate in Stormwater Discharges from the Naval Support Activity, Mechanicsburg, PA
- Assessment of BOD Concentration in the Lower Hudson River Estuary, New York
- Predicting Fecal Indicator Bacteria Concentrations in an Urban Stream: a Modeling Approach
- Evaluating Stormwater Runoff and its Impacts to Lakes James, Virginia Beach, Virginia
- Estimation of Dispersion Coefficients and Applications in Finite Segment Steady State Model for Lake
Maumelle, AR
- Impact of Deep-Well Groundwater on Surface Water Quality during Drought Mitigation Operations,
Lake Prince, Norfolk, VA
- Determining the Peclet Number of the Kuparuk River using Tracer Study Data, Alaska
- Study of the Elizabeth River Dispersion Coefficient
- Modeling the Elizabeth River to Evaluate Hampton Roads Sanitation Districts Total Nitrogen Reduction
Plan at the Virginia Initiative Plant (VIP)
- Downstream Impacts Impacts of Zinc on the Animas River Following the Gold King Mine Spill
- Phytoremediation as Strategy to Reduce Surface Water Lead Concentration
- Predicting Dissolved Oxygen Concentration Downstream of the Blue
Plains Water Treatment Facility Using the Steady-State Response
Matrix (SSRM) Method
- Dissolved Oxygen, Biochemical Oxygen Demand, Coastal Flooding
- Determining Advective or Diffusive Dominated Dispersion of the Lower portion of the James river in Richmond, Virginia
- Investigation of the magnitude of the impact of the point source discharge to the Lake Maurepas water quality, LA
- Determining the impact of Central Valley Water Reclamation Facility upgrades on the Jordan River: a water quality modeling study
|
|
|
