11University of TorontoDepartment of Computer Science© 2012 Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. CSC302:Engineering Large Software SystemsProf Steve [email protected]://www.cs.toronto.edu/~sme/CSC302University of TorontoDepartment of Computer Science© 2012 Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 22University of TorontoDepartment of Computer Science© 2012 Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 3About the Course Course website www.cs.toronto.edu/~sme/CSC302/ Textbooks Fowler: UML Distilled (3rd Edition) (or equivalent) Lecture Notes Available on the course website prior to each lecture Coursework Involves an ongoing open source project, using legacy code Carried out in teams of 6 - 7 Each team submits one report per assignment Each team member also submits a peer-assessment form Use these to tell us how much your team mates contributed to the project If some members are contributing significantly more than others, we will adjust thegradesUniversity of TorontoDepartment of Computer Science© 2012 Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 4About the Course Build on what you’ve learned in CSC301 How do these skills scale up to larger projects? What new techniques and processes are needed? Important Topics advanced modeling (UML) project management reverse engineering requirements analysis verification and validation (especially testing) software architecture and design3University of TorontoDepartment of Computer Science© 2012 Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 5Assessment 4 team assignments:1. Phase 0: Reverse Engineering / Familiarization (5%) 3 weeks. Generate models from the legacy code2. Phase 1: Select and implement change requests (10%) 3 weeks. Submit analysis of CRs, plus implemented and tested changes3. Phase 2a: Requirements analysis and test plan (15%) 4 weeks. Analyse requests for new features, and write test cases4. Phase 2b: Implement new features and review process (15%) 3 weeks. Submit implemented and tested features, plus lessons learned report 2 tests: Midterm test (20%) Final Exam (35%) Must obtain at least 30% on this exam to pass the course.University of TorontoDepartment of Computer Science© 2012 Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 6Course Policies Assignment Deadlines Are very strict (use a U of T medical certificate if you are seriously ill) Assignments are due in the first 10 minutes of a lecture (i.e. 10:20am) Daily penalties apply to late work Re-grading Will only be done by the professor (TAs will not re-grade your work) The whole report will be re-graded (not just individual sections) Your mark may go up or down Communication Ask questions in Lectures and Tutorials Announcements will appear on the course website. Please check it regularly. TAs and instructor will not answer any queries related to the assignments inthe 24 hour period prior to the deadline I will rarely respond to email Spam filter may kill email from non-UofT adddresses I will (try to) answer emailed questions in the next available lecture/tutorial.4University of TorontoDepartment of Computer Science© 2012 Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 7Choose a Project Class vote next lecture everyone works on the same system Candidates: See course website: http://www.cs.toronto.edu/~sme/CSC302/University of TorontoDepartment of Computer Science© 2012 Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 8Canadian University SoftwareEngineering Conferencehttp://2012.cusec.net/5University of TorontoDepartment of Computer Science© 2012 Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 9Discussion1. Review of CSC3012. Your goals for this course3. Options: Bonus for changes accepted back into project base? Trade projects at end of phase 1: bonus for popular projects? Shorter iterations? TAʼs as “on-site users”? TAʼs as management consultants? Extra material on project management & Risk assessment? NASA Case studies? Climate Science Case studies?University of TorontoDepartment of Computer Science© 2012 Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 10Summary This course addresses the challenge of big projects Working with legacy code Analyzing problem situations Deciding which features can be feasibly implemented Delivering quality software systems This course is different to most CS courses You will be contributing to a much larger project You will decide for yourself what is feasible to do You will manage your own project risks You will figure out how to work in a (large?) team You will learn to think as an engineer Your mileage will vary There are no right and wrong answers We give credit for good judgment about which things to implement …and may penalize you for trying to do too
View Full Document
Unlocking...