臺灣博碩士論文加值系統

需求的攫取與分析對所有的軟體系統都是十分重要的步驟，而如何處理需求的本身的不明確性與需求間的衝突一直都是需求工程中一個重要的研究。學者Balzer等就曾強調非正規的需求在軟體設計的過程中無法避免的；Borgida等也進一步的指出一個好的軟體分析方法必須要有能力處理需求中的不明確性與需求間的衝突。
儘管如此，目前的軟體分析方法並沒有辦法妥善的處理此一問題。傳統的正規方法論必須將不明確的需求轉換成精確的描述句才能處理，但此一方法卻會造成對需求描述的失真；另一方面，大部份的非正規的模組方法，如UML、DFD以及OMT等方法都未針對此問題提出解決的方法。在本研究中，我們提出一個目標導向的方法來解決此問題，因為我們認為需求間的衝突來自於使用對系統有不同的目的。學者Robinson 也提出類似的看法；他認為衝突的需求應該在『目標』這個階層考慮。目標導向的精神在於它強調系統設計的原因，藉此提供一個審視軟體系統設計的依據。
本研究的主要目的在提出一套目標導向的方法以助於攫取、分析並管理使用者的不明確需求與需求間的衝突關係。為達到此目的，此研究包含以下的功能：
- 利用截面分析的方式來幫助找出各種不同類型的使用者目標；
- 利用目標擴充使用案例以幫助攫取使用案例；
- 利用使用案例與目標之間的關係分析目標間的關係；
l 結合模糊邏輯與物件導向之概念以模組不明確需求；
l 利用目標之間的關係以組織建構模糊物件導向模組；
l 透過分析衝突的原因以解決需求間的衝突。

Of particular importance for any software system is to elicit and analyze the software requirements. A major challenge in requirements engineering of complex system is that the requirements to be captured are imprecise in nature and usually conflicting with each other. User requirements are often expressed in general and qualitative terms which are vague (imprecise) in nature.
Balzer et al. have argued that informality is an inevitable (and ultimately desirable) feature of the specification process. Borgida et al. have further elaborated that a good requirement modeling approach should take the problem of describing nature kinds into account, which usually runs the risk of being vague and subject to contradiction.
In recent years, goal-based requirements analysis methods have attracted an increasing attention in the area of requirements engineering and trade-off analysis, as goals information are valuable in identifying, organizing and justifying software requirements. Robinson also emphasizes that many inconsistencies originate from conflicting goals, and their management should proceed at the goal level. The tenet of goal-based approaches is focusing on why systems are constructed, which provides the motivation and rationale to justify software requirements.
This research is aimed to develop an goal-driven approach to capturing, analyzing and managing the imprecise or conflicting requirements. Toward these objectives, a goal-driven use cases and fuzzy object-oriented modeling have been developing with the following features:
- Identifying goals based on a faceted classification scheme: competence, view and content. Competence concerns whether a goal is completely satisfied or only to a degree; view concerns whether a goal is actor-specific or system-specific; and content concerns whether a goal is functional and non-functional.
- Extending use cases with goals to guide the derivation of use cases: A faceted classification scheme is proposed to identify goals from domain descriptions and system requirements; and a use case is viewed as a process that can be associated with a goal to be achieved, optimized, maintained, ceased, or impaired by the use case.
- Analyzing the interactions among nonfunctional requirements: Four types of interacions among nonfunctional requirements are identified, which could be either conflicting, cooperative, irrelevant, or counterbalanced.
- Formulating imprecise requirements along four dimensions: (1) to extend a class by grouping objects with similar properties into a fuzzy class, (2) to encapsulate fuzzy rules in a fuzzy class to describe the relationship between attributes, (3) to evaluate the membership function of a fuzzy class by considering both static and dynamic properties, and (4) to model uncertain fuzzy associations between classes.
- Structuring fuzzy object-oriented models based on the interactions analyzed: Goals are organized into several alternatives based on the intracions analyzed to form a goals hierarchy; and a stable kernel is constructed to serve as a basis for further refinement in an increamental fashion.
- Resolving conflicting requirements based on the root of conflicts. The root of conflicts are classified into competing resources, divergent expectations and side effects. we propose three approaches to handling the conflicts: prevention to avoid the occurrence of conflicts, compromise to reach a consensus between conflicting goals, and competition to achieve a goal without regard to another.

封面
ABSTRACT
DEDICATION
ACKNOWLEDGMENTS
TABLE OF CONTENTS
LIST OF FIGURES
LSIT OF TABLES
CHAPTER Ⅰ INTRODUCTION
Ⅰ.A Motivation
Ⅰ.B Organization of the Dissertation
Ⅱ REVIEW OF THE LITERATURE
Ⅱ.A Relate Literature to Requirements Trade-off Analysis Approaches
Ⅱ.B Relate Literature to Goal-Based Requirements Engineering Approaches
Ⅱ.C Relate Literature to Use Cases with Goals
Ⅱ.D Relate Literature to Fuzzy Object-Oriented Modeling
Ⅲ GOAL-DRIVEN USE CASES
Ⅲ.A Overivew of Use Cases
Ⅲ.B Goal-Driven Use Cases
Ⅲ.C Evaluation of Goals
Ⅲ.D Summary
Ⅳ FUZZY OBJECT-ORIENTED MODELING
Ⅳ.A Features of Object Orientation
Ⅳ.B Fuzzy Object-Oriented Modeling
Ⅳ.C Summary
Ⅴ GOAL-DRIVEN REQUIREMENTS SPECIFICATIONS
Ⅴ.A Establishing a Goals Hierarcht
Ⅴ.B Constructing a Stable Kernel
Ⅴ.C Integrating Alternatives
Ⅴ.D Summary
Ⅵ CONCLUSION
Ⅵ.A A Summary of the Research
Ⅵ.B Future Research
REFERENCES
APPENDIX
A A PROBLEM DESCRIPTION OF THE MEETING SCHEDULER SYSTEM
B A NOTE PM STATE MODELING THROUGH INHERITANCE
B.A Basic Concepts
B.B Subclassing vs. Subtyping
B.C Predicting the Dynamic Behavior of Subclasses
B.D Conclusion
C GOAL-DRIVEN USE CASES FOR THE MEETING SCHEDULER SYSTEM
VITA

R.~Darimont A.~van Lamsweerde and E.~Leitier. Managing conflicts in goal-driven requirements engineering. IEEE Transactions on Software Engineering, 24(11):908--926, November 1998.
M.~Ancona. Inheritance and subtyping. In Proceedings of the 1991 Symposium on Applied Computing, pages 382--388, 1991.
A.I. Anton. Goal-based requirements analysis. In Proceedings of the International Conference on Requirements Engineering, pages 136--144, 1996.
R.~Balzer and N.~Goldman. Principles of good software specification and their implications for specification languages. In Proceedings of IEEE Conference on Specifications of Reliable Software, pages 58--67, 1979.
R.~Balzer, N.~Goldman, and D.~Wile. Informality in program specifications. IEEE Transactions on Software Engineering, 4(2):94--103, 1978.
L.A. Belady and C.J. Evangelisti. System partitioning and its measure. Journal of Systems and Software, pages 23--29, 1981.
B.S. Blair. Object-Oriented Languages, Systems, and applications. Pitman, 1991.
G.~Blair. What are object-oriented systems? In G.~Blair et~al, editor, Object-Oriented Languages, Systems and Applications, pages 108--135. Pitman, 1991.
B.~Boehm and H.~In. Identifying quality-requirement conflicts. IEEE Software, 13(2):25--35, March 1996.
G.~Booch. Object-Oriented Analysis and Design with Applications. Benjamin/Cummings Publishing Company Inc., 1994.
G.~Bordogna, D.~Lucarella, and G.~Pasi. A fuzzy object oriented data model. In Proceedings of the Third IEEE Conference on Fuzzy Systems, pages 313--318, 1994.
A.~Borgida, S.~Greenspan, and J.~Mylopoulos. Knowledge representation as the basis for requirements specification. Computer, pages 82--91, April 1985.
C.~Souveyet C.~Rolland and C.B. Achour. Guiding goal modeling using scenarios. IEEE Transactions on Software Engineering, 24(12), December 1998.
C.~Carlsson. On optimization with interpendent multiple criteria. In R.~Lowen and M.~Roubens, editors, Fuzzy Logic: State of the Art, pages 287--300. Kluwer Academic Publishers, Netherlands, 1993.
C.~Carlsson and R.~Fuller. Interdependence in fuzzy multiple objective programming. Fuzzy Sets and Systems, 65:19--29, 1994.
J.M. Carroll. The scenario perspective on system development. In J.M. Carroll, editor, Scenario-Based Design: Envisioning Work and Technology in System Development, pages 1--17. Jone Wiley \& Sons, Inc, 1995.
M.G. Christel and K.C. Kang. Issues in requirements elicitation. Technical Report CMU/SEI-92-TR-012, CMU/SEI, September 1992.
R.G. Clark. Type safety and behavior inheritance. Information and Software Technology, 37(10):539--545, 1995.
P.~Coad and E.~Yourdon. Object-Oriented Analysis. Berlin, Germany: Springer-Verlag, 2nd Edition, 1990.
A.~Cockburn. Goals and use cases. Journal of Object-Oriented Programming, 10(7):35--40, September, 1997.
D.~Coleman, F.~Hayes, and S.~Bear. Introducing objectcharts or how to use statecharts in object-oriented design. IEEE Transactions on Software Engineering, 18(1):9--18, January 1992.