Hi All,
I am new to FDD and want to make sure I understand how to build a feature list.
I know some of this has been covered in http://www.featuredrivendevelopment.com/node/view/590
so please exuse the repeat but I'd like to be specific about business systems.
Firstly some observations using a real-world example of an insurance firm we deal with in the
language they use to describe their business:
a) their business is made up of one or more business units
b) we deal with one or more business units (travel insurance, medical insurance)
c) we talk with business people who make up those business units (domain expert) (claims manager)
d) business people perform and are responsible for certain business processes
e) business units perform lines of business for that business (subject area) (insurance claims)
f) lines of business are made up of business processes (feature set) (claims management)
g) business processes are made up of business activities (feature) (claim application)
So in our case our feature list would be made up of:
Business Unit -> Line of business -> Business Process -> Business Activities
Travel Insurance -> Insurance Claims -> Claims Management -> Claim application
Travel Insurance -> Insurance Claims -> Claims Management -> Claim processing
Travel Insurance -> Insurance Claims -> Claims Management -> Claim payment
Travel Insurance -> Insurance Claims -> Claims Management -> Claim rejection
Have I got the right mapping for FDD :?
Regards,
Grant
do the first process first
you have nothing to direct this without the modeling process first. No scope, no requirements, nothing.
Would anonymous care to offer a real world example?
:O Would anonymous care to offer a real world example we can discuss then so I can get an answer to a legitimate question a number of people seem to be asking also?
Tadd StuartPortland Maine U
Tadd Stuart
Portland Maine USA
Using the templates defined for FDD is a great help and may also help you with the functional decomposition for FDD
FDD breaks downs into three basic tiers with a template for each tier.
Major Feature
<object> Management
Feature Set
<action> <-ing> a(n)<object>
Feature
<action> <result> by|for|of|to a(n)<object>
So from your examples, you would see something like...
Claim Management -> Paying a Claim -> List the payments made to a Claimant
Claim Management -> Paying a Claim -> Create the payment request for a Claimant