From Trade-only to Zero-Value NFTs: The Asset Proxy NFT Paradigm in Web3

Many implementations of smart contracts available in NFT marketplaces today allow the modification of NFT token attributes, without any specific mechanism to control the consistency with off-chain metadata. We believe this is a weakness in overall design of NFTs today. We propose a computation model called the Asset Proxy NFT that guarantees the consistency between the NFT token (on-chain) and its corresponding asset metadata (off-chain). In general, the proposed model can be applied to any type of NFT that requires immutability or controlled mutability of metadata. A second contribution of this paper is the notion of the NFT design patterns which recognizes that a coherent framework for dealing with hybrid assets is required, and that for specific hybrid-asset deployments, suitable technological components must be utilized under the framework.Comment: 15 pages, 2 figure

Evolution Handling in PSEEs

The move to more mature software development processes (in the sense of the CMM approach [1]) implies a significant emphasis on process evolution. Currently, Process-centred Software Engineering Environments (PSEEs) are providing means to define and enact process models. However, consistent process and process model evolution still presents considerable difficulties. A major reason is the commonplace deviation between the enactment of a process model and the corresponding activities (process performance) taking place in the real world. In this paper, we analyse the evolution problem and we identify the core requirements for an enhanced PSEE architecture for evolution handling. Then we propose a generic PSEE architecture for consistent process and process model evolution and we describe the experimentation of our theoretical results, done using the Process Weaver system [2]. Keywords: process modelling, process evolution, meta-process, consistency management, architecture for process-c..

Software Engineering 2.0 & Research 2.0

International audienceSoftware systems are engineering artifacts of increasing complexity. Development of ultra large-scale systems, management of geographically distributed teams, integration of multiple products and large legacy migration are typical activities composing the current software process landscape