Larissa T. Moss and Shaku Atre have covered all the bases in a cohesive and Business Intelligence Roadmap is a visual guide to developing an effective. Business Intelligence Roadmap: The Complete Project Lifecycle for Decision- support Applications. Front Cover. L.T. Moss. Addison-Wesley, – pages The Complete Project Lifecycle for Decision Larissa Terpeluk Moss,S. Atre. , English, Book, Illustrated edition: Business intelligence roadmap: the complete project lifecycle for decision-support applications / Larissa T. Moss, Shaku.
,445,291,400,400,arial,12,4,0,0,5_SCLZZZZZZZ_.jpg "business intelligence roadmap larissa moss")
| Author: | Muzil Zoloramar |
| Country: | Iceland |
| Language: | English (Spanish) |
| Genre: | Life |
| Published (Last): | 10 March 2008 |
| Pages: | 292 |
| PDF File Size: | 13.78 Mb |
| ePub File Size: | 14.23 Mb |
| ISBN: | 730-1-63528-718-6 |
| Downloads: | 27885 |
| Price: | Free* [*Free Regsitration Required] |
| Uploader: | Mikagor |
We use cookies to give you the best possible experience. By using our website you agree to our use of cookies. International Function Point Users Group. Home Contact Us Help Free delivery worldwide.
Management Decision Making Computing: Description “If you are looking for laarissa complete treatment of business intelligence, then go no further than this book. Moss and Shaku Atre have covered all the bases in a cohesive and logical order, making it easy for the reader to follow their line of thought.
From early design to ETL to physical database design, the book ties together all the components of business intelligence. This book outlines a methodology that takes into account the complexity of developing lntelligence in an integrated BI environment. The authors walk readers lagissa every step of the process–from strategic planning to the selection of new technologies and the evaluation of application releases.
The book also roadmaap as a single-source guide to the best practices of BI projects. Part I steers readers through the six stages of a BI project: Each chapter describes one of sixteen development steps and the major activities, deliverables, roles, and responsibilities.
All technical material is clearly expressed in tables, graphs, and diagrams. Part II provides five matrices that serve as references for the development process charted in Part I.
Management tools, such as graphs illustrating the timing and coordination of activities, are included throughout the book. The authors conclude by crystallizing their many years of experience in a list of dos, don’ts, tips, and rules of thumb. Both the book and the methodology it describes are designed to adapt to the specific needs of individual stakeholders and organizations.
The book directs business representatives, business sponsors, project managers, and technicians to the chapters that address their distinct responsibilities. The framework of the book allows organizations to begin at any step and enables projects to be scheduled and managed in a variety of ways.
Business Intelligence Roadmap is a clear and comprehensive guide to negotiating the complexities inherent in the development of valuable business intelligence decision-support applications show more. The Best Books of Check out the top books of the year on our page Best Busienss of Looking for beautiful books? Visit our Beautiful Books page and find lovely books for kids, photography lovers and more.
Other books in this series. Enterprise Integration Beth Gold-Bernstein. Request for Proposal Bud Porter-Roth. Peer Reviews in Software Karl E. Principles of the Business Rule Approach Jr. Enterprise Application Integration David S. Effective Requirements Practices Ralph R. A Requirements Pattern Patricia L.
Web Services Anne Thomas Manes. A History of Bisexuality Steven Angelides. Services Blueprint Ravi Kalakota. Proven Portals Dan Sullivan. Enterprise Security David Leon Clark. Back cover copy roadmwp you are busniess for intellience complete treatment of business intelligence, then go no further than this book.
Table of contents About the Authors. The Purpose of This Book. How This Book Is Organized. How to Use This Book. Who Should Read This Book. Guide to the Development Steps.
The Traditional Development Approach. The Cross-Organizational Development Approach. Engineering Stages and the Development Steps. BI Project Team Structure.
Business Intelligence Roadmap : Larissa Terpeluk Moss :
The BI Arbitration Board. Bibliography and Additional Joss. Types of Data Sources. Business Case Assessment Activities. Deliverable Resulting from These Activities. Roles Involved in These Activities. Risks of Not Performing Step. Step 2, Section A: Technical Infrastructure Evaluation Activities. Deliverables Resulting from These Activities. Step 2, Section B: The Effects of Stovepipe Development. The Need for Nontechnical Infrastructure.
Nontechnical Infrastructure Evaluation Activities. Managing the BI Project. Defining the BI Project. Project Goals and Objectives.
Business Intelligence Roadmap : The Complete Project Lifecycle for Decision-Support Applications
Planning the BI Project. Risks of Not Performing Step 3. Interviewees for General Business Requirements. Interviewees for Project-Specific Requirements. Project Requirements Definition Activities.
Risks of Not Performing Step 4.
Top-Down Logical Data Modeling. Project-Specific Logical Data Model. Enterprise Logical Data Model. Logical Data Modeling Participants. Standardized Business Meta Data. Bottom-Up Source Data Analysis. Technical Data Conversion Rules. Business Data Domain Rules. Business Data Integrity Rules. Source Data Selection Process. Key Points of Data Selection. To Cleanse or Not to Cleanse.
Risks of Not Performing Step 5. Best Mosss for Prototyping. Risks of Not Performing Step 6. Meta Data Repository Analysis. The Importance of Meta Data.
Meta Data Repository as Navigation Tool. Groupings of Meta Data Components.
Prioritization of Meta Data Components. Meta Data Repository Challenges. The Logical Meta Model. The Entity-Relationship Meta Model. Meta Data Repository Analysis Activities. Risks of Mos Performing Step 7.
Differences in Database Design Philosophies.
Risks of Not Performing Step 8.
