Waterfall Model: The Software Development Life Cycle Model

1042 Words3 Pages
bulb-icon

Recommended: Traditional software development life cycle

Introduction A software development process, also known as a software development life cycle (SDLC) can be explained as a structure, imposed on the development of a software product. The software development life cycle (SDLC) is an umbrella term for the overall process of developing, implementing, and retiring information systems through a multiple step process from initiation, training, documentation , design, analysis, maintenance, and consulting. Software development life cycle (SDLC) can be termed as a process of bringing ideas to reality in the creation of a software product with in the software industry. Types of Software Developing Life Cycles (SDLC)
1. Waterfall Model.
2. Prototype Model.
3. Spiral …show more content…

It is very simple to understand and use. In a waterfall model, each phase must be completed in its entirety before the next phase begin. At the end of each phase, review takes place to determine if the project is on the right path and whether or not to continue or discard the project. In this model the testing starts only after the development is complete. In waterfall model phases do not overlap.

Diagram of WATERFALL MODEL Figure1. 1
Advantages of WATERFALL MODEL
• This model is simple and easy to understand and use.
• A disciplined approach.
• Waterfall model works well for smaller projects where requirements are very well understood.
• Progress of software development is visible.
• In this model phases are processed and completed one at a time. Phases do not overlap.
Disadvantages of WATERFALL MODEL.
• Poor model for long and ongoing projects.
• Time consuming
• Not good model for complex and object oriented projects.
• Once an application is in testing stage, it is very difficult to go back and change something that was not well thought out in the concept stage.
• High amounts of risk and uncertainty.

When to use the WATERFALL MODEL
• This model is used only when the requirements are very well know, clear

Show More
Related

  • Agile Management: Enhancing Project Success

    766 Words  | 2 Pages

    Agile project management is an iterative approach to the planning and monitoring of project processes. Agile projects are conducted in smaller tranches called iterations with each of these iterations closely reviewed and critiqued by the project team (employees, representatives of the clients etc.). The knowledge gained from this process is then used to ascertain the next steps of the

    Read More

  • Pt1420 Unit 1 Question Paper

    483 Words  | 1 Pages

    4. Explain why change is inevitable in complex systems and give examples (apart from prototyping and incremental delivery) of software process activities that help predict changes and make the software being developed more resilient to change.

    Read More

  • Certification of Electronic Health Records

    1150 Words  | 3 Pages

    ...tion requirements. Similarly, the systems analysis, or define phase, is the deliverable which defines the system’s requirements. This includes taking the deficiencies in the existing system and addressing them with specific proposals for improvement. These proposals can be to ensure that the new EHR has all the necessary requirements to qualify for certification and help to narrow down vendor selection. Incorporated into the SDLC is a maintenance phase in which constant upkeep and evaluation is needed to ensure an operational system that is properly maintained, supported and secured. During this phase, system users should be kept up-to-date about the latest modifications and procedures. It is therefore important to know that your vendor has a good standing reputation and plans to provide continuous support for your software throughout the product’s lifecycle.

    Read More

  • Compare And Contrast Waterfall And Agile

    1825 Words  | 4 Pages

    In the waterfall method, the steps have to be finished iterative, meaning the next step cannot be started until the previous step is completed. Once the current step is completed, then the next step can be started and so on. The customer does not get a working build during any of the steps and cannot make any changes in the scope at all. Once all steps are completed, the end result is given to the customer and then they can deploy and hope it does what they are needing it to do. If any of the steps need to be changed, then the whole process will need to be restarted from the beginning and the process began again. In agile methods, the process is more flexible. This method is flexible and can allow changes after each iteration. The goal of each iteration is to provide a working build so that the customer can give feedback on it and changes can be made, if needed, so that all requirements are met, or if requirements have changed since the initial build of the

    Read More

  • Systems Development Life Cycle ( Sdlc )

    829 Words  | 2 Pages

    The Systems Development Life Cycle (SDLC) consists of phases used in developing a piece of software. It is the plan of how to develop and maintain software, and when necessary, replace that software. In 2007 during my hospital’s transition to a new software system, I was fortunate enough to be included in the process. I did not get involved until the implementation phase, but from then on, until now, I remain very active in the process. I decided to highlight the Waterfall Model of SDLC. The Waterfall Model is a “sequential development process” with each phase continuing in a line (McGonigle and Mastrian, 2012, p. 205).

    Read More

  • Three Criteria That Are Most Important In A Software System Case Study

    1058 Words  | 3 Pages

    A software development methodology is a standard proven process which helps programmers, architects, system analysts and others to make a well controlled and an efficient progress in the high quality software development.

    Read More

  • Work Breakdown Structure Case Study

    817 Words  | 2 Pages

    In this case study, the work breakdown structure is classified as a waterfall methodology where it is more rigid whereas eXtreme programming (XP) would be considered under the agile approach. The work breakdown structure (WBS) is a hierarchical structure that outlines tasks needed to deliver the product or service.

    Read More

  • The System Development Lyfe Cycle Phases

    1089 Words  | 3 Pages

    The system development life cycle, also know as the SDLC, is the process of designing and developing a system or software to meet certain requirements. (“System development life,”). This cycle involves many different phases, in which the system is planned, analyzed, designed, implemented, and tested. There are five major phases in the system development life cycle: systems planning, systems analysis, systems design, systems implementation, and systems security and support. Each of these phases has a particular responsibility and certain tasks are perfumed in each phase.

    Read More

  • Overview of Agile Methodology

    1555 Words  | 4 Pages

    Agile software development is a group of software development methods based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change.

    Read More

  • Specifications and Metrics Paper for Baderman Island

    1962 Words  | 4 Pages

    Introduction of the three programs being suggested will require an examination of the systems development life cycle. Haag, Cummings, and McCubbrey (pg 6-7, 2005) separate the life cycle into seven separate sections: planning, analysis, design, development, testing, implementation, and maintenance. The first piece of the systems development life cycle (SDLC), planning, requires the analysis of the projected idea's impact on the business. Haag, Cummings, and McCubbrey (pg 12, 2005) point out that the planning phase of the SDLC "focuses on either solving a problem or taking advantage of an opportunity." The next section of the SDLC is the analysis, which allows project managers to criticize the milestones established in the planning phase. In other words, the operations of each of the three projects must be judged on each project's accuracy, including the design, for long-term functionality.

    Read More

  • Rational Unified Process

    1248 Words  | 3 Pages

    Given the time, it takes to develop large sophisticated software systems it not possible to define the problem and build the solution in a single step. Requirements will often change throughout a projects development, due to architectural constraints, customer’s needs or a greater understanding of the original problem. Iteration allows greater understanding of a project through successive refinements and addresses a projects highest risk items at every stage of its lifecycle. Ideally each iteration ends up with an executable release – this helps reduce a projects risk profile, allows greater customer feedback and help developers stay focused.

    Read More

  • System Development Life Cycle

    962 Words  | 2 Pages

    Through a series of processes or steps as prescribed by the SDLC methodology, a firm can find the answers to a business situation and thereby improve operations and hopefully attain a competitive advantage. This paper will address the importance of the Systems Development Life Cycle Methodology to organizations. SDLC and Benefits The SDLC is a problem-solving process which, through a series of steps, helps produce a new computer information system. Each step from system planning, system analysis, system design, system implementation and system maintenance conducted in sequence should provide the answers to a problem or opportunity (Farah, 2006). An example may be a user who employs an order system may sense a problem with that system because customers may complain that orders are late or being lost.

    Read More

  • Software Process Improvement

    1784 Words  | 4 Pages

    The main objective of Software Engineering as a discipline [11] is the production of error-free, reliable software that meets user’s requirements effectively and that it is delivered on time and within budget. To support this objective introduces the idea of Software Process Improvement, which is a combination of appropriate software engineering techniques and principles geared towards improving software production. In order for these techniques to be engaged, they first have to be taught. This paper shall discuss the reason why SPI should be taught at undergraduate level and also look at the way it should be taught in an attempt to get the full potential of the SPI into the minds of undergraduate students as to equip them with new technical focuses. In this paper I shall analyze and discuss ways to improve the module and how to make it more interactive and produce a better learning environment for students and lecturers alike.

    Read More

  • Software Engineering Process And Process Improvement In Software Process

    1114 Words  | 3 Pages

    It is the current working stage on process assessment and improvement that started at the Software Engineering Institute(SEI) in the 1980s.

    Read More

  • What Is The Importance Of Software Testing?

    936 Words  | 2 Pages

    The software testing phase can be broken down into smaller stages, each of which have their own importance:

    Read More

More about Waterfall Model: The Software Development Life Cycle Model

Open Document