June 12, 2005
June 12, 2005
June 15, 2005
10.721.1 - 10.721.22
Implementation of Business policies using object-oriented methodologies and design patterns
Gholam Ali Shaykhian
National Aeronautics and Space Administration (NASA) Bethune Cookman College (NAFP Fellow) Daytona Beach, Florida
Introduction In the early problem-solution era of software programming, functional decompositions were mainly used to design and implement software solution. In functional decompositions, functions and data are introduced as two separate entities during the design phase, and are followed as such in the implementation phase. In general, separation of function and data in a software program causes tight coupling between the two. Tight coupling means that a change in a data may require multiple changes to the design and code through the system. Also, tight coupling of data and function adversely impacts the cost of software maintenance. For example, the year 2000 phenomena (Y2K) broke many software program logics that involved date arithmetic operations (subtracting year portion of the date), processing the year portion of a date produced erroneous results. Conceptually the correction is minimal; “just change the year from two digits to four digits”, however we now know that correcting the date error cost the business communities billions of dollar. The correction included fixing the software so that the year portion of a date is represented as four digits attribute versus two digits programmed earlier. The major cost was due to “tight coupling”; date was tightly coupled with all functions using the date; as such, changing the date required making several changes throughout the software systems.
The reuse of the design artifacts in functional decompositions also lacks transparency; mostly the design artifact incorporates functions needed to solve a software problem at a time. Considering that software life cycles assumed for business problems include problem analysis and design, implementation, testing and verification, deployment and maintenance phases. Where a set of robust practices required within each phase. Often practices within a phase are limited to the availability of tools, technologies and programming languages used for implementation. Software reuse in object-oriented methodologies has proven their superiority over functional decompositions. This has led to exponential growth in object-oriented market.
This paper advocates the usage of object-oriented methodologies and design patterns as the centerpieces of software solution in implementing business policies. The combine usage of object-oriented methodologies and design pattern could facilitate business "Proceedings of the 2005 American Society for Engineering Education Annual Conference & Exposition Copyright © 2005, American Society for Engineering Education”
Shaykhian, G. A. (2005, June), Implementation Of Business Policies Using Object Oriented Methodologies And Design Patterns Paper presented at 2005 Annual Conference, Portland, Oregon. https://peer.asee.org/15059
ASEE holds the copyright on this document. It may be read by the public free of charge. Authors may archive their work on personal websites or in institutional repositories with the following citation: © 2005 American Society for Engineering Education. Other scholars may excerpt or quote from these materials with the same citation. When excerpting or quoting from Conference Proceedings, authors should, in addition to noting the ASEE copyright, list all the original authors and their institutions and name the host city of the conference. - Last updated April 1, 2015