成功大學博碩士論文系統

簡易檢索 / 詳目顯示

回結果列表

研究生：	蔡曜旭 Tsai, Yiau-Syu
論文名稱：	劇本架構:一個建構物件導向軟體系統之整體觀點之方法論 Scenario Architecture – A Methodology to Build a Global View of OO Software System
指導教授：	焦惠津 Jiau, Hewi-jin
學位類別：	碩士 Master
系所名稱：	電機資訊學院 - 電機工程學系 Department of Electrical Engineering
論文出版年：	2003
畢業學年度：	91
語文別：	英文
論文頁數：	73
外文關鍵詞：	imperative software engineering, architecture, object-oriented software engineering
相關次數：	點閱：75 下載：2
分享至:	分享至facebook 分享至twitter

查詢本校圖書館目錄查詢臺灣博碩士論文知識加值系統勘誤回報

OO software engineering has been a well-known software engineering methodology for years; however, there are still some issues remaining unsolved: the engineers using imperative software engineering have a large gap to stride across when adopting OO software engineering; the software may have some problems resulting from process issue; and a generic mechanism for checking consistency of designs is still lacking. A new methodology is represented to provide a complete global view of OO software system, which solves issues that are identified. It uses requirements document and some analysis documents as foundation because these three issues intersect in the early analysis phase. Three case studies are also represented to exemplify the result of applying the proposed methodology on both OO software engineering and imperative software engineering.

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  1
1 Consistency Checking . . . . . . . . . . . . . . . . . . . . . . . . . . .  2
2 Process Issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3 The Gap Between Imperative Software Engineering and OO Software Engineering 4
4 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Related Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  6
1 AUML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  6
2 Use Case Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3 Flow Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  8
Notation and Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1 Level 1. Overall Scenarios . . . . . . . . . . . . . . . . . . . . . . . . 10
2 Level 2. Interactions Between Use Cases . . . . . . . . . . . . . . . . .  11
3 Level3. Internal Use Case Process . . . . . . . . . . . . . . . . . . . .  12
Methods to Apply Scenario Architecture . . . . . . . . . . . . . . . . . . . 15
1 Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
2 Applying Scenario Architecture to Object-Oriented Software Engineering . . 17
3 Applying Scenario Architecture to Imperative Software Engineering . . . .  20
Case Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
1 Elevator System . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  24
1.1 Use Case Descriptions of Elevator Control System . . . . . . . . . . . . 25
1.2 Scenarios of the Elevator System . . . . . . . . . . . . . . . . . . . . 27
1.3 Level1 Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
1.4 Level2 Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . .  29
1.5 Level3 Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . .  29
2 Banking System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2.1 Scenarios of the Banking System . . . . . . . . . . . . . . . . . . . .  34
2.2 Level1 Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2.3 Level2 Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . .  37
2.4 Level3 Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . .  38
3 Tester . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.1 Scenarios of Tester . . . . . . . . . . . . . . . . . . . . . . . . . .  44
3.2 Step1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  46
3.3 Step2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  46
3.4 Step3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  48
Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
1 Initializing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
2 Drawing Level1 Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3 Drawing Level2 Diagrams . . . . . . . . . . . . . . . . . . . . . . . . .  60
4 Drawing Level3 Diagrams . . . . . . . . . . . . . . . . . . . . . . . . .  61
5 Opening And Saving Projects . . . . . . . . . . . . . . . . . . . . . . .  62
6 Checking Consistency of Scenario Architecture Diagrams . . . . . . . . . . 64
After Applying Scenario Architecture . . . . . . . . . . . . . . . . . . . . 65
1 Class Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  65
2 Sequence Diagram and Collaboration Diagram . . . . . . . . . . . . . . . . 66
3 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  67
Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
1 Future Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
                                    

[1] R. W. Sebesta, Concept of Programming Language. Addison-Wesley, 1999.
[2] G. B. Shelly, T. J. Cashman, and H. J. Rosenblatt, System Analysis and Design. Course Technology, 2001.
[3] S. R. Schach, Classical and Object-Oriented Software Engineering With UML and
Java. McGraw- Hill, 1999.
[4] T. C. Lethbridge and R. Laganiere, Objected-Oriented Software Engineering - Practical software development using UML and Java. McGraw- Hill, 2001.
[5] E. J. Braude, Software Engineering - An Object-Oriented Perspective. John Wiley and Sons, Inc., 2001.
[6] Agent UML. URL http://www.auml.org.
[7] R. J. A. Buhr, “Use Case Maps As Architectural Entities For Complex System,” IEEE Transaction on Software Engineering, vol. 24, no. 12, pp. 1131–1155, Dec. 1998.
[8] J. Mylopoulos and J. Castro, “Tropos: A Framework for Requirements-Driven Software Development,” Information Systems Engineering: State of the Art and Research Themes, pp. 261–273, Jun. 2000.
[9] G. Booch, J. Rumbaugh, and I. Jacobson, The Unified Modeling Language User
Guide. Addison-Wesley, 1999.
[10] H. C. Jiau and Y. E. Tsai, “Scenario Architecture in Object-Oriented Software Engineering,” 13th Workshop on Object-Oriented Technology and Applications, Dec. 2002.
[11] J. Odell, H. V. D. Parunak, and B. Bauer, “Extending UML for Agents,” Proceeding of the Agent-Oriented Information Systems Workshop at the 17th National conference on Artificial Intelligence, pp. 3–17, 2000.
[12] J. L. Whitten and L. D. Bentley, System Analysis and Design Methods. McGraw-
Hill, 1998.
[13] A. Dardenne, A. van Lamsweerde, and S. Fickas, “Goal-Directed Requirements Acquisition,”Science of Computer Programming, vol. 20, no. 1-2, pp. 3–50, Apr. 1993.
[14] R. S. Wahono and B. H. Far, “A framework for object identification and refinement process in OO analysis and design,” Proceedings of the First IEEE International Conference on Cognitive informatics, pp. 351–360, Aug. 2002.
[15] H. Gomma, Designing Concurrent, Distributed, and Real-Time Applications with
UML. Addison-Wesley, 2000.
[16] H. C. Jiau and J. C. Chen, “A Unified Testing and Development Framework for
Component Reuse,” Proceedings of 2002 Symposium on Digital Life and Internet
Technologies, 2002.
[17] Java. URL http://java.sun.com.
[18] C. Philippe and T. F. Pascale, “Automated Generation of Statistical Test Cases from UML State Diagrams,” 25th Annual International Computer Software and Applications Conference (COMPSAC’01), pp. 205–214, Oct. 2001.
[19] Extreme Programming. URL http://www.extremeprogramming.org/index.html.

校內：立即公開
校外：2003-07-11公開

簡易檢索 / 詳目顯示

相關論文