Software Development: Spiral Model

I am using the spiral software development system to develop prototypes at this later stage. The RAPID model had been used for individual prototype development, but now i can determine set objectives for a specific purpose and test and re-test following prototypes. I am now moving towards a fully functioning prototype, so requirements capture is required and will be determined following todays focus group with the partially functioning prototype.

Below: diagram of spiral waterfall model

http://en.wikipedia.org/wiki/Spiral_model

This model was developed in 1986 by Barry Boehm and utilises iterative development; a system where a series of prototypes are continuously developed, tested, and improved. 

I am currently at stage 1 of this model, where i has a partly-functioning prototype with a concept of requirements, and a concept of operation as well as a requirements plan; i hope to capture a context of use, more detailed requirements, develop the prototype and re-test . This is what i hope to gain from the focus group and user test. I also need to consider the development of instructions as well as proposed packaging.

Prototype development until now has been to develop understanding of the arduino/xbee environment, for proof of concept and interaction with users has been done through paper prototyping. I am now able to use the skills and understanding of the technology to quickly prototype and develop the system into a finished one. I have been using the RAPID model until now for prototyping, but now that a specific system is proposed, a more appropriate model will be utilised.