The development team uses some Software development model to create the software. In layman terms, these software development models are set of rules that everybody in the team follows to get the things done.
Waterfall Model
There is a Waterfall model which is a traditional model and does not fit well in today’s fast- moving world.
In the Waterfall model, the following phases are followed in order:
· System and software requirements: captured in a product requirements document
· Analysis: resulting in models, schema, and business rules
· Design: resulting in the software architecture
· Coding: the development, proving, and integration of software
· Testing: the systematic discovery and debugging of defects
· Operations: the installation, migration, support, and maintenance of complete systems
Thus, the waterfall model maintains that one should move to a phase only when its preceding phase is reviewed and verified. This model is good for the Operations team as they get the whole software developed at once which they can deploy and maintain. New changes will also be less frequent and does not put so much burden on the Operations team. But this model does not scale well with the current fast-moving world. There are so many downfalls with this model and most of the Development is happening with Agile model now.
Agile Model
The agile model developed software in small iterations instead of developing entire software at once. Entire products feature list is divided into multiple lists of features. For example, if there are 50 features in software we can create 5 lists of 10 features each. Now developers will work on 10 features at a time, create and deliver those 10 features in the first iteration and continue with the rest of the features until you get the final product.
Every iteration involves cross functional teams working simultaneously on various areas like:
· Planning
· Requirements Analysis
· Design
· Coding
· Unit Testing and
· Acceptance Testing
Comments
Post a Comment