Agile Method Proposal for GUS DevelopmentZeke LongCS 38310/22/2010I propose that we use feature-driven development (FDD) for the GUS project. FDD is an industry-recognized software development methodology that is used by many engineering companies. Using FDD, we will begin by establishing an overall domain model that describes the finished product. Then we will focus on one feature at a time in order to incrementally produce a final product. As each feature is completed, it will be added to the main build as a functioning addition. In short, FDD can be described as approaching a project by viewing it as a set of features that are combined to create the overall product. Since GUS will have many features that can be well-defined, this is an ideal approach. FDD splits the project into five activities. First, we have to develop the overall domain model. Next, we have to construct a feature list by splitting up the domain into subject areas and identifying activities within each subject area. These activities will make up the feature list, and each one should be small enough to be implemented within a two week time frame; often times they are implemented much faster than two weeks. Next, we plan by feature, which consists of designing the development plan and assigning features to chief programmers. Next, we design by feature. In this step, a feature team is formed by the chief programmer. The teamcreates sequence diagrams for each feature, refines the overall model, writes class and method prologues, and conducts a design inspection. The final activity is called build by feature. This isthe step where classes and methods are actually implemented. After implementation, they are inspected and tested. Once all tests pass, the feature is added to the main build.Milestones are recorded during the design by feature and build by feature activities. There are six milestones, which consist of: domain walkthrough, design, design inspection, code, code inspection, and promote to build. The first three are contained within the design by feature stage, and the last three are contained within the build by feature stage. Each one is marked with a percentage to track the progress of each feature. Domain object modeling, developing by feature, component/class ownership, feature teams, inspections, configuration management, regular builds, and visibility of progress and results are all industry best practices. FDD combines all of these (as described in the second and third paragraphs) effectively to create a high quality final product.Many developers agree that this development method is intuitive and provides a lot of benefits. One benefit is the fact that clients like it when you can demonstrate to them the features that are completed so far and tell them what features are currently being worked on. Another benefit is that you can easily track the progress of the project at hand. A third benefit is that development iterations are usually shorter than with most other agile methods. Furthermore, FDD can be combined with pair programming within each feature team. These are just a few of the benefits of using FDD.It is clear that FDD is well-suited for the development of GUS. Other agile methods would work, but FDD is simple and effective. We have already identified much of the overall domain model in previous assignments. We have also identified use cases and created apreliminary class diagram. From this point, we just need to continue from where we left off by constructing the feature list and going from there. We will have to refine our domain model and come up with more features (basically use cases) of course, but we are already off to a