Scribd Logo
Upload

Welcome to Scribd!

  • 366 views

    M.I.S Assignment 1 Waterfall Model

    Uploaded by

    Mansi Saini
    The document summarizes the waterfall model of software development. It consists of distinct phases in linear order: 1) Requirements analysis, 2) Design, 3) Coding and unit testing, 4) Integration and system testing, 5) Implementation, and 6) Operation and maintenance. Each phase has distinct activities and deliverables, with the output of one phase becoming the input to the next. The waterfall model provides a systematic approach but is not well suited for projects where requirements are not well defined.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    M.I.S Assignment 1 Waterfall Model

    Uploaded by

    Mansi Saini
    366 views4 pages
    The document summarizes the waterfall model of software development. It consists of distinct phases in linear order: 1) Requirements analysis, 2) Design, 3) Coding and unit testing, 4) Integration and system testing, 5) Implementation, and 6) Operation and maintenance. Each phase has distinct activities and deliverables, with the output of one phase becoming the input to the next. The waterfall model provides a systematic approach but is not well suited for projects where requirements are not well defined.

    Original Title

    file

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document summarizes the waterfall model of software development. It consists of distinct phases in linear order: 1) Requirements analysis, 2) Design, 3) Coding and unit testing, 4) Integration and system testing, 5) Implementation, and 6) Operation and maintenance. Each phase has distinct activities and deliverables, with the output of one phase becoming the input to the next. The waterfall model provides a systematic approach but is not well suited for projects where requirements are not well defined.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    366 views4 pages

    M.I.S Assignment 1 Waterfall Model

    Uploaded by

    Mansi Saini
    The document summarizes the waterfall model of software development. It consists of distinct phases in linear order: 1) Requirements analysis, 2) Design, 3) Coding and unit testing, 4) Integration and system testing, 5) Implementation, and 6) Operation and maintenance. Each phase has distinct activities and deliverables, with the output of one phase becoming the input to the next. The waterfall model provides a systematic approach but is not well suited for projects where requirements are not well defined.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 4

    M.i.

    s assignment 1
    Waterfall model

    Submitted by: submitted t0:

    Mansi saini Mr. shaifali sharma

    B.b.a vi sem

    Water fall model


    The waterfall model state that the phases are organisedin a linear order.
    The waterfall model is also known as classical waterfall model.

    The essence of this model is that the process of software development


    consist of a linear set of distinct phases. Each phases in this model is
    distinct and mandatory every project irrespective of project size, at every
    phases there is a provision of verification and validation and correction of
    errors .

    Following ar the phases of this model:

    1. Requirement analysise and specification: The


    requirement describe the “what “ of a system not a “how” .this
    phases produce a large document , contain what the system will do
    without describing how it will be done .the resultant document is
    known as software requirement specification (SRS) document.

    2.Design and specification : the goal of the design


    phase is to transform the requirement sepicified in the SRS
    document into the structure that is suitable for implementation in
    some programming language.
    (i)traditional design approach: it consist of two
    activities , first a structured of the analysise of the
    requirement specification is carried out where the detailed
    structure of the problem is examined . the result of the
    structured design are transformed in the software design.
    (ii)Object Oreinted deisgn approach: various
    object in this system are identified .The OOD approach has
    several benefit such as lower development time and effort
    and better mentalibilty.

    3.Coding and unit testing: The main purpose of this


    phase is to translet the software design into source code.initially,
    small modulas are tested unto isolation from the rest of the
    software product . the purpose of unit testing is to determine the
    correct working of individual modualas

    4.Integration and system testing: Integration is


    normally carried out incrementally over a number of steps .During
    each integration steps, the partially integrated system is tested and
    a set of previously planned modules is added to it.

    The objective of system testing is to determine


    whether the software system performed as per the requirement
    mentioned in the SRS document .

    5.Implementation: once the system has been design, it si


    ready for implementation . it is concerned with those task leading
    immediately to a fully operational system :
    (i) Implementation of computer system to replace a manual
    system
    (ii) Implementation of a new computer system to replace an
    exisiting one
    (iii) Implementation of a modified application to repalce an
    exisiting one using the same computer

    6.Operation and maintainence: Maintainence is an


    important part of SDLC. If there is any error to correct or change
    needed by the system then it is done in the matinenace phase . it
    may consume more time than the time consume in the
    development . it include the set of activities that are performed after
    the system deliverd to the customer.

    Advantages of waterfall model


    1. It follwa simple approach and has proper documentation.
    2. Enforced disciplined ,planned and manageable approach.
    3. This model provide a systematic and sequential approach to
    software development.
    4. It is well suited for routine type of project where the requirement
    are well understood.

    Disadvantages of warefall model

    1.difficult to estimate resources accurately.


    2. lead to some what bureaucrartic style of work.
    3. it is difficult to define all requirement at the beginning of a
    project.

    You might also like