Demo Data from VLDB 2026 / reviewers in the wild / expert
Ramesh Bharadwaj
dblp:45/235
· DBLP profile ↗
14ranked-venue papers
5as first author
3since 2021 · last 2025
0009-0008-3214-307XORCID · corroborated
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 9 · 5 first-authorComputer networks · 3 · 3 since 2021Theory of computation · 2Applied, interdisciplinary, general and emerging computing · 2 · 2 first-authorSystems, architecture and hardware · 1Security and privacy · 1
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Software engineering, system software, and programming languages
2 papers |
Requirements engineering and software design · 100% | |
| Theoretical computer science
2 papers |
Automated reasoning and model checking · 100% |
Topics — the 6 heaviest of 8, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Requirements engineering and software design › inconsistency management
consistency checking |
0.0 | 1 | 1998 | Using Abstraction and Model Checking to Detect Safety Violations in Requirements Specifications · IEEE Trans. Software Eng. 1998 |
Requirements engineering and software design
requirements analysis |
0.0 | 1 | 1998 | SCR*: A Toolset for Specifying and Analyzing Software Requirements · CAV 1998 |
Requirements engineering and software design
requirements specification |
0.0 | 1 | 1998 | SCR*: A Toolset for Specifying and Analyzing Software Requirements · CAV 1998 |
Requirements engineering and software design › requirements analysis
requirements specification analysis |
0.0 | 1 | 1998 | Using Abstraction and Model Checking to Detect Safety Violations in Requirements Specifications · IEEE Trans. Software Eng. 1998 |
Automated reasoning and model checking › model checking › state space reduction
abstract model checking |
0.0 | 1 | 1998 | Using Abstraction and Model Checking to Detect Safety Violations in Requirements Specifications · IEEE Trans. Software Eng. 1998 |
Automated reasoning and model checking
model checking |
0.0 | 1 | 1998 | Using Abstraction and Model Checking to Detect Safety Violations in Requirements Specifications · IEEE Trans. Software Eng. 1998 |
Methods — techniques the papers use, named apart from their topics
simulation · 0.0model checking · 0.0abstraction · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2025 | Data Rate Control for Closing Networked Control System Loop Over Costly Wireless ChannelabstractLoRa is a low power, long range modulation scheme that has grown in popularity in recent years. Wireless sensors utilizing LoRa have very limited bandwidth, particularly in regions like the EU, that impose strict 1% duty cycles. Thus, it is critical to reduce the number of transmissions while still meeting performance goals. In doing so, these sensors can greatly improve the quality of service and extend the battery life of the sensors. The importance of efficient bandwidth usage is amplified in time critical applications, such as in feedback control. In this work, we studied event-based transmission schemes used for sampling the state of a control system. Modern communication protocols, such as LoRa, have different transmission options to match transmission rates to channel quality. To model these transmission options, we extended past work by modeling the option to use different transmission schemes, which have independent packet drop rates and quantization error. To this end, we developed model based algorithms to allow nodes to adapt to unknown channel conditions when transmitting packets. We verified the performance of these algorithms in simulation and compared them to previous work. Frederick M. Chache, Caden J. Pici, Ramesh Bharadwaj |
ICC | 3 |
| 2025 | Effects of Lossy Compression on the Value of Information in a Low Powered NetworkabstractLow power, long range wireless sensor networks (WSMs) have found many applications, but are often limited to small packets and low data rates. To improve data throughput, lossy compression can be utilized. This however, induces distortion in the data which can harm the accuracy of the underlying applications. This can be especially dangerous in safety critical applications, where incorrect classifications can cause serious harm, but a lack of new updates can be just as dangerous. In this paper, we provided an example application, nodes transmitting images to a back-end classifier. The effects of distortion on classification accuracy were studied, and different metrics were examined to better predict the usefulness of the data transmitted. These metrics were used to develop models to predict the VoI for a given compression ratio (CR). With these models, we developed a reward function to provide a trade-off between timeliness of data and the precision of the data. We used this to develop algorithms which can adjust to changing channel conditions to provide the most useful information possible, in a range of network traffic conditions. In this way, data quality can degrade gently as channel traffic increases. This provided more value to back-end nodes than with other methods tested. Frederick M. Chache, Caden J. Pici, Ramesh Bharadwaj |
WoWMoM | 3 |
| 2023 | Effects of Lossy Compression on the Age of Information in a Low Power Network
Frederick M. Chache, Sean Maxon, Ram M. Narayanan, Ramesh Bharadwaj |
WoWMoM | 4 |
| 2015 | Reasoning about security in sensor networksabstractSummary We present a formal framework for reasoning about security concerns in the context of embedded sensor networks. We first provide an agent‐based programming model for sensor networks. A logical framework enables reasoning about security, safety, and integrity with respect to usage of resources in this model. Embedded sensor networks often operate in rapidly changing mission‐critical environments where both functional and nonfunctional requirements can alter dynamically in an unforeseen manner. The network may need to be reconfigured and reprogrammed in response to changes in its operating conditions. We provide a framework based on counterfactual logic to formally represent changes to the system and perform what‐if reasoning about their impact on security and safety even before they have been applied. Copyright © 2015 John Wiley & Sons, Ltd. Manuel Peralta, Supratik Mukhopadhyay, Ramesh Bharadwaj |
Concurr. Comput. Pract. Exp. | 3 |
| 2011 | Counterfactually reasoning about securityabstractIn this short paper, we provide the background to counterfactual logic and give very general suggestions on how we could employ this logic to help us reason about security policies. It seems very appropriate to use this kind of logic to anticipate a change that will compromise the security concerns of a given system before actually applying the changes. Manuel Peralta, Supratik Mukhopadhyay, Ramesh Bharadwaj |
SIN | 3 |
| 2008 | A Formal Approach to Developing Reliable Event-Driven Service-Oriented SystemsabstractIn this paper, we present a formal framework for developing distributed service-oriented systems in an event-driven secure synchronous programming environment. More precisely, we present a synchronous programming language called SOL (Secure Operations Language) that has (i) capabilities for handling service invocations asynchronously, (ii) strong typing to ensure enforcement of information flow and security policies, and (iii) the ability to deal with failures (both benign and byzantine) of components. SOL is supported by formal operational semantics. Applications written in our framework can be verified using formal static checking techniques like theorem proving. The framework runs on the top of the SINS (secure infrastructure for networked systems) infrastructure that we have developed. Ramesh Bharadwaj, Supratik Mukhopadhyay |
COMPSAC | 1 |
| 2007 | RE Theory Meets Software Practice: Lessons from the Software Development TrenchesabstractBased on our recent experience in four projects, each focused on either security-critical or safety-critical software, this paper evaluates several notions, widely held by RE researchers, for their utility in practical software development. It describes four notions which in our view work in practice and five others which do not. Constance L. Heitmeyer, Ralph D. Jeffords, Ramesh Bharadwaj, Myla Archer |
RE | 3 |
| 2005 | What Is SINS?abstractThe goal of the NRL secure middleware project (SINS) is to develop infrastructure for the deployment and protection of time- and mission-critical applications on a distributed computing platform, in a hostile computing environment such as the Internet, while using unreliable or untrusted COTS components. In this project, we are rethinking basic ways in which distributed applications are developed, deployed, configured, and maintained. Such a methodology and infrastructure are crucial for the deployment of mission-critical applications in a collaborative environment spanning multiple sites, by multiple agencies, and across multiple enterprises. Ramesh Bharadwaj |
COMPSAC (2) | 1 |
| 2005 | Extended abstract: formal verification of architectural patterns in support of dependable distributed systemsabstractBuilding robust, secure distributed systems in the presence of transient faults, node failures, and changes in network topology poses a multitude of challenges. To meet current engineering challenges such as pervasive and ubiquitous computing, one must adopt model-driven approaches to build distributed applications. We propose the synchronous paradigm for component integration and coordination: developers use an abstraction that respects the synchrony hypothesis, i.e., each external event is processed by the system completely before the arrival of the next event. Based on the synchronous model, the Secure Operations Language (SOL) is designed as a verifiable language for the integration of high assurance systems. Ralph D. Jeffords, Ramesh Bharadwaj |
MEMOCODE | 2 |
| 2004 | Introduction
Ramesh Bharadwaj, Robert J. Hall 0001 |
Autom. Softw. Eng. | 1 |
| 2000 | Salsa: Combining Constraint Solvers with BDDs for Automatic Invariant Checking
Ramesh Bharadwaj, Steve Sims |
TACAS | 1 |
| 1999 | Model Checking Complete Requirements Specifications Using Abstraction
Ramesh Bharadwaj, Constance L. Heitmeyer |
Autom. Softw. Eng. | 1 |
| 1998 | SCR*: A Toolset for Specifying and Analyzing Software Requirements
Constance L. Heitmeyer, James Kirby, Bruce G. Labaw, Ramesh Bharadwaj |
CAV | 4 |
| 1998 | Using Abstraction and Model Checking to Detect Safety Violations in Requirements SpecificationsabstractExposing inconsistencies can uncover many defects in software specifications. One approach to exposing inconsistencies analyzes two redundant specifications, one operational and the other property-based, and reports discrepancies. This paper describes a "practical" formal method, based on this approach and the SCR (software cost reduction) tabular notation, that can expose inconsistencies in software requirements specifications. Because users of the method do not need advanced mathematical training or theorem-proving skills, most software developers should be able to apply the method without extraordinary effort. This paper also describes an application of the method which exposed a safety violation in the contractor-produced software requirements specification of a sizable, safety-critical control system. Because the enormous state space of specifications of practical software usually renders direct analysis impractical, a common approach is to apply abstraction to the specification. To reduce the state space of the control system specification, two "pushbutton" abstraction methods were applied, one which automatically removes irrelevant variables and a second which replaces the large, possibly infinite, type sets of certain variables with smaller type sets. Analyzing the reduced specification with the model checker Spin uncovered a possible safety violation. Simulation demonstrated that the safety violation was not spurious but an actual defect in the original specification. Constance L. Heitmeyer, James Kirby, Bruce G. Labaw, Myla Archer, Ramesh Bharadwaj |
IEEE Trans. Software Eng. | 5 |