HW 21: Team Progress I

Team Progress

Team Lamp has come together quite well on the project. Each member has been upfront about deficiencies but also indicated a willingness to work toward completing each deliverable on time. I'm going to give a brief overview of our progress and some of the challenges we have faced thus far. 

The goal of our project was to find an open-source project and use that project to create a testing framework to test a small portion of the project. We chose Glucosio, an android project designed to help people manage their blood sugar levels. 

Building the Project

Our first real hurdle came shortly after this when we had quite a bit of trouble getting the project to build. It had been dormant for about four years and this point and it had no real documentation about installation or development. A contributing factor in this was the fact that no one on our team had experience with Android Studio or, I'm sad to admit, experience with building a project period. Because of this, it took us roughly 2 weeks to figure out that the Gradle version the project was using was 3 full iterations out of date and needed some minor tweaks to get it to function properly. 

After being able to build the project the team needed to identify methods within the project that we could test. Initially, this was a daunting task as the project is far larger than we were used to working with and because it is an android project, much of the project is built for user interaction and figuring out how to test this type of interaction was beyond the capabilities of our team at the time. We were able to find a suite of classes that were doing the calculations for the bulk of the project and decided these better suited our needs. 

Testing

Creating a test plan was the next phase of the project. Our original idea was to have a script that read a text file and sent the parameters to a java file that parsed through and 'decided' how to deal with the information being passed by the text file. After feedback, we created a 'smarter' script that parsed the text files and only passed the most basic information to the java file and used the output to compare with the expected output. This was faster and met the team project requirements.

Current To Do

We are currently working on polishing up the script and making the HTML output presentable. Additionally, preparing the presentation and final report will take up the bulk of the time remaining for the project. All in all, there have been struggles throughout the process but the team has come together and worked through them all the while learning to work with tools and languages outside our comfort zone.

Comments

Post a Comment

Popular posts from this blog

HW10: Chapter 5

Image
System Modeling 5.3. You have been asked to develop a system that will help with planning large-scale events and parties such as weddings, graduation celebrations, and birthday parties. Using an activity diagram, model the process context for such a system that shows the activities involved in planning a party ( booking a venue, organizing invitations, etc.) and the system elements that might be used at each stage. This diagram does not include food, drinks, decorations, chairs, equipment, DJ, photography, or the other myriad of things possible at a party. It simply goes through the process of determining the size, date, venue, guest list, and invitations.     5.5 Develop a sequence diagram showing the interactions involved when a student registers for a course in a university. Courses may have limited enrollment, so the registration process must include checks that places are available. Assume that the student accesses an electronic course catalog to find out about a...
Read more

HW11: Chapter 6

Image
This is my take on the conceptual and process views of 3 different machines. I found myself having difficulty distinguishing between the two in some instances. I seemed to want to go directly to the process view and skip the conceptual view altogether. I'd like to find some simple, real-world examples of conceptual and then process view diagrams of the same system to see the differences. 6.4: Draw diagrams showing a conceptual view and a process view of the architectures of the following systems: A ticket machine used by passengers at a railway station. A computer-controlled video conferencing system that allows video, audio, and computer data to be visible to several participants at the same time. A robot floor-cleaner that is intended to clean relatively clear spaces such as corridors. The cleaner must be able to sense walls and other obstructions. %3CmxGraphModel%3E%3Croot%3E%3CmxCell%20id%3D%220%22%2F%3E%3CmxCell%20id%3D%221%22%20parent%3D%220%22%2...
Read more

HW26:Chapter 24

24.6. Explain why program inspections are an effective technique for discovering errors in a program. what types of errors are unlikely to be discovered through inspections? Program inspections are essentially peer reviews of code that take place during development. Teams collaborate and walk through code line-by-line in search of bugs, exceptions, erroneous conditions, in house compliance issues, as well as things the team deems worthy to discuss. They are considered good practice because they bring together a diverse set of engineers to review the code and it can also help create a company culture that understands the importance of acknowledging errors and moving forward to improving. Sommerville states that during program inspections, there is broad use of checklists to help guide the process. These checklists are typically language-based and cover a wide range of common errors found in the past. This could lead to a reliance on such lists and overlook some more technical issue...
Read more