||According to Project Management Institute research: over 70% or more software projects fail; 50% of software projects cannot meet customers’ expectations. The American Institute of Electrical and Electronics Engineers also found that cognitive differences caused by uncertain requirement and frequently changing requirement were the two main reasons leading to project’s failure. However, in the initial stages of the software development, requirements elicitation is particularly important to solve cognitive differences. To solve this problem, future wheel, a method of future research methodology, containing the easy accessibility, sustainability, and organized, could be applied in system analysis domain. Therefore, this study by introducing the future wheel as a supplementary tool to create a requirement elicitation process, and through the process to export object-oriented model-use case model. Finally, it evaluates process’ availability and practice’s instructions.|
Individual case study method is adopted and is oriented by the logic of exploring, discovering and inducing. The prepositions, process’ verifications, and adjustment by concluding the references and expert’s suggestions in interview are proposed by this paper.
The contributions of the research include creating the process of using future wheel in requirement elicitation, providing instructions of the process, and combining future wheel with object-oriented model. Besides, this study possibility of future wheel in three different situations: assisting requirement elicitation, model adjustment, project goals setting.
Cockburn, Alistair. (2001). Writing effective use cases: Addison-Wesley Reading.
Davis, Alan M. (1993). Software requirements: objects, functions, and states: Prentice-Hall, Inc.
Eisenhardt, Kathleen M. (1989). Building theories from case study research. Academy of management review, 14(4), 532-550.
Gibbs, W Wayt. (1994). Software’s chronic crisis. Scientific American, 271(3), 72-81.
Glenn, Jerome C. (1994). The futures wheel. Washington, DC: United Nations University.
Glenn, Jerry. (1972). Futurizing Teaching vs. Futures Courses. Social Science Record.
Johnston, S. (2004). Rational UML Profile for business modeling. IBM Developer Works, http://www. ibm. com/developerworks/rational/library/5167. html..
McManus, John, & Wood-Harper. (2003). Information systems project management: Methods, tools and techniques: Pearson Education.
Minichiello, Victor, Aroni, Rosalie, & Hays, Terence. (2008). In-depth interviewing: Principles, techniques, analysis: Pearson Education.
Patton, Michael Quinn. (2005). Qualitative research: Wiley Online Library.
Pilone, Dan, & Pitman, Neil. (2007). UML 2.0 in a Nutshell: O’Reilly Media.
Pimentel, João, Santos, Emanuel, Castro, Jaelson, & Franch, Xavier. (2012). Anticipating Requirements Changes-Using Futurology in Requirements Elicitation. International Journal of Information System Modeling and Design, 3(2), 89-111.
Sommerville, Ian, & Kotonya, Gerald. (1998). Requirements engineering: processes and techniques: John Wiley & Sons, Inc.
Telem, Moshe. (1988). Information requirements specification I: Brainstorming collective decision-making approach. Information processing & management, 24(5), 549-557.
Wagschal, P. (1981). Futuring: A Process for Exploring Detailed Alternative Futures: World Futures Society Bulletin (Futures Research Quarterly).
Wiegers, Karl E. (2009). Software requirements: O’Reilly.
Yin, Robert K. (2002). Case study research: Design and methods: SAGE Publications, Incorporated.