We perform a structural estimation of the preference parameters in a buffer-stock consumption model augmented with temptation disutility. We adopt a two-stage Method of Simulated Moments methodology to match our simulated moments with those observed in the US Survey of Consumer Finances. To identify the parameters we use liquid and quasi-liquid (retirement) wealth holdings at different ages as ...

At ICALEPCS '09, we introduced a source code generator that allows processes to communicate safely using data types native to each host language[1]. In this paper, we discuss further development that has occurred since the conference in Kobe, Japan, including the addition of three more client languages, an optimization in network packet size and the addition of a new protocol data type.

Vx86 is the first static analyzer for sequential Intel x86 assembler code using automated deductive verification. It proves the correctness of assembler code against function contracts, which are expressed in terms of pre-, post-, and frame conditions using first-order predicates. Vx86 takes the annotated assembler code, translates it into C code simulating the processor, and then uses an exist...

Setback in elevation of a structure is a special irregularity with considerable effect on its seismic performance. This paper addresses multistory Reinforced Concrete (RC) frame buildings, regular and irregular in elevation. Several multistory Reinforced Concrete Moment Resisting Frames (RCMRFs) with different types of setbacks, as well as the regular frames in elevation, are designed according...

A certifying compiler takes a source language program and produces object code as well as a certi cate that can be used to verify that the object code satis es desirable prop erties such as type safety and memory safety Certifying compilation helps to increase both compiler robustness and program safety Compiler robustness is improved since some compiler errors can be caught by checking the obj...

Current approaches to mobile code safety—inspired by the technique of Proof-Carrying Code (PCC) [4]—associate safety information (in the form of a certifícate) to programs. The certifícate (or proof) is created by the code supplier at compile time, and packaged along with the untrusted code. The consumer who receives the code+certiñcate package can then run a checker which, by a straightforward...

Proof-Carrying Code (PCC) allows a code producer to provide to a host a program along with its formal safety proof. The proof attests a certain safety policy enforced by the code, and can be mechanically checked by the host. While this language-based approach to code certification is very general in principle, existing PCC systems have only focused on programs whose safety proofs can be automat...

Proof-Carrying Code (PCC) is a technique that can be used for safe execution of untrusted code. In a typical instance of PCC, a code receiver establishes a set of safety rules that guarantee safe behavior of programs, and the code producer creates a formal safety proof that proves, for the untrusted code, adherence to the safety rules. Then, the receiver is able to use a simple and fast proof v...

This paper presents a process for the refinement of safety-critical source code into a more tractable representation. For large software-intensive information systems, the safety engineering view of the system reveals a “long thin slice” of hazard-related software involving a number of different software components. The hazard-related software is documented in the system “safety verification ca...