What are the most significant differences among structured, object-oriented, and agile methods? What do they have in common?

Question

What will be an ideal response?

Answer 1

• Structured analysis regards processes and data as separate components, and uses DFDs to show how processes transform data into useful information.
• Object-oriented (O-O) analysis combines data and the processes that act on the data into things called objects. O-O analysis uses various diagrams and object models to represent data, behavior, and by what means objects affect other objects. By describing the objects (data) and methods (processes) needed to support a business operation, a system developer can design reusable components for faster system implementation and decreased development cost. Many analysts believe that, compared with structured analysis, O-O methods are more flexible, efficient, and realistic in today’s dynamic business environment.
• Agile development methods have attracted a wide following and an entire community of users. Agile methods typically use a spiral model, which represents a series of iterations, or revisions, which are based on user feedback. Proponents of the spiral model believe that this approach reduces risks and speeds up software development. Analysts should recognize that agile methods have advantages and disadvantages. By their nature, agile methods allow developers to be much more flexible and responsive, but can be riskier than more traditional methods. For example, without a detailed set of system requirements, certain features requested by some users might not be consistent with the company’s larger game plan. Other potential disadvantages of adaptive methods can include weak documentation, blurred lines of accountability, and too little emphasis on the larger business picture. Also, unless properly implemented, a long series of iterations might actually add to project cost and development time.
Although the three methods use different techniques, they have a great deal in common. Each method seeks to create a model of the system that can be analyzed, documented, and modified to meet system requirements. It is not uncommon for a developer to use all of these methods, and more – they are not mutually exclusive.