Re: Use-case driven development - getting to work-tasks ?
From: Anders Pedersen (psredna_at_pallas.dk)
Date: 01/25/05
- Next message: cr88192: "Re: new here, my lang project..."
- Previous message: Ramrao: "Requires more information about *.acs file entries"
- In reply to: A Mackie: "Use-case driven development - getting to work-tasks ?"
- Next in thread: H. S. Lahman: "Re: Use-case driven development - getting to work-tasks ?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 25 Jan 2005 12:19:12 +0100
"A Mackie" <andrew@mackie14.freeserve.co.uk> wrote in message
news:xn0dxo4ee101gk8001@news.btclick.com...
> 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.
You get from a use case collection to a component collection by doing design
work.
In RUP-speak:
Select some architecturally significant use cases (vague, I know), add the
nonfunctional requirements (uptime, throughput, usability, developer
staffing etc.),
do some creative thinking and produce a candidate architecture.
> 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!
The use cases are end-user requirements and the specs for the components are
a design artifact. They are not the same thing.
You may be right that it's "double the work", but it's necessary work. The
design
represents new insight, knowledge and decisions about how you want to
build the system. That insight is not present in the use cases.
Regards,
--Anders.
- Next message: cr88192: "Re: new here, my lang project..."
- Previous message: Ramrao: "Requires more information about *.acs file entries"
- In reply to: A Mackie: "Use-case driven development - getting to work-tasks ?"
- Next in thread: H. S. Lahman: "Re: Use-case driven development - getting to work-tasks ?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
