Process of Requirements Evolution in Web-Enabled Employee Service Systems

  • Pradip K. Sarkar
  • Jacob L. Cybulski
Conference paper


In recent times, according to the Association for Payroll Specialists, the adoption rate of web-enabled employee service systems (ESS) in Australia has accelerated to a point where one in 10 Australian firms now have such systems in place for employees to view and update their details online (Nixon, 2003). The main objective of web-based support for HR solutions was to replace paper-based documents and the multiple steps of the HR process with online data entry and interaction by employees and managers themselves. Furthermore, the adoption of such services was greatly influenced by the organizational strategic plans that basically translate into operational goals of improved productivity, data accuracy, and the reduction of paperwork and administrative overheads. Despite the optimism and success stories, these systems have their share of obstacles. One of these obstacles is the plain fact that only a fraction of employees have access to the web and computers (Lapointe, 1997). Such systems necessitate infrastructure support in the forms of increased security features, workflow and transaction management, and web administration. Moreover, these systems have been designed keeping in mind that the users will be casual and untrained. Also, the stakeholder base will be far wider than that of conventional non-web HR systems, which are traditionally used by HRstaff alone (Lapointe, 1998). The broad, diverse, and expanding stakeholder base, characteristic of web-enabled information systems (WBIS) in general (Nazareth, 1998; Carter, 2002; Standing, 2002; Stevens and Timbre11, 2002), raises the issue of multiple and possibly conflicting viewpoints regarding the various facets of the web system (Easterbrook, 1994; Sommerville et al., 1997).


Project Team Requirement Engineer Information System Development Requirement Evolution Project Initiator 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. Avison, D. E., Wood-Harper, A. T., et al., 1998, A Further Exploration into Information Systems Development: The Evolution of Multiview 2, Information Technology & People, 11 (2): 124–139.CrossRefGoogle Scholar
  2. Boehm, B., 1986, A Spiral Model of Software Development and Enhancement, Software Engineering Notes, 11 (4): 22–32.CrossRefGoogle Scholar
  3. Boland, R., 1979, Control, Causality and Information System Requirements. Accounting, Organizations and Society, 4 (4).Google Scholar
  4. Boland, R., 1985, Phenomenology: A Preferred Approach to Research in Information Systems, in: Research Methods in Information Systems, A. T. Wood-Harper, ed., Amsterdam, NorthHolland.Google Scholar
  5. Carter, J., 2002, Developing E-Commerce Systems,Prentice-Hall.Google Scholar
  6. Creswell, J. W., 1994, A Framework for the Study, in: Research Design: Qualitative & Quantative Approaches, SAGE Publications.Google Scholar
  7. Curtis, B., Krasner, H. et al., 1988, A Field Study of the Software Design Process for Large Systems, Communications of the ACM, 31 (11): 1268–1287.CrossRefGoogle Scholar
  8. Darke, P., Shanks, G. et al., 1998, Successfully Completing Case Study Research: Combining Rigour, Relevance and Pragmatism, Information Systems Journal, 8: 273–289.CrossRefGoogle Scholar
  9. Easterbrook, S., 1994, Resolving Requirements Conflicts with Computer-Supported Negotiation, in: Requirements Engineering: Social and Technical Issues. J. Goguen. London, Academic Press: 41–65.Google Scholar
  10. Fratemali, P., 1999, Tools and Approaches for Developing Data-Intensive Web Applications: A Survey, ACM Computing Surveys,31(3): 227–263.CrossRefGoogle Scholar
  11. Freeman, R. E., 1984, Strategic Management: A Stakeholder Approach. Boston, Pitman.Google Scholar
  12. Gadamer, H.-G., 1976, Philosophical Hermeneutics. California, University of California Press.Google Scholar
  13. Galliers, R. D., 1985, In Search of a Paradigm for Information Systems Research, in: Research Methods in Information Systems, A. T. Wood-Harper, ed., North-Holland, UK: 3–9.Google Scholar
  14. Ginige, A., 1998, Web Engineering: Methodologies for Developing Large and Maintainable Web-Based Information Systems, IEEE International Conference on Networking India and the World, Ahmedabad, India.Google Scholar
  15. Gordijn, J., Akkermans, H., et al., 2000, Value Based Requirements Creation for Electronic Commerce Applications, The 33rd Hawaii International Conference on Systems Sciences, Hawaii: 1915–1924.Google Scholar
  16. Hancock, B., 2002, An Introduction to the Research Process,Trent Focus Group.Google Scholar
  17. Irani, Z., 2002, Information systems evaluation: navigating through the problem domain, Information and Management, 40 (1): 11–24.CrossRefGoogle Scholar
  18. Kaplan, B. and Maxwell, J. A., 1994, Qualitative Research Methods for Evaluating Computer Information Systems, Evaluating Health Care Information Systems: Methods and Applications, S. J. Jay, ed., Thousand Oaks, CA, SAGE: 45–68.Google Scholar
  19. Klein, H. K. and M. D. Myers, 1999, A Set of Principles for Conducting and Evaluating Interpretive Field Studies in Information Systems, MIS Quarterly, 23 (1): 67–94.CrossRefGoogle Scholar
  20. Lapointe, J. R., 1997, Trends in Employee Self-Service, Benefits and Compensation Solutions Magazine, Accessed 2003.Google Scholar
  21. Lapointe, J. R., 1998, Several Steps to Successful ESS (Employee Self-Service). HR Focus, (Special Report on HR Technology, 75: 13–16.Google Scholar
  22. Lee, A. S., 1994, Electronic Mail as a Medium for Rich Communication: An Empirical Investigation Using Hermeneutic Interpretation, MIS Quarterly: 143–157.Google Scholar
  23. Leffingwell, D. and Widrig, D, 2000, Managing Software Requirements: A Unified Approach,Addison Wedley.Google Scholar
  24. Marshall, C. and Rossman,G. B. (1989). Designing Qualitative Research,SAGE Publications Inc.Google Scholar
  25. Moreno Jr., V., 1999, On the Social Implications of Organizational Reengineering: A Phenomenological Study of Individual Experiences of BPR Processes, Information Technology & People, 12 (4): 359–388.CrossRefGoogle Scholar
  26. Moustakas, C., 1994, Phenomenological Research Methods,SAGE Publications.Google Scholar
  27. Murugesan, S., Y., Deshpande, et al., 1999, Web Engineering: A New Discipline for Development of Web-Based Systems, Proc First ICSE Workshop on Web Engineering, Los Angeles: 1–9.Google Scholar
  28. Nazareth, D., L, 1998, Designing Effective Websites: Lending Structure to a Chaotic Process, Fourth Americas Conference on Information Systems, Baltimore, Maryland: 1011–1013.Google Scholar
  29. Nixon, S., 2003, Net pay is all the wage, with its future now on the line, The Age, Melbourne.Google Scholar
  30. Pouloudi, A., 1999, Aspects of the Stakeholder Concept and their Implications for Information Systems Development, 32nd Hawaii Conference on System Sciences, Hawaii.Google Scholar
  31. Riggins, F. J. and T. Mukhopadhyay, 1999, Overcoming Adoption and Implementation Risks of EDI, International Journal of Electronic Commerce.Google Scholar
  32. Russo, N. L., 2000, Developing Applications for the Web: Exploring Differences Between Traditional and World Wide Web Application Development, in: Managing Web-Enabled technologies in Organizations: A Global Perspective, M. Khosrowpour, ed., Idea Group Publishing, 23–35.Google Scholar
  33. Sharp, H., Finkelstein A., et al., 1999, Stakeholder identification in the Requirements Engineering Process, in: Proc. Database and Expert Systems Applications (DEXA 99), Florence, Italy, IEEE Computer Society Press, pp. 387–391.Google Scholar
  34. Siau, K., 1998, Method Engineering for Web Information Systems Development: Challenges and Issues, Fourth Americas Conference on Information Systems, Baltimore, Maryland: 1017–1019.Google Scholar
  35. Sommerville, I. and Sawyer P., 1997, Viewpoints: Principles, Problems, and a Practical Approach to Requirements Engineering, Annals of Software Engineering, 3: 101–130.CrossRefGoogle Scholar
  36. Sommerville, I., Sawyer, P. et al., 1997, Viewpoints for Requirements Elicitation: a Practical Approach, The 3rd IEEE International Conference on Requirements Engineering, CO, USA: 74–81.Google Scholar
  37. Standing, C., 2000, Internet Commerce Development,Artech House Inc.Google Scholar
  38. Standing, C., 2001, The Requirements of Methodologies for Developing Web Applications, ECIS, Bled, Slovenia: 548–556.Google Scholar
  39. Standing, C., 2002, Methodologies for developing Web applications, Information and SoftwareTechnology 44 (3): 151–159.Google Scholar
  40. Stevens, K. J. and Timbrell, G. T., 2002, The Implications of E-Commerce for Software Project Risk: A preliminary investigation, IFIP, Copenhagen.Google Scholar
  41. Strauss, A. and J. Corbin, 1990, Basics of Qualitative Research: Grounded Theory Procedures and Techniques, Newbury Park, CA, SAGE Publications.Google Scholar
  42. Vidgen, R., 2002a, Constructing a Web Information System development Methodology, Information Systems Journal, 12: 247–261.CrossRefGoogle Scholar
  43. Vidgen, R., 2002b, What’s so different about Developing Web-based Information Systems?, European Conference in Information Systems, Gdansk, Poland: 262–271.Google Scholar
  44. Walsham, G., 1993, Interpreting Information Systems in Organizations. London, Wiley & Sons.Google Scholar
  45. Yin, R. K., 1994, Case Study Research: Design and Methodology. Thousand Oakes, Sage Publications.Google Scholar

Copyright information

© Springer Science+Business Media New York 2004

Authors and Affiliations

  • Pradip K. Sarkar
    • 1
  • Jacob L. Cybulski
    • 1
  1. 1.School of Information Systems, Faculty of Business and LawDeakin UniversityAustralia

Personalised recommendations