MAKING THE TRANSITION FROM OO ANALYSIS TO OO DESIGN WITH THE UNIFIED PROCESS

1Citations
Citations of this article
16Readers
Mendeley users who have this article in their library.

Abstract

The current momentum for OO development in industry makes OO techniques worthy of considerable attention. Consequently, information systems researchers and practitioners are increasingly using constructs such as use cases and class diagrams to define system requirements. A glaring weakness in the literature is the lack of useful guidelines and strategies for taking a relatively high level OO requirements model and translating it into an implementable architecture and detailed OO design. This tutorial demonstrates techniques for bridging the gap between OO requirements models and detailed OO design, drawing on the framework provided by the Unified Process (UP) and based on concepts and techniques developed by researchers working on OO design patterns. The examples provided illustrate the transition from requirements, to architecture, and to detailed design.

Cite

CITATION STYLE

APA

Satzinger, J. W., & Jackson, R. B. (2003). MAKING THE TRANSITION FROM OO ANALYSIS TO OO DESIGN WITH THE UNIFIED PROCESS. In 9th Americas Conference on Information Systems, AMCIS 2003 (pp. 3200–3210). Association for Information Systems. https://doi.org/10.17705/1cais.01245

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free