1 However ConferenceXP Presenter 10 weeks is too short Developed - PDF document

Introductions CSE 403 Software � Richard Anderson Engineering � Professor, Computer Science and Engineering � Joined UW in 1986 � Research interests � Educational Technology Richard Anderson � Algorithms Autumn 2002 � Industrial Experience � Microsoft, 2001-2002 (Sabbatical) � Design Intelligence, 1998-1999 (Summers) � Control-C Software, 1981 Teaching Assistant Course goal � Mark Yamagishi � To gain an understanding that � 1 st year EE grad student, Robotics and developing a software product is not merely a matter of programming controls � BS in EECS at UC Berkeley, 1999 � Raytheon Systems 1999-2000 � i2 Technologies 2000-2002 If it's not merely programming Project � What is it? � It's difficult to appreciate software engineering issues without working on a large project � Issues only become real on larger projects 1

However ConferenceXP Presenter � 10 weeks is too short � Developed last year at Microsoft Research � There will be a natural tendency to over emphasize development � Instructor oriented system � Synchronous display of slides on multiple � Teams will be homogenous machines � Integration of ink and slides � But that won't stop us � www.conferencexp.net Management charge Details � Develop a companion student product to go � Work in teams of size about 6 with ConferenceXP presenter � Management will specify teams � Target in class (laptop) and out of class use � Development environment � Management doesn't know what they really � C# using Visual Studio .NET want � Possible integration with existing code base � But student note taking associated with slides is the natural starting point � Other tools will be specified � But management wants it by Christmas � Deliverables expected in addition to � Release to Manufacturing (RTM) December 13 (working) code Team selection Evaluation � Project grade will have a large impact � Fill out background survey on course grade � Survey will be used only for assignment of teams � Project grade will (attempt to) � I t will not be used for assignment of roles in team recognize individual contributions � Team assignments will be announced � All artifacts will be considered in the Tuesday evaluation � Teams should appoint a Program Manager, � Quality matters but will otherwise be self organizing 2

Teams Milestones � Independent and non-competing � October 14, Project proposal, management pitch � Think of other teams as working for other organizations � October 28, Project specification � Code and document sharing between � November 14, Dev milestone teams is not permitted � November 27, Code complete � December 6, Code freeze � December 13, RTM Reading The Mythical Man-Month Expresses many key � Assigned texts � ideas of large scale � Mythical Man Month, Frederick Brooks software development Written in 1975, based � Code Complete, Steve McConnell � on I BM OS 360 Project � Supplementary papers (1965) Read past ancient � technology � Microfiche � Renting memory for $12 per Kilobyte-Month Code Complete Reading assignments � Monday, October 7 � Overview of Software � M M-M Chapters 1-8 Construction � Monday, October 14 � Practical developer � M M- M Chapters 9-15 oriented advice � A short writing assignment will be based on this reading 3

Administration � It's on the web . . . � Course mailing list – cse403@cs � To subscribe to the mailing list, send mail to cse403-request@cs � subscribe � Instructor/TA mailing addresses � anderson@cs.washington.edu � gishi@u.washington.edu 4