To save content items to your account,
please confirm that you agree to abide by our usage policies.
If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account.
Find out more about saving content to .
To save content items to your Kindle, first ensure no-reply@cambridge.org
is added to your Approved Personal Document E-mail List under your Personal Document Settings
on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part
of your Kindle email address below.
Find out more about saving to your Kindle.
Note you can select to save to either the @free.kindle.com or @kindle.com variations.
‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi.
‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.
• 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.
• 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.
• 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.
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.
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.
This chapter collects and reflects upon ten key themes that emerge from previous chapters:
• Set and agree the objectives and outcomes
• Deliver something customers need
• Create value from the ecosystem
• Design the business to perform
• Plan for growth and scalability
• Build a culture with the right mix of talent
• Distribute equity to motivate and reward investment
• Control finances and know the runway
• Understand and manage the risk envelope
• Think like an investor in all matters
For each of the key themes, a brief narrative summarizes its applicable contexts and picks out the principal points to be noted.
• understand the importance of SQL in an RDBMS environment;
• use SQL as a data definition language (DDL);
• use SQL as a data manipulation language (DML) for retrieving, inserting, deleting, and updating data;
• define and use views in SQL;
• define indexes in SQL;
• use SQL for granting and revoking privileges;
• understand how SQL can be used to manage metadata.
Opening Scenario
The relational model adopted by Sober needs to serve various information needs. For example, the insurance firm of the company requests an overview of all accidents together with the number of Sober cars involved and the average damage amount per accident. As part of its customer relationship management (CRM) program, the company wants to retrieve the customer with the maximum wait time and offer him or her a free ride-hailing service. Furthermore, Sober also would like to find out which customers have never booked any of its services and target them with a promotion campaign. To implement its eco-friendly tree-planting program, Sober needs to know which customers booked more than 20 Sober ride-sharing services. Finally, the company remembers that one of the limitations of the EER conceptual data model was that it is perfectly possible that customers book either a ride-hailing or ride-sharing service with their own car. To safeguard its data quality, Sober wants to periodically check that this is not the case in its relational database.
In the previous chapter, we dealt with the modeling aspects of relational databases. In this chapter, we elaborate on SQL, which is the lingua franca of RDBMSs and one of the most popular data definition and manipulation languages in use in the industry nowadays. Its core functionality is implemented, with only some minor variations, throughout all RDBMS products. We discuss the SQL language constructs to express a relational model and to formulate queries that retrieve and modify the data in a relational database.
First, we provide an overview of the SQL data definition language (SQL DDL) to define a relational data model. We also discuss how the SQL data manipulation language (SQL DML) can be used for data manipulation such as retrieving data, updating data, inserting new data and deleting existing data. We then elaborate on SQL views and SQL indexes, which are part of the external and internal data model, respectively.
There is a collection of customer delivery terms that it is particularly important to consider when agreeing a delivery contract with a customer. This Appendix gives explanations, cautions and in some cases, optional forms of words for the principal terms. It is important to note that the specific wording adopted may need to be reviewed in the light of applicable legal jurisdictions.
Topics covered include:
• Term of the project
• Payment and payment terms
• Defining the deliverables
• Supplier’s obligations
• Customer’s obligations
• Project management
• IP Rights
• Confidentiality and non-disclosure
• Change management
• Liabilities
• Warranties and disclaimers
• Penalty clauses and liquidated damages
• Termination
• Non-poaching of staff
• Assignment
• Jurisdiction
In the period from the 1990s emerging market financial crises until the North Atlantic financial crisis of 2008, the development of domestic bond markets in developing economies was a prominent agenda item in international financial reform circles. The crises of the 1990s drew attention to the vulnerabilities generated by frequently occurring double mismatches of currency denominations and maturities in the borrowing of emerging economies. This led to a series of reform efforts targeted at both increasing liquidity and the range of borrowers in domestic bond markets. In the aggregate, these efforts were successful: For emerging market economies as a whole, domestic debt now exceeds international debt. Moreover, domestic corporate bond markets have emerged in many countries, often for the first time. However, the nature of market development has been far from uniform, and often has not been in line with government aims. In this paper, we examine the interplay of government and business actors in market development. Drawing on 155 interviews with policy and market actors as well as secondary data, we show that the main explanation of variation in market development lies in the pre-existing structure of financial markets, conceptualized as a heterogeneous set of interest/influence constellations.
What factors explain U.S. participation in multilateral forums that govern finance? Current literature misses the key features of the Federal Reserve, Treasury, and Congress that result in their distinct manners of support for various multilateral arrangements. I revisit the archival record and apply a new understanding to American participation in the Bank for International Settlements (BIS) and Basel Committee on Banking Supervision (BCBS) as the financial regime has evolved since the collapse of fixed parity in the IMF after 1971. I thus explain the puzzle of American ambivalence through an exploration of the fragmented U.S. regulatory system, which inhibits the United States from acting as a unitary, lead actor of multilateral negotiations. Hence, American coordination must take place both domestically and internationally for an agreement to emerge.
Communication Skills for Business Professionals is a student-friendly introduction to the principles and practice of effective communication in the workplace. Engagingly written and full of real-life examples, it explains the key theories underpinning communication strategies and encourages students to consider how to apply them in a contemporary business environment. After working through foundation topics such as understanding the audience, persuasion and influence, negotiation and conflict management, and intercultural complexities, students will explore the various modes and contexts of workplace communication including meetings, oral communication, written reports and correspondence. The text incorporates discussion of new digital technologies such as virtual real-time communication, and dedicates an entire chapter to the specific considerations involved in writing for the web. With its emphasis on Australian contexts and examples, Communication Skills for Business Professionals is an excellent introduction to the world of professional communication.
There is a standard trade-off in compensation contracts between the provision of incentives and insurance. We hypothesize that this trade-off influences the precision with which firm performance is measured. We find that firm outcomes are measured less precisely when chance plays a large role in these outcomes. Further, this precision is determined through the choice of shares outstanding. This has several novel implications. Nominal stock prices can remain constant over time, and firms with unpredictable cash flows should have more shares and lower stock price levels, all else equal. We find evidence consistent with these implications.
The European Union’s regulation for chemical safety (REACH) addresses the registration, evaluation, assessment, and consequent authorization (or restriction) of chemicals which are potentially harmful for both public health and the environment. The current study aims at ascertaining the costs and benefits of the REACH framework for the Austrian economy under major uncertainties, and draws on a wide range of databases on public and workplace health, chemical accidents in households, and the potential environmental impacts of harmful chemicals.
The uncertainties in the REACH system assessments of the effects of chemicals on health lie not only in the insufficiency of scientific evidence but also in the economic evaluation of effects on health, especially in regard to the value of statistical life (VSL), and the economic value of diseases attributed to chemicals.
This benefit-cost analysis (BCA) of the REACH system in Austria therefore takes into account these manifold uncertainties by designing a conservative baseline scenario and by varying all determinants in comprehensive sensitivity analyses. Projected over a period of about 30 years, this paper provides evidence that the REACH system most probably leads to net benefits for the Austrian economy (benefit-cost ratio of about 10.6) even though many benefits are still highly uncertain or unknown.