Business requirements analysis and development for legacy system replacement projects in government organizations

2012 20th IEEE International Requirements Engineering Conference, RE 2012 - Proceedings

Volumn , Issue , 2012, Pages 337-340

  Alexandrova, Assia ^a  

^a OPEN UNIVERSITY   (United Kingdom)

Author keywords

e government; legacy systems; requirements development; risk and opportunity analysis; serious games

Indexed keywords

BUSINESS PROCESS; BUSINESS REQUIREMENT; E-GOVERNMENT; GOVERNMENT ORGANIZATIONS; PUBLIC SECTOR AGENCIES; REQUIREMENTS ANALYSIS; REQUIREMENTS DEVELOPMENT; REQUIREMENTS PHASE; RISK AND OPPORTUNITY; SERIOUS GAMES; SYSTEM REPLACEMENT; TECHNICAL CONSTRAINTS;

COMPETITION; GOVERNMENT DATA PROCESSING; REQUIREMENTS ENGINEERING;

LEGACY SYSTEMS;

EID: 84870668214     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/RE.2012.6345833     Document Type: Conference Paper

References (16)

1. R. Heeks, R. "Most eGovernment development projects fail: how can risks be reduced?" iGovernment Working Paper Series, IDPM. University of Manchester, UK, 2003.
2. W. Lam. "Barriers to e-government integration. " Journal of Enterprise Information Management, 18, no. 5, 2005, pp. 511-530.
3. A. D. Lloyd, R. Dewar and R. Pooley. "Business process and legacy system reengineering: A pattern perspective, " Communications of AIS, vol. 2, 1999.
4. W. Ebbers and J Vandijk. "Resistance and support to electronic government, building a model of innovation. " Government Information Quarterly 24, no. 3, July 2007, pp. 554-575.
5. A. Halachmi. "Imagined promises versus real challenges to public performance management. " International Journal of Productivity and Performance Management 60, no. 1, 2011, pp. 24-40.
6. Y. Gong and M. Janssen. "From policy implementation to business process management: Principles for creating flexibility and agility. " Government Information Quarterly, September 2011, pp S61-S71.
7. S. Kelly, N. Gibson, C. P. Holland and B. Light. "A business perspective of legacy systems. " Communications of the Association for Information Systems, 2(7), 1999.
8. A. Aurum, and C. Wohlin. "The fundamental nature of requirements engineering activities as a decision-making process. " Information and Software Technology, no. 14, November 2003, pp. 945-954.
9. W. S. Adolph. "Cash Cow in the Tar Pit: Reengineering a Legacy System. " IEEE Software, 1996, pp. 41-47.
10. P. M. Gupta, and D. Bhatia. "Reworking with a legacy financial accounting system: Lessons from a Pharma Company. " Interfaces, 30 (3), 2005, pp. 79-91.
11. P. Kardasis, and P. Loucopoulos. "Aligning Legacy Information Systems to Business Processes. " Lecture Notes in Computer Science 1413, 1998, pp. 25-39.
12. L. Aversano, and M. Tortorella. "An assessment strategy for identifying legacy system evolution requirements in eBusiness context. " Journal of Software Maintenance and Evolution: Research and Practice. 16, no. 4-5, 2004, pp. 255-276.
13. H. Khamooshi, and A. King. "IS/IT Requirements Elicitation/ Specification Procedure Assessment within a UK Government Service Organization. " Journal of Information Technology Management, Volume XV, Numbers 3-4, 2004, pp. 33-43.
14. C. Mainemelis, and S Ronson. "Ideas are Born in Fields of Play: Towards a Theory of Play and Creativity in Organizational Settings. " Research in Organizational Behavior 27, no. 6, 2006, pp. 81-131.
15. C. Harteveld, C. "Triadic Game Design-Balancing Reality, Meaning and Play". Springer-Verlag, London, UK, 2011.
16. D. Charsky. "From Edutainment to Serious Games: A Change in the Use of Game Characteristics. " Games and Culture 5, no. 2, February 11, 2010, pp. 177-198.