A scenario, goal and feature-oriented domain analysis approach for developing software product lines

Industrial Management and Data Systems

Volumn 104, Issue 3, 2004, Pages 296-308

  Park, Sooyong ^a   Kim, Minseong ^a   Sugumaran, Vijayan ^b  

^a Sogang University   (South Korea)

^b OAKLAND UNIVERSITY   (United States)

Author keywords

Computer software; Manufacturing resource planning; Product management

Indexed keywords

COMPUTER SOFTWARE; ENTERPRISE RESOURCE PLANNING; MATHEMATICAL MODELS; PRODUCT DEVELOPMENT; QUALITY CONTROL; SOCIETIES AND INSTITUTIONS; COMPUTER SIMULATION; FEATURE EXTRACTION; INTEGRATION; MANUFACTURE; RESOURCE ALLOCATION; VARIATIONAL TECHNIQUES;

DOMAIN REQUIREMENTS MODELS (DRM); MANUFACTURING RESOURCE PLANNING; SOFTWARE PRODUCT LINES (SPL); SOFTWARE REUSE;

SOFTWARE ENGINEERING; PRODUCT DEVELOPMENT;

COMMONALITY AND VARIABILITY; HOME INTEGRATION SYSTEM; MANUFACTURING RESOURCE PLANNING; PRODUCT MANAGEMENT;

EID: 3242714778     PISSN: 02635577     EISSN: None     Source Type: Journal    
DOI: 10.1108/02635570410530711     Document Type: Article

References (35)

1. Antón, A.I. (1996), "Goal-based requirements analysis", Proceedings of the Second International Conference on Requirements Engineering, Colorado Springs, CO, pp. 136-44.
2. Bosch, J. (2000), Design and Use of Software Architectures: Adopting and Evolving a Product-line Approach, Addison-Wesley, Boston, MA.
3. Chandrasekaran, B. and Kaindl, H. (1996), "Representing functional requirements and user-system interactions", Proceedings of AAAI-96 Workshop on Modeling and Reasoning about Function, Portland, OR.
4. Chastek, G., Donohoe, P. and McGregor, J.D. (2002), Product Line Production Planning for the Home Integration System Example, Technical Note CMU/SEI-2002-TN-029, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA.
5. Chastek, G., Donohoe, P., Kang, K.C. and Thiel, S. (2001), Product Line Analysis: A Practical Introduction, Technical Report CMU/SEI-2001-TR-001, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA..
6. Clements, P. and Northrop, L. (2001), Software Product Lines: Practices and Patterns, Addison Wesley Longman, Reading, MA.
7. Dardenne, A., Lamsweerde, A.V. and Fickas, S. (1993), "Goal-directed requirements acquisition", Science of Computer Programming, Vol. 20 No. 1/2, pp. 3-50.
8. Donohoe, P. (Ed.) (2000), Software Product Lines: Experience and Research Directions, Kluwer Academic Publishers, Boston, MA.
9. Fey, D., Fajta, R. and Boros, A. (2002), "Feature modeling: a meta-model to enhance usability and usefulness", in Chastek, G. (Ed.), Proceedings of the Second Software Product Line Conference, Springer Verlag, Berlin, pp. 198-216.
10. Gong, B., Yen, D.C. and Chou, D.C. (1998), "A manager's guide to total quality software design", Industrial Management & Data Systems, Vol. 98 No. 3, pp. 100-7.
11. Griss, M.L., Favaro, J. and d'Alessandro, M. (1998), "Integrating feature modeling with the RSEB", Proceedings of the 5th International Conference on Software Reuse, Victoria, BC, pp. 76-85.
12. Jacobs, S. and Holten, R. (1995), "Goal-driven business modelling - supporting decision making within information systems development", Proceedings of Conference On Organizational Computing Systems, Milpitas, CA, pp. 96-105.
13. Jacobson, I., Griss, M.L. and Jonsson, P. (1997), Software Reuse: Architecture, Process and Organization for Business Success, Addison-Wesley Publishing, New York, NY.
14. Kaindl, H. (1995), "An integration of scenarios with their purposes in task modeling", Proceedings of Symposium Designing Interactive Systems: Processes, Practices, Methods, and Techniques, ACM Press, New York, NY, pp. 227-35.
15. Kaindl, H. (2000), "A design process based on a model combining scenarios with goals and functions", IEEE Transactions on Systems, Vol. 30 No. 5, pp. 537-51.
16. Kang, K.C., Lee, J. and Donohoe, P. (2002), "Feature-oriented product line engineering", IEEE Software, Vol. 9 No. 4, pp. 58-65.
17. Kang, K.C., Lee, K. and Lee, J. (2003), "Feature oriented product line software engineering: principles and guidelines", Domain Oriented Systems Development: Practices and Perspectives, Taylor & Francis, London, pp. 19-36.
18. Kang, K.C., Cohen, S.G., Hess, J.A., Novak, W.E. and Peterson, A.S. (1990), Feature-oriented Domain Analysis Feasibility Study, Technical Report CMU/SEI-90-TR-21, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA.
19. Kang, K.C., Kim, S., Lee, J., Kim, K., Shin, E. and Huh, M. (1998), "FORM: a feature-oriented reuse method with domain-specific reference architectures", Annals of Software Engineering, Vol. 5, pp. 143-68.
20. Lamsweerde, A.D. and Willemet, L. (1998), "Inferring declarative requirements specification from operational scenarios", IEEE Transactions on Software Engineering, Vol. 24 No. 12, pp. 1089-114.
21. Lee, K., Kang, K.C., Kim, S. and Lee, J. (1999), "Feature-oriented engineering of PBX software for adaptability and reusability", Software-Practice and Experience, Vol. 29 No. 10, pp. 875-96.
22. Li, L. (2002), "Western exporting manufacturers' channel structure in emerging markets", Industrial Management & Data Systems, Vol. 102 No. 9, pp. 483-92.
23. Mylopoulos, J., Chung, L. and Nixon, B. (1992), "Representing and using non-functional requirements: a process-oriented approach", IEEE Transactions on Software Engineering, Vol. 18 No. 6, pp. 483-97.
24. Mylopoulos, J., Chung, L. and Yu, E. (1999), "From object-oriented to goal-oriented requirements analysis", Communications of the ACM, Vol. 42 No. 1, pp. 31-7.
25. Neighbors, J. (1981), "Software construction using components", PhD thesis. Department of Information and Computer Science, University of California, Irvine, CA.
26. Potts, C., Takahashi, K. and Antón, A.I. (1994), "Inquiry-based requirements analysis", IEEE Software, Vol. 11 No. 2, pp. 21-32.
27. Rolland, C., Grosz, G. and Kla, R. (1999), "Experience with goal-scenario coupling in requirements engineering", paper presented at The 4th IEEE International Symposium on Requirements Engineering.
28. Rolland, C., Souveyet, C. and Achour, C.B. (1998), "Guiding goal modeling using scenarios", IEEE Transactions on Software Engineering, Vol. 24, pp. 1055-71.
29. Steinke, G. and Nickolette, C. (2003), "Business rules as the basis of an organization's information systems", Industrial Management & Data Systems, Vol. 98 No. 3, pp. 52-63.
30. Sutcliffe, A.G. (1998), "Scenario-based requirement analysis", Requirements Engineering Journal, Vol. 3 No. 1, pp. 48-65.
31. Thiel, S. and Peruzzi, F. (2000), "Starting a product line approach for an envisioned market: research and experience in an industrial environment", Proceedings of the First Software Product Line Conference, Kluwer Academic Publishers, Boston, MA, pp. 495-512.
32. Vici, A.D. and Argentieri, N. (1998), "FODAcom: an experience with domain analysis in the Italian telecom industry", Proceedings of the 5th International Conference on Software Reuse, Victoria, BC, Canada, pp. 166-75.
33. Wiegers, K.E. (1999), Software Requirements, Microsoft Press, Redmond, WA.
34. Yang, H.L. and Tang, J.H. (2003), "A three-stage model of requirements elicitation for Web-based information systems", Industrial Management & Data Systems, Vol. 103 No. 6, pp. 398-409.
35. Yang, Y.H. (2001), "Software quality management and ISO 9000 implementation", Industrial Management & Data Systems, Vol. 101 No. 7, pp. 329-38.