: :() ():P63~80 957 :N9890004

AGORA(attribute value)(Conflict)(Screen Factor)

CMMI-SE/SW /IPPD/SS version 1.1Capability Maturity Model IntegrationCMMI CMM-Level 2repeatable

CMM-Level 3defined

GORAM(Goal-Oriented Requirements Analysis Method)(Priority values)(Cost- values)

(Goal-Oriented Analysis) (Scenario Analysis)

KOASOshirotop-downKaiyaAGORA(Attributed Goal-Oriented Requirements Analysis)

ShinbaraOshiroAGORAAGORA(EAGORA)

AGORAAGORA(goal graph)(contribution value)(preference matrices value)

ARORA 1. Cn(Sub-goal)(PrimaryGoal)-1010 2. Pf-1010(stakeholder) 3. (Rationale)OR

AGORA1. (InitialGoal) 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. (FinalGoal)

AGORA

(EAGORA)AGORA

1Pr010 10 2Co(PreliminaryGoal)

EAGORA

1. AND-(AND-logic) 2. OR-(OR-logic)

EAGORA

4.1.1 (Root node)

2()()

4.1.2

4.1.3

4.1.4 ANDOR

3 AND-emailOR-E-mailE-mail

4.1.5 (CnPfPr)Cn-1010

(Gap)

Pr010 10 E-mail

1

9-60

(satisfiability)

4.1.6

4.1.7 emailE-mailE-mailE-mailE-mailemail

4emailE-mail 10

4.1.8

4emailOR-E-mail+10E-mail

4.1.9

59

4.1.10

SF(Screening Factor)

4.1.11 2,12

5.1

5.2 AGORAAGORA(EAGORA)

5.2.1

5.2.2 3 AGORA12

5.2.3 1. (custumerized)2. (objective)3. (prioritization)

AGORAEAGORA

[1] Ahern, Dennis, Aaron Clouse, Richard Turner (2003), CMMI Distilled, Addison-Wesley, ISBN: 0-321-18613-3. [2] Bourque, Pierre and Dupuis, Robert (2004), Guide to the Software Engineering Body of Knowledge, IEEE Computer Society. [3] Anton, A. and Potts, C. (1998) The use of goals to surface requirements for evolving systems, In Proc. of 20th International Conference on Software Engineering, 157166. [4] Dardenne, A., Van Lamsweerde, A. and Fickas, S. (1993), Goal-directed Requirements Acquisition, Science of Computer Programming, 20, 350. [5] Sutcliffe, A. (1998), Scenario-Based Requirements Analysis, Requirements Engineering, 3, 4865, [6] Rolland, C., Ben Achour, C., Cauvet, C., Ralyte, J., Sutcliffe, A., Maiden, N., Jarke, M., Haumer, P., Pohl, K., Dubois, E., Heymans, P. (1998), A Proposal for a Scenario Classification Framework, Requirements Engineering, 3, 2347.

[7] Leite, J., Hadad, G., Doorn, J., and Kaplan, G. (2000), A Scenario Construction Process, Requirements Engineering, 5, 3861. [8] Yu, Eric, (2004), GRL homepage http://www.cs.toronto.edu/km/GRL/. [9] Oshiro, K.; Watahiki, K., and Saeki, M. (2003), Goal-oriented idea generation method for requirements elicitation, Requirements Engineering Conference, 2003 Proceedings. 11th IEEE International, 8-12. [10] Kaiya, H., Horai, H., and Saeki, M. (2002), AGORA: Attributed Goal-Oriented Requirements Analysis Method, In Proc. of the 10th IEEE International Requirements Engineering Conference (RE02), 1322. [11] Shinbara, D., Kawano, J., Kaiya, H., and Saeki, M. (2004), Identifying Requirements Gaps among Stakeholders by using Goal Oriented Analysis, REFSQ04 Post Workshop Proceedings, Riga, Latvia June, 7 - 11, 219-234. [12] Karlsson, J. and Ryan, K. (1997), A Cost-Value Approach for Prioritizing Requirements, IEEE Software,14(5), 6774.