Anne's Logbook
From SoftwarePractice.org
Contents |
16th August
- Team Formation
- Chosen Topic for assignment: Tagged Object Finder.
- Worked out set times for the MUP phases for the project
- Decided to meet every thursday, otherwise contact via email and instant messaging services
Group task for next meeting:
- Refresh Java
- Relevant research and reading
23rd August
Discussion on the following:
(1)Key System Elements:
- Tagged Object User
- Server
- Tag Reader
- Taged objects
- User interface
(2)Key Stakeholders
- Engineers/Developers
- Customers
(3)Key Risks Development Risks:
- Inadequacy of resources
Implementation Risks:
- Privacy issues
- System Maintenance
Activities carried out in relation to the assignment:
(1) CRC Modelling - did this as an activity in class which forced us to think about what classes we were going to have for the progoram.
Classes that we thought of were:
- GUI
- TaggedReader
- Tag
- Database
- GUIRelator
We identified what each class's responsbilities and collaborators would be.
30th August
(1) Worked on Sequence Diagrams in class
(2) Finalised everyone's responsibilities:
Myself:
- CRC cards
- Class interaction
David:
- Wiki content creation
- Scenarios
- Stakeholders
Lloyd:
- Sequence Diagram
- Essential use cases
- Use case diagrams
Shane:
- GUI design and implementation
- User interface design sketch
- Research on RFID Tag
6th September
Following were discussed among our team:
- Assessment of everyone's progress with their tasks.
- Checked classes with instructor for any further advice. Classes were satisfactory.
- Wiki documentation progress - team suggested that I use wiki tools to improve CRC cards
Following activities were done in regards to the assignment:
- Seuquence Diagrams
13th September
Discussed about building the GUI. We wanted the GUI to have the following properties:
- Touch screen
- Had a map
- Simple for user
Presentation preparation for 20th September:
Anne:
- Diagram of how software prototype fits into overall device/system
- Design issues or points of contention
David:
- 3-5 sentences capturing the essential scope and functionality of your
system
- Class diagram showing class names and relationships
Shane:
- Sketch/mockup of GUI design ideas
- A single sequence diagram related to a specific scenario/use case
Lloyd:
- A single example of a usage scenario
- The associated use case
Task for team for 17th September:
- Finalise slides for presentation
- Updated wiki
17th September
Met up and made sure wiki document reflected all the work done so far.
Prepared for class presentation and put slides together.
I had trouble with what "software prototype fitting into overall design/system" meant and had to seek advice from instructor and learnt that software prototype was the input and output of the system, a diagram showing this.
Group tasks:
- Finalised Presentation slides
- Ready for presentation
20th September
Initial Design Milestone.
Instructor recommended that we had to be more specific about our use case prototype.
27th Sept VC week
On E-mail:
Task breakdown for coding:
Shane: GUI/GUI relator
Lloyd and David: Database/Tag/GUIrelator
Anne: Tagged Reader
4th October
Discussion on coding:
Tag class finished.
Tagged reader class almost done.
18th October
Activity:
- Desgining test cases
Tag reader, Tag, Database, GUI finished.
Lloyd, David, Shane work on integrating classes with the GUI.
Anne: Write test cases
25th October
Project development, program is not finished.
27th Ocotber
Finalise program.
5th November
Finalise Wiki documentation.
