October 26, 2012 § Leave a comment
Well this is just a quick post before the final submission of the THICK I.C.E android application tomorrow in our tutorial. I am not exactly sure what I am going to put in this post but i am kind of making it up as i go. Through the majority of the semester working with this team, who happen to be some of my closest friends at uni i have definitely enjoyed myself. I like being able to rock up to class to a relaxed atmosphere with a great group of people and it really helps when you get along with everyone (including staff). At the beginning of the semester I only knew my close circle of friends within the class, we had even pre arranged for us all to take this class so we could stay together. However towards the end of the semester and now I have gotten to know the majority of my class mates and really enjoy my time in the tutes. I had my opinions of some of my class mates at the start of the semester from past experience (primarily in INB385) but this semester i really got to know them a little better. My opinions have honestly changed greatly, some people in the class who I thought I would never get along with I now find extremely interesting to be around. Although the work load has been a struggle and none of my other units have really given me any slack I still wouldn’t change a single thing about my last semester at QUT. I have enjoyed the ups and downs of the Advanced Multimedia unit and I really do believe that I will take something away from the unit. That something is more maturity and openness.
Thank you to everyone involved in the unit for the second semester in 2012, I have enjoyed your company and I hope to see some of you again.
October 25, 2012 § Leave a comment
Hey welcome back to my multimedia blog/little personal reflection, i hope my blog posts have been adequate so far. for my final blog submission before we actually present the final THICK ICE application infront of our multimedia class I would like to mention some things that we discussed in one of our final tutorials. In the weeks leading up to the final submission of our android application the app itself was progressing well, new components were being completed regularly (some late some early). We had a planned informal critique and Had some valuable feedback from both Jen and our fellow class mates that we all took on board. As much as everyone really hates seeing something they put time and effort into being deconstructed and picked apart I think it is a necessity. I am definitely no exception and some times I cant stand seeing work I have done or contributed to have negative reactions or feedback. But the whole idea of having our prototype completed for the informal critique tutorial was to have exactly this happen. The group collectively summed up the primary points where improvements could be made to the project at the end of the class. These were
– Improve the internal application navigation
– Develop the prototype for its presentation
– Add more content
These are summarised categories in which all of the feedback we received fall into.
Improve the internal application navigation
In its current state the application was by no means complete, however there were some aspects that we needed to address. One of the consistant problems we had was users not being able to navigate to and from (mainly back from) menus within the application. For users who were not familiar with the hardware we were using the demo on they found it difficult to make their way back through pages. This was an obvious gap in our design however i am torn between the decision to agree and disagree. I personally find it pointless having redundancy within any software, what many users did not realise is that the phone hardware was being used to navigate back through menus. I can however see how it is a problem as it conflicts with consistency when the user has to switch from using the application to then using the hardware as a form of navigation. Another feature that came under the internal navigation category was the application buttons themselves. After watching multiple users and even myself while demonstrating fat finger (overlap buttons and press the wrong one) the wrong button it was clear that we had some slight adjustments to make. After speaking with Jacob our project leader and one of our primary developers we decided on the implementing of an “auto fit” feature that will enable the application to perform consistently across multiple devices. This was our solution to the user feedback regarding some of the internal navigation issues. Personally I am happy with the results and really happy about the feedback we were receiving on the day. It put a smile on my face to see one group in particular being extremely impressed with how far we had come with an android application.
Prototype development for presentation
This was a category that had feedback and I had never even thought of which was great. Given that this is a prototype of what could be the final application 100% functionality is not expected. However we did see some students becoming confused as we had a lot of potential routes for them to follow but we had only planned the two primary scenarios. This raised the issue of developing the application for its prototype presentation. How we planned to solve the issue was to keep all of the content that we had added in the application but make it clear to the user on which routes were implemented. Making the available content stand out from the rest was the least time consuming and more viable method of designing for the presentation. It was frustrating to see some students using our application and when they could not activate a button they almost became disappointed with our work however this was an easy fix for the final presentation of our prototype. I am glad that we got this feedback as now it will make the prototype substantially easier to use during our demonstration and for marking purposes.
Adding more content
This category was probably the simplest, this feedback was mainly from Jen which is understandable as she wants us to have as much as we possibly can to showcase our efforts. Some of the content we had implemented for the prototype informal critique was purposely left not completed. Features like the expert system had only been partially completed because the group wanted to gauge exactly how well we were satisfying users needs. There was no point in having a system implemented 100% only to find that it was not correct and required hours of adjustments. This feedback was probably the most important for me as i took it in a way that meant, yes we are on the right track and all we need to do implement some changes to other aspects of the app and then continue on how we have been for the last few weeks.
I would like to thank both Jen and the class for helping us with the THICK ICE project and contributing their ideas and opinions that have helped us make a better product.
Thank you so much for reading
October 25, 2012 § Leave a comment
Hey guys welcome back to my blog again for some more multimedia goodness. Since i last spoke about my multimedia project on my blog we have come a considerable distance towards completion of the project. There are a few things I would like to mention in this blog post about the project that we have been working towards since my last post.
Firstly I would like to touch a little on expert systems and how they relate to our project. By definition an expert system within the field of artificial intelligence is a computer system that emulates the decision making of a human expert. Now if you remember just what our application is about then you will agree with me that the implementation of an expert system is critical. An expert system would be perfect for our application given that is essentially regurgitating the knowledge of an expert which we have obtained and verified. Upon some research we did find a system called Jboss which was an already implemented expert system. This system however did not really match what we were looking for because it involved the integration of an external java archive format which none of us had ever worked with before. Given that we were on a tight schedule for our project and the final due date was only weeks away we decided to push the idea of heavy programming loads away from the project as much as possible. I am by no means a programmer in any way so I couldn’t begin to fathom just how much was really involved in actually implementing other expert systems. At times I do wish I had more of a development role within the group with regards to the app itself, however our group composition and other constraints hardly allowed for it. It is rather difficult to organise a project and team and then it becomes irritating trying to baby some one through content they know nothing about. I decided I would stick more to my research and documentation role even though one of my aims from my last reflective portfolio was to become more attuned with the development aspects of this project.
It was decided that the implementation of the “expert” system was a job best suited to the development team. Jacob and Caitlin are far more adept android SDK users than Nicole, Ben and I, it would only delay the project if the three of us attempted to implement it. I am some what disappointed that I could not assist the development team as much as i would have liked without slowing the project down however the three members left found that researching, analysing and compiling the information for the scenarios was a task in itself. Nicole Ben and I were left with this task, that was to compile as much relevant information as we could find and make it easy to implement into the project for the final submission demonstration.
Over the course of the project so far I have found myself wondering that if I just had a little more experience in programming and scripting I might be of substantially more use to this group. I am more than happy to dedicate my time into research and documentation however I think if I were the type that took coding in my stride I would enjoy this project more as I would have a better feeling of satisfaction knowing I have had my finger in every piece of the metaphorical THICK ICE pie.
Thats all for this week, thank you for reading
September 27, 2012 § Leave a comment
Sorry for being late with my blog post once again, but hey at least i am consistent with being late and i guess that counts for something. I do apologize but this week over the break I celebrated my 21st birthday, however it is time to get back to reality. This week we are going to be talking about Wiki implementation in enterprise, im sure you can all remember how much i support the use of wikis so prepare. If anyone has ever used a wiki before they would know just how powerful it can be in more ways than one, take the best buy case study from a few weeks ago for example. Considering im going to be talking about wikis all through out this weeks post i will give you a quick run down. A wiki is essentially a tool that is used for mass collaboration and sharing the wisdom of crows/harnessing collective intelligence. Users who are allowed to by administration can create their own pages, add to existing pages and chat on discussion boards, a lot of us overlook how useful this can be for a business especially one with a substantial base of employees. The more users (trust worthy ones :P) you have the more knowledge you can share, that is a key ingredient in making a wiki a viable enterprise 2.0 strategy.
Connecting Employees via Wikis
This week in our groups for Enterprise 2.0 our task was to discuss a few different wiki implementation strategies for our case study on the Brisbane Airport. While in our discussion as a group I really wanted to push the idea of Brisbane Airport implementing a wiki to be used by employees. As i mentioned Wikis are a great tool that allows the aggregation of information/data, this can be extremely useful in the right scenario. I mentioned an example last week of an employee giving out incorrect information due to not being informed about flight changes and due to IT infrastructure malfunctions a message was delivered manually however it was too late. As i mentioned this entire scenario could have been avoided if a wiki that allowed the rapid sharing of knowledge across a broad range of employees had been implemented. So how would we implement this kind of employee based wiki into Brisbane Airport you say? well it is rather simple really. A wiki can be easily setup online by using a hosting service like Wiki Farm (i even linked the wiki for you) however it will be up to Brisbane Airport IT management to place administration rights and restrictions on the pages. I think this is a very viable strategy to implement in order to increase organisation effectiveness across the board at the Brisbane Airport. A wiki used by employees can contain a wealth of information, all of which is contributed by knowledgeable employees and other authorised contributors with the aim of sharing and then harnessing the collective intelligence of the entire airport employee base. The wiki can include information ranging from personal employee profile pages, employment sector private pages, management pages, important updates pages, company wide announcement pages and even a suggestions page that could be made anonymous. From what i have just mentioned you can probably already see the benefits of implementing a wiki like this into the internal structure and workings of the Brisbane Aiport. I hope that i demonstrated just how powerful a wiki can be to everyone who read this, thank you so much for reading.
Watson, J. 2012. Micro Blogging and Wikis in the Enterprises From INB 347 Lecture
September 22, 2012 § Leave a comment
Welcome back guys, im sure you get sick of me saying that every week but i do appreciate all who read my blog each week. Sorry again for the late post on last weeks content but im still dealing with far more things than i can handle at the moment. This week though I will be talking a little about airports and the implementation of social media in order to promote healthy business growth and efficiency. This week the main goal was for my group and I for our second assessment to discuss the finer points of Brisbane Airport and discuss social media implementation. Now Brisbane airport is essentially a business providing a product and in turn making a profit, some people definitely forget this. Brisbane airports goal is to provide a serve that transports goods and passengers all from a central location. It does all of this while providing its services with a level of quality in order to keep customers, thus making whoever requires the airport and its services its stake holders. stake holders are definitely not limited to business, corporate or private passengers but also the employees and other institutions or organisations that require airport serves. During our discussion within the group this week the general mindset when we talked about social media implementation was the utilization of tools like twitter and the like. However i on the other hand would like to mention something many overlook when we think about the adoption of social media.
Micro-Blogging & Wiki implementation
The topic i would like to touch briefly is the implementation of tools like Wiki’s into the workplace. As you might have noticed by reading a few of my other posts i feel Wiki’s are a very under rated tool and they should be implemented more. As we have seen in the Best-Buy case study from the weeks past they can really give a business an advantage and help them keep ahead of the competition. The amount of information that passes through an Airport on a daily basis is incredible, there are hundreds of flight time, thousands of passengers and a multitude of staff to manage. I honestly believe that with the implementation of a wiki the Brisbane airport could really streamline its information logistics processes. Imagine you are an employee at an airport and a customer asks which gate their flight will taxi to on arrival. Keep in mind that this customer might not have seen the other notifications that the airport displays about flight changes and there is a member of management on the way to your desk to inform you of a change to said customers flight. upon arrival the customer asks which gate they should be at and you to the best of your knowledge reply with what you think is the correct answer as you have received this data from your PC. after the customer leaves your manager arrives only to inform you that the computer is displaying the wrong information and as a result you have told a customer the wrong gate and they have missed a flight. You are now technically not responsible for this however this could have been avoided if only you had been up to date with current information. I think the utilization of Wiki’s could solve issues like this, which are the the issues created by lack of knowledge and communication. A wiki can be used to streamline information logistics within any organisation. Keeping every employee up to date can be done without a wiki however i believe that implementation of Wiki’s and other blogging tools into everyday work at the Brisbane airport can help increase organisational effectiveness and encourage a standard of employee engagement within this business.
Thank you so much for reading my Enterprise 2.0 strategy input for the Brisbane Airport for this week and once again i apologize for the extreme delay, I hope you understand.
Dreiling, A. 2012. Airportss – What’s Next From INB 347 Lecture
September 20, 2012 § Leave a comment
Well hello again for the second time today blog readers, i hope you are enjoying my blog for multimedia. Given that this post is in the same day as my last i believe it warrants some form of explanation. Well I usually leave my blog posts until a few days or so after the week that the post is meant to be detailing, however considering that assignment two is due tomorrow i thought it might be a good idea to get this blog post out of the way. Writing something tonight for my blog might help inspire me to add something further to my one page journal summery and contribution statement. What are these two tasks that are due tomorrow you might ask? well tomorrow is the final due date for
– The poster i have mentioned recently
– My contribution statement for said poster
– My reflective entry about these blog/journal posts
Now I have been keeping up to date with my blog entries most weeks, having them done a few days into the week after giving me some time to think about what i have done and perhaps what i could have done more of or better. This week I am getting this one out of the way a few days early, I think having something a little extra to talk about will help me conclude the final touches on my journal summery and contribution reflection. This week was mostly dedicated to finishing off the final touches on the poster for the THICK I.C.E android application. As you might remember from my post previous to this i mentioned that we had our poster completed a week early as we thought it was due last friday instead of this friday. I think this has helped me in a way because i have had a lot of other assessment due, including a 20 minute oral presentation based on the psychology of team diversity within a workplace environment. During this week I also dedicated time into revising the project plan one last time to make sure it was suitable for submission with the poster and reflection documentation. For the poster I think the feedback that was given last week regarding the section in the bottom left (who its for) was fair, there was too much white space and the images took up far too much room. When constructing this portion of the poster our goal was to demonstrate that the THICK I.C.E product would be suitable for a diverse range of consumers. The rest of the poster had very little negative/constructive feedback given, meaning we had less changes to make for tomorrow, which the group was very happy about. The rest of the poster i thought after the presentation could have less text and more visual aids implemented. We talked about this within our group and even mentioned it within the informal critique last friday. This is one change to the poster that we hope will make it more visually appealing and eye catching but also make it less of a task to read but instead more interesting to follow. This is one of the changes that is in my opinion critical to getting the highest grade possible as it is a visual aid/prototype for our product that in a real world scenario we would want to sell to our best ability.
Overall I think it has been a productive week for our multimedia group in general, the poster looks great and has some really solid content. Also the prototype of the actual android application is in the works although slightly behind I think we are making good progress considering this is our first attempt at actually coding a working application in the Android SDK. Things i could have done better this week personally would be communication with the group, I think everyone has been a little busier than they would like to be at the moment (including myself). I have sort of let it go and not worried a great deal about it however looking back i think we could have managed our communication better in order to make completing the poster and dividing up group work a little easier. As a personal goal I also want to contribute more towards the programming side of the project even though it isnt part of my duties within the group i am still interested in Android application development and it would take a little pressure of our two primary programmers. Other than the few things that i mentioned above i think we are going swimmingly with the project, I am happy with the poster and all thats left to do now if print out the final version of the project plan and touch up my one page reflection for tomorrow.
Thanks for reading