Final Project – Due Dec 14th

Posted on by gmadey
  • Final project due Dec. 14th before the final, but extra credit if submitted by Dec 10th (midnight)
  • Deliverables:
    • Promotional description of the product (press release style or a promotional flier)
    • Link to product
    • User manual
    • Tutorial
    • Software architecture, technology stack, and design overview
    • Code
    • Code documentation
    • Final Gantt Chart
    • Requirements document
    • A statement of who contributed to each part (if multiple contributors, percentage contribution, and what part if relevant)
    • Other documentation deliverables as appropriate?
  • Send all deliverables to:  gmadey, qzhi, and snjoroge as a team submission (Subject line: Final Project – Team #). If needed, send zipped folder of all files.

Lecture Notes – Dec 6th

Posted on by gmadey

Agenda

  • Study guide for the final exam
    • One page, 8 1/2″ x 11″, front-back “cheat sheet” allowed for the exam
    • One half of final will be quiz style questions of which some will come directly from quizzes; other questions from the class notes. See all quizzes below.
    • One half of final will be code focused questions, e.g.,
      • Explain presented (pseudo) code, what is it doing
      • Find bug in code
      • Modify code to make it do something different
    • Suggestions on how to review for the final
      • Review syllabus
      • Review class notes
        • Give extra attention to terms, acronyms and ideas explicitly listed in the notes.
        • For Wikipedia links, review the intro and additional sections associated with the term listed in the notes.
      • Review programming assignments
        • Review code examples examples in the notes
        • Review the code you and your team wrote for the assignments
          • Hint: each team might conduct a code walkthrough for their team projects
        • Sample questions
          • Explain presented (pseudo) code, and what is it doing:
          • keyword = request.GET.get('keyword')
Search.objects.filter(name=keyword).count()
          • Find the bug in the following model definition and propose a solution.
          • class Recipe(model):
 id = AutoField()
 name = CharField(max_length=100)
 views = CharField(default=0)
          • Example provided in class

Lecture Notes – Nov 29th

Posted on by gmadey

Agenda:

Mobile web development

Live demo and class participation in web application exercise

HW 14 – Due Dec 1st

Posted on by gmadey
  • Continue development on your project
  • Update the Gantt chart to reflect your progress
  • Submit first draft of your project documentation
  • Send: 1) link to project 2) updated Gantt chart (*.gan file) and 3) first draft of documentation to:  gmadey, qzhi, and snjoroge as a team submission (Subject line: HW 14 – Team #).

Lecture Notes – Nov 27th

Posted on by gmadey

Class agenda

HW 13 – Due Nov 26th

Posted on by gmadey
  • Continue software development on your project
  • Update the Gantt chart to reflect:
    • First draft of your project documentation will be due on Dec. 1st
    • Progress (percent complete) on tasks in Gantt chart
  • Send: 1) link to project and 2) updated Gantt chart (*.gan file) to  gmadey, qzhi, and snjoroge as a team submission (Subject line: HW 13 – Team #).

Lecture Notes – Nov 20th

Posted on by gmadey

Class agenda

HW 12 – Due Nov 17th

Posted on by gmadey
  • First “minimum viable product” of your project due online by midnight, November 17.
  • Email URL and a few tips/hints on how to execute/evaluate the application to gmadey, qzhi, and snjoroge as a team (Subject line: HW 12 – Team #). Tell us what works and what is a placeholder in the email note.
  • Download and play with the program GanttProject (GPL v.3)
  • Also attach to the email:
    • An update to your requirements document
    • Include as an attachment a GanttProject “.gan” file that includes 1) your Gantt chart (updated if needed) and 2) a Resources chart presenting the team members and their effort allocations on the project.