Scribd Logo
Upload

Welcome to Scribd!

  • 45 views

    The Software Development Process: Excerpts From Martin Fowler, 2004, UML Distilled 3 Edition, Addison-Welsey New York

    Uploaded by

    Jane Asasira
    The document discusses four main software development processes: 1) Waterfall - A linear process that breaks a project into distinct phases like requirements, design, coding, and testing. 2) Iterative - Breaks a project into iterations where a subset of functionality is developed in each iteration through the full lifecycle. 3) Agile - Adaptive people-oriented processes using short iterations and frequent reassessment. 4) Rational Unified Process (RUP) - An iterative framework with four phases: inception, elaboration, construction, and transition.

    Copyright:

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

    The Software Development Process: Excerpts From Martin Fowler, 2004, UML Distilled 3 Edition, Addison-Welsey New York

    Uploaded by

    Jane Asasira
    45 views13 pages
    The document discusses four main software development processes: 1) Waterfall - A linear process that breaks a project into distinct phases like requirements, design, coding, and testing. 2) Iterative - Breaks a project into iterations where a subset of functionality is developed in each iteration through the full lifecycle. 3) Agile - Adaptive people-oriented processes using short iterations and frequent reassessment. 4) Rational Unified Process (RUP) - An iterative framework with four phases: inception, elaboration, construction, and transition.

    Original Description:

    A guide to developing any computer software convenient for both beginners and professionals.

    Original Title

    Software Development Process

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document discusses four main software development processes: 1) Waterfall - A linear process that breaks a project into distinct phases like requirements, design, coding, and testing. 2) Iterative - Breaks a project into iterations where a subset of functionality is developed in each iteration through the full lifecycle. 3) Agile - Adaptive people-oriented processes using short iterations and frequent reassessment. 4) Rational Unified Process (RUP) - An iterative framework with four phases: inception, elaboration, construction, and transition.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    45 views13 pages

    The Software Development Process: Excerpts From Martin Fowler, 2004, UML Distilled 3 Edition, Addison-Welsey New York

    Uploaded by

    Jane Asasira
    The document discusses four main software development processes: 1) Waterfall - A linear process that breaks a project into distinct phases like requirements, design, coding, and testing. 2) Iterative - Breaks a project into iterations where a subset of functionality is developed in each iteration through the full lifecycle. 3) Agile - Adaptive people-oriented processes using short iterations and frequent reassessment. 4) Rational Unified Process (RUP) - An iterative framework with four phases: inception, elaboration, construction, and transition.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    You are on page 1of 13

    THE SOFTWARE

    DEVELOPMENT PROCESS
    Excerpts from Martin Fowler, 2004, UML Distilled 3rd Edition, Addison-
    Welsey New York
    Software development processes
    Modelling techniques, like UML, are part of or fit into the software
    development process. There are four software development processes;

    • Waterfall

    • Iterative

    • Agile and

    • Rational unified Process


    1. The Waterfall Process
    Breaks down a project based on activity. Software development is
    broken down into: Requirements analysis, Design, Coding and
    Testing. Design can only be done after Requirements analysis.
    Coding can only be done after design. And, Testing can only be done
    after coding.

    There is usually some form of handover between phases (but there


    are often backflows too).
    1. The Waterfall Process
    2. The Iterative Process
    The Iterative Process Breaks down a project by subsets of functionality.
    One can take a year and breaks it into 3-month iterations. For example; In
    the first iteration, a quarter of the requirements can be taken and the
    complete software lifecycle for that quarter is done: analysis, design, code
    and test. At the end of the first quarter, one would thus have a system that
    does a quarter of the needed functionality. A second iteration would have
    to be done so that at the end of it, one would have a system that does half
    the functionality.
    2. The Iterative Process
    3. Agile Process
    Agile processes are strongly adaptive in their nature. They are
    people-oriented processes. They assume that the most important
    factor in a project’s success is the quality of the people on the project
    and how well they work together. Processes and tools used are
    inconsequential. Agile methods tend to use short time-boxed
    iterations.
    3. Agile Process
    4. Rational Unified Process (RUP)
    RUP is actually a process framework. It is also an iterative process. All RUP
    projects follow four phases;

    • Inception: Makes an initial evaluation of a project. Typically, in inception, one


    decides whether to commit enough funds to do an elaboration phase.

    • Elaboration: Identifies the primary use cases of the project and builds software in
    iterations in order to shake out the architecture of the system. At the end of
    elaboration, one should have a good sense of the requirements and a skeletal
    working system that acts as the seed of development. One should have identified
    and resolved the major project risks.
    4. Rational Unified Process (RUP)
    • Construction: Continues the building process, developing enough
    functionality to release.

    • Transition: Includes various late-stage activities like software


    deployment into the data center, user training, debugging etc.
    PREDICTIVE Vs ADAPTIVE PLANNING
    Predictive
    A predictive planning approach looks to do work early in the project in
    order to yield a greater understanding of what has to be done later.

    A project has two stages. The first stage comes up with plans and is
    difficult to predict, but the second stage is much more predictable
    because the plans are in place.

    The waterfall process is predictive.


    Adaptive

    Change, especially requirements change, is a constant in a software


    project. A plan is treated as a baseline to assess the consequences of
    change rather than a prediction of the future.

    You might also like