Issues will arise which will pertain to the system architecture due to not all

Issues will arise which will pertain to the system

This preview shows page 2 - 4 out of 10 pages.

Issues will arise which will pertain to the system architecture due to not all the requirements will be gathered up front with entire life cycle of software. Rapid Application Development model is known as RAD model. This is same as type of the incremental model . In this function or the components will be developed in the parallel for the projects which are smaller. Time boxed development is used then delivered and then it will be assembled into the working prototype. This will provide something which customer can be seen and it can use and then provide its feedback based on requirements and delivery. Advantages of the RAD model: Development time will be reduced Component reusability increases Fast occurrence of initial reviews Customer feedback will be encouraged Many integration issues will be solved as integration will be from starting. Disadvantages of the RAD model: Needs tough team and depend on performances of individual System which will be modularized only that can be used Need highly skilled designers/developers
Image of page 2
Modeling skills dependency Not start with a full requirement specification is an iterative model . Whereas, development will start by just specifying and by implementing some part of the software, which will be reviewed so that we can identify further project requirements. Advantages of the Iterative model: We can build only the high-level design of the application before we start the actual build of product and will provide the solution of design to whole of the project. We will be creating and improving product step by step. In this we will get user feedback which is reliable. Time which is spent on documentation is less and more time is used for designing. Disadvantages of Iterative model: There is no overlaps but iterations are rigid Design or architecture issues are costly as all requirements will not be gathered up front. (Ray, 2005) Models of Software life cycle will illustrate phases of the software cycle and also the order where those phases will be executed. Every phase will create the deliverables which are required by the next phase in the life cycle. Below are following 6 phases in each of the model of the life cycle of Software development: 1. Analysis and Requirement gathering: Requirements of business will be gathered in the phase. Here main focus is on stack holders and project managers. Here we will create the document on re- quirement specification which will provide guidelines for another phase. 2. Design: software and system design will be prepared from specification of requirement which will be studied in the first phase. The system Design will help in specifying the system requirements and hardware and also it will helps in by defining the overall architecture of system. The specifica- tion for the system design serves as input for next phase of model.
Image of page 3
Image of page 4

You've reached the end of your free preview.

Want to read all 10 pages?

  • Summer '14
  • Systems Development Life Cycle, Iterative and incremental development

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture