Feature Driven Development

Hi Jeff,
I am sending you an attachment so that you can have a bit more clear idea about my current work. This is my research proposal. I need more specific problem and scope to work here. Could you suggest me anything?

Thank you.
Afroza

I have a question regarding conversion work and how it is typically reported on FDD projects. We are currently developing a second release of an application that is already live. As such we have a small but none-the-less critical conversion activity that involves the creation of some conversion sql scripts and a mechanism to import conversion data from an external system by a batch process. Therefore there are several conversion activities that need to be done during the development phase to prepare these scripts/mechanisms ready for use on 'go live' day.

At the start of the project we derived PD, UI and SI features and didn't include conversion development activities in these lists.

Hi,

I've recently learned about FDD. We are currently working on the dependency view among all the features in a feature model and have developed an user interface for feature model and dependency model.

Now the idea that I wanted to explore is to use the use case to model functional features taken from the feature model. I want to define the use case in detail, I just identify use case associated to each feature. Afterwords this idea may be used to specify component. Like this..........
Feature model -> Functional features ->Use case -> Component

My questions are: 1) Is this something that could work? 2) What should be the intermediate phases? 3) What will happen to the Non-functional features?

An RSS feed of this site is available by using this link http://www.featuredrivendevelopment.com/rss.xml. The majority of the content of this site is contained in the discussion forums with the rest of the content being the few top level pages linked in the banner at the top of each page.

If you are relying on RSS, you will be notified when a new top-level page is added or a new discussion forum topic is added. RSS will not notify you if a comment (discussion thread) is added to any existing content.

What the means is that if you want to see the discussion threads or are waiting on a reply to a comment, the RSS feed will not notify you of this.

The official FDD Certified List

Last Update: 7 October 2011

Hi All,

ITPS is pleased to announce a new pricing model for FDDTracker http://www.fddtracker.com.

We listened to your feedback on our old pricing model and have made the pricing model much more flexible for smaller development teams.

In response to the FDD communities feedback We have also now moved to a single product edition providing all the features.

Single User $US 99
Up to 2 Users $US 190
Up to 3 Users $US 290
Up to 4 Users $US 350
Up to 5 Users $US 395
Up to 10 Users $US 590

I first learned about FDD this year at the Agile Developers Conference and was so impressed by it, that I've implemented a slightly different version of it at my workplace. We're still ironing out some of the administrative stuff, and one of those is the evaluation of the programmers.

In the past, the supervisor of the programmer has worked with him/her throughout the year, and we have some standard forms that they would fill out. We now have Chief Programmer positions and Supervisor positions. The way we'll be handling the salary/bonus allocations is with feedback from the CP about the programmer. I'm trying to develop the things that will be in this feedback, and was looking for some insight from those that have been doing it longer.

I am pleased to anounce that the October release of FDDManager, which includes the following enhancements, is now available for download.

• Linux compatibility
• New Project Summary panel
• New Parameterised Reports
• A Quick Edit table view

For more details, or to download, please visit www.fddmanager.com.

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?

Hi all,

Can anyone point me to metrics that demonstrate the advantages (or disadvantages) of adopting an agile development methodology and/or FDD? I'm looking for things like cost savings, defect density, SLOC/hour, etc.

Thanks a bunch! :)

-- Patrick