Free Ebook A Practical Guide to Enterprise Architecture, by James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. J
Collect the book A Practical Guide To Enterprise Architecture, By James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. J start from currently. Yet the extra method is by gathering the soft file of the book A Practical Guide To Enterprise Architecture, By James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. J Taking the soft data can be saved or stored in computer system or in your laptop. So, it can be more than a book A Practical Guide To Enterprise Architecture, By James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. J that you have. The simplest way to expose is that you can additionally conserve the soft file of A Practical Guide To Enterprise Architecture, By James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. J in your appropriate as well as available gizmo. This problem will expect you too often review A Practical Guide To Enterprise Architecture, By James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. J in the extra times greater than chatting or gossiping. It will not make you have bad habit, but it will certainly lead you to have much better practice to read book A Practical Guide To Enterprise Architecture, By James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. J.
A Practical Guide to Enterprise Architecture, by James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. J
Free Ebook A Practical Guide to Enterprise Architecture, by James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. J
Schedule A Practical Guide To Enterprise Architecture, By James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. J is among the valuable well worth that will make you always abundant. It will certainly not suggest as rich as the cash give you. When some individuals have lack to deal with the life, individuals with lots of e-books in some cases will certainly be better in doing the life. Why must be book A Practical Guide To Enterprise Architecture, By James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. J It is actually not suggested that e-book A Practical Guide To Enterprise Architecture, By James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. J will certainly provide you power to reach everything. Guide is to read as well as just what we implied is the publication that is read. You could additionally see how the e-book qualifies A Practical Guide To Enterprise Architecture, By James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. J and also varieties of publication collections are giving right here.
As understood, adventure and experience about lesson, amusement, and knowledge can be gained by only checking out a publication A Practical Guide To Enterprise Architecture, By James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. J Even it is not directly done, you can recognize more regarding this life, about the world. We offer you this appropriate and also simple method to gain those all. We offer A Practical Guide To Enterprise Architecture, By James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. J as well as several book collections from fictions to science in any way. Among them is this A Practical Guide To Enterprise Architecture, By James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. J that can be your companion.
Exactly what should you assume much more? Time to get this A Practical Guide To Enterprise Architecture, By James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. J It is easy then. You could just sit and also remain in your place to get this book A Practical Guide To Enterprise Architecture, By James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. J Why? It is on the internet book establishment that offer so many compilations of the referred publications. So, just with net connection, you could appreciate downloading this book A Practical Guide To Enterprise Architecture, By James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. J as well as varieties of publications that are hunted for now. By going to the web link page download that we have supplied, guide A Practical Guide To Enterprise Architecture, By James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. J that you refer a lot can be located. Simply save the asked for publication downloaded and after that you can enjoy the book to review every time and place you really want.
It is really easy to review the book A Practical Guide To Enterprise Architecture, By James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. J in soft data in your gizmo or computer. Once again, why need to be so difficult to obtain guide A Practical Guide To Enterprise Architecture, By James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. J if you can pick the simpler one? This website will relieve you to choose and also choose the very best collective publications from the most wanted vendor to the launched book just recently. It will certainly constantly update the collections time to time. So, attach to internet and also see this site consistently to obtain the new publication everyday. Now, this A Practical Guide To Enterprise Architecture, By James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. J is your own.
In A Practical Guide to Enterprise Architecture, six leading experts present indispensable technical, process, and business insight into every aspect of enterprise architecture. You'll find start-to-finish guidance for architecting effective system, software, and service-oriented architectures; using product lines to streamline enterprise software design; leveraging powerful agile modeling techniques; extending the Unified Process to the full software lifecycle; architecting presentation tiers and user experience; and driving the technical direction of the entire enterprise. For every working architect and every IT professional who wants to become one.
- Sales Rank: #1113743 in Books
- Published on: 2003-11-07
- Released on: 2003-10-28
- Format: AC-3
- Original language: English
- Number of items: 1
- Dimensions: 9.00" h x 1.10" w x 6.90" l, 1.41 pounds
- Binding: Paperback
- 336 pages
From the Back Cover
- Comprehensive explanation of enterprise architecture concepts and methods
- Extend the Rational Unified Process to include Enterprise Architecture
- Unified view of the various architectural disciplines to create strategic blueprints
- Perspectives on Enterprise Development and Technology
Indispensable technical, process, and business insight from leading enterprise architects
Many organizations today face the challenge of designing, building, and maintaining large-scale distributed enterprise systems that are able to adapt to changing business needs. Many repeat the mistakes of others, resulting in cost overruns, blown deadlines, and lost opportunity. Today's business climate places additional burden on IT to deliver. Ever-adapting business drivers can diverge from the capabilities of the enterprise IT systems today, especially if the systems are complex, fragile, and intolerant of change. Enterprise architecture can help future-proof IT investments made today.
A Practical Guide to Enterprise Architecture helps readers create adaptive architecture strategies for successfully implementing enterprise architectures. This classic handbook goes beyond theory and presents strategies that are based on experiences within organizations across multiple industry verticals. Behind each opinion, technique, and principle is a wealth of knowledge provided by some of the best-known industry thought leaders today.
This book's authors have architected industrial-strength software and infrastructure for many of the world's leading firms-in financial services, telecommunications, media, and e-business. They present practical guidance, candid assessments of existing practice, and detailed examples from their own experience. Coverage includes:
- Strategies for enterprise architecture-which ones work and why
- Proven "product line" practices for streamlining the design of enterprise software
- Understanding how to translate key business drivers into enterprise architecture output
- Agile architectural and modeling techniques-presented by their creator, Scott Ambler
- Architecting presentation tiers, user experience, and usability methods to create a reusable base of core assets
- Overcoming the challenges of transitioning to agile methods
- Identifying architecture enabling human resource practices
Whether you're a working architect or plan to become one, A Practical Guide to Enterprise Architecture will be your timely, trusted advisor-today and for years to come.
About the Author
JAMES McGOVERN, Enterprise Architect for Hartford Financial Services, is a co-author of the bestselling books Java Web Services Architecture and Agile Enterprise Architecture. SCOTT W. AMBLER, senior consultant with Ronin International, specializes in O-O analysis/design, agile modeling, and architectural audits of mission-critical systems. His best sellers include Agile Modeling and The Elements of Java Style. MICHAEL E. STEVENS, Software Architect for Hartford Financial Services, is a columnist for Developer.com. He co-authored Java Web Services Architecture. JAMES LINN, consultant at Hartford Technology Services, co-authored XQuery Kick Start. VIKAS SHARAN is managing partner of Lozoic and architecture team member at Baypackets. ELIAS JO, Systems Architect for The New York Times Digital, has architected and/or led development at DeutscheBank, Citibank, Standard & Poor, and ADP.
Excerpt. © Reprinted by permission. All rights reserved.
Preface
In today's business climate, the rules of competition have changed. Organizations are forced to eliminate the process of reinventing the wheel each time a new business problem arises that forces the enhancement of an existing system or implementation of a new one. Enterprise architecture is the practice that allows organizations to build foundations they need to survive and adapt to present and future business challenges. Sound enterprise architecture supports the ability to stay agile, provides for increased return on investment, and creates a framework for making future technology decisions.
Enterprise architecture identifies the main components of an organization and how components in the organization's nervous system function together to achieve defined business objectives. These components include personnel, business processes, technology, financial information and other resources. If decisions about components and their interrelationships are uncoordinated, minimally effort and resources will be duplicated; performance and management problems will arise and will result in the loss of agility. Enterprise architecture done correctly will ensure the choice of appropriate components and will specify how each component will operate together in a fluid manner that increases organizational efficiencies.
Enterprise architecture is one of the most challenging roles in information technology today. Many aspects of the role are technical while much more of it is about interaction. Many people who have this position have significant responsibility but do not have authority or control. Enterprise architecture as an area of study allows one to focus on interesting, complex problems, to advance on the corporate ladder, and to maintain technical competencies while making a colossal difference to the enterprise.
Enterprise architecture requires skill sets not normally taught in university curriculum or acquired on the job. Even good architectures are rarely accepted without formidable challenges. The successful architect has to overcome any aversion to politics and become the evangelist of architecture in the eyes of its various stakeholders. Architects cannot simply buy into any vision that is articulated. Any involvement in the implementation of enterprise architecture requires one to understand it. The most successful architecture will have an architect that can describe the motivation behind architectural choices. Likewise, a successful architecture has an architect who leads the architecture team, the development team, the technical direction of the enterprise, and sometimes the organization itself. The primary focus of this book is to be a guide and trusted advisor to those who want to be successful in this role.A wise enterprise architect once worked for a very well-respected organization (name intentionally withheld). He was passionately engaged in a conversation with a senior executive about what direction the organization should take with its information systems. His recommendations fell on deaf ears until he asked the executive three very simple questions:
- How can we have a viable customer relationship management strategy when we do not even know where all of our customer's data reside?
- How does our technology spending equate to enabling our strategic business goals?
- Does our organization have an operational process model?
As you can surmise, the answers to these questions were not known. Many executives in information technology are not knowledgeable about what it takes to guide the architecture in the direction that results in the biggest bang for the buck. Sadly, many executives have lost control of the ship they steer, which has resulted in bloated infrastructures and conclusions being made on whims rather than on sound principle-based judgment and experience.In many organizations, the annual budget cycle starts with clueless, disruptive questions such as "How many servers do we have?" or "Let's get the new Intel 3333 GHz machines as desktops." None of these statements is appropriate for a discussion about enterprise architecture. A good architecture addresses the following:
- The organization's business and information needs
- Leverage of the synergistic relationship between return on investment (ROI) and total cost of ownership (TCO)
- The ability to support migration from the current state (as-is)
- The ability to support easy migration to the organization's desired future state
- Ways to support the business objectives of reducing costs, improving operational service, and increasing revenue
Many organizations will claim to have an architect who creates architecture. Others will attempt to buy a nicely packaged architecture from one of the Big Five consulting firms without having a clue as to what they are getting. If your architecture does not address the following principles, you may be doing more harm than good:
- Data are separated from logic (business functions).
- The principles of modularity are observed by ensuring that each component within the enterprise architecture performs only one or two discrete tasks.
- Functions are separated into differentiated tasks that are generic and self-contained.
- The architecture is self-documenting. If it isn't, something is wrong.
- All data and artifacts that are generated by an organization are managed and maintained by the same organization.
- The architecture is technically feasible and can be implemented at a reasonable cost within a reasonable time frame.
- The architecture is traceable from business requirement to technology implementation.
- Logical architecture is separated from physical architecture.
The term architect was derived from the building trade. The building of a corporation's nervous system is directly comparable to building a house. One may say, "I have no clue about how to build a $50 million dollar skyscraper, let alone a $50,000 house." Yet the response to both tasks is simple: They are accomplished by creating blueprints.
Blueprints show how a house will be constructed. They provide multiple views, each expressing its own level of detail. One view of the house may include all the electrical circuits that are of extreme value to an electrician. Likewise, the plumber will need a blueprint to show where all the pipes and water should go. Enterprise architecture diagrams the blueprints for all of the people within an organization so they know how to build an agile enterprise. The enterprise architecture blueprint is meant to provide sufficient detail to allow the idea to become a reality when put in the hands of skilled professionals, much as a house blueprint does.
We do not mean to imply that building a skyscraper is as easy as building a house. A decade ago, Garlan stated, "As the size and complexity of software systems increases, the design problem goes beyond the algorithms and data structures of the computation: designing and specifying the overall system structure emerges as a new kind of problem. . . . This is the software architecture level of design." Garlan 1992.
Enterprise architecture within this context seeks to solve for intellectual manageability. Architecture of large projects and their complexity arise from broad scope, massive size, novelties of the minute, currently deployed technologies, and other factors. The goal of enterprise architecture in this situation is to provide a manner to hide unnecessary detail, simplify difficult-to-understand concepts, and break down the problem into better-understood components (decomposition).
Complexity also arises within organizations due to processes used in building the system, the number of people who are involved with construction, the introduction of the possibility of outsourcing and geographically dispersed teams, and the organizational funding model. Ideally, enterprise architecture can assist, but not eliminate, the management of the process by providing clearer separation of concerns, enhancing communications, and making dependencies more manageable.
Building enterprise architecture is difficult but not impossible, as long as one sticks to architectural principles. The architectural blueprint defines what should be built, not how or why. Project plans document the how, and their creation is best left to individuals who have studied project management. The why is best left to one's business customer, as all architecture should be business-driven.
A word of advice: A good architecture provides agility but also provides constraints. A highly successful architecture will remove points of decision from those who are traditionally accustomed to having a free-for-all, making decisions impulsively or reacting to the opinions of those who are uninformed. Good architects will see things that make their heads hurt, but their aspirin is in knowing that their hard work and persistence will result in the reduction of future problems. Helping others see the value of enterprise architecture is crucial, as it brings benefit to the enterprise even if decisions have local consequences.
The idea for this book came about during a lunchtime conversation between two of its authors. They were reminiscing about why the computer field was the only field in which one could become a manager, director, or even vice president without any computing experience. During this lunchtime conversation, we compared the computer field to such other professional fields as accounting, the practice and enforcement of law, and medicine.
Imagine that the town you live in is looking to hire a new police chief. Can you have confidence in the chief if he has never been a police officer? Furthermore, what if the prospective chief does not know how to use a gun and has no knowledge of proper investigation procedures? Extend this concept by envisioning a former McDonald's manager applying to be a partner at an accounting or law firm simply because he is a leader. The partners in the legal and accounting fields are leaders, but they also retain current knowledge of their professions and can argue a case or balance one's books. With relevant experience, the prospective police chief is a leader, too, and most likely remembers how to write a parking ticket and perform other cop-on-the-street duties.
Getting to the root of this problem cannot be done quickly. Unlike other fields, in the computer field you can have the title of architect but not necessarily know your job. The information technology field is constantly evolving and ever-changing. For the motivated, it requires long hours reading numerous books by the thought leaders of the industry. Even for the most diligent, the goal of achieving knowledge and enlightenment may never be fulfilled.
Many businesses are faced with such challenging problems as technology changing rapidly, employees with limited skill sets, smaller budgets, and less tolerance for failure. The only way one can be successful in this new order is to learn a new strategy. Today's businesspeople no longer have the opportunity to learn from their failures.
This book presents several provocative alternatives and serves as a leader, teacher, and guide to help you manage the chaos. It will challenge both the conventional and the contrarian's wisdom. This book is written by some of the brightest information technology thought leaders with the purpose of helping you create an agile enterprise using techniques learned on the battlefield of life.Come to success.
The goal of this book is to share insight gathered by industry thought leaders in an easy-to-read and practical style. This book contains many leading-edge examples that illustrate how enterprise architecture can be applied to existing business and technology issues to help one focus on how to think concretely about enterprise architecture while providing solutions to today's problems. The following topics are covered within this book:- Systems architecture
- Software architecture
- Service-oriented architecture
- Product-line practice
- Methodology
- Enterprise unified process
- Agile architecture
- Agile modeling
- Presentation tier architecture
- User experience and usability
- Data architecture
- Thought leadership
Authors and readers alike have their own religion when it comes to the best way a given topic should be explained. The examples contained within this book will not be blow-by-blow descriptions of the subjects. There are books better suited for this goal. We shall strictly focus on content that provides an additional value-added experience.
The author team also believes this book is not one to curl up with and read from cover to cover. The topics contained within this book mandate further study and even implementation before they can be fully appreciated.
AudienceThis book is suitable for all information technology professionals who have the passion and discipline to study technology to the level required for successful implementation. Ideally, the reader of this book should be a project manager, senior developer, software architect, or enterprise architect employed by a Fortune 1000 organization or by a consulting firm that serves these enterprises. This book is also suitable for such information technology executives as chief information officers (CIO), chief technology officers (CTO), and others within the IT technology management chain.
Since architect is not a title one is granted based merely on the number of years on the job, this author team has intentionally avoided making any references to years of experience in the profession. We assume that the reader has basic familiarity with emerging technologies and their use in solving existing problems. We provide references in Appendix E hat the readers may refer to if they are interested in drilling deeper into any particular topic.The advice, diagrams, and recommendations contained within this book may be used however you desire, with the sole exception that you may not claim you were the author. The publisher, authors, and their respective employers do not provide any form of warranty or guarantee this book's usefulness for any particular purpose.
Developing an enterprise architecture is a difficult task. It requires refinement of overlapping and conflicting requirements; invention of good abstractions from those requirements; formation of an efficient, cost-effective implementation; and ingenious solutions to isolated coding and abstraction evils. Additionally, enterprise architects must manage all this work up to a successful finish, all at the lowest possible cost in time and money. The only way this can be truly accomplished is by remaining agile.
In an agile approach, architects assume responsibilities beyond modeling and conceptual design. They must minimally serve as technical advisors to project managers. This is analogous to industrial engineers and their relationships to architects in the construction fields.
Many of the thoughts presented will assume an agile approach to explaining the solutions to the problems presented. An understanding of agile methods for software development will help readers become more successful in implementing practical enterprise architecture.
Most helpful customer reviews
13 of 24 people found the following review helpful.
Good introduction
By Martin Omander
This is a good introduction to the field of enterprise architecture. It generally doesn't go into technical detail, so anyone should be able to get something out of it. Also, it is to the point and so mercifully short. The only reason that I didn't give it 5 stars is that the book has six authors and it shows. There is no red thread running through the chapters, even if the chapters themselves are good.
16 of 18 people found the following review helpful.
Don't bother
By ML
book does not discuss enterprise architecture -- doesn't cover some of the methods, frameworks, and the purpose for EA. Doesn't even give a definition of what EA is. Contains several disjointed chapters with topics that are remotely related to EA but does not even begin to tie together or address the queston "what is EA?" You can do better with free online resources.
11 of 14 people found the following review helpful.
The title is misleading. The book is NOT a practical guide to Enterprise Architecture
By R. Aalders
The title 'A Practical Guide to Enterprise Architecture' led me to expect a book that dealt with the processes, challenges and techniques for creating an ENTERPRISE architecture. It does not. The book is about various technology frameworks. The Contents lists Systems Architectures, Solution Architectures and Service Oriented Architectures but not Enterprise Architecture. Enterprise Architecture is skimmed over in the Preface. The book barely touches on Zachman and Spewak and Hill. It ignores FEAF, TEAF, TOGAF, PERA, C4ISR, the Clinger-Cohen Act and other ENTERPRISE stuff completely. Enough said. Whatever this book is, is it is NOT a practical guide to ENTERPRISE Architecture. The book may be of use to technical architects designing solution-frameworks to support an Enterprise Architecture.
A Practical Guide to Enterprise Architecture, by James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. J PDF
A Practical Guide to Enterprise Architecture, by James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. J EPub
A Practical Guide to Enterprise Architecture, by James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. J Doc
A Practical Guide to Enterprise Architecture, by James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. J iBooks
A Practical Guide to Enterprise Architecture, by James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. J rtf
A Practical Guide to Enterprise Architecture, by James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. J Mobipocket
A Practical Guide to Enterprise Architecture, by James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. J Kindle
Tidak ada komentar:
Posting Komentar