scispace - formally typeset
Search or ask a question
JournalISSN: 1660-1769

The Journal of Object Technology 

EtH Zurich
About: The Journal of Object Technology is an academic journal published by EtH Zurich. The journal publishes majorly in the area(s): Unified Modeling Language & Software development. It has an ISSN identifier of 1660-1769. It is also open access. Over the lifetime, 940 publications have been published receiving 14078 citations. The journal is also known as: Journal of Object Technology.


Papers
More filters
Journal ArticleDOI
TL;DR: This paper lays the foundations of COP, shows how dynamic layer activation enables multi-dimensional dispatch, illustrates the application of COP by examples in several language extensions, and demonstrates that COP is largely independent of other commitments to programming style.
Abstract: Context-dependent behavior is becoming increasingly important for a wide range of application domains, from pervasive computing to common business applications. Unfortunately, mainstream programming languages do not provide mechanisms that enable software entities to adapt their behavior dynamically to the current execution context. This leads developers to adopt convoluted designs to achieve the necessary runtime exibility. We propose a new programming technique called Context-oriented Programming (COP) which addresses this problem. COP treats context explicitly, and provides mechanisms to dynamically adapt behavior in reaction to changes in context, even after system deployment at runtime. In this paper, we lay the foundations of COP, show how dynamic layer activation enables multi-dimensional dispatch, illustrate the application of COP by examples in several language extensions, and demonstrate that COP is largely independent of other commitments to programming style.

457 citations

Journal ArticleDOI
TL;DR: An overview and a personal perspective on the roots of FOSD, connections to other software development paradigms, and recent developments in this field are given.
Abstract: Feature-oriented software development (FOSD) is a paradigm for the construction, customization, and synthesis of large-scale software systems. In this survey, we give an overview and a personal perspective on the roots of FOSD, connections to other software development paradigms, and recent developments in this field. Our aim is to point to connections between different lines of research and to identify open issues.

436 citations

Journal ArticleDOI
TL;DR: In this article, the authors define a programming methodology for using object invariants, which enriches a program's state space to express when each object invariant holds, deals with owned object components, ownership transfer, and subclassing, and is expressive enough to allow many interesting object-oriented programs to be specified and verified.
Abstract: An object invariant defines what it means for an object’s data to be in a consistent state. Object invariants are central to the design and correctness of objectoriented programs. This paper defines a programming methodology for using object invariants. The methodology, which enriches a program’s state space to express when each object invariant holds, deals with owned object components, ownership transfer, and subclassing, and is expressive enough to allow many interesting object-oriented programs to be specified and verified. Lending itself to sound modular verification, the methodology also provides a solution to the problem of determining what state a method is allowed to modify.

360 citations

Journal ArticleDOI
TL;DR: Cloud computing is in its infancy in terms of market adoption, but it is a key IT megatrend that will take root and discusses technical issues that are expected to be addressed.
Abstract: During the past few years, cloud computing has become a key IT buzzword. Although the definition of cloud computing is still “cloudy”, the trade press and bloggers label many vendors as cloud computing vendors, and report on their services and issues. Cloud computing is in its infancy in terms of market adoption. However, it is a key IT megatrend that will take root. This article reviews its definition and status, adoption issues, and provides a glimpse of its future and discusses technical issues that are expected to be addressed.

356 citations

Journal ArticleDOI
TL;DR: The different types of security requirements are defined and associated examples and guildlines are provided with the intent of enabling requirements engineers to adequately specify security requirements without unnecessarily constraining the security and architecture teams from using the most appropriate security mechanisms for the job.
Abstract: Most requirements engineers are poorly trained to elicit, analyze, and specify security requirements, often confusing them with the architectural security mechanisms that are traditionally used to fulfill them. They thus end up specifying architecture and design constraints rather than true security requirements. This article defines the different types of security requirements and provides associated examples and guildlines with the intent of enabling requirements engineers to adequately specify security requirements without unnecessarily constraining the security and architecture teams from using the most appropriate security mechanisms for the job.

242 citations

Performance
Metrics
No. of papers from the Journal in previous years
YearPapers
202318
202235
20217
202052
201935
20189