Understanding the role of inferential reasoning in the requirements elicitation process

ICIS 2010 Proceedings - Thirty First International Conference on Information Systems

Volumn , Issue , 2010, Pages

  Rai, Sudhanshu ^a   Chakraborty, Suranjan ^b   Sarker, Suprateek ^c  

^a Copenhagen Business ^*  (Denmark)

^b TOWSON UNIVERSITY   (United States)

^c WASHINGTON STATE UNIVERSITY   (United States)

Author keywords

Inferential reasoning; Naiyayika school; Requirements elicitation

Indexed keywords

INFERENTIAL REASONING; INFORMATION SYSTEM DEVELOPMENT; IT SERVICES; NAIYAYIKA SCHOOL; QUALITATIVE DATA; REASONING PROCESS; REQUIREMENTS ELICITATION; RULE BASED;

INFORMATION SYSTEMS;

REQUIREMENTS ENGINEERING;

EID: 84870967258     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: None     Document Type: Conference Paper

References (32)

1. Bettman, J.R. and Park, C.W. 1980. Effects of Knowledge and Experience and Phase of the Choice Process on Consume Decision Processes: A Protocol Analysis",Journal of Consumer Research, (7:3), pp. 243-248.
2. Bhattacharyya, S. 1987"Some Aspects of the Navya Nyaya Theory of Inference, in: Doubt, Belief and Knowledge, N.C.O.P. Research (ed.), Indian Council of Philosophical Research, pp. 245-267.
3. Bochenski, I.M. 1956. The Indian Variety of Logic, in: A History of Formal Logic, F.T.I. Thomas (ed.), Notre Dame:University of Notre Dame Press, pp. 416-447.
4. Browne, G.J., and Pitts, M.G. 2004 Stopping Behavior of Information Analysts During Information Requirements Elicitation, Journal of Management Information System (21:1), pp. 203-226.
5. Browne, G.J., and Ramesh, V.2002. Improving Information Requirements Determination: A Cognitive perspective, Information & Management (39), pp 625-645.
6. Browne, G.J., Ramesh, V., Pitts, M.G. and Rogich, M.B. 1997 "Representing user requirements: An empirical investigation of formality in modeling tools." in Proceedings of the Americas Conference on Information Systems. J.N.P. Gupta (ed.), Pittsburgh, PA, pp. 89-91.
7. Browne, G. J. and Rogich, M. B. 2001. An empirical investigation of user requirements elicitation: Comparing the effectiveness of prompting techniques." Journal of Management Information Systems, (17:4), 223.
8. Chakraborty, S., Sarker, S. and Sarker, S. 2010 An Exploration into the Process of Requirements Elicitation: A Grounded Approach, Journal of the Association for Information Systems, (11: 4) Article 1.
9. Curtis, B., Krasner, H., and Iscoe, N. 1988. A field study of software design processes for large systems, Communications of ACM (31), pp 1268 -1287.
10. Colebrooke, H.T. 1824.On the Philosophy of the Hindus: Part II - On the Nyaya and VaiSeshika systems, Trans. Royal Asiatic Society (1) pp. 92-118.
11. Davidson, E.J. 2002. Technology frames and framing: A socio-cognitive investigation of requirements determination, MIS Quarterly (26:4) 2002, pp 329-358.
12. Davis, B. G. 1982. "Strategies for Information Requirements Determination", IBM Systems Journal (21:1), pp. 4-30.
13. Deifel, B.1999. "A Process Model For Requirements Engineering of CCOTS, 10th International Workshop on Database and Expert System Applications, IEEE Computer Society.
14. De Morgan, A. 1860.Syllabus of a Proposed System of Logic, in: On the Syllogism and Other Logical Writings P. Heath (ed.), London:Routledge and Kegan Paul.
15. Gadamer, H. 2002. The beginning of knowledge, New York, NY: Continuum International Publishing Group.
16. Ganeri, J. 2001 Indian Logic, A Reader, Richmond, Surrey: Curzon Press.
17. Ganeri, J. 2001. Philosophy in Classical India The proper work of reason London:Routledge.
18. Gasson, S. 2006. A genealogical study of boundary-spanning IS design, European Journal of Information Systems (15), pp 26-41.
19. Gioia, D. A. 1986. "Symbols, Scripts, and Sense making: Creating meaning in the organizational experience," in The Thinking Organization, H.P. Simms and D.A. Gioia (eds.), San Francisco: Jossey-Bass pp. 49-74.
20. Glaser, B. G. and Strauss, A. L. 1967. The Discovery of Grounded Theory. Chicago, IL: Aldine
21. Green, G.I. 1989.Perceived Importance Of Systems Analysts' Job Skills, Roles, MIS Quarterly (13:2), pp 115-133.
22. Hickey, A. M. and Davis A. M. 2004. A Unified Model of Requirements Elicitation, Journal of Management Information Systems (20:4), pp. 65-84.
23. Jarke, M., and Pohl, K. 1993.Establishing visions in context: Towards a model of requirements processes, 12th International Conference of Information Systems, Orlando, Florida.
24. Kennedy, V. 1839 The Philosophy of the Hindus, Asiatic Journal (NS) (28:110), pp. 7-152.
25. Lohse, G.L. Daihwan, M. and Olson, J.R. 1995. "Cognitive evaluation of system representation diagrams", Information and Management, (29: 2), pp. 79-94.
26. Newell, A. and Simon, H. A. 1972. Human Problem Solving, Englewood Cliffs, N.J.: Prentice-Hall, Inc.
27. Sarukkai, S. 2005. Indian Philosophy and Philosophy of Science, Delhi: Motilal Banarsidass Publishers Pvt. Ltd.
28. Schenk, K.D., Vitalari, N.P. and Davis, K.S. 1998."Differences between novice and expert systems analysts: What do we know and what do we do?" Journal of Management Information Systems, (15: 1), pp. 9-50.
29. Sommerville, I. 2007. Software Engineering, New York, NY:Addison Wesley.
30. Urquhart, C. 1997. "Exploring Analyst-Client Communication: Using Grounded Theory Techniques to Investigate Interaction in Informal Requirements Gathering," in Information Systems and Qualitative Research, A.S. Lee, J. Liebenau, and J. DeGross (eds.), London, UK: Chapman and Hall, pp. 149-181.
31. Vitalari, N.P., and Dickson, G.W. 1983."Problem solving for effective systems analysis: An exploration", Communications of the ACM, (26: 11), pp. 948-956.
32. Walz, D.B.; Elam, J.J.; and Curtis, B. 1993. "Inside a software design team: Knowledge acquisition, sharing, and integration", Communications of the ACM, (36:10) (1993), pp. 63-77.