Enterprise architecture at work: Modelling, communication, and analysis

Enterprise Architecture at Work: Modelling, Communication, and Analysis

Volumn , Issue , 2005, Pages 1-334

  Lankhorst, Marc ^a   Iacob, M E ^a   Jonkers, H ^a   Van Der Torre, L ^b,j   Proper, H A ^c   Arbab, F ^b,d   De Boer, F S ^b,d   Bonsangue, M ^d   Hoppenbrouwers, S J B A ^c   Van Zanten, G Veldhuijzen ^c   Groenewegen, L ^d   Van Buuren, R ^a   Slagter, R J ^a   Campschroer, J ^e   Steen, M W A ^a   Stam, A W ^d,e   Wieringa, R J ^f   Van Eck, P A T ^f   Krukkert, D ^f   Ter Doest, H W L ^a   Van Leeuwen, D ^a   Fennema, P ^a   Jacob, J ^b   Bosma, H ^e   Cuvelier, M J ^g   Penders, P G M ^h   Bekius, S F ⁱ   Janssen, W P M ^a   more..

^a TELEMATICA INSTITUUT   (Netherlands)

^b CWI   (Netherlands)

^c RADBOUD UNIVERSITY NIJMEGEN   (Netherlands)

^d LEIDEN UNIVERSITY   (Netherlands)

^e Ordina   (Netherlands)

^f UNIVERSITY OF TWENTE   (Netherlands)

^g Stichting Pensioenfonds ABP   (Netherlands)

^h ABN AMRO Corporate Research   (Netherlands)

ⁱ Dutch Tax and Customs Administration   (Netherlands)

^j DELFT UNIVERSITY OF TECHNOLOGY   (Netherlands)

more..

Author keywords

[No Author keywords available]

Indexed keywords

EID: 84892048357     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1007/3-540-27505-3     Document Type: Book

References (170)

1. Acme (1998), http://www-2.cs.cmu.edu/~acme/.
2. Alter S, Ein-Dor P, Lynne Markus M, Scott J, Vessey I (2001), Does the Trend Toward E-Business Call for Changes in The Fundamental Concepts of Information Systems? A Debate. Communications of AIS, 5(10), April.
3. Ambler SW (2002), Agile Modeling - Effective Practices for Extreme Programming and the Unified Process. Wiley, New York.
4. Amdahl GM, Blaauw GA, Brooks Jr FP (1964), Architecture of the IBM System/360, IBM Journal of Research and Development, 8(2):21-36.
5. Aquilani F, Balsamo S, Inverardi P (2001), Performance analysis at the software architectural design level, Performance Evaluation, 45(2-3), July.
6. Baeten J C M, Weijland WP (1990), Process Algebra. Cambridge Tracts in Theoretical Computer Science 18. Cambridge University Press, Cambridge.
7. Basel II (2004), Basel II: International Convergence of Capital Measurement and Capital Standards: a Revised Framework, Basel Committee Publications No. 107, June. http://www.bis.org/publ/bcbs107.htm.
8. Bass L, Clements P, Kazman R, (1998), Software Architecture in Practice. Addison-Wesley, Reading, Massachusetts.
9. Bayens G, Commandeur A (2004), De Architect als Econoom: 'Kostenbewust ontwerpen', Landelijk Architectuur Congres (LAC2004), Nieuwegein, 30 November-1 December (in Dutch).
10. Bergstra JA, Ponse A, Smolka SA (eds.) (2001), Handbook of Process Algebra. Elsevier, Amsterdam.
11. Biemans F P M, Lankhorst MM, Teeuw WB, Van De Wetering RG (2001), Dealing with the Complexity of Business Systems Architecting. Systems Engineering, 4(2):118-133.
12. BiZZdesign (2004), http://www.bizzdesign. com.
13. Blanchard BS, Fabrycky WJ (1990), Systems Engineering and Analysis. Prentice Hall, Englewood Cliffs, New Jersey.
14. Booch G, Rumbaugh J, Jacobson I (1999), The Unified Modeling Language User Guide. Addison-Wesley, Reading, Massachusetts.
15. Bosch J, Grahn H (1998), Characterising the Performance of Three Architectural Styles. Proc. First International Workshop on Software and Performance, Santa Fe, New Mexico.
16. Brooks FP (1975), The Mythical Man-Month: Essays on Software Engineering. Addison-Wesley, Reading, Massachusetts.
17. Buschmann F, Meunier R, Rohnert H, Sommerlad P, Stal M (1996), A System of Patterns: Pattern-Oriented Software Architecture. Wiley, New York.
18. Business Process Management Initiative (2003), Business Process Modeling Notation. Working Draft (1.0), Aug. http://www.bpmi.org.
19. Buuren R Van, Jonkers H, Iacob, M-E, Strating P (2004), Composition of Relations in Enterprise Architecture Models. In Ehrig H et al. (eds.), Graph Transformations, Proc. Second International Conference on Graph Transformation (ICGT 2004), Rome, Italy, LNCS 3256, pp. 39-53. Springer, Berlin.
20. C4ISR Architecture Working Group (1997), C4ISR Architecture Framework Version 2.0, US Department of Defense, December 18, 1997. http://www.c3i.osd. mil/org/cio/i3/AWG-Digital-Library/pdfdocs/fw.pdf.
21. CIO Council (2004), Federal Enterprise Architecture Framework (FEAF), http://www.cio.gov.
22. Clinger-Cohen Act (1996), Information Technology Management Reform Act, August 8. http://wwwoirm.nih.gov/policy/itmra.html.
23. CMMI Product Team (2002), Capability Maturity Model Integration (CMMI), Version 1.1, Staged Representation, CMU/SEI-2002-TR-029, ESC-TR-2002-029, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, Pennsylvania.
24. rd Edition. IT Governance Institute, Rolling Meadows, Illinois. http://www.isaca.org/cobit.htm.
25. Conway ME (1968), How do committees invent? Datamation, 14(4):28-31.
26. Creasy PN, Ellis G (1993), A Conceptual Graph Approach to Conceptual Schema Integration. In Proc. ICCS'93, Conceptual Graphs for Knowledge Representation: First International Conference on Conceptual Structures, Quebec, Canada.
27. Cruse DA (2000), Meaning in Language - An Introduction to Semantics and Pragmatics. Oxford University Press, New York.
28. Dai Q, Kauffman R (eds.) (2002), B2B e-commerce revisited: revolution or evolution. Special section in Electronic Markets, 12 (2).
29. Davenport T, Short JE (1990), The New Industrial Engineering: Information Technology and Business Process Redesign, Sloan Management Review, Summer: 309-330.
30. th IEEE International Enterprise Distributed Object Computing Conference (EDOC'04), Monterey, California, September 20-24.
31. th Hawaii International Conference on System Sciences (HICSS'05), Hawaii, January.
32. Di Marco A, Inverardi P (2004), Compositional Generation of Software Architecture Performance QN Models. In Magee J, Szyperski C, and Bosch J, (eds.), Proc. Fourth Working IEEE/IFIP Conference on Software Architecture, pp. 37-46, Oslo, Norway.
33. Dijkstra EW (1968), Structure of the 'THE'-Multiprogrammeming System, Communications of the ACM, 11(5):341-346.
34. Eager D, Sevcik K (1986), Bound hierarchies for multiple-class queuing networks. Journal of the ACM, 33:179-206.
35. st World Congress on Formal Methods, Toulouse, France.
36. EFQM (2003), EFQM Excellence Model, EFQM Brussels Representative Office, Brussels. http://www.efqm.org/model-awards/model/excellence-model.htm
37. Eriksson, H-E, Penker M (1998), Business Modeling with UML: Business Patterns at Work. Wiley, New York.
38. Falkenberg ED, Hesse W, Lindgreen P, Nilsson BE, Oei J L H, Rolland C, Stamper RK, Van Assche F J M, Verrijn-Stuart AA, Voss K (eds.) (1998), A Framework of Information Systems Concepts, IFIP WG 8.1 Task Group FRISCO.
39. FEAPMO (2004), Federal Enterprise Architecture, http://www.feapmo.gov.
40. Ferris C, Farrell J (2003), What are Web Services? Communications of the ACM, 46(6):31.
41. Finkelstein A, Kramer J, Nuseibeh B, Finkelstein L, Goedicke M (1992), Viewpoints: A Framework for Integrating Multiple Perspectives in System Development, International Journal of Software Engineering and Knowledge Engineering, Special issue on Trends and Research Directions in Software Engineering Environments, 2(1):31-58.
42. Fitzsimmons JA, Fitzsimmons MJ (2000), New Service Development: Creating memorable experiences. Sage, Thousand Oaks, California.
43. Fowler M (2003), Who Needs an Architect? IEEE Software, July-August: 2-4.
44. nd edition. Addison-Wesley, Springfield, Virginia.
45. Franckson M, Verhoef TF (eds.) (1999), Information Services Procurement Library. Ten Hagen & Stam, Den Haag.
46. Frankel DS (2003), Model Driven Architecture: Applying MDA to Enterprise Computing. Wiley, New York.
47. Franken H, Bal R, Van Den Berg H, Janssen W, De Vos H (2000), Architectural Design Support for Business Process and Business Network Engineering. Inter-national Journal of Services Technology and Management, 1(1):1-14.
48. st edition. Addison-Wesley, Reading, Massachusetts.
49. Garrett GR (2004), Volkswagen of America's Enterprise Architecture Story, Presentation at the ACT/IAC Enterprise Architecture (EA) Best Practices Seminar, July 23.
50. Gartner (2004), Gartner's Research Note of 7 January 2004.
51. Goldstein SM, Johnston R, Duffy J, Rao J (2002), The Service Concept: The Missing Link in Service Design Research? Journal of Operations Management, 20(2):121-134.
52. Grice HP (1975), Logic and Conversation. In: Cole P, Morgan JL (eds.), Syntax and Semantics III: Speech Acts. pp. 41-58. Academic Press, New York.
53. Hall AD (1962), A Methodology for Systems Engineering. Van Nostrand, Princeton, New Jersey.
54. Hall AD (1969), Three-Dimensional Morphology of Systems Engineering. IEEE Transactions on System Science and Cybernetics, SSC-5(2):156-160.
55. Hammer M (1990), Reengineering Work: Don't Automate, Obliterate, Harvard Business Review, July-August: 109-144.
56. Hardjono TW, Bakker R J M (2001), Management van processen: Identificeren, besturen, beheersen en vernieuwen. Kluwer, Dordrecht (in Dutch).
57. Harel D, Pnueli A (1985), On the development of reactive systems. In Apt K, (Ed.), Logics and Models of Concurrent Systems, pp. 477-498. NATO ASI Series. Springer, Berlin.
58. Harel D, Rumpe B (2004), Meaningful Modeling: What's the Semantics of 'Semantics'? IEEE Computer, October: 64-72.
59. Harrison P, Patel N (1992), Performance Modelling of Communication Networks and Computer Architectures. Addison-Wesley, Reading, Massachusetts.
60. Henderson JC, Venkatraman N (1993), Strategic alignment: leveraging information technology for transforming operations, IBM Systems Journal, 32(1):4-16.
61. Hermanns H, Herzog U, Katoen J-P (2002), Process Algebra for Performance Evaluation, Theoretical Computer Science, 274(1-2):43-87.
62. Hoque F (2000), e-Enterprise: Business Models, Architecture, and Components. Cambridge University Press, Cambridge.
63. Horton W (1991), Illustrating Computer Documentation, Wiley, New York.
64. Iacob M-E, Jonkers H (2004), Quantitative Analysis of Enterprise Architectures, Proc. INTEROP-ESA 2005 Conference, 23-25 February, Geneva.
65. th International Conference on Enterprise Information Systems (ICEIS 2004), 14-17 April, Porto, Portugal.
66. IBM Corp. (1964), IBM System/360 Principles of Operation. IBM Systems Reference Library, File No. S360-01, Form A22-6821-0. Poughkeepsie, New York.
67. IDEF (1993), Integration Definition for Function Modeling (IDEF0) Draft, Federal Information Processing Standards Publication FIPSPUB 183. U. S. Department of Commerce, Springfield, Virginia.
68. IEEE Computer Society (2000), IEEE Std 1471-2000: IEEE Recommended Practice for Architecture description of Software-Intensive Systems. IEEE, New York.
69. IFIP-IFAC Task Force (1999), GERAM: Generalised Enterprise Reference Architecture and Methodology, Version 1.6.3, March (Published also as Annex to ISO WD15704). http://www.fe.up.pt/~jjpf/isf2000/v1-6-3.html.
70. Illeris S (1997), The Service Economy: A Geographical Approach, Wiley, New York.
71. ISO (2000), Quality Management Systems - Requirements, ISO 9000:2000, International Organization for Standardization, Geneva.
72. ITU (1995a), Open Distributed Processing - Reference Model - Part 2: Foundations, ITU Recommendation X.902 | ISO/IEC 10746-2, International Telecommunication Union, Geneva.
73. ITU (1995b), Open Distributed Processing - Reference Model - Part 3: Architecture, ITU Recommendation X.903 | ISO/IEC 10746-3, International Telecommunication Union, Geneva.
74. ITU (1996), Open Distributed Processing - Reference Model - Part 1: Overview, ITU Recommendation X.901 | ISO/IEC 10746-1, International Telecommunication Union, Geneva.
75. ITU (1997) Open Distributed Processing - Reference Model - Part 4: Architectural Semantics, ITU Recommendation X.904 | ISO/IEC 10746-4, International Telecommunication Union, Geneva.
76. Jacob J (2004), The RML tutorial, CWI, Amsterdam. http://homepages.cwi. nl/~jacob/rml
77. Jacobson I, Booch G, Rumbaugh J (1999), The Unified Software Development Process. Addison-Wesley, Reading, Massachusetts.
78. Jagannathan R (1995), Data flow Models, In Zomaya EY (ed.), Parallel and Distributed Computing Handbook. McGraw-Hill, New York.
79. th Hawaii International Conference on System Sciences (HICCS'03), IEEE Computer Society Press, Silver Spring, Maryland.
80. Jonkers H, Boekhoudt P, Rougoor M, Wierstra E (1999), Completion Time and Critical Path Analysis for the Optimisation of Business Process Models. In Obaidat M, Nisanci A, Sadoun B (eds.), Proc. 1999 Summer Computer Simulation Conference, pp. 222-229, Chicago, Illinois.
81. Jonkers H, De Boer F, Bonsangue M, Van Buuren R, Groenewegen L, Hoppenbrouwers S J B A, Lankhorst MM, Proper HA, Stam A, Van Der Torre L, Veldhuijzen Van Zanten G (2004a), Concepts for Architecture Description, Archi-Mate 2.2.1, version 3.0, Telematica Instituut, Enschede.
82. Jonkers H, Lankhorst MM, Buuren R Van, Hoppenbrouwers S, Bonsangue M, Van Der Torre L (2004b), Concepts for Modelling Enterprise Architectures, International Journal of Cooperative Information Systems, special issue on Architecture in IT, Vol. 13, No. 3, Sept. 2004, pp. 257-287.
83. Jonkers H, Swelm M Van (1999), Queuing Analysis to Support Distributed System Design. Proc. 1999 Symposium on Performance Evaluation of Computer and Telecommunication Systems, pp. 300-307, Chicago, Illinois.
84. Kalakote R, Robinson M (2001), e-Business 2.0. Addison-Wesley, Reading, Massachusetts.
85. Kaplan R, Norton D (1992), The Balanced Scorecard - Measures That Drive Performance, Harvard Business Review, January-February: 71-79.
86. th International Conference on Software Engineering, pp. 81-90, Sorento, Italy.
87. Koning H (2002), Guidelines Concerning Readability of IT-Architecture Diagrams version 1.0, May 17, 2002, http://www.cs.vu.nl/~henk/research/via/ guidelines-readability-020517b.doc.
88. Kotonya G, Sommerville I (1992), Viewpoints for Requirements Definition. IEE/BCS Software Engineering Journal, 7(6):375-387.
89. Krogstie J, Lindland OI, Sindre G (1995), Defining Quality Aspects for Conceptual Models, In Falkenberg ED, Hesse W, Olive A (eds.), Information Systems Concepts: Towards a consolidation of views, Proc. IFIP international working conference on information system concepts, pp. 216-231. Chapman & Hall, London.
90. Kruchten P (1995), Architectural Blueprints - The'4+1' View Model of Software Architecture, IEEE Software, 12(6):42-50.
91. nd edition. Addison-Wesley, Reading, Massachusetts.
92. Labovitz G, Rosansky V (1997), The Power of Alignment. Wiley, New York.
93. Lindland OI, Sindre G, Sölvberg A (1994), Understanding Quality in Conceptual Modeling, IEEE Software, 11(2):42-49.
94. Lung, C-H, Jalnapurkar A, El-Rayess A (1998), Performance-oriented software architecture analysis: An experience report. Proc. First International Workshop on Software and Performance, Santa Fe, New Mexico.
95. Martin, J (1982), Strategic Data-Planning Methodologies. Prentice Hall, Englewood Cliffs, New Jersey.
96. Martin, J (1989), Information Engineering (3 vols.). Prentice Hall, Englewood Cliffs, New Jersey.
97. Martin RC (2002), Agile Software Development Principles, Patterns, and Practices, Prentice Hall, Englewood Cliffs, New Jersey.
98. Mayer RJ, Menzel CP, Painter MK, De Witte PS, Blinn T, Perakath B (1995), Information Integration for Concurrent Engineering (IICE), IDEF3 Process Descrition Capture Method Report, Interim Technical Report April 1992-September 1995. Knowledge Based Systems, College Station, Texas.
99. McGovern J, Ambler SW, Stevens ME, Linn J, Sharan V, Elias KJ (2004), A Practical Guide to Enterprise Architecture. Pearson Education, Upper Saddle River, New Jersey.
100. Medvidovic N, Taylor RN (2000), A Classification and Comparison Framework for Software Architecture Description Languages, IEEE Transactions on Software Engineering, 26(1):70-93.
101. Menzel C, Mayer RJ (1998), The IDEF Family of Languages. In Bernus P, Mertins K, Schmidt G (eds.), Handbook on Architectures of Information Systems, vol. 1 of International Handbooks on Information Systems, Chap. 10, pp. 209-241. Springer, Berlin.
102. Miller GA (1956), The Magical Number Seven, Plus or Minus Two: Some Limits on Our Capacity for Processing Information. Psychological Review, 63:81-97.
103. Nadler DA, Gerstein MS, Shaw RB, (1992), Organizational Architecture: Designs for Changing Organizations. Jossey-Bass, San Francisco.
104. NASCIO (2003), NASCIO Enterprise Architecture Maturity Model Version 1.3, National Association of State Chief Information Officers. https://www.nascio. org/hotIssues/EA/EAMM.pdf
105. Nonaka I, Takeuchi H (1991), The Knowledge-Creating Company. Harvard Business Review, November-December: 97-130.
106. Nuseibeh BA (1994), A Multi-Perspective Framework for Method Integration. PhD thesis, Imperial College, University of London.
107. Object Management Group (2002), UML Profile for Enterprise Distributed Object Computing Specification. http://www.omg.org/docs/ptc/03-09-05.pdf.
108. Object Management Group (2003a), Unified Modeling Language (UML) Specification: Infrastructure, Version 2.0. http://www.omg.org/docs/ptc/03-09- 15.pdf.
109. Object Management Group (2003b), UML 2.0 Superstructure Specification. http://www.omg.org/docs/ptc/03-08-02.pdf.
110. Object Management Group (2003c), XML Metadata Interchange (XMI), Version 2.0. http://www.omg.org/cgi-bin/doc?formal/03-05-02
111. Object Management Group Architecture Board (2001), Model Driven Architecture (MDA), Miller J, Mukerji J (eds.), ormsc/2001-07-01, Object Management Group. http://www.omg.org/docs/ormsc/01-07-01.pdf.
112. ODMG (2000), Using XML as an Object Interchange Format, Object Data Management Group. http://www.odmg.org/.
113. Olle TW, Hagelstein J, Macdonald IG, Rolland C, Sol HG, Van Assche F J M, Verrijn-Stuart AA (1988), Information Systems Methodologies: A Framework for Understanding. Addison-Wesley, Reading, Massachusetts.
114. Pahl G, Beitz W (1986), Konstruktionslehre. Handbuch für Studium und Praxis. Springer, Berlin.
115. Parker MM, Benson RJ (1989), Enterprise-wide Information Management: Stateof-the-Art Strategic Planning, Journal of Information Systems Management, 6(3):14-23.
116. Paulk M, Curtis B, Chrissis M, Weber C (1993), Capability Maturity Model for Software (Version 1.1), Technical Report CMU/SEI-93-TR-024, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, Pennsylvania.
117. Peirce CS (1969a), Volumes I and II - Principles of Philosophy and Elements of Logic. Collected Papers of C. S. Peirce. Harvard University Press, Boston, Massachusetts.
118. Peirce CS (1969b), Volumes III and IV - Exact Logic and The Simplest Mathematics. Collected Papers of C. S. Peirce. Harvard University Press, Boston, Massachusetts.
119. Peirce CS (1969c), Volumes V and VI - Pragmatism and Pragmaticism and Scientific Metaphysics. Collected Papers of C. S. Peirce. Harvard University Press, Boston, Massachusetts.
120. Peirce CS (1969d), Volumes VI and VIII - Science and Philosophy and Reviews, Correspondence and Bibliography. Collected Papers of C. S. Peirce. Harvard University Press, Boston, Massachusetts.
121. Proper HA (ed.) (2001), ISP for Large-Scale Migrations, Information Services Procurement Library. Ten Hagen & Stam, Den Haag.
122. Proper HA (2004), Da Vinci - Architecture-Driven Information Systems Engineering. Nijmegen Institute for Information and Computing Sciences, University of Nijmegen.
123. Putman JR (1991), Architecting with RM-ODP, Prentice Hall, Englewood Cliffs, New Jersey.
124. Rechtin E, Maier MW (1997), The Art of Systems Architecting. CRC Press, Boca Raton, Florida.
125. Reeves J, Marashi M, Budgen D (1995), A Software Design Framework or How to Support Real Designers, IEE/BCS Software Engineering Journal, 10(4):141-155.
126. Rittgen P (2000), A Modelling Method for Developing Web-Based Applications. Proc. International Conference IRMA 2000, Anchorage, Alaska, pp. 135-140.
127. Romani MB (2003), Using the Enterprise Architecture to Quantify the Benefits of Information Technology Projects, IR204L2/March 2003. Logistics Management Institute, McLean, Virginia.
128. Roozenburg N F M, Eekels J (1995), Product Design: Fundamentals and Methods. Wiley, New York.
129. Rueping A (2003), Agile Documentation: A Pattern Guide to Producing Lightweight Documents for Software Projects. Wiley, New York.
130. Sarbanes-Oxley Act (2002), http://www.law.uc.edu/CCL/SOact/toc.html.
131. nd Edition. Springer, Berlin.
132. Schefstroem D, Van Den Broek G (1993), Tool Integration: Environments and Frameworks. Wiley, New York.
133. Schomig A, Rau H (1995), A Petri Net Approach for the Performance Analysis of Business Processes. Technical Report 116, Lehrstuhl für Informatik III, Universitat Wurzburg.
134. Smith C (1990), Performance Engineering of Software Systems. Addison-Wesley, Reading, Massachusetts.
135. Smith JM, Smith D C P (1977), Database Abstractions: Aggregation and Generalization, ACM Transactions on Database Systems, 2:105-133.
136. Sowa JF, Zachman JA (1992), Extending and Formalizing the Framework for Information Systems Architecture, IBM Systems Journal, 31(3):590-616.
137. Spitznagel B, Garlan D (1998), Architecture-based Performance Analysis. Proc. 1998 Conference on Software Engineering and Knowledge Engineering, San Francisco Bay.
138. st International Symposium on Leveraging Applications of Formal Methods (ISOLA'04), Paphos, Cyprus.
139. th IEEE International Enterprise Distributed Object Computing Conference (EDOC'04), Monterey, California, September 20-24.
140. Steen M W A, Lankhorst MM, Wetering RG Van De (2002), Modelling Networked Enterprises, in Proc. Sixth International Enterprise Distributed Object Computing Conference (EDOC'02), Lausanne, Switzerland, September, pp. 109-119.
141. Stevens M (2002), Service-Oriented Architecture Introduction, Part 1. www.developer.com/design/article.php/1010451, April.
142. Teeuw WB, Berg, H Van Den (1997), On the Quality of Conceptual Models. In Liddle SW (ed.), Proc. ER'97 Workshop on Behavioral Models and Design Transformations: Issues and Opportunities in Conceptual Modeling, UCLA, Los Angeles. http://osm7.cs.byu.edu/ER97/workshop4/tvdb.html.
143. The Open Group (2002), The Open Group Architectural Framework (TOGAF) Version 8 'Enterprise Edition'. The Open Group, Reading, UK. http://www.opengroup.org/togaf/.
144. Treacy M, Wiersema, F (1997), The discipline of market leaders. Perseus Publishing, Reading, Massachusetts.
145. th International Conf. on Protocol Specification, Testing, and Verification, pp. 15-28.
146. UN/CEFACT (2004), http://www.unece.org/cefact/.
147. US Treasury (2004), Treasury Enterprise Architecture, http://www.ustreas.gov/teaf/.
148. Van Bon J (ed.) (2002), IT Service Management - An Introduction - Based on ITIL. Van Haren Publishing, Zaltbommel.
149. Van Der Sanden W A M, Sturm B J A M (1997), Informatiearchitectuur, de infrastructurele benadering. Panfox, Rosmalen (in Dutch).
150. Van Der Zee H, Laagland P, Hafkenscheid B (eds.) (2000), Architectuur als Management Instrument - Beheersing en Besturing van Complexiteit in het Netwerktijdperk. Ten Hagen & Stam, Den Haag (in Dutch).
151. Van Eck P A T, Blanken H, Wieringa RJ (2004), Project GRAAL: Towards operational architecture guidelines. International Journal of Cooperative Information Systems, 13(3):235-255.
152. th International Conference on Enterprise Information Systems (ICEIS 2004), Porto, Portugal, 14-17 April 2004.
153. Van Velzen R C G, Van Oosten J N A, Snijders T, Hardjono TW (2002), Procesmanagement en de SqEME-benadering. Kluwer, Dordrecht.
154. Venkatraman N (1995), IT-enabled Business Transformation: From Automation to Business Scope Redefinition, Sloan Management Review, Fall: 32-42.
155. Veryard R (2004), Business-Driven SOA 2 - How business governs the SOA process, CBDI Journal, June.
156. W3C (1999), XSL Transformations 1.0, World Wide Web Consortium. http://www.w3.org/TR/xslt.
157. W3C (2000), XML 1.0, World Wide Web Consortium. http://www.w3.org/XML/.
158. W3C (2001), XML Schema 1.0, World Wide Web Consortium. http://www.w3.org/XML/Schema.
159. Weill P, Vitale M (2002), What IT Infrastructure Capabilities Are Needed to Implement E-Business Models? MIS Quarterly Executive, 1(1):17-34.
160. Weinberg GM (1988), Rethinking Systems Analysis & Design. Dorset House Publishing, New York.
161. Wieringa RJ (1996), Requirements Engineering: Frameworks for Understanding. Wiley, New York.
162. Wieringa RJ (1998a), Postmodern Software Design with NYAM: Not Yet Another Method. In Broy M, Rumpe B (eds.), Requirements Targeting Software and Systems Engineering, LNCS 1526, pp. 69-94. Springer, Berlin.
163. Wieringa RJ (1998b), A Survey of Structured and Object-Oriented Software Specification Methods and Techniques, ACM Computing Surveys, 30(4):459-527.
164. Wieringa RJ (2003), Design Methods for Reactive Systems: Yourdon, Statemate and the UML. Morgan Kaufmann, San Francisco.
165. Wieringa RJ, Blanken HM, Fokkinga MM, Grefen P W P J (2003), Aligning application architecture to the business context. Proc. Conference on Advanced Information System Engineering (CaiSE'03), LNCS 2681, pp. 209-225. Springer, Berlin.
166. Wijers GM, Heijes H (1990), Automated Support of the Modelling Process: A view based on experiments with expert information engineers. In Steinholtz B, Sölvberg A, Bergman L (eds.), Proc. Second Nordic Conference on Advanced Information Systems Engineering (CaiSE'90), LNCS 436, pp. 88-108. Springer, Berlin.
167. Williams LG, Smith CU (1998), Performance Evaluation of Software Architectures. Proc. First International Workshop on Software and Performance, Santa Fe, New Mexico, October, pp. 164-177.
168. Wood-Harper AT, Antill L, Avison DE (1985), Information Systems Definition: The Multiview Approach. Blackwell Scientific, Oxford, UK.
169. Woods WA, Schmolze JG (1992), The KL-ONE family, Computers & Mathematics with Applications, 23(2/5):133-177.
170. Zachman JA (1987), A Framework for Information Systems Architecture, IBM Systems Journal, 26(3):276-292.