Advantages of RUP Software Development 1 This is a complete methodology in

Advantages of rup software development 1 this is a

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

Advantages of RUP Software Development 1. This is a complete methodology in itself with an emphasis on accurate documentation 2. It is proactively able to resolve the project risks associated with the client's evolving requirements requiring careful change request management 3. Less time is required for integration as the process of integration goes on throughout the software development life cycle . 4. The development time required is less due to reuse of components. 5. There is online training and tutorial available for this process. Disadvantages of RUP Software Development 1. The team members need to be expert in their field to develop software under this methodology. 2. The development process is too complex and disorganized. 3. On cutting edge projects which utilize new technology, the reuse of components will not be possible. Hence the time saving one could have made will be impossible to fulfill. 4. Integration throughout the process of software development , in theory sounds a good thing. But on particularly big projects with multiple development streams it will only add to the confusion and cause more issues during the stages of testing
Advantages of RAD Software Development 1. The time required to develop the software is drastically reduced due to a reduced requirement analysis business requirements documentation and software requirement specification) and planning stage. 2. All the software prototypes produced can be kept in a repository for future use. The reusability of the components also enhances the speediness of the process of software development . 3. It is much easier for a project manager to be accurate in estimating project costs which of course means that project cost controls are easier to implement and manage as well. 4. It is a big cost saver in terms of project budget as well as project time and cost due to reusability of the prototypes. 5. If a component is being picked for the repository, it is already tested and hence need not be tested again. This helps in saving time required for testing. 6. The project management requirements are collected in a dynamic manner. Every time there is a prototype ready, requirements are studied and matched. If there are any additional requirements, these are then included in the next prototype built. 7. There is a strong and continuous participation of the project sponsor who keeps giving feedback in the whole process. Hence the end user satisfaction level is higher when the end result is produced. 8. It promotes better documentation through written test cases. Disadvantages of RAD Software Development 1. This method may not be useful for large, unique or highly complex projects 2. This method cannot be a success if the team is not sufficiently motivated and nor is unable to work cohesively together.

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture