AHW2 Hello I have an agile software development methodology

AHW2) Hello I have an agile software development methodology that is proposed by the combining the two other agile development methodologies, my question is how can I draw its process model that describe it entirely(as drawing graphs). The description of the new proposed methodology is given below:

1. The new Agile methodology is \"Feature and Test Driven Development\".

2. Feature Driven Development (FDD) is an iterative and incremental Agile methods
for developing software. This is client centric pragmatic Software process.
As the name implies, \"Features\" are important in FDD.
A feature is a smallclient valued function expressed in form of
action - result - object.

Test Driven Development (TDD) relies on repetition of development cycle -
i.e. write a test before we write the production code to fulfill the requirement.
Goal of TDD is specification and not validation.

We can combine this FDD and TDD to form new \"Feature and Test Driven Development\"
(FTDD).

In FDD, we concentrate on feature based on client request and do the development.
We only think of testing once the development of the feature is complete.

In TDD, requirements are turned into smalltestcases and code is improved to
pass the test case.

We need both the approach for effective Software development and delivery.

Once we get the requirement from customer, we can do FDD and TDD in parallel,
so that testing and development happens in parallel and there is no wastage of time.

3. We can have the project flow as below.

once we get the requirement, we can have 1 week time for FDD and TDD to happens
in parallel.
So that in one end, FDD team can concentrate on developing feature.
And, TDD team can develop suitable test cases so that they can check the feasibility.

4. - Adaptation -> Based on the complexity of requirement, we can have change
                   in 1 week duration time.
                   With this approach, FDD team need not doseperate testing.
                   And TDD team need not write production code after introducing
                   test cases.
                  
   Communication -> FDD and TDD teams can communicate each other for the
                   new feature interface and help each other.
                     
   Customer Satisfaction and Business value ->
                   With FTDD approach, there is lot of time saved.
                   For example, FDD team need not do write test cases to
                   test the feature.
                   TDD team after verifying the requirement need not write
                   production code and that time is saved.
                   If TDD team finds that requirement is not feasible, then
                   it can discard the code developed by FDD.
                  
   Frequent Inspection and Retrospective ->
                   Here FDD teams and TDD teams are completelyindependant and
                   only need to communicate and start requirement analysis and
                   after either developing code or writing the test cases.
                  
                   By this the retrospective time for completion is reduced by a week.

sincerely...

Solution

The above scenario is good to apply whether it is a small or large projects.

As discussed above first get the requirement from the client and plan the time for the project.Then plan how many FDD and TDD teams needed fo the project.

Then divide the project into modules and assign to each team. Here the main important thing to get successfull is make those all teams communicated regularly and make them discuss about the issues or progress about the things goign on.