It is week 10 already! Time flies so fast that the end of the semester is closing in. Although our software is still in progress, its shape has been formed after 8 weeks of tireless working and now it can function smoothly as expected. This exciting journey has been proven a great learning opportunity for me: we have overcome communication barriers, learnt how to collaborate with each other, and gained amazing experiences of developing software. We need not only to keep improving and finalising our product, but also to prepare for the forthcoming software demo, which is also the final oral presentation of CS2101. However, perfection is not easy to pursue as we still encounter many challenges in the preparation process.
Firstly, although we have indeed gained some experiences in preparing presentation, the last OP, software demo, is somehow a bit different as opposed to the previous two ones because of some factors beyond our control. One of the things which can go wrong is that our software might not perform correctly when we are presenting. There are potential bugs and glitches in our programmes that can crash the whole system and prevent it from operating normally. The controller class, which parses users’ inputs, is possibly the weakest component in our system since it is exposed to all variations of inputs. In order to reduce the chance of unexpected behaviours, we have composed several scripts containing commands that might be taken as inputs. Before presenting, we should test these scripts carefully on the software to ensure that they will function correctly. Thereafter, our presentations will follow accordingly to these scripts so that we can manage them better. These preparatory works are also precious experiences for us to deal with risk in the future.
Secondly, one influential criterion to evaluate the outcomes of a demo session is how well its presentations are delivered. Software demo is a valuable opportunity to introduce one’s product and demonstrate its features and user-friendliness to the target audiences. Therefore, enthusiasm plays a crucial role to make a software demo successful. Only when the developers themselves truly love their software, they are able to pass their passion to the audiences. In contrast, software will certainly fail to convince the prospective users if its own developers lack interest. The presenter’s level of enthusiasm and the methods to convey information will determine how the audiences would respond. A presentation is likely considered successful when attention and satisfaction from the audiences can be observed. Although a long applause at the end may not confirm too much, a presenter has to be engaging until his or her last words.
In a nutshell, all preparatory work has brought great lessons to me. I am prepared to step into my future profession in which making live presentations and group collaboration are essential. I sincerely appreciate all experiences I have obtained from this module and all efforts we have put together into it. Let us wrap up our exciting journey by an excellent demo session. Eventually, not winning or losing but learning really matters.
Program running unexpectedly during software presentation can really be troublesome. I agree that we should do intense testing before the presentation. In addition, I think we should apply the concepts of solidifying code defense into our program. This way, we could reduce bugs in our code, and our program can accept all kinds of inputs and respond accordingly.
ReplyDeleteI agree that the software developer’s enthusiasm plays a big role in presenting a great software demo. It is only when you have great passion and confidence on your software that you could give an exciting talk on your software. Without it, how could you convince the audience on what your software can do if you yourself is not convinced?
It is true that we have gained many experiences out of the two modules, but I believe they are not enough, and we still have much to learn in our future career.
I agree that OP3 is quite different from the former two. This time we are going to demonstrate our own software. As you said, the most important thing is our enthusiasm. If ourselves do not like our software, how can we persuade others like it? But I think because we have put a lot of effort on it, there is no reason for us to dislike it.
ReplyDeleteI also learnt a lot during the process of making this software, not only programming skills but also the importance of teamwork. I enjoy working with you all and I really like to make software together with others, because everyone can come up with excellent ideas.
Yes, it’s our time to shine. I like this blog. Wish us all the best for our demo.
Just as what you said, how well the oral presentation is delivered matters a lot. No matter if the software is attractive to the audience or not, the demonstrators should present their enthusiasm and passion to influence the audience. A demonstrator who dislikes his or her own product definitely will not make the audience like the produce. However, enthusiasm and passion cannot guarantee the demonstrator a good result. What the demonstrator should also command are the skills of delivering a speech, such as maintaining a good speed of speaking and eye contacts with the audience. In my opinion, all the above are what we should obtain after this module. Although this module is coming to the end, I will continue learning to become a good speaker. Thanks to this module for the opportunity of learning a lot!
ReplyDelete