scholarly journals Building a Secure Biomedical Data Sharing Decentralized App (DApp): Tutorial

10.2196/13601 ◽  
2019 ◽  
Vol 21 (10) ◽  
pp. e13601 ◽  
Author(s):  
Matthew Johnson ◽  
Michael Jones ◽  
Mark Shervey ◽  
Joel T Dudley ◽  
Noah Zimmerman

Decentralized apps (DApps) are computer programs that run on a distributed computing system, such as a blockchain network. Unlike the client-server architecture that powers most internet apps, DApps that are integrated with a blockchain network can execute app logic that is guaranteed to be transparent, verifiable, and immutable. This new paradigm has a number of unique properties that are attractive to the biomedical and health care communities. However, instructional resources are scarcely available for biomedical software developers to begin building DApps on a blockchain. Such apps require new ways of thinking about how to build, maintain, and deploy software. This tutorial serves as a complete working prototype of a DApp, motivated by a real use case in biomedical research requiring data privacy. We describe the architecture of a DApp, the implementation details of a smart contract, a sample iPhone operating system (iOS) DApp that interacts with the smart contract, and the development tools and libraries necessary to get started. The code necessary to recreate the app is publicly available.

Author(s):  
Matthew Johnson ◽  
Michael Jones ◽  
Mark Shervey ◽  
Joel T Dudley ◽  
Noah Zimmerman

UNSTRUCTURED Decentralized applications (DApps) are computer programs that run on a distributed computing system, such as a blockchain network. Unlike the client-server architecture that powers most internet applications, DApps that are integrated with a blockchain network can execute application logic that is guaranteed to be transparent, verifiable, and immutable. This new paradigm has a number of unique properties that are attractive to the biomedical and health care communities. However, instructional resources are scarcely available for biomedical software developers to begin building DApps on a blockchain. Such applications require new ways of thinking about how to build, maintain, and deploy software. This tutorial serves as a complete working prototype of a DApp, motivated by a real use case in biomedical research requiring data privacy. We describe the architecture of a DApp, the implementation details of a smart contract, a sample iPhone operating system (iOS) DApp that interacts with the smart contract, and the development tools and libraries necessary to get started. The code necessary to recreate the application is publicly available.


Author(s):  
Steve Sawyer ◽  
William Gibbons

This teaching case describes the efforts of one department in a large organization to migrate from an internally developed, mainframe-based, computing system to a system based on purchased software running on a client/server architecture. The case highlights issues with large scale software implementations such as those demanded by enterprise resource package (ERP) installations. Often, the ERP selected by an organization does not have all the required functionality. This demands purchasing and installing additional packages (known colloquially as “bolt-ons”) to provide the needed functionality. These implementations lead to issues regarding oversight of the technical architecture, both project and technology governance, and user department capability for managing the installation of new systems.


2015 ◽  
Vol 1 (2) ◽  
pp. 116
Author(s):  
Sandy Kosasi

Perancangan sistem aplikasi point of sale (POS) dapat memberikan pelayanan yang lebih baik kepada konsumen, seperti dalam perhitungan harga dan jumlah barang yang dibeli dapat menjadi lebih cepat dan kuantitas barang tidak lagi bergantung kepada pencatatan manual. Penelitian menghasilkan aplikasi POS menggunakan arsitektur client/server yang terintegrasi antar proses bisnis untuk bagian penjualan, kasir dan gudang. Pengembangan arsitektur client/server ini menggunakan sistem operasi Linux distro Redhat 9 dan Windows Xp Profesional. Penelitian ini menggunakan metode research and development dengan teknik pengumpulan data berupa observasi, wawancara, daftar pertanyaan. Perancangan aplikasi menggunakan menggunakan diagram use case, activity, sequence dan class. Hasil penelitian meliputi modul aplikasi kasir (front office), modul aplikasi gudang dan modul aplikasi laporan (back office). Modul aplikasi antara lain mencakup pengelolaan penjualan, edit data penjualan, pengisian data barang, penentuan harga barang, dan menghasilkan laporan penjualan.Point of sale (POS) application system design can give better service to the consumer, example in the price count and sum of item purchased can become faster and quantity of the item no longer rely on the manual recording. As for the research purpose is create integrated point of sale application using client/server architecture between business process to the warehouse, sales and cashier. The development of client/server architecture is using Linux operating system with distro Redhat 9.0 and windows Xp profesional. Experiment is using research and development method with technique to gather data are observation, interview, question list. This application design is using use case, activity, sequence and class diagram. The research instrument consist of cashier application (front office), warehouse application module and report application module (back office). Application module like sales management, sales data edit, equipment data insertion, pricing of the goods and generate sales report.


Author(s):  
Steve Sawyer ◽  
William Gibbons

This teaching case describes the efforts of one department in a large organization to migrate from an internally developed, mainframe-based, computing system to a system based on purchased software running on a client/server architecture. The case highlights issues with large scale software implementations such as those demanded by enterprise resource package (ERP) installations. Often, the ERP selected by an organization does not have all the required functionality. This demands purchasing and installing additional packages (known colloquially as bolt-ons) to provide the needed functionality. These implementations lead to issues regarding oversight of the technical architecture, both project and technology governance, and user department capability for managing the installation of new systems.


Author(s):  
Mary Ann Piette ◽  
Girish Ghatikar ◽  
Sila Kiliccote ◽  
David Watson ◽  
Ed Koch ◽  
...  

This paper describes the concept for and lessons from the development and field-testing of an open, interoperable communications infrastructure to support automated demand response (auto-DR). Automating DR allows greater levels of participation, improved reliability, and repeatability of the DR in participating facilities. This paper also presents the technical and architectural issues associated with auto-DR and description of the demand response automation server (DRAS), the client/server architecture-based middleware used to automate the interactions between the utilities or any DR serving entity and their customers for DR programs. Use case diagrams are presented to show the role of the DRAS between utility/ISO and the clients at the facilities.


2014 ◽  
Vol 556-562 ◽  
pp. 5194-5197
Author(s):  
Lian Fen Huang ◽  
Wei Huang ◽  
Xian Long Yang ◽  
Yu Liang Tang

Broadband trunking communication system has been widely used with a variety of industries, such as public transportation security and navigation, etc. Trunking communication is a branch of mobile communication. Because the client of traditional dispatch services based on C/S (client/server) architecture need to install the client software, this paper studies and designs one dispatch client, which is based on B/S (browser/server) architecture.


Sign in / Sign up

Export Citation Format

Share Document