Question:

Software Prototyping is a very popular model of developing software. In this model, working small scale replicas (or prototypes) of parts of end product software. This usually in the form of screens which are developed and linked quickly through a small programming language like javascript. Sometimes the programming language is not used at all and the screens are presented and linked using other hardcoded means. A sequence of screens and buttons is used to rapidly show the user how a module of the developed software would look like and behave. Then customer feedback is taken and the prototype is developed further again and again. When the customer is satisfied, then the actual development of the module is started in the actual programming language and using the actual software tools (eg database management systems) appropriate for usage in at the industry level.

This popular model is usually not used in development of safety-critical or mission-critical systems and therefore there is usually no need to incorporate a formal system specification phase or activity in this model. However, you if a customer emphasizes that they need formal system specification incorported into the prototyping model for their project, then how will this incorporation be possible and practical?

What would be some difficulties that you would experience in this incorporation? Outline the reasons for these difficulties.

What would be some of the factors that would naturally support each other and make the incorporation of these two models easier? Again outline the reasons for these easily combined or favourable features.