Applying object-oriented analysis on a case study

Three object-oriented analysis techniques: Shlaer & Mellor, Coad & Yourdon, and Document-Driven Analysis were evaluated. Criteria for comparison of analysis techniques were developed. These criteria state that an analysis technique should (1) cover data, transformation, and control perspectives of the problem, (2) address large problems through partitioning, bounding the problem, and supporting prototypes and incremental analysis, (3) provide approaches for verification and validation, and (4) support configuration control. A case study in a software engineering class was conducted using the three OOA techniques. Through the case study we found that (1) identifying objects is affected by notation and flexibility of object models, (2) visualizing global data, transformations, and control are necessary to capture end-user’s processes, (3) emphasizing hierarchical structures and third normal form divert the analyst’s attention from analysis to implementation, (4) an explicit representation of relationships is necessary, (5) peer review is useful in improving selection of objects and methods to support end-user processes, and (6) supporting a standard document from OOA products is not easy.

Download Full-text

Object-Oriented Analysis and Design — A Case Study

Shifting Paradigms in Software Engineering ◽

10.1007/978-3-7091-9258-0_25 ◽

1992 ◽

pp. 223-223

Author(s):

Wolfgang Eder ◽

Gerti Kappel ◽

Jan Overbeck ◽

Michael Schrefl

Keyword(s):

Object Oriented ◽

Analysis And Design ◽

Object Oriented Analysis

Download Full-text

OBJECT-ORIENTED ANALYSIS AS DESIGN: A CASE STUDY

International Journal of Software Engineering and Knowledge Engineering ◽

10.1142/s0218194092000233 ◽

1992 ◽

Vol 02 (04) ◽

pp. 489-521 ◽

Cited By ~ 3

Author(s):

I. A. ZUALKERNAN ◽

W. T. TSAI ◽

A. JEMIE ◽

I. C. WEN ◽

J. M. DRAKE

Keyword(s):

Software Design ◽

State Transition ◽

Explanatory Power ◽

Object Oriented ◽

Design Activity ◽

Consistency Checking ◽

Automated Software ◽

Alternative Theories ◽

Object Oriented Analysis

Object-oriented analysis is the activity of understanding a problem domain and developing a specification for it within an object-oriented paradigm. In this paper we propose object-oriented analysis can be viewed as a design task that consists of analysis, synthesis and internal and external completeness and consistency checking. We postulate a blackboard based design framework and propose several alternative theories within this framework. Data from an expert analyst is collected and analyzed for relative explanatory power of the alternative theories. Basic findings are that viewed as a design activity, object-oriented analysis is neither top-down nor completely opportunistic in nature, Rather, (1) analysis (the process of finding objects and processes) and synthesis (constructing the object model and state-transition diagrams) are complementary activities while internal completeness and consistency checking is coupled with synthesis and (2) construction of objects and processes are cyclic and complementary processes. The findings are compared with both descriptive and normative research in automated software design.

Download Full-text

A Taxonomic Class Modeling Methodology for Object-Oriented Analysis

Information Modeling Methods and Methodologies ◽

10.4018/978-1-59140-375-3.ch011 ◽

2011 ◽

pp. 216-240 ◽

Cited By ~ 7

Author(s):

Il-Yeol Song ◽

Kurt Yano ◽

Juan Trujillo ◽

Sergio Lujan-Mora

Keyword(s):

Object Oriented ◽

Teaching Experience ◽

English Sentence ◽

Requirement Specification ◽

Modeling Methodology ◽

Business Applications ◽

Taxonomic Class ◽

Verb Phrases ◽

Object Oriented Analysis

Discovering a set of domain classes during object-oriented analysis is intellectually challenging and time consuming for novice analyzers. This chapter presents a taxonomic class modeling (TCM) methodology that can be used for object-oriented analysis in business applications. Our methodology helps us discover the three types of classes: (1) classes represented by nouns in the requirement specification, (2) classes whose concepts were represented by verb phrases, and (3) hidden classes that were not explicitly stated in the requirement specification. Our approach synthesizes several different class modeling techniques under one framework. Our framework integrates the noun analysis method, class categories, English sentence structures, checklists, and other heuristic rules for modeling. We illustrate our approach using a detailed case study and summarize the results of several other case studies. Our teaching experience shows that our method is effective in identifying classes for many business applications.

Download Full-text