Goal and scenario based domain requirements analysis environment

Journal of Systems and Software

Volumn 79, Issue 7, 2006, Pages 926-938

  Kim, Jintae ^a   Kim, Minseong ^a   Park, Sooyong ^a  

^a Sogang University   (South Korea)

Author keywords

Domain requirements analysis; Goal; Scenario; Use case

Indexed keywords

COMPUTER AIDED SOFTWARE ENGINEERING; COMPUTER SIMULATION; COMPUTER SOFTWARE; COMPUTER SOFTWARE REUSABILITY; MARKETING; STRATEGIC PLANNING;

DOMAIN REQUIREMENTS ANALYSIS; GOAL; SCENARIO; USE CASE;

REQUIREMENTS ENGINEERING;

EID: 33646801990     PISSN: 01641212     EISSN: None     Source Type: Journal    
DOI: 10.1016/j.jss.2005.06.046     Document Type: Article

References (28)

1. Antón, A.I., 1996. Goal-based requirements analysis. In: Proceedings of the second International Conference on Requirements Engineering, Colorado Springs, CO, pp. 136-144.
2. Bertolino, A., Fantechi, A., Gnesi, S., Lami, G., Maccari, A., 2002. Use case description of requirements for product lines. In: Proceedings REPL'02, pp. 12-18.
3. Chastek, G., et al. 2001. Product line analysis: a practical introduction. Techical report CMU/SEI-2001-TR-001, Software Eng. Inst., Carnegie Mellon University, Pittsburgh.
4. Chastek, G., et al. 2002. Product line production planning for the home integration system example. Techical note CMU/SEI-2002-TN-029, Software Eng. Inst., Carnegie Mellon University, Pittsburgh.
5. Dardenne, A., Fickas, S., van Lamsweerde, A., 1991. Goal-directed concept acquisition in requirements elicitation. In: Proc. IWSSD-6-Sixth Int'l Workshop Software Specification and Design, Como, Italy, pp. 14-21.
6. Geyer, L., Becker, M., 2002. On the Influence of Variabilities on the Application-Engineering Process of a Product Family. In: Chastek, G. (Eds.), Proc. 2nd Software Product Line Conf., LNCS 2379, Heidelberg, Germany, 1-14.
7. Griss, M.L., et al. 1998. Integrating feature modeling with the RSEB. In: Proc. 5th Int. Conf. on Software Reuse (ICSR'98), Victoria, BC, Canada, pp. 76-85.
8. Jacobson I., et al. Software Reuse-Architecture, Process and Organization for Business Success (1997), Addison-Wesley
9. Jacobson I., Booch G., and Rumbaugh J. The Unified Software Development Process (1999), Addison Wesley
10. Jaring, M., Bosch, J., 2002. Representing variability in software product lines: a case study. In: Chastek, G. (Ed.), Proc. 2nd Software Product Line Conf., LNCS 2379, Heidelberg, Germany, pp. 15-36.
11. John, I., Muthig, D., 2002. Tailoring use cases for product line modeling. In: Proceedings REPL'02, pp. 26-32.
12. Kang, K.C., et al. 1990. Feature-oriented domain analysis (FODA) feasibility study. Technical Report, CMU/SEI-90-TR-21, Software Engineering Institute, Carnegie Mellon University, Pittsburgh.
13. Kang K.C., et al. Feature-oriented product line engineering. IEEE Software 9 4 (2002) 58-65
14. Kim J.W., Kim J.T., Park S.Y., and Sugumaran V. A Multi view approach for Requirements analysis using goal and scenario. Ind. Manage. Data Syst. J. 104 9 (2004) 702-711
15. Maßen, T., Lichter, H., 2002. Modeling variability by UML use case diagrams. In: Proceedings REPL'02, pp. 19-25.
16. Myllymäki, T., 2001. Variability management in software product lines. Archimedes Technical report.
17. Nurcan S., Grosz G., and Souveyet C. Describing business processes with a use case driven approach. In: Pernici B., and Thanos C. (Eds). Proc. 10th Int'l Conf. CAiSE '98. Lecture Notes in Computer Science 1413 (1998), Springer, Pisa, Italy
18. Park S.Y., Kim M.S., and Sugumaran V. A scenario, goal and feature oriented domain analysis approach for developing software product lines. Ind. Manage. Data Syst. (IMDS) J. 104 4 (2004) 296-308
19. Plihon, V., Ralyté, J., Benjamen, A., Maiden, N., Sutcliffe, A., Dubois, E., Heymans, P., 1998. A reuse-oriented approach for the construction of scenario based methods. In: Proc. Int'l Software Process Assoc. Fifth Int'l Conf. Software Process (ICSP '98), Chicago, pp. 14-17.
20. Potts, C., 1997. Fitness for use: the system quality that matters most. In: Proc. Third Int'l Workshop Requirements Eng.: Foundations of Software Quality REFSQ '97, Barcelona, pp. 15-28.
21. Potts C., et al. Inquiry-based requirements analysis. IEEE Software 11 2 (1994) 21-32
22. Prat, N., 1997. Goal formalisation and classification for requirements engineering. In: Proc. Third Int'l Workshop Requirements Eng.: Foundations of Software Quality REFSQ '97, Barcelona, pp. 145-156.
23. Rolland C., Achour C., Cauvet C., Ralyté J., Sutcliffe A., Maiden N., Jarke M., Haumer P., Pohl K., Dubois, and Heymans P. A proposal for a scenario classification framework. Requirements Eng. J. 3 1 (1998) 23-47
24. Rolland C., Souveyet C., and Achour C. Guiding goal modeling using scenarios. IEEE Trans. Software Eng. 24 12 (1998) 1055-1071
25. Sommerville I., and Sawyer P. Requirements Engineering: A Good Practice Guide (1997), Wiley
26. Speck, A., Clauss, M., Franczyk, B., 2002. Concerns of variability in bottom-up product-lines. In: Proceedings of the Workshop on Aspect-Oriented Software Development.
27. Sutcliffe A. Scenario based requirement analysis. Requirements Eng. J. (1998) 48-65
28. Vici, A.D., Argentieri, N., 1998. FODAcom: an experience with domain analysis in the Italian telecom industry. In: Proc. 5th Int. Conf. on Software Reuse (ICSR'98), Victoria, BC, Canada, pp. 166-175.