Subscribe
Issue No.04 - July (1995 vol.12)
pp: 19-33
ABSTRACT
Systems analysis is the study of a system for the purpose of understanding and documenting its essential characteristics. Analysis is neither design nor implementation. Analysis focuses on real-world problems, whereas design and implementation focus on computerized solutions. During analysis, you should take care that you don't begin devising solutions like, "How can these naturally parallel activities be done sequentially?" <p> Some critics of object-oriented analysis have concluded that object-oriented analysis as preached and practiced is more preliminary design than pure analysis and offers little real analytical support. In general, we agree with this assessment. We surveyed several of the most popular object-oriented analysis methods and found that many of their features are more appropriate for design than analysis. We believe the presence of such features can corrupt the analysis process by introducing design considerations -- solutions -- before the problem has been fully defined. </p> <p> We have developed a new analysis method -- object-oriented systems analysis -- that focuses exclusively on analysis. We argue that OSA both directly addresses the problems cited by object-oriented analysis critics and offers some interesting new insights into object-oriented analysis. It avoids being a preliminary design method because it specifically omits several design features. </p>
INDEX TERMS
systems analysis, systems modeling, object-oriented analysis, object-oriented analysis models
CITATION
David W. Embley, Scott N. Woodfield, "OO Systems Analysis: Is It or Isn't It?", IEEE Software, vol.12, no. 4, pp. 19-33, July 1995, doi:10.1109/52.391825