Recent Changes - Search:
ECG Home

GitHub

People

Publications

Calendar

Projects

Fall 2017

Older Courses

Spring 2017

Fall 2016

Spring 2016

Fall 2015

Spring 2015

Fall 2014

Spring 2014

Fall 2013

Spring 2013

Fall 2012

Spring 2012

Fall 2011

Spring 2011

Fall 2010

Spring 2010

Fall 2009

Spring 2009

Fall 2008

Spring 2008

Fall 2007

HOWTOs

edit SideBar

Assignments

Assignments Discussion Group Theater Apps Course Advertisement
Lecture Blog Design Patterns SVN Server Flex Links Student Wikis Bug Tracker

Boehm Reading — Due Wed May 6

  • reading is on the Google group: http://91411-s09.googlegroups.com/web/p12-boehm.pdf
  • please prepare a 2-page summary—this looks like a good paper
  • the summary should include a reflection on this semester's work, situating it in the historical continuum presented in the paper.

Theater Project Beta — Due Fri Mar 13

  • check Flex source code into SVN
  • upload .swf file to wiki and create link to it (or embed in its own page)
  • create release notes for it (e.g., what works, what doesn't, what was annoying, what was fun)

Spolsky Reading — Due Wed Mar 11

Theater Project Alpha 2 — Due Fri Mar 6

  • check Flex source code into SVN
  • upload .swf file to wiki and create link to it (or embed in its own page)
  • create release notes for it

Theater Project Alpha 1 — Due Fri Feb 27

  • check Flex source code into SVN
  • upload .swf file to wiki and create link to it (or embed in its own page)

Theater Project Proposal — due Monday Feb 23

  • See Lecture Blog for class notes from Fri Feb 20.
  • From a user's standpoint, the proposal should present 3 stages of completion of the project, representing alpha 1 (end of implementation week 1), alpha 2 (week 2), and beta (week 3). Please assign code-names to the three releases. Then you can say (e.g.), “The alpha 1 release, code-named ‘gimpy,’ will have the following features ... (etc.).”
  • From a software-internals point of view, the proposal should reference ideas in the SWEBOK chapter on Software Design. You don't need a separate discussion of all three stages—focus on the essential core: what are pieces, and how will they fit together.
  • Make ample use of diagrams/drawings to illustrate your ideas. There should be at least 1 drawing representing the UI for each of the 3 releases, and at least 1 drawing illustrating aspects of the internal software design. You are welcome to create free-hand sketches and scan them, versus making electronic diagrams, if you think that will be more effective/save time.
  • The total document should be 6 to 8 pages, or longer if appropriate (e.g., you have lots of diagrams).
  • Post your proposal directly to your wiki. Upload the document using the Attach: wiki markup syntax. Note: do not name the document proposal.doc. Because we're all sharing the same upload directory, include your initials or username as part of the filename; e.g., fgm-theater-proposal.doc.

Week 4

due Friday Feb 20

Week 3 — AS3 and MMM Chapters 1 - 3

due Friday Feb 13

  • read chapters 1 - 3 of Mythical Man Month
    • write 1 page of bullet lists of key ideas in each of the 3 chapters (1 to 5 ideas per chapter, as appropriate)
    • write 2 pages of narrative: reflections on your past experiences and how they connect to this work
  • Amazon S3 and Flex

Week 1 — Introduction to Flex

Edit - History - Print - Recent Changes - Search
Page last modified on May 01, 2009, at 04:54 PM