Design and Prototyping High Endurance Multi-Rotor

The topic of this thesis fo cus on the preliminary design and the p erformance analysis of a multirotor platform. A multirotor is an electrically p owered Vertical Take Off (VTOL) machine with more than two rotors that lift and control the platform. Multirotor are agile, compact and robust, making them ideally suited for b oth indo or and outdo or application especially to carry-on several sensors like electro optical multisp ectral sensor or gas sensor. The main disadvantage is the limited endurance due to heavy Li-Po batteries and high disk loading through the use of different small prop ellers. At the same time, the design of the multirotor do es not follow any engineering principle but it follow the ideas of amateurs’ builder. An adaptation of the classic airplane design theory for the preliminary design is implemented to fill the gap and detailed study of the endurance is p erformed to define the right way to make this kind of VTOL platforms.

The Scrum approach to software development

Agile methodologies have become the standard approach to software development. The most popular and used one is Scrum. Scrum is a very simple and flexible framework that respond to unpredictability in a really effective way. However, his implementation must be correct, and since Scrum tells you what to do but not how to do it, this is not trivial. In this thesis I will describe the Scrum Framework, how to implement it and a tool that can help to do this. The thesis is divided into three parts. The first part is called Scrum. Here I will introduce the framework itself, its key concepts and its components. In Scrum there are three components: roles, meetings and artifacts. Each of these is meant to accomplish a series of specific tasks. After describing the “what to do”, in the second part, Best Practices, I will focus on the “how to do it”. For example, how to decide which items should be included in the next sprint, how to estimate tasks, and how should the team workspace be. Finally, in the third part called Tools, I will introduce Visual Studio Online, a cloud service from Microsoft that offers Git and TFVC repositories and the opportunity to manage projects with Scrum. == Versione italiana: I metodi Agile sono diventati l’approccio standard per lo sviluppo di software. Il più famoso ed utilizzato è Scrum. Scrum è un framework molto semplice e flessibile che risponde ai cambiamenti in una maniera molto efficace. La sua implementazione deve però essere corretta, e visto che Scrum ci dice cosa fare ma non come farlo, questo non risulta essere immediato. In questa tesi descriverò Scrum, come implementarlo ed uno strumento che ci può aiutare a farlo. La tesi è divisa in tre parti. La prima parte è chiamata Scrum. Qui introdurrò il framework, i suoi concetti base e le sue componenti. In Scrum ci sono tre componenti: i ruoli, i meeting e gli artifact. Ognuno di questi è studiato per svolgere una serie di compiti specifici. Dopo aver descritto il “cosa fare”, nella seconda parte, Best Practices, mi concentrerò sul “come farlo”. Ad esempio, come decidere quali oggetti includere nella prossima sprint, come stimare ogni task e come dovrebbe essere il luogo di lavoro del team. Infine, nella terza parte chiamata Tools, introdurrò Visual Studio Online, un servizio cloud della Microsoft che offre repository Git e TFVC e l’opportunità di gestire un progetto con Scrum.

Ubuntu phone - un sistema operativo convergente per desktop e cellulari

Ubuntu Touch è un nuovo sistema operativo per Desktop e Cellulari che nasce dalla necessità di unire sistemi eterogenei sotto un'unica piattaforma. L'infrastruttura di Touch, che garantisce convergenza fra dispositivi diversi, è basata sull'innovativo server grafico Mir e sull'interfaccia grafica Unity. L'Application Model è notevolmente migliorato, le applicazioni sono confinate attraverso AppArmor, e scambiano fra loro contenuti tramite il servizio Content-Hub. I tool di sviluppo supportati sono le tecnologie web (HTML5 e JavaScript) e C++ su Framework Qt (possibilità di utilizzare QML). Gli aggiornamenti di sistema, del core, sono sia parziali, attraverso archivi "delta" che introducono solo i cambiamenti necessari, sia full, sovrascrivono l'intero dispositivo. Lo sviluppo in Ubuntu SDK è veloce e agile. Notevole la gestione degli emulatori, ma pecca di alcune feature tutt'ora mancanti. Gli Scope sono application content indipendent, vera innovazione in Ubuntu. Per sperimentare questa tecnologia si sviluppa uno scope per la ricerca di libri nella Biblioteca Gian Paolo Dore della Facoltà di Ingegneria di Bologna.

Come le startup selezionano i software di project management?

Il presente lavoro di tesi punta a cercare di capire quali funzionalità, le startup del settore IT ritengono più utili all’interno dei software di project management. L’approccio per rispondere alla domanda sarà quello di intervistare startup presenti in diversi incubatori italiani ed elaborare i dati raccolti. Le aziende dovranno essere operanti nel settore informatico ed avere massimo 7 anni. Nel primo periodo di ricerca ho analizzato le funzionalità descritte nella letteratura scientifica e ho trovato che quanto presente non fosse compatibile con le attuali necessità e caratteristiche delle startup. Per avvalorare quanto affermo, sottoporrò un questionario alle startup compatibili con i requisiti, in cui valuterò se concordano o smentiscono ciò che dichiaro. L’intervista sarà rivolta ai project manager delle aziende, verrà loro sottoposto un questionario online in cui dovranno esprimere una preferenza tra 2 elenchi di funzionalità e indicare qual è maggiormente compatibile con le loro esigenze. In base alla scelta che effettueranno gli verrà domandato quali funzionalità tra quelle elencate ritengono più utili per i loro bisogni aziendali. Al termine della ricerca verranno elaborate le informazioni osservando se hanno trovato più utile il nuovo elenco di funzionalità e quali funzionalità sono considerate maggiormente necessarie a soddisfare le esigenze aziendali.

Dynamic Web Development with Seaside

Seaside is the open source framework of choice for developing sophisticated and dynamic web applications. Seaside uses the power of objects to master the web. With Seaside web applications is as simple as building desktop applications. Seaside lets you build highly dynamic and interactive web applications. Seaside supports agile development through interactive debugging and unit testing. Seaside is based on Smalltalk, a proven and robust language implemented by different vendors. Seaside is now available for all the major Smalltalk including Pharo, Squeak, GNU Smalltalk, Cincom Smalltalk, GemStone Smalltalk, and VA Smalltalk.

Io volcano observer (IVO) integrated approach to optimizing system design for radiation challenges

One of the major challenges for a mission to the Jovian system is the radiation tolerance of the spacecraft (S/C) and the payload. Moreover, being able to achieve science observations with high signal to noise ratios (SNR), while passing through the high flux radiation zones, requires additional ingenuity on the part of the instrument provider. Consequently, the radiation mitigation is closely intertwined with the payload, spacecraft and trajectory design, and requires a systems-level approach. This paper presents a design for the Io Volcano Observer (IVO), a Discovery mission concept that makes multiple close encounters with Io while orbiting Jupiter. The mission aims to answer key outstanding questions about Io, especially the nature of its intense active volcanism and the internal processes that drive it. The payload includes narrow-angle and wide-angle cameras (NAC and WAC), dual fluxgate magnetometers (FGM), a thermal mapper (ThM), dual ion and neutral mass spectrometers (INMS), and dual plasma ion analyzers (PIA). The radiation mitigation is implemented by drawing upon experiences from designs and studies for missions such as the Radiation Belt Storm Probes (RBSP) and Jupiter Europa Orbiter (JEO). At the core of the radiation mitigation is IVO's inclined and highly elliptical orbit, which leads to rapid passes through the most intense radiation near Io, minimizing the total ionizing dose (177 krads behind 100 mils of Aluminum with radiation design margin (RDM) of 2 after 7 encounters). The payload and the spacecraft are designed specifically to accommodate the fast flyby velocities (e.g. the spacecraft is radioisotope powered, remaining small and agile without any flexible appendages). The science instruments, which collect the majority of the high-priority data when close to Io and thus near the peak flux, also have to mitigate transient noise in their detectors. The cameras use a combination of shielding and CMOS detectors with extremely fast readout to mi- imize noise. INMS microchannel plate detectors and PIA channel electron multipliers require additional shielding. The FGM is not sensitive to noise induced by energetic particles and the ThM microbolometer detector is nearly insensitive. Detailed SNR calculations are presented. To facilitate targeting agility, all of the spacecraft components are shielded separately since this approach is more mass efficient than using a radiation vault. IVO uses proven radiation-hardened parts (rated at 100 krad behind equivalent shielding of 280 mils of Aluminum with RDM of 2) and is expected to have ample mass margin to increase shielding if needed.

JExample: Exploiting Dependencies Between Tests to Improve Defect Localization

To quickly localize defects, we want our attention to be focussed on relevant failing tests. We propose to improve defect localization by exploiting dependencies between tests, using a JUnit extension called JExample. In a case study, a monolithic white-box test suite for a complex algorithm is refactored into two traditional JUnit style tests and to JExample. Of the three refactorings, JExample reports five times fewer defect locations and slightly better performance (-8-12\%), while having similar maintenance characteristics. Compared to the original implementation, JExample greatly improves maintainability due the improved factorization following the accepted test quality guidelines. As such, JExample combines the benefits of test chains with test quality aspects of JUnit style testing.

Behindertenpolitik – Positionen der Parteien nach der 6. IV-Revision

Für Menschen mit Behinderungen und ihr Umfeld ist es entscheidend zu wissen, welche Parteien sie mit ihrer Arbeit im Parlament unterstützen. In den Fragen rund um Behinderungen zeigt sich unter der Bundeshauskuppel tendenziell ein Rechts-Links-Graben. Die Mitte-Parteien, insbesondere die CVP, scheinen diese Tatsache allerdings in Frage zu stellen.

Developing a point-of-care electronic medical record system for TB/HIV co-infected patients: experiences from Lighthouse Trust, Lilongwe, Malawi.

BACKGROUND Implementation of user-friendly, real-time, electronic medical records for patient management may lead to improved adherence to clinical guidelines and improved quality of patient care. We detail the systematic, iterative process that implementation partners, Lighthouse clinic and Baobab Health Trust, employed to develop and implement a point-of-care electronic medical records system in an integrated, public clinic in Malawi that serves HIV-infected and tuberculosis (TB) patients. METHODS Baobab Health Trust, the system developers, conducted a series of technical and clinical meetings with Lighthouse and Ministry of Health to determine specifications. Multiple pre-testing sessions assessed patient flow, question clarity, information sequencing, and verified compliance to national guidelines. Final components of the TB/HIV electronic medical records system include: patient demographics; anthropometric measurements; laboratory samples and results; HIV testing; WHO clinical staging; TB diagnosis; family planning; clinical review; and drug dispensing. RESULTS Our experience suggests that an electronic medical records system can improve patient management, enhance integration of TB/HIV services, and improve provider decision-making. However, despite sufficient funding and motivation, several challenges delayed system launch including: expansion of system components to include of HIV testing and counseling services; changes in the national antiretroviral treatment guidelines that required system revision; and low confidence to use the system among new healthcare workers. To ensure a more robust and agile system that met all stakeholder and user needs, our electronic medical records launch was delayed more than a year. Open communication with stakeholders, careful consideration of ongoing provider input, and a well-functioning, backup, paper-based TB registry helped ensure successful implementation and sustainability of the system. Additional, on-site, technical support provided reassurance and swift problem-solving during the extended launch period. CONCLUSION Even when system users are closely involved in the design and development of an electronic medical record system, it is critical to allow sufficient time for software development, solicitation of detailed feedback from both users and stakeholders, and iterative system revisions to successfully transition from paper to point-of-care electronic medical records. For those in low-resource settings, electronic medical records for integrated care is a possible and positive innovation.

“Realidad o Utopía" : : ley de ordenamiento territorial

La lógica del mercado y al cambio de modelo de desarrollo en América Latina, en el intento de poder competir a nivel mundial, ha agudizado las disparidades y el deterioro ambiental. La presión que ejercen las grandes empresas y ciertos grupos con poder, el enquistamiento de una estructura administrativa que puja por mantener esquemas tradicionales ya perimidos y la falta de planificación impiden atender uno de los problemas claves que plantea la economía en el territorio, el de la concentración y los desequilibrios territoriales. Surge entonces el Ordenamiento Territorial como alternativa válida para atenuar estos procesos y dar respuesta a la sociedad. El caso que se presenta pone en el tapete muchos de estos temas que hoy preocupan y puede servir como experiencia transferible y aplicable a otras realidades que buscan consolidar un desarrollo local sustentable. El ante-proyecto de Ley de Ordenamiento Territorial y Usos del Suelo para la provincia de Mendoza, República Argentina, es un instrumento elaborado en el año 2006 por el sector académico-científico que desde una visión interdisciplinaria incorpora fundamentos técnicos y aportes de los actores sociales involucrados. La metodología aplicada permite consensuar por la sociedad en su conjunto los principios que sustentan la Ley, determinar la aplicación de ciertos instrumentos para efectivizar acciones en el territorio y definir una forma innovadora de hacer política, gestionar y planificar el uso del suelo. La propuesta considera al Ordenamiento Territorial como una política de Estado que debe propiciar condiciones de gobernabilidad. Sus principios y normas priorizan la equidad y el bienestar general por encima de los intereses particulares así como también el respeto de los valores y costumbres de la sociedad. Surge de un proceso participativo y sus principios y fines responden a los problemas actuales. Incorpora una serie de instrumentos debidamente jerarquizados conforme a las competencias jurisdiccionales y existencia de distintas escalas geográficas, como también, instrumentos jurídicos y prácticas administrativas innovadoras que permiten la resolución de conflictos territoriales. Identifica además recursos financieros para implementarla y prioriza el fortalecimiento de los mecanismos de control para un funcionamiento más ágil y eficaz de la gestión pública. Sin embargo existen riesgos vinculados a la voluntad política y el poder económico que pueden impedir que esta utopía se transforme en realidad. Solo la participación social es la que puede lograr vencer los intereses en juego y conseguir la aprobación de la Ley. Si esto se consigue se habrá dado un paso muy importante a ser imitado, sin lugar a dudas, en otros lugares de Argentina y América Latina.