The Community for Technology Leaders
Green Image
Issue No. 01 - January/February (2010 vol. 27)
ISSN: 0740-7459
pp: 64-71
Matti Sade , Tel-Aviv University, Tel-Aviv
Roy Gelbard , Bar-Ilan University , Ramat-Gan
Dov Teéeni , Tel-Aviv University, Tel-Aviv
Academic researchers and practitioners frequently describe a situation in which the object-oriented (OO) approach strongly supports the design and coding phases of software development but only weakly supports the analysis phase. Such observations conflict with impressions imparted by textbooks and training programs. This article examines whether object oriented analysis (OOA) theory has been deployed in practice (with or without support of computer-aided software engineering tools) or whether it exists only in theory. This study explores 54 projects, diverse in scope and topic, all of which were implemented using object-oriented tools. The study shows that practitioners haven't widely adopted the theoretically popular OOA and suggests a cost-benefit perspective, arguing that OOA fails to attract practitioners because of a low ratio of costs to benefits relative to other methodologies. In particular, practitioners perceive the cost of system modeling using OOA methodologies and UML diagrams as high relative to its benefits. The authors present of recommendations to reduce costs and increase benefits in OOA.
object oriented analysis, uml, cost-benefit, software, software engineering
Matti Sade, Roy Gelbard, Dov Teéeni, "Object-Oriented Analysis: Is It Just Theory?", IEEE Software, vol. 27, no. , pp. 64-71, January/February 2010, doi:10.1109/MS.2009.151
94 ms
(Ver 3.3 (11022016))