1 / 7

CSE 436 Software Engineering Workshop Course Overview

CSE 436 Software Engineering Workshop Course Overview. Christopher Gill CSE 436 January 2007 Department of Computer Science and Engineering. Monday January 22, 2007. Please write and sign your name on roster Discussion today will focus on course itself

gtoby
Download Presentation

CSE 436 Software Engineering Workshop Course Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CSE 436 Software Engineering WorkshopCourse Overview Christopher Gill CSE 436 January 2007 Department of Computer Science and Engineering

  2. Monday January 22, 2007 • Please write and sign your name on roster • Discussion today will focus on course itself • Overview, expectations, questions you may have • Introductory lecture on software requirements • Followed by (or in-line) discussion of material • Working session on project descriptions/roles • Discover and discuss ideas, fill in details • Web site, questionaire posted by 2pm today • Due via e-mail/hardcopy by 2pm tomorrow • Team/project/role info e-mailed by 5pm tomorrow

  3. Course Description • Explores concepts and issues related to large-scale software systems development • Teams will be formed, to emulate industrial development • Projects cover life-cycle phases from requirements analysis, to software design, and implementation • A studio course • Lecture material each week, 25% or less of classroom time • Most of the time will be given to open discussion and work • Teams should be prepared to present and discuss each time • Prerequisites: CSE 332S (f.k.a. CS 342S)

  4. Grading • 50% Process and product documents from teams • Requirements • Software architecture • Design and implementation • 30% two individual exams (both take-home) • Midterm 10% of grade • Final 20% of grade • 20% full-circle review of contributions & participation • Feedback from teammates, other teams, professor, TAs • Deadlines are firm, what is handed in gets graded • Communicate problems and concerns early, get help

  5. Key Resources • Lecture and lab sessions (attendance mandatory) • Each other (except on exams) • Professor (Chris Gill, cdgill@cse.wustl.edu) • Teaching assistants (Carol Brickman, Jared Lerner) • External “Customer” (John Aughey) • Team wiki, cvs or other resources you may set up • Course web page (under construction, to appear) • Course newsgroup (under construction, to appear) • Outside sources of information you can find • Especially books, papers, journals, Google, etc.

  6. A Monday in the Life of CSE 436 • Students, professor, and TAs attend (10 to 1) • Bring a sack lunch if you would like to do so • Let professor know as early as possible if you have a conflict, illness, etc. • Teams, professor, TAs discuss progress • A chance for teams to note inter-dependences • Professor presents new lecture material • Students, professor, TAs discuss material • Working session on next project topics • A chance for teams to negotiate collaborations

  7. A Friday in the Life of CSE 436 • Team members, professor, and assigned TA attend regularly scheduled 1 hour team sessions • Let professor and your team members know as early as possible if you have a conflict, illness, etc. • Professor will be away Friday April 6, 2007 at RTAS 2007, will make special arrangements for team meetings that day • Team, professor, TA discuss progress • A chance for detailed review, discussion, feedback • Working session on next project topics • A chance for teams to solicit guidance, pose ideas

More Related