Using object-oriented analysis and design over traditional structured analysis and design

International Journal of Business Research, March, 2008 by Kenneth Pefkaros

Although the OOAD methodology provides many benefits, it does not resolve all the issues associated with the traditional SSAD methodology. There are still some shortcomings and weaknesses that need to be addressed which include: the amount of training needed, the time necessary to learn the new methodology, and the amount of money to invest in it. According to Glass (Glass, 2002) there is no guarantee that the adoption of a new technology will result in it being used effectively and efficiently. In addition, if the organization completely submerges itself in the new OOAD methodology, there can be costly and destructive results. Consequently, to take advantage of all the positive benefits that the new methodology offers, the organization needs to develop a carefully planned and gradual introduction of the methodology to all the system developers.

Before any effort is made to use the OOAD methodology as mentioned previously, it is imperative that the necessary education be provided in order to assure its success. The skills, knowledge and experience of the systems analyst and programmers who are indoctrinated in the traditional SSAD methodology can be enhanced by the new methods. Since changes to the basic structure of the OOAD methodology are stressful to manage, first attempts to use this methodology should be applied only to small scale and non critical applications. This will enable the company to receive immediate feedback and to have time to make any necessary modifications in the application of the OOAD methodology. Consequently, the benefits and advantages gained from using the new OOAD methodology can be much greater and more rewarding for the organization in the long term than using the traditional SSAD methodology (Glass, 2002).

REFERENCES:

Bahrami, A., Object-Oriented Systems Development, Irwin McGraw-Hill, Boston, Massachusetts, 1999.

Bailin, S., Remarks on Object-Oriented Requirements Specification, Computer Technology Associates, Laurel, MD, 1988.

Booch, G., "Object-Oriented Design", Ada Letters Volume 1 (3), 1982, 64-76.

Booch, G., Rumbaugh, J., and Jacobson, I., The Unified Modeling Language User Guide, 2nd ed., Addison-Wesley, Upper Saddle River, New Jersey, 2005.

Booch, G., Maksimchuk, R., Engle, M., Young, B., Conallen, J., Houston, K., Object-Oriented Analysis and Design with Applications, 3rd ed., Addison Wesley, Reading MA, 2007.

Bowman, Kevin, Systems Analysis: A Beginner's Guide, Palgrave Macmillan, Gordonsville, VA. 2004.

Brown, D., An Introduction to Object-Oriented Analysis, Objects and UML in Plain English, John Wiley and Sons, New York, New York, 2002.

Coad, P., and Yourdon, E., Object-Oriented Analysis, 2nd ed., Yourdon Press, Englewood Cliffs, New Jersey, 1991.

Davis, W., Systems Analysis and Design A Structured Approach, Addison-Wesley, Reading, Massachusetts, 1983.

Dennis, A., Wixom, B., and Tegarden, D., Systems Analysis and Design An Object-Oriented Approach with UML, John Wiley & sons, New York, New York, 2002.

Dewitz, S., Systems Analysis and Design and the Transition to Objects, Irwin McGraw-Hill, Boston, Massachusetts, 1996.