Posts Tagged ‘paper’

First outcomes on DyCaPo

Thursday, October 15th, 2009

My first day at FBK has just finished, so there are some updates. I've uploaded about every document to the Wiki regarding my analysis of the papers. The Analysis Grid is available for view and as a PDF file. Chek them out at http://www.opensocialcapital.com/dynamic_carpooling/wiki/!
For the next week I'm going to review some existing mobile application. I will also contact some Opentrip members to ask them about the status of their work. I will contact the author of dynamicridesharing.org Wiki to ask him some information.

Wiki set up, first meeting

Wednesday, October 14th, 2009

Both the Wiki and the blog has been set up. Tomorrow I'm going to have the first official meeting at FBK to discuss my first results.
I've just finished the grid containing a short description that each paper proposed as a solution (or suggest) for the areas:

  • System Suggestions
  • Interface Design
  • Algorithms
  • Coordination
  • Trustiness
  • Safety/Reputation Systems
  • Social Aspects
  • Chicken-Eggs problem
  • Incentives

The WIKI is located at the following URL: http://www.opensocialcapital.com/dynamic_carpooling/wiki/
The Blog, which currently takes the RSS of the category carpooling-research of my blog, is located at: http://www.opensocialcapital.com/dynamic_carpooling/wiki/.
I will fill the Wiki as soon as I have the time to do it, I promise.

Papers analyzed, grid

Sunday, October 11th, 2009

I've just finished to analyze the 12 papers of my research activity. I'm going to prepare a grid to summary and underline the main aspects. These will surely contain proposed solutions about the barriers against dynamic car pooling, UI design, social aspects and capital, security issues. We also bought the domain, that will be revealed when the WIKI will be set up

First papers collected and analyzed

Thursday, October 8th, 2009

While I am waiting for my wiki to be setup, I'm updating here my first week of work. I read lots of papers regarding dynamic car pooling and friends. Most of them are listed on this MIT website and on dynamicridesharing.org. The second site is maintained by Dan Kirshner, the author of three (unlucky) experiments regarding dynamic car pooling.
I actually selected 13 publications for my scope. I'm going to publish the list as soon as I've got my wiki. What I'm going to do is to review them, comparing my work with the excellent one done by Hannes Zimmerman and Yann Stempfel (Current Trends in Dynamic Ridesharing, identification of Bottleneck Problems and Propositions of Solutions).

Internship: Dynamic Carpooling

Friday, October 2nd, 2009

I've just started an internship for my University. I'm working at the Fondazione Bruno Kessler, a research organization of the Autonomous Province of Trento that promotes research in the areas of science, technology, and humanities. In particular, I'm at the Center for Information Technology - Irst, in the SoNET explorative unit.
My research activity will last until the end of January and hopefully continue during the second semester, if the collaboration will be fruitful enough for a thesis.
The internship activities will focus on Dynamic Carpooling. I'm going to use my blog and the new category /carpooling-research to publish updates about the status of my research. We are going to purchase a domain that will also contain the outcomes of the research activities, available to the general public.
Here is a quick overview of the contents of my internship:

1. Dynamic Ridesharing Reviews

  • Review of existing papers
  • Review of existing web and mobile applications
  • Review of protocols
  • Research about the motivations of failure/success of existing realities

2. Release of Prototypes

  • API definition for Dynamic Carpooling
  • Implementation of a web application for Dynamic Carpooling
  • Implementation of a mobile application for Dynamic Carpooling
  • Possible integration with FBK systems

Introduction To Software Testing

Sunday, July 19th, 2009

Elements and Concepts - A brief overview


Download PDF version of the whole document. You can browse the article online but I encourage the download of the PDF since it is written with accuracy.


Introduction

This document contains some basic concepts and definitions about software testing. It has been written for studying a part of the Software Engineering Project course at my University. It is composed by a summary of the intersection of more than 10 different sources, all of which are cited. If you feel that some contents of this publication belong to your intellectual property and it is not cited, please contact the author who is willing to correct any mistake.

The first part of the paper focuses on the definition of the most important key aspects of software testing. Then some information about input partitioning are given. What follows is a research about code coverage and two useful and famous tools, Control-flow coverage and Data-flow analysis. A complete example on using those tools is then given. The second half of the document also contains the definition of the most important software testing practices.

The goal of this tiny document is to clarify key terms and therefore become a base start for the reader to go in deep with the interested topics. Another goal is to give a simple but clear example about data flow analysis, as I realized that not all the people understand the examples around the Net.

Software Testing

Software Testing is an empirical investigation conducted to provide stakeholders with information about the quality of the product or service under test, with respect to the context in which it is intended to operate. Software Testing also provides an objective, independent view of the software to allow the business to appreciate and understand the risks at implementation of the software. Test techniques include, but are not limited to, the process of executing a program or application with the intent of finding software bugs. It can also be stated as the process of validating and verifying that a software program/application/product meets the business and technical requirements that guided its design and development, so that it works as expected and can be implemented with the same characteristics. 1

(more...)