Agile vs Traditional Methodologies and Other Approaches
Classified in Other subjects
Written at on 
English with a size of 3.35 KB.
Agile vs. Traditional Methodologies
This table compares key differences between Agile and Traditional software development methodologies:
| Agile Methodology | Traditional Methodology |
|---|---|
| Few artifacts. Modeling is dispensable, with disposable models. | More artifacts. Modeling is essential, with maintained models. |
| Few, more general and flexible roles. | More roles, more specialized. |
| No traditional contract; should be fairly flexible. | There is a fixed contract. |
| Customer is part of the development team (in addition to being in-situ). | The customer interacts with the development team through meetings. |
| Aimed at small projects. Short term (or frequent deliveries), small teams (<10 members) working on the same site. | Applicable to projects of any size, but tend to be especially effective/used in large projects and possibly dispersed teams. |
| The architecture is defined and improved throughout the project. | Promotes that the architecture is defined early in the project. |
| Emphasis on human aspects: the individual and teamwork. | Emphasis on defining the process: roles, activities, and artifacts. |
| Changes are expected during the project. | It is *not* expected that high-impact changes occur during the project. |
| Based on heuristics from code production practices. | Based on rules from standards followed by the development environment. |
Gane/Sarson Methodology
Method Gane/Sarson
- Orientation: This method is process-oriented and uses data flows.
- Approach: Uses a top-down approach, which allows processes to decompose into smaller processes until a specification is reached.
- This method is a method of analysis and structured design, based on these two main processes.
- Each of these major phases is composed of stages that contribute to efficiently developing the whole system development process.
- Structured Analysis:
- Stages: Initial study, detailed study, set menu options, select alternative.
2. Structured Design: The fundamental purpose of the design phase is to deliver the functions required by the user.
- Objectives: Control, Performance, Changeability.
Techniques used: Interviews, data flow diagrams, data dictionary, logical processes, physical techniques for immediate access.
Coad/Yourdon Methodology
Method Coad/Yourdon
Uses a 5-step model:
- Definition of objects and classes.
- Definition of structures.
- Definition of topic area.
- Definition of attributes.
- Definition of services.
Techniques:
- Class and Object Diagram
- Object-State Diagram: Shows all possible states of an object and the allowed transitions between states.
- Service Diagram: Depicts the detailed logic within a single service.