Use-case driven development - getting to work-tasks ?

From: A Mackie (andrew_at_mackie14.freeserve.co.uk)
Date: 01/25/05

  • Next message: stevenmathers_at_yahoo.com: "Re: cant find a pattern to fit neatly - how to make a large number of monsters?" 
    Date: Tue, 25 Jan 2005 08:09:52 +0000 (UTC)

    How do you get from a list of use cases, to a list of software components
    which can be assigned to individual developers to create ? There seems to be
    a basic mismatch between use cases, and generating development tasks for
    developers to work on. Consider:

    A single use case may require numerous software components to implement it.
    A single software component may be used across multiple use cases.

    How do you avoid writing requirements twice, once in the form of use-cases,
    and once in the form of specs for software modules ? Seems like double the
    work!

    A simple manual approach - spread*** with a matrix of use cases down one
    side, software components along the top, mark an X in each cell where a
    software component supports a particular use case. It should then be clear to
    a developer what uses cases they need to be looking at, to be aware of what
    requirements their software component must help satisfy. Not very scalable
    though!

    How is this problem typically solved ?

    Thanks,
    Andy Mackie

  • Next message: stevenmathers_at_yahoo.com: "Re: cant find a pattern to fit neatly - how to make a large number of monsters?"
    • Quantcast