Date

9/3/2014

Original Meeting

9/8/2014

Priority Meeting

9/24/2014

First Meeting with

Customer

9/29/2014

Group Meeting

10/8/2014

Group Meeting

10/13/2014

IDE Download

10/17/2014

Status Meeting

10/20/2014

To Do

Who Attended

Add to original plan of what kind of features the app should contain.

Simpson, Shields,
Tepe

Priorities were set for which goals should be met first. Responsibilities were divied out for each
team member. Shields should begin to find where the blue towers are located. Drew Ford is to get
a list of the resturaunts on the outskirts of campus given the boundaries the group agreed on.
Shannon is to get a spreadsheet together for the buildings and websites. Each team member will
add to this once the spreadsheet has been created. John Tepe and Logan will find a digital copy of
the map of campus for us to begin to integrating it into out app. The name of the app was also
decided on as UK Ma-app. The IDE environment was also agreed on and everyone will be using
the same one.
1. The resources Nick mentioned. We need to learn more about how internet maps work and how
to use them. It sounds like there are many ways to do what we want to do, we just have to find a
good one. Nick has experience in mapping, so he could probably help us if we really need to.
2. We should adjust our requirements to follow an agile method instead of waterfall method. Right
now, we have a lot of things that we hope will work in 3 months. Instead we should arrange it so
that we are progressing from "working iteration" to "working iteration," as Agile describes it. For
example this could be something like:
Phase I: Have a working app with a slippy (I think is the technical term) map
and a user
interface.
Phase II: Add some needed features, such as clickable buildings that have relevant
information (hours, food, website, etc.).
Phase III+: Add more features based on how we prioritize them.
3. Prioritize our features. Nick suggested talking to a couple people on what they think is
important. Possibly give them something that doesn't work and ask them what they don't like
about it. The driving force behind app success is user experience, so we want to spend time
finding out what users want to experience.
The team has decided to use Eclipse to write the app in and utilize the Google Play Services. The
team has also decided that the code will be "shared" through GitHub since it is connected through
Eclipse. We will also begin to familiarize ourselves with the developing software, but Drew and
Logan will begin to formulate a potentially working map app and "report" back on Wednesday with
problems or stumbling blocks so that the team can begin splitting the work.

EStudio

10/27/2014

Midterm Presentation

10/29/2014

Design Meeting

Andrew Shields,
Logan Wells

Everyone

Andrew Shields,
Team met to show the code that has been put together that has a few code flaws. The team
Logan Wells,
debugged the program through the Eclipse IDE. Short term goals were set. Slippy map was
Shannon Simpson,
achieved. Working "ping" locator is the next on the agenda.
Andrew Ford
Each team member brought laptops and Android Studios as well as required packages were
downloaded so that the slippy map that has been already created on one machine can now be ran
Everyone
on everyone's.

Meeting with Prof to go over the status of the project.

met to create presentation and decide who is going to say what. Emulators were fixed.
Presentation Creation Group
Further goals were set. Icon decided on for the App.

10/23/2014

Everyone

Presentation practive with the EStudio

20 minutes to present your project to inform an audience of your peers about your
project
Meet with professor about design of project and ability to acheive set goals.

Everyone
Everyone
Everyone
Everyone
Everyone

11/6/2014

Testing Meeting

The team met to discuss testing strategies and to decide who would be the testers. The 2 team
members with android also tested the code that the team has put together since a new feature
was implemented that could not be tested on a laptop emulator. The test passed according to the
team members. The group is about ready to put it out for others to download.

11/17/2014

Testing Meeting

Meeting with prof to discuss testing strategies

Everyone
Everyone

11/24/2014

Code Review Meeting Meeting with prof to discuss the code that the team has compiled at this point.

Everyone

12/5/2014

the project to a small group of peers: 20 minutes to present your project and giv
Practice Presentation Team will present
(and demonstration if applicable) so the audience knows what it is

Everyone

12/1/2014

Project Documentation

12/12/2014

Final Presentation

Team will present the project to the class

Everyone