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: Agile and Ruby Lab
26 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.
We acknowledged today from Mr. Jens Trompeter, Board Member in Itemis company, that there's more in SCRUM than just that we learned from the Agile Lab and OOSC class: we had the opportunity to get real life, production-grade advices on how actually this technique (who is used to manage the projects) can help companies to finish projects in a timely and budget manner.
No method is perfect – GPS needs clear sky, aGPS improves this but still needs some satellites to be seen, GSM works like a charm if you have lots of antennas but falls dramatically if you’re in a remote place and WiFi positioning is good in cities, but absolutely lacks in remote zones. Only the composition of all can cover all the situations encountered in a normal life – crowded city when going to work and big, empty spaces when going to mountains to relax.
GPS is the oldest one from the frameworks available to the large audience. It isn't the first positioning system, but it is the one with the most success and longevity. It started as a military project in 1957. Because of the cold war, once the Russians sent to space the first man-made satellite, a team of scientists started monitoring its radio transmissions. The crucial discovery was that, because of the Doppler Effect, the signal transmitted frequency increases as the satellite approached, and lowers as it continued moved away from them.
Scrum is one of Agile processes that use incremental framework for developing complex software and managing new products so it is considered more like a framework in which you can employ various processes.
The software as industry relies more on reusability and on site modifications. If a programmer finds a piece of code, of course respecting the intellectual property, can easily adapt it to his project. This approach is called adaptive, because these methods focus on adapting quickly to changing realities – no customer knows from the start exactly what he needs from the start.
This methodology and set of principles has the root in the Toyota company. After the Second World War, the Japan and its companies were almost ruined both physical and financial. To recover the economy, they had to rethink all the processes of production in order to maximize their efficiency.
Agile methods are a family of development processes, not a single approach to software development. It represents the ways of creating software in a lighter, faster, more people-centric way. The base of this is the Agile Manifesto, widely regarded as the canonical definition of agile development and accompanying agile principles.