The “Big-Bang” Software development lifecycle model
Since i have had a lot of free time these last days i have spent the time reading about all kinds of subjects and one of the subjects was the “Big-Bang” lifecycle model.
First of all lets start with a short explanation of what a software development lifecycle model is. Simply put it is the process used to create a software product from its initial conception to its public releases. There are many different methods that can be used for developing software, and no model is necessarily the best for a particular project. But there are four frequently used models:
- Big–Bang Model
- Waterfall Model
- Prototype Model
- Spiral Model
In my experience the either the waterfall model or some variation of it is the one most commonly used in development firms. But this post is about the Big-Bang model.
What is the Big-Bang model?
So how useful is it according to the lameguy?
- This is a very simple model
- Little or no planning required
- Easy to manage
- Very few resources required
- Gives flexibility to developers
- Is a good learning aid for new comers or students
- Very High risk and uncertainty.
- Not a good model for complex and object-oriented projects.
- Poor model for long and ongoing projects.
- Can turn out to be very expensive if requirements are misunderstood
After reading this post you hopefully have a basic understanding of the model, if you want a deeper understanding then you can read more about it at the following pages.
And also the following book:
Software Engineering, FIFTH EDITION, Roger S. Pressman, Ph.D.