Skip to main content
SpringerLink
Log in
Book cover

Data Warehouse Requirements Engineering pp 1–17Cite as

Requirements Engineering for Transactional Systems

  • Chapter
  • First Online:

Abstract

The book starts with failure statistics of transactional systems and the technological responses for failure mitigation. We discuss the evolution of development processes for transactional systems and highlight the emerging role of agile development. This mitigates failure through iterative and incremental development. The second response is to focus on system requirements. Here we first define the term requirements and consider the requirements engineering process. The approaches to requirements elicitation are reviewed. This lays the basis for the next chapter so as to discuss the differences between transactional and data warehouse requirement engineering respectively.

This is a preview of subscription content, log in via an institution.

Chapter
USD   29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD   49.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD   64.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD   99.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Learn about institutional subscriptions

References

  1. Chaos Report, Standish Group. (1994).

    Google Scholar 

  2. Hooks, I. F., & Farry, K. A. (2001). Customer-centered products: Creating successful products through smart requirements management. New York: AMACOM Div American Mgmt Assn.

    Google Scholar 

  3. Boehm, B. W., & Papaccio, P. N. (1988). Understanding and controlling software costs. IEEE Transactions on Software Engineering, 14(10), 1462–1477.

    Article  Google Scholar 

  4. Standish Group. (2003). Chaos Chronicles Version 3.0. West Yarmouth, MA.

    Google Scholar 

  5. Charette, R. N. (2005). Why software FAILS. IEEE Spectrum, 42(9), 42–49.

    Article  Google Scholar 

  6. Wake, W. C. (2003). INVEST in good stories and SMART tasks. Retrieved December 29, 2005. From http://xp123.com/xplor/xp0308/index.shtml.

  7. IEEE Standard, IEEE-Std 610. (1990).

    Google Scholar 

  8. Robertson, S., & Robertson, J. (2012). Mastering the requirements process: Getting requirements right. MA: Addison-wesley.

    Google Scholar 

  9. Kotonya, G., & Sommerville, I. (1998). Requirements engineering: Processes and techniques. New York: Wiley.

    Google Scholar 

  10. Sutcliffe, A. (2002). User-centred requirements engineering. Berlin: Springer.

    Book  MATH  Google Scholar 

  11. Mylopoulos, J., Chung, L., & Yu, E. (1999). From object-oriented to goal-oriented requirements analysis. Communications of the ACM, 42(1), 31–37.

    Article  Google Scholar 

  12. Zave, P. (1997). Classification of research efforts in requirements engineering. ACM Computing Surveys (CSUR), 29(4), 315–321.

    Article  Google Scholar 

  13. van Lamsweerde, A. (2000, June). Requirements engineering in the year 00: A research perspective. In Proceedings of the 22nd International Conference on Software Engineering (pp. 5–19). New York: ACM.

    Google Scholar 

  14. Nuseibeh, B., & Easterbrook, S. (2000, May). Requirements engineering: A roadmap. In Proceedings of the Conference on the Future of Software Engineering (pp. 35–46). New York: ACM.

    Google Scholar 

  15. Yu, E. S. (1997, January). Towards modelling and reasoning support for early-phase requirements engineering. In Proceedings of the Third IEEE International Symposium on Requirements Engineering (pp. 226–235). IEEE.

    Google Scholar 

  16. Goguen, J. A., & Linde, C. (1993). Techniques for requirements elicitation. Requirements Engineering, 93, 152–164.

    Google Scholar 

  17. Suchman, L., & Jordan, B. (1990). Interactional troubles in face-to-face survey interviews. Journal of the American Statistical Association, 85(409), 232–241.

    Article  Google Scholar 

  18. Hickey, A., & Davis, A. (2003). Barriers to transferring requirements elicitation techniques to practice. In 2003 Business Information Systems Conference.

    Google Scholar 

  19. Leffingwell, D., & Widrig, D. (2000). Managing software requirements. MA: Addison-Wesley.

    Google Scholar 

  20. Davis, G. B. (1982). Strategies for information requirements determination. IBM Systems Journal, 21, 4–30.

    Article  Google Scholar 

  21. Burton, A. M., Shadbolt, N. R., Rugg, G., & Hedgecock, A. P. (1990). The efficacy of knowledge elicitation techniques: A comparison across domains and levels of expertise. Journal of Knowledge Acquisition, 2, 167–178.

    Article  Google Scholar 

  22. Lapouchnian, A. (2005). Goal-oriented requirements engineering: An overview of the current research. University of Toronto.

    Google Scholar 

  23. Antón, A. I. (1996, April). Goal-based requirements analysis. In Proceedings of the Second International Conference on Requirements Engineering (pp. 136–144). IEEE.

    Google Scholar 

  24. van Lamsweerde, A. (2004, September). Goal-oriented requirements engineering: A roundtrip from research to practice engineering. In Requirements Engineering Conference, 2004. Proceedings. 12th IEEE International (pp. 4–7). IEEE.

    Google Scholar 

  25. Dardenne, A., van Lamsweerde, A., & Fickas, S. (1993). Goal-directed requirements acquisition. Science of Computer Programming, 20(1), 3–50.

    Article  MATH  Google Scholar 

  26. Pohl, K. (2010). Requirements engineering: Fundamentals, principles, and techniques. Berlin: Springer.

    Book  Google Scholar 

  27. van Lamsweerde, A. (2001). Goal-oriented requirements engineering: A guided tour. In Proceedings. Fifth IEEE International Symposium on Requirements Engineering, 2001(pp. 249–262). IEEE.

    Google Scholar 

  28. Haumer, P., Pohl, K., & Weidenhaupt, K. (1998). Requirements elicitation and validation with real world scenes. IEEE Transactions on, Software Engineering, 24(12), 1036–1054.

    Article  Google Scholar 

  29. Antón, A. I., & Potts, C. (1998, April). The use of goals to surface requirements for evolving systems. In Proceedings of the 1998 International Conference on Software Engineering, 1998 (pp. 157–166). IEEE.

    Google Scholar 

  30. Horkoff, J., & Yu, E. (2010). Interactive analysis of agent-goal models in enterprise modeling. International Journal of Information System Modeling and Design (IJISMD), 1(4), 1–23.

    Article  Google Scholar 

  31. Horkoff, J., & Yu, E. (2012). Comparison and evaluation of goal-oriented satisfaction analysis techniques. Requirement Engineering Journal, 1–24.

    Google Scholar 

  32. Matulevičius, R., & Heymans, P. (2007). Comparing goal modelling languages: An experiment. Requirements engineering: Foundation for software quality (pp. 18–32). Berlin Heidelberg: Springer.

    Chapter  Google Scholar 

  33. Castro, J., Kolp, M., & Mylopoulos, J. (2002). Towards requirements-driven information systems engineering: The Tropos project. Information Systems, 27(6), 365–389.

    Article  MATH  Google Scholar 

  34. Sutcliffe, A. G., Maiden, N. A., Minocha, S., & Manuel, D. (1998). Supporting scenario-based requirements engineering. IEEE Transactions on Software Engineering, 24(12), 1072–1088.

    Article  Google Scholar 

  35. Holbrook, H., III. (1990). A scenario-based methodology for conducting requirements elicitation. ACM SIGSOFT Software Engineering Notes, 15(1), 95–104.

    Article  Google Scholar 

  36. van Lamsweerde, A., & Willemet, L. (1998). Inferring declarative requirements specifications from operational scenarios. IEEE Transactions on Software Engineering, 24(12), 1089–1114.

    Article  Google Scholar 

  37. Plihon, V., Ralyte, J., Benjamen, A., Maiden, N. A., Sutcliffe, A., Dubois, E., & Heymans, P. (1998). A reuse-oriented approach for the construction of scenario bases methods. In Proceedings of International Conference on Software Process (pp. 1–16).

    Google Scholar 

  38. Liu, L., & Yu, E. (2004). Designing information systems in social context: A goal and scenario modelling approach. Information Systems, 29(2), 187–203.

    Article  Google Scholar 

  39. CREWS Team. (1998). The CREWS glossary, CREWS report 98-1. http://SUNSITE.informatik.rwth-aachen.de/CREWS/reports.htm.

  40. Pohl, K., & Haumer, P. (1997, June). Modelling contextual information about scenarios. In Proceedings of the Third International Workshop on Requirements Engineering: Foundations of Software Quality REFSQ (Vol. 97, pp. 187–204).

    Google Scholar 

  41. Cockburn, A. (1997). Structuring use cases with goals, 1997. Journal of Object-Oriented Programming.

    Google Scholar 

Download references

Author information

Authors and Affiliations

  1. ICLC Ltd., New Delhi, India

    Naveen Prakash

  2. Central University of Rajasthan, Kishangarh, India

    Deepika Prakash

Authors
  1. Naveen Prakash
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Deepika Prakash
    View author publications

    You can also search for this author in PubMed Google Scholar

Corresponding author

Correspondence to Naveen Prakash .

Rights and permissions

Reprints and permissions

Copyright information

© 2018 Springer Nature Singapore Pte Ltd.

About this chapter

Check for updates. Verify currency and authenticity via CrossMark

Cite this chapter

Prakash, N., Prakash, D. (2018). Requirements Engineering for Transactional Systems. In: Data Warehouse Requirements Engineering. Springer, Singapore. https://doi.org/10.1007/978-981-10-7019-8_1

Download citation

  • DOI: https://doi.org/10.1007/978-981-10-7019-8_1

  • Published:

  • Publisher Name: Springer, Singapore

  • Print ISBN: 978-981-10-7018-1

  • Online ISBN: 978-981-10-7019-8

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics

Search

Navigation