The first model of software development is not really a model but, the model is used in small projects. That model is the code and fix model. In code and fix model there are no required documentation, no quality assurance, no formal requirements or formal testing and delivery is haphazard at best.
Do not even think about schedules and effort estimates when this model used. It tells take a minimal amount of time to understand the problem then start code. Run or compile your code and try it out. If it is not working, fix that first problem and try it again.
Continue this process of type compile – run – fix until program work what you want with no errors and then ship it. Every programmer know and understand this model. This model is work for quick, disposable tasks. For example, this model works better for proof – of – concept programs. No maintenance includes. The model works good for small and single – person programs.
Code fix model shown in figure:
However, it is very dangerous model for any other kind of program. With little in the way of testing, no real mention of management configuration, no architectural planning and probably little more than desk check of the program for code review. Code – fix model is good for dirty and quick prototypes and really nothing more.
Using this model small and short Software developed on user interface. That said, this is a terrific way to do dirty and quick prototypes and short, one – of programs. It is useful to show a quick version of a user interface design and to validate architectural decisions. Use this model to understand the larger problem you are working on.