Overview of Civ E 300: Civil Engineering Project Course Structure and Requirements
Civ E 300 is a project-based course focused on solving specific design problems in civil engineering. Students will form teams of 3-4 members, select a project topic, and develop a proposal under the guidance of a technical advisor. The course emphasizes project management skills including teamwork, problem analysis, design evaluation, and effective communication through proposals and presentations. Key components include client-team meetings, progress reporting, and formal evaluations. By the end, students will present their final report, showcasing their practical and technical abilities.
Overview of Civ E 300: Civil Engineering Project Course Structure and Requirements
E N D
Presentation Transcript
Civ E 300 Civil Engineering Project T. Hegazy Department of Civil Engineering
Outline • Course Objectives • Course Procedure and Requirements • Team, Project Topic • Meeting, Reporting, and Presentation… • Course Evaluation • Course Schedule
What Is Civ E 300 About? • You will select and work on a project to address a specific design problem • You will Learn • How to analyze problems • How to search for related information • How to identify and develop appropriate solutions • How to evaluate the solutions • Other Skills You will Learn • How to be a team player • How to give effective presentations • How to write proposals and reports • How to manage a project …
Form a Project Team Technical Advisor Identify a Project Topic Develop a Project Proposal Work on the Project Client/Team Meetings Write a Project Report Present Project How Does It Work?
Project Team • Each team should include 3~4 students • Each team must have a Project Manager for • tasks, schedule, work • meetings • Each team must decide a project topic and sign up (course website) before Jan. 13 (next Tuesday)
Project Topic • What is a Good Project Topic? • Not too big or too small • Not too complex or too simple • Make use of what you have learned (2A, 2B and 3A) • Reflect the common interests of the team members • How to Develop and Select a Project Topic? • Have a brainstorm session • Approach a professor
Technical Advisor ? • Roles of Technical Advisor: • Give advices on the topic you selected • Suggest references/information sources • They are very busy! – consultation time should not exceed 2 hours over your project life.
Client-Team Meetings • I will be the “Client” who has hired you (“Team”) for the “Job” • Each Client-Team Meeting will discuss • What have been done so far? • What are the problems encountered? • What is the plan for the following week(s)? • Each meeting will take app. 10 minutes. • Each team must submit a one-page Progress Summary for each meeting.
Schedule for Client-Team Meetings • See Schedule of events • You can choose your team’s meeting time
Project Reporting • Each Team is Required to Write Three (3) Reports: • Project Proposal (Week 4) • Final Report (Week 10) • Administration Report (Week 11)
Oral Presentations • Each team is required to give three oral presentations: • Proposal (Week 4) in Dr. Hegazy office • Progress (Week 8) in Dr. Hegazy office • Final (Week 11) in Classroom • Each presentation is limited to 10 minutes, plus 2 minutes for questions • In the final presentation only, presenter will be selected at random from his team • Look at “Guidelines for Effective Presentation”
Course Requirements & Evaluation • A formal written proposal (25%) • A formal oral presentation of project proposal (5%) • Interim Client-Team Meetings/Reports (10%) • Final client report (30%) • A formal oral presentation of final report (15%) • An administration report (5%)
Course Website • www.civil.uwaterloo/tarek/hegazy300.html
Your Tasks for This Week? • Find partners and form a team • Develop a project topic and find a tech. advisor • Sign up as a team (Due next Tues.)
Project Proposal? • What Is a Project Proposal? • ~15 pages plus appendices • References: • “Guidelines for Writing Project Proposals” • “Project Proposal Format” • Other References (listed on the Course Website)
Issues in Project Proposals • Very good overall: • Appearance: Format/Tables/Figures • Logical order • Management/Budget • Major issues: • Not sufficient background • Not clear what is the exact problem (project need) • Too much vague statements or lack of quantitative support (Statistics) • Mixed up between Introduction (problems), Objectives and Approach • Little literature review • Lack of details on Technical Approach
Progress Report • 2~3 pages • It should include: • Briefing on the activities performed to-data • Discussion on any additions / deletions to the scope • New improvement ideas, etc. • Revised Plan (Schedule / Cost)
Project Administration Report • 3~5 pages (Required at the end of the term) • It should include • Discussion on the differences between the planned project schedule/budget (from proposal) and the actual schedule/costs (from Records of project activities) • Discussion on how team performance would be improved if you were asked to do it again • Minutes of team meetings • Project Manager Duties
Project Administration Report • Using Microsoft Project • Define tasks and durations • Assign resources • Save Baseline • Tracking • Reports
Final Report • 15~20 pages of text + figures and tables • Objectives: • Define a problem. • Define a method to solve the problem. • Define budget, resources, time & costs. • Develop a solution within the budget. • Conclusions and recommendations.
