Tuesday, April 24th
Engineering Showcase: 12:00-3:30
Final Presentation: 6:30-7:00
Monday, April 23rd 3:00-4:30
Derek, Vyyom, and Kumar met up to finish up the APEX test cases to hit the required 75% mark. We also picked up the poster and talked about who would be present at what times for the showcase. We also went over the final project presentation slides and made a few changes to them as well.
Friday, April 20th 3:00-4:15
The project members met up to have a voice conference with our project sponsor so we could iron out any last minute things with the project. We discussed what we would have to do to hand off the project to the sponsor. It turns out we won’t have to do anything because she will be able to take back control of the Salesforce Sandbox.
Thursday, April 19th 5:30-5:50
The team met up to talk about and edit the poster that we will have for the engineering showcase. We made a couple changes to the poster and we each checked it over for any mistakes. We also discussed some more APEX test cases and how to implement them.
Tuesday, April 17th 5:30-6:15
The team did not present have the normal weekly updates so we met together for a while to discuss APEX test cases. We are currently at 35% test coverage and we need minimum of 75% before we can bring the code into production. This is a Salesforce requirement.
Thursday, April 12th 5:30-6:00
The team met just briefly to again discuss what we had left to meet the requirements set by our sponsor.
Tuesday, April 10th 5:30-7:25
Weekly presentation on the project. We included a demo showing emails sent to Salesforce creating a case automatically.
Thursday, April 5th 5:30-6
The project members discussed what we need to focus on, namely, APEX Class test cases.
Tuesday, April 3rd 5:30-7:05
The group presented to the class on what portions of the project have changed in the last week.
Thursday, March 29th 5:30-7:25
The group met up to work on catching Kumar up with the current state of the project. We were able to find a good balance of work flow between all members of the group and we’re looking forward to having a successful project at the end of the semester.
Tuesday, March 27th 5:30-7:35
The group presented to the class on the progress and problems that we have ran into since the Midterm Presentations.
Thursday, March 22nd 5:30-7:45
Again, instead of normally presenting with the weekly update the group focused on accomplishing several things such as:
- Expanding implementation of the APEX EmailParser Class to handle the Lyric Leak Detector
- Bug fixing with the Alexa Voice Integration with Salesforce
Tuesday, March 20th 5:30-7:15
Instead of normally presenting with the weekly update the group focused on accomplishing several things such as:
- Further implementation of the APEX EmailParser Class
- Beginning to write test cases to debug the email parsing process
Thursday, March 15th
Spring Break- The group was able to get very few minor things accomplished.
Tuesday, March 13th
Spring Break- The group was able to get very few minor things accomplished.
Thursday, March 8th 5:30-7:30
The other groups presented their midterm presentations.
Tuesday, March 6th 6:00-6:30
Derek, Vyyom, and Jesse presented the current state of the project in the Midterm Presentations to our Sponsor and the class.
Thursday, March 1st 5:30-7:30
Derek, Vyyom, and Jesse met up to discuss what needs to happen before the midterm presentations for the following week. Derek was able to figure out how to get the custom code, (APEX) to parse an email correctly and to automatically create a case with some of the material figured out. Jesse showed off some of the details on the Alexa integration and explained how it could work for the demo.
Tuesday, February 27th 5:30-7:30
Derek, Vyyom, and Jesse presented our weekly meeting to the rest of the class to update them on the recent success and failures in the past week.
Thursday, February 22nd 5:30-7:05
Derek, Vyyom, and Kumar met up to discuss what each of us was working on and to decide who was working on specific tasks on the Trello Board. Once that was settled, Derek and Vyyom explored around in Salesforce more and discovered that we will have to abandon our attempt at using the “Email-to-Case” system in Salesforce and instead implement the “Email Services” system that will allow us to write custom APEX code to customize our case creation. This is finally what we are looking for in Salesforce and it will allow us to complete the main success criteria.
Information regarding Email-to-Case vs Email Services
To use the Email Services software within Salesforce we will have to create our own APEX Classes that will define what will happen when an email is sent to a specific and custom address that is within Salesforce. This will enable the team to change the various parameters for the automatic case creation and allow the information to be organized in a manageable way.
Tuesday, February 20th 5:30-7:30
The group presented their weekly presentations on the success of the project so far and what our sprints look like and consist of. We made some adjustments to prioritize the Arlo device over the others at the moment but once we get one device working we’re confident that it will be easy to roll out on the other devices as well.
Thursday, February 15th 5:30-7:30
The entire group got up to pace with the project. We assigned more material for each project member to work on. For the next presentation we documented all of the material that needs to be on the slides and starting finishing some of it.
Tuesday, February 13th 5:30-7:30
Derek and Jesse presented to the class on what we had accomplished in the previous week and what we plan on accomplishing before the next meeting. We also discussed:
- “What does success look like?”
- “How do I know I’ve completed the project?”
- “How do I know I’ve done a great job?”
- “How will all this be measured?”
From there we also presented to the class on what the scope of the project was in order to make it clearer to the audience on what this project will accomplish. We also fielded various questions on how the team is able to mitigate the risks and problems that we have ran into.
Monday, February 12th
Derek sent our project presentations to our project sponsor to look over. We then received detailed feedback on different parts of the project. We are able to narrow down the scope of the project more so and we are also able to define what makes the project a success at the end of this semester.
Friday, February 9th
Contacted our Project Sponsor and received some very helpful information regarding the use of Salesforce. Of the three documents, the one includes over 3,000 pages of documentation of APEX within Salesforce.
Thursday, February 8th 5:30-7:30
Derek, Vyyom, and Jesse met in the computer lab to work on Salesforce integration with Arlo. Also discussed what we needed to do to be on par with the rest of the groups after everyone presented with their projects earlier in the week. We discovered some more information about creating custom objects within Salesforce and also explored their built in Schema tool.
We also split up the hardware devices among one another. Derek kept the Honeywell Humidity/Leak Detector, Vyyom received the Arlo cameras, and Jesse received the Amazon Echo Dot and the Amazon Echo Buttons.
Tuesday, February 6th 5:30-7:45
The group presented our project to the rest of the students in the capstone course. We also listened, asked questions, and answered questions about the projects in the course. This allows all of us to come together as a group and spread the wealth of knowledge between one another to help move the projects forward.
Monday, February 5th 6:30 – 7:45
The group met up to discuss and review the presentation for the following day. We split up different portions of the slides and talked in detail about each slide and how it directly relates to the project. We also added several other slides as we seen fit to further describe to our peers on what the project will accomplish and how it will accomplish these tasks.
Thursday, February 1st 5:30 – 7:30
The group did a mock presentation in class and the group was able to get feedback from our fellow peers. The group could also see what other groups were doing with regards to their presentations and all adjusted ours closer to the requirements.
Tuesday, January 30th 5:30 – 6:55
The entire group meet in the classroom to talk about the upcoming presentation on the 6th. We discussed what we wanted to have accomplished before then. A few examples of this was finding out how we could connect all of these new devices together. We researched how the Honeywell device was able to communicate with Saleforce and we set a plan to research the Amazon devices later the next week.
Monday, January 29th 12:15 – 12:20
Derek stopped by their office in downtown Columbus to pick up some of the new hardware that we’ll be working with.
Friday, January 26th 3:30 – 4:15
All of the group members got together on campus to video chat our sponsor to further refine the scope of the project. We were able to get some sample documents of what the expected outcome would look like. This is immensely helpful as we go forward trying to replicate the process automatically. The group also accepted the challenge to incorporate additional products into the scope of the project. This includes the Amazon Echo, the Echo Buttons, and the Honeywell Humidity/Leak Detector.
Tuesday, January 23rd 5:30 – 7:30
The entire group was able to meet together in order to discuss what we had each discovered that weekend. We discussed what we had learned about Salesforce so far and how we would incorporate AGILE and SCRUM software development practices into the evolution of the project. We again divided up some of the work that we wanted to have done before our next meeting with Rebecca Thomas. Jesse also constructed a Trello board to keep the team organized as we moved forward.
Friday, January 19th 3:00 – 4:15
First meeting in person with Becky Thomas to begin discussion on the Capstone project. The entire group was in attendance and each one of us personally introduce ourselves to the Sponsor. We were able to discuss what the scope of the project was going to be as we brought the project forward. We also bounced some ideas off one another on what we thought this project could evolve into as we incorporated different devices in the Salesforce platform. Additionally, several of us had some personal stories that we were able to share to show a purpose behind doing a project of this sort. We were also able to receive some hardware from her that we are able to experiment with. The first device we were able to get was a wireless security camera build by Netgear and branded as Arlo that has motion detection abilities. Going forward we decided that we were going to try and get in contact with one another on Friday afternoons so we would have the weekends to work on anything that would pop up. Each of us picked a certain topic that we had just discovered and then researched it a bit over the weekend to find out how challenging it would be to pursue that route.
Monday, January 15th
Heard back from Rebecca Thomas and scheduled a meeting this coming Friday at the Ohio Union on campus.
Friday, January 12th
Reached out and made our first contact with Rebecca Thomas over email to set up an in person meeting.