Week 12 - Final Progress!

On this week's progress, I contributed my team in the making of ladder diagram for our application. I draw several black dots in each rule which represent a blank space for a statement and a horizontal line to represent a rule. Moreover, I also implemented a feature, in which the icon can be changed to logical AND with NOT by simply touch it once by the user when the icon had been placed into a rule. I also did not forgot to implements the logical OR for statements. Therefore, the user can make a logical OR by simply touching the black dot next to the statements substitute, and touch the black dot on the top of it.

Week 11 - Working on PLC in Android Application

After my team had brainstorming on how we used PLC's ladder diagram into our application, we decided to make it inside a canvas. To start off, we tried to make a simple logical AND which can be improved by implementing logical AND with NOT, and OR later on. Therefore, every condition-action will be represented as one rule in a horizontal line as seen as below:

Week 10 - PLC (Programmable Logic Controller)

On this week, my team finally decided to meet with our client to show our progress. We also would like to tell him that we had icon's swapping bug which cannot be resolved. After we gave him all of our progress and information about the project, he told us to learn about PLC (Programmable Logic Controller) to be used as our application's concept.

I had a research for this new concept for our application and I still find it quite related to our project. In PLC, there is a ladder diagram which consists of logical AND, AND with NOT, and OR. These logical statements were similar with what our client want previously. Therefore, my group members started to think on how to use this ladder diagram to our application.

Week 9 - Unsolved Icon's Swapping Bug

Two weeks had passed, but my team still cannot fix the bug existed in our application. On this week, I tried to find any solution from the internet. However, I did not even find anything useful which at least reduce the impact of this bug. Since it took quite a long time to fix this bug, my team decided to ask about this error to Stack Overflow. Still, there is no clear solution to get rid from this bug until now.

Week 8 - Icon's Swapping Bug! (and Cycle Report 3)

On this week's project progress, my team member named Chandra had modified the application of our project as his contribution on our team. He told us that he had successfully implemented swapping feature to swap icons in a panel. However, he encountered a bug, in which the icon often disappeared when it is swapped to another icon. Since this became a major problem for our project, all of our team members were looking for a solution. Unfortunately, we did not even find any clue to fix this issue!

Although we had this kind of bug in our project, we still have to make the next cycle report to be submitted on the Friday of this week. In this part, I listed all information about delete feature which had been created on the previous week in this document. Finally, we successfully delivered the report before the deadline which was announced on the midnight of this week's Friday.

Week 7 - Delete Feature and GridView Layout

After we had successfully integrate the icons to the application as statements for condition panel and action panel, my team told me to work on delete feature to remove an icon when it had been placed on either condition panel or action panel. During this discussion, we decided to make the delete feature looks similar like Facebook Version 6.0 for iPhone. Therefore, the icon can be removed by dragging it to the delete area at the bottom of the screen.

From this idea, my team member, Hendry, helped me in making this feature by giving me Nicolas Desjardins's Project from the internet that is really useful for me. I took some knowledge from his project and ended up in having a small gray rectangle at the bottom of the screen with trash icon and "Delete" text in it with a little transparency which basically looks like this:

When I had completed this feature, I realized that our project's condition panel and action panel are using Linear Layout which only enables multiple statements in one row. Therefore, I changed their layouts into Grid-View Layout.

Week 6 - Statement's Icon

For this week's project progress, I had finally completed the icons which are used to represent statements in condition and action. Therefore, I told Hendry, one of my team member, about the completion of the images since he was working on the project's application. However. he told me that the application needs various sizes for each image in order to prevent bad graphics on several Android devices.

The size of the icon is called density by the application. Thus, I had to make at least 3 different densities for each image. Soon after, I made various sizes for each image such as 16x16 pixels for mdpi(medium-density screen) devices, and 24x24 pixels for hdpi(high-density screen) devices. After I gave my images to Hendry's application, we can finally put these icons to the application which can also be dragged to the condition and rule panel as seen as below:

Week 5 - Statement's Image and Presentation

Several days ago from this week's class, my team had a meeting to discuss about our presentation. As a result, we proceed to divide this assignment to 3 tasks which are given to each member. For my contribution, I added several images and animations in every slides to make it attractive for the audience. Satisfactorily, we finished this presentation slides and had a good reaction from our lecturer and audiences on what we had done at the time we did the presentation.

On Friday, we also did a meeting as usual to continue the project's progress. In this session, I did the design of icons which are used to be statements in condition and action. However, the icons were not completed yet due to difficulty in finding and making the image of the statement. Below is the screenshot of the icons created on this week:

Week 4 - New Requirement(?) and Cycle Report 2

On this week's class, we were instructed to make the next cycle report for our project. On the same day, we submitted the required cycle report with the help of low-fidelity prototype which had been done on the previous week.

On Friday's meeting with my group members, we went to research lab to approach our client, Dr. Insu Song, to discuss about the project. From this occasion, he told us to change the concept of creating the custom behavior. Rather than choosing statement in the condition panel and rule panel, he requested to make them as icons, in which these items can be dragged.

Week 3 - Low-fidelity Prototype

Although we had made a sketch for my team's visualization to make the application GUI, we did not received a positive feedback from our client on this Friday. Therefore, we updated the sketch many times as we took client's request on the application GUI and its contents. Finally, we ended up on a sketch which looks like this:

Afterwards, we tried to make a low-fidelity prototype from this sketch as one of our resources for power-point presentation and cycle report. However, Chandra and I only could help a little in the making of this prototype due to hardware failures (laptop break-down). As a result, our low-fidelity prototype can be seen as below:

Week 2 - Issue-tracking System

On this week's class, my team were instructed to find a free and good freeware-system from Wikipedia's Comparison of issue-tracking systems to track our project's bugs. From this link provided by the lecturer, we agreed to chose JIRA software as our bug-tracker program. Afterwards, we were ordered to fill any current bugs from our project in an excel document given by the lecturer too.

On Friday, we met our client, Dr. Insu Song, to discuss about our project. As a result, he gave us two alternatives for the project's continuation. For the first option, he recommend us to make a GUI with condition-action based. Thus, the user can freely make a set of various conditions in order to execute an action. For the second option, he told us to make a scripting language inside android application. Therefore, the user can execute several commands with customized language created by our own. In a short time, we discussed about this matter, and we conclude to make the GUI for robot's conditions and actions. By having this agreement, Dr. Insu Song builds SVN Repository from his own URL at http://www.kopo.com/ as our project's version control.

After this discussion, we decided to make a sketch of our GUI application. As a result, we made 3 different kind of sketches created by every team member for each sketch. Next, we approached some of our friends to get feedback in terms of user-friendly.

From this survey, we conclude to use Hendry's sketch as our project's application design. Since there were several positive reviews on some features from my sketch and Chandra's sketch, we used them as improvement for Hendry's features.

Week 1 - Project Continuation and Cycle Report 1

On this week's class, my team had to create a cycle report about the current status of our project. In this task, I contributed some information about the requirements of our project. Although there were little arguments between group members, we had finished the cycle report. However, we were quite late in submitting this assignment because we accidentally forgot the task's deadline.