Object Oriented and Agile Methods versus Classical Methods

Object Oriented analysis and design along with the Agile approach is compared and contrasted to Classical Methods, such as Structured Analysis, Structured Design, Data Flow Analysis, and Entity Relalionship database modeling.

Title Sort by Title, Ascending Sort by Title, Descending Description Sort by Description, Ascending Sort by Description, Descending
Extreme Programming Considered Harmful One of the variants of the Agile methodology is Extreme Programming (XP), characterized by brevity, or lack, of external documentation, minimal up front design, requirements on 3x5 cards, and continuous testing and "refactoring" of code. This paper explores some of the limitations of that approach, including some history on what was probably the original XP project, the Chrysler Comprehensive Compensation payroll project of 1998-1999, and how it ultimately failed.
Has the Object Oriented Paradigm Kept its Promise? This research paper substantiates that whether measured directly or indirectly, object-oriented software is more complex than functionally equivalent procedural software. The promise that more natural description and encapsulation will result in less complex software has not been realized. Another finding: These complexities, and the lack of many proven testing techniques to handle them, increase the overall cost of testing OO systems when compared to procedural systems. With regard to the cost of long-term maintenance, effectively no clear answer may be asserted which accurately conveys the financial savings potential of long-term OO maintenance. The verdict is still out with regard to the naturalness of the language and its reusability.