RAD is the high speed version of waterfall model (short cycles). We understand the requirement needed in this application which is setting up a platform for online shopping. As we only have 12 weeks to set up this fully functional application, RAD is suitable for our group as one of the characteristic of RAD is system produced in short time.
Another reason we chose this model is because, we divide our jobs to mainly two teams, one for programming and another on designing. Programming will be doing coding part, setting up database while designing will follow up the appearance of our website, design logo etc. We have a leader to guide us through and make sure all the things are in control and on time. Documentation manager responsible for combining both their jobs and update it time to time. After all the functions are completed, we will then integrate it as a whole.
RAD model requires human resource and commitment, performance issue, not for high technical risk. We trust our own members on doing work and this application is a basic online shopping web application, therefore no high technical risk involved.
Other models are not suitable for us because like for spiral, it focuses on each iteration produces a more complete product whereas we need to make sure a job is done after one another; prototyping model-we don't wish to just let the customers to see a prototype instead of the real product.
In conclusion, software lifecycle model is chosen base on the type of product and how we are going to carry it out. The stages are almost the same for all the models: communication, planning, modeling, construction and deployment, just that how it is formed and also how the sequence of the model goes.
No comments:
Post a Comment