This section will present the Breiny application’s user interface and the available interactions with it, features which will be evaluated by the users. Following the requirements for extensibility, modularity and flexibility, the subsequent visible objects were separated into several user controls.
Category: Master thesis
25 posts
Be careful when copying information from this article! The paper is already published and you will be charged with plagiarism! My thesis proposes several approaches as result of the research questions. Their validity of each approach should be verified by allowing users to interact with a prototype built to fulfill all the proposed solutions. Hence, the final users will prove the correctness of this thesis approaches. The implemented prototype will be a brainstorming supporting application. Because my thesis studies brainstorming on a tabletop, I will choose the Microsoft Surface as the underlying hardware because it supports multitouch and multiuser experience. […]
is article presents the system architecture and the underlying decisions that were taken to achieve the above requirements. The system requires a repository for sessions, a repository for Brainstorming items and a native Windows application for achieving the baseline of desired features. Thus, a distributed client – server architecture is considered, exemplified here.
In this section the application requirements will be presented. They are split into functional and non-functional ones. The first refers to all the features needed to be implemented, while the second category refers to performance, extensibility and scalability of the system.
There are two sets of features that must or can be implemented: the first ones which regulate the brainstorming activity as a set of rules; the second ones add productivity to the process, enabling additional scenarios that improve the user experience.
My thesis claims as a basic concept that an ideal tabletop application supporting the brainstorming process must have an implemented answer to the issues raised above. Considering the first category of additional features which makes an application usable in the context of the brainstorming process, some properties were already mentioned and looked for in different applications: organization of ideas, relationships between ideas, sessions save and session restart for being continued.
Be careful when copying information from this article! The paper is already published and you will be charged with plagiarism! As we read before in the Introduction, collaboration is a recursive and iterative process with the purpose of solving a problem or a situation in a systematic way (Dictionary 2007). It implies two or more individuals or organizations involvement in a mutually interested common goal. This process is creative in nature and its results are dependent on knowledge sharing, on learning from each team member and on building consensus towards a commonly recognized solution. Because humans are essentially different, the tendency […]
Radu Poenaru's Master thesis - The natural gesture of touching employed by the new devices’ interface led to it becoming ubiquitous. The interface dissolved itself in the device that we are using, creating a more natural interaction.
The last milestone in my Master in Media Informatics is the master thesis. I quickly found a interesting topic: Improving the collaboration using a multitouch system (aka Microsoft Surface) using with C#, WCF, XAML
I am very close to finish another project in Fraunhofer FIT: IdeaPitch on the Microsoft Surface. This concept is very simple, you are able to “store” ideas in a repository, created using PHP and MySQL, and later on manipulate it on Microsoft Surface, along with the rest of the contributors. Other clients, iPhone and Air, were developed and are able to connect to the repository and register the ideas there. They are acting like individual clients, the iPhone can’t be used comfortable by more than one person. Not to mention that this is kind of personal device by its nature. The Surface […]
In order to understand the need of changing the screen orientation on a Microsoft Surface, you might want to think aboutthe situation in which you have casual visitors, who sit in pairs working on one Surface, you might considering rotating the window such that the ’Down’ of the application would be the nearest edge to them.
For sure at some point in your Microsoft Surface application you'll need to do programatically some screenshots. This article explains how to do it in two simple steps.