Comments for peer group’s pitch

Jobitti


This pitch was especially well rehearsed compared to the others, the two speakers also worked well together. the start of the pitch clearly established the problem and the overall style of the pitch seemed professional. They did not utilize the PowerPoint at all but that made little impact because the pitch was very clear and the aim of the project came across well. The teams resources and roles of its members was a nice addition. What the pitch lacked was a clear view of the exact look or feel of the game being delivered and as the pitch was a bit short at about two minutes there was time to include more.

Know Your Hoods


Know your hoods-teams pitch stood out from the rest with its relaxed style. With only one speaker the pitch had a good flow and the problem and solution as well as the resources were all made very clear. Their PowerPoint had a bit more text than necessary but as some of the slides were referenced during the pitch it wasn't a huge problem. The pitch was on the shorter side with just over one and half minutes of time used, so there could have been more additions to the actual solution part of the pitch, then again keeping the pitch short may have been a good choice as they were able to get there point across and it was very easy to concentrate the whole time.

Week 2 update: Start of the new year

As the break ended and the team was well rested we began work right where we left off. First we made some finishing touches to our pitch and the pitching team began to practice. Now that we have a clear picture of where the project is headed from the project owner as well as the information from Toyota the programming can finally begin. We divided the team into two groups one of witch will work on the front end and the other will develop the back end. The next week will be spent pitching and setting the first tasks for the programming groups.

Prototyping

A scetch of what the UI could look like, with some backend connections.

Ishikawa fishbone diagram

Idea tree

Mindmap

Group Task 5: Secondary Research

This group task was about researching both scientific journals and interesting (existing) applications/concepts based on our project and presenting them on our blog.



For the application/concept part of the task, the closest to the description of our project that could be found was a US patent for dynamic browser-based industrial automation interface system and method by David M. Callaghan (link to pdf https://patentimages.storage.googleapis.com/f3/5d/73/bb62080ae1554d/US7480709.pdf). Our project is to create a browser-based UI for internal logistics management system, so there might be similar ideas behind both.



For the article part the first one chosen is Single Page Application using AngularJS by Madhuri A. Jadhav, Balkrishna R. Sawant and Anushree Deshmukh (published in International Journal of Computer Science and Information Technologies in 2015). This article explains what a single page application is as well as what Angular is and how it can be used in this context. This is a quote from the abstract of the article: “The idea behind using AngularJS in web application is to make your web application modular and easy to maintain. AngularJS brings MVC (Model View Controller) capability to your application. After using minified and compressed files in your application, the size reduces to some KBs which will results in faster loading of pages.” We are especially interested in AngularJS because we will use it in our project.

The second article is A path following control of an unmanned autonomous forklift by Tua Agustinus Tamba, Bonghee Hong and Keum-Shik Hong (published in International Journal of Control, Automation and Systems in 2009) discusses different methods of forklift movement automation. This is a quote from the abstract of the article: “In this paper, the development of an unmanned autonomous forklift is discussed. A system configuration using vision, laser ranger finder, sonar, etc. for autonomous navigation is presented. The kinematics of a spin-turn mechanism is analyzed first, and then the obtained kinematics equations are transformed to the equations represented by path variables.” This article might help us understand how automated warehouse traffic might work in some cases. Might provide some insight on the topic, but most likely isn’t going to be used in any practical parts of the project.

The third article is A Metadata Approach for Building Web Application User Interface by Dimas Gilang Saputra and Fazat Nur Azizah (published by Elsevier in 2013). This is a quote from the abstract of the article: “Although it seems that there are millions of ways in building web application user interfaces, experienced web application developers are usually familiar with particular “patterns”. Nevertheless, user interfaces are often still developed from scratch, even if they are built based on existing applications. This makes web application user interface development a repetitive job. Furthermore, changes on the user interfaces often require a lot of work. This paper explores metadata as an approach to store the elements of user interfaces, so that the elements can be managed dynamically without having to go through the codes.” This might not be as relevant as the first article about AngularJS, but might be useful nonetheless.