Ask a question from expert

Ask now

Sample Assignmemnt on Waterfall Model

5 Pages1509 Words203 Views
   

Added on  2021-06-14

Sample Assignmemnt on Waterfall Model

   Added on 2021-06-14

BookmarkShareRelated Documents
Task 1: Waterfall Model1.List the problems associated with waterfall modelWaterfall model is considered to be a very basic software development approach which was used over the decade. With the passage of time when development continue to increase on a very large-scale people use to find this model difficult to adopt for every project. Here are some problems which are associated with this model. I.Linear or sequential process:In water fall model processes are linear which mean they use to be performed in a sequence. And those all the process doesn’t allows to revisit any phase. There is no chance to repeat any phase during the project. Once a project is complete it will be evaluated after completion and if changes are required the whole model will be repeated from requirement phase to maintenance phase.II.Do not support requirement changes:As already explained that processes are linear thus if there is any change in requirement during any phase of the project this model doesn’t entertain those changes. As it is very difficult in large projects to define all clearly state all the requirements at once, there is always change in requirements which this model doesn’t supports.III.Every phase needs to complete previous phase:All the phases of this model need the previous phase to be completed to continue to move towards the next phase. Which means there is delay and
Sample Assignmemnt on Waterfall Model_1
wait time before and after every phase. Also, this is a big drawback as different teams were assigned different task designers to design the product, developers to code the programs so those teams may be wasting their time while waiting for a phase to complete by other teams.IV.Difficult to measure progress:In this model is it always difficult to measure progress. Every team is focused to complete their assigned work but there is difficulty to measure overall progress of the project which is one the big drawback of this model.V.Difficult to estimate risk and problems: Risk and problems ae very important to measure for any type of project whether it’s a small or big project. Unless there is iteration and feedback but it is really difficult to accommodate the imperfection of early stages in one of the later phases.2.Why do organizations continue to use the waterfall model?Where every model has some problems, they also have some good point or advantages so organization still prefer to choose this model. Many organizations are still using the waterfall model on and off for their projects. Following are some advantages which are supporting the waterfall model adaption for developing software.I.Easy to understand:This is sequential and hierarchal model thus easy to understand for people within the team and outside the team like clients. It provides a complete life cycle for controlling and organizing software development projects.II.Focus on goal:Every team whether they are part of development team or part of design team, every person has a common goal to complete this project. They share common goal and stay stick on one point to complete their work in assigned time frame.III.Coordination between teams:This development model allows departmentalization and managerial controls. They focus to coordinate with each team and provide a specific time frame to each of them tocomplete their work on time. In this model team’s coordination is easy when a design team finish their work and complete design phase, they handover all the material to development team to start coding the design.Task 2: Alternative ModelsExtreme Programming1.Who is primarily responsible for introducing the model and when was it introduced?Extreme programming was introduced in March 6, 1996 by Kent Beck.
Sample Assignmemnt on Waterfall Model_2

End of preview

Want to access all the pages? Upload your documents or become a member.

Related Documents
System Analysis: Feasibility Study and Lifecycle Models
|24
|4376
|346

Agile Methodologies and Agile Systems Discussion 2022
|11
|2500
|8

Characteristics or Phases in Project Life Cycle
|9
|1232
|16

Project Management Methodologies
|9
|1681
|92

System Analysis and Design
|13
|1658
|447

Project Management Methodologies: Types, Advantages and Disadvantages
|5
|1128
|327