Team Wunuontoo: Project Plans
From SoftwarePractice.org
Contents |
Project Plan
This is a brief list of all the milestones that will be reached and their due dates for the system. It covers both the Software Architecture Documentation artefact as well as the Executatble Architecture code to be provided.
Milestone 1
| Milestone Date | Milestone Description | Completed |
| 10th Aug 08 | Team Registered | Yes |
| 10th Aug 08 | Topic Chosen | Yes |
| 10th Aug 08 | System Context, Scope & Usage Narratives Completed | Yes |
| 17th Aug 08 | Quality Attributes Defined | Yes |
| 24st Aug 08 | Conceptual Architecture Defined | Yes |
| 31th Aug 08 | Execution Architecture Defined | Yes |
| 8th Sep 08 | Implementation Architecture Defined | Yes |
| 9th Sep 08 | Documentation Completed | Yes |
| 9th Sep 08 | Preliminary Review Completed | Yes |
| 10th Sep 08 | Final Review of Documentation Completed | Yes |
| 11 Sep 08 | Project Presentation | Yes |
| 11 Sep 08 | Project Peer Review | Yes |
Other Plan Documents
The Meeting Minutes template is located here: Team_Wunuontoo:_Meeting_Minutes_Sample
| Meeting Date | Minutes |
| 7th Aug 08 | Team_Wunuontoo:_Meeting_7th_Aug |
| 14th Aug 08 | Team_Wunuontoo:_Meeting_14th_Aug |
| 21th Aug 08 | Team_Wunuontoo:_Meeting_21th_Aug |
| 28th Aug 08 | Team Wunuontoo:_Meeting_28th_Aug |
| 3rd Sept 08 | Team Wunuontoo:_Meeting_3rd_Sep |
| 4th Sept 08 | Team Wunuontoo:_Meeting_4th_Sep |
| 18th Sept 08 | Team Wunuontoo:_Meeting_18th_Sep |
| 24th Sep 08 | Team_Wunuontoo:_Meeting_24th_Sep |
| 4th Oct 08 | Team_Wunuontoo:_Meeting_4th_October |
| 9th Oct 08 | Team_Wunuontoo:_Meeting_9th_October |
| 13th Oct 08 | Team_Wunuontoo:_Meeting_13th_October |
The Team's Charter is Located here: Team_Wunuontoo:_Team_Charter
Team Member Logbooks
| Name | Logbook |
| James Dibley | T4_JamesD_Logbook |
| Dean McNiven | Link |
| Phillip Fyvie | Link |
| Rui Huang | Link |
| Daniel Le Clere | Link |
| Christopher Davies | Link |
Managing Distributed Artefact Creation/Modification
Software Architecture Documentation
All documentation will be created and altered on this Wiki, allowing for version control and revision.
Code & Other Artefacts
Managed through the SVN server mounted on https://swordfish.eng.uts.edu.au/projects/sa08spr_t4/svn
Access Details:
Username: Student ID #
Password: UTS Webmail password
If you need help setting up and/or using subversion see: Team_Wunuontoo:_Using_Subversion
The SVN server will manage all version control and no formal numbering system will be implemented.
Milestone 2
| Milestone Date | Milestone Description | Completed |
| xx | Team Assignment | Yes |
| xx | Finalise Documentation | No |
| xx | Cell and DHT Prototypes | No |
| xx | Preliminary Interface Testing | No |
| xx | Final Cell and DHT Prototypes | No |
| xx | Final Interface Testing | No |
| 28th Oct 08 | Final Review of Code | No |
| 30th Oct 08 | Demonstration | No |
| 6th Nov 08 | Presentation | No |
The work packages will be broken up as such
| Cell Work Packages | DHT Work Packages |
| Network | Database |
| Database | Network |
| Application | Application |
| GUI | GUI |
Program Standards for Development
The development team will all work with the following software:
- Eclipse Ganymede
- JDK 1.6, Update 7
Coding Standards
At the top of all classes the following should be included, please note the JDocs for @author and version. More on JDocs is here: http://java.sun.com/j2se/javadoc/writingdoccomments/index.html
/**
* Module Name: name * Description: Description goes here * @author: * @version: * Date: * Planned Improvements: * Test Plan: * Revision/Change Log: */
Variable Naming
Obviously naming variables should be done logically and succiently, and using the CamelCaps notation is preferred. For example portnr would not be acceptable, portNumber however would be.
Classes should begin with a capital letter, i.e. OperatorInteface.
Methods should be named as <verb><noun>, e.g. handleIncomingConnection.
Method Commenting
Again, we will be using JDocs to comment these.
/**
* Description: * @author: * @version: * @param * @return * @throws (if needed) **/
Inside the method, don't over or under comment, obviously use your head. For instance, topPanel.add(testChoicePanel) does not need a comment, whereas h.start() needs a comment as it isn't immediatly clear what h is (poor variable naming), or what start() will do.
Be succient and neat please!
Eclipse Guides
Team Assignments
The Cell Team will consist of:
- James Dibley
- Christopher Davies
- Phillip Fyvie
The DHT Team will consist of:
- Daniel Le Clere
- Ray Huang
- Dean McNiven
