計算機的應用Computer-based Applications Assignment范文
10-06, 2015
構建基于計算機的應用Building Computer-based Applications Assignment
當今在工業上構建基于計算機應用的主要方法被稱為結構分析與設計。這個方法在1970年代作為一種結構化程序設計技術的成果被映入。這個結構化系統開發方法已經被調整并在世界上應用了數年。但是在過去數年內，面向對象語言正在越來越受到公業機構和大學的歡迎和普及。隨著這個趨勢的持續，一個方法被發展用來幫助那些使用面向對象語言開發應用程序的程序員。
引言 INTRODUCTION
OOAD策略方法的問題從一個對象的視角與功能的角度來看，這是傳統的結構化開發方法的主要焦點。在過去的幾年中越來越多地使用OOAD比傳統的結構化開發方法已經蔓延著。隨著新的和更先進的面向對象的語言被創建，似乎是一個更大的需要一個面向對象的方法來開發業務應用。然而，這是否需要更大的使用這種新的方法比傳統的嗎？我們將比較兩種方法和它們的優點和缺點，以解決這個問題。The existing methodology used primarily in industry today in building computer-based applications is known as structured analysis and design. This methodology came into existence as a result of the structured programming techniques introduced in the 1970's. This structured systems development methodology (SDM) has been fine-tuned and used for many years in the real world. However, during the last several years object-oriented languages have become increasingly more popular and more widely used in industrial organizations as well as university institutions. As this trend continued a methodology was developed to assist the programmer with the development of applications using object-oriented languages. This methodology has become known as object-oriented analysis and design (OOAD).The OOAD strategy approaches the problem from an object perspective as opposed to a functional perspective, which is the primary focus of the traditional structured development methodology. During the last few years the increasing use of OOAD over the traditional structured development methodology has spread significantly. As newer and more sophisticated object-oriented languages are created, there appears to be an even greater need for an object-oriented approach to develop business applications. However, does this need warrant greater use of this new methodology over the traditional one? We will compare the two methodologies and their advantages and disadvantages in order to address this problem.
傳統系統法系與設計 TRADITIONAL SYSTEMS ANALYSIS & DESIGN
The systems development life cycle (SDLC) or the structured systems analysis & design methodology (SSAD) is a framework of activities and tasks that need to be accomplished to develop an information system. This methodology as mentioned previously is called the waterfall model as each major phase of the methodology flows downward into the next phase (Wu and Wu, 1994). Consequently, this methodology is a strategy consisting of various techniques, tools, documentation and tasks that need to be integrated in order to develop the system. The SSAD is based on the concept of functional decomposition where the analyst breaks down the system into the basic processes that make it up and then breaks these down into smaller ones and so on until the analyst understands all the essential components of the system being investigated (Senn, 1989). The basic principles of the SSAD methodology can be summarized as follows:
This methodology requires that the user be involved from the beginning to the end of project development. The analyst will meet with the user regularly to resolve problems and validate the user's needs. This also requires that the analyst possess highly developed communication skills.
The first principle of SSAD is top down functional decomposition. Here the system is considered in its entirety where the analyst first tries to understand the key features of the system, ignoring the smaller details until later.
Next the scope of system is defined where the physical details of the existing system are analyzed. The analyst focuses on two objectives: what the new system should do and how it should do it.
REFERENCES:文獻
Bahrami, A., Object-Oriented Systems Development, Irwin McGraw-Hill, Boston, Massachusetts, 1999.
Rob, M., "Issues of Structured vs. Object-Oriented Methodology of Systems Analysis and Design", Issues in Information Systems, Volume V (1), 2004, 275-280.
Rumbaugh, J., Blaha, M., Premerlani, W., Eddy, F., and Lorensen, W., Object-Oriented Modeling and Design, Prentice-Hall, Englewood Cliffs, New Jersey, 1991.
Satzinger, J., Jackson, R., and Burd, S., Object-Oriented Analysis and Design with the Unified Process, Course Technology, Boston, Massachusetts, 2005.
Senn, J., Analysis and Design of Information Systems, McGraw-Hill, New York, New York, 1989.
Shah, V., Sivitanides, M., Martin, R., "Pitfalls of Object-Oriented Development", Business Quest A Journal of Applied Topics in Business and Economics, November 1997, www.westga.edu.
Shlaer, S., and Mellor, S., Object-Oriented Systems Analysis: Modeling the World in Data. Yourdon Press, Englewood Cliffs, New Jersey, 1988.
Sircar, S., Nerur, S., and Mahapatra, R., "Revolution or Evolution? A Comparison of Object-Oriented and Structured Systems Development Methods ", MIS Quarterly, Vol. 25 (4), 2001, 457-471.
當今在工業上構建基于計算機應用的主要方法被稱為結構分析與設計。這個方法在1970年代作為一種結構化程序設計技術的成果被映入。這個結構化系統開發方法已經被調整并在世界上應用了數年。但是在過去數年內，面向對象語言正在越來越受到公業機構和大學的歡迎和普及。隨著這個趨勢的持續，一個方法被發展用來幫助那些使用面向對象語言開發應用程序的程序員。
引言 INTRODUCTION
OOAD策略方法的問題從一個對象的視角與功能的角度來看，這是傳統的結構化開發方法的主要焦點。在過去的幾年中越來越多地使用OOAD比傳統的結構化開發方法已經蔓延著。隨著新的和更先進的面向對象的語言被創建，似乎是一個更大的需要一個面向對象的方法來開發業務應用。然而，這是否需要更大的使用這種新的方法比傳統的嗎？我們將比較兩種方法和它們的優點和缺點，以解決這個問題。The existing methodology used primarily in industry today in building computer-based applications is known as structured analysis and design. This methodology came into existence as a result of the structured programming techniques introduced in the 1970's. This structured systems development methodology (SDM) has been fine-tuned and used for many years in the real world. However, during the last several years object-oriented languages have become increasingly more popular and more widely used in industrial organizations as well as university institutions. As this trend continued a methodology was developed to assist the programmer with the development of applications using object-oriented languages. This methodology has become known as object-oriented analysis and design (OOAD).The OOAD strategy approaches the problem from an object perspective as opposed to a functional perspective, which is the primary focus of the traditional structured development methodology. During the last few years the increasing use of OOAD over the traditional structured development methodology has spread significantly. As newer and more sophisticated object-oriented languages are created, there appears to be an even greater need for an object-oriented approach to develop business applications. However, does this need warrant greater use of this new methodology over the traditional one? We will compare the two methodologies and their advantages and disadvantages in order to address this problem.
傳統系統法系與設計 TRADITIONAL SYSTEMS ANALYSIS & DESIGN
The systems development life cycle (SDLC) or the structured systems analysis & design methodology (SSAD) is a framework of activities and tasks that need to be accomplished to develop an information system. This methodology as mentioned previously is called the waterfall model as each major phase of the methodology flows downward into the next phase (Wu and Wu, 1994). Consequently, this methodology is a strategy consisting of various techniques, tools, documentation and tasks that need to be integrated in order to develop the system. The SSAD is based on the concept of functional decomposition where the analyst breaks down the system into the basic processes that make it up and then breaks these down into smaller ones and so on until the analyst understands all the essential components of the system being investigated (Senn, 1989). The basic principles of the SSAD methodology can be summarized as follows:
This methodology requires that the user be involved from the beginning to the end of project development. The analyst will meet with the user regularly to resolve problems and validate the user's needs. This also requires that the analyst possess highly developed communication skills.
The first principle of SSAD is top down functional decomposition. Here the system is considered in its entirety where the analyst first tries to understand the key features of the system, ignoring the smaller details until later.
Next the scope of system is defined where the physical details of the existing system are analyzed. The analyst focuses on two objectives: what the new system should do and how it should do it.
REFERENCES:文獻
Bahrami, A., Object-Oriented Systems Development, Irwin McGraw-Hill, Boston, Massachusetts, 1999.
Rob, M., "Issues of Structured vs. Object-Oriented Methodology of Systems Analysis and Design", Issues in Information Systems, Volume V (1), 2004, 275-280.
Rumbaugh, J., Blaha, M., Premerlani, W., Eddy, F., and Lorensen, W., Object-Oriented Modeling and Design, Prentice-Hall, Englewood Cliffs, New Jersey, 1991.
Satzinger, J., Jackson, R., and Burd, S., Object-Oriented Analysis and Design with the Unified Process, Course Technology, Boston, Massachusetts, 2005.
Senn, J., Analysis and Design of Information Systems, McGraw-Hill, New York, New York, 1989.
Shah, V., Sivitanides, M., Martin, R., "Pitfalls of Object-Oriented Development", Business Quest A Journal of Applied Topics in Business and Economics, November 1997, www.westga.edu.
Shlaer, S., and Mellor, S., Object-Oriented Systems Analysis: Modeling the World in Data. Yourdon Press, Englewood Cliffs, New Jersey, 1988.
Sircar, S., Nerur, S., and Mahapatra, R., "Revolution or Evolution? A Comparison of Object-Oriented and Structured Systems Development Methods ", MIS Quarterly, Vol. 25 (4), 2001, 457-471.
如果您有論文代寫需求，可以通過下面的方式聯系我們
點擊聯系客服