Team Log
From SoftwarePractice.org
Ground Rules
1. Meeting every Thursday during tutorial class CB02.04.22. Also before and after class.
2. Contact members on mobile when late or cannot attend meetings.
3. Every meeting will be a working meeting. This means all members of team will have to participate in group discussion and work together to produce good quality work without the need of revising each other's work again and again.
4. Split work equally.
5. Exchange emails. Communicate through email and check emails regularly.
6. Communicate via MSN or discussion board if it is required.
7. Individual log must be completed every Monday on Wiki.
8. Every member must read and check this Team Log page all the time. As all meeting agenda for thursday group meeting are set out here and logged at end of day.
Back to Home
Planning of the Project - Phases of the MUP
Inception
The inception stage is to establish a 'business case' for the system.
- Team has been formed: T7 on 16/08/07
- Team members consists of - Daniel So, Jimmy Tang and Anna Tang
- Project working on: RFID Tagged Object Finder
- Ground rules established already here
- Initial documentation on Wiki: 19/08/07
- A schedule is agreed on. Here is a Gantt chart which shows the for the full project lifecycle.
- Identify key system elements: Please visit Individual Log for each team member's thoughts
- Identify key stakeholders: Please visit Individual Log for each team member's thoughts
- Identify key risks: Please visit Individual Log for each team member's thoughts
Elaboration
This phase establishes system requirements and architecture for the system.
- Create key use cases: Please visit Individual Log for each team member's thoughts
- Use-case diagrams:
- Proposed design user:
- Initial class diagram:
- Initial sequence diagram:
- Elaborate key risks:
Construction
This stage focuses on the building and testing of the system. There are 3 iterations that this project goes through.
- Iteration 1:
- Iteration 2:
- Iteration 3:
Transition
This is the final phase of the MUP. This stage ensures that there is enough time to deliver the system's code, user interface design and documentation.
Submissions:
- Project Milestone Initial Design: 20/09/07
- Post BlueJ folder and support files on UTSonline digital dropbox: 1/11/07
- Full Documenation on Wiki: 8/11/07
- Completed individual logbook: 8/11/07
Team Progress
This section logs all the outcome for meetings held on Thursdays and also log what needs to be done in the following week.
16 August
- Form team.
- Decided on project topic.
- Initial creation of Wiki article.
- Each member to prepare and put thoughts into Inception and Elaboration phase.
- Then every member to log their thoughts on Individual Log page.
23 August - Meeting 1 Duration 2 hrs
Present: All
- First meeting with the team
- Discussed the topic and the scope of the project
- Come up with classes and prepared for attributes within the class. Daniel has volunteered to re-produce the class diagram on proper a drawing program like Visio.
- CRC modelling
- Decided on which scenarios to put up
30 August - Meeting 2 Duration 2.5 hrs
Present: All
- Discussed about one good sequence diagram. Main sequence we believe was the search function
- The initial sequence diagram was a preliminary to get a design a little edge start.
- Finalised class diagram as Danial had a few issues
- Discuss how the GUI will look like. Good input from every member
12 September - Meeting 3 Duration 2 hrs
Present: All
- Main meeting reason was to get the initial milestone done properly and executed efficiently.
- Realisation - Presentation of the initial milestone is due
- We have to follow a presentation guide as follows:
1. Introduction: includes project description, scope 2. Description of how prototype fills into overall device system key elements 3. A single usage scenario 4. Use case 5. Class diagram 6. A single sequence diagram that fits the usage scenario 7. A sketch or mock up of GUI 8. Design issues
- Presentation Breakdown: Anna - 1, 2, 3, 4 Daniel - 5, 6 Jimmy - 7, 8, 9
13 September - Meeting 4 Duration 2 hrs
Present: All
- Discuss about what to present for each member and have come up with content for every section
- The GUI was discussed and rough sketched by Jimmy
- Daniel was suppose to finalise our class diagram but has not done it yet but said that he will in time for the presentation
- Our main discussion was the concern of how to implement the code
- We believe there will be a lot of changes during our progress
- Issues that we have are - lack of resources, knowledge and time management - all these issues were discussed and we have agreed to do more research before we meet up every time so we can all teach and learn from each other
19 September - Meeting 5 Duration 2 hrs
Present: Jimmy and Anna, Absent: Daniel
- Prepare for presentation tomorrow
- Completed presentation slides for Jimmy's and Anna's
- Rehearsed our presentation sections
20 September - Meeting 6 Duration 3.5 hrs
Present: All
- Completed all presentation slides
- Rehearsed
- Presented our slides at 2.30pm
- We believed that it went quite well
11 October - Meeting 7 Duration 2.5 hrs
Present: Jimmy and Anna, Absent: Daniel
- We were suppose to have a meeting 2 weeks ago but everyone had other commitments and Anna has been ill.
- Main purpose of meeting was to get our project back on track and propose other requirements and designs.
- Anna proposed new GUI design as the scope has changed greatly, we believe we are unable to fulfill our original goal and cut down on requirements.
- We had to redesign our class digram. Not enough time to complete all tasks. We redesign to fit the MVC (Model/View/Control) approach.
18 October - Meeting 8 Duration 2 hrs
Present: Jimmy and Anna, Absent: Daniel
- Anna has begun coding the new GUI on Java BlueJ
- Discussed the new GUI design
- Split coding work up - Jimmy: Back-end, Anna: Front-end
20 October - Meeting 9 Duration 3.5 hrs
Present: All
- Crunch time.
- The new GUI layout was completed and shown at the meeting.
- The map had to be re-designed and this task was given to Daniel
- Jimmy continued to work on the array and saving of data
- Anna has started the control class that will integrate both the GUI and the model classes together
24 October - Meeting 10 Duration 2 hrs
Present: Jimmy and Anna, Absent: Daniel
- Discussed the backend operation realised that we had to work together to get the backend and frontend working in the integration process.
- Discussed the integration process
- Believe that Daniel is no longer participating, so extra work was assigned just for the 2 of the members
- Will use xsteam-1.2.jar package library because it is easy to store xml files
25 October - Meeting 11 Duration 2 hrs
Present: Jimmy and Anna, Absent: Daniel
- Crunch time.
- Continue to work on our parts
- Decompose classes
- Daniel has told us he has given up
30 October - Meeting 12 Duration 4 hrs
Present: Jimmy and Anna, Absent: Daniel
- Emailed Lian (Customer) before about our situation
- Continued on our parts and slowly integrating while we can
31 October - Meeting 13 Duration 4 hrs
Present: Jimmy and Anna, Absent: Daniel
- Vector working, XML working, polished GUI and Integration was done
- Storing, Deleting, Searching and works fine through GUI and saving in vector and XML file
- Tomorrow is the deadline for demonstrating our program.
- We have not met a few requirements we know but we have tired our best due to our condition.
1 November - Meeting 14 Duration 2 hrs
Present: Jimmy and Anna, Absent: Daniel
- Met up to do the JUnit and Testing classes.
- We had some trouble trying to do it without knowing what to do
- Prepared for the demonstration
