Team pLANer- 12/01/2011

What did we do:

• Ironed out final bugs. Fulfilled all test cases.
• Converted to a single easy to use windows executable (Using Py2exe).
• Created setup files for windows client server.
• Re ran all testing after bugs were fixed to confirm the fixes.

• Some computer specific run-time issues popped up.
• Warrant further research
• Unforeseen bugs.
• Pushing the project to a release on Linux and Mac.
• Finals are coming. Prepare yourself.

• Implement all the features we didn’t get to (outlined in our PowerPoint from class)
• Completely document all the current features and code we have
• Add support to text people
• Real world testing using the members of the RGA club at RPI.

Team pLANer- 12/01/2011

What did we do this week?

• Finished implementing the network code backend
• Finished the tournament bracket generation and “win reporting”

What are the impediments or risks?

• A few bugs, only 1 hurts a usecase
• 1 Feature cut -- No texting before an upcoming match =(

What are our plans for next week?

• Prepare the presentation
• Fix some bugs

Team pLANer- 11/28/2011

What did we do this week?

• Nothing.  Working on exam.

What are the impediments or risks?

• Exam was hard.

What are our plans for next week?

• Finish the program

Team pLANer- 11/14/2011

What did we do this week?

• Worked on integrating the network, GUI, and database code

What are the impediments or risks?

• Final Exam due Monday and upcomming Thanksgiving break
• Hopefully we will effectively manage our time

What are our plans for next week?

• Finalize code integration
• Add alert messaging via email

Team pLANer- 11/14/2011

What did we do this week?

• Refactored NetCode
• Partially Integrated Twisted networking library
• Our current choke hold. Needs more work.
• Extended database code
• Handles Tournaments, LANs, and Users (Everything)
• Ready to talk with Twisted netcode
• Refactored code to follow 9 rules of object calisthenics

What are the impediments or risks?

• Netcode is behind
• Twisted installer isn’t working.
• Have to compile from source for use, which is a time sink.

What are our plans for next week?

• Get the network coding fully integrated
• Will provide persistent http connections
• By next week, should have a fully functioning prototype
• Optional features left to implement after this

Feedback from Being Reviewed by

• Code is very well commented
• Code is very well organized
• Code is consistent and readable
• Code matches the class diagram
• Code matches the coding standard
• No suggestions

Team pLANer- 11/3/2011

What did we do this week?

• GUI work.
• Partially implemented the finalized layout
• Database can now accept user names, and all authentication information
• Utilizes SQLite

What are the impediments or risks?

• Moving GUI design from paper/planning to actual code
• May reveal unforseen issues

What are our plans for next week?

• Finish GUI implementing
• Apply Netcode (Twisted library) to current project
• Prepare for Stakeholder presentation
• Have we met the minimums?

Team pLANer- 10/27/2011

What did we do this week?

• (Skurka) Worked through some twisted tutorials
• (Mike) Tournament Bracket Drawing.
• Layouts, etc.
• (Alex) GUI work.
• Coded more on it.
• (Brendan) Database tweaking
• Organized tables to work with calls from client.

What are the impediments or risks?

• Lot of code. Not a lot of time!

What are our plans for next week?

• Finalize overall GUI layout.
• Lock down the final organization.

Team pLANer- 10/24/2011

What did we do this week?

• Elaboration
• Completed Iteration 1
• Demo!

What are the impediments or risks?

• None so far this week

What are our plans for next week?

• Work on iteration 2

Team pLANer- 10/20/2011

What did we do this week?

• Tried to get Python communicating with database in PostgreSQL
• Investigated SQLite for Python
• Implemented Main GUI window in Glade UI Designer

What are the impediments or risks?

• Can’t get Python talking to Postgre Database
• If we switch to SQLite, will it be fast enough?

What are our plans for next week?

• Keep working on GUI
• Keep working on Database
• Coding party this weekend
• Write Elaboration Deliverable

Team pLANer- 10/17/2011

What did we do this week?

• Set up the database (Postgre SQL)
• Designed Most of the GUI
• Main window
• LAN party creation screen
• Tournament creation screen

What are the impediments or risks?

• Impediment: Corrupted SQL install
• Risk: Python modules not found on some computers?
• Risk: Glade UI designer crashes every four seconds
• Solution: Press Ctrl-S every 5 milliseconds.

What are our plans for next week?

• Implement GUI Windows
• Continue programming the database side

Team pLANer- 10/13/2011

What did we do this week?

• Looked into the elaboration deliverable
• Leverage workload versus time left to prevent getting behind.
• Domain model diagram modeled after example in slides
• Didn’t get to any major coding, no pushes

What are the impediments or risks?

• Time commitments from other assignments

What are our plans for next week?

• Un-changed from Tuesday
• Keep working on the GUI
• Implement Basic Registration (No verification)
• Use actual database entries for username/salted password
• Begin work on elaboration deliverable
• Set a day to meet this weekend

Team pLANer- 10/11/2011

What did we do this week?

• Lots of research into SSL
• Decided not to use it
• Using random key hashing and salted password system instead
• Implemented random key hashing and debugged/tested it.
• Confirmed that we’re secure enough now (Mitigated previous risk)

What are the impediments or risks?

• Server load?

What are our plans for next week?

• Keep working on the GUI
• Implement Basic Registration (No verification)
• Use actual database entries for username/salted password

Notes: Make sure load testing is documented. Also make sure that the security and load requirements are documented.

Team pLANer- 10/6/2011

What did we do this week?

• Finished Inception
• Developed a project schedule
• Further discussed backend implementation
• Wrote some more code, specifically login validation code

What are the impediments or risks?

• Deadlines
• How secure is considered good enough for logging in to the server?

What are our plans for next week?

• Discuss Elaboration Deliverable
• Improve project schedule
• Work on GUI
• Work on secure SSL Handshake for client connections
• Get basic database communication working
• Continue to write code, specifically the main GUI windows

-Team pLANer – 10/3/2011 -

What did we do this week?

• Created the Inception write up
• Continued to work on code
• Discussed access control based on user (eg. admin)

What are the impediments or risks?

• miscommunication in how tournaments would be scheduled, but we’ve since rectified it.
• may be more miscommunications

What are our plans for next week?

• Continue working on code
• Revise the Inception write up

-Team pLANer – 9/29/2011 -

What did we do this week?

• Collaborated on the Inception write up
• Continued to work on code

What are the impediments or risks?

• miscommunication in how tournaments would be scheduled, but we’ve since rectified it.
• may be more miscommunications

What are our plans for next week?

• Continue working on code
• Finish Inception

-Team pLANer – 9/26/2011 -

What did we do this week?

• Another Group Meeting
• Assign subsystems to group members
• Checked in code
• All group members set up PyDev and Eclipse for Python development
• Smart Git front end for git version control
• Collaborated on the Inception write up
• Fleshed out features blurb

What are the impediments or risks?

• Difficulties splitting up subsystems; assigning to members
• Leverage versus abilties

What are our plans for next week?

• Continue working on code
• Complete class diagram

-Team pLANer – 9/22/2011 -

What did we do this week?

• Group Meeting
• Set up development environment on some computers
• Fixed OS issues on others
• Wrote In Depth project feature description
• Wrote some client and server code

What are the impediments or risks?

• Learning curve on sourceforge/git/python and technologies

What are our plans for next week?

• Assign subsystems to group members
• Start designing system interaction
• Continue working on code

-Team pLANer – 9/19/2011 -

What did we do this week?

• Another Group Meeting
• Set up source forge
• Wrote Peer Review form
• Set up git repository
• Checked in code
• Setup PyDev and Eclipse for Python development
• Back end Thoughts: PostgreSQL

What are the impediments or risks?

• Might be disagreements about how pLANer should work
• Learning new API for Python (PyTk or PyQt)

What are our plans for next week?

• Develop Project Description
• Set up IDE for all developers (Eclipse and PyDev)
• Back end Encryption?

-Team pLANer – 9/15/2011 -

What did we do this week?

• Group Meeting
• Discussed primary features of the application and programming environment. (Python)
• Discussed where to set up git/wiki/website repository (Sourceforge)
• Planner exists already
• “TournypLANner”?
• Discussed high level model Server/client
• Weekly meetings, on the weekend.
• Wrote Project description

What are the impediments or risks?

• A lot of possible expansion, must avoid feature creep.

What are our plans for next week?

• Develop concrete list of required features
• Explain features in depth
• Construct high level block diagram of all systems
• Assign tasks to all group members