利用設計樣式開發可重複使用之會計系統

以作者查詢圖書館館藏

、以作者查詢臺灣博碩士

、以作者查詢全國書目

、勘誤回報

、線上人數：64

、訪客IP：3.15.1.100

姓名

張宴良(Y-L Chang ) 查詢紙本館藏

畢業系所

資訊工程研究所

論文名稱

利用設計樣式開發可重複使用之會計系統
(Developing Reusable Accounting System using Design Patterns)

相關論文

★ 應用J2ME技術建立無線企業應用程式	★ 以XML為基礎的企業應用程式架構
★ 異質應用程式間的資料同步	★ 在J2EE架構下發展Web應用程式

檔案

[Endnote RIS 格式]

[Bibtex 格式]

[相關文章]

[文章引用]

[完整記錄]

[館藏目錄]

[檢視]

[下載]

本電子論文使用權限為同意立即開放。
已達開放權限電子全文僅授權使用者為學術研究之目的，進行個人非營利性質之檢索、閱讀、列印。
請遵守中華民國著作權法之相關規定，切勿任意重製、散佈、改作、轉貼、播送，以免觸法。

摘要(中)

企業的資訊化在近幾年來愈來愈普及，為了提昇企業本身的競爭力，一套合適的軟體系統就顯得格外重要，雖然企業資訊系統(Business System)已經被應用到企業很長一段時間，然而，面對今日快速變更的企業環境，大多數的系統已經無法滿足公司本身的需求，一旦企業的需求隨著環境而改變時，這些系統將變得不再適用。再者，站在企業的觀點來看，決不希望每當需求一變更，就必須投入大量的人力、物力來開發新系統，因此，如果能讓既有的軟體系統簡單地就可以擴充其功能，並且可以透過重複使用(Reuse)來滿足企業需求，會是一個較好的方法。
所以在本論文中，我們希望開發一套可重複使用的會計系統，並且透過可重複使用的元件(Reusable Component)來建構整個系統。對軟體系統而言，雖然部分的元件可以被直接重複使用，然而，大部分的元件卻必須先經過特殊化(Specialization)才能滿足使用者的需求，因此，我們必須在系統當中先定義這些可變動元件(Variable Component)的變更性(Variability)。為此，設計者會在這些元件上先找出變更點(Variation Point)，可能的話，對於每個變更點也會預先提供一些可能的變化(Variant)。
為了開發這個可重複使用的會計系統，我們會在系統中提出幾個變更點以及對應的變化，並介紹一些設計樣式(Design Pattern)來實作這些變更點，最後，我們可以透過在系統所提供的變更點之上附加(Attach)一些變化，來訂製(Customize)一個符合需求的會計系統。

摘要(英)

The globalization of business is more and more popular in last few years. To keep up and remain competitive, a suitable business system can achieve this objective to a certain degree. While business systems have been used in enterprise for several decades, most existing business systems have difficulty in dealing with today's rapidly changing business environment. As long as business requirements change, these systems will become inapplicable immediately. Furthermore, businesses will not develop a new business system from scratch to meet their requirements continually. Therefore, A better way is to make existing business systems can be easily extended and reused in order to effectively reflect specific business needs.
We try to improve the reusability of our accounting system through building system from reusable components. Notably, some components may be used directly in a software system, whereas most components must be specialized prior to reuse. Developers have to identify the variability on these variable components. For this purpose, we could find the variation points on each component to define their variability. If possible, some variants are also given corresponding to each variation point.
In order to develop a reusable accounting system, we will identify several variation points with some variants in this system, and introduce some useful design patterns for implementing these variation points. Consequently, we can customize an accounting system just through attaching variants on corresponding variation point in our system.

關鍵字(中)

★ 會計系統
★ 統一模式化語言
★ 設計樣式
★ 軟體重用

關鍵字(英)

★ Accounting System
★ Design Pattern
★ Software Reuse
★ UML

論文目次

Chapter 1 Introduction . . . . . . . . . . . . . 1
1.1 Motivation . . . . . . . . . . . . . . . . . 1
1.2 UML . . . . . . . . . . . . . . . . . . . . . 2
1.3 Thesis structure . . . . . . . . . . . . . . 4
Chapter 2 Related work . . . . . . . . . . . . . 5
2.1 Design pattern . . . . . . . . . . . . . . . 5
2.2 Software reuse . . . . . . . . . . . . . . . 6
2.3 Accounting cycle . . . . . . . . . . . . . 10
Chapter 3 Problem description . . . . . . . . . 13
3.1 General requirement . . . . . . . . . . . . 13
3.2 Variation part . . . . . . . . . . . . . . . 15
3.2.1 Journalize policy . . . . . . . . . . . . 17
3.2.2 Posting policy . . . . . . . . . . . . . . 19
3.2.3 Reporting strategy . . . . . . . . . . . . 19
3.2.4 General ledger account . . . . . . . . . . 19
3.2.5 GL journal (header and line item) . . . . 20
3.2.6 Presentation . . . . . . . . . . . . . . . 21
Chapter 4 Some design patterns for variation . . 22
4.1 Property container . . . . . . . . . . . . . 22
4.2 Strategy . . . . . . . . . . . . . . . . . . 24
4.3 Decorator . . . . . . . . . . . . . . . . . 25
4.4 Command . . . . . . . . . . . . . . . . . . 26
4.5 MVC . . . . . . . . . . . . . . . . . . . . 28
Chapter 5 Applications . . . . . . . . . . . . . 30
5.1 A component system . . . . . . . . . . . . 30
5.1.1 Add general ledger account . . . . . . . . 33
5.1.2 Journalize and post . . . . . . . . . . . 35
5.1.3 Display financial statement . . . . . . . 39
5.2 Application systems . . . . . . . . . . . . 41
5.2.1 Application for Taiwan subsidiary . . . . 42
5.2.2 Application for US subsidiary . . . . . . 43
Chapter 6 Implementation . . . . . . . . . . . . 45
6.1 Problem statement . . . . . . . . . . . . . 45
6.2 System architecture . . . . . . . . . . . . 46
6.3 Environment . . . . . . . . . . . . . . . . 47
6.4 Illustration . . . . . . . . . . . . . . . . 47
Chapter 7 Conclusion and future work . . . . . 55
References . . . . . . . . . . . . . . . . . . . 57

參考文獻

[Appl97]Apple, WebObjects Online Documentation,
http://www.apple.com/webobjects/, 1997.
[Appl00]B. Appleton, “Patterns and Software: Essential Concepts and Terminology,” http://www.enteract.com/~bradapp/, 2000.
[Barn99]R. Barnett, T. Neple, J. Hassall, “Developing a Global Standard for Interoperable Accounting System,” IEEE, 1999.
[Blai98]J. Blain, B. Dodd, D. Sandison, Administering SAP R/3: The FI-Financial Accounting and CO-Controlling Modules, Macmillan Computer Publishing, 1998.
[Bidd98]R. L. Biddle, E. D. Tempero, “Inheritance and Reusability,” IEEE Software Engineering Conference, pp.184 - 191, 1998.
[Booc96]J. L. Boockholdt, Accounting Information System: transaction processing and controls, Times Mirror Books, 1996.
[Booc99]G. Booch, J. Rumbaugh, I. Jacobson, The Unified Modeling Language User Guide, Addison-Wesley, 1999.
[Busc96]F. Buschmann, R. Meunier, H. Rohnert, P. Sommerlad, M. Stal, Pattern-Oriented Software Architecture: A System of Patterns, John Wiley & Sons, New York, 1996.
[Care00]J. Carey, B. Carlson, T Graser, SanFrancisco Design Patterns, Addison Wesley, 2000.
[Copl95]J.O. Coplien, D.C. Schmidt, Pattern Languages of Program Design, Addison-Wesley, 1995.
[Dage96]P. Dagermo, J. Knutsson, “Development of an Object-Oriented Framework for Vessel Control System,” Technical Report, 1996.
[Erik00]H.E. Eriksson, and M. Penker, Business Modeling with UML: Business Patterns at Work, John Wiley & Sons, Inc, 2000.
[Evit00]P. Evitts, A UML Pattern Language, MTP, 2000.
[Fowl00]M. Fowler, K. Scott, UML Distilled 2nd Edition: A Brief Guide to the Standard Object Modeling Language, Addison-Wesley, 2000.
[Gamm95]E. Gamma, R. Helm, R. Johnson, and J. Vlissides, Design Patterns: Elements of reusable object-oriented software, Addison Wesley, 1995.
[Ibm99]IBM, “SanFrancisco Concepts and Facilities,” http://www.software.ibm.com/ad/sanfrancisco/, 1999.
[Inco90]A. J. Incorvaia, A. M. Davis, “Case Studies in Software Reuse,” IEEE Computer Software and Applications Conference, pp.301 —306, 1990.
[Jaco94]I. Jacobson, M. Christerson, P. Jonsson, G. Overgaard, Object-Oriented Software Engineering: A Use Case Driven Approach, Addison-Wesley, 1994.
[Jaco97]I. Jacobson, M. Griss, P. Jonsson, Software Reuse: Architecture Process and Organization for Business Success, Addison-Wesley, 1997.
[John92]R. Johnson, “Documenting Frameworks using Patterns,” OOPSLA ’92 Proceedings, pp.63-76, Vancouver, Oct. 1992.
[John95]R. E. Johnson, “Transactions and Accounts,” in Pattern Languages of Program Design 2 Proceedings, pp.239-254, 1995.
[Kruc95]P. Kruchten, “Architectural Blueprints — The 4+1 View Model of Software Architecture,” IEEE Software, pp. 42-50, Nov. 1995.
[Kruc99]P. Kruchten, The Rational Unified Process: An Introduction, Addison-Wesley, 1999.
[Larm98]C. Larman, Applying UML and Patterns: An Introduction to Object- Oriented Analysis and Design, Prentice Hall, 1998.
[Lea00]D. Lea, “Patterns - Discussion FAQ,” http://g.oswego.edu/dl/pd-FAQ/pd-FAQ.html, 2000.
[Mond00]P. Monday, M. Dangler, J. Carey, SanFrancisco Component Framework: an introduction, Addison-Wesley, 2000.
[Nobl98]J. Noble, “Towards a Pattern Language for Object Oriented Design,” IEEE Technology of Object-Oriented Languages, pp.2 — 13, 1998.
[Omg97]Object Management Group, “What Is OMG-UML and Why Is It Important?,” http://cgi.omg.org/news/pr97/umlprimer.html, 1997.
[Quat00]T. Quatrani, Visual Modeling with Rational Rose 2000 and UML, Addison-Wesley, 2000.
[Rati97]Rational, and UML partners, “UML Notation Guide version 1.1,” http://www.rational.com/uml/, 1997.
[Robe97]D. Roberts, R. Johnson, “Patterns for Evolving Frameworks,” in Pattern Languages of Program Design 3 Proceedings, pp.471-486, 1997.
[Rose99]D. Rosenberg, K. Scott, Use Case Driven Object Modeling with UML: a practical approach, Addison-Wesley, 1999.
[Rumb91]J. Rumbaugh, M. Blaha, W. Premerlani, F. Eddy, W. Lorenzen, Object-Oriented Modeling and Design, Prentice Hall, 1991.
[Rumb99]J. Rumbaugh, I. Jacobson, G. Booch, The Unified Modeling Language Reference Manual, Addison-Wesley, 1999.
[Schm96]D.C. Schmidt, “Using Design Patterns to Develop Reusable Object-Oriented Software,” Communications of the ACM, Dec. 1996.
[Sun01]Sun Java Center, “J2EE Patterns,”
http://developer.java.sun.com/developer/technicalArticles/J2EE/patterns/, 2001.
[Trau98]R. Trauter, “Design-Related Reuse Problems: An Experience Report,” IEEE Software Reuse, pp.176 - 183, 1998.
[Tsai99]W. T. Tsai, Y. Tu, W. Shao, E. Ebner, “Testing Extensible Design Patterns in Object-Oriented Frameworks through Scenario Template,” IEEE,1999.
[Yasi94]A. A. Yasiri, M. Ramachandran, “Developing Software Systems with Domain Oriented Reuse,” IEEE, 1994.
[Zimm95]W. Zimmer, “Relationships between design patterns,” in Pattern Languages of Program Design Proceedings, pp.345-364, 1995.

指導教授

黃為德(Wei-T. Huang)

審核日期

2001-7-3

推文