Skip to main content Accessibility help
×
  1. Home
  2. Publications
  3. Textbooks
  4. Content Listing

Refine search

Refine search

Access:
Content type:
Publication date:
Apply   From and To filters
Subject: Show more
Journals Show more
Publishers: Show more
Societies Show more
Series: Show more
Collections: Show more

Actions for selected content:

Select all | Deselect all
  • View selected items
  • Export citations
  • Download PDF (zip)
  • Save to Kindle
  • Save to Dropbox
  • Save to Google Drive

Save Search

You can save your searches here and later view and run them again in "My saved searches".

Please provide a title, maximum of 40 characters.
Cancel
×

38536 results in Cambridge Textbooks

Page 1180 of 1927

  • 6 - Compounding

  • Ingo Plag, Heinrich-Heine-Universität Düsseldorf
  • Book:
    Word-Formation in English
    Published online:
    30 April 2019
    Print publication:
    12 July 2018, pp 131-161

  • Summary

    This chapter is concerned with compounds. Section 6.1 focuses on the basic characteristics of compounds, investigating the kinds of element compounds are made of, their internal structure, headedness, and stress patterns. This is followed by descriptions of individual compounding patterns and the discussion of the specific empirical and theoretical problems these patterns pose. In particular, nominal, adjectival, verbal, and neoclassical compounds are examined, followed by an exploration of the syntax-morphology boundary.

  • 3 - Conceptual Data Modeling Using the (E)ER Model and UML Class Diagram

  • from Part I - Databases and Database Design
  • Wilfried Lemahieu, KU Leuven, Belgium, Seppe vanden Broucke, KU Leuven, Belgium, Bart Baesens, KU Leuven, Belgium
  • Book:
    Principles of Database Management
    Published online:
    17 August 2019
    Print publication:
    12 July 2018, pp 38-78

  • Summary

    Chapter Objectives

    In this chapter, you will learn to:

  • • understand the different phases of database design: conceptual design, logical design, and physical design;

  • • build a conceptual data model using the ER model and understand the limitations thereof;

  • • build a conceptual data model using the EER model and understand the limitations thereof;

  • • build a conceptual data model using the UML class diagram and understand the limitations thereof.

    • Opening Scenario

    Sober has decided to invest in a new database and begin a database design process. As a first step, it wants to formalize the data requirements in a conceptual data model. Sober asks you to build both an EER and a UML data model for its business setting. It also wants you to extensively comment on both models and properly indicate their shortcomings.

    In this chapter we start by zooming out and reviewing the database design process. We elaborate on conceptual, logical, and physical database design. We continue the chapter with conceptual design, which aims at elucidating the data requirements of a business process in a formal way. We discuss three types of conceptual data models: the ER model; the EER model; and the UML class diagram. Each model is first defined in terms of its fundamental building blocks. Various examples are included for clarification. We also discuss the limitations of the three conceptual data models and contrast them in terms of their expressive power and modeling semantics. Subsequent chapters continue from the conceptual data models of this chapter and map them to logical and internal data models.

    Phases of Database Design

    Designing a database is a multi-step process, as illustrated in Figure 3.1. It starts from a business process. As an example, think about a B2B procurement application, invoice handling process, logistics process, or salary administration. A first step is requirement collection and analysis, where the aim is to carefully understand the different steps and data needs of the process. The information architect (see Chapter 4) will collaborate with the business user to elucidate the database requirements. Various techniques can be used, such as interviews or surveys with end-users, inspections of the documents used in the current process, etc. During the conceptual design, both parties try to formalize the data requirements in a conceptual data model.

  • 12 - Physical File Organization and Indexing

  • from Part III - Physical Data Storage, Transaction Management, and Database Access
  • Wilfried Lemahieu, KU Leuven, Belgium, Seppe vanden Broucke, KU Leuven, Belgium, Bart Baesens, KU Leuven, Belgium
  • Book:
    Principles of Database Management
    Published online:
    17 August 2019
    Print publication:
    12 July 2018, pp 351-394

  • Summary

    Chapter Objectives

    In this chapter, you will learn to:

  • • grasp the basic principles of storage hardware and physical database design;

  • • understand how data items can be organized into stored records;

  • • identify various methods for primary and secondary file organization;

    • Opening Scenario

    Now that Sober has its relational logical data model from Chapter 6 ready, it wants to understand how it can be physically implemented. The company is also wondering whether there exist any physical means to speed up the response times of frequently used queries.

    This chapter focuses on the most important principles pertaining to the physical organization of records and files. As such, it can be considered as the prerequisite to Chapter 13, which applies these principles in the context of physical database organization. In this way Chapters 12 and 13 are complementary in covering all facets of physical database design – the translation of a logical data model into an internal data model, including the design of indexes to speed up data access.

    First, we present some overall properties of storage devices and the impact of the mechanicals of hard disk drives on the performance aspects of data retrieval. After that, we overview the mapping of logical modeling constructs onto physical concepts, and thus of the logical data model onto the internal model. Then, we briefly discuss record organization, covering the different alternatives to organize physical data records, consisting of individual data fields. After that comes the main body of this chapter, focusing on file organization and covering methods to organize records into physical files, as well as techniques to efficiently search for records with certain characteristics. We discuss several approaches, such as sequential files, hashing and the use of different index types, including B+-trees. Chapter 13 follows on from this chapter, applying the insights gained from the file organization section to the particular context of physical database organization.

    Storage Hardware and Physical Database Design

    Physical database design pertains to the design of an internal data model and to the way in which the logical database concepts discussed in the previous chapters are realized physically as stored records, physical files, and, ultimately, a physical database.

  • 4 - Delivery and Operations

  • Dick Whittington, University of York
  • Book:
    Digital Innovation and Entrepreneurship
    Published online:
    06 December 2018
    Print publication:
    12 July 2018, pp 154-192

  • Summary

    Driving objectives for scalability and growth whilst managing continuing development demands careful consideration and planning. This chapter offers generally-applicable principles and techniques, including: • How required services and materials will be sourced and managed through the supply chain, including standardization and options for out-sourcing • How the desired customer experience will be achieved through the design of a customer journey • How continuing development will be prioritized and planned including technology readiness, requirement prioritization and roadmap design • How development, release and deployment of the offering will be managed and controlled, including variation and source code management • How the offering will be delivered to customers, including through a channel strategy and routes to market For each of these topics relevant principles, considerations and techniques are introduced and illustrated using real-world examples and the rolling case study. Many of the subjects introduced in this chapter are large and sophisticated: the approach adopted is structured and presented at a level to serve the principal needs of the entrepreneur.

  • 2 - Framing the Business

  • Dick Whittington, University of York
  • Book:
    Digital Innovation and Entrepreneurship
    Published online:
    06 December 2018
    Print publication:
    12 July 2018, pp 52-97

  • Summary

    Framing a venture makes a real contribution to its value. It creates a shared and constructive baseline for evaluating choices, giving clarity to the team and to those with whom they need to communicate. It expresses a commonly held, high-level understanding that evolves with the venture and contributes to the process of continuing development. A poorly framed venture results from, and exacerbates, confusion and division. Ad hoc decisions can lead to continuing fragmentation, loss of focus and mounting stress. A business is framed by answering: • What is the mission? • Who is the customer – business ecosystem? • What is the offering, and how is it distinctive? • What is the problem that is solved? • How will success be measured – key objectives and KPIs? • What are the risks to be mitigated or transferred? • What is the plan to make it happen? Each of these answers is developed further by a later chapter. A business idea is introduced as a sample case exercise for illustration throughout the book. Its complete design is incrementally completed as the book progresses. A template for business design is introduced to capture, record and manage the evolving business design.

  • 5 - Derivation without Affixation

  • Ingo Plag, Heinrich-Heine-Universität Düsseldorf
  • Book:
    Word-Formation in English
    Published online:
    30 April 2019
    Print publication:
    12 July 2018, pp 105-130

  • Summary

    This chapter deals with non-affixational word-formation processes. First, three major problems of conversion are discussed. This is followed by an introduction to prosodic morphology with a detailed analysis of some morphological categories that are expressed by chiefly prosodic means, such as truncated names, -y diminutives, clippings, and blends. Finally, abbreviations and acronyms are investigated.

  • 5 - Legacy Databases

  • from Part II - Types of Database Systems
  • Wilfried Lemahieu, KU Leuven, Belgium, Seppe vanden Broucke, KU Leuven, Belgium, Bart Baesens, KU Leuven, Belgium
  • Book:
    Principles of Database Management
    Published online:
    17 August 2019
    Print publication:
    12 July 2018, pp 93-103

  • Summary

    Chapter Objectives

    In this chapter, you will learn to:

  • • understand why it is important to know the basic concepts of legacy databases;

  • • identify the basic building blocks and limitations of the hierarchical model;

  • • identify the basic building blocks and limitations of the CODASYL model.

    • Opening Scenario

    Sober purchased the customer database of Mellow Cab, who recently stepped out of the taxi business after many years at the top. Since Mellow Cab started in the mid-1970s, it was still using outdated database technology. It used CODASYL to store and manage its customer data. Sober is not familiar with this technology and wants to understand its limitations before deciding to either continue with it or invest in a modern DBMS.

    In this chapter we briefly zoom into legacy database technologies and their logical data models. Although these are outdated and semantically inferior to modern database technologies, there are three reasons to review them. Firstly, many firms still struggle with legacy databases due to historical implementations and limited IT budgets – hence, knowing the basic characteristics of these models is essential to the maintenance of the corresponding database applications and the potential migration to modern DBMSs. Secondly, understanding the basics of these legacy models will contribute to better understanding the semantical richness of newer database technologies. Finally, the concept of procedural DML and navigational access originally introduced by these legacy models has also been adopted by more recent databases such as OODBMSs.

    In this chapter we cover both the hierarchical and CODASYL data models. Throughout the discussion, we extensively discuss the expressive power and limitations of both models.

    The Hierarchical Model

    The hierarchical model is one of the first data models developed. The model originated during the Apollo moon missions program conducted by NASA. To manage the huge amount of data collected, IBMdeveloped the Information Management System or IMS DBMS (1966–1968). There is no formal description available and it has lots of structural limitations. Therefore, it is considered legacy.

    The two key building blocks of the hierarchical model are record types and relationship types. A record type is a set of records describing similar entities. Think about a product record type or a supplier record type. A record type has zero, one, or more records. It consists of fields or data items.

  • 18 - Data Integration, Data Quality, and Data Governance

  • from Part IV - Data Warehousing, Data Governance, and (Big) Data Analytics
  • Wilfried Lemahieu, KU Leuven, Belgium, Seppe vanden Broucke, KU Leuven, Belgium, Bart Baesens, KU Leuven, Belgium
  • Book:
    Principles of Database Management
    Published online:
    17 August 2019
    Print publication:
    12 July 2018, pp 590-625

  • Summary

    Chapter Objectives

    In this chapter, you will learn to:

  • • identify the key challenges and approaches for data and process integration;

  • • understand the basic mechanisms of searching unstructured data within an organization and across the World Wide Web;

  • • define data quality as a multidimensional concept and understand how master data management (MDM) can contribute to it;

  • • understand different frameworks and standards for data governance;

  • • highlight more recent approaches in data warehousing, data integration, and governance.

    • Opening Scenario

    Things are going well at Sober. The company has set up a solid data environment based on a solid relational database management system used to support the bulk of its operations. Sober's mobile app development team has been using MongoDB as a scalable NoSQL DBMS to handle the increased workload coming from mobile app users and to provide back-end support for experimental features the team wants to test in new versions of their mobile app. Sober's development and database team is already paying attention to various data quality and governance aspects: the RDBMS is the central source of truth, strongly focusing on solid schema design and regular quality checks being performed on the data. The NoSQL database is an additional support system to handle large query volumes from mobile users in real-time in a scalable manner, but where all data changes are still being propagated to the central RDBMS. This is done in a manual manner, which sometimes leads to the two data sources not being in agreement with each other. Sober's team therefore wants to consider better data quality approaches to implement more robust quality checks on data and make sure that changes to the NoSQL database are propagated to the RDBMS system in a timely and correct manner. Sober also wants to understand how their data flows can be better integrated with their business processes.

    In this chapter we will look at some managerial and technical aspects of data integration. We will zoom in on data integration techniques, data quality, and data governance. As companies often end up with many information systems and databases over time, the concept of data integration becomes increasingly important to consolidate a company's data to provide one, unified view to applications and users.

  • 4 - Affixation

  • Ingo Plag, Heinrich-Heine-Universität Düsseldorf
  • Book:
    Word-Formation in English
    Published online:
    30 April 2019
    Print publication:
    12 July 2018, pp 71-104

  • Summary

    This chapter provides an overview of the affixational word-formation processes of English. First, it discusses how affixes can be distinguished from other entities. This is followed by an introduction to the methodological problems of data gathering for the study of affixation through dictionaries and electronic corpora. Then some general properties that characterize the system of English affixation are introduced, and a survey of a wide range of suffixes and prefixes is presented. Finally, we investigate cases of infixation.

  • 10 - XML Databases

  • from Part II - Types of Database Systems
  • Wilfried Lemahieu, KU Leuven, Belgium, Seppe vanden Broucke, KU Leuven, Belgium, Bart Baesens, KU Leuven, Belgium
  • Book:
    Principles of Database Management
    Published online:
    17 August 2019
    Print publication:
    12 July 2018, pp 255-299

  • Summary

    Chapter Objectives

    In this chapter, you will learn to:

  • • understand the basic concepts of XML, Document Type Definition, XML Schema Definition, Extensible Stylesheet Language, namespaces, and XPath;

  • • process XML documents using the DOM and SAX APIs;

  • • store XML documents using a document-oriented, data-oriented, or hybrid approach;

  • • grasp the key differences between XML and relational data;

  • • map between XML documents and (object-)relational data using table-based mapping, schema-oblivious mapping, schema-aware mapping, and SQL/XML;

  • • search XML data using full-text search, keyword-based search, structured search using XQuery, and semantic search using RDF and SPARQL;

  • • use XML for information exchange in combination with message-oriented middleware (MOM) and web services;

  • • understand other data representation formats such as JSON and YAML.

    • Opening Scenario

    For regulatory and insurance purposes, Sober needs to store a report for each accident. The report should include the date, the location (including GPS coordinates), a summary of what happened and the individuals involved. Furthermore, for each individual Sober needs to know:

  • • the name;

  • • whether he/she is a driver driving a Sober car or not, a pedestrian, or a cyclist;

  • • whether he/she was injured.

    • The report should also include information about aid provided, such as police or ambulance assistance. Sober would like to know the best way to store this report.

    In this chapter, we discuss how to store, process, search, and visualize XML documents, and how DBMSs can support this. We start by looking at the XML data representation standard and discuss related concepts such as DTDs and XSDs for defining XML documents, XSL for visualizing or transforming XML documents, and namespaces to provide for a unique naming convention. This is followed by introducing XPath, which uses path expressions to navigate through XML documents. We review the DOM and SAX API to process XML documents. Next, we cover both the documentand data-oriented approach for storing XML documents. We extensively highlight the key differences between the XML and relational data model. Various mapping methods between XML and (object-)relational data are discussed: table-based mapping, schema-oblivious mapping, schema-aware mapping, and the SQL/XML extension. We also present various ways to search XML data: full-text search, keyword-based search, structured search, XQuery, and semantic search. We then illustrate how XML can be used for information exchange, both at the company level using RPC and message-oriented middleware and between companies using SOAP or REST-based web services.

  • Preface

  • Dick Whittington, University of York
  • Book:
    Digital Innovation and Entrepreneurship
    Published online:
    06 December 2018
    Print publication:
    12 July 2018, pp xvii-xxii

  • Summary

    Most STEM students graduate with a rudimentary and anecdotal appreciation of how digital techniques, technologies and processes apply to business and entrepreneurship. This book bridges that gap. Some readers will have ambitions to start their own businesses, others will intend to join existing start-ups or larger organizations: all students need to understand how business works in the digital economy, to enhance the contribution they offer to a prospective employer. The book also provides a concise and practical introduction to digital innovation and entrepreneurship for those studying a more wide-reaching business study programme. It gives students a thorough grasp of the fundamentals of business in one volume, without the need for a full-blown business curriculum. It is effective with students of many disciplines and situations, from first-year undergraduates through to research staff and those entering the world of business. There are no assumed pre-requisites, other than a broad appreciation of the digital world. Every topic is introduced, explained and illustrated. Where relevant, references are provided to sources for further research or learning.

  • 7 - Intellectual Property and Protection

  • Dick Whittington, University of York
  • Book:
    Digital Innovation and Entrepreneurship
    Published online:
    06 December 2018
    Print publication:
    12 July 2018, pp 285-330

  • Summary

    This chapter is about ensuring a venture benefits from its capabilities and investment by maximizing the value of its intellectual property (IP) and managing risks from deliberate and accidental activity. Failure to protect can rapidly lead to damage and disruption, financial and reputational. It addresses the following: • Protection of IP – trademarks, registered designs, patents, copyright, open source – to establish and crystalize IP value and to protect it from abuse • Protection of confidential information – trade secrets, know-how, non-disclosure • Protection against onerous contracts: licensing, customer service, customer delivery • Protection against damage and intrusion – physical and cyber security • Protection against legal non-compliance – IP infringement, employment law, data protection Risks are illustrated and examined, and protective mechanisms described to enable a reasonable assessment of options and implications. Real-world examples are explained and the rolling case study is developed. The section that addresses protection against onerous contracts refers to three appendices of relevant contractual terms and their implications for the venture.

Page 1180 of 1927