OBJECT-ORIENTED SYSTEMS ANALYSIS

The article "OO Systems Analysis: Is It or Isn't It?" is summarized and critiqued. The article is considered within the contexts of (1) summary, (2) major conclusions, (3) significance to systems analysts, (4) major weakness, and (5) critique.

This article identifies problems with the conceptual approach of most systems analysis methods. Once these problems have been identified, the authors of the article company selected major systems analysis methods both with one another and with a new systems analysis model that they propose in this article. The framework for the comparison of the systems analysis methods is the set of problems previously identified with the conceptual approach to systems analysis methods. The authors then describe and discuss a conceptual approach to systems analysis that they propose and then present and discuss a systems analysis model based on this conceptual approach which they have developed. Their model is named the Object-Oriented Systems Analysis Model. Following the presentation of the Object-Oriented Systems Analysis Model, the authors present what they refer to as metamodel of their Object-Oriented Systems Analysis Model. The article closes with a statement of conclusions drawn by the authors with respect to their findings presented in the article.

The first of the major conclusions drawn by the auth

. . .
hat the model will perform well. The authors would have strengthened their arguments about the appropriateness and efficacy of their Object-Oriented Systems Model if they had assessed their model and developed a metamodel from their model through the application of external norms to their model. Had their Object-Oriented Systems Analysis Model fared well when subjected to description and analysis within a framework of external standards, the reader could be expected to have greater confidence in the claims of the authors concerning the appropriateness and efficacy of the Object-Oriented Systems Analysis Model which they presented in the article. Critique of the Article Object-oriented programming has the ability to simplify computer software. Such simplification will, in most instances, enhance the productivity of users. One approach to object-orientation that reduces excessive type system coupling while retaining the benefits of polymorphism is to only inherit type signatures, not implementation code. This is the fundamental principle behind interface-based development, which can be viewed as the second wave of object-orientation. Interface-based programming is a refinement of classical object-orientation. It assumes tha
. . .

Some common words found in the essay are:
Analysis Model, Jackson Woodfield, Summary Article, Article Object-oriented, systems analysis, object-oriented systems, object-oriented systems analysis, Analysis Isn't, systems analysis model, Systems Analyst, analysis model, Object-Oriented Systems, Systems Analysis, Model Essentially, Systems Model, embley jackson woodfield, embley jackson, analysis models, jackson woodfield, systems analysis models, conceptual approach, analysis methods, systems analysis methods, own model, significance article,
Approximate Word count = 1391
Approximate Pages = 6 (250 words per page)

More Essays on OBJECT-ORIENTED SYSTEMS ANALYSIS