[Robotics] Morse development: requirements analysis

Tim Vercruysse timosater at hotmail.com
Thu Sep 16 14:24:54 CEST 2010


Hi,

Prof H. Bruyninckx hired me to help develop the Blender for Robotics  
project and integrate it with the morse project.
When I looked at both projects it seemed that there was no clear plan  
of action, which I find to be a big flaw.

In order to facilitate the integration of work from different labs, it  
is necessary that we first agree on the big picture of this project.  
Where do we want to go?
How do we structure the code? How do we come up with consistent and  
"standardised" naming of files, directories, objects, robots, ...?

As a first step in this proces I made a requirements analysis of the  
project. This analysis tells on a high level what we require of the  
project on a both functional and non-functional level.

If everyone could share their thoughts on this message, including  
adding expectations, making concrete suggestions, etc., we could find  
a common ground to start building the rest of the project from.

Thanks,

Tim Vercruysse

p.s. The idea of requirements analysis comes from the Unified Software  
Development Process( or UP). A very common used structure to develop  
bigger software projects. The requirements analysis is the first stap  
in this process.
The UP is a big help in keeping software projects clear and telling  
the developers what the main goals are. If everyone agrees with this  
first step I will start with the next steps of this process.



More information about the Robotics mailing list