Programming-in-the-Large Versus Programming-in-the-Small

DeRemer, Frank; Kron, Hans H.

doi:10.1109/tse.1976.233534

Cited by 291 publications

(18 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Thus, wrapping script handling through workflow technology increases the level of abstraction for the operators as they do not have to deal with the deep technical details of script handling [15]. This is in line with the programming-in-the-large idea by DeRemer and Kron [8], which is applied by the workflow technology, too [20].…”

Section: Scripts and Plansmentioning

confidence: 87%

TOSCA: Portable Automated Deployment and Management of Cloud Applications

Binz

Breitenbücher

Kopp

et al. 2013

Advanced Web Services

166

122

View full text Add to dashboard Cite

Portability and automated management of composite applications are major concerns of today's enterprise IT. These applications typically consist of heterogeneous distributed components combined to provide the application's functionality. This architectural style challenges the operation and management of the application as a whole and requires new concepts for deployment, configuration, operation, and termination. The upcoming OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) standard provides new ways to enable portable automated deployment and management of composite applications. TOSCA describes the structure of composite applications as topologies containing their components and their relationships. Plans capture management tasks by orchestrating management operations exposed by the components.This chapter provides an overview on the concepts and usage of TOSCA.

show abstract

Section: Scripts and Plansmentioning

confidence: 87%

TOSCA: Portable Automated Deployment and Management of Cloud Applications

Binz

Breitenbücher

Kopp

et al. 2013

Advanced Web Services

166

122

View full text Add to dashboard Cite

show abstract

“…While these existing works about application decomposition align well with our design choice, where we incorporate device's capabilities into the application modeling, they do not provide a unified programming model for the fog application developers. Thus, a programming-in-the-large mindset 19 is still relevant to build and deploy applications in large scale fog computing environment.…”

Section: Related Workmentioning

confidence: 99%

Developing applications in large scale, dynamic fog computing: A case study

2019

View full text Add to dashboard Cite

Summary In recent years, fog computing has emerged as a new distributed system model for a large class of applications that are data‐intensive or delay‐sensitive. By exploiting widely distributed computing infrastructure that is located closer to the network edge, communication cost and service response time can be significantly reduced. However, developing this class of applications is not straightforward and requires addressing three key challenges, ie, supporting the dynamic nature of the edge network, managing the context‐dependent characteristics of application logic, and dealing with the large scale of the system. In this paper, we present a case study in building fog computing applications using our open source platform Distributed Node‐RED (DNR). In particular, we show how applications can be decomposed and deployed to a geographically distributed infrastructure using DNR, and how existing software components can be adapted and reused to participate in fog applications. We present a lab‐based implementation of a fog application built using DNR that addresses the first two of the issues highlighted earlier. To validate that our approach also deals with large scale, we augment our live trial with a large scale simulation of the application model, conducted in Omnet++, which shows the scalability of the model and how it supports the dynamic nature of fog applications.

show abstract

“…Software was becoming a commodity-built at one location used at another-so that code portability and quality were serious concerns, as previously mentioned. Software systems were becoming larger, hierarchical and layered [33,34]. Emerging ideas of control/data abstraction and data hiding were aimed at reducing the difficulty and complexity of building these larger systems.…”

Section: The Context: Software Engineering and Programming Languages mentioning

confidence: 99%

Language design and analyzability: a retrospective

Ryder

Wiedermann

2011

Softw Pract Exp

View full text Add to dashboard Cite

SUMMARY There is tension between programming language design for modularity and flexibility of programming and the amenability of the resulting programs to static analysis. At the start of Software Practice and Experience in 1971, most languages in commercial use were procedural (e.g., FORTRAN, ALGOL, PL/I) and on the whole were easier to analyze than languages of today such as JavaScript and Python. Modern languages include dynamic features, which enhance prototyping of approaches, often resulting in programs that are difficult for software tools or humans to understand. Starting with this perspective, we explore the relationship between language features and the ability of static analysis to precisely determine control flow and data flow in programs, thus enabling program optimization, transformation and understanding. Copyright © 2011 John Wiley & Sons, Ltd.

show abstract

Programming-in-the-Large Versus Programming-in-the-Small

Cited by 291 publications

References 10 publications

TOSCA: Portable Automated Deployment and Management of Cloud Applications

TOSCA: Portable Automated Deployment and Management of Cloud Applications

Developing applications in large scale, dynamic fog computing: A case study

Language design and analyzability: a retrospective

Contact Info

Product

Resources

About