PREDICTION OF SUITABILITY OF SOFTWARE DEVELOPMENT METHODOLOGY USING AGILE CONFIGURATION

Abstract

For a strong house, we need a strong foundation. Similarly we need strong software development methodology to develop a strong and reliable software product which meets the needs of stakeholders. To ensure the durability and reliability of software, appropriate methodology is required. From the very beginning, many non-agile methods have been used for software development. Developers used ER Diagrams to show detailed entity relationship model of an organization. The main components of the ER diagrams were data entity, relationships and their associated attributes. To show the flow in the Information system, Process flow diagrams were used. For visualization, specifying and documenting object oriented system UML provides modeling language. These approaches take significant time and cause overhead in the software development even in the situations where they are not required. Major time is spent on documenting rather than actually implementing the system. Due to the drawbacks of the heavyweight traditional methods, Agile methods are welcomed in the industry by both the developers and the managers. Agile methods focus on quick delivery of the software to the customer and modifying the software as per the requirements of the customer. There is a need of the constant communication among the development teams and the customer to provide feedback for the system so that it can be quickly adapted to new requirements and satisfy the customer needs. Many Agile methodologies are used in the industry such as DSDM(Data System Development Method), XP(Extreme Programming), RAD(Rapid Application Development), SCRUM, FDD(Feature Driven Development) etc. Refer to Chapter 2 for the overview of these methodologies. Large Software like Windows , Google Drive cannot be developed using Agile Methods as there is proper documentation required for the system being developed.