近來，觀點導向之軟體發展方法在軟體工程領域引起了相當大的關注。然而，在現階段的研究中，並沒有方法能夠以量化的方式，將早期觀點從盤根錯節的需求描述文件中辨識出來並加以系統性的方析。本論文嘗試研究探討目標、劇情及早期觀點之間的彼此互動關係，並提出一個利用競標程序來進行早期觀點識別的目標驅動軟體工程方法。此競標程序探查了使用案例與目標之間的關係，並利用目標與目標之間的相似度與互相影響度來形成目標叢集，進而幫助系統分析者辨識出早期觀點之所在。藉由將早期觀點引入目標驅動之軟體工程方法，便能於系統發展分析階段時，加以處理盤根錯節的需求陳述問題。本研究包含兩項主要功能：?
(1)以量化的方式進行早期觀點之識別。
? (2)提供一套目標驅動之塑模方法，能夠將早期觀點與被其所影響的系統行為描述於以UML為基礎的需求描述文件中。

Recently, aspect-oriented approaches have resulted in a tremendous impact on the processing of system properties during the development of software systems. However, a quantitative way for eliciting early aspects from requirements is still underdeveloped to better integrate early aspects with the analysis results. As an attempt towards the investigation of the interactions among goals, scenarios, and early aspects, this dissertation proposed a
goal-driven quantitative approach as a continuation of our previous work to the discovery of early aspects by means of a bidding process - a process that explores the interactions among goals, use cases, and early aspects, which engages similarity degrees among goals for grouping goal clusters, interaction degrees for checking the validity of the bidding, and scattering together with tangling degrees for stabilizing the derivation of new goal clusters in the process. By introducing early aspects, the goal-driven approach can be further enhanced
to deal with the crosscutting properties in the analysis stage of software development. The proposed approach is illustrated using the problem domains of meeting scheduler system.

[1] J. Ara´ujo, E. Baniassad, P. Clements, A. Moreira, A. Rashid, and B. Tekinderdo˘gan.
Early aspects: The current landscape. Technical report, Software Engineering Institute,
Carnegie Mellon University, May 2005.
[2] J. Ara´ujo, A. Moreira, I. Brito, and A. Rashid. Aspect-oriented requirements with
uml. In Workshop on Aspect-oriented Modeling with UML, 2002.
[3] J. Ara´ujo, J. Whittle, and D.-K. Kim. Modeling and composing scenario-based requirements
with aspects. In Proceedings of the 12th IEEE international conference on
Requirements Engineering, 2004.
[4] E. Baniassad and S. Clarke. Finding aspects in requirements with theme/doc. In
Workshop on Early Aspects: Aspect-Oriented Requirements Engineering and Architecture
Design, 2004.
[5] E. Baniassad and S. Clarke. Theme: An approach for aspect-oriented analysis and design.
In Proceedings of 26th International Conference on Software Engineering (ICSE),
pages 158–167, 2004.
[6] E. Baniassad, P. C. Clements, J. Ara´ujo, A. Moreira, A. Rashid, and B. Tekinerdo˘gan.
Discovering early aspects. IEEE Software, 23(1):61–70, Jan-Feb 2006.
[7] G. Booch, J. Rumbaugh, and I. Jacobson. The Unified Modeling Language User Guide.
Addision-Wesley, 1999.
[8] N. Boucke and T. Holvoet. State-based join-points: Motivation and requirements. In
Proceedings of the Second Dynamic Aspects Workshop, 2005.
[9] L. Constantine and L. Lockwood. Software For Use. Addison Wesley, 1999.
[10] L. Constantine and L. A. D. Lockwood. Structure and style in use cases for user interfaces.
In M. van Harmelan, ed., Object Modeling an User Interface Design, Addison
Wesley, 2001.
[11] A. Dardenne, A. van Lamsweerde, and S. Fickas. Goal-directed requirements acquisition.
Science of Computer Programming, 20(1-2):3–50, 1993.
[12] M. Deubler, M. Meisinger, S. Rittmann, and I. Kruger. Modeling crosscutting services
with uml sequence diagrams. In Proceedings of IEEE 8th International Conference on
Model Driven Engineering Languages and Systems, 2005.
[13] C. Duan and J. Cleland-Huang. A clustering technique for early detection of dominant
and recessive cross-cutting concerns. In Early Aspects at ICSE: Workshops in Aspect-
Oriented Requirements Engineering and Architecture Design 2007, May 2007.
[14] M. S. Feather, S. Fickas, A. Finkelstein, and A. van Lamsweerde. Requirements
and specifications exemplars. Automated Software Engineering, 4(4):419–438, October
1997.
[15] R. Filman, S. Barrett, D. Lee, and T. Linden. Inserting ilities by controlling communications.
Communications of the ACM, 45(1):116–122, 2002.
[16] R. B. France, D.-K. Kim, S. Ghosh, and E. Song. A uml-based pattern specification
technique. IEEE Transactions on Software Engineering, 30(3), March 2004.
[17] G. Georg, I. Ray, and R. France. Using aspects to design a secure system. In Proceedings
of the 8th IEEE International Conference on Engineering of Complex Computer Systems, 2002.
[18] K.-H. Hsu. Model Architecture with Goals. PhD thesis, National Central University,
Taiwan, 2002.
[19] I. Jacobson. Object-Oriented Software Engineering: A Use Case Driven Approach.
Addison-Wesley, 1992.
[20] I. Jacobson. Use cases and aspects- working seamlessly together. Journal of Object
Technology, 2(4):7–28, July-August 2003.
[21] G. Kiczales, J. Lamping, A. Mendhekar, C. Maeda, C. V. Lopes, J.-M. Loingtier,
and J. Irwin. Aspect-oriented programming. In Proceedings of the 11th European
Conference on Object Oriented Programming (ECOOP’97), 1997.
[22] D.-K. Kim, R. B. France, S. Ghosh, and E. Song. A uml-based metamodeling language
to specify design patterns. In Proceedings of Workshop on Software Model Engineering
(WiSME), at UML 2003, 2003.
[23] J. Lee and Y. Fanjiang. Modeling imprecise requirements with xml. Information and
Software Technology, 45(7), May 2003.
[24] J. Lee and K. Hsu. Modeling software architectures with goals in virtual university
environment. Information and Software Technology, 44:361–380, April 2002.
[25] J. Lee and N. Xue. Analyzing user requirements by use cases: A goal-driven approach.
IEEE Software, 16(4):92–101, July/August 1999.
[26] J. Lee, N. L. Xue, and J.-Y. Kuo. Structuring requirement specifications with goals.
Information and Software Technology, 43:121–135, Feb. 2001.
[27] S. Miller. Aspect-oriented programming takes aim at software complexity. IEEE Computer,
34:18–21, April 2001.
[28] A. Moreira, J. Ara´ujo, and I. Brito. Crosscutting quality attributes for requirements
engineering. In Proceedings of the 14th international conference on Software engineering
and knowledge engineering, 2002.
[29] J. Mylopoulos, L. Chung, and B. Nixon. Representing and using nonfunctional requirements:
A process-oriented approach. IEEE Transactions on Software Engineering,
18(6):483–497, 1992.
[30] N. Noda and T. Kishi. On aspect-oriented design-an approach to designing quality
attributes. In Proceedings of 6th Asia Pacific Software Engineering Conference, pages
230–237, 1999.
[31] A. R. Noorazean Mohd Ali. A state-based join point model for aop. In Workshop on
Views, Aspects and Roles, 2005.
[32] I. Object Management Group. Omg unified modeling language (omg uml), superstructure,
February 2009.
[33] K. Pohl. The three dimensions of requirements engineering: a framework and its
applications. Information Systems, 19(3):243–258, 1994.
[34] A. Popovici, G. Alonso, and T. Gross. Just-in-time aspects: Efficient dynamic weaving
for java. In Proceedings of the 2nd international conference on Aspect-oriented software
development, 2003.
[35] C. Potts, K. Takahashi, and A. Anton. Inquiry-based requirements analysis. IEEE
Software, 11(2):21–32, March 1994.
[36] A. Rashid, A. Moreira, and J. Ara´ujo. Modularisation and composition of aspectual
requirements. In Proceedings of Second Aspect-Oriented Software Development Conference,
pages 11–21, 2003.
[37] A. Rashid, A. Moreira, and B. Tekinerdogan. Early aspects – aspect-oriented requirements
engineering and architecture design. Software, IEE Proceedings, 151(4):153–155,
August 2004.
[38] C. Rolland, C. Souveyet, and C. Achour. Guiding goal modeling using scenarios. IEEE
Transactions on Software Engineering, 24(12):1055–1071, December 1998.
[39] J. Rumbaugh. Getting started: Using use cases to capture requirements. Journal of
Object-Oriented Programming, 7(5):8–12, September 1994.
[40] J. Rumbaugh, I. Jacobson, and G. Booch. The Unified Modeling Language Reference
Manual. Addision-Wesley, 2004.
[41] A. Sampaio, R. Chitchyan, A. Rashid, and P. Rayson. Ea-miner: a tool for automating
aspect-oriented requirements identification. In Proceedings of the 20th IEEE/ACM
international Conference on Automated software engineering, pages 352–355, 2005.
[42] A. Sampaio, A. Rashid, and P. Rayson. Early-aim: An approach for identifying aspects
in requirements. In Proceedings of the 2005 13th IEEE International Conference on
Requirements Engineering, pages 487–488, 2005.
[43] T. L. Satty. Analytic Hierarchy Process. McGraw-Hill International, New York, 1980.
[44] M. Shomrat and A. Yehudai. Obvious or not? regulating architectural decisions using
aspect-oriented programming. In Proceedings of 1st International Conference on
Aspect-Oriented Software Development, pages 3–9, April 2002.
[45] J. Sillito, C. Dutchyn, A. D. Eisenberg, and K. D. Volder. Use case level pointcuts. In
Proceedings of European Conference on Object-Oriented Programming, 2004.
[46] G. Sousa, S. Soares, P. Borba, and J. Castro. Separation of crosscutting concerns from
requirements to design: Adapting an use case driven approach. In Proceedings of Early
Aspects Workshop at AOSD, 2004.
[47] D. Stein, S. Hanenberg, and R. Unland. Designing aspect-oriented crosscutting in uml.
In AOSD-UML workshop at AOSD’02, 2002.
[48] D. Stein, S. Hanenberg, and R. Unland. On representing join points in the uml. In
Aspect Modeling with UML workshop at the Fifth International Conference on the
Unified Modeling Language and its Applications, 2002.
[49] A. van Lamsweerde, R. Darimont, and E. Leitier. Managing conflicts in goal-driven
requirements engineering. IEEE Transactions on Software Engineering, 24(11):908–
926, November 1998.
[50] J. Viega and J. Voas. Can aspect-oriented programming lead to more reliable software?
IEEE Software, 17:19–21, November-December 2000.
[51] J. Whittle and J. Ara´ujo. Scenario modelling with aspects. IEE Software, 151(4):157–
172, August 2004.
[52] Y. Yu, J. C. S. do Prado Leite, and J. Mylopoulos. From goals to aspects: Discovering aspects from requirements goal models. In Proceedings of the 12th IEEE International
Requirements Engineering Conference, pages 38–47, 2004.