Abstract
The current momentum for object oriented (OO) development in industry makes OO techniques worthy of attention. 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 paper 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, to detailed design, and on to program code for one UP iteration.
DOI
10.17705/1CAIS.01245
Recommended Citation
Satzinger, J., & Jackson, R. (2003). Making the Transition from OO Analysis to OO Design with the Unified Process. Communications of the Association for Information Systems, 12, pp-pp. https://doi.org/10.17705/1CAIS.01245
When commenting on articles, please be friendly, welcoming, respectful and abide by the AIS eLibrary Discussion Thread Code of Conduct posted here.
