Minutes of Meeting
Project
Responsible
BuySafe
Date
Start-end
time
Location
/type
Saša Marjančić
Attended by
Juraj Murgić
Saša Marjančić
Želimir Kompes
Fouad Yaseen
Xiaowei Ma
Trevor Jagerfield
Location
Home
Home
Home
Home
Home
Home
26.10.2012.
21:00-22:45
Audio Conference
Zagreb - Västeras
Remarks
1. Parsing of data
We started this meeting talking about parsing of data that is going to be required for this project.
Trevor created an application using C# that can be used for parsing of data. That application is going to
be a valuable source of knowledge for building future, more complex, data parsers that our application is
going to use.
CONCLUSION: Data parsing will require a lot of our attention.
ACTION: Explore our options regarding data parsing.
2. Web server
Next agenda of today meeting was about a web server. We had to decide if we were going to use a
web server to test our application or just local data. Everybody agreed that a web server will give us
much more benefits over local data. It could be used not just to store a database, but also for a lot of
other things concerning our project.
CONCLUSION: Web server should be a useful asset for our project.
ACTION: Juraj will talk to Marin about setting up a web server.
3. Testing the mobile application
Testing the mobile application will be one of the most important parts of the project, as this
application will be directly used by the customers. There were two options available for this situation:
1. Use an emulator to test
2. Use a mobile phone to test
1
Želimir and Fouad said, based on their previous experience, that emulator testing works just fine and will
be sufficient for our needs. Having that in mind if it will be possible, the application will also going to be
tested on a mobile phone afterwards.
CONCLUSION: Emulator testing of mobile applications will suffice for our project.
ACTION: Test the application on an emulator and mobile phone if possible.
4. Wal-Mart1 data
Trevor found another possible source of data for our project. The Wal-Mart online database can be
queried for products and contains the following information:
• UPC number
• Item Description
• Product Reviews
• Ingredients
• Q&A Exchange
• Specifications
• Directions
• Nutrition Facts
• More Info
It also allows search of products by UPC number, which is exactly what we need.
CONCLUSION: Wal-Mart is another possible data source.
ACTION: Explore ways of using this data source.
5. Project milestones
After discussing another possible source of data we needed to address the project milestones.
Xiaowei stated that milestones are a certain times in project development that mark the end of a project
phase or the completion of an important deliverable. Milestones will have to be carefully defined to
reflect the needs of our project development.
CONCLUSION: Milestones are an important part of project development tracking.
ACTION: Juraj will define the required milestones.
6. Software development process
The software development process was the next topic that we had to go through. A few possible
options were mentioned during the conversation:
1. Waterfall process
2. Agile methods
3. Scrum
Scrum seemed to have been the most interesting option and Trevor also found a software development
tool that is based on Scrum. The tool is called Kunagi2, a web-based tool for integrated agile project
management and collaboration. Kunagi and Scrum seem to be the best options for now, but we need to
think more about this and settle it during the next meeting.
CONCLUSION: Kunagi seems to be a great project management tool.
ACTION: Decide which software development process is going to be used and which tools are going to support it.
1
2
http://www.walmart.com/
http://kunagi.org/
2
7. Project plan presentation
Next Tuesday, 2012-10-30, we are going to present our Project Plan, so we decided to talk about
what is required for that presentation. The following topics should be included in the presentation:
 Short overview of the project
 Development methodology
 Deliverables
 Communication
 Milestones
 Activity plan
 Project risks
We went through all of the topics and agreed on the basic information, the rest will be handled by the
presenters. After that we had to agree who is going to present. Since he did such a great job last time,
Juraj will do it again, but this time he will be joined by Trevor.
CONCLUSION: Project Plan presentation is due next Tuesday, 30-10-2012, Juraj and Trevor are going to present it.
ACTION: Juraj and Trevor will create the presentation and practice presenting.
8. Development environment
To make certain that we are all going to use the same development environment Juraj and Želimir
are going to prepare it for all the team members, who are all going to download it afterwards. The
environment used is going to be Eclipse. Juraj and Želimir are also going to create a very basic prototype
so we can all test it. Since there are some more important things to do at the moment, this is going to be
done sometime next week.
CONCLUSION: Eclipse will be the official development environment.
ACTION: Juraj and Želimir will prepare it for everybody and create a basic prototype.
9. Use cases
To be able to write requirements definition document, we also had to discuss possible use cases.
These use cases were separated into two groups, main and optional functionality. Some of the possible
use cases that are going to be included in the project are:
Main functionality:
 “user scans product”
 “user searches product by name”
 “user rates the product”
 “user is warned not to buy product”
 “user inputs illness or allergies”
 “user starts the app”
Optional functionality:
 “user creates a shopping list/ product report”
 “user flags a product as harmful”
 “user uses the how to shop guide”
 “user compares three products”
CONCLUSION: Use cases will be separated into two groups: main and optional functionality.
ACTION: Everyone will think of other possible use cases and how to design them.
3
10. Name of the application
Although the name SafeShopper was good for our application we were certain that there is a better
name somewhere out there. Therefore, everyone tried to come up with possible names and some of them
are:
 FoodInspector
 Foody
 BuySafe
 PreShopper
 FoodWatch
 HealthAdvisor
Next thing to do was to vote for the new name. The voters decided that the new name of the application
is going to be BuySafe.
CONCLUSION: New name of the application is BuySafe.
ACTION: Ask Marin if we need to change all the documents to reflect the new name.
11. Application design
The last thing we discussed during the meeting was the design of the mobile application. It has to be
appealing to the users, intuitive and above anything else, user-friendly. Juraj also suggested that we
could create a mockup for our next presentation, so we can show the basic design. The idea is not to
spend too much time on the design at the moment, as there are more pressing concerns.
CONCLUSION: A good design is important for our application to be successful.
ACTION: Possibly create a mockup of the design for the next presentation.
12. Conclusion
At the end of the meeting we talked once more what has to be done for the next meeting that was
going to be held at Sunday 28.10.2012. We also discussed what is required for the next presentation so
that we could start preparing for that.
CONCLUSION: Next meeting will take place on Sunday 28.10.2012. at 20:00.
ACTION: Everyone will think about requirements, possible use cases and write part of the project plan that was assigned to
them.
4