What is a Feature

I am sorry about my ignorance to the term "feature" in FDD, however I am still confused and unable to understand it fully. My question is that

1. What exactly a feature is? is it a way to define the system requirement or the way to define how the new system will work?
2. What level of granularity should we need to go in terms of defining a feature?
3. A feature set could be a synonym to the sofwtare Module and its features?
4. How this grouping should be done?
5. is a feature could be synonym to use cases?

How the activities like user interface design, System user interaction behavior are supported by FDD?

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Jeff De Luca's picture

Try reading these threads first

In no particular order.

Breakdown of requirements in features

Planning by feature

Feature grouping

Fixes

Maintenance and FDD

Use case driven development 1

Use case driven development 2

Also, try the search box on this website.

Post back if you have more questions.

Jeff