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.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
References
Chaos Report, Standish Group. (1994).
Hooks, I. F., & Farry, K. A. (2001). Customer-centered products: Creating successful products through smart requirements management. New York: AMACOM Div American Mgmt Assn.
Boehm, B. W., & Papaccio, P. N. (1988). Understanding and controlling software costs. IEEE Transactions on Software Engineering, 14(10), 1462–1477.
Standish Group. (2003). Chaos Chronicles Version 3.0. West Yarmouth, MA.
Charette, R. N. (2005). Why software FAILS. IEEE Spectrum, 42(9), 42–49.
Wake, W. C. (2003). INVEST in good stories and SMART tasks. Retrieved December 29, 2005. From http://xp123.com/xplor/xp0308/index.shtml.
IEEE Standard, IEEE-Std 610. (1990).
Robertson, S., & Robertson, J. (2012). Mastering the requirements process: Getting requirements right. MA: Addison-wesley.
Kotonya, G., & Sommerville, I. (1998). Requirements engineering: Processes and techniques. New York: Wiley.
Sutcliffe, A. (2002). User-centred requirements engineering. Berlin: Springer.
Mylopoulos, J., Chung, L., & Yu, E. (1999). From object-oriented to goal-oriented requirements analysis. Communications of the ACM, 42(1), 31–37.
Zave, P. (1997). Classification of research efforts in requirements engineering. ACM Computing Surveys (CSUR), 29(4), 315–321.
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.
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.
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.
Goguen, J. A., & Linde, C. (1993). Techniques for requirements elicitation. Requirements Engineering, 93, 152–164.
Suchman, L., & Jordan, B. (1990). Interactional troubles in face-to-face survey interviews. Journal of the American Statistical Association, 85(409), 232–241.
Hickey, A., & Davis, A. (2003). Barriers to transferring requirements elicitation techniques to practice. In 2003 Business Information Systems Conference.
Leffingwell, D., & Widrig, D. (2000). Managing software requirements. MA: Addison-Wesley.
Davis, G. B. (1982). Strategies for information requirements determination. IBM Systems Journal, 21, 4–30.
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.
Lapouchnian, A. (2005). Goal-oriented requirements engineering: An overview of the current research. University of Toronto.
Antón, A. I. (1996, April). Goal-based requirements analysis. In Proceedings of the Second International Conference on Requirements Engineering (pp. 136–144). IEEE.
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.
Dardenne, A., van Lamsweerde, A., & Fickas, S. (1993). Goal-directed requirements acquisition. Science of Computer Programming, 20(1), 3–50.
Pohl, K. (2010). Requirements engineering: Fundamentals, principles, and techniques. Berlin: Springer.
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.
Haumer, P., Pohl, K., & Weidenhaupt, K. (1998). Requirements elicitation and validation with real world scenes. IEEE Transactions on, Software Engineering, 24(12), 1036–1054.
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.
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.
Horkoff, J., & Yu, E. (2012). Comparison and evaluation of goal-oriented satisfaction analysis techniques. Requirement Engineering Journal, 1–24.
Matulevičius, R., & Heymans, P. (2007). Comparing goal modelling languages: An experiment. Requirements engineering: Foundation for software quality (pp. 18–32). Berlin Heidelberg: Springer.
Castro, J., Kolp, M., & Mylopoulos, J. (2002). Towards requirements-driven information systems engineering: The Tropos project. Information Systems, 27(6), 365–389.
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.
Holbrook, H., III. (1990). A scenario-based methodology for conducting requirements elicitation. ACM SIGSOFT Software Engineering Notes, 15(1), 95–104.
van Lamsweerde, A., & Willemet, L. (1998). Inferring declarative requirements specifications from operational scenarios. IEEE Transactions on Software Engineering, 24(12), 1089–1114.
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).
Liu, L., & Yu, E. (2004). Designing information systems in social context: A goal and scenario modelling approach. Information Systems, 29(2), 187–203.
CREWS Team. (1998). The CREWS glossary, CREWS report 98-1. http://SUNSITE.informatik.rwth-aachen.de/CREWS/reports.htm.
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).
Cockburn, A. (1997). Structuring use cases with goals, 1997. Journal of Object-Oriented Programming.
Author information
Authors and Affiliations
Corresponding author
Rights and permissions
Copyright information
© 2018 Springer Nature Singapore Pte Ltd.
About this chapter
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)