101 Lessons From Enterprise Architecture : Roger Evernden txt
USA : San Bernardino, CA : Designs and Patents Act , 2015Descripción: 208 p. ill. ; 21 cmTipo de contenido:- text
- unmediaded
- volume
- 9781502835659
- HF5548.32 E947 2015
| Imagen de cubierta | Tipo de ítem | Biblioteca actual | Biblioteca de origen | Colección | Ubicación en estantería | Signatura topográfica | Materiales especificados | Info Vol | URL | Copia número | Estado | Notas | Fecha de vencimiento | Código de barras | Reserva de ítems | Prioridad de la cola de reserva de ejemplar | Reservas para cursos | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Libro | CARIBET Biblioteca Arquitectura Colección General CARIBET | General HF5548.32 E947 2015 (Navegar estantería(Abre debajo)) | 1 | Disponible | 91000000042853 | |||||||||||||
| Libro | CARIBET Biblioteca Arquitectura Colección General CARIBET | General HF5548.32 E947 2015 (Navegar estantería(Abre debajo)) | 2 | Disponible | 91000000041772 |
Descripciones mejoradas de Syndetics:
This is a book for enterprise architects and anyone interested in the design of our digital future.It explains 101 clear and simple lessons that the author learned from the practical use of enterprise architecture techniques. These are the common-sense things that you learn from long-years of experience. But they are also the sort of things that can easily get overlooked or forgotten.The 101 topics provide insights and lessons into the way that enterprise architects actually think about architectures, and how they help enterprise change and transformation. It covers many of the fundamental techniques - from ways of working, to how value depends more on dynamic elements than static ones, to open-ended design, and the nature of logic.Each insight uses a two-page format - with a brief explanation and an illustration highlighting the key points in a whimsical or diagrammatic way. There are quotes, such as the one from Einstein about computers being fast and stupid, while humans are slow and brilliant. There are guidelines and recommendations, such as playing with elements in diagram to organize them in a way that makes them less complex and easier to understand. And there are plenty of examples, anecdotes and stories to explain things that are too often omitted from the standard enterprise architecture training programs.Written by an enterprise architect, mentor, and trainer, who regularly helps and guides individuals, teams and companies to apply enterprise architecture techniques in practical and effective ways. "101 Lessons From Enterprise Architecture" is a concise summary of some of the most important techniques in day-to-day enterprise architecture practice. It summarizes valuable knowledge and experience that will benefit anyone starting out in enterprise architecture through to experienced practitioners.It will also provide inspiration and guidance to those in many other disciplines - from IT development and planning, to business strategy and planning, or anyone involved in design for the information age.
Contents:
1. Ways of working (WOW) 6 --
2. Value depends more on dynamic elements than static ones 8 --
3. Each experience is strongly influenced by how we arrive at it 10 --
4. Each Component is influenced by surrounding Components 12 --
5. Slow, inaccurate and brilliant 14 --
6. Make steady and sure progress 16 --
7. Open ended design 18 --
8. The value in bits and bytes 20 --
9. Discarded pieces may have the germ of the next idea 22 --
10. The nature of logic 24 --
11. Separate the dynamic from the static 26 --
12. Old solutions and new solutions 28 --
13. Arrangement versus complexity 30 --
14. Current use and future possibilities 32 --
15. Certainty is a rarity 34 --
16. Systematic design 36 --
17. Leave Plenty of Clues 38 --
18. Unpredictability 40 --
19. Nobody expects the unexpected 42 --
20. Take a Break 44 --
21. Generality and specificity 46 --
22. Function and feeling 48 --
23. Beware of WASTING Effort 50 --
24. Tactically strategic 52 --
25. Look up, look down 54 --
26. Ways of Thinking 56 --
27. Solutions and problems 58 --
28. Completeness 60 --
29. There is no single solution 62 --
30. Right or wrong 64 --
31. Actively reduce entropy 66 --
32. Success is 80% persistence 68 --
33. Success is 80% planning and thinking 70 --
34. Taking the First Step 72 --
35. Small change 74 --
36. The WHole is the Sum of the Parts 76 --
37. Triage 78 --
38. Not all sollutions are technology based 80 --
39. Dynamic plans 82 --
40. Principles and patterns 84 --
41. Smart and dramatic 86 --
42. Resource fit 88 --
43. Get Each Stage Right 90 --
44. Value and importance 92 --
45. Learning on the job 94 --
46. Simple and elegant 96 --
47. Questions 98 --
48. Drawing a blank 100 --
49. Steps or stages 102 --
50. Step by step 104 --
51. Vagueness 106 --
52. The future 108 --
53. Know you know 110 --
54. Perfection 112 --
55. The next level of detail 114 --
56. Simpliflying through organisation 116 --
57. Create or arrange 118 --
58. Going back 120 --
59. Deliver, deliver, deliver 122 --
60. Estimates 124 --
61. Visibility 126 --
62. The unexpected 128 --
63. expectations 130 --
64. Decision log 132 --
65. The small print 134 --
66. Certainty 136 --
67. Traceabilility 138 --
68. Divergence 140 --
69. The cost of omission 142 --
70. Common sense and the obvious 144 --
71. Simplification 146 --
72. Reflection 148 --
73. Stretch versus stretched 150 --
74. Quick and dirty 152 --
75. Trust 154 --
76. Practicality 156 --
77. Play with words 158 --
78. Messy or neat 160 --
79. Start and ends 162 --
80. A or B ? 164 --
81. Issues or vision 166 --
82. 6 up, 9 dowm 168 --
83. Broad or deep 170 --
84. Work the white space 172 --
85. The journey and the destination 174 --
86. Degree and pace of change 176 --
87. The key to a closed door 178 --
88. Difference and similarity 180 --
89. Agendas and minutes 182 --
90. Sufficient sophistication 184 --
91. Balance 186 --
92. Design and use 188 --
93. Endurance 190
94. Design = form + content 192 --
95. Templates and principles 194 --
96. Black box 196 --
97. Famalies inherit DNA 198 --
98. Language 200 --
99. Design language 202 --
100. Consistency and rigidity 204 --
101. Check everything personally 206 --