Bøger udgivet af Technics Publications LLC

Escrito por mais de 120 praticantes de gerenciamento de dados, o guia DAMA® que estabelece um corpo de conhecimento em gerenciamento de dados (DMBOK®) é a mais impressionante compilação dos princípios do gerenciamento de dados e melhores práticas já montadas. Este guia oferece para o gerenciamento de dados, profissionais de TI, executivos, profissionais do conhecimento, educadores e pesquisadores uma estrutura de trabalho para gerenciar seus dados e as informações da infra-estrutura. O DMBOK® é equivalente ao PMBOK® ou BABOK®, fornecendo informações sobre Governança de Dados, Arquitetura de Dados, Desenvolvimento de Dados, Operações de banco de dados, Segurança de dados, Dados mestre e de referência, Data Warehousing e Inteligência de negócios, Gerenciamento de documentos e conteúdos, Gerenciamento de metadados, Qualidade de dados e desenvolvimento profissional. O DMBOK® faz referencia também ao dicionário de gerenciamento de dados da DAMA ( ISBN9780977140046). O DMBOK® esta disponível também em formato eletrônico (ISBN 9780977140084).Como uma introdução oficial para o gerenciamento de dados, os objetivos do guia DMBOK® são: Construir um consenso para uma aplicação, geralmente visível das funções do gerenciamento de dados; Fornecer definições padrões para os usos comuns das funções do gerenciamento de dados, entregas, papéis e outras terminologias; Documentar os princípios voltados para o gerenciamento de dados; Apresentar uma visão geral neutra em relação a vendedores de soluções e produtos visando praticar boas práticas comuns, métodos e técnicas sabiamente adotados, e abordagens alternativas significativas; Esclarecer o escopo e os limites do gerenciamento de dados; Agir como uma referência que guia os leitores para recursos adicionais e para maiores entendimentos Os editores são Mark Mosley, Editor de desenvolvimento, Michael Brackett, Editor de produção, Susan Early, Editor assistente, e Deborah Henderson (Presidente da fundação DAMA, e vice-presidente da Pesquisa e Educação da DAMA Internacional), e o posfácio por Michael Brackett. Prefácio por John Zachman: A publicação começou como não trivial, e necessária compilação de artigos e fatos de assuntos pouco entendidos do gerenciamento de dados orquestrados por algumas pessoas do capítulo da DAMA de Chicago. Como havia pouco material de referência de fundo sobre o assunto, foi o único na época. Cresceu para se tornar um manual pragmático dos praticantes e que certamente merece um lugar em toda pratileira dos profissionais que de alguma maneira estão envolvidos com o gerenciamento de dados.

Are you struggling with the formal design of your organisation''s data resource? Do you find yourself forced into generic data architectures and universal data models? Do you find yourself warping the business to fit a purchased application? Do you find yourself pushed into developing physical databases without formal logical design? Do you find disparate data throughout the organisation? If the answer to any of these questions is Yes, then you need to read Data Resource Design to help guide you through a formal design process that produces a high quality data resource within a single common data architecture. Most public and private sector organisations do not consistently follow a formal data resource design process that begins with the organisation''s perception of the business world, proceeds through logical data design, through physical data design, and into implementation. Most organisations charge ahead with physical database implementation, physical package implementation, and other brute-force-physical approaches. The result is a data resource that becomes disparate and does not fully support the organisation in its business endeavours. This book describes how to formally design an organisation''s data resource to meet its current and future business information demand. It builds on "Data Resource Simplexity", which described how to stop the burgeoning data disparity, and on "Data Resource Integration", which described how to understand and resolve an organisation''s disparate data resource. It describes the concepts, principles, and techniques for building a high quality data resource based on an organisation''s perception of the business world in which they operate. Like "Data Resource Simplexity" and "Data Resource Integration", Michael Brackett draws on five decades of data management experience building and managing data resources, and resolving disparate data in both public and private sector organisations. He leverages theories, concepts, principles, and techniques from a wide variety of disciplines, such as human dynamics, mathematics, physics, chemistry, philosophy, and biology, and applies them to properly designing data as a critical resource of an organisation. He shows how to understand the business environment where an organisation operates and design a data resource that supports the organisation in that business environment.

Business data integration is a complex problem that must be solved when organizations change or enhance their internal structures. The goal of this book is to present a simple yet thorough resource that describes the challenges of business data integration and the solutions to these challenges such as schema integration, illustrated through an Operational Data Store (ODS) case study. This book contains three sections spanning ten chapters. Section I, Foundational Concepts, will provide you with the necessary basic concepts and discuss schema integration. Section II, Preparation and Design, introduces the case study and we will reverse engineer each of the data sources to create a set of data dictionary reports which will provide us with the meta data we need to apply the schema integration process. Section III, Physical Implementation, will present scripts to populate each of the source databases and spreadsheets and use reports to create Extract, Transform, and Load (ETL) specifications. The ten chapters within these three sections are:Chapter 1 – Introduction and RoadmapChapter 2 – What is an Operational Data Store (ODS)?Chapter 3 – What is Schema Integration?Chapter 4 – The Role of the ODS within DW ArchitecturesChapter 5 – Reverse Engineering the four Source SchemaChapter 6 – Designing the Interim SchemaChapter 7 – Preparing the ETL SpecificationsChapter 8 – Designing the Physical ODS Database ModelChapter 9 – Designing Our ETL processes with SSISChapter 10 – Data Quality Profiling

Do you enjoy completing puzzles? Perhaps one of the most challenging (yet rewarding) puzzles is delivering a successful data warehouse suitable for data mining and analytics. The Analytical Puzzle describes an unbiased, practical, and comprehensive approach to building a data warehouse which will lead to an increased level of business intelligence within your organisation. New technologies continuously impact this approach and therefore this book explains how to leverage big data, cloud computing, data warehouse appliances, data mining, predictive analytics, data visualisation and mobile devices. This book describes an unbiased, practical, and comprehensive approach to building a data warehouse which will lead to an increased level of business intelligence within your organisation. New technologies continuously impact this approach and therefore this book explains how to leverage big data, cloud computing, data warehouse appliances, data mining, predictive analytics, data visualisation and mobile devices.

Many Cultures, One Team is an essential aid for anyone who leads, is a member of, consults with, or supports global teams.  Starting from the premise that the concept of team is culturally bound, Catherine Mercer Bing provides guidance for improving team function and performance. Drawing on her extensive experience in supporting global teams, she challenges team leaders and members to reflect on their cultural assumptions – to improve their cultural metacognition – and provides key advice concerning engagement, productivity, and human process interactions on teams. Global competition is fierce, and the timeframe within which businesses maintain their competitive advantage is now counted in months rather than years. One important source of competitive advantage is human behavior. Team leaders that manage the subtle, but powerful, forces of group dynamics and culture achieve better business outcomes. Team leaders that fail to identify and manage these subtle forces in real-time risk having their plans thwarted.

Here you will learn how to develop an attractive, easily readable, conceptual, business-oriented entity/relationship model, using a variation on the UML Class Model notation. This book has two audiences: Data modelers (both analysts and database designers) who are convinced that UML has nothing to do with them; and UML experts who don't realize that architectural data modeling really is different from object modeling (and that the differences are important).David Hay's objective is to finally bring these two groups together in peace. Here all modelers will receive guidance on how to produce a high quality (that is, readable) entity/relationship model to describe the data architecture of an organization. The notation involved happens to be the one for class models in the Unified Modeling Language, even though UML was originally developed to support object-oriented design. Designers have a different view of the world from those who develop business-oriented conceptual data models, which means that to use UML for architectural modeling requires some adjustments. These adjustments are described in this book. David Hay is the author of Enterprise Model Patterns: Describing the World, a comprehensive model of a generic enterprise. The diagrams were at various levels of abstraction, and they were all rendered in the slightly modified version of UML Class Diagrams presented here. This book is a handbook to describe how to build models such as these. By way of background, an appendix provides a history of the two groups, revealing the sources of their different attitudes towards the system development process.

Learn essential techniques from data warehouse legend Bill Inmon on how to build the reporting environment your business needs now!Answers for many valuable business questions hide in text. How well can your existing reporting environment extract the necessary text from email, spreadsheets, and documents, and put it in a useful format for analytics and reporting? Transforming the traditional data warehouse into an efficient unstructured data warehouse requires additional skills from the analyst, architect, designer, and developer. This book will prepare you to successfully implement an unstructured data warehouse and, through clear explanations, examples, and case studies, you will learn new techniques and tips to successfully obtain and analyze text.Master these ten objectives: Build an unstructured data warehouse using the 11-step approach Integrate text and describe it in terms of homogeneity, relevance, medium, volume, and structure Overcome challenges including blather, the Tower of Babel, and lack of natural relationships Avoid the Data Junkyard and combat the "Spider's Web" Reuse techniques perfected in the traditional data warehouse and Data Warehouse 2.0,including iterative development Apply essential techniques for textual Extract, Transform, and Load (ETL) such as phrase recognition, stop word filtering, and synonym replacement Design the Document Inventory system and link unstructured text to structured data Leverage indexes for efficient text analysis and taxonomies for useful external categorization Manage large volumes of data using advanced techniques such as backward pointers Evaluate technology choices suitable for unstructured data processing, such as data warehouse appliances

Join Simon on a quest to uncover the value of Enterprise Architecture (and it's not what you think it is!)Simon is a seasoned Enterprise Architect who joins a corporation in New York as their first-ever Vice President of Enterprise Architecture. On his very first day, he meets the global Chief Executive Officer (CEO) who asks Simon 'What do you do?' Simon's reply triggers the CEO to respond in a way that our hero least expects. What follows is a journey across continents and oceans in which Simon uncovers the true meaning of Enterprise Architecture, who is doing it, and how successful they are.On his travels, Simon teams up with senior executives around the world to integrate Enterprise Architecture into their strategies and business plans, and to innovate in the architecture of their enterprise. Everyone he meets has some wisdom to offer, and is looking for his in return. Finally, Simon has to make a choice between the kind of Enterprise Architect he used to be and the one he has become.Join the characters in this sequel to the highly-acclaimed business novel fruITion, as they contribute to Simon's journey and he makes his final choice. Share in his thoughts and experiences, and join the author in observing key messages along the journey.

Here you'll find one key to the development of a successful information system: Clearly capture and communicate both the abstract and concrete building blocks of data that describe your organization. In 1995, David Hay published Data Model Patterns: Conventions of Thought - the groundbreaking book on how to use standard data models to describe the standard business situations. Enterprise Model Patterns: Describing the World builds on the concepts presented there, adds 15 years of practical experience, and presents a more comprehensive view.You will learn how to apply both the abstract and concrete elements of your enterprise's architectural data model through four levels of abstraction:Level 0: An abstract template that underlies the Level 1 model that follows, plus two meta models: Information Resources. In addition to books, articles, and e-mail notes, it also includes photographs, videos, and sound recordings. Accounting. Accounting is remarkable because it is itself a modeling language. It takes a very different approach than data modelers in that instead of using entities and entity classes that represent things in the world, it is concerned with accounts that represent bits of value to the organization.Level 1: An enterprise model that is generic enough to apply to any company or government agency, but concrete enough to be readily understood by all. It describes: People and Organization. Who is involved with the business? The people involved are not only the employees within the organization, but customers, agents, and others with whom the organization comes in contact. Organizations of interest include the enterprise itself and its own internal departments, as well as customers, competitors, government agencies, and the like. Geographic Locations. Where is business conducted? A geographic location may be either a geographic area (defined as any bounded area on the Earth), a geographic point (used to identify a particular location), or, if you are an oil company for example, a geographic solid (such as an oil reserve). Assets. What tangible items are used to carry out the business? These are any physical things that are manipulated, sometimes as products, but also as the means to producing products and services. Activities. How is the business carried out? This model not only covers services offered, but also projects and any other kinds of activities. In addition, the model describes the events that cause activities to happen. Time. All data is positioned in time, but some more than others.Level 2: A more detailed model describing specific functional areas: Facilities Human Resources Communications and Marketing Contracts Manufacturing The LaboratoryLevel 3: Examples of the details a model can have to address what is truly unique in a particular industry.

Rediscover how your organization works and where it can be improved by using simple, yet powerful techniques!How Work Gets Done will provide the business or IT professional with a practical working knowledge of Business Process Management (BPM). This book is written in a conversational style that encourages you to read it from start to finish and master these objectives: Learn how to identify the goals and drivers important to your organization and how to align these with key performance measures Understand how business strategies, business policies, and operational procedures need to be connected within a Business Process Architecture Know the basic building blocks of any business process - Inputs, Outputs, Guides, and Enablers Learn how to create a BPM Center of Excellence in your organization Acquire the skills to establish a BPM methodology addressing Enterprise-level, Process-Level, and Implementation-Level priorities Learn how to build a Process Competency Framework encompassing all BPM stakeholders Obtain the knowledge to improve a process step-by-step with easy to use techniques and templates such as swimlanes and flowcharts