| |
|
|
|
|
|
-
Go directly to
| |
-
One of requirements of this class is that students conduct a small-scale
project on a water quality management/assessment/planning problem,
prepare a Final Project Report and give a formal presentation of their
work.
The project will be a group effort, ideally two
students per group, but
the student/group ratio will depend on the class size.
Please check with your classmates early in the semester and
identify your project partner ASAP.
Professional collaboration is an integral part of
any engineering activities, and this is a good opportunity
to familiarize yourself with project task allocation,
subjugated responsibility and most of all, good teamwork
and communication skill. Keep in mind that you're not a
superman, and everyone should carry one's own weight.
Project topic can be one of
various water quality management/assessment/planning topics
deal with surface, river & stream, lake & reservoir, subsurface
and groundwater, and estuarine water quality issues.
Suggested list of topics will be further discussed in the class.
Idea is that by conducting such small-scale class project,
you would
- Really learn topics discussed in class by actually using them
- Possibly develop the very problem/idea/concept from this project into
your own dissertation/thesis/project research
(there are several cases of this already)
- Readily apply similar methodology/technique(s) learnt from this
project to your own dissertation/thesis/project research
Each group is required to submit/e-mail a Project Proposal, a Project Progress Report,
and
full written Final Project Report
(in a PDF format) -- no hardcopy, let's save some trees.
You need to submit/upoad your Final Report to Canvas/Assignments.
(be sure to also submit your group's powerpoint presentation in .pptx)
-
If your group has a difficulty to decide/select a tangible
topic by Sept. 23 (Monday), please
make an appointment and consult with
me for further brainstorming.
Also, be serious about the deadline -- if it
is not that serious, people wouldn't put the word 'dead' in the first
place! Late project report submission will be still accepted with
a 30% deduction penalty, i.e., your final project report will be
graded based on a maximum point of 70 instead of 100.
Finally, a word of advice. You may find that following guidelines
are bit too stringent and specific, which are fully intentional.
As some of you already noticed, these are typical requirements
used in any professional "real-world" engineering projects and RFPs,
and I do not see your class project any different. Take advantage
of this opportunity and get yourself familiarized with
them if you have not yet.
|
| |
-
Each *group* is required to submit one-page written proposal
of the project by
Sept. 30 (Monday) class.
A good project proposal --
well-conceptualized problem
statement with clearly justifiable merits
-- is what makes any project successful and *doable*.
If you have done a good job in preparing the project proposal, I'd say
you've already accomplished 75% of your project.
Without a clear and careful problem conceptualization (of
your project), you'd have a danger of building your
project game plan solely based on familiar and comfortable
methodology (=how to do)
instead of really dealing with the problem
itself (=why and what to do).
Using your familiar methodology/technique is nothing wrong.
However, every problem has its own particular solution,
and your methodology should correctly reflect such.
Remember, if you have only a hammer,
everything else starts looking like
a nail. Subsequently, sooner or later, you'll end up with ten
throbbing fingers that no longer can hold your beloved hammer.
A project
proposal should include following core components based on
rigorous preliminary research and literature reviews;
- Title of your project (Be concise)
- Project Group Name (Yes, a nickname for your group -- choose yours wisely!)
- Project Conceptualization (Why to do)
- Project Objectives (What to do)
- Study site/Source of data (where/when/what types of data)
- Proposed procedures and methodologies for the project (How to do)
- (realistic) Timeframe -- use a Gantt Chart format
Project proposals will be returned to each group on
October 8 with (possible) comments/suggestions.
|
| |
-
Each group would optionally submit one-page project progress report
by Nov. 4 (Monday) class.
It is meant to be as a milestone for your project management
-- only if you really mean it.
Take an advantage of this project progress report element, and
re-prioritize project elements if necessary.
Good project management does not rely on "luck" (well, sometimes...)
or "flexible time management scheme -- when push comes shove,"
but it is all about steadily
putting pieces in right places as planned. The term "being able to pull off"
is nothing but a self-induced euphoria that typically implies a shady
and less-dependable project outcome. Be serious about the time
management strategy for your project.
A project progress report should reiterate objectives defined in group's
project proposal and clearly state on the Gantt Chart
the levels of progress (completed, underway and not started)
made since the project starting date.
Again, please include;
- Title of your project
- Project Group Name
- Project Objectives
- Levels of progress -- use a Gantt Chart format
|
|
One-page Project Presentation Summary
|
| |
-
Make it sure to e-mail one-page summary of your
presentation to Dr. Yoon,
no
later than
Nov. 29 (Friday) 5:00 PM
,
in a Microsoft Word file format.
These summaries will be put together into the proceedings of class project
presentation and will be distributed via e-mail on
Dec. 1 (Sunday).
(so that you can read and prepare questions in advance)
Each one-page summary should contain;
- Group name and group member names
- Title of your project
- Three keywords best describing your project
- Abstract (300 words max.)
When you're e-mailing your summary, please name it as
'xxx_wqmg_fa2024_project_summary.docx' where
'xxx' is your project group name. For
example, a project summary
filename from a project group "OinkyWater" would be
-
OinkyWater_wqmg_fa2024_project_summary.docx
|
| |
-
Project presentations are scheduled on
Dec. 2 (Monday) class via Zoom
.
Each group shall prepare a PowerPoint presentation
for the project presentation.
Each project group would have about 20 minutes.
There is no limit on the number of slides yet around 25 slides or less would
be ideal.
All group members will participate in the
presentation; i.e., a multi-speaker setting.
Please allocate time for a Q&A session at the end of
your presentation so that the audience could ask and learn
valuable lessons from your project experience.
For presentation tips, here's an old WEF paper you may find
still helpful.
-
Final Project Report and Project Presentation (in .pptx) are due on
Dec. 4 (Wednesday) 5:00 PM to Canvas/Assignments.
Final presentation will be graded based on instructor's
and students' peer evaluation scores. In the begining of your presentation,
clearly indicate each member's task/role and contribution to your
project.
The project report
grading will be based on the problem conceptualization,
assumption and limitation, correctness of the procedures,
thoroughness of analysis
and the clarity and conciseness of the explanation.
|
|
Final Report Core Elements
|
| |
-
A written project report in a PDF format
(submitted/e-mailed to Dr. Yoon, no hardcopy required),
shall include following core components;
- Title of your project
(in the Cover page)
Title should be concise and self-explanatory. Be specific.
Vehemently avoid an ambiguous or a run-on title. 15 words maximum.
- Course name, current Semester and Year,
Project group name, Member names with 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, objectives, 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. Three keywords maximum, see the example
below;
KEYWORDS: Total Suspended Solids (TSS); Seasonal influence; Dispersive transport
- Table of Contents
(in the third page)
Include correct page numbers for each section. Also list
Appendix if there's any.
- List of Tables
(in the fourth page)
If there's any Tables in your report.
- List of Figures
(in the fifth page)
If you included any Figures in your report.
- Introduction/Background of your project topic
(Why are you investigating this problem?)
(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 did choose it
in the first place.
Avoid such problem conceptualization that was
defined subjugatedly to fit your methodology/technique.
- Literature review on similar studies done previously (if there's any).
Were there any previous studies/investigations conducted
on the same or similar problem? If there were,
what methods were used? (i.e., field sampling? mathematical? experimental, etc.?)
Also, clearly describe the difference(s) between previous studies/investigations and
your project research.
List all such references in you Reference section using
proper formats. (see below for the format guideline)
- Provide detailed background information
of your study site/data.
- Project Objectives
(What are you investigating?)
(Objectives)
- Use bullets or numbers to list objectives.
Get to the point and stop beating around the bushes.
- Bottomline is that you should know exactly what do you want to
investigate 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 sample data
(Data section)
Where/When/What types of data did you get and use in your study?
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.
If you're conducting any statistical analysis of the data,
data should be validated in the first place. (by using
standard tests such as
Shapiro-Wilk test and Normal probability plot)
- Procedures and methodologies
used in your project
(Methodology section)
Must clearly state assumptions and
limitations of
each procedure/method if there is any.
- Actual analysis
(Analysis section)
You can use appropriate tools (such as computer programs, models, etc.)
if necessary.
Always provide full results from your analysis.
Be sure to attach printouts in the Appendix if there's any.
- Your interpretation and conclusion
(Discussion and Conclusion section)
- By far, the most important part of your report, of course.
- Make it sure that refer/reiterate your Objectives
first, and corresponding analysis results in your
conclusion. Were you completed what defined in Objectives?
Were they as expected in the Problem conceptualization?
Why and why not. Discuss in detail.
- Also, list and discuss any major difficulties that you had encounted
during the project. What were the problems, and in your opinion
(retrospectively speaking), what were the probable cause,
and how would you avoid/resolve them
if you're doing the same project
all over again? --- i.e., lessons learned.
- Also, always express your conclusion in form
of a recommendation for possible future actions. Finding
whether previous/current condition/status is right or wrong
is one thing.
But a good engineering analysis should also be able
to suggest a way to correct/obviate
the current problem.
- References
(References section)
Include only ones that were actually cited in your report.
Internet website/webpage are not citable
and should not used "as is" references -- find the correct
reference/source that the webpage was 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 such as EPA, USGS, NOAA, NWS, etc.)
Use correct formats (
see below for the format guideline)
- Appendix
(Appendix section)
Results/outputs from your
methodology/analyses.
|
Formatting Guideline for Final Project Report
|
- Your final report should be submitted in
single PDF file
that contains;
- a Final Report file (in a Word format)
-
Naming convention;
[Group Name]_wqmg_fa2024_project_report.doc
For example, a final report by a group 'ODU-AquaQual' would look like
ODU-AquaQual_wqmg_fa2024_project_report.pdf
- Data that used in your project should be included in your
Final Report file.
- Any additional supplementary materials should be included in your
Final Report file.
Again, regardless of how many number of data sets, appendice, supplementary
materials, etc. you have, be sure to incorporate them all into
single PDF file.
The project report
grading will be based on the problem conceptualization,
assumption and limitation, correctness of the procedures,
thoroughness of analysis, correct and meaningful
interpretation/conclusion/recommendation, and professionalism
demonstrated in presentation.
|
| |
-
In regard to the project report format, following guidelines shall rigorously
be used;
- Using wordprocessor,
no smaller than 11-point San Serif font (i.e.,
Times Roman or similar font) with 1.5 line spacing,
justified with at least 1-inch margins at top, bottom, and sides on
good quality white Letter size paper 8.5"x11" (21.5 x 28 cm).
- Do not number the Title page. However Abstract and Table of Contents
pages should be numbered in the bottom, aligned center using lowercase roman
numerals (i.e., i, ii, iii, etc.).
- Each page after the Table of Contents page should be numbered
properly in the bottom, aligned right using your
group name and numeral
combination. (i.e., Oink 1, Oink 2, and so forth). You don't have to
number Appendix.
- Use correct spelling, punctuation, grammar, and syntax. Spelling and
hyphenation of compound words follow the unabridged Webster's Third New
International Dictionary.
- Figures and Tables should be placed in text body, not in separate
pages or Appendix. A title for a Figure should be placed under the
Figure, and a title for a Table should be placed over the Table with
appropriate Figure/Table number.
- Final conclusion in the Discussion and
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 likely that you're not quite sure what you did. In such
case, check your hypothesis again.
- There is no page limit for your final report. However, keep in mind
that a good report is always succinct 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,"
"her," and "hers." Instead, use words such as "the authors," and
"researchers" for the objectivity.
- For reference(s) in your main body of the
report, use complete and accurate APA format references.
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, 2022) |
| two author |
(Marks and Bormann, 2024) |
| more than two authors |
(Megahan et al., 2024) |
| multiple references -- start from recent one |
(Alerich, 2023; Megahan et al., 2018; Marks and Bormann, 1985) |
| the same author with multiple references
-- start from recent one |
(Alerich, 2023;2021;2020;1997a;1997b) |
|
- For listing reference(s) in the References
section which should be at the end of your report, use standard format examples shown below.
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 author |
Marks, W.L. and M.S. Bormann |
| three authors or more more |
Megahan, D.D., M.S. Bormann and J.K. Alerich |
|
See more reference 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.
- Standard Formats for References section
- Abstract
-
Yoon, J., (2015), Optimal Site Characterization and Selection Criteria
for Oyster Restoration using Multicolinear Factorial Water Quality Approach,
General Oceanography II, OS31A-1981, Am. Geophysical Union (AGU).
- Book
-
Montgomery, D.C. and G.C. Runger, (2018),
Applied Statistics and Probability for Engineers, 7th Ed.,
John Wiley & Sons, ISBN: 978-1-119-40036-3.
- 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 (ASCE), Reston, Virginia, ISBN:
0784408696.
- Journal Article
-
Weyant, D.B. and J. Yoon (2024), Uranium Mine Proposed
Experimental Design for Natural Background Gross Gamma
Exposure Rates, Post Remediation Final Status Survey Sampling
Density, and Radiological Water Quality Modeling
for a Worst-case Catastrophic Failure, Coles Hill, Virginia,
Health Physics Journal, 2024 Sep 1;127(3):392-403. doi: 10.1097/HP.0000000000001823.
-
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
-
Shahvari, A. and J. Yoon, (2014), Comparative Study on Advective-Dispersive
Mixing Plume Characterization Models for Estimating Spatiotemporal Brine
Dilution from Desalination Process, In 2nd Annual Symposium on Desalination
and Water Reuse, Concentrate Management Session 1, 2014 ASCE EWRI Congress, Portland,
OR, June 1-5, 2014.
- Report
-
Yoon, J., (2008), Calibration of a Three-Dimensional, Numerical
Hydrodynamic Model of the Mattaponi Tidal Estuary, Virginia ,
City of Newport News, Grant No. 781041 & 781049.
|
|
Examples of Previous Project Topics
|
| |
- Relative Sensitivity Analysis of the Lagrangian Model for
Simulation of Horizontal Submerged Buoyant Jet in
Stagnant Ambient
- Evaluation of Contributing Factors for Cochlodinium Polykrikoides Bloom
in the Upper Branch of the Lafayette River
- Comparison of Monitoring Methods of Total Suspended Solids: Finding
A Real a Real Time Solution
- An Effect of Total Copper on Dissolved Oxygen with respect to the
Benthic Community in an Estuary and Evaluation of Secondary BMP Design to
Prevent Re-contamination
- Best Management Practices to Reduce Iron Contamination in Stormwater
Runoff from Salvage Yards
- Application of QUAL2K Model for the Sabattus River
- A Comparative Study of the Effectiveness of LID to Conventional
Stormwater Management Design
- Evaluation of the Effectiveness of the EPA SWMM Model in Estimation
the Load Reductions Provided when Implementing New Low Impact Design (LID)
Measures in an Urban Watershed
- Evaluation of Williamsburg Treatment Plant for the Removal of Select
Endocrine-Disrupting Compounds
- The Salton Sea: Planning and Management to Control Water Quality
- A Different Approach to Water Quality Permitting
- Lamberts Point BMP Post Implementation Audit
- NDMA- Nitrosodimethylamine (and Nistrosamines group): An emerging Water Quality Management Concern
- Evaluating Site Selection, Monitoring Guidelines and Alternative Substrates for Oyster Reef Restoration
- Assessment of the Mummichog (Fundulus Heteroclitus) as an Indicator of Environmental Contamination
- Green Technology Provides Innovative Approach to Meeting Chesapeake Bay TMDL: Hampton Roads Sanitation District's Struvite Recovery Facility
- Modeling of Brine Waste Discharge under Tidal Currents in Coral Bay
- Total Maximum Daily Load (TMDL) Study of River Ganga at Varanasi , India
- Application of EPA?s QUAL2K Model for Yamuna River
- Total Maximum Daily Load Implementation Strategies: Are They Working??
- Recommendations on the Control of Endocrine Disruptors for Publicly Owned Treatment Works
- Wastewater Reclamation Modeling for MBR WWTP Effluents, Stonehouse Development, VA
- Ambient Assessment of Chlorophyll a and Turbidity/TSS Data from the
Lower James River and Their
Impact on the
Availability of Light for Submerged Aquatic Vegetation
- The Elizabeth River, Is Progress Being Made, Small Step - NORSHIPCO
- Recommendations on the Control of Endocrine Disruptors for Publicly Owned Treatment Works
- Review of Efficiency of an Urban BMP for Harwoods Mill Reservoir
- War-Zone Effects and Years of Neglect: Remediation of Baghdad's Primary Water Supply, the Tigris River
- Evaluation of sources and potential impacts of perchlorate from allegany ballistics laboratory (ABL) into the potomac
river using a TMDL approach
- Chesapeake Bay Anoxic Zones - Why and Where
- Testing Of A Detention Pond As A BMP For Highway Runoff
- Hydrologic Influences on Fecal Coliform TMDL for Christians Creek, Virginia
- A Study of Enterococci Levels on the James River
- Analysis of the Factors Involved in the Development of a Total Maximum Daily Load for Tributyl Tin for the Elizabeth
River, Virginia
- Water Quality Criteria Assessment for the Elizabeth River
- Chemical and Physical Drivers in Lake Water Quality Analysis: A Case Study of Arizona's Lakes
- Big Woods Preliminary Stormwater Management Plan
- The Impact of Biofiltration From Bi-Valve Marine Organisms (Oysters) On Water Quality In The Chesapeake Bay
- Experiences in TMDL Development: The Trial and Error of Regulatory Personnel Modeling TMDLs
- Development of Groundwater Treatment Systems at the XYZ Landfill
- The feasibility of geographically enhancing an export coefficient model by using regression and uncertainty analysis
- Assessment of Total Suspended Solids in Birch Creek, Roanoke River Basin, VA using BASINS and QUAL2e Models
- 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
- 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
- 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
|
|
|
|
