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.
In this chapter, we review some of the risk management implications of the regulation of banks and insurance companies. Banks are largely regulated through local implementation of the Basel II and Basel III Accords. Insurance regulation is more varied, but the development of the Solvency II framework in the European Union has influenced regulation more widely, and so we focus on Solvency II as an example of a modern insurance regulatory system.
This chapter describes the software design document. This is the first step in the software life cycle where we leave the abstract plane and begin to think more concretely about the product. The structure of this chapter is as follows. First, we discuss (Section 13.1) that we are at the point of creating a bridge from the system requirements to the actual code.
This chapter presents the “business” view of medical software. It takes a company to bring an idea to market and, ultimately, clinical use. We begin with a brief description of issues related to entrepreneurship (Section 6.1): Should somebody who has a promising idea consider starting a company on their own?
In this chapter, we distinguish funding liquidity from market liquidity, and idiosyncratic liquidity from systemic liquidity. We discuss the nature of highly liquid assets, and methods by which a firm might acquire liquid assets to cover short-term cash flow problems, either in normal operations, or in more extreme crises. As liquidity risk is a problem of cash flow management, we explain how cash flow scenario tests can be used to identify and mitigate risks. We describe liquidity adjusted risk measures used in banking. Finally, we describe how firms might create emergency plans for managing extreme and unexpected liquidity shocks.
On Monday, February 3, 2020, the results of the Iowa Democratic Party Caucus, the first caucus in the US election cycle, were delayed as a result of bugs in the software used to report the results. This software (the IowaReporterApp) was not properly tested prior to the elections, and the whole reporting system failed during the event.
The chapter begins by examining why the EU regulates, beginning with how the EU attempts to justify its regulatory power before exploring the main principles underlying EU regulation. We will then focus on who regulates in the EU, that is, the institutions, such as agencies and committees, that assist the EU in achieving its regulatory goals. The remaining sections will focus on the questions of how the EU regulates, distinguishing between the main legal and non-legal tools by which the EU regulates, and the judicial routes available to enforce or challenge the validity of such regulatory choices. Throughout, the focus will lie on the tension between efficiency and diversity that drives EU regulatory choices.
This chapter presents an example medical software life cycle process. We first introduce the topic (Section 10.1), and introduce our example project – the image-guided neuro-navigation system – that we will use to illustrate the process over the next few chapters.