| |
|
|
|
|
|
|
|
|
1. |
Record Nr. |
UNINA9910790327903321 |
|
|
Autore |
Bente Stefan |
|
|
Titolo |
Collaborative enterprise architecture [[electronic resource] ] : enriching EA with lean, agile, and enterprise 2.0 practices / / Stefan Bente, Uwe Bombosch, Shailendra Langade |
|
|
|
|
|
|
|
Pubbl/distr/stampa |
|
|
Waltham, MA, : Morgan Kaufmann, 2012, c2013 |
|
|
|
|
|
|
|
ISBN |
|
1-283-57267-2 |
9786613885128 |
0-12-415989-3 |
|
|
|
|
|
|
|
|
Edizione |
[1st edition] |
|
|
|
|
|
Descrizione fisica |
|
1 online resource (323 p.) |
|
|
|
|
|
|
Altri autori (Persone) |
|
BomboschUwe |
LangadeShailendra |
|
|
|
|
|
|
|
|
Disciplina |
|
|
|
|
|
|
Soggetti |
|
Management information systems |
Business enterprises - Computer networks |
Information technology - Management |
Software architecture |
|
|
|
|
|
|
|
|
Lingua di pubblicazione |
|
|
|
|
|
|
Formato |
Materiale a stampa |
|
|
|
|
|
Livello bibliografico |
Monografia |
|
|
|
|
|
Note generali |
|
Description based upon print version of record. |
|
|
|
|
|
|
Nota di bibliografia |
|
Includes bibliographical references and index. |
|
|
|
|
|
|
Nota di contenuto |
|
Cover; Collaborative Enterprise Architecture: Enriching EA with Lean, Agile, andEnterprise 2.0 Practices; Copyright; Dedication; Contents; Acknowledgments; Chapter 1: Why Collaborative Enterprise Architecture?; Content; Reasons for this book; Goals and benefits of enterprise architecture; Controlling IT complexity; Aligning business and IT; The gray reality: Enterprise architecture failures; Between success and disappointment; Perspective: Between bird's-eye view and nitty-gritty on the ground; Governance: A host of directives, but no one follows them; Strategy: Marathon or 100m run? |
Transformation: Between standstill and continuous revolutionEnriching EA by Lean, Agile, and Enterprise 2.0 Practices; How this book is structured; Chapter 2: What Is Enterprise Architecture?; Content; The meaning of architecture; Applying architecture to an enterprise; EA applicability and use; Chapter 3: What Enterprise Architects Do: Core Activities of EA; Content; Defining the IT strategy (EA-1); Defining the goals; Stipulating the rules; The Gartner Grid; Identifying the initiatives; |
|
|
|
|
|
|
|
|
|
|
|
The role of an enterprise architect; Modeling the architectures (EA-2) |
Models and views of various architecturesVisualizing cross-relations and transformations; Modeling standards; Evolving the IT landscape (EA-3); Application rationalization; Identifying applications and key performance indicators; Assessing applications; Assessing alternatives; Summary; General IT transformations; SOA transformations; Assessing and building capabilities (EA-4); Competence development for enterprise architects; Competency tree for an enterprise architect; Building the competence; Formalizing enterprise architecture; Team organization; Team composition |
EA team position in the organization structureDeveloping and enforcing standards and guidelines (EA-5); Standardizing on technology usage; Introducing new architectural paradigms; Enforcing standards and guidelines; Monitoring the project portfolio (EA-6); Building the project portfolio; Pushing IT-focused effort into the portfolio; Prioritizing the projects; Auditing the portfolio; Patrolling for architecture conformance; Taking a collective view of portfolio performance; Making it a two-way dialogue; Leading or coaching projects (EA-7); Managing risks involved in IT (EA-8) |
Chapter 4: EA FrameworksContent; What is an EA framework?; The Zachman framework for enterprise architecture; The open group architecture framework (TOGAF); TOGAF architecture development methodology (ADM); TOGAF architecture content framework; TOGAF architecture capability framework; Gartner methodology (formerly META framework); The role and use of EA frameworks; Chapter 5: EA Maturity Models; Content; Applying maturity model to EA; What is a maturity model?; Relevance of maturity models in EA; A rule of thumb for the architectural maturity of an enterprise; OMB EA assessment framework |
Architecture capability maturity model of the US department of commerce |
|
|
|
|
|
|
Sommario/riassunto |
|
Ever-changing business needs have prompted large companies to rethink their enterprise IT. Today, businesses must allow interaction with their customers, partners, and employees at more touch points and at a depth never thought previously. At the same time, rapid advances in information technologies, like business digitization, cloud computing, and Web 2.0, demand fundamental changes in the enterprises' management practices. These changes have a drastic effect not only on IT and business, but also on policies, processes, and people. Many companies therefore embark on enterprise-wide transfo |
|
|
|
|
|
|
|
| |