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.