M. Mira da Silva

  • Citations Per Year
Learn More
Current RPC mechanisms for persistent languages are either pass by reference — in which case they do not scale — or pass by copy — in which case they duplicate objects and destroy sharing relationships. In this paper we argue that to build very large distributed persistent applications a compromise between these two mechanisms is needed. The ultimate goal(More)
The paper describes how a persistent programming language can be used to implement an RPC mechanism that automatically supports type-safety. It is type-safe since the expected interface is checked against the actual remote procedure interface before a call is attempted, and automatic because user intervention is that already needed to call a normal local(More)
In the last three years we have been working with persistence and distribution, in particular migration of higher-level objects (such as procedures) between autonomous persistent programs. In this paper we introduce persistence and the suitability of Napier88 | the persistent system we have used for our experiments | as an agent language. We then present a(More)
The ITIL framework is the best known set of best practices for managing IT services. In this paper we introduce process mining as a useful technique for assessing whether a business process is implemented according to ITIL guidelines. We evaluated our approach using a real-world case study in an IT vendor developing a complex software platform. The company(More)
The traditional approach for building distributed applications is by calling a procedure in another store using an RPC mechanism. However, an RPC requires a round-trip network delay for every call and makes each store dependent on the availability of other stores. A solution to this problem is to migrate the remote objects needed to the client store, and in(More)
An orthogonally persistent programming language is a type-safe programming language that seamlessly includes a database for long-term object storage. A remote procedure call (RPC) mechanism permits calls of a procedure in another address space, and has proved to be a useful tool for building distributed systems. Taken together, an RPC mechanism and a(More)
Integration needs are difficult to predict and solve appropriately, and this leads to multiple partial solutions that lack a broader vision of the problem. The Enterprise Architecture defines a global view of the business data and processes, and of the applications that manage and support them. In this paper, we propose an integration methodology based on(More)
  • 1