Classwork‎ > ‎Project Milestones‎ > ‎

Wrap Up

CSE 403 Final Write Up

This document reflects all the work you have done in CSE 403 with regards to how you engineered your project.  Answer all the questions.  You may include links to other documents or locations on your wiki or you may inline all of your answers.  Be sure that the links are “clickable” from this document.  Include the question preceding your answer in your document. 


We prefer you turn in this write up as an HTML document that we can access from the web.   However, other forms (such as a MS Word document) are fine too.  Make sure the links you use are clickable.  You will use dropbox to turn in the link to this document.  An MS Word document of this page is included here, if you want to use it as a template for your answers.


·      Do you have written requirements?  Are they up to date?

·      What is the vision of your project?  What's the one sentence, 1 paragraph, and 1 page summary of what your project is?

·      What are the key metrics for success?  When will you plan to achieve various goals?  Are you achieving them?

·      Do you have a requirements review process?  What is it?  Do you use it?

·      Did you collect feedback?  What was it?  How did you use it?

·      How close does your final deliverable match the original requirement/goals?  Were you successful at delivering the product?

·      What would  your plans be there is to be a release 4, if there were to be one?

·      What is the longer term (1 year) for your project?


·      Do you have written design specifications?  Are they up to date?

·      Do you have a design review process?  What is it?  Do you use it?

·      Is your software modular?  Do you have clean interfaces -- interfaces that are "cleanly" separated from implementation?

·      Is your software loosely coupled?  Your organization?  Has it aided in the success of your project?


·      What is your architecture? Is there an up to date document to reflect this?

·      What is your run time platform?  How did you choose it?

·      Do you have an architecture review process? What is it? Do you use it?

·      What is your design center for scale?  Any idea how you will grow beyond that?


·      Do you have coding standards?  What is it? Do you use it?

·      Do you successfully use a source code/version control system?

·      What is your version management strategy?  Branch a lot?  Branch as little as possible?  What is your team's philosophy on branching?


·      What is your test strategy?  Do you have a regression test suite?

·      Do you have a bug database? Do you use it?  How do you use it? (What's the process for filing, triaging, fixing bugs, and deploying fixes? How many bugs have been filed?

·      Do you have a code review process?  What is it? Do you use it?

·      Do you have a test server?  Where is it deployed?  How close does it look like the live site?


·      Where do you deploy your live site?  Why did you choose this? What are the physical and logical topologies?

·      Do you have a build process?  Is it nightly?

·      What is your deployment process?  How many steps?  Is it documented?

·      Do you have a staging server?  Where is it deployed?  How close does it look like to the live site?

·      Do you back up your software?  Your data?  Can you recover?  Under what conditions?

·      Do you have monitoring software in place?  What is it? How do you use it?


·      What is the process for delivering software?  How did you come to this decision?

·      What was your team organization structure like? Who does what? How did this work out? In retrospect, would you have organized your team differently?

·      What are the communication mechanisms your team uses?  Discuss all the methods/processes in addition to your wiki

·      Did your team use weekly status reports to communicate?  An alternative mechanism?

·      Do you have an up to date schedule?

·      If a new developer comes on board, how do they bring up a development environment?  Is it documented?

·      Have you released your project onto GitHub for public consumption?

·      Do individuals have GitHub projects where they show case your project?  Why or why not?

·      Where do you use divide and conquer in your project?


·      What decisions did your team make that turned out to be mistakes?  How did you correct for them?

·      What three big lessons did you learn from working on this project?

Wayne Yamamoto,
Nov 25, 2012, 7:40 PM