Scribd
Upload
3 views6 pages

Assignment 2 Agile

The document discusses Feature Driven Development (FDD), an Agile methodology focused on systematic, client-valued feature development for larger projects. It outlines the processes of model development, feature list creation, and five main processes of FDD, illustrated with a feature breakdown structure for a To-Do List application. Additionally, it compares FDD with other Agile methodologies and highlights challenges and best practices for successful implementation.

Uploaded by

WQ Entertainment
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
3 views6 pages

Assignment 2 Agile

The document discusses Feature Driven Development (FDD), an Agile methodology focused on systematic, client-valued feature development for larger projects. It outlines the processes of model development, feature list creation, and five main processes of FDD, illustrated with a feature breakdown structure for a To-Do List application. Additionally, it compares FDD with other Agile methodologies and highlights challenges and best practices for successful implementation.

Uploaded by

WQ Entertainment
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

Subject

Software Process and Agile Pratice


Submitted To
Ms. Tehmeena Ehsan
Submitted By
Waqas Ahmad
Course Code
SE-417
Roll No.
21011598-081
DEGREE PROGRAM TITLE AND SECTION
BSSE-B
Table of Contents
Introduction ............................................................................................................................................. 1
Understanding Feature Driven Development (FDD) ........................................................................... 1
Model Development in FDD ................................................................................................................... 1
Feature List Creation ............................................................................................................................. 2
Steps to Create a Feature List: .......................................................................................................... 2
Five Main Processes of FDD .................................................................................................................. 2
1. Develop an Overall Model .............................................................................................................. 2
2. Build a Feature List ........................................................................................................................ 2
3. Plan by Feature ............................................................................................................................... 2
4. Design by Feature ........................................................................................................................... 3
5. Build by Feature .............................................................................................................................. 3
Feature Breakdown Structure for a To-Do List Application.............................................................. 3
Feature 1: Add a Task ........................................................................................................................ 3
Feature 2: Mark a Task as Completed.............................................................................................. 3
Expanded Feature Breakdown for Scalability ................................................................................. 3
Comparison of FDD with Other Agile Methodologies......................................................................... 4
Challenges and Best Practices in FDD .................................................................................................. 4
Challenges:........................................................................................................................................... 4
Best Practices: ..................................................................................................................................... 4
Conclusion ............................................................................................................................................... 4
Question:
Discuss how you would implement Feature Driven Development (FDD) from start to finish.
Include details on model development, feature list creation, and the five main processes. Create a
feature breakdown structure for a small project (e.g., developing a to-do list application) with an
example. Include at least 2 features and describe the steps to plan, design, and build these features.

Introduction

Feature Driven Development (FDD) is an iterative and incremental Agile methodology primarily
used for larger projects. Unlike Scrum or Kanban, FDD focuses on developing small, client-valued
features systematically. The core idea of FDD is to ensure continuous progress by following a
structured model-driven approach. This assignment discusses the complete process of
implementing FDD, covering model development, feature list creation, and the five key processes.
Additionally, it includes a feature breakdown structure for a small project a To-Do List application
with examples of two core features.

Understanding Feature Driven Development (FDD)

FDD was introduced in 1997 by Jeff De Luca and Peter Coad to address challenges in large-scale
software projects. The methodology emphasizes:

 Domain modeling to understand the problem space


 Small, incremental feature development
 Frequent builds and feature deliveries
 Strong focus on design and quality
 Collaboration among cross-functional teams

FDD is particularly useful in projects where requirements change frequently, ensuring that
business needs are continuously met.

Model Development in FDD

The first step in FDD is developing an Overall Model that represents the system’s functionalities.
The model development process includes:

1. Understanding the Problem Domain – Identify business needs and system requirements.
2. Building High-Level Diagrams – Represent the system’s core architecture and
functionality.
3. Collaborating with Domain Experts – Ensure that developers and business stakeholders
align on project goals.

1
4. Iterative Refinement – Modify the model as new insights emerge during the development
process.

A well-defined model provides a roadmap for further feature development, reducing ambiguities
and misinterpretations.

Feature List Creation

Once the model is established, the next step is breaking the system into manageable features. A
feature in FDD is defined as a small, client-valued function that can be implemented within two
weeks. Features are typically structured as “action + result + object” (e.g., "Allow users to add a
task to the to-do list").

Steps to Create a Feature List:

1. Identify Subject Areas – Broad functional categories (e.g., Task Management, User
Authentication).
2. Break Down into Feature Sets – Smaller logical groups of functionalities.
3. List Individual Features – Each feature should be atomic and provide a tangible business
value.
4. Prioritize Features – Rank features based on business needs and dependencies.

Five Main Processes of FDD

FDD consists of five key processes that guide systematic development:

1. Develop an Overall Model

 Conduct domain analysis and define the system structure.


 Create conceptual diagrams, class models, and entity-relationship models.

2. Build a Feature List

 Define core functionalities using the structured approach discussed earlier.


 Group features logically for ease of development.

3. Plan by Feature

 Assign features to small development iterations (sprints).


 Define deliverables for each iteration.
 Identify dependencies and risks associated with features.

2
4. Design by Feature

 Create design documentation for selected features.


 Define UI wireframes, database schema, and business logic.
 Ensure alignment with the overall model.

5. Build by Feature

 Implement and unit-test each feature.


 Integrate with the existing system.
 Conduct user acceptance testing (UAT) before deployment.

Feature Breakdown Structure for a To-Do List Application

To demonstrate FDD implementation, we consider a simple To-Do List application with two core
features:

Feature 1: Add a Task

 Plan: Define task structure (title, description, due date, priority).


 Design: Create UI wireframes for "Add Task" button and input fields.
 Build: Develop front-end form, implement backend storage logic, and test.

Feature 2: Mark a Task as Completed

 Plan: Identify how task status is stored and updated.


 Design: Design a checkbox or toggle button for task completion.
 Build: Implement logic to update task status and modify UI to reflect completed tasks.

Expanded Feature Breakdown for Scalability

To further expand our project scope, we consider additional features:

 Edit a Task – Modify existing tasks in the list.


 Delete a Task – Remove completed or unwanted tasks.
 Set Task Reminders – Notify users of upcoming deadlines.
 User Authentication – Secure login system for task management.

Each feature follows the plan-design-build approach, ensuring systematic implementation.

3
Comparison of FDD with Other Agile Methodologies

Methodology Focus Best For


Scrum Iterative sprints, team collaboration Small to medium teams
Kanban Continuous workflow, minimal planning Ongoing maintenance projects
FDD Feature-based incremental development Large-scale software projects

Unlike Scrum, which emphasizes fixed-length iterations, or Kanban, which focuses on workflow
optimization, FDD ensures a structured, model-driven approach suitable for complex projects.

Challenges and Best Practices in FDD

Challenges:

 Requires experienced developers due to its model-driven nature.


 May not be suitable for very small teams or projects.
 Heavy reliance on upfront modeling can delay initial development.

Best Practices:

 Keep feature descriptions concise and client-focused.


 Ensure continuous integration and testing for each feature.
 Encourage collaboration between developers, designers, and domain experts.
 Maintain updated documentation to align with evolving system requirements.

Conclusion

Feature Driven Development (FDD) is a structured Agile methodology that promotes high-quality
feature delivery through systematic planning and incremental development. By following the five
key processes—modeling, feature list creation, planning, designing, and building—teams can
deliver scalable software efficiently. The To-Do List application example demonstrates how FDD
can be applied in real-world scenarios to ensure structured development. This methodology is
particularly advantageous for large-scale projects where organization, predictability, and quality
assurance are critical. By adhering to best practices, teams can maximize efficiency and deliver
robust software solutions that meet evolving business needs.

You might also like