Abstract
Current information systems (IS) are enterprise-wide systems supporting strategic goals of the enterprise and meeting its operational business needs. They are supported by information and communication technologies (ICT) and other software that should be fully integrated. To develop software responding to real business needs, we need requirements engineering (RE) methodology that ensures the alignment of requirements for all levels of enterprise system. The main contribution of this chapter is a requirement-oriented methodological framework allowing to transform business requirements level by level into software ones. The structure of the proposed framework reflects the structure of Zachman’s framework. However, it has other intentions and is purposed to support not the design but the RE issues.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
References
Caplinskas, A.; Lupeikiene, A.; Vasilecas, O. (2002) Unified enterprise engineering environment: ontological point of view. In Proceedings of the Baltic Conference, BalticDB\&IS 2002, Institute of Cybernetics at Tallin Technical University, pp. 30–50.
Luftman, J. (2000) Assessing business-IT alignment maturity. Communications of the AIS, 4(14), pp. 1–50.
Henderson, J. C.; Venkatraman, N. (1993) Strategic alignment: leveraging information technology for transforming organizations. IBM Systems Journal, 32(1), pp. 4–16.
The Open Group (2003) The Open Group Architecture Framework TOGAF. Version 8.1, Enterprise Edition.
Sowa, J. F.; Zachman, J. A. (1992). Extending and formalizing the framework for information systems architecture. IBM Systems Journal, 31(3), pp. 590–616.
Capgemini (2007) Enterprise, Business and IT Architecture and the Integrated Architecture,Capgemini. Consulting, Technology, Outsourcing, Brochure. Available from <http://www.capgemini.com/services/soa/ent_architecture/enterprise_arch/> [accessed 29 April 2008].
Sousa, P; Pereira, C. M.; Marques, J. A. (2005) Enterprise architecture alignment heuristics. The Architecture Journal (Microsoft Architect Journal), Journal 4. Available from <http://msdn2.microsoft.com/en-us/library/aa480042.aspx> [accessed 29 April 2008].
Hay, D. C. (2002) Requirements Analysis, From Business Views to Architecture, Prentice Hall PTR, Upper Saddle River, NJ.
Oracle Corporation (2000) CDM Quick Tour, Release 2.0.0.
Wiegers, K. E. (2003) Software Requirements. 2nd edition, Microsoft Press, Redmond, WA.
IEEE (1998) Std 1233-1998: IEEE Guide for Developing System Requirements Specifications. Software Engineering Standards Committee of the IEEE Computer Society, USA.
Karlsson, J. (1997) Managing software requirements using quality function deployment. Software Quality Journal, 6, pp. 311–325.
Chung, L.; Nixon, B. A.; Yu, E.; Mylopoulos, J. (2000) Non-Functional Requirements in Software Engineering, Kluwer Academic Publishers, Boston.
Lamsweerde, A. v. (2001) Goal-oriented requirements engineering: a guided tour. Proceedings of the 5th IEEE International Symposium on Requirements Engineering (RE’01), Toronto, Canada, pp. 249–261.
Demarco, T. (1979) Structured Analysis and System Specification, Prentice Hall PTR, Upper Saddle River, NJ.
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2009 Springer Science+Business Media, LLC
About this chapter
Cite this chapter
Caplinskas, A., Paškevičiūtė, L. (2009). A Methodological Framework for Enterprise Information System Requirements Derivation. In: Papadopoulos, G., Wojtkowski, W., Wojtkowski, G., Wrycza, S., Zupancic, J. (eds) Information Systems Development. Springer, Boston, MA. https://doi.org/10.1007/b137171_68
Download citation
DOI: https://doi.org/10.1007/b137171_68
Published:
Publisher Name: Springer, Boston, MA
Print ISBN: 978-0-387-84809-9
Online ISBN: 978-0-387-84810-5
eBook Packages: Computer ScienceComputer Science (R0)