Requirements Engineering

, Volume 11, Issue 1, pp 4–16 | Cite as

Requirements engineering for e-business advantage

  • Steven J. BleisteinEmail author
  • Karl Cox
  • June Verner
  • Keith T. Phalp
Original article


As a means of contributing to the achievement of business advantage for companies engaging in e-business, we propose a requirements engineering framework that incorporates a business strategy dimension. We employ Jackson’s Problem Frames approach, goal modeling, and business process modeling (BPM) to achieve this. Jackson’s context diagrams, used to represent business model context, are integrated with goal models to describe the requirements of the business strategy. We leverage the paradigm of projection in both approaches as a means of simultaneously decomposing both the requirement and context parts, from an abstract business level to concrete system requirements. Our approach maintains traceability to high-level business objectives via contribution relationship links in the goal model. We integrate use of role activity diagrams to describe business processes in detail where needed. The feasibility of our approach is shown by a well-known case study taken from the literature.


  1. 1.
    Stratopoulos T, Dehning B (2000) Does successful investment in information technology solve the productivity paradox? Inform Manage 38:103–117CrossRefGoogle Scholar
  2. 2.
    Andersen TJ (2001) Information technology, strategic decision making approaches and organizational performance in different industrial settings. J Strateg Inform Systems 10:101–119CrossRefGoogle Scholar
  3. 3.
    Bharadwaj A (2000) A resource-based perspective on information technology capability and firm performance: an empirical investigation. MIS Quart 24:169–96CrossRefGoogle Scholar
  4. 4.
    Feeney D, Ives B. (1990) In search of sustainability: reaping long-term advantage from investment in information technology. J Manage Inform Systems 7:27–46CrossRefGoogle Scholar
  5. 5.
    Kosynski B, McFarlan W (1990) Information partnerships—shared data, shared scales. Harvard Bus Rev 52:90–102Google Scholar
  6. 6.
    Mata F, Fuerst W, Barney J (1995) Information technology and sustainable competitive advantage: a resource-based analysis. MIS Quart 19:387–401CrossRefGoogle Scholar
  7. 7.
    McFarlan FW (1984) Information technology changes the way you compete. Harvard Bus Rev 62:98–103Google Scholar
  8. 8.
    Porter M, Millar V (1985) How information gives you competitive advantage. Harvard Bus Rev 63:149–160Google Scholar
  9. 9.
    Dehning B, Stratopoulos T (2003) Determinants of a sustainable competitive advantage due to an IT-enabled strategy. J Strateg Inform Systems 12:7–28CrossRefGoogle Scholar
  10. 10.
    Sambamurthy V (2000) Business strategy in hypercompetitive environments: rethinking the logic of it differentiation. In: Zmud RW (eds) Framing the domains of IT management. Pinnaflex Educational Resources, Cincinnati, OH, pp 245–61Google Scholar
  11. 11.
    McKeen JD, Smith H (2003) Making IT happen: critical issues in IT management. Wiley, ChichesterGoogle Scholar
  12. 12.
    Weill P, Vitale M (2001) Place to space: moving to ebusiness models. Harvard Business School Publishing Corporation, BostonGoogle Scholar
  13. 13.
    Oliver RW (2001) What is strategy, anyway? J Bus Strateg, pp 7–10Google Scholar
  14. 14.
    Porter M (1996) What is strategy? Harvard Bus Rev 74:61–78Google Scholar
  15. 15.
    Yu E (1993) Modeling organizations for information systems requirements engineering. In: Presented at IEEE international symposium on requirements engineeringGoogle Scholar
  16. 16.
    Giunchiglia F, Mylopoulos J, Perini A (2002) The Tropos software development methodology: processes, models and diagrams. Agent-Oriented Softw Eng Iii 2585:162–173CrossRefGoogle Scholar
  17. 17.
    Gordijn J, Akkermans J (2003) Value-based requirements engineering: exploring innovative ecommerce ideas. Requirement Eng J 8:114–135CrossRefGoogle Scholar
  18. 18.
    Loucopoulos P (2001) The S3 (strategy-service-support) framework for business process modelling. In: Presented at 3rd international conference on enterprise information systems (ICEIS 2001), Setubal, PortugalGoogle Scholar
  19. 19.
    Loucopoulos P, Kavakli E (1995) Enterprise modeling and the teleological approach to requirements engineering. Int J Cooperat Inform Systems 4:45–79CrossRefGoogle Scholar
  20. 20.
    Bubenko JA, Rolland C, Loucopoulos P, DeAntonellis (1994) Faciliating fuzzy to formal requirements modelling. In: Presented at first international conference on requirements engineering, Colorado SpringsGoogle Scholar
  21. 21.
    Rolland C, Souveyet C, Ben Achour C (1998) Guiding goal modeling using scenarios. IEEE Trans Softw Eng 24:1055–1071CrossRefGoogle Scholar
  22. 22.
    Feather MS, Cornford SL, Dunphy J (2002) A risk-centric model for value maximization. In: Presented at 4th international workshop on economics-driven software research, OrlandoGoogle Scholar
  23. 23.
    Feather MS, Cornford SL, Hicks KA (2002) Descoping. In: Presented at 27th NASA/IEEE software engineering workshop, GreenbeltGoogle Scholar
  24. 24.
    Kiper JD, Feather MS (2005) A risk-based approach to strategic decision-making for software development. In: Presented at 38th annual Hawaii international conference on system sciences (HICSS’05), Big IslandGoogle Scholar
  25. 25.
    Giorgini P, Mylopoulos J, Pistore M (2004) The Tropos methdology: an overview. In: Bergenti F, Gleizes M-P, Zambonelli F (eds) Methodologies and software engineering for agent systems: the agent-oriented software engineering handbook. Kluwer, Boston, pp. xxx, 505 pGoogle Scholar
  26. 26.
    Garzetti M, Giorgini P, Mylopoulos J, Sannicolo F (2002) Applying Tropos methdology to a real case study. In: Presented at joint workshop from objects to agents: from information to knowledge (WOA 2002), Milan, ItalyGoogle Scholar
  27. 27.
    Bleistein SJ, Cox K, Verner J (2004) RE approach for e-business advantage. In: Presented at 10th anniversary international workshop on requirements engineering: foundation of software quality (REFSQ), Riga, LatviaGoogle Scholar
  28. 28.
    Bleistein SJ, Cox K, Verner J (2004) Requirements engineering for e-business systems: integrating Jackson problem diagrams with goal modeling and BPM. In: Presented at 11th Asia Pacific software engineering conference, Busan, KoreaGoogle Scholar
  29. 29.
    Jackson M (2001) Problem frames: analyzing and structuring software development problem, 1st edn. Addison-Wesley, ReadingGoogle Scholar
  30. 30.
    Feather MS, Fickas S, Finkelstein A, van Lamsweerde A (1997) Requirements and specification exemplars. Automat Softw Eng 4:419–438CrossRefGoogle Scholar
  31. 31.
    Bensaou M (1997) Seven-Eleven Japan: managing a networked organization. INSEAD Euro-Asia Centre, Case studyGoogle Scholar
  32. 32.
    Whang S, Koshijima C, Saito H, Ueda T, Horne SV (1997) Seven Eleven Japan (GS18). Stanford University Graduate School of BusinessGoogle Scholar
  33. 33.
    Rapp WV (2002) Retailing: Ito-Yokado Seven-Eleven Japan. In: Information technology strategies: how leading firms use IT to gain an advantage. Oxford University Press, New York, pp. 163–186Google Scholar
  34. 34.
    Makino N, Suzuki T (1997) Convenience stores and the information revolution. Japan Echo 44:44–49Google Scholar
  35. 35.
    Kunitomo R (1997) Seven-Eleven is revolutionising grocery distribution in Japan. Long Range Plann 30:887–889Google Scholar
  36. 36.
    The Economist Newspaper Limited (2001) Over the counter e-commerce; e-strategy brief: Seven-Eleven; Japan’s Seven-Eleven. Economist (US), vol 359, pp 77Google Scholar
  37. 37.
    Lowe D (2003) Web system requirements: an overview. Requirements Eng J 8:102–113CrossRefGoogle Scholar
  38. 38.
    Overmeyer S (2000) What’s different about requirements engineering for web sites. Requirements Eng J 5:62–65CrossRefGoogle Scholar
  39. 39.
    Standing C (2001) Methodologies for developing web applications. Inform Softw Technol 44:151–159CrossRefGoogle Scholar
  40. 40.
    Zowghi D, Gervasi V (2001) Why is RE for web-based software development easier. In: Presented at seventh international workshop on requirements engineering: foundation for software quality (REFSQ’01), Interlaken, SwitzerlandGoogle Scholar
  41. 41.
    Hahn J, Kauffman RJ, Park J (2002) Designing for ROI: toward a value-driven discipline for e-commerce systems design, In: Presented at 35th Hawaii international conference on system sciences, HawaiiGoogle Scholar
  42. 42.
    Castro J, Kolp M, Mylopoulos J (2002) Towards requirements-driven information systems engineering: the Tropos project. Inform Syst J 27:365–389CrossRefzbMATHGoogle Scholar
  43. 43.
    Gamma E, Helm R, Johnson R, Vlissides J (1995) Design patterns: elements of reusable object-oriented software. First edn. Addison-Wesley, ReadingGoogle Scholar
  44. 44.
    Hall J, Jackson M, Nuseibeh B, Rapanotti L (2002) Relating software requirements architectures using problem frames. In: Presented at RE’02 – 10th international conference on requirements engineering. Essen, GermanyGoogle Scholar
  45. 45.
    I. Bray (2002) An introduction to requirements engineering, 1st edn. Pearson Addison Wesley, ReadingGoogle Scholar
  46. 46.
    Kovitz BL (1999) Practical software requirements: a manual of content and style. Manning, GreenwichGoogle Scholar
  47. 47.
    Cox K, Phalp K (2003) From process model to problem frame. In: Presented at 9th international workshop on requirements engineering: foundation for software quality - REFSQ’03, Velden, AustriaGoogle Scholar
  48. 48.
    Bleistein S, Cox K, Verner J (2004) Problem frames approach for e-business systems. In: Presented at the 1st international workshop on advances and applications of problem frames (IWAAPF) at the international conference on software engineering (ICSE’04), EdinburghGoogle Scholar
  49. 49.
    Bleistein SJ, Cox K, Verner J (2004) Modeling business strategy in e-business systems requirements engineering. In: Presented at fifth international workshop on conceptual modeling approaches for e-business (eCOMO 2004), Shanghai, ChinaGoogle Scholar
  50. 50.
    Bleistein SJ, Cox K, Verner J (2005) Strategic alignment in requirements analysis for organizational IT: an integrated approach. In: Presented at 20th ACM symposium on applied computing (SAC’05), Santa Fe, NM, USAGoogle Scholar
  51. 51.
    Bleistein SJ, Cox K, Verner J (2005) Validating strategic alignment of organizational IT requirements using goal modeling and problem diagrams. J Softw Systems (in press)Google Scholar
  52. 52.
    Cox K, Bleistein SJ, Verner J (2004) Connecting role activity diagrams to the problem frames approach. In: Presented at 9th Australian workshop on requirements engineering (AWRE’04), Adelaide, AustraliaGoogle Scholar
  53. 53.
    Cox K, Phalp K, Bleistein SJ, Verner J (2005) Deriving requirements from process models via the problem frames approach. Inform Softw Technol 47:319–337CrossRefGoogle Scholar
  54. 54.
    Cox K, Hall J, Rapanotti L (2005) Editorial: a roadmap of problem frames research. J Inform Softw Technol (in press)Google Scholar
  55. 55.
    van Lamsweerde A (2001) Goal-oriented requirements engineering: a guided tour. In: Presented at 5th IEEE international symposium on requirements engineering, TorontoGoogle Scholar
  56. 56.
    Gross D, Yu E (2001) From non-functional requirements to design through patterns. Requirements Eng J 6:18–36CrossRefzbMATHGoogle Scholar
  57. 57.
    Yu E, Liu L (2001) Modelling strategic actor relationships to support intellectual property management. In: Presented at 20th international conference on conceptual modelling, ER-2001, Yokohama, JapanGoogle Scholar
  58. 58.
    Liu L, Yu E (2001) From requirements to architectural design - using goals and scenarios. In: Presented at ICSE-2001 (STRAW 2001), Toronto, CanadaGoogle Scholar
  59. 59.
    Anton AI, Potts C (1998) The use of goals to surface requirements for evolving systems. In: Presented at ICSE-98: 20th international conference on software engineering, KyotoGoogle Scholar
  60. 60.
    Kolber AB, Estep C, Hay D, Struck D, Lam G, Healy J, Hall J, Zachman JA, Healy K, Eulenberg M, Fishman N, Ross R, Moriarty T, Selkow W (2000) Organizing business plans: the standard model for business rule motivation. The Business Rule Group November 15Google Scholar
  61. 61.
    Bleistein SJ, Aurum A, Cox K, Ray P (2004) Strategy-oriented alignment in requirements engineering: linking business strategy to requirements of e-business systems using the SOARE approach. J Res Pract Inform Technol 36:259–276Google Scholar
  62. 62.
    Chung LE, Nixon B, Yu E, Mylopoulos J (1999) Non-functional requirements in software engineering, vol. 5, 1st edn. Kluwer, DordrechtGoogle Scholar
  63. 63.
    Zave P, Jackson M (1997) Four dark corners of requirements engineering. ACM Trans Softw Eng Methodol 6:1–30CrossRefGoogle Scholar
  64. 64.
    Hammer M, Champy J (1993) Reengineering the corporation: a manifesto for business revolution, 1st edn. HarperBusiness, New YorkGoogle Scholar
  65. 65.
    DeMarco T (1979) Structured analysis and system specification. Prentice-Hall, Englewood CliffsGoogle Scholar
  66. 66.
    Yourdon E (1989) Modern structured analysis. Yourdon Press, Englewood CliffsGoogle Scholar
  67. 67.
    Jackson MJ (1995) Software requirements and specifications: a lexicon of practice, principles, and prejudices. ACM Press; Addison-Wesley, New York; ReadingGoogle Scholar
  68. 68.
    Jacobson I, Ericsson M, Jacobson A (1995) The object advantage: business process reengineering with object technology. Addison-Wesley, WokinghamGoogle Scholar
  69. 69.
    Arlow J (1998) Use cases, UML, visual modelling, and the trivialisation of business requirements. Requirements Eng J 3:150–152CrossRefGoogle Scholar
  70. 70.
    Buhr RJA (1998) Use case maps as architectural entities for complex systems. IEEE Trans Softw Eng 24:1131–1155CrossRefGoogle Scholar
  71. 71.
    Buhr RJA, Casselman RSO (1996) Use case maps for object-oriented systems. Prentice Hall, Upper Saddle RiverzbMATHGoogle Scholar
  72. 72.
    Eriksson HE., Penker M, Lyons B, Fado D (2004) UML 2 toolkit. Wiley, IndianapolisGoogle Scholar
  73. 73.
    Ould MA (1995) Business processes: modelling and analysis for re-engineering and improvement. Wiley, ChichesterGoogle Scholar
  74. 74.
    University of Toronto (2003) Goal-oriented requirements language, University of TorontoGoogle Scholar
  75. 75.
    Yu E (1997) Towards modelling and reasoning support for early-phase requirements engineering. In; Presented at 3rd IEEE international symposium on requirements engineering (RE’97), WashingtonGoogle Scholar

Copyright information

© Springer-Verlag London Limited 2005

Authors and Affiliations

  • Steven J. Bleistein
    • 1
    • 2
    Email author
  • Karl Cox
    • 1
    • 2
  • June Verner
    • 1
  • Keith T. Phalp
    • 3
  1. 1.Empirical Software Engineering Research ProgramNational ICT AustraliaSydneyAustralia
  2. 2.School of Computer Science and EngineeringUniversity of New South WalesSydneyAustralia
  3. 3.Emprical Software Engineering Research GroupBournemouth UniversityDorsetUK

Personalised recommendations