Scribd Logo
Upload

Welcome to Scribd!

  • Q2

    Uploaded by

    Manoj Kathuria
    184 views1 page
    The document discusses ways to build software that is resilient to changes. It suggests talking to end users early in the development process to understand their needs. It also recommends more planning, involving more people in the design process, and publicizing plans to catch problems early. More testing at early stages can also help address issues before the software is fully developed.

    Original Description:

    Q2 SE

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The document discusses ways to build software that is resilient to changes. It suggests talking to end users early in the development process to understand their needs. It also recommends more planning, involving more people in the design process, and publicizing plans to catch problems early. More testing at early stages can also help address issues before the software is fully developed.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    184 views1 page

    Q2

    Uploaded by

    Manoj Kathuria
    The document discusses ways to build software that is resilient to changes. It suggests talking to end users early in the development process to understand their needs. It also recommends more planning, involving more people in the design process, and publicizing plans to catch problems early. More testing at early stages can also help address issues before the software is fully developed.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 1

    Course- DAC

    Abhirup Majumder (02)

    Submitted By: Manoj Kathuria (39) &

    Q: Many modern applications change frequently before they are


    presented to the end user and then after the first version have
    been put into use. Suggest a few ways to build software to stop
    deterioration due to change.
    A:
    One suggestion is to talk to the end users in the beginning.
    Too often something gets developed without ever communicating
    with that level.
    Another suggestion is more planning and more checks. In
    many companies the initial design of something is based on just a
    few people. We need to get more people involved on the front end
    and the end result will be better. If the plans are publicized and
    shared with more people, we might be able to catch more
    problems early.
    More testing at early stage also helps.

    You might also like