Requirements elicitation in the context of enterprise engineering: A vision driven approach

Informatica

Volumn 20, Issue 3, 2009, Pages 343-368

  Čaplinskas, Albertas ^a  

^a VILNIUS UNIVERSITY   (Lithuania)

Author keywords

Enterprise engineering; Methodical frameworks; Requirements engineering; Strategic alignment vision driven approach

Indexed keywords

EID: 70349802349     PISSN: 08684952     EISSN: None     Source Type: Journal    
DOI: None     Document Type: Article

References (53)

1. Blick, G. (2000). Defining business process requirements for large-scale public sector ERP implementations: A case study. In: Proc. of the 8th Eur. Conf. on Information Systems (ECIS 2000), Vienna, Austria, July 3-5. Accessible at: http://is2.lse.ac.uk/asp/aspecis/20000156.pdf.
2. Bray, I.K. (2002). An Introduction on Requirements Engineering. Addison-Wesley. An imprint of Pearson Education.
3. Caplinskas, A., Paskeviciute, L. (2009). A methodological framework for enterprise information system requirements derivation. In: Papadopoulos, G.A.,Wojtkowski,W.,Wojtkowski,W.G., Wrycza, S., Zupancic, J. (Eds), Information Systems Development: Towards a Service Provision Society, Springer-Verlag (in press).
4. Caplinskas, A., Lupeikiene, A., Vasilecas, O. (2002a). A framework to analyse and evaluate information systems specification languages. In: Manolopoulos, Y., Navrat, P. (Eds.), Advances in Databases and Information Systems. 6th East European Conf., ADBIS 2002, Bratislava, Slovakia, September 2002. Proc. LNCS, Vol. 2435, Springer, pp. 248-262.
5. Caplinskas, A., Lupeikiene, A., Vasilecas, O. (2002b). Shared conceptualisation of business systems, information systems and supporting software. In: Haav, H.-M., Kalja, A. (Eds.), Databases and Information Systems II: Selected Papers from the Fifth International Baltic Conference, BalticDB&IS'2002. Kluwer Academic, pp. 109-320.
6. Caplinskas, A., Lupeikiene, A., Vasilecas, O. (2003). The role of ontologies in reusing domain and enterprise engineering assets. Informatica, 14(4), 455-470.
7. Davis, G.B., Olson, M.H. (1985). Management Information Systems: Conceptual Foundations, Structure and Development, 2nd ed. McGraw-Hill.
8. De la Vara, J.L., Diéaz, J.S. (2007). Business process-driven requirements engineering: A goal-based approach. In: Proc. of the 8th Workshop on Business Process Modeling, Development, and Support (BPMDS'07), 11-15 June 2007, Trondheim, Norway. Accessible at: http://lamswww.epfl.ch/conference/ bpmds07/program/Gonzalez-23.pdf.
9. Department of Defense (DoD) (1997). Command, Control, Communications, Computers, Intelligence, Surveillance, and Reconnaissance (C4ISR) Architecture Framework. Version 2.0, 18 Dec. 1997.
10. Department of Defense (DoD) (2007). DoD Architecture Framework. Version 1.5, 23 April 2007:
11. Vol. I. Definitions and Guidelines. Accessible at: http://www. defenselink.mil/cio-nii/docs/DoDAF-Volume-I.pdf
12. . Vol. II. Product Descriptions. Accessible at: http://www.defenselink. mil/cio-nii/docs/DoDAF-Volume-II.pdf.
13. Vol. III. Architecture Data Description. Accessible at: http://www.defenselink.mil/cio-nii/docs/DoDAF-Volume-III.pdf.
14. Dumas, M., Aalst, W. van der, Hofstede, A. (2005). Process-Aware Information Systems: Bridging People and Software Through Process Technology. Wiley.
15. Ferrstl, O.K, Sinz, E.J. (2006).Modeling of business systems using SOM. In: Bernus, P., Mertins, K., Scmidt, G. (Eds.), Handbook on Architectures of Information Systems, 2nd ed. Springer-Verlag, pp. 347-368.
16. Frappier, M., St-Denis, R. (1998). A specication method for cleanroom's black box description. In: Proc. of the Thirty-First Hawaii Intern. Conf. on System Sciences, Kohala Coast, Hawaii, USA, January 6-9. Electronic ed., Vol. 6: Organizational Systems and Technology. IEEE Computer Society, pp. 112-121. Accessible at: http://computer.org/proceedings/hicss/8248/82480112abs.htm.
17. Goikoetxea, A. (2007). Enterprise Architectures and Digital Administration: Planning, Design and Assessment. World Scientific.
18. Gomaa, H., Olimpiew, E.M. (2005). The role of use cases in requirements and analysis modeling. In: Proc. of the 2nd Intern. Workshop on Use Case Modeling (WUsCaM-05): Use Cases in Model-Driven Software Engineering, Montego Bay, Jamaica, October 2-7. Electronic ed. Accessible at: http://www.ie.inf.uc3m. es/wuscam-05/.
19. Griffin, M. (2007). System Engineering and the Two Cultures of Engineering. Boeing Lecture at the Purdue University, 28 March 2007. Accessible at: http://www.spaceref.com/news/viewsr.html?pid=23775.
20. Grotevant, S.M. (1998). Business engineering and process redesign in higher education: Art or science? In: Online Proc. of EDUCAUSE Conf. on Information Technology in Higher Education (CAUSE 98), December 8-11. Washington State Convention & Trade Center, Seattle, Washington. Accessible at: http://net.educause.edu/ir/library/html/cnc9857/cnc9857.html.
21. Hay, D.C. (2002). Requirements Analysis: From Business Views to Architecture. Prentice-Hall.
22. Haskins, C. (2005). Application of patterns and pattern languages to systems engineering. In: Proc. of the 15th Annual Intern. Symposium of the INCOSE on Syst. Eng.: Bridging Industry, Government,& Academia (INCOSE 2005), Rochester, July 10-15.
23. Haskins, C. (2007). Using patterns to transition systems engineering from a technological to social context. Syst. Eng., 11(2), 147-155.
24. Haskins, C. (2008). Using systems engineering to address socio-technical global challenges. In: Proc. of the 6th Annual Conf. on Systems Engineering Research (CSER 2008), Crowne Plaza Redondo Beach & Marina Hotel, Redondo Beach, April 4-5. Accessible at: http://www.gilb.com/tiki-download-file.php? fileId=235.
25. IEEE (1998). Std 1233-1998: IEEE Guide for Developing System Requirements Specifications. Software Engineering Standards Committee of the IEEE Computer Society, USA.
26. Inmon, W.H, Zachman, J.A., Geiger, J.G. (1997). Data Stores, Data Warehousing, and the Zachman Framework: Managing Enterprise Knowledge. McGraw-Hill.
27. Jacobson, I., Christerson, M., Jonson, P., Overgaard, G. (1992). Object-Oriented Software Engineering: A Use Case Driven Approach. Addison-Wesley.
28. Lamsweerde, A. van (2001). Goal-oriented requirements engineering: A guided tour. In: Proc. of the 5th IEEE Intern. Symposium on Requirements Engineering, Toronto, Canada. Accessible at: http://www.info.ucl.ac.be/Research/ Publication/2001/RE01.pdf.
29. Linger, R.C., Mills, H.D., Witt, B.I. (1979). Structured Programming: Theory and Practice. Addison-Wesley.
30. Malan, R., Bredemeyer, D. (1999). Functional Requirements and Use Cases. Bredemeyer Consulting. Accessible at: http://www.bredemeyer.com/pdf-files/ functreq.pdf (last modified: July 25, 2006).
31. Martin, J. (1995). The Great Transition, Using the Seven Disciplines of Enterprise Engineering to Align People, Technology and Strategy. American Management Association.
32. Mayer, B. (1988). Object-Oriented Software Construction. Prentice-Hall.
33. Mayers, M., Kaposi, A. (2004). A First Systems Book: Technology and Management. Imperial College Press.
34. McLean, V.A. (2006). The MITRE Corporation, NET Recruiter. Accessible at: http://www.netrecruiter.net/currentreqs.html.
35. Moore, G.A. (1999). Crossing the Chasm: Marketing and Selling High-Tech Products to Mainstream Customers. Harper Business.
36. Office of Management and Budget (OMB) (1996). Circular No. A-130. Revised. Transmittal Memorandum No. 4. Accessible at: http://www.whitehouse.gov/ omb/circulars/a130/a130trans4.html.
37. Oracle Corporation (OC) (2000). CDM Quick Tour. Release 2.0.0.
38. Prowell, S.J., Trammell, C.J., Linger, R.C., Poore, J.H. (1999). Cleanroom Software Engineering - Technology and Process. Addison-Wesley.
39. Roubtsova, E.E., Roubtsov, S.A. (2006). A feature computation tree model to specify requirements and reuse. In: Proc. of the 8th Intern. Conf. on Enterprise Information Systems (ICEIS-2006), Vol. 3, Information Systems Analysis and Specification, pp. 118-125.
40. Rukanova, B., van Slooten, K., Stegwee, R. (2006). Business process requirements, modeling technique, and standard: How to identify interoperability gaps on a process level. In: Konstantas, D., Bourriéres, J.-P., Léonard, M., Boudjlida, N. (Eds.), Interoperability of Enterprise Software and Applications. Springer, pp. 13-24.
41. Sowa, J.F., Zachman, J.A. (1992). Extending and formalizing the framework for information systems architecture. IBM Syst. J., 31(3), 590-616.
42. Spewak, S.H., Hill, S.C. (1995). Enterprise Architecture Planning: Developing a Blueprint for Data, Applications, and Technology. Wiley.
43. Strassmann, P.A. (1998). What is alignment? Cutter IT Journal, August 1998. Accessible at: http://www.cutter.com/itjournal.html.
44. The Open Ggroup (OG) (2002). The Open Group Architecture Framework TOGAF. Version 8.1.1, Enterprise Edition. Accessible at: http://www.opengroup.org/ architecture/togaf8-doc/arch/.
45. Van den Broek, P., Galvão, I., Noppen, J. (2008). Elimination of constraints from feature trees. In: Proc. of the 12th Intern. Software Product Line Conf., 12 Sept., Limerick, Ireland. Lero International Science Centre, University of Limerick, Ireland, pp. 227-232.
46. Warfield, J.N. (1994). A Science of Generic Design: Managing Complexity Through Systems Design. 2nd ed. Iowa State University Press.
47. Wegmann, A. (2004). On the systemic enterprise architecture methodology (SEAM). In: Proc. of the Int. Conf. on Enterprise Information Systems (ICEIS 2003), Angers, France.
48. Wegmann, A., Balabko, P., Le, L-S., Regev, G, Rychkova, I. (2005). A method and tool for business- IT alignment in enterprise architecture. In: Belo, O., Eder, J., Cunha J.F., Pastor, O. (Eds.), Proc. Of the 17th Conf. on Advanced Information Syst. Engineering (CAiSE '05), Porto, Portugal, 13-17 June.
49. CAiSE Forum, Short Paper Proc., electronic ed. Accessible at:http://www.informatik.unitrier.de/ley/db/conf/caise/caisefo2005. html#WegmannBLRR05.
50. Wells, D. (2006). Modeling business metrics. Part 1: TDWI flash point. Electronic Journal, March 9. The Data Warehousing Institute. Accessible at: http://www.tdwi.org/Publications/display.aspx?id=7884&t=y.
51. Wiegers, K.E. (2003). Software Requirements. 2nd ed., Microsoft Press.
52. Zachman, J.A. (1982). Business systems planning and business information control study: A comparison. IBM Syst. J., 21(1), 31-53.
53. Zachman, J.A. (1987). A framework for information systems architecture. IBM Syst. J., 26(3), 276-292.