Blog Reflections #18

   Tonight my team went over the topics everyone is going to talk about during the presentation:

      Chris: Introduction
      Albert: Failed open source projects
      Me: Deliverable 2, major issues with deliverables
      Hannah: Toy project
      Matt: Fault injections

     We decided to have our presentation cover mostly our experience, since our document went very in depth on our testing framework I liked this layout because it gave everyone a chance to speak. I enjoyed working with this group during the semester. Everyone put forth an effort and tried to help towards the finished project. I learned many things during the course of this project. I hope I get put in as good of a group next semester in 462.

Blog Reflections #17: Almost done...

The semester is almost over, and we are in the final stretch of our project. I started the powerpoint for our presentation and will finish it tonight. We are mostly going to talk about our experience with completely our project. Albert and Chris will be finishing the final touches on the poster, and Hannah will be adding the faults to our script and writing about it in our document. I learned alot during the course of this project. I hope our presentation goes well!

Blog Reflections #16: Deliverable #4, Testing, Website(side work)

 I accidentally made two #9's so I will just skip 15 to get on track. We have been working on changing our write up for the fourth deliverable. This experience has been pretty smooth for the most part. We added more test cases to our project without many issues. This is mainly because we have worked specifically to make our script as flexible as possible. This is why it was rather easy to add testcases or different methods.

  I am starting to think about some faults we can add in our testcases or methods to get some failures. Right now, I do not think we are getting any failures with our current methods. From what we have been learning in 362, I know that this is not a good thing. If we do not find a way to get a failure, it will be hard for us to know of our script can even handle such a case. This will be our next task after we receive feedback and make changes to chapter 4 of our write up. 

  In other news, I have finished making the website for Women in Computing and it went live on Tuesday. I am very excited that everyone gets to see my work. I hope this actually draws interest in the club. 

Link to site: wic.clubs.cofc.edu 

Blog Reflections #14: Side Work

    I always like to work on coding outside of class. Recently, I have been doing many freelance website project under the guidance of Christine Moore. I have made a site for two non-profit organizations, the women in computing club here at the college, and a small start up in Charleston. I am learning alot doing this. I would like to learn way more though. I checked out books from the library on Javascript and PHP. I want to learn these languages to make my websites more interactive. I am using what I learned on the project for this course as well.
   Another aspect of computers I would like to branch out to is developing apps. I have an idea on a particular app that I would need in my daily life. When developing apps, I heard it was a good idea to develop one that you personally would like to use. I do not have a car, so sometimes I depend on local transportation to get where I'm going. I have to wait a long time for the bus when it is late. I would like to make an app that tells bus riders how far away their bus is. I've seen this system already on Washington D.C.'s Metro. However, their system was by the tracks. It was not on the rider's handheld. CARTA also had this system online. But yet again it was not available on a phone where it would be the most convenient.The system would involve sensors on each bus. The system would then calculate how far the bus is from the person's location. This would all be shown on a map on Charleston.

Blog Reflections #13: Hover, banner, final!

    After a few tries, Hannah and I got a hover to work in our html report that contains the requirement being tested for a specified testcase. I thought this was a cool way to show the requirements without taking up too much room on our table. Albert also created a banner for our poster. It is very fire-y!
   We also had a little problem with our framework. It was only taking float types for our max and min methods. Our next task will be expanding our testing framework to use more than just the max and min methods. I like this idea better. I feel like coming up with many test cases for one method will become redundant and pointless. In the max function for example: if we test two positive integers for a test case and then for the next test case we also test two positive integers there wouldn't really be a need for that.
    We will finish deliverable #4 this weekend. We have also planned on seeing Dr. Bowring early next week to see if we are on the right track with the changes we made in deliverable #3.
      I have also started studying for the final. I am starting by reading through all the chapters we have gone over in class. I hope I do well! :)

Blog Reflections #12: More Deliverable #3 Feedback

    We got the feedback on our write up for deliverable #3 to be more specific with what our script does exactly. Also, we needed to be more fluid and narrator like in our writing. When we looked at the project from the previous year, they listed what all the methods did in their script. We do not have methods in our script, but we are going to model ours after that write and write all what our script does.

     This weekend, we started to add those changes to our write up. We also started to add Method names and requirements to our table. I am trying to figure how to add a hover to the html/css code so we do not have to add an extra column for the requirements. This idea was suggested to us, and I liked it.

    We also found all the test cases we will be using for the whole project.

Blog Reflections #11: Deliverable #3 Feedback

   I feel like our presentation for deliverable #3 went well. Our script ran as planned. We have to make a few changes that I feel we already knew about coming into the presentation. We need to:

• Not hard code our methods into their specified drivers
• Add a method and id column to our html reports

  These are easy fixes. We will change these two things this weekend. Once we change this we still need to find 1 to 2 more methods to test. If we finish this, we will be way ahead of our schedule and can start working on our poster.